Develop Bugs

[Q] Flash new ROM after boot or recovery no longer works

I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.

I have downloaded the RUU from forum.xda-developers.com/showthread.php?t=695667 (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe) and run it.
It starts working and then stops with the message "Error[140]: Bootloader version error". How do I get the correct RUU for my bootloader (HBoot 0.92.0001)?

I have also tried Froyo downgrade (forum.xda-developers.com/showthread.php?t=768256) but it just returned a whole lot "Error: Device not found" messages.

Tried flashing RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed and received an error about a file not being able to be opened for writing.
Just ran RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe and it completed successfully but it still doesn't go past the screen with the white background and the green HTC logo.

RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.0 0.32U_5.09.05.30_2_release_142828_signed.exe didn't work originally but I charged until it was fully charged and then tried booting it again and it worked.
I had taken my sim and sd card out so I switched it off and put those back in and again it booted up fine. I was then switching Wi-fi on and it suddenly restarted and now it refuses to boot again.
Any ideas?

I can now consistently get it to boot by doing the following:
1. Remove battery
2. Put battery back
3. Charge until full and then leave plugged in for about 15 minutes.
4. Switch phone on.
Unfortunately it is still randomly re-booting while using the phone, could be it be a bad partition on the sd card?

trancehead said:
I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.
Click to expand...
Click to collapse
try flashing the bootfix on the first post of LeeDroid thread
EDIT: here it is http://db.tt/QLu5cPL

Thanks for replying. How do I flash the bootfix?
Also, I don't have Leedroid anymore and I am back on stock Froyo ROM.

you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.

w.0.o.t said:
you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.
Click to expand...
Click to collapse
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method

trancehead said:
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method
Click to expand...
Click to collapse
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.

More frustration. If I take the sd card out it will boot up so that I can see the home screen but then it just reboots again, and again, and again at the same point.
When I put the sd card back again it gets to the HTC logo and stops again.
This is really starting to annoy me

w.0.o.t said:
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.
Click to expand...
Click to collapse
I have yet to get recovery to actually run, always stalls on the HTC logo. I also can't get the phone to start with the SD card in so I can't load files onto it.

One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt

EddyOS said:
One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt
Click to expand...
Click to collapse
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?

trancehead said:
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?
Click to expand...
Click to collapse
i'd try that if i were you. this goes without saying but make sure you back up first.

I actually don't think any of the above made any difference...
I just put back my SD card and the phone is working perfectly again. The only thing I can think of is that during the day it is too hot and it is cooler now (at night). This seems to be backed up by this thread - forum.xda-developers.com/showthread.php?t=676402
has been running since yesterday evening without a problem. Weird...

[Q] 5 vibrate no boot inc

Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?

sorry wrong place mods please move to q&a
/10 characters

Try reformatting your memory card to FAT32 and then put the PB31IMG.zip to the root and try again.

reformat suggestion
did that. only two files on card are pb31img and update.zip. freshly formatted fat32

This is in the wrong section.
But to answer your question, RUU.
Also, root voids warranty. So if they happen to look into it and see that your device is rooted, you'll likely get charged the $100 insurance deductable. Unless you don't have the insurance.. then you'll end up paying the full $549 or whatever it is.
Sent from my ADR6300 using XDA App

un-root and get a refurb. happened twice to me allready/

stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I've had this happen before. I'm not sure why the nandroid restore would fail, but it may have been because of a near-full SD card. I was stuck at hboot for a while, but couldn't get into recovery. I tried to enter recovery like 30 times and it worked once so I wiped and installed my rom.

i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?

stoffelck said:
i can get into recovery but it is the stock recovery. can only flash update.zip. if i had a rom could i rename it update.zip?
Click to expand...
Click to collapse
no, root is needed for any rom other than HTC

also, then phone will boot if you have it plugged in. get a refurb, ask for over night delivery, they never say no.

stoffelck said:
Ok so it has happened to me finally.
I was installing a rom. It was unsuccessful so i restored my last backup.
It restored and upon reboot i got 5 vibrates and black screen.
i can get to hboot and hboot usb
hboot ver 92
radio 78
I have tried a couple pb31img. they install all with ok and then 5 vibrate no boot.
I can get to recovery and flash update.zip. 5 vibrates no boot.
I have a replacement on the way.
But i really want to fix it! any ideas?
Click to expand...
Click to collapse
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?

