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.
I flashed IceColdSandwhich rom, did backup before. I realized I forgot to wipe cache and devik cache.
After the installation said it was successful, I clicked reboot on instinct and then it is now stuck on the loading screen.
I tried to hold volume down+power button, however it leads me back to normal boot screen. Why is that? Is there a way to get back into recovery?
This seems like a simple problem and I did a search but the normal response was the vol down+power button, which isn't working for me.
Any help/advice?
How long were you suck on the loading screen? Sometimes the first boot can take awhile. My recommendation is to to restart and try to wait it out, as some first boots can take up to 10 minutes (although very rarely.)
If that doesn't work, try powering down to launch HBOOT, don't just restart. Hopefully you'll get back to recovery and wipe again and reinstall.
Good luck. Maybe someone else has better advice.
P.S. LC isn't updating Ice Cold anymore, so I'd recommend flashing Redemption or existz aospX. Redemption is my favorite ICS ROM out of them all.
Sent from my Inspire 4G w/Redemption
WordsworthESP said:
How long were you suck on the loading screen? Sometimes the first boot can take awhile. My recommendation is to to restart and try to wait it out, as some first boots can take up to 10 minutes (although very rarely.)
If that doesn't work, try powering down to launch HBOOT, don't just restart. Hopefully you'll get back to recovery and wipe again and reinstall.
Good luck. Maybe someone else has better advice.
P.S. LC isn't updating Ice Cold anymore, so I'd recommend flashing Redemption or existz aospX. Redemption is my favorite ICS ROM out of them all.
Sent from my Inspire 4G w/Redemption
Click to expand...
Click to collapse
Thank you resolved.
For those with similar problems:
I finally was able to access HBOOT by holding vol down and then pressing and releasing power button after about 2sec. Do not let the HTC boot screen to show up before release.
Oh my I think i screwed my phone up
I tried flashing ZenSeries 6.42 kernal (wipe cache and davlik) and everything seemed fine. Went to boot up and i get passed the splash screen, but the phones stays stuck on with the google nexus logo and never boots to my lock screen. I tried taking out the battery and going into recovery but it's a no go. I press volume down and power and i go into "odin mode" and it's telling me it's "downloading" then if I hit the power button it takes me back to boot loop. I've been away from the scene due to new marriage, school and work so I'm not sure if i lost touch and forgot how to use my phone like a hacker should anyone know how i can fix this?
cyaiphone said:
Oh my I think i screwed my phone up
I tried flashing ZenSeries 6.42 kernal (wipe cache and davlik) and everything seemed fine. Went to boot up and i get passed the splash screen, but the phones stays stuck on with the google nexus logo and never boots to my lock screen. I tried taking out the battery and going into recovery but it's a no go. I press volume down and power and i go into "odin mode" and it's telling me it's "downloading" then if I hit the power button it takes me back to boot loop. I've been away from the scene due to new marriage, school and work so I'm not sure if i lost touch and forgot how to use my phone like a hacker should anyone know how i can fix this?
Click to expand...
Click to collapse
Volume Up & down + power to boot into the bootloader & then use the volume keys to change "start" to "recovery"
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
justsomedude23 said:
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
Click to expand...
Click to collapse
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM(clockworkmod) is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache(the factory reset in TWRP), but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search.
But if its loading to the CM logo, it is not a paperweight. Worst case scenario you can use LGNPST and a stock bin file to go completely back to stock. But as long as you can get into recovery you shouldn't have to go to those lengths.
Hope this helps.
EDIT: I know it's your phone and if you are like me, it's probably your only phone. But don't panic, real bricks are rare and if you can get back into recovery you are usually fine!
HPTesla said:
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache, but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search. Hope this helps.
Click to expand...
Click to collapse
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
justsomedude23 said:
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
Click to expand...
Click to collapse
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
HPTesla said:
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
Click to expand...
Click to collapse
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
justsomedude23 said:
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
Click to expand...
Click to collapse
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
HPTesla said:
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
Click to expand...
Click to collapse
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
justsomedude23 said:
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
Click to expand...
Click to collapse
Good stuff man, glad to hear it and you're welcome!