I have a Desire HD, rooted with Visionary, ENG S-OFF, Radio S-OFF, Super-CID and SimUnlock'd, I installed ClockworkMod using ROM Manager and chose to boot into recovery, the phone now doesn't boot whatsoever, when turning on it vibrates 3 times and the amber LED flashes continuously about every second. If I hold down and press power, the phone vibrates 5 times and a green LED flashes instead, but nothing on the screen. Back and Power does the same as turning it on normally. When plugged into USB, my computer searches for the Qualcomm CDMA Technologies MSM driver which it cannot find...
Does anyone have any idea how I can get the phone into recovery mode, fastboot mode, or any other mode where I can flash a RUU?
Thanks, Jordan.
:::im not sure about this, and whatever happens, im not responsible, this is entirely your decision:::
But if i was in your shoes, given that it doesnt want to open at all but just flashes (the LED), ... , i would take the battery out and try again.
But if this keeps happening, then you should sent it to HTC.
Take your battery out, then try and flash into recovery mode
If you get into recovery mode then either install a new Rom or if you backup your Rom restore it
Sent from my Desire HD using XDA App
Taking the battery out and putting it back in does nothing, left the battery out for hours, nothing. No way to get into recovery...
If u flashed a 2.x.x.x version of CWM u could try use the bug thats now corrected in 3.x versions.
By taking the battery out then plugging USB in to charge and replace the battery. that used to start my DHD into recovery. if u flashed the 3.x.x..x CWM it wont have that bug.
^it's actually a feature which was removed...^
Sent from my Desire HD using XDA App
As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).
b_bhavu said:
As long as your DHD vibrates, shows LED.. it is not bricked if I am not wrong. Wait for some senior member to reply your question. You might need to erase recovery via fast boot (just a thought, I am not sure).
Click to expand...
Click to collapse
Which of course works only if you can get into fastboot.
@OP: If you connect your phone to the computer and turn it on, does the computer recognise it?
as he said, windows searches for "Qualcomm xxx"-drivers.
i had a similar issue with my nearly-bricked hd2 some months ago.
but you know: hd2 and dhd aren't really the same when compared on bootloader level
DN41
Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?
JordanT92 said:
Can't get into fastboot mode because pressing down and power just makes the phone vibrate 5 times and show a green LED. The phone failed to boot after installing CWM, which was v3 anyway, but obviously isn't present if it fails to boot into recovery in any form. I sent the phone away with Vodafone to get repaired under warranty, but they sent it back today saying it's water damaged and they won't go any further into fixing it. My house mate dropped the phone in the bath once, it worked fine afterwards, no problems whatsoever until now. It's obviously not water damage that caused this, but vodafone refuses to take a look... Am I gonna have to resort to a third party repair center? or replace my friends damn expensive phone... Any ideas?
Click to expand...
Click to collapse
does your phone carrier offer extended warranty? as in full coverage?... basically i did this once.. my gf got pissed (as they do).. and basically tossed her phone towards me lol missed completely.. bounced off a wall, then off a metal heater, and then the floor.. thus .. screen completely broken.
We went onto our carriers website, added a 3 dollar a month full coverage warranty (12 month commitment). and after 2 weeks sent it in .. fully repaired 2 week later ...
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...
Here's what happened to my (not rooted) G3
The phone has been weird for a couple of days, rebooting randomly once in a while, but working fine whenever plugged onto a power source. Google told me it could be a battery related issue, so I bought a new battery online (and I didn't get it yet).
This morning the phone entered a boot loop, even when plugged in to any power source. Google this time told me I could put the phone in "download mode", then restore upgrade errors via LG PC Suite. I try to do that, and the phone actually goes into download mode, but I'm not able to restore upgrade errors with that ugly piece of software because it keeps "losing" my phone usb connection. I unplug and plug it back in several times, the phone seems to make progress on the firmware upgrade screen but I see a red ASSERT error on my phone at around 15% of recovery.
Now whenever I turn on my phone and try to put it on download mode keeping the volume up button pressed, the screen will just go straight into firmware update, warning me not to unplug the usb connection, even if the phone isn't plugged. I'm able to start a restore but again the usb issue comes up and the phone is totally frozen and stuck to that firmware update screen. If I want to turn it off I need to remove the battery.
I'm doing this because I would love to recover some data from my phone, otherwise I would have done a hard reset or a flash of some kind
Please someone help me before i throw this piece of junk out of the window
Nobody able to help me in any way?
bump =(
Contact LG in this case. Might be faulty NAND memory. If it is then it will probably be impossible to get those files back...but they will replace it and fix the phone. (if it is under warranty that is...)
BTW if you take out the battery during flashing...you may hard brick the phone...then you're technically more fked
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem