Get Unstuck from ICS Leak 200 (AKA Upgrading from 200 to 206) INSTRUCTIONS

[buddyrich]

It works.

This information should not be kept hidden; Motorola will fix the vulnerability and then someone else will find another one for the next update. Whether a new rooting technique is discovered and shared or discovered and kept a secret, the only difference it makes is the pointless frustration in the mean time.

I can't think of any reason that those who are stuck unable to use their device to its full potential should have to wait for a way to obtain root permissions if a method is available, strictly for the sake of preserving the effectiveness of that technique which will likely be rendered ineffective by the next update anyway.

 

[1989trouble07]

It works.

This information should not be kept hidden; Motorola will fix the vulnerability and then someone else will find another one for the next update. Whether a new rooting technique is discovered and shared or discovered and kept a secret, the only difference it makes is the pointless frustration in the mean time.

I can't think of any reason that those who are stuck unable to use their device to its full potential should have to wait for a way to obtain root permissions if a method is available, strictly for the sake of preserving the effectiveness of that technique which will likely be rendered ineffective by the next update anyway.

am I missing something? All I get is permission denied error while executing the commands.

 

[orangechoochoo]

It works.

This information should not be kept hidden; Motorola will fix the vulnerability and then someone else will find another one for the next update. Whether a new rooting technique is discovered and shared or discovered and kept a secret, the only difference it makes is the pointless frustration in the mean time.

I can't think of any reason that those who are stuck unable to use their device to its full potential should have to wait for a way to obtain root permissions if a method is available, strictly for the sake of preserving the effectiveness of that technique which will likely be rendered ineffective by the next update anyway.

What are you on, GB to leak or leak to leak?

 

[buddyrich]

Leak to leak.

 

[buddyrich]

am I missing something? All I get is permission denied error while executing the commands.

You can't execute the commands in a terminal emulator on the phone, they have to be executed via adb; or, you can try the script I posted in the original thread.

 

[1989trouble07]

You can't execute the commands in a terminal emulator on the phone, they have to be executed via adb; or, you can try the script I posted in the original thread.

I'm using adb. I can't even change directory to "/sdcard" with adb, it just says permission denied.. I can change to /sdcard with terminal emulator though. Lol.

 

[Danis]

Your mass USB mass storage mode is enabled. Put your phone to camera mode in the USB options then you can get into the /sdcard folder.

Sent from my XT894 running ICS

 

[1989trouble07]

Thanks I've been up for hours trying to figure that part out. Lol.
I now have root again. Sweet. Ha

 

[adventuretuber]

Try redownloading the 206 image file and put your sd card in another phone and redownload the full 206 update then put it iback in your phone. Then start over. Maybe one of the downloads is corrupt.

If that fails still you should still be able to reflash 200.

I feel like a giant goon. I wasn't unzipping the .206 and .208 downloads to pull apart the update and the crc file. Now that I have, everything is swimming right along. Thanks again to all of the more competent people who have been posting here.

 

[siggma]

I'm trying to think out loud about retaining root for those who upgrade from 206 to 208 because doing the upgrade removes root and there currently is no way to root ICS. Right now I have rooted 206 using rootkeeper when I went from 219 to 206. The files that rootkeepr modded in 206 to retain root, can that be copied and flashed separately after upgrading to 208 so we can keep root? Rootkeeper doesn't use an exploit to root, it saves the SU and reactivates it. People have been having trouble because when rootkeeper tries to reactivate SU some of the paths have been changed when using the unstick method to go from 200 to 206, and presumably from 206 to 208. So if there is some way to save and restore/flash whatever was changed during the unstick process then rootkeepr may still work.

Basically the process would copy the files that contain the paths that allows rootkeeper to work on 206. Then use the unstick method to upgrade from 206 to 208. Then flash those files back and then rootkeepr will have the correct files & paths so it can retain root in 208.

Just make a backup manually. Open a terminal, find su and make a backup copy somewhere like in /data/local or in /tmp or in /usr/src. Make several copies and name them su-somethig. Then when you get the new version up and running go find your su-something and execute it. Then copy it to /system/xbin/su or /system/bin/su

Like this; From a terminal, commands with a # require root access.

first run su to gain root.
$su
You should now have a # prompt.
#which su
This will tell you where the su binary is located.
Assuming it's in /system/bin/ do the commands below.
If it's in /system/xbin or /xbin you'll need to substitute that path for /system/bin below.

