please help! 3.2 update problem - Xoom Q&A, Help & Troubleshooting

i updated and now it wont fully boot up. i get to the screen where the honeycomb is going up and down and it just stays there. im having trouble getting it into recovery from adb so if anyone knows what to do please save me.

How long are you waiting because the first time mine booted in 3.2 it took about 10 mins.

Long enough for the xoom to die. I just want to be able to boot into recovery but when I try to from fastboot it doesn't do anything. I hope it's not bricked and there's something that can be done.
Sent from my ThunderBolt using XDA Premium App

Do you have CWM installed? If so, boot the Xoom and at the Moto logo wait about 2-3 secs then press the Vol Down button. This will give you the option for recovery, press Vol Up to get in.

i do have it installed but it wont let me get into it through fastboot or those instructions.
do you think this is bricked?

Hmm. I'd keep resetting it (hold power and Vol Up) and trying to get into CWM. I can't see why this wouldn't work. To reiterate, you want to press vol down after about 2 secs of the Moto dual core image.

awesome, i didnt realize i had to press it down. i kept holding it and getting into fastboot. thanks for the help guys!

Glad to help

Related

Can't get my G1 into recovery mode.

Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Dharkaron said:
Just to make sure, with the phone off you press and hold the home button and then press and hold (while still holding the home button) the power button. It should take ~20 seconds for the recovery mode screen to come up.
Click to expand...
Click to collapse
i tried and did not work
natienn said:
Hi to all,
I been trying to upgrade to JF 1.14 rc33 and haven't been able to get to the recovery mode to process the update.zip file. Im not a noob but also not and expert i rooted my my phone so i know basics. When i try to hold the home butoon and power button the g1 logo keeps reappearing for as long as i hold it from 10 seconds to 2 minutes. any ideas of what im doing wrong, i dont care if i have to wipe i just want rc33. Thanks.
I currently have Fimware 1.0
Build #:1.0 TC-4 RC30
Custom Theme: Windows beta 7
Click to expand...
Click to collapse
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
andonnguyen said:
Flash back to the original G1 theme, then try the update. Your theme may be preventing you from upgrading.
Click to expand...
Click to collapse
how do you flash to the original theme? do you know of any links? thanks
Start holding the Home button before you press the Power button.
jashsu said:
Start holding the Home button before you press the Power button.
Click to expand...
Click to collapse
i tried that in different time lentghs from 10 seconds holdin both to 2 minutes, of course pressing the home key 1 sec before the power and holding both
Same problem
Need to bump this thread as I'm having the same issue. Have a HTC Dream with CyanogenMod-5.0.7-DS, trying to go to 5.0.8, but cannot get into Recovery Mode.
Yes, I am completely powering the phone off, holding Home just prior to pressing & holding Power. I keep both depressed for a few minutes and no joy, just sits at the G1 splash screen. I can remove the battery and press Power to bring the phone up normally. Have even dropped to the console, switched to root and issued "reboot recovery". The phone restarts and sits at the G1 splash screen as well.
Can anyone offer advice on how to restore my Recovery Mode? Many thanks...
You can try to reflash (or flash another) recovery with adb, fastboot or in terminal. Btw this thread is in wrong section. It should be in Q & A section.
You could even flash a recovery image from within your rom...you said you could boot the phone normally correct?
So drop into terminal and flash it if you don't want to mess with adb.
The Amon Ra 1.7 Recovery thread has the commands you need to flash through terminal...
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
yutsoku said:
These people apparently are no help. If you hold down the home key and it stays at the G1, try fastboot by holding down the camera button on the side while you power it on. You only need to hold the home key until it vibrates. It should instantly boot into fast boot, if you're holding down camera when powering on.
... if you can get into fastboot, you might need to unroot your phone and reroot it.
... if you can't get into fastboot or recovery mode, then you probably bricked your G1 and you'll need a jtag or scrap it. Or if it's under insurance, tell them you updated and your phone is stuck on the G1 screen....
You could also try taking out your battery then powering it on into fastboot/recovery but odds are that wont help at all.
Hope this was some help.
Click to expand...
Click to collapse
Why would you need to reroot it, just flash a new recovery through fastboot.
fastboot flash recovery <name>.img
misread, yeah he could do that too but it would be easier to reroot if he knows how to do that... instead of learning a whole new method.
You're right though, that would be better.
Update
I am able to fastboot by holding the camera button in and powering on. It sounds like I just need to do the Amon Ra Recovery procedure in order to restore my recovery partition. I assume that I'll need to re-root, but I'm sure there are instructions there for that as well.
Thanks for all the quick replies!
So here's what I found....
I had the exact same problem, but first a little history then how I fixed it.
I purchased an 8GB MicroSD card so I could use Apps2SD and was quite pleased with the ability to do so. Until my battery life dropped to 5mins. It was already down from when I bought it last year.
The battery was severely screwed on my. If I used ANYTHING for more than 5 mins, it would die and would NOT boot up. Oh I could pres the power button and it would try to boot but then die somewhere in the boot process. That is until I plugged it into some charger (car or wall) and then it would boot, showing anywhere from 70 to 90% battery life.
After much research I found that it was the battery and so ordered a replacement off eBay from Hong Kong. $3.96 shipped to my door. Works great, and I am incredibly thankful for that.
So just prior to getting the battery I had done an upgrade to 5.0.8 with the vain hopes that it might help limp along but to no avail. The battery was gone.
Ok, so in comes the new battery. Great! I'll just reflash the ROM to make sure there are no lingering issues and we'll be good to go! Little did I realize that I did an 'upgrade' from CM Updater and when I booted into Recovery I flashed th zip file that was there....which was 5.0.7. DOH! No biggie, everything was working so I didn't worry too much.
Then I installed Clockwork's ROM Manager 1.8.x. A few days later there was an update, so I updated to 2.0.1.3. So I updated that. It went fine.
Few days later, and a few more apps re-installed, the system was running slow.
Apps2SD was greyed out. Huh?
Checked the card....Ubuntu was only mounting it Read Only. And the old swap partition, which I thought I had deleted, was still there. Dammt. But this s a side story I think.
So I wanted to reflash but there was no way I could do it because I could not get into Recovery mode. Ugh.
ROM manager had an update to 2.0.1.4. Ok, maybe that'll work. Nope. It said it updated fine but stuck at G1 logo like many others.
Doing some googling around I saw that it was a ROM Manager issue and that you should flash back down to 1.4.x. Well, since I knew it was working at 1.8.x I decided to reflash to 2.0.0.3. I could get into recovery mode now!
While this kinda solves one issue....I'll have to go into another thread to figure out the Read Only problem so I can re-partition my card again.
Thread closed. Please post questions in the Questions and Answers forums and not in the development forum.

