Database Info

How to Root Your New Official Cupcake 1.5 OTA Update or Regain Root lost by update

OTA update to cupcake make you lose root? Have a fastboot enabled SPL?
These instructions are for those who have a Bootloader with fastboot enabled. (Hard SPL, Engineering SPL, etc.)
Again these instructions are for those who have a bootloader with fastboot enabled.
THIS WILL WORK ON ALL FIRMWARE VERSIONS WITHOUT HAVING TO REFLASH!
As long as you have fastboot enabled in your SPL you can root any of the OTA update without having to reflash your firmware or downgrade.
1) Download JF Recovery V 1.43
2) Extract recovery.img from the data directory
3) Boot phone into bootloader (power off then power+camera buttons)
4) use fastboot to boot into recovery firmware (this will NOT flash just boot)
# fastboot boot recovery.img
5)wait for firmware to boot and hit Alt+x
6)press enter when it tells you
7)type on your phone
# mount system
8)wait for a new prompt #
9)type on your phone
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
10) Your phone is now rooted

semyazza said:
OTA update to cupcake make you lose root? Have a fastboot enabled SPL?
These instructions are for those who have a Bootloader with fastboot enabled. (Hard SPL, Engineering SPL, etc.)
Again these instructions are for those who have a bootloader with fastboot enabled.
THIS WILL WORK ON ALL FIRMWARE VERSIONS WITHOUT HAVING TO REFLASH!
As long as you have fastboot enabled in your SPL you can root any of the OTA update without having to reflash your firmware or downgrade.
1) Download JF Recovery V 1.43
2) Extract recovery.img from the data directory
3) Boot phone into bootloader (power off then power+camera buttons)
4) use fastboot to boot into recovery firmware (this will NOT flash just boot)
# fastboot boot recovery.img
5)wait for firmware to boot and hit Alt+x
6)press enter when it tells you
7)type on your phone
# mount system
8)wait for a new prompt #
9)type on your phone
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
10) Your phone is now rooted
Click to expand...
Click to collapse
How can this be done through adb ? if you can't load-flash hard-spl or the engineered one ? It states E:No signature

Please read the directions
You must have the Hard SPL,Engineering SPL or a Fastboot enabled SPL for this to work. Try the file I have linked to at the bottom of this post. It is a production signed SPL and has the proper non-test keys so should be able to flash as stock firmware. This SPL is also fastboot enabled.
http://www.filedropper.com/hboot-09500007d2fc780
If it still gives you a key error my method will not work for you (because the first direction I posted is you MUST have an fastboot enabled SPL).
http://www.filedropper.com/hboot-09500007d2fc780

semyazza said:
You must have the Hard SPL,Engineering SPL or a Fastboot enabled SPL for this to work. Try the file I have linked to at the bottom of this post. It is a production signed SPL and has the proper non-test keys so should be able to flash as stock firmware. This SPL is also fastboot enabled.
http://www.filedropper.com/hboot-09500007d2fc780
If it still gives you a key error my method will not work for you (because the first direction I posted is you MUST have an fastboot enabled SPL).
http://www.filedropper.com/hboot-09500007d2fc780
Click to expand...
Click to collapse
Thanks for the link. Still can't flash.

can anyone confirm this works?

Worked for me
This procedure worked for me. I took the JF 1.43 recovery image from http://code.google.com/p/android-roms/

Worked perfect running gfh_eu CRB43 all OTA updated

I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?

I believe the official ADP images do not come by default with root enabled any more. I could be wrong though.

Datruesurfer said:
I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?
Click to expand...
Click to collapse
Yes, I followed the instructions to update to Haykuro 6.0.
Flashed radio first,then spl, then firmware.
I now have no root and can only downgrade to rc29 through recovery and flash dream. I cannot flash anything ! Cannot flash the recovery.test keys. Am stuck on the ota cupcake( the only file I can flash).
Any suggestions. I downgraded and rooted several times. Still cannot flash anything.

Datruesurfer said:
I don't understand the point of this... As long as your running the official ADP image or a JF ROM you shouldn't have lost root in the first place. Since the OTA update doesn't include a new SPL you can still downgrade to RC29 and use the root bug to update to 1.5.
Am I missing something?
Click to expand...
Click to collapse
Why would you want to have to reflash your phone twice? Your chips CAN wear out from repeated unnecessary flashing. You will also have to install a modified build then (see below).
techvd said:
I believe the official ADP images do not come by default with root enabled any more. I could be wrong though.
Click to expand...
Click to collapse
Techvd is correct. The new google production ADP images do not allow you to SU to a root prompt. ADB still works but it is kind of pointless without root access. I prefer the least modified firmware possible as it is much more stable than the custom roms (although that is getting less and less true).

I had just updated to the newest hero rom and for some reason i lost root. I followed your step except for the recovery image part because i already had it on my phone, thanks for the instructions!!!

why it doesn't works for me? I have the SPV thing, and the haykuro SPL. when I press camera and power, after a very fast sliding of messages telling me that a don't have this this and this (but in my sd, on root, there are the dreaming.* and the recovery.img from JF 1.43 files), I got a screen telling
Dream PVT 32B ENG S-off
HBOOT-1.33.2005 (DREA1100)
CPLD-4
RADIO 2.22.19.26I
Apr 20 2009, 15.30:43
HBOOT
<BACK> FastBoot Mode
by pressing <Back>
I obtain the following screen:
FASTBOOT (evidenced in red)
<Camera step2> hboot mode
<Send> reset device
<Action> Restart to HBOOT
<Menu> Power down
So how to enter if fast boot mode? I'm really missed up! any help?

iso67 said:
I obtain the following screen:
FASTBOOT (evidenced in red)
<Camera step2> hboot mode
<Send> reset device
<Action> Restart to HBOOT
<Menu> Power down
So how to enter if fast boot mode? I'm really missed up! any help?
Click to expand...
Click to collapse
You are already in fastboot mode. You need to flash the recovery image to the phone now. Open a terminal window and use the command:
Code:
fastboot flash recovery [i]/path/to/JF_recovery.img[/i]
Then, press MENU on the phone, and it will reboot. Reboot the phone into recovery mode (HOME+POWER), Alt+X at the log screen, and then enter those commands.

