Hi I am a follower of LeeDroid on Sensation and thus far have always been able to find the answers to my questions without any issues. But now I am starting to dabble with root on Xoom. Needless to say I had a LOT of issues as it's not nearly as straight forward as my Sensation. I resolved most of my issues and am finally ready to install Team Tiamat's rom. Reboot into recovery, choose the zip and it freezes on Unpacking New Files.... I've been at this all night and really would like to go to bed knowing that it's installed and I can mess with it tomorrow. Any ideas?
Thanks so much for the anticipated help!
Like what excatly is happening? You do have the CWM recovery flashed to the recovery partition, right? What have you've done so far? What guide you've followed thus far?
Pretty much rooting the XOOM is pretty straight forward, unlock the bootloader (adb reboot bootloader, fastboot oem unlock, on xoom press volume down then up and repeat once to unlock), boot back into the bootloader and flash the recovery (adb reboot bootloader, fastboot flash recovery recovery_image_name.img, fastboot reboot), then reboot into the recovery and flash either the root files or the ROM you want to use.
^^^
Totally agree. Once custom recovery is installed flashing rom is same as with other devices:
Boot into recovery.
wipe data/reset
install zip
choose zip file
Done
................
Avoid flashing through rom manager.
You need to have custom recovery tailored for Xoom (not what is available through rom manager)
.................
The rooting process is done and I also have already flashed cwm. The problem is when I go into cwm through recovery and attempt to load the tiamat rom it freezes at the step "unpacking new files"....
Sent from my HTC Sensation 4G using Tapatalk
please check the md5 checksum (given from where you downloaded tiamat).
also flashing takes some time.
do not inturrupt.
Yesterday i flashed it and it took some time(even i thought it is doing nothing).
But it flashed ok.
rickm8384 said:
The rooting process is done and I also have already flashed cwm. The problem is when I go into cwm through recovery and attempt to load the tiamat rom it freezes at the step "unpacking new files"....
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
Have you checked your downloaded file. It may be corrupt.
It seems post no#5 & 6 posted at same time
rohit3192 said:
It seems post no#5 & 6 posted at same time
Click to expand...
Click to collapse
Great minds and all that!
Hehe...
BTW I have flashed international stock version over US MZ604.
It has last update of 3.1 with micro sd support.
It gives a choice of what to mount(internal or sd card)
2 extra wallpaper also there.
Let's see how it performs.
Are you using the correct version of the recovery? This seems to be a common mistake made by quite a few people. You need to be using this version and loading the ROMs and kernels to a Microsd card. "Newer" versions do not use the microsd card so you would be flashing from the same internal memory that you are trying to flash over.
HuckFinn said:
Are you using the correct version of the recovery? This seems to be a common mistake made by quite a few people. You need to be using this version and loading the ROMs and kernels to a Microsd card. "Newer" versions do not use the microsd card so you would be flashing from the same internal memory that you are trying to flash over.
Click to expand...
Click to collapse
What he said, read the pre-requisites very carefully on the ROM page. Also what ROM are you trying to download and what version of honeycomb are you currently running? What xoom? Wifi or 3g?
I was finally able to get it done. The issue it turns out was my own impatience coming out. I just had to be patient and eventually it installed.
Thanks for all the help everyone!!!
Sent from my HTC Sensation 4G using Tapatalk
rickm8384 said:
I was finally able to get it done. The issue it turns out was my own impatience coming out. I just had to be patient and eventually it installed.
Thanks for all the help everyone!!!
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
I'm glad it worked. I know what you mean about being impatient...sometimes it seems like nothings happening and in fact, you just need to hang in a little longer.
Related
Well I haven't been on XDA in over sixth months but in my times of trouble I require help. Awhile back I flashed one of the first experimental ICS ROMs to my Xoom, it was non fuctional in many aspect but I liked it and kept it. Now, I'd like to get rid of it but I can't install ADB on my new computer (It's a Java JDK thing that I can't solve for the life of me) I tried flashing a new ROM over it but it fails half way through. So how can I get back to stock without being able to flash or use fastboot? Thanks guys.
P.S. Sorry that my terminology is rusty.
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
I already tried flashing different ROMs but it won't let me, I just get an error after it tries to install, no matter what SD card or ROM I'm using.
I'd recommend flashing this in recovery: http://goo.im/roms/TeamRogue/Xoom/Recovery/rogue_XM-recovery-1.5.0-rc3.zip
It's an updated touch recovery for the xoom, then reboot and go back into recovery and flash a new rom with that recovery, should work but let us know if you have more issues
To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.
What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".
Its not bricked.If u can enter recovery
Sent from my HTC sensation
Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse
DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I hate to post this but after 3 days of trying to get this damned phone serviceable I am seeking higher powers.
I have viewed just about every thread I can, and everytime i think I'm getting close only to be disappointed.
I was attempting to root a Rogers HTC One X for a friend. Ive rooted 3 other devices prior to this one without issue and constantly custom rom my own device (HTC Raider).
As of now, I CAN: Boot to Hboot (1.11.000), Flash Custom Recovery (Have tried TWRP and CWM, can enter successfully cant do much else), flash things via fastboot.
I CANNOT boot to OS. Its apparently gone. so as such, i have no access to the SD-ext. I CAN mount USB in TWRP but while it shows up in windows as a storage device, I CANT see it on the phone, so i cant flash it. I CANNOT mount in CWM.
I have attempted to RUU via fastboot. I have gotten errors for signature, size and model. Even the stock, non-root one (1.94) stated that the size is incorrect. Im also seeing alot of Errors regarding android-info.txt.
I really desperately need to get this running. Which ever rom. i dont care. If i can get stock, fine, if not Custom rom/kernel.
My biggest issue is not having access to the sd-ext and this phone, for some stupid reason, does not have a microSD slot, which would have made this whole issue alot easier.
I dont know if im missing a file or a step. Im really not sure where to go next.
If you have files that will work and can tell me how to do it, I will forever be in your debt.
It seems to me that i SHOULD be able to run fastboot update xxx.zip and just have it fix it but thats when im getting the android-info.txt errors.
If i could manually flash the 3 files through fastboot (system and boot more than recovery), i would think it would work but nooooooo.
Is there any way any of you know how to get me to atleast being able to see my sd-ext on both windows and TWRP so i can flash it that way? ANYTHING?
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Kesler84 said:
So, Got it up and running with Team Nocturnals Rom.
What I had to do was wipe SD and caches in TWRP. Flashed CWM from fastboot. Wiped SD and cache AGAIN. Flashed back to TWRP. Wiped SD and Cache. Rebooted to fastboot. Flashed the boot.IMG. Rebooted to recovery. Mounted USB. Windows detected it. Formatted to fat32. Copied the .zip to SD and installed. Problem solved.
Stock 2.20 Rom that's around didn't work, deodexed rooted stock didnts, nor did Android Revolution HD.
I still thank all of you, because even though I got this working myself, it was bits and pieces of every other thread that got me to that point. Thank you all.
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Ummmm android revolution is for the international one x.... Maybe that's how u f'd it up in the first place? Idk just be careful the threads are kinda similar ...
No, I didn't even touch Revolution until it was already not working. I was originally just rooting the stock. It wasn't until it softbricked that I attempted any customs.
Sent from my HTC Velocity 4G X710s using xda app-developers app
I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.
Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard
Juts mount your sd in recovery and drag a Rom over from your computer
J3susisl0rd7 said:
Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard
Click to expand...
Click to collapse
Sounds like the initial problem was just a bad flash/download. It happens.
Try unplugging your phone, shutting down and restarting into bootloader, then hooking it up.
You flashed an incompatible kernel it sounds like.
Make sure you try flashing the kernel within the ROM
Sent from my One X using Tapatalk 2
Hello everyone! Thanks for the replies. Sorry for the rushed post earlier, was on the way out the door after trying for a while to figure something out. I'd love to send a rom to it, but TWRP shows that I have 0 mb available of storage, and the computer says I must format it to access files or something. I may have forgotten to mention- I think i flashed rohan kernel b6 improperly... used flash image gui then went to recovery and clicked it and hit install ... it hung at installing for a while, and upon reboot the starting apps problem happened, followed by no rom being on there, only being able to access TWRP, and ... well, above things. If I formatted it would I be able to put twrp and everything back on it necessary to make the thing function properly? Orr.... Thanks for any help!
God bless!
P.S. Forgot to add- Not sure why I thought I needed to try to "install" rohan kernel later on in TWRP lol
P.S.S I tried to mount sd card in twrp, nomatter how many times i try to select it it wont work
Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium
thejosh86 said:
Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm sorry- I really don't understand what I'm going to lose if I format, like... apparently all my data is somewhere in the air now lol, but will I not lose any important things the phone needs to run? TWRP? Will the bootloader still be unlocked?
And, if above "issues" aren't "issues", then will the following steps be correct?
1. Send ROM to phone
2. Throw fastboot.exe and adb thing into a folder with the ROM/ boot.img
3. CMD prompt to flash
4. Magic
?
Thanks so much and sorry to be a pain here if this isn't that big of an issue! I was afraid I bricked the thing, but I was holding on to hope that I didn't since it seemed like a good thing that it would still boot to TWRP.
Also- not sure if this is an issue, I tried to hit adb sideload in TWRP just messing around with options, and it said it couldn't mount the SD card.... so.... yeah, is that an issue?
Whatever data you had on the sd card is gone anyway. You need to reformat to use it.
Formatting the sd card won't affect your /system files or recovery, which are stored on a different area, or cause you to lose root.
You guys are awesome. Thanks so much!
And, as you get a lot: Sorry... for being a noob. lol