How to shut down a (semi)bricked Xoom

I have had a hard day trying to recover my Xoom. No success. My biggest problem for now is:
How do I shut it down. The screen is on showing the M bootlogo. The powerbutton doesn't do it. From what I understand so are the tablet "off" because the charging light goes on when I connect the charger. I read in a thread somewhere that the light doesn't go on if the tablet is on.
So how do I shut down a tablet that's not on?
I'm afraid that the screen will be damaged if it has the same picture on it untill the battery is drained. Perhaps that's not the case nowadays, but I don't know.
Anyone that do know?
Have u tried just hold power volume up?
Sent from my PC36100 using XDA App
Yes. That only reboots to logoscreen and Starting RSDmode 3.
jai134 said:
Yes. That only reboots to logoscreen and Starting RSDmode 3.
Click to expand...
Click to collapse
Can't just shut it down. Gotta boot into fastboot and flash a boot.img, then power it off. Obnoxious I know.
Sent from my Xoom using XDA Premium App
Hold volume up and power at the same time. See if that works!
Oops just saw the 2nd post.
Yup, follow post #2 to shut it down. But make sure you let go of both buttons as soon as the screen turns off. Also, if you wanna unbrick your semi bricked xoom, use a windows XP machine (win 7 64bit just gives me too many problems). You can use the one click root solution to make it easier for you. To get it to fastboot mode (to restore the boot.I mg and system.I mg files), you have to hold power+volume up button, and as soon as the screen turns on, let go of both buttons and press volume down immediately.
Sent from my Xoom using XDA Premium App
u may need to download your devices partition images and reflash them in fastboot
Thank you. I'm sorry but that didn't help. I can't boot into fastboot mode. When I follow your advice I boot into the logo screen without any text in the upper left corner. Then I give the "fastboot flash boot boot.img"-command from CMD. It just sits there <waiting for device>. I think I have to send it back to Best Buy and let them repair it. It was nice for 5 hours though. My personal best in bricking.
I got stuck at that screen once and shut it down by holding the power button for a very long time. At least 30 second, if not more. Perhaps that'll work for you.
jai134 said:
Thank you. I'm sorry but that didn't help. I can't boot into fastboot mode. When I follow your advice I boot into the logo screen without any text in the upper left corner. Then I give the "fastboot flash boot boot.img"-command from CMD. It just sits there . I think I have to send it back to Best Buy and let them repair it. It was nice for 5 hours though. My personal best in bricking.
Click to expand...
Click to collapse
OK, try this.. Reboot the device by pressing on the power and volume up key. Hold both keys til it reboots and you see the motorola logo. As soon as you see the motorola logo, let go of the power and volume up key. Press on the volume down button once and it would then give you the choice of booting Android (recovery), press the volume down again for the RSD mode, press on the volume again and it will then give you the choice of fastboot mode. Pressing the volume up key will select the current boot mode displayed... See if that works..
Sent from my Xoom using XDA Premium App
No. I can't get into any recovery. It boot into RSD mode 3 or no text in upper left corner. In that mode I can't use fastboot or adb. What can I do with RSD mode 3? Can I create the file that can be flashed with RSD Lite from a wifi xoom dump in the development forum?

