stuck on rootboot.img? Read here 1st

sicario666

Well-known member
Dec 27, 2009
2,931
366
83
im trying to root my xoom. im stuck at the rootboot.img file, when i need to access it via adb. can any1 help me out. i tried extracting the files with winzip...this is the error i get
rootboot.png


any help is appreciated. for some reason my comp isnt seeing this as an img file. i dunno. running windows7 64bit
 
Last edited:
Got me on this one. I'm still on 3.1 and I'm asked all day to update but need to go stock first. Might do it this weekend and them ill be able to help. Hopefully someone will jump in.

sent by CyanogenMod X
 
  • Like
Reactions: sicario666
Re: stuck on rootboot.img via adb

Got me on this one. I'm still on 3.1 and I'm asked all day to update but need to go stock first. Might do it this weekend and them ill be able to help. Hopefully someone will jump in.

sent by CyanogenMod X

OK. Thanks tnt. My xoom still works. Its unlocked just waiting to push su and flash a rom/OC. I wasn't able to get an answer on xda either...
 
Re: stuck on rootboot.img via adb

i figured i would try and delete WinZip. since it was the program that was reading the IMG files as zip files. If anyone else runs into the same problem that i did, just delete Winzip and the img files will show up as img files and not zip files. Winzip is free to install so you can just grab it at a later time.

On to the rooting...:cool::)

Oh btw...if this helps. Please tap the good ol thanks.
 
Last edited:
  • Like
Reactions: tntdroid
I may update to 3.2 tonight and wipe. Should be fun. Glad your on the right track now.

sent by CyanogenMod X
 
I may update to 3.2 tonight and wipe. Should be fun. Glad your on the right track now.

sent by CyanogenMod X

Ha ha. Thanks again TNT. It was one of those wake up in the middle of the night things. If you've got winzip this should help bypass a few mins of irritation :D
 
I broke my Xoom twice last night and ended up getting it working on 3.0.1 lol. I factory reset and locked the bootloader then tried to take the ota to 3.2 and it bricked? ??? Guess I fix it later. Owell.

sent by CyanogenMod X
 
I broke my Xoom twice last night and ended up getting it working on 3.0.1 lol. I factory reset and locked the bootloader then tried to take the ota to 3.2 and it bricked? ??? Guess I fix it later. Owell.

sent by CyanogenMod X

That's odd...hmmmm. did you unroot and lock the xoom before accepting the ota? Maybe that was the problem?
 
Even more odd??? I did the OTA while back on 3.0.1 and when it booted I was on 3.1 then got another notice for the 3.2. Looks like everything should be good. Once it loads ill just unlock root and get me some tiamat
 
Even more odd??? I did the OTA while back on 3.0.1 and when it booted I was on 3.1 then got another notice for the 3.2. Looks like everything should be good. Once it loads ill just unlock root and get me some tiamat

Awesome. Git er done. I'm drawing a blank when it comes to why you're having these issues.
Its good to hear you're on the road to root and tiamat! There's a cool theme on xda too. Stargate is what its called. Let me get you the link

http://forum.xda-developers.com/showthread.php?t=1261616
There ya go,bud
 
Have you gotten the system update notification since being on 3.2? I've seen it a few times but don't want to except it.
 
Re: stuck on rootboot.img

I following the procedure for my ZOOM WIFI MZ604. When executed rootboot, the device is struck on logo forever. I somehow got clockworkmod recvoery. How how do i recover or install the image?
 
Here is the final story:
The rootboot.img downloaded from rootboot.img was stuck and there was no way out.

I tried hard reset option cited from [Q] How to hard reset xoom wifi - xda-developers didn't work.

Finally, i copied Zip file from update_US-Xoom-WiFi-4.0.4-IMM76_stachre_v01.zip for IMM76 to SD card. Then, using clockwork mod from [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6] - xda-developers , I installed ICS 4.0.4

God! I was able to recover my Xoom wifi!!!!! Though it is thrilling, we are far far away from Windows what it is today [sign].
 
I am now stuck updating 4.0.4 to 4.1.2 The update will show up with ! in triangle of android icon after boot. I have no idea how to move forward. The update alert is very frequent that I am not able to focus on my actual apps. I would appreciate if someone could recommend a solution for 4.1.2 update.

Thanks,
Pingala
 

Forum statistics

Threads
954,669
Messages
6,962,397
Members
3,163,102
Latest member
ashy