Develop Bugs

[Howto] Update rooted 3G Xoom to 3.1 and get root

To make things easier here is a link to BRD's update to 3.1 I suggest you check it out for an easy upgrade to 3.1.
http://forum.xda-developers.com/showthread.php?t=1074609
If you are already on 3.1 just flash the stock HRI66 system image and Tiamats boot image to get sd card support back from there you should be able to run BRDs update from the SD card in clockwork
I did this using CWR on a rooted Xoom
1. Copy the update to your sdcard and name it update.zip
2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
4. Then back to fastboot and flash the root31.img to your boot partion (link below)
5. Then reboot your xoom and push su using koush's original root instructions and you are rooted running 3.1
6. You can then use rom manager to reflash CWR.
Link to post with root31.img
http://forum.xda-developers.com/showthread.php?t=1073298
Other files easily found on xda
Just have to wait for an updated kernel to has sdcard support back.
All credit goes to the people that did the actual work I'm just listing instructions. And of course you assume all risk in flashing and modding your device.
Sent from my Xoom using my Xoom

After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk

dch921 said:
6. You can then use rom manager to reflash CWR.
Click to expand...
Click to collapse
Just use fastboot. That's what it's there for.

JFMFT said:
After using this method to update, could we re-flash a custom kernel (such as Tiamat 1.4.1) - or would that be incompatible for some reasonn with the 3.1 update?
Nice find/tutorial... this may be what many of us have been waiting for. Me, personally, I am waiting for a flashable .zip one-step update process. I maintain hope that it'll happen =)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Haven't tried it but worse case scenario just reflash root31.img
Sent from my Xoom using my Xoom

Nice! It worked perfectly!

I tried flashing Tiamat 1.4.1, wouldn't recommend it, you'll have to go right back to stock.

I am doing this right now on my XOOM. I will update this post when I am done.
Thank you for the instructions
EDIT: works perfectly!!
Got confused at first and followed the whole guide to originally root...but then realized that you do not flash rootboot.img.
Only do the following code:
1. adb remount
2. adb push su /system/bin
3. adb shell
4. ln –s /system/bin/su /system/xbin/su
5. chmod 4755 /system/bin/su
6. exit
7. adb push Superuser.apk /system/app
Click to expand...
Click to collapse

props worked great

Cansay that this worked great. I love the update and I love keeping my root. The device is running smoothly with the stock 3.1. Good post indeed.
Sent from my Xoom using Tapatalk

So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.

2. Then you must flash the HRI66 stock boot and system imgs. No data is lost
3. After flashing through fastboot go directly to CWR and install update.zip from SD card
Click to expand...
Click to collapse
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.

sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
This instruction is very unclear...