[Q] Triumph stuck at moto logo, cant get into clockworkmod

Ok so today my triumph stopped responding so i restarted it (took out the battery). then rebooted. upon reboot phone shuts down and now will hang at the motorola logo for about 10 min before boots but will shut back down due to the battery being dead(but had full charge when this started). Dont know what happened. So i try to get into clockworkmod to flash backup. cant get into it. the only thing i can do is get to the recovery.img file(pressing power+volume down). Other than that nothing.
also tried to boot with power pluged in. it stayed on but would not respond to any touches or button press except the lock button.
I have cwm 5.0.2.6 installed and tickerguy's cm7.
never had this problem till today. Any help would be appreciated.
a new development has occurred. now when i try to access recovery, the phone will just vibrate without stopping.
and i believe its stuck in a boot loop but without recovery i dont know anyway to exit the loop.
Are you able to get into download mode (power off then simultaneously press power button & vol- (should show polling))
Sent from my Triumph using xda premium
Yes i am able to get to download mode
Well after some tinkering (replacing the recovery image, assuming something corrupted it) i can now get to recovery, still takes 10 min to load it though. But i am unable to do anything in recovery because i have to press the menu button to confirm selection but the buttons wont respond. Some help would be appreciated.

[Q] Stuck on HTC, Can't boot into bootloader

Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
H8rift is working on a solution right now. If you can flash back to a backup? I would do so.
Sent from my One X using xda premium
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
You can't get into recovery?
Sent from my One X using xda premium
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
WhatTheAndroid? said:
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
Click to expand...
Click to collapse
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down until screen goes off, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Myrder said:
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
Click to expand...
Click to collapse
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
absolutelygrim said:
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
Click to expand...
Click to collapse
What he said, but after your phone powers off, when i held it for around 7 more seconds, it booted into bootloader when i did it .But try both methods.I was stuck in a bootloop as well, you will be fine. I forgot commands for fastboot, but if anyone wants to tell them to him he could prob get into fastboot by command prompt mabye?
vowelsounds said:
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
Click to expand...
Click to collapse
type "fastboot devices"
your serial number should be on the screen if fastboot recognizes your phone. but I was always able to get into bootloader through commands on the phone.
Also, I can't thank Absolutelygrim and a few others whom I can't think of their names for helping me out of that situation.
ANYTHING Absolutelygrim says, I would listen and take note.
Myrder said:
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down for 6 flashes, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Click to expand...
Click to collapse
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Glad your device is back, good job. Hope i helped.
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Is there a way to close a thread? I've never done this before :/
Thanks to all of you again!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
It's always best to Nandroid before you flash a ROM.
I didn't and I almost made my phone into a very expensive paperweight. Thank god for RUUs.
I also tried to flash a ROM that was for the international version and not the XL which is our phone.
Mods will eventually Close it, just ingnore the thread and it will be closed soon.
If you want to, I know posting a thread in here can amount to a long wait time, just shoot me a PM and I'll give you my email. I get that directly to my phone so I'll be able to reply a lot quicker.
I have the same problem as this guy, but when I hol the volume down button, it has no effect... I hold vol down and power, lights flash 15 times, I keep holding volume down while phone reboots, but no matter how long I hold it down, it just stays at the HTC legal screen.
Was running CM 10.0, and updated to 10.1 (9-3-2012 nightly) with 3-03-2013 GAPPS, via TWRP. Made a backup before flash, Installed both the zips succefully, pressed reboot, and now it doesn't get past the legal screen, and no button pressing is getting me back to TWRP =(
I replaced the screen once, and the volume buttons behaved differently after I re-assembled. Both the buttons work, but they act differently. Pressing vol down or vol up both bring up the volume dialog, but instead of increasing or decreasing the amount, it swtiches between mute and non mute. So I'm thinking the button is not actually doing a 'volume down' action. Any thoughts?
AND, how do you actually turn this device off? It keeps turning itself back on after the 15 flashes.
Thanks for any help.
new developer need 10 posts in general discussion sry