Why fastboot? Use ADB
I don't understand why there's the need to change the recovery image or use fastboot at all. You can do this from ADB.
Code:
$ adb remount
$ adb shell
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
($ and # are terminal prompts, not to be entered on the command line)

rpcameron said:
You are already in fastboot mode. You need to flash the recovery image to the phone now. Open a terminal window and use the command:
Code:
fastboot flash recovery [i]/path/to/JF_recovery.img[/i]
Click to expand...
Click to collapse
but how to enter this command from this screen? I don't know how to open a terminal windows from here (I know how to open it from the telefon properly powered on)
Then, press MENU on the phone, and it will reboot. Reboot the phone into recovery mode (HOME+POWER), Alt+X at the log screen, and then enter those commands.[/QUOTE]
whenb to run those commands?

Has anoyne else tried running the recovery.img (JF 1.43) from the fastboot on the new Rogers Dream phones?
Mine just displays the Rogers text and logo, but never boots into the recovery mode.

I got it!
I didn't perfom the the recovery.img part, since I already have the JF 1.43, and since I didn't understand the process!
I didn't just the second part and it worked!
thanks

rpcameron said:
I don't understand why there's the need to change the recovery image or use fastboot at all. You can do this from ADB.
Code:
$ adb remount
$ adb shell
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
($ and # are terminal prompts, not to be entered on the command line)
Click to expand...
Click to collapse
And what do you do when you are running a Google/T-mobile production ROM instead of a user debug? I CAN guarantee you that will not work. Also, you are not changing the recovery image on the phone (as stated in the directions). You are simply booting from the modified recovery image on your computer.

outsider787 said:
Has anoyne else tried running the recovery.img (JF 1.43) from the fastboot on the new Rogers Dream phones?
Mine just displays the Rogers text and logo, but never boots into the recovery mode.
Click to expand...
Click to collapse
There seems to be an incompatibility with the Rogers Phone and the Recovery images that we currently have. If anyone has a NAND dump of the *stock* boot, recovery, and System images for the rogers Phone I'll give it a go and try to get a modified recovery working.

[Q] I think I bricked the xoom after 4g upgrade??

- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John

jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...

^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!

jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:

Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.

So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g

jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.

okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John

I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)

^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!

LOL! Safe flight.

Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!

Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium

okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?

okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!

Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!

Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium

hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?

^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.

Can someone lead me to the patience pool; I need a drink.

[Q] Adb commands

For someone who is more familiar then me with ADB...i have a a few requests.
1. What is the command to maybe to a factory reset from fastboot
2. Wipe Sdcard from fastboot
3. Automatically install PG59IMG.ZIP if present from Fastboot
Thanks in advance
-Wildchild

xmc wildchild22 said:
For someone who is more familiar then me with ADB...i have a a few requests.
1. What is the command to maybe to a factory reset from fastboot
2. Wipe Sdcard from fastboot
3. Automatically install PG59IMG.ZIP if present from Fastboot
Thanks in advance
-Wildchild
Click to expand...
Click to collapse
Those commands don't exist to my knowledge. If you want all of that done, I suggest you use the bootloader itself.

aww maan lol I was hoping to put Blue's unroot guide in Mr Root (automated) but I was hoping you could like to fastboot wipe system or some thing.....

xmc wildchild22 said:
aww maan lol I was hoping to put Blue's unroot guide in Mr Root (automated) but I was hoping you could like to fastboot wipe system or some thing.....
Click to expand...
Click to collapse
I believe there is a wipe command when in fastboot.
Sent from my RubiX ICS Infused using xda premium

PG59IMG.zip will load before you can get to fastboot - as soon as hboot loads up it checks for this file, and if present loads that first.
Maybe a better tactic would be to take the PG59IMG.zip apart, strip the signatures from the various .img files inside it, and then use "fastboot flash" commands to flash the images one at a time from it?
Also look into "fastboot flashall" to see how it's implemented and what source files it uses.
I was able to use dsixda's kitchen to strip the signature from the boot.img when I made the insecure boot image for the 1.55.531.3 people - so maybe look into that for whatever ones you can get away with it on to save you from using a hex editor to strip the signatures out.
Also - starting with the new PG59IMG.zip and anyone who's applied the OTA update - the new partitions that are flashed end up making it so that the kernel is taken out of the boot.img and flashed separately as ramdisk.img - something to keep in mind.
When you are all done you could send the fastboot oem reset command to reboot, or fastboot oem powerdown to shut the device off.
Have you looked into generic (non-oem) fastboot commands like "fastboot erase (partition name)" ?
A factory reset is the equivalent of wiping cache and data. If they are empty when the phone turns on it rebuilds them from what is in the /system partition. I have a flashable script found in this post which does that when flashed from clockworkmod.
I made it back when our most up-to-date cwm was paul's 4.0.0.9 - neither 4.0.0.8 or 4.0.0.9 supported the format commands correctly, so it does wipe instead of format - but it's basically the same thing, and for your purpose here wipe/delete or format will fork interchangeably.
I'm pretty tired, so hope this is enough to get you started with, i'll post more another day when i'm not half asleep.

rajzzz said:
I believe there is a wipe command when in fastboot.
Sent from my RubiX ICS Infused using xda premium
Click to expand...
Click to collapse
I know you can do it with a task command, not sure which one
fastboot task (number)
it's a dangerous thing to randomly try, since you can do a lot of damage trying random task numbers not knowing what they do.
task and radio task (rtask) are my current subject of study, since i'll have to learn more about how to use a radio shell to progress in the s-off quest, but i'm getting ready for work and don't have time or the headspace to get into it more now.
XMC - check into fastboot task commands to see if you can dig up the numbers for format and it should be what you are looking for, should've posted that last night too when I got in but was tired then and wasn't thinking clearly.

First time rooting, few questions.

ACTUALLY I GOT THE ANSWER TO THESE QUESTIONS (ignore this thread)
I've been reading through this guide: http://forum.xda-developers.com/showthread.php?t=1249798
Question 1: When they say wipe everything, do they mean media too? (like music and such) Because when I had a samsung vibrant, they also said that but it never wiped media.
Question 2: Will I have to run a nandroid backup if this is my first time rooting, or will it be unnecessary?
Question 3: After finishing doing everything (unlocking and rooting)
do I just directly flash this http://forum.xda-developers.com/showthread.php?t=1484770 or is there something I need to do beforehand?
Also, in the guide, it says something about green android of ! if you have received an OTA. Which I have received many from Moto before. Will I have to download the original motorola files (HC or ICS, I'm currently on ICS)? If so, where do I put it? I'm confused
okantomi said:
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
Thanks so much! I'm new to this, it's so much different from rooting my Samsung Vibrant phone

cmd hangs
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.

rosystreasures said:
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
Click to expand...
Click to collapse
There may be something wrong with my instructions...they've gotten convoluted over time. Try one of the other guides in General..there are a couple of newer ones that might work better. Mine still gives a lot of information but I think I'll retire it 'cause I don't want to cause issues.

I recently rooted and flashed a rom on my xoom. I'm a simple point and click windows user and I didn't have much trouble, so it's not that hard to do.
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
http://forum.xda-developers.com/showthread.php?t=1477024
is the thread I used. Follow the instructions exactly and read the entire thread before you start, it'll save you a few headaches. This'll get you in (I think) ICS with superuser and all that jazz. If you want a rom, like me, then you'll have to head over to the development forum and take your pick. I'm running EOS 2.0, still deciding what to do with my xoom atm.

I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.

rosystreasures said:
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
Click to expand...
Click to collapse
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.

Quickboot vs. ROM manager
okantomi said:
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Click to expand...
Click to collapse
I started out with the standard 3.2 on my Xoom Wifi
with a nagging system message to update (I am guessing 3.2.2)
So I followed thread 1249798 and now am unlocke & rooted!
I am also using Recovery: Eos Recovery R6
I still get the nagging system message to update.
I would like to load a custom ROM, probably Moray.
My questions are this:
1. Will the Nagging system update message cause a
problem loading a custom ROM?
2. I could use the process as described in thread 1249798
to load the ROM, but I have read that since I am rooted
I could use Quick Boot app. Is this true? What about the
ROM Manager app, could I use this to load Moray? What is
the difference?
3. Since my base is 3.2 I am guessing I cannot load any
EOS ICS Rom's, is this correct? I need to bring my base
to 4.0 right?
4. Both Hammerhead and Moray state that they are both:
"Pre rooted with su and Superuser". Does this mean I did
not have to root my Xoom, I could have just loaded either
of these Roms and become rooted?
5. I have read some comments about:
/system/etc/install-recovery.sh
If I remove this file, will this stop the nagging System Update message?
6. Do I need to back anything up prior to loading a ROM?
Thanks!

Still with that, you can flash TEAM EOS ROM ICS. just boot into recovery and flash the TEAM EOS ROM. Mine was 3.2.1 as well. GOOD LUCK

[Q] Can't open /cache/recovery/command EVO 3D

I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!

twingle said:
I get this problem in y htc evo 3d when i open recovery it shows yellow exclamation mark i proceed with pressing volume up+power buttons. Then in bottom of the commands it says Can't open /cache/recovery/command. After i press begin update from external storage it says invalid operation. Success rebooting by reason oem_00. Help me please I tried to install other rom. It is unlocked S-ON non-rooted hboot 1.53.007 latest android 4.0.3
Help please! Need to install Custom ROM!
Click to expand...
Click to collapse
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!

thebeastglasser said:
In other words, you haven't installed a custom Recovery yet. Don't worry, at least you haven't bricked it like I did with my Old Epic 4G.
Here's what you have to do.
Download SDK-Tools. http://goo.gl/zmFNr
Move it to your C:\ directory (assuming that's you're on Windows otherwise I can't help), afterwards... unzip there.
Then, download TWRP, (this is from my own personal stash please don't go around distributing it) http://goo.gl/oeA2b
And take the "recovery.img" and put in your now unzipped SDK-Tools folder.
From here on out you're going to be using the command prompt to control your phone. Pray that you have Android Debugging checked on your phone, otherwise this probably won't work.
Go to the Windows flag on the bottom left corner, and type in "cmd" and hit enter.
Command prompt open. Time to get into SDK-Tools. From here on out I'll be using code to explain, it there's an extra space between a line, that means you have to hit enter.
Code:
cd c:\sdk-tools
adb reboot bootloader
fastboot flash recovery recovery.img
And there you have it, you've now flashed your recovery. You now have two options, you can reboot into the System (GUI, ROM, whatever you want to call it.)
Code:
fastboot reboot
(if that doesn't work, try "adb reboot" but I believe the first is correct)
Or you can now go to the recovery...
Code:
fastboot boot recovery recovery.img
That's it! Enjoy!
And when you eventually get the courage to obtain S-Off, check my signature. Make sure to thank Globatron when you're done!
Click to expand...
Click to collapse
Thank you very much for your tutorial, everything was very clear and I made everything easily. Now there's another, even funnier problem. When I am trying to access Recovery, it just reboots my phone? How can be this?

twingle said:
When I am trying to access Recovery, it just reboots my phone...
Click to expand...
Click to collapse
My only guess would be the recovery I sent you. It's for the Evo V 4G... which is essentially the same phone (same hardware, different software).
Try this one. http://goo.gl/PyVdR
It's TWRP 1.1.1 for the 3D, the official one. Let's see how this works... :fingers-crossed:
EDIT: Or, while you're in fastboot and bootloader is highlighted... http://goo.gl/SEh0o
Press the power button, then hit the volume rockers until Recovery is highlighted. Press the power button and that could work as well.

No, this also doesnt load. I think something can be wrong with cmd. Theres an error.
Code:
C:\Users\aser>cd c:\Android
c:\Android>adb reboot bootloader
error: device not found
c:\Android>adb reboot bootloader
error: device not found
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)...
OKAY [ 1.328s]
writing 'recovery'...
OKAY [ 8.887s]
finished. total time: 10.223s
c:\Android>fastboot boot recovery recovery.img
cannot load 'recovery'
c:\Android>
Everything what I do: I connect my phone, open fastboot(in bootloader) than in pc open cmd type everything what I should, when it is installed I reboot bootloader than open recovery... And BAM! HTC is loading to boot my phone, gets black screen (turns off) after a sec turns on . Also after it I tried doing Bootloader Reboot mannualy, I pressed to reboot the bootloader. The same happened.Thats all

Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?

thebeastglasser said:
Do you have USB debugging enabled?
For the record, the same thing happens with my device, but I have S-Off. There's nothing wrong with command, I can tell you that. But if you can flash the recovery, clearly something's going right.
What I'd recommend from this point, is rooting your phone and getting something that can put you into recovery. Be it ROM Manager, Goomanager or Quickboot, clearly it doesn't want to manually work.
Before I get into that though... you do have HTC Sync installed... correct?
Click to expand...
Click to collapse
Sure, USB debugging is always enabled! Yes i have installed htc sync. You think i need to delete it?

twingle said:
You think i need to delete it?
Click to expand...
Click to collapse
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.

thebeastglasser said:
No, you certainly need it for this.
Clearly the conventional tactics are not going to work. I'm afraid you're going to have to go all out. This will be easily achieved if your computer can boot from a Live CD. (and when I say easily, I mean more easily than UnknownForce's method)
Go for this, it's the last piece of help I can get you. It'll also save you a lot of work in the long run.
http://forum.xda-developers.com/showthread.php?t=1563342
There you go. Go for it. :highfive:
KEEP IN MIND THIS ONLY WORKS IF YOU HAVE AN EVO 3D NOT AN EVO V 4G, AND MUST BE CDMA.
Click to expand...
Click to collapse
Thanks for your help. Mine phone is GSM, so this won't go. I realy want to install custom rom, but I am doing that too much (about 8hours of trying) and I didn't do it just only unlocked from htcdev.com
That is awkward, that only you try to help me, theres so many people in xda (45000) online. I unlocked my evo 3d, people say that it is enough to install other rom. I don't want to do the S-OFF because I think it will be the same and we need to find solution now. Its because I won't do the S-OFF, because to make it unlocked was hard, and to make S-OFF is 10x harder! I know that you know more than me, please help me!

To be perfectly honest, I have the CDMA version, so I don't necessarily know anything more than you... nonetheless, I'll do what I can. It seems with the GSM version, you may need to flash the whole .zip versus just the recovery.
Skip to 10:17.
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-htc-evo-3d-gsm/
Also, before I continue, you're on HBOOT 1.5.X... so we're working with a totally different creature right now. I could be wrong, as I've heard the HBOOT 1.4.X. for the GSM can flash just about anything using 4ext (an app) or by flashing the kernel in fastboot. But I don't know how that applies to HBOOT 1.5.X.
If that's true, you may want to get S-Off so you can flash an older bootloader, otherwise I don't know whether or not you can flash custom ROMs.
And for the record, I know what it feels like. I've had a bunch of questions in the past and gotten 1 or no people responding. If you can't get the answer here, keep in mind there are more forums than just this. Something I did not initially know.
For example... androidcentral.com androidforums.com (aka phandroid.com ) and more...
Try posting there too if this doesn't work. That way you'll get the maximum amount of help. Good luck...

By the way, for the record, if you'd like to get S-Off, you can through this... afterwards everything's going to be easier. I know you'd rather not, but nonetheless I'd recommend it. To be honest I thought the same thing before I did it...
http://unlimited.io/jb_shooteru.htm
Either way, good luck in your endeavors.

You know what? It worked! I did it yesterday. I thought it will not work, that I will be with stock rom forever . I followed a bit of that video and the only things that I needed were to unlock bootloader from htcdev.com, download 4ext recovery updater from 4ext.com and downloaded latest final version of 4ext. Than download 4ext recovery.img put in computer and do the work with cmd (fastboot) which was explained before. And install the rom . And also the problem was that I needed to flash custom recovery (4ext). I gave thanks to every post you posted. Thanks a lot to you for your big help :highfive:

Hey, no problem come back any time. Happy flashing.