Related
Hi,
I rooted my DHD today and tried to flash the CyanogenMod-7 for Desire HD & Inspire. It seemed to work but now keeps re-booting every couple of seconds. It won't actually stay on long enough to put another ROM on. Can anyone help? This is the first time I've done something like this and it seemed to be going so well!
Thanks!
Pull the battery for about 10 seconds. Then hold the vol- button down and power your device on. Now you should see a white screen with some text on it. Navigate to recovery and press the power button. Now it should boot into recovery.
In the recovery choose wipe data/factory reset ald let it finish. Once its finished choose wipe cache partition.
Then go to install .zip from sd and then choose zip from sd. Now search for your rom and reinstall it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
This is common. Simply wait for it to boot and power off or use the power button to select reboot. You only have to do it once.
The instructions for installing CM7 all say to install ROM then reboot after first complete start up. Shouldn't need to reinstall anything.
Having been left alone for a few hours it seems to have sorted itself out. Thanks! I just wasn't expecting it to spend quite so long re-booting.
I guess you have enabled wi-fi just after flash cm7. Seems like there is a bug or whatever, all you need is re-boot device after first boot.
And about the re-boot loop, just remove battery to turn off you device then turn it on, enter recovery and flash cm7 again WITHOUT do wipe operation. OK, In this time remember to re-boot after first boot.
I got a bit trigger happy and tried to flash Android Revolution HD 3.3. I did a full wipe from ClockworkMod Recovery and tried to install the zip, exactly like I did for the previous ROM. That kept aborting the installation so I mounted the phone and re-downloaded and copied it onto the SD card again. Same problem. I then tried to re-install cm7 and that also kept aborting.
I now have the message "Back menu button disabled" and if I use the power button to select anything it goes straight to a white triangle with an explanation and the Droid, which I think is stock recovery? I'm getting there from what I think is Clockwork though. Is this recoverable or have I managed to brick it?
I had a similar issue a few days ago - it turned out that the battery stats were screwed up so a fix for me was to boot into recovery and then wiping the battery stats.
Everything was fine after that.
How do I do that? I don't want to reboot out of Clockwork as I'm not 100% sure I actually have a ROM at the moment.
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
mdaigt said:
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
Click to expand...
Click to collapse
open recovery, goto advanced and wipe battery stats
Going to leave battery out for the night as read in other posts. Fixes the problem of not totally shutting down for some. Thanks.
Well leaving battery out didn't help. Continuous boot loop. Put on charger after turning off orange light came on and didn't go to green after 10 hours. Restarted when I got home and boot loop again. Had CoreDroid ROM installed. Working fine than tried to load Kalagas Mixed Theme and that is where I am now. Looping.
Even a blind squirrel will find a nut now and then. During HTC Hboot menu, noticed it was looking for PD98IMG zip. So I shut phone down. Inserted card with it on it and it restored to original firmware. PHEW. Hope this might help someone else.
I have bricked my Motorola Defy.
I have tried flashing a new ROM using RSD Lite (following this guide). It says 'complete' but my phone will not turn on. Sometimes it will just show the Moto boot logo but never fully boot up. I can only open the boot menu.
The ROMs I have tried flashing can be found here (All UK 2.1 at the top of the page).
Background - I got into this mess by attempting to flash the Gingerbread UI ROM (here).
Does anyone have any ideas? I would really appreciated any suggestions.
Thank you.
Probably you have flashed a firmware which cannot be downgraded to eclair. Try to get again in the bootloader and flash a froyo build (the official french one, for instance).
Hope this helps
Sent from my MB525 using XDA App
but supposedly it is still an éclair ROM so it shouldn't be the reason... best thing would be to flash an original 2.1 rom, I'm sure you can find one on the development section. Make sure to have a fully charged battery though - charge it on someone else's phone, for example.
It's most likely a problem with cache. Power your phone with Volume Down holded, when in recovery press Volume Up + Down, clear data/factory reset, clear cache.
rafaccb said:
but supposedly it is still an éclair ROM so it shouldn't be the reason... best thing would be to flash an original 2.1 rom, I'm sure you can find one on the development section. Make sure to have a fully charged battery though - charge it on someone else's phone, for example.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I have tried using the UK ROMs here: h**p:// and-developers. com/sbf:defy but none have worked. Any other suggestions?
Thank you.
antony.ps said:
It's most likely a problem with cache. Power your phone with Volume Down holded, when in recovery press Volume Up + Down, clear data/factory reset, clear cache.
Click to expand...
Click to collapse
Hey, unfortunately I cannot get into recovery, only the boot menu. Do you have any other suggestions?
Try flashing a JRDNEM_U3_2.59.0 sbf.
ABC_Universal said:
Try flashing a JRDNEM_U3_2.59.0 sbf.
Click to expand...
Click to collapse
Thanks, I will try now. Any particular country?
ABC_Universal said:
Try flashing a JRDNEM_U3_2.59.0 sbf.
Click to expand...
Click to collapse
Hey.
I have just tried this using the Australian version from here:h**p://and-developers.com/sbf%3adefy
Unfortunately, it did not work. I still cannot boot the phone.
Thanks for your advice, do you have any other ideas?
Have you tried one of the 2.51 version roms?
like JRDNEM_U3_2.51.1 Blur or
JRDNEM_U3_2.51.0 deblur.
Kaljam
kaljam said:
Have you tried one of the 2.51 version roms?
like JRDNEM_U3_2.51.1 Blur or
JRDNEM_U3_2.51.0 deblur.
Kaljam
Click to expand...
Click to collapse
Hi, yes I have tried the UK JRDNEM_U3_2.51.1 from here. Is that the same as blur or deblur?
Thanks.
Just an update...
All ROMS I have tried have installed OK through RSD Lite. The result is always 'Finished' or 'PASS'. But then when I try to turn my phone on, it never boots up.
I really appreciate the replies so far. If anyone has any further ideas, I would love to hear them.
Thank you.
UPDATE
I have just flashed the latest froyo leaked ROM as suggested around the net. Slight progress, the phone now boots to the moto boot logo but no further?
Does anyone have any ideas from here?
Thank you.
you do know that after flashing an sbf it takes a very LONG time to boot the first time! I just hope you are not giving up after a a couple minutes of M logo and pulling the battery or something it literally takes like 5 minutes.
You said you are still able to enter bootmenu? That is not possible after flashing an sbf, as it wipes the bootmenu away! Are you talking about bootloader?
Pull the battery and immediately put it back in while holding vol down. If the phone does not turn on just by inserting the battery then continue to hold vol down and press the power button for about 3 seconds, do not let go of vol down. Continue holding vol down until stock recovery appears.
Once you're in stock recovery press vol up AND vol down at the SAME TIME. Now use the volume toggle to select wipe date/factory reset, use the power button to make your selection, then wipe cache partition. Reboot
Walk away for like 5-10 minutes and check back on it.. Theres no reason it shouldn't work
zyxwvut said:
you do know that after flashing an sbf it takes a very LONG time to boot the first time! I just hope you are not giving up after a a couple minutes of M logo and pulling the battery or something it literally takes like 5 minutes.
You said you are still able to enter bootmenu? That is not possible after flashing an sbf, as it wipes the bootmenu away! Are you talking about bootloader?
Pull the battery and immediately put it back in while holding vol down. If the phone does not turn on just by inserting the battery then continue to hold vol down and press the power button for about 3 seconds, do not let go of vol down. Continue holding vol down until stock recovery appears.
Once you're in stock recovery press vol up AND vol down at the SAME TIME. Now use the volume toggle to select wipe date/factory reset, use the power button to make your selection, then wipe cache partition. Reboot
Walk away for like 5-10 minutes and check back on it.. Theres no reason it shouldn't work
Click to expand...
Click to collapse
Hey,
I have just got back from dropping of the phone with T-Mobile - Damm!!!!!!!
Thanks for the detailed explanation. I must have talking about the bootloader. Not the menu. I will head back to the shop in the morning and collect it back off them. Hopefully as it is a Saturday they have not sent it off?
Sooooo frustrating!!!!!!!!
I will update you when I have got it back and tested the above.
Thanks again,
Chris.
LOL I know what you mean... I had instant heart failure the first time I was stuck in a bootloop!!! Thought I wasted $400
I just panicked and gave up.. damm! Loads of people have said that its almost impossible to brick a defy. Fingers crosses thats true!! Lol
First, sorry for my english.
I have a similar problem. I flashed the official french froyo.
First it runs good. But today, two days later, the defy reseted automaticaly.
Several times.
Then I did a wipe. At the end the defy reseted automaticaly and stopped at the motorola logo. I flashed again. At the end of the flash, when RSD boots the defy, it stopped at the logo again. After...it must have been 15 minutes I pulled the battery and tried to get into the bootloader for a wipe.
But I can't enter the bootloader (vol up + power). The motorola logo appears and nothing happens. The last time I waited over 30 minutes.
OK, I have my phone back from T-Mobile...here it goes!!! (fingers crossed).
EDIT
Battery is out - will re-charge with the USB cable trick..
zyxwvut said:
you do know that after flashing an sbf it takes a very LONG time to boot the first time! I just hope you are not giving up after a a couple minutes of M logo and pulling the battery or something it literally takes like 5 minutes.
You said you are still able to enter bootmenu? That is not possible after flashing an sbf, as it wipes the bootmenu away! Are you talking about bootloader?
Pull the battery and immediately put it back in while holding vol down. If the phone does not turn on just by inserting the battery then continue to hold vol down and press the power button for about 3 seconds, do not let go of vol down. Continue holding vol down until stock recovery appears.
Once you're in stock recovery press vol up AND vol down at the SAME TIME. Now use the volume toggle to select wipe date/factory reset, use the power button to make your selection, then wipe cache partition. Reboot
Walk away for like 5-10 minutes and check back on it.. Theres no reason it shouldn't work
Click to expand...
Click to collapse
Hey, I am still have issues...
I have charged it up but cannot access recovery. I have tried taking out the battery and putting it back in while holding vol down but no luck. I have also tried holding the power button as well like you said.
I am going to leave it charging even longer to see if that helps.
Looking for some help here My battery drained to 0% last evening while i was out. Went back home plugged it in to wall charger, quite sure that it'll boot shortly.. unlucky for me the phone booted for a minute or so and then powered off again. Did a small research today, and found some news about Nova kernel not having an option to charge while off, and an advice of one of the mebers to reflash kernelto one with this option. Dunno why but i did a complete wipe and now im stuck without any ROM and on JB splash screen (i've been using PA ROM) with an empty battery.
Need some help, anybody?
BobbyManifesto said:
Looking for some help here My battery drained to 0% last evening while i was out. Went back home plugged it in to wall charger, quite sure that it'll boot shortly.. unlucky for me the phone booted for a minute or so and then powered off again. Did a small research today, and found some news about Nova kernel not having an option to charge while off, and an advice of one of the mebers to reflash kernelto one with this option. Dunno why but i did a complete wipe and now im stuck without any ROM and on JB splash screen (i've been using PA ROM) with an empty battery.
Need some help, anybody?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2118921
Sent from my LT30p using xda premium
Try puting it to offline charging by,
When it boots turn if off via power button + power up. After the 3 vibrations then plug it in and let it charge.
Sent from my Xperia S using xda app-developers app
cant get in to fastboot nor flashmode. phone charges a bit turns on and then after a while it turns off..
flashtool says that i have no rom no kernel and the other thingy..
will try Li-polymers advice
As I've mentioned, before I wiped the device (dumb ass) i was on Nova kernel, after the wipe "S" im stuck on JB splash and nothing more. After that phone turns itself off and again to the splash..
Need some help desperately :crying:
Trying Hackberry's method atm, device gets listed in terminal when its on the JB splash -
[email protected]:~$ adb devices
List of devices attached
BX9036AF9B device
so it's doing something but i can't get into fastboot mode and flash a new kernel... is there any other way, option?
Or send it on warranty?
BobbyManifesto said:
Trying Hackberry's method atm, device gets listed in terminal when its on the JB splash -
[email protected]:~$ adb devices
List of devices attached
BX9036AF9B device
so it's doing something but i can't get into fastboot mode and flash a new kernel... is there any other way, option?
Or send it on warranty?
Click to expand...
Click to collapse
i had exactly the same same situation as you yesturday..... no rom battery 0%
plug it to your pc, open the terminal window where you got your stock ics17.elf ,type the code to flash it, meanwhile wait for the phone to boot that JB logo, when it does press power button + volume up button till 3 vibrations ( one vibration didnt work for me), the phone will reboot but you keep volume up button pressed, you'll se the blue led on ,press enter key in cmd to flash the kernel .
thats it it will charge.
@Ofcos mate, if it'll work, i owe U a keg xD
EDIT: Success!!!
what i did:
- flashed kernel via fastboot as Ofcos suggested
- waited 'till Nozomi will boot to splash again
- put it into fastboot again
- flashed recovery-nozomi.img
- fastboot reboot
- wait a while for it to boot again
- boot into recovery
- flash ROM zip as usual
Nozomi's charging and running!!!
So... i was backing up my phone(twrp 2.8) and the light on the screen turned off. When i pressed the power button to turn it back on... well nothing. Hard bricked? The red LED wont turn on when plugged in. Does detect the phone if i plug it in PC.
Edit: Well... i managed to reboot it... but keeps rebooting in recovery.
God... moved past the recovery bootloop. but now im stuck at "Android is upgrading. Starting apps." fml.
DarkZen33 said:
So... i was backing up my phone(twrp 2.8) and the light on the screen turned off. When i pressed the power button to turn it back on... well nothing. Hard bricked? The red LED wont turn on when plugged in. Does detect the phone if i plug it in PC.
Edit: Well... i managed to reboot it... but keeps rebooting in recovery.
God... moved past the recovery bootloop. but now im stuck at "Android is upgrading. Starting apps." fml.
Click to expand...
Click to collapse
Looks like u had installed twrp 2.8 on lollipop v5.0.2 .
- you will get your phone jammed there just like paralyses when you try to backup/restore i too got this problem.
- U were supposed to install TWRP 2.8.7 in lollipop
- HOLD power + BOTH VOL button long to come out
Well... i managed to reboot it... but keeps rebooting in recovery
- After u come out again ur screen is on if u go back to recovery again , In recovery HOLD POWER + VOL UP long
- Your phone will get restarted normally to HTC boot .
stuck at "Android is upgrading. Starting apps."
- Just leave the phone to upgrade if failes
- power down your phone
- Go to HBOOT VOL DOWN + POWER
- Staying at bootlodder flash TWRP 2.8.7 exe just doble click from pc ( put this exe in fastboot & ADB drivers folder for best result )
- Reboot now to FASTBOOT
- Go to recovery
- Check for TWRP changes
- MAke backup
- reboot system
- You Must not be stuck at upgrading long.
Make sure of above all button combination you do
Here is TWRP 2.8.7 exe for lollipop > https://mega.nz/#!ndk2SQpb!aNoRdnonBds_zZ5ZX28qrhC40rlj5TfLca1OvSUMa5s
Worked
Thx man. Worked.
DarkZen33 said:
So... i was backing up my phone(twrp 2.8) and the light on the screen turned off. When i pressed the power button to turn it back on... well nothing. Hard bricked? The red LED wont turn on when plugged in. Does detect the phone if i plug it in PC.
Edit: Well... i managed to reboot it... but keeps rebooting in recovery.
God... moved past the recovery bootloop. but now im stuck at "Android is upgrading. Starting apps." fml.
Click to expand...
Click to collapse
DarkZen33 said:
Thx man. Worked.
Click to expand...
Click to collapse
Good to hear that :good:
I have a rooted One M8 here with a custom ROM and recovery that I have been trying to boot into recovery however every time I try the phone seems to crash, turn of and then won't boot. After about 15, 20 minutes the phone boots up again by itself. Anyone else ran into this problem before or any advice on a solution? Thanks.
You can get to bootloader okay?
If so, go into fastbootmode (connected to computer) and fastboot erase cache, and try installing TWRP again.
redpoint73 said:
You can get to bootloader okay?
If so, go into fastbootmode (connected to computer) and fastboot erase cache, and try installing TWRP again.
Click to expand...
Click to collapse
That didn't work.. Tried booting into recovery and wiping the data and re-flashing the ROM but no luck.
lkavo said:
That didn't work.. Tried booting into recovery and wiping the data and re-flashing the ROM but no luck.
Click to expand...
Click to collapse
So what exactly worked, and what didn't? The way you've typed it, I can't tell:
You can boot into bootloader?
You were able to flash recovery?
You are able to get into recovery?
The ROM flashed successfully?
But then it failed to boot?
Also, what ROM?
What version TWRP (version number)?
Try another ROM. Be sure to do the default TWRP wipe (data, cache, Dalvik) before flashing ROM.
I can boot into the bootloader and into the system it's self but it takes maybe 15 to 20 minutes everytime the phone is turned of to start back up again and begin booting.
I'm not sure what version TWRP is as it been months since I flashed it and I can't check because I'm waiting on the phone to boot again.
lkavo said:
I can boot into the bootloader and into the system it's self but it takes maybe 15 to 20 minutes everytime the phone is turned of to start back up again and begin booting.
Click to expand...
Click to collapse
So do I have this right: The phone turns itself off, will stay off 15-20 min; during which time you can't do anything until it starts to reboot itself?
What happens if you hold power button, or power + vol up for a minute or more? Do either of these force it to start booting, or no response until it boot on its own (15-20 min).
redpoint73 said:
So do I have this right: The phone turns itself off, will stay off 15-20 min; during which time you can't do anything until it starts to reboot itself?
What happens if you hold power button, or power + vol up for a minute or more? Do either of these force it to start booting, or no response until it boot on its own (15-20 min).
Click to expand...
Click to collapse
Yep that's right.
No response until it boots on it's own.