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.
Related
Ok so i installed this this app called "GST (Galaxy S Tweaker)" because i wanted to change my lock screen to froyo. i did all the procedures and i locked my phone to see if it worked... the screen went black and i couldnt unlock it. so i did a battery pull and turned it back on... the screen was stuck at AT&T world phone bootup screen. I pulled the battery and restarted it at least 5 more times and the same thing kept happening. I started the phone it bootloader and i clicked reinstall packages since i was running eclair 2.1.... i restared nothing happend..... i factory reset the phone while in bootloader restarted nothing happend.... now i dont know what to do i need help fast i have only had my phone for 2 weeks. its a great phone and love it but i need a unbricking method fast someone help please....HELP!!!!!
Yeah, the same exact thing happened to me, and I've done pretty much everything I can think of. No luck so far...
Put your phone into download mode then reflash with the odin one click provided in the link below
Hope this helps
http://forum.xda-developers.com/showthread.php?t=731989
Thanks, I'm downloading it right now.
When the official update for Froyo comes out, I'll be able to download it since this is stock, right?
klawz324 said:
Thanks, I'm downloading it right now.
When the official update for Froyo comes out, I'll be able to download it since this is stock, right?
Click to expand...
Click to collapse
If you can get the phone booted yes.
Wow. Even though I did accidentally get on the "phone-!-computer" screen, after a while, my phone was all back to normal. I can't thank you enough!
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.
So i used my xtc clip to s off an inspire and tried installing clockwork and SU but clockwork gave me an SU error. So i loaded the acehack and tried that, then i ended up getting the soft brick, so i flashed the ruu and it seemed to flash fine but now the phone wont turn on it just charges.
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
xboxhaxorz said:
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
Click to expand...
Click to collapse
Have you started with the easiest fix by pulling out the battery & waiting a minute & putting it back in, then try to power on the phone.
Sent from my Inspire4G using xda premium
yes left it out for 5 mins
Can you get into bootloader or fastboot
Sent from my Inspire 4G using XDA App
left battery out overnight and tried turning on again no go
no fastboot or bootloader
removed all cards and still will not power on
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Does it allow you to get into the bootloader by pressing power and - volume at all?
xboxhaxorz said:
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Click to expand...
Click to collapse
Sounds like you have a corrupt hboot (or ENG hboot on a late model Inspire). You need to get the stock hboot on it and it's not trivial. Try jumping into our irc channel and hopefully we can get you straightened out:
http://webchat.freenode.net/?channels=#liberatedAria
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
ctsfinishes said:
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
Click to expand...
Click to collapse
Make a nandroid of your current rom(if it's what you llike/want to use), run the RUU to restore factory config and dl the newest version of the hack kit and reroot it. Once done, restore your nandroid that you made earlier.
ATTN1 made a version of the HK w/ ENG-HBOOT that was discovered to cause very slow boots an pulled it down, the latest version should boot normally upon completion.
thank you for the info. i'll post back when i try to reroot and install ruu
i ended up warranty exchanging my phone, attn was helping me but i think mine was too fubared
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
Hi.
I found my old Backflip yesterday and decided to use it as a bluetoot-keyboard. Since the original ROM was so out of date, I decided to flash a bootloader and flash CM. So I flashed the recovery, flashed CM. Rebooted, phone started booting, but as soon as it was showing "ANDROID" on the screen, it went off and started over. I was able to get back to the recovery, so I wiped it again and flashed CM again, same. Now it's even worse: The battery is dead, the phone can't power up by itself, only works with the wall-adapter. Even hooked up to my computer, only the light around the port flashes up.
Can someone help me pls?
Cheers!
Jukpulfer said:
Hi.
I found my old Backflip yesterday and decided to use it as a bluetoot-keyboard. Since the original ROM was so out of date, I decided to flash a bootloader and flash CM. So I flashed the recovery, flashed CM. Rebooted, phone started booting, but as soon as it was showing "ANDROID" on the screen, it went off and started over. I was able to get back to the recovery, so I wiped it again and flashed CM again, same. Now it's even worse: The battery is dead, the phone can't power up by itself, only works with the wall-adapter. Even hooked up to my computer, only the light around the port flashes up.
Can someone help me pls?
Cheers!
Click to expand...
Click to collapse
I think that the battery is faulty......
Try using the battery with another mobile
eatsleep said:
I think that the battery is faulty......
Try using the battery with another mobile
Click to expand...
Click to collapse
I agree with him it sounds like your battery has issues. Although it could be somewhere in the flashing something went wrong. (doubt it)