Related
Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .
OK.
I will put in a detailed info about what happened.
A week back, my wildfire's touchscreen started to function abnormally.
I was rooted and on Cyanogenmod 7.0.3
So, I flashed the phone with DK custom FROYO to make it look like sense so that the warranty is not void and took it to the HTC store.
They replaced the touchscreen for a flat fee (It was water damage according to them. But the phone was never used in wet conditions nor exposed to water)
But anyway, the phone was working fine when I brought it home from their store.
Then I flashed CM7.0.3 again.
And everything was working fine.
I OCed acc. to CM's settings to 652-352 Mhz.
And left the phone to charge in charger overnight.
When I woke up, the phone was off and there was just the red LED light blinking.
I tried to boot it again, but nothing works.
Pressing the power button does not do anything.
The phone still boots into recovery. At times.
I don't know what makes it boot into recovery. But at times it does, at times it doesn't. (Right now it's not booting into recovery no matter what I do)
Just the red LED keeps on blinking.
Please help.
I am not familiar with pushing commands onto the wildfire since I use a mac.
Please suggest any methods. If they involve using command line, I can use my windows PC for that. But please give a how-to of length enough for a noob ) ) to understand.
Thank you.
Pulz
EDIT :
I got to boot into recovery once. Tried to reflash CM7.0.3
It came to "Installing update" and then failed to go further.
Tried to install DK Custom Froyo 4.5
And it went to opening package and then failed to go further.
Now entering into a panic mode !
Red light blinking generally occurs when phone is hot and plugged in to wall socket. Is it so at that time ?
Unplug the charger or usb. Remove the battery and reinstall the battery. Try to boot into hboot mode (volume down + power) or fastboot mode (trackpad + power) . If your phone can boot into hboot/fastboot mode and has no restarts or power offs, then I think you can solve it.
Try to clear storage from hboot menu. Or factory reset from recovery once you enter it. If still it is not solved, try using "pc49img" method of flashing an RUU from the hboot menu. Hope it helps. Shouldn't help if there is hardware issue.
Sent from my Blade using XDA App
hye another noob here running on cm7.
actually i have the similiar problem my wildfire start rebooting over and over again but the cause is different.
this problem happen after i want to know what class my micro sd is.
what i do is i go to settings>storage>unmount sd card.
so after knowing the class were i insert back the card then the problem happens.
my phone start to crash then cm7 logo appear after that i enter my pin no so brought me back to the home screen after few seconds the logo appear again so i have 2 repeat the same steps...
this happen many times what i do is i remove the battery wait few hours then turn back on..
so help me if someone have the similiar problem and solutions.. thanks!!
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Paulius Sirv said:
Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*
Click to expand...
Click to collapse
Did u wipe the system file and data before flashing new ROM?
redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
Ive tried your technique, few times actully. Phone does not want to show any indication of life. I might have flashed the rom on low battery I just found out that the cable I was using to flash roms ir damaged and does not function properly. Now Im using a new power cable to charge the device but still, no signs of life.
Thank you very much for helping
justinchao740 said:
Did u wipe the system file and data before flashing new ROM?
Click to expand...
Click to collapse
Revolution HD has a aroma installer, I wiped it during instalation process
Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Paulius Sirv said:
Revolution HD has a aroma installer, I wiped it during instalation process
Click to expand...
Click to collapse
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand
sayad1 said:
Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand
Click to expand...
Click to collapse
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).
Paulius Sirv said:
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).
Click to expand...
Click to collapse
Wc reply if this method work for you
redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
I left my phone to charge overnight and the LED light came on (Its a really good sign). At first it was flashing orange, later it was only orange and now its green, so that means that my battery was fully drained. However, I tried holdin power + vol up for atleast 3-4 minutes but nothing happened except that the LED light is not greeen nor orange anymore. If I connect my phone to a pc, in the device manager "Qualcomm HS-usb qdloader 9008" shows up for 20-30 seconds and dissapears, after few secs it reappears again and so on. I was looking for a solution for a few hours and I think I found a decent tutorial how to unbrick it but Im not able to find neccesary firmware for my phone because I dont know my CID (link: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/). Any other ideas?
BTW, thank you very much for trying to help
I've never seen these "unbricking" guides work on this device. If you can't get to at least bootloader, you are probably looking at JTAG, new motherboard, or new phone.
Really, your best bet is to keep playing with the button combos with the charger attached and unattached.
I just wiped my phone with TWRP using the "advanced" settings and ticked everything. Obviously not a good idea as I think I have wiped everything including the ROM from my phone. Any idea how to get it going again? It just goes to the "Sony Xperia" screen and stays there when booting. I'm not sure how to get back into TWRP (i used to get there from a utilities app that restarted the phone into recovery). I have TWRP backup on my computer before I did the stupid thing...
Thanks for any help!
I've tried to flash from Emma and and Xperia Companion but I can't enter Flashmode (hold the volume down button and connect to computer). It just automatically turns on and shows the Sony/Xperia screen and the LED is solid RED.
I let it run down over night and still unable to enter Flashmode.
I assume TWRP is still there as it was the program that wiped the phone. Any ideas how I can get into TWRP?
The computer does not recognise the phone either. It was rooted and had an unlocked bootloader before it happened.
Thanks!
Hold power down and press power button. Release power button when phone vibrates but keep holding vol down until you see twrp logo. If you don't see it after maybe 10 seconds. If nothing happens you can try pressing power button and when you see led light keep pressing or holding (try both) vol down. If that doesn't work then you can try flashing with flashtool. You can check my thread for downloads and instructions
col320ce said:
I just wiped my phone with TWRP using the "advanced" settings and ticked everything. Obviously not a good idea as I think I have wiped everything including the ROM from my phone. Any idea how to get it going again? It just goes to the "Sony Xperia" screen and stays there when booting. I'm not sure how to get back into TWRP (i used to get there from a utilities app that restarted the phone into recovery). I have TWRP backup on my computer before I did the stupid thing...
Thanks for any help!
Click to expand...
Click to collapse
In sim card slot there is a small red button. Hold it down with toothpick or paper clip until you feel three vibrations. That will shut off your phone.
Now you can try Flashtool or Emma.
Thanks so far ... here is an update.
After letting it run down overnight it eventually let me get it into flashmode. Xperia Companion doesn't work (unlocked) but Emma is trying to work. It has taken a few hours to download the software as the phone only stays in flashmode for about 30 seconds but it was able to eventually download the software. Now it is trying to load it but it gets to 11% and the phone goes out of flashmode (but automatically re enters it without me doing anything) and the cycle continues. Is there any way to force it to stay in flashmode?
I've tried the suggestions above to get to TWRP but nothing seems to work.
I can think of 2 reasons. Either emma is broken (never used it, can't tell) or your connection to pc gets interrupted by bad cable or broken connector. Why don't you try flashtool instead of emma?
col320ce said:
Thanks so far ... here is an update.
After letting it run down overnight it eventually let me get it into flashmode. Xperia Companion doesn't work (unlocked) but Emma is trying to work. It has taken a few hours to download the software as the phone only stays in flashmode for about 30 seconds but it was able to eventually download the software. Now it is trying to load it but it gets to 11% and the phone goes out of flashmode (but automatically re enters it without me doing anything) and the cycle continues. Is there any way to force it to stay in flashmode?
I've tried the suggestions above to get to TWRP but nothing seems to work.
Click to expand...
Click to collapse
Silly question, but did you recharge your battery after letting it run overnight?
PiixJu said:
Silly question, but did you recharge your battery after letting it run overnight?
Click to expand...
Click to collapse
I wiped whole storage few times as he did (Without letting it run overnight tho) and you can't charge your battery without system or recovery. If your battery drains in this situation you are SOL
yeah I think that is my problem. The phone won't charge and that's why it only stays on for 30 seconds before losing connection.
Can I charge the battery out of the phone? I know it a pain to pull out ... but I've done it before as it needs changing every 12 mths or so.
Not sure about that. I mean there has to be a way to charge it outside phone but you would need special equipment since you can't just use random charger. Since you said you charged your batteries before you could try to use one of them and hope that they have charge in them for flashing. I saw that @munjeni has a lot of experience with this phones hardware so you could try and contact him and ask if he knows about contact points on motherboard for charging
Ok. Got it going again eventually. Not sure exactly what I did that made it work but FYI these are the things that I did that seemed to help:
Charged it on my ASUS tablet charger today - seemed to do a better job than the other charger I was using (it was a Nokia). It seems to hold a very small charge but was not charging the battery properly. Hooked it up to Emma which had already managed to download the software and put the phone under my laptop (trying to warm the battery to squeeze everything our of it). 355 seconds later it had copied the software and the phone was able to turn on normally again. The phone was getting to about 60% of the software copied across before I used the ASUS charger and the heating the phone technique.
BTW I couldn't get flashtool to work. It recognised the phone but stopped saying USB debugging was off.
Thanks for everyones help!!