After flashing the new froyo radio rom and the new DJ Droid R1 1.1 rom, when i turn off my desire the screen doesn't turn on and the phone vibrates 5 or 6 six times and then it doesn't do anything!! please help!!
Can you come into recovery mode?
no, i can't do anything. my desire only vibrates
What happened during the flash? Did you interrupt it? Did the flash work correctly without errors? Have you tried booting without sim and SD card? What recovery did you use?
socktug said:
What happened during the flash? Did you interrupt it? Did the flash work correctly without errors? Have you tried booting without sim and SD card? What recovery did you use?
Click to expand...
Click to collapse
the flash worked correctly without errors, the problem started when i rebooted. i used fake flash and i tried booting without sim and sd card
Related
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.
A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.
grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.
@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?
I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?
Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.
sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.
Neither are bricked. Ruu back to stock.
yeah bro not good practice
@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.
Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb
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...
Hello, I got a problem when I flash the ROM for my desire with Clockwork 3.0.0.5 , need your help !!!
Thanks at first !!!
before flash the ROM, I have do the completely wipe and right partition for SD card (Fat32 +EXT4+EXT4+SWAP) or (FAT32+EXT4) according to the ROM requirement.
then after flashing, the flashing successful is displayed. but when I reboot the phone, it will keep in the first screen, and dead there.
And I have also connect it to the computer with ADB logcat, but nothing reported , it seems dead .
I have tried so many ROMs, only one or two ROMs can be flashed successfully and working ,also the information can be reported via the ADB logcat, others just display successful in recovery mode, but dead after reboot( I have waited for nearly 40 minites, nothing happed only the first screen ).
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
please help me and tell me why !
thank you very much!!!
Does anyone know why?
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
Click to expand...
Click to collapse
Why does it fail?
Try booting up with a completely FAT32 SD card and see if that changes anything. You could also try flashing with ClockworkMod 2.1.0.7 (what ever version it is) because you can get some errors with CWM 3.
Yes, I have tried for many times, and every time it is successful in the recovery mode and no error message reported,
but after reboot, it still dead at the first screen
why?
No idea. Devices are tempremental sometimes
I guess you could just wipe your phone clean with an RUU, root it again and then see if anything changes. Something could be corrupted.
Help! no one knows why???
I was installing ARHD 5.2.2 and sense 3.0 mods but it resulted in a bootloop so when i went to recovery i accidentally recovered back to 5.1.9 and now i cant even get in to bootloader and I cant even access my sd card on my computer it says that it needs to be formatted to be used. Is there any way for me to get out of the bootloops or am i stuck with a brick?
imptb said:
I was installing ARHD 5.2.2 and sense 3.0 mods but it resulted in a bootloop so when i went to recovery i accidentally recovered back to 5.1.9 and now i cant even get in to bootloader and I cant even access my sd card on my computer it says that it needs to be formatted to be used. Is there any way for me to get out of the bootloops or am i stuck with a brick?
Click to expand...
Click to collapse
u can´t enter into the bootloader of fastboot?
had u tried to enter via adb? (for to say something)
its probable that you bricked your phone...perhaps u don´t followed correctly the flash steps...
If its still actually turning on, it can be recovered. Just run an ruu.
you can only full brick a DHD with flashing a faulty bootloader or radio.
there is no other way to brick it (ok there was the CWM bug but that is fixed)
Sent out of my Free Candy Van.
Do you have adb on your computer?
If so run the command "adb reboot recovery"
While it is booting.
For sure the sd card is corrupt. Format it and download a new copy of your rom and CHECK THE MD5 SUM before you try to flash again.
Also make sure you do a full wipe this time. Upgrade isn't always possible.
As stated above, if your office is booting it can be fixed.
Sent from my Cyanogenmod 7 phone.
Hey all, My Desire HD just up and died on me. the sd card slot stopped working, and it is in boot loop. Any ideas?
prestybear said:
Hey all, My Desire HD just up and died on me. the sd card slot stopped working, and it is in boot loop. Any ideas?
Click to expand...
Click to collapse
We're going to need a few more dteails than that. What happened right before it died? Was it unlocked? S-Off? Rooted? ROM'ed? Which ROM? What do you mean by boot loop - is it hanging on the boot splash? How do you know the SD card slot stopped working? Can you get into recovery or bootloader? Is it detected in adb or fastboot?
Additional Info
bananagranola said:
We're going to need a few more dteails than that. What happened right before it died? Was it unlocked? S-Off? Rooted? ROM'ed? Which ROM? What do you mean by boot loop - is it hanging on the boot splash? How do you know the SD card slot stopped working? Can you get into recovery or bootloader? Is it detected in adb or fastboot?
Click to expand...
Click to collapse
Sorry about that. So the whole story is, when I first got the phone the screen was broken, everything worked. replaced the screen, and the SD card wouldn't recognize when booted up to ROM it mnokee os jb 4.1 I believe. However the sd card was recognized in the bootloader, so I loaded OTA for rooted phone onto sd and it updated from sd card within bootloader. ADB and fastboot was working. Then after a while I put JB back on. A few months later, it just died and stays in the boot loop.
Any help that can be given to get device up and running with sd card would be much appreciated.
prestybear said:
Sorry about that. So the whole story is, when I first got the phone the screen was broken, everything worked. replaced the screen, and the SD card wouldn't recognize when booted up to ROM it mnokee os jb 4.1 I believe. However the sd card was recognized in the bootloader, so I loaded OTA for rooted phone onto sd and it updated from sd card within bootloader. ADB and fastboot was working. Then after a while I put JB back on. A few months later, it just died and stays in the boot loop.
Any help that can be given to get device up and running with sd card would be much appreciated.
Click to expand...
Click to collapse
So in your case, when you say bootloop, you mean its stuck on the currents ROM's boot animation right?
what recovery were you having?
Can you boot into recovery or bootloader.
If you had a custom recovery, you could try booting into it and reinstall your rom.