Blades said:
So a custom boot.img is a no go? Is this because of the different kernel or the (possibly different) initrd... for those that are confused by this question - remember a boot.img is comprised of the ramdisk and the kernel.
Click to expand...
Click to collapse
Of course not. You can have a ramdisk with ro.secure 0 and the stock kernel, or you can use any kernel you like that will run.
(IMO, it's better to root with as small a change as needed, and if you want to use a different kernel, you can do so if you want separate to the decision of wanting root)

sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
Again, just use fastboot (because it's unlocked), then reboot into recovery. Does that not work?

ljwnow said:
This instruction is very unclear...
Click to expand...
Click to collapse
No its pretty simple you must not know what your doing

sooner2k1 said:
How is step 3 possible? Every time I do step 2 I lose root (loading stock boot.img), and thus can't open CWR? Is there a way to get to CWR and install update.zip without root? I'm using it by going into recovery via an app.
Click to expand...
Click to collapse
after you flashing boot.img and HRI66 system.img, type this in cmd, fastboot reboot
xoom will reboot to normal mode, then wait untill it completly settle to home screen, it will take sometime (it seems like bootloop but it does not, HC doing re-dalvik cache, so it takes time)..after it boot to normal mode type this in cmd, adb reboot recovery
you will reboot to cwm recovery (i'm guessing you have flash cmw before on 3.0.1) then follow the OP steps..
i'm on 3.1 now.. with no data loose and rooted ;-)

I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks

wsuo2006 said:
I am just wondering if sd card support is still there after the update (I am using tiamat kernel). Thanks
Click to expand...
Click to collapse
No sdcard support until we get a new kernel
Sent from my Xoom using my Xoom

I was wondering if anyone could package the stock 3.0.1 kernel and system.img into an update.zip so this can all be done using rom manager? Thinking about it most likely not cause moto has been pulling system dump images
Sent from my Xoom using XDA Premium App

dch921, would it be possible for you to please add the relevant links to your OP instead of saying to search XDA for them? If you do this, I will gladly sticky this guide.
Thanks!

Cannot find recovery-from-boot.p

Hello. I'm not eligible to post in the development section so I'm posting it here instead. So I've unlocked the bootloader and rooted the phone via the GNex Toolkit 3.0. My next step is flashing CWM but since I'm keeping my stock rom, I need to delete recover-from-boot.p from /system.
However, I can't find this file anywhere in the /system folder. I'm using root explorer, btw. Should I just go ahead and flash CWM and not worry about the stock recovery coming back?
Thanks in advance.

gtm3nky said:
Hello. I'm not eligible to post in the development section so I'm posting it here instead. So I've unlocked the bootloader and rooted the phone via the GNex Toolkit 3.0. My next step is flashing CWM but since I'm keeping my stock rom, I need to delete recover-from-boot.p from /system.
However, I can't find this file anywhere in the /system folder. I'm using root explorer, btw. Should I just go ahead and flash CWM and not worry about the stock recovery coming back?
Thanks in advance.
Click to expand...
Click to collapse
good call posting here (question = Q&A) gsm versions don't have it

ogdobber said:
good call posting here (question = Q&A) gsm versions don't have it
Click to expand...
Click to collapse
I have same issue, cannot find recovery-from-boot.p in /system? I need to rename it or delete it because must to flash recovery image at every phone reboot... Or do you have some other solution?

vintermut said:
I have same issue, cannot find recovery-from-boot.p in /system? I need to rename it or delete it because must to flash recovery image at every phone reboot... Or do you have some other solution?
Click to expand...
Click to collapse
flash a custom rom, every custom rom has it removed(or flash a rooted stock/aosp).

Only ota puts the files there; if you flashed a factory image, then the files ain't going to be there. If they aren't there, can't delete them. Why would you want to put them there again? lol
Dump that toolkit and do it proper. Also, search/dig through q&a before posting.
Sent from my i9250

simms22 said:
flash a custom rom, every custom rom has it removed(or flash a rooted stock/aosp).
Click to expand...
Click to collapse
I have custom ROM (Minco v5). If there is no that file why I must flash recovery every time at phone reboot?

vintermut said:
I have custom ROM (Minco v5). If there is no that file why I must flash recovery every time at phone reboot?
Click to expand...
Click to collapse
clockworkmod has a new feature that gives the option to disable "recovery from boot" on the first restart from it.
however, what commands are you using to flash your recovery?
it must be
Code:
fastboot flash recovery name-of-recovery-image.img

ogdobber said:
clockworkmod has a new feature that gives the option to disable "recovery from boot" on the first restart from it.
however, what commands are you using to flash your recovery?
it must be
Code:
fastboot flash recovery name-of-recovery-image.img
Click to expand...
Click to collapse
Yes, that is the command that I use.

Cant enter recovery

my phone will not boot into recovery mode through CWM or by powering off and manually starting it. I get a dead android with a red triangle and ! sign, how can i fix this?
galaxy nexus (verizon)
4.0.2
rooted via Gnex tool kit

That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
If you are rooted, you need to check the CWM thread for the file to delete through root explorer and then re-flash CWM to get it to stick.

Or use rom manager to flash it.

Jubakuba said:
Or use rom manager to flash it.
Click to expand...
Click to collapse
Ah yea, good point.
I prefer the difficult and manual way lol

Or re-flash your recovery from fastboot, then boot into it, and install whatever ROM you wanted.

OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?

bk201doesntexist said:
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
Click to expand...
Click to collapse
I agree. This option will let you boot into cwm once. when you finish there and reboot your nexus will wipe every trace of cwm. When you need it again just use the same trick again.
Sent from my Galaxy Nexus using XDA

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
Before anybody suggests I use search - I DID search, and it brought me to this thread.
Background: After unboxing my shiny new GNex last week, I immediately flashed stock yakju IMM76D using GNex Tookit.
So ... let me make sure I understand this. With stock recovery, when I fire up fastboot and select recovery, it is NORMAL to get the little dead robot with a red triangle above him? And the only way I've found to get out of it is to pull the battery? Seems odd.....
(I did temporarily flash CWM via the Toolkit and it worked fine. I don't want to leave it on as I understand it will prevent me from getting future OTA updates.)

As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
If you get that error, your phone will reboot after a minute or so, but like I said it should be gone after flashing a custom ROM.

Theshawty said:
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
Click to expand...
Click to collapse
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.

Zepius said:
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Click to expand...
Click to collapse
I renamed it, it should be the same as doing away with it. However, upon rebooting, I faced that triangle. I ran stock 4.0.4 by the time.

you still have to reflash CWM after deleting/renaming the file.

Zepius said:
you still have to reflash CWM after deleting/renaming the file.
Click to expand...
Click to collapse
Which I did, but the problem wouldn't wanna go away.

Theshawty said:
Which I did, but the problem wouldn't wanna go away.
Click to expand...
Click to collapse
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.

efrant said:
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
Click to expand...
Click to collapse
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
I haven't read about the install script but ill be sure to follow your guide when and if I ever return to stock. They're awesome.
Sent from my Galaxy Nexus using Tapatalk 2

Theshawty said:
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
Click to expand...
Click to collapse
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?

Theshawty said:
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Click to expand...
Click to collapse
Who knows? I personally don't care, and no one else should either, as:
1) the OTA update file to IMM76D is availability for any yakju user to install,
2) the full IMM76D image is available to install,
3) the IMM76D source has been pushed to AOSP.
Those are three options for you to get IMM76D on your device, with the first one being the same as an OTA update.
For me, IMM76D runs perfectly fine, and better than ICL53F.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
For me, IMM76D runs perfectly fine, and better than ICL53F. 2
Click to expand...
Click to collapse
What radio are you using? The XXLA2?

[Q] CWM recovery disappearing

Hi,
I am using the Gnex root kit on this forum to unlock, root and install CMW.
All is working fine but every once in a while (especially after the two latest upgrade to 4.0.4) CWM disappears from my phone: is this normal?

thegios said:
Hi,
I am using the Gnex root kit on this forum to unlock, root and install CMW.
All is working fine but every once in a while (especially after the two latest upgrade to 4.0.4) CWM disappears from my phone: is this normal?
Click to expand...
Click to collapse
An OTA will flash the stock recovery image back to your phone so you will lose cwm. Just reflash it and everything should be fine. Also you might need to delete the Recovery Restore files if they are present on your system or the Stock Recovery will be reflashed after a reboot.
Mark.

mskip said:
Also you might need to delete the Recovery Restore files if they are present on your system or the Stock Recovery will be reflashed after a reboot.
Mark.
Click to expand...
Click to collapse
ahaaaaa that could be the problem: how to do that?

thegios said:
ahaaaaa that could be the problem: how to do that?
Click to expand...
Click to collapse
You can do it via my ToolKit.
Mark.

mskip said:
You can do it via my ToolKit.
Mark.
Click to expand...
Click to collapse
of course hahaha
Off topic: do u use volume+ on ur gnex or sny othet tool to fix the loe notifications volume?

thegios said:
of course hahaha
Off topic: do u use volume+ on ur gnex or sny othet tool to fix the loe notifications volume?
Click to expand...
Click to collapse
No sorry I have never installed any volume patch as my sounds are plenty loud enough for me.
Mark.

-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.

after renaming my s3 rooted into android mode
juliano_q said:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse
after renaming my s3 rooted into android mode i just renamed the file into /system/recovery-from-boot.p-bak but aftr renaming my s3 rooted into android mode plz help me how i boot my s3 into clockmod recovery mode......

rockondudu said:
after renaming my s3 rooted into android mode i just renamed the file into /system/recovery-from-boot.p-bak but aftr renaming my s3 rooted into android mode plz help me how i boot my s3 into clockmod recovery mode......
Click to expand...
Click to collapse
How about asking in the S3 forums?

Twrp Install

Can someone help me with twrp install? Ive flashed the latest version #7 using odin v 3.07 and it says "Reset" and i have a green block yet when i boot into recovery i still have the stock recovery.I also tried the suggested toolkit, says successful yet no twrp just stock recovery. Can someone tell me what I'm doing wrong? Thanks in advance...JW

pabowhunter59 said:
Can someone help me with twrp install? Ive flashed the latest version #7 using odin v 3.07 and it says "Reset" and i have a green block yet when i boot into recovery i still have the stock recovery.I also tried the suggested toolkit, says successful yet no twrp just stock recovery. Can someone tell me what I'm doing wrong? Thanks in advance...JW
Click to expand...
Click to collapse
Use a root explorer and navigate to /system, there will be some recovery____.sh file and one in /system/etc too. Rename these files. (P.s I don't know exactly what its called)

emwno said:
Use a root explorer and navigate to /system, there will be some recovery____.sh file and one in /system/etc too. Rename these files. (P.s I don't know exactly what its called)
Click to expand...
Click to collapse
I have this same problem and the file you mention doesn't exist in either location. I flashed the new tar you have up today. Recovery fails to load at first and the samsung white load screen flashed a couple time. Eventually the default recovery loads.

recovery-from-boot.p / install-recovery.sh. Search for these in /system. This is all I got, try reading around the toolkit thread, there should be something there

emwno said:
recovery-from-boot.p / install-recovery.sh. Search for these in /system. This is all I got, try reading around the toolkit thread, there should be something there
Click to expand...
Click to collapse
That first one is there yes. I should delete that?

Rename to something else