Database Info

[Oh Crap] XOOM is dead and it won't boot up!

I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.

Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?

fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.

Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk

It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App

Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App

Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2

That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App

Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2

jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.

I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.

Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.

gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.

No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App

I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App

Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.

Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.

dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?

Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.

[Q] completely dead ns last resort please help

i flashed ics ota update along with superuser zip and all was fine, ics was running perfectly along with root access. google wallet kept forceclosing so i uninstalled it. then i decided i wanted it back to see if i could fix it. without thinking i rebooted to recovery and reflashed the update and su. when i rebooted the phone shut down and wont restart, its completey dead. it wont charge or boot at all. after thinking about it i realize i shouldnt have flashed it since i was already on 4.0 and the update was from 2.3.6 to 4.0. can anyone help me or am i screwed. please help!

Dont know if it is bricked or what, but this may help you:
http://forum.xda-developers.com/showthread.php?t=1397393
but yeah that sucks, good luck

swamp goblin said:
Dont know if it is bricked or what, but this may help you:
http://forum.xda-developers.com/showthread.php?t=1397393
but yeah that sucks, good luck
Click to expand...
Click to collapse
tried that but i get some theme error

Can you get to the bootloader?
From off, Power + VOL-UP. If you get the bootloader screen w/4 options, youre phone is not bricked.

nickmv said:
Can you get to the bootloader?
From off, Power + VOL-UP. If you get the bootloader screen w/4 options, youre phone is not bricked.
Click to expand...
Click to collapse
no does not power on at all and will not charge

OK got it to boot using unbrickable resurrector everything works great but if I power off or reboot its unresponsive again. Anyone know how to make it stick from terminal emulator. Haven't had any luck with adb or fastboot from my computer and would like to use terminal. Please help, soon close!
Sent from my Nexus S

Try flash a stock full ROM.

Si_NZ said:
Try flash a stock full ROM.
Click to expand...
Click to collapse
how? Can I do it through terminal, because I cant power off or reboot to recovery.
Sent from my Nexus S

Pm sent...

Everything fixed......thanks
Sent from my Nexus S

Please explain how you did it. I bought my phone outright and am scared to brick it.. can be us s be bricked. Can I use a Samsung jig to put in download mode since it is a Samsung Google phone??
Sent from MY Google Nexus S

navykid0211 said:
Please explain how you did it. I bought my phone outright and am scared to brick it.. can be us s be bricked. Can I use a Samsung jig to put in download mode since it is a Samsung Google phone??
Sent from MY Google Nexus S
Click to expand...
Click to collapse
The nexus s is pretty hard to permanently brick, but can be a pain depending how bad it is. This time was bad for me. I had already flashed the ics update and flashed superuser zip and all was fine except Google wallet. I uninstalled it with titanium but had second thoughts , so I decided to flash the update again. I know better but just wasn't thinking. The update was from 2.3.6 to 4.0 and since I was already on 4.0 it really screwed it up. It wouldn't do anything absolutely nothing. Apparently the bootloader , boot, and recovery images were completely gone. I did some searching and found unbrickable resurrector. Only problem was it only worked on Linux. So I had to make my laptop duel boot Ubuntu and windows. Ubuntu for unbrickable resurrector and windows for adb/fastboot. Although it sounds rather easy it took about 2 days till I finally figured it all out. I could probably do it now in 30 minutes. And a jig would most likely work but I wouldn't know where to get one. Anyway the resurrector allowed me to boot into fastboot mode and adb/fastboot allowed me to reflash the lost images. Thank God that's over!
Sent from my Nexus S

Solid amber light with no/long boot

I know this title comes up a lot but I can't seem to find my problem.
I wanted to go back to the stock rom and I used the proper RUU but totally forgot to use the S-ON tool before hand. It installed successfully but now I get a solid amber light and so far I got my inspire to boot once only to get stuck on the splash screen with it vibrating non-stop.
And now it just vibrated once, went to a black screen and then shut off. I really don't know what to do since I can't even get to HBOOT nor will the computer recognize it.
I've done numerous batter/sim card pulls as well as clean them out.
Any help would be greatly appreciated

Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA

I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium

lay012 said:
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?

moutansos said:
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Never do a factory reset on a S-OFF device....it will jam u up.
greggyt79 said:
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
Click to expand...
Click to collapse
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....

Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA

greggyt79 said:
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....

glevitan said:
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
Click to expand...
Click to collapse
I will get back on the IRC this evening when I get home from work thanks again!!!

Does it say anything about QHUSB_DLOAD USB device being connected?

I ran into a similar problem not too long ago, immediate vibrating followed by a solid amber light and no phone activity (nothing on the screen at all). I knew I had a backup in Recovery, but I couldn't even get into recovery.
In order to work around this, I did the following steps.
1. Deleted the PD98IMG file from my SD card (so I could get to recovery once I made it to the bootloader).
2. Take out the battery, then put it back in.
3. Plug in the phone, and let it sit for a few minutes.
4. Start into bootloader (hold power + Volume Down)
Now, in my case I was just trying to get back into recovery. if you don't have a working recovery, or no ROM to flash, you'll want to grab a few RUU 's to try from the bootloader. Try stock GB first, then try a stock Froyo just for the heck of it.
Hope this helps! Good luck to anyone else that's stumbled into this problem.
side note: I've also heard of this "power problem" occurring to other people without bootloops or screwed up bootloaders: which is solved by doing steps 2 and 3, then it'll boot up normally.

help
im having same issue i have gb stock and i accidtly did froyo ruu phones power bottun does nothing i have to plug it into computer and it will get solid amber light then eventually it either brings up battery charge icon and then if i press power button or unplug it. it just shuts off the i plug it back in and wait sometimes white htc screen comes up and it vibrates for a while then boots ad works like nothing is wrong but i cant flash gb ruu when i try to do that or re root and go to recovery to reistall ics that is on my sd as soon as phone restarts during process it doesnt reboot then i have to go threw whole procss of trying to get it to boot back up