Rebooting for infinity

Hi,
This is my first post so im sorry if I dont explain myself very well, I still practising English.
Anyway, yesterday I was chatting via whatsapp on my Nexus 5 16gb with CyanogenMod 12.1 and sundely it stars rebooting, i thought that i press the power button but when the Cyanogen logo was loading, it started to reboot again and again. When the cyanogen logo apears it reboot again. I can get into the phone a few times but it reboots again and I cant enter the twp to wipe or reinstall another room. I also tried to flash with ADB but i cant enter the recovery mode because it reboots again. I dont know why is this happenig or how can I fix it.
If anyone knows or is in the same trouble let me know thank you.
Regards, zatorr.
zatorr said:
Hi,
This is my first post so im sorry if I dont explain myself very well, I still practising English.
Anyway, yesterday I was chatting via whatsapp on my Nexus 5 16gb with CyanogenMod 12.1 and sundely it stars rebooting, i thought that i press the power button but when the Cyanogen logo was loading, it started to reboot again and again. When the cyanogen logo apears it reboot again. I can get into the phone a few times but it reboots again and I cant enter the twp to wipe or reinstall another room. I also tried to flash with ADB but i cant enter the recovery mode because it reboots again. I dont know why is this happenig or how can I fix it.
If anyone knows or is in the same trouble let me know thank you.
Regards, zatorr.
Click to expand...
Click to collapse
Sounds to me like u have the famed stuck power button that plagues the Nexus 5, if I were u, I would try getting into bootloader mode by holding volume down while it's booting, if that doesn't work and u continue to be stuck in a boot loop, then its def the power button, take the device apart, CAREFULLY, and spray some air into the power button to try and losen it, if that doesn't work then ur going to have to have it replaced
Sent from my Nexus 6 using Tapatalk
soupysoup said:
Sounds to me like u have the famed stuck power button that plagues the Nexus 5, if I were u, I would try getting into bootloader mode by holding volume down while it's booting, if that doesn't work and u continue to be stuck in a boot loop, then its def the power button, take the device apart, CAREFULLY, and spray some air into the power button to try and losen it, if that doesn't work then ur going to have to have it replaced
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, I removed the back case and spray some air but it didnt work, i will have to replace it... I don't understand why is this happenig because i was with the device in my hands when its started to reboot. Dont even fall of or nothing like that... Anyway thanks for the info, now i know that its not the Rom or something like that.

Categories

Resources