#cp /system/bin/su /data/local/su-something # copy and rename su in one step
make another backup elsewhere...
#cp /system/bin/su /tmp/su-something # make another copy elsewhere
make a third backup just in case
#mkdir -p /usr/src
#cp /system/bin/su /usr/src/su-something # make a third copy /usr/src will probably be left alone during patching and updating.

Install 208, once up on 208 use a terminal to gain root:
$/data/local/su-something
You should see a # sign for the prompt. If this fails try the other locations you saved it:
$/tmp/su-something
or
#/usr/src/su-something

If you get "permission denied" you're screwed.
If it runs you'll have root again then you can:
cp /usr/src/su-something /system/bin/su
or
cp /data/local/su-something /system/bin/su
or
.... you get the idea.

Then go back and delete the unwanted copies:
rm /data/local/su-something
rm /tmp/su-something
rm /usr/src/su-something

This should retain root unless the SHELL user is prohibited from running su... I managed to copy the su binary to my phone using abd push but it won't run even though it's marked executable. I think the shell user is prohibited from running the su binary. I haven't looked all all the meta for the su binary or poked around at user 2000 permissions but I might be able to get it to run if I keep tinkering.

 

[orangechoochoo]

I'm on 208 with root!dancedroid

As a rundown, I was on 206 from 219. Followed the instructions for Unsticking to move to 208. Then ran the ICS root script. I didn't see Superuser in the app drawer so I downloaded it from the market, installed it, and now I'm rooted! I installed and ran a few apps that require SU and as usual the prompt comes up for SU permissions, so it definitely works.

 

[siggma]

No...because you can't flash back to an older kernel/bootloader. The updating procedure (OTA, fastboot, whatever) does not allow for it.

There is no way to actually flash an older kernel back to the device.

Not true. I flashed (via ap-fastboot and windows shell) the 208 kernel in preparation for update to 208 but was unsuccessful at updating to 208 system so I went back to 206 and re-flashed the older kernel and it worked fine. I don't think it's looking at the kernel itself, only at the kernel version string and apparently not even at the minor kernel version but only at the major. GB is 2.6.---, ICS is 3.0.---. In any case it's the CDT that prevent flashing an older kernel, not any gremlin or magic code checker in the update. If the CDT were turned off you could flash anything you wanted for a kernel. If the kernel version check in the OTA update is says "yes" you can update to any kernel you want. How the eFuse works to generate flash and boot errors is still somewhat of a mystery, at least to me.

 

[r314bd]

I'm on 208 with root!dancedroid

As a rundown, I was on 206 from 219. Followed the instructions for Unsticking to move to 208. Then ran the ICS root script. I didn't see Superuser in the app drawer so I downloaded it from the market, installed it, and now I'm rooted! I installed and ran a few apps that require SU and as usual the prompt comes up for SU permissions, so it definitely works.

Good deal. Was waiting for a few confirmations, I think I'll do the .206 -> .208 upgrade tonight as well.

 

[orangechoochoo]

Not true. I flashed (via ap-fastboot and windows shell) the 208 kernel in preparation for update to 208 but was unsuccessful at updating to 208 system so I went back to 206 and re-flashed the older kernel and it worked fine. I don't think it's looking at the kernel itself, only at the kernel version string and apparently not even at the minor kernel version but only at the major. GB is 2.6.---, ICS is 3.0.---. In any case it's the CDT that prevent flashing an older kernel, not any gremlin or magic code checker in the update. If the CDT were turned off you could flash anything you wanted for a kernel. If the kernel version check in the OTA update is says "yes" you can update to any kernel you want. How the eFuse works to generate flash and boot errors is still somewhat of a mystery, at least to me.

He is talking about going back to the GB kernel. I suppose you could try the Unstick method as follows:

Flash 219
Flash 219 kernel
Install 219 via recovery

If it works then great! If not then use the Unstick method to go back to an ICS leak.

 

[kenji91]

I'm on 208 with root!dancedroid

As a rundown, I was on 206 from 219. Followed the instructions for Unsticking to move to 208. Then ran the ICS root script. I didn't see Superuser in the app drawer so I downloaded it from the market, installed it, and now I'm rooted! I installed and ran a few apps that require SU and as usual the prompt comes up for SU permissions, so it definitely works.

Can you give me a link to the "ICS root script" ? I want to try this, but I'm afraid of losing root and I'm still not sure what .208 has that .206 doesn't.