glevitan said:
Never do a factory reset on a S-OFF device....it will jam u up.
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Click to expand...
Click to collapse
im new to this site but i did exactly what you said in your post and now my inspire wont reboot unless i go threw a few hour process of plugin my phone in and i get solid amber light for like 5 min then a battery charge screen comes up then i have to unplug my phone and plug it back in the last time i did this it took about 8 hours of tryin until it finally got amber light for like 5 min then started vibrating for a min or 2 then it booted up and its bin workin fine for like a week now ive tried to reflash gingerbread ruu ive tried doin upgrade from my phone and tried reroot but as soon as it shuts down to start upgrade my phone is off and wont reboot

Stuck on Boot after Update

I have never installed another Rom before.
However I checked for software updates for my phone, and apparently I needed to update my phone.
After I updated it, it looked great and very fresh.
However when my battery died, I tried turning it back on...and it's just stuck on the whole boot loader sequence. How do I fix this??

Take out the battery, wait a minute, put it back in, check to see what happens.
Sent from a dream.

elijahwhite said:
I have never installed another Rom before.
However I checked for software updates for my phone, and apparently I needed to update my phone.
After I updated it, it looked great and very fresh.
However when my battery died, I tried turning it back on...and it's just stuck on the whole boot loader sequence. How do I fix this??
Click to expand...
Click to collapse
Teichopsia said:
Take out the battery, wait a minute, put it back in, check to see what happens.
Sent from a dream.
Click to expand...
Click to collapse
Do that ^^^^, and if you still are in bootloop, then do a wipe cache...if not contact HTC support. Just for curiosity, was your phone rooted?

Hmm
Unfortunately it wasn't that easy.
I even did a factory reset...and it continues to loop. I tried connecting it to my PC and manually install the software again...no luck.
I called HTC and they have made an "escalated tech ticket" for my current situation. There didn't seem to be any problems during the installation of the software from the update via phone. And the new software was working perfectly for a couple hours...until it's battery died.
I have never modded or rooted or flashed my phone. So I'm just confused as to how this can randomly happen with no cure.

Since you've never done any of those things, let htc handle it. If you have any issues after that, come back and we will see what we can do to help.
Sent from a dream.

Can I recover my data? "System software not authorized by Verizon"

So I guess i followed an outdated tutorial! My phone ever since the ota update months ago destroyed my battery life felt sluggish and constant reboots. Today i followed a tutorial to install rom manager to install clockwork mod recovery so I can delete dalvik cache. On reboot i get "System software not authorized by Verizon Wireless has been found on your phone.”
So now after I realized that the bootloader is locked,
1) Is there a way I can get my phone to work again.
2) But MOST importantly, did I completely screw up and lost any of my pictures saved on the phone?
I'm posting here because everything I look up online is either outdated or I am afraid to break things more. So I would like someone to help me.
Thanks.
P.S. Im pretty sure I had the newest OTA which is 4.4 i think. And the phone was Rooted with towelroot. I can also boot into downloading mode.
Update: Ok so I pressed down + home + power to download mode but this time I pressed Down to cancel and the phone booted to my homescreen. I'm kind of scared to never ever restart my phone. Is my data safe? why booting this way work?
Thank you.

kongol said:
So I guess i followed an outdated tutorial! My phone ever since the ota update months ago destroyed my battery life felt sluggish and constant reboots. Today i followed a tutorial to install rom manager to install clockwork mod recovery so I can delete dalvik cache. On reboot i get "System software not authorized by Verizon Wireless has been found on your phone.”
So now after I realized that the bootloader is locked,
1) Is there a way I can get my phone to work again.
2) But MOST importantly, did I completely screw up and lost any of my pictures saved on the phone?
I'm posting here because everything I look up online is either outdated or I am afraid to break things more. So I would like someone to help me.
Thanks.
P.S. Im pretty sure I had the newest OTA which is 4.4 i think. And the phone was Rooted with towelroot. I can also boot into downloading mode.
Update: Ok so I pressed down + home + power to download mode but this time I pressed Down to cancel and the phone booted to my homescreen. I'm kind of scared to never ever restart my phone. Is my data safe? why booting this way work?
Thank you.
Click to expand...
Click to collapse
On the newest kk OTA you can't run a custom recovery other than safestrap. Unsure if your data is safe at this point since you've created a soft brick
Sent from my Nexus 5

well I don't think this is a soft brick since now I can boot like normal. If I shut off the phone and restart it it boots fine. The only thing now is if i press home +power +up i get that message. So not sure how to delete the recovery and undo what i did.

kongol said:
well I don't think this is a soft brick since now I can boot like normal. If I shut off the phone and restart it it boots fine. The only thing now is if i press home +power +up i get that message. So not sure how to delete the recovery and undo what i did.
Click to expand...
Click to collapse
You will have to Odin back to stock that's basically your only choice. And if it was a hard brick your phone wouldn't work at all
Sent from my Nexus 5

Thanks bro. I'll leave it like this until I have time to do a backup. I need a new phone anyways because of the battery drain. Is there a method or app you recommend to do a back up

kongol said:
Thanks bro. I'll leave it like this until I have time to do a backup. I need a new phone anyways because of the battery drain. Is there a method or app you recommend to do a back up
Click to expand...
Click to collapse
If you can get into recovery and make a backup it's worth a shot. And yea I understand what you mean about battery drain. I love my S3 and I will probably never get rid of it. Try to get into recovery if you can and if not we will go from there
Sent from my Nexus 5