Alpha Maven said:
I have the same trouble. This happened Monday afternoon after backing up via clockworkmod, full wipe, and flashing cm_inc_full-0.zip. 5 buzzes and green LED flash at boot after the white splash screen.
Previously, I had S-OFF, but after the buzzing, hboot shows S-ON.
I can get the phone to boot completely if I have it connected to my computer, but as soon as I disconnect the cable, the display blacks out, 5 buzzes and green LED flash.
I have flashed the latest Verizon stock PB31IMG (build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip) and it is successful, but the phone still behaves the same. Trying to flash older stock Verizon firmware does not work, because hboot knows it is older, and refuses to install.
I cannot get adb to recognize the phone, no matter what I do, but fastboot sees the phone at hboot. RUU also does not work, it never sees the phone. Unrevoked starts to run, but quickly stops with a communication error.
From what I have read on this forum and others, this issue is happening quite frequently in the last few days.
I tried the "old school" method for rooting, by running a adb shell loop and trying the eject sd card method. That did not work.
Does anyone have any suggestions as to try?
Click to expand...
Click to collapse
yea, un-root, s-on and get a refurb.

It might be helpful to know which ROM(s) were being flashed when this happened, to see if there is any consistency.

i had been flashing the #XX-inc-cm7src-syko-eng packages before I flashed cm_inc_full-0.zip

I am having this same problem, to the letter. I had been running Skyraider and wanted to try MIUI. However, I was only preparing to flash a new rom. I hadn't even put the rom on the sd card yet. It was giving me issues getting into clockwork and when I finally managed to get in, it wouldn't backup. I reformatted my sd card and tried again; it said it succeeded doing the nandroid backup and when I rebooted it started doing the 5 vibration no boot thing. I never actually even loaded a rom, all I did was a nandroid backup, which I can't find on my sd card now so it apparently failed despite the message.
I messed with this for a day and managed to get the stock november OTA loaded with s-on via timely connection and disconnection to my pc, so I shouldn't have a warranty issue. I took it into the verizon store and they overnight shipped me a refurb. Unfortunately, it was evening when I went in so it could apparently take until monday
In the meantime, I can still use it if I turn it on while connected to my pc and disconnect as soon as I see the "quietly brilliant" screen. If you wait until it boots all the way in it will usually shut down vibrating when you disconnect it. Hope that helps someone that just needs the phone to work for a bit. Would love to know if someone finds out what is happening and if there is a way to fix it.
Don't know if this helps but I had been having issues with my phone frequently telling me the sd card was mounted read only leading into this, but it would usually fix itself if I tapped the icon that popped up. I also had lost the ability to unmount the sd card prior to this, and the phone would no longer work as a mass storage device when connected to the pc. I thought it was a problem with Skyraider but now I'm not so sure. Don't know if others are also experiencing this, but even now that I got it running on stock and into the os the 8gb internal phone storage and my sd card no longer register.

This basing on the info I have gather from people smarter then myself...
5 vibs = qualcomm download mode. From what i have been able to gather a simple batt pull should resolve the issue.
The way you get into this download mode is by pressing the vol+/- at the same time. Kinda explains the reason it is becoming so frequent.
I have no proof to back this up but give it shot.

Okay, so do you have CWM at this point?

CWM?
Sent from my ADR6300 using XDA App

[Q] Problem with SGS and custom kernels

So I decided to try out the new cyanogen mod 7.1. I followed These instructions and everything went fine until it was time for the phone to reboot after heimdall's flash.
It didnt reboot, but stayed on the splash screen. I could still both boot in recovery (recovery was CVM) and download. I thought everything was ok, and put the cyanogen-update zip onto the external memory card. However, as all of you (and now I) already know, it doesnt work that way, as the zip has to be on the internal SD.
"Sucks to be me" I thought, but I applyed the update.zip that was already on the card, hoping that it would reset everything (did a factory wipe as well). It didnt.
So, I started kies, set the phone to download and hoped. Kies detects the phone, but it couldnt connect (it just tries infinitly). So, here comes the retard part: I found a guide for installing the same kernel with odin, so I tried that. Odin found the device, but stopped right after (SetupConnection). So, I pulled the battery, waited 5 minutes, and the dreaded "download error" came up. So I restarted the phone, tried to put it in download mode, and it worked! So, now Im back at square retard, becuase heimdall can still flash it and kies still finds the phone (without succeding in connecting), but it doesnt do anything else.
So: what do I do? At the present, I am prepared to settle for stock everything, as long as I get my phone back (I will probably try to install cyanogen again, and come back with new questions, but that is a later problem).
Thanks in advance<3

Prob better posting this in General or on a CM 7 thread/post...
You shouldn't have a problem flashing a stock rom with odin. Just remember to pick repartition, with the correct pit file for the rom.
Sent from my GT-I9000 using XDA App

is this **** bricked??

its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load

can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?

aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.

mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.

Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...

tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.

I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!

Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.

Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...

fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.

Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!

Maybe http://www.microsoft.com/windows/virtual-pc/ can help?

alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!

fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.

So you're saying you go into the boot loop after turning off your phone even after unbricking?

I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?

fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.

[Q] my phone isn't booting up all the way

For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:

It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.

Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app