I've got a new (or refurbished, can't tell) Desire from HTC customer care yesterday, i rooted/s-off, and was playing with it withoout any issue. Then i booted in fastboot mode, trying to flash a custom splash image, but fastboot got stuck on the message "waiting for device". I waited for a while, then chose the option "reboot bootloader". Tried using fastboot again, but still the same. Tried to reboot into recovery, but the phone was stuck at the alpharev splash screen. I waited some minutes, pulled off the battery and put it back in. The phone doesn't power on. When plugged to pc or AC, the led does not turn on. I also tried removing the sim card, the sd and the battery and plugging it again to AC, but it's still not working. Seems totally dead. Is there something i can try before sending it to HTCfor repair (again!!!)? Will they be able to tell that the phone was rooted even if it is practically impossible to boot it?
did you try to press the power button and the down volume key for about 20 seconds? sometimes that kicks it on. Also htc will not be able to tell if it is rooted or not. I sent one in for repair that was s-off and a custom rom and the same one came back fixed and reflashed with proper rom. I had to s-off and root again. Hope this helps.
I tried holding vol- and power for about 30 seconds twice, but nothing happened. I'll send it for repairs tomorrow. Thanks anyway for the advice.
Sorry your having problems. Good luck.
Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>
c4p3fi3rr said:
Sent it to an authorized lab for repairs... It took 3 weeks the first time... Another 3 weeks without my phone! >_>
Click to expand...
Click to collapse
Rule #1 when rooting and flashing..... always have a back-up phone. (I keep 3)
I defy you to be bricked the 2 days. Put in office the night the morning was completely blocked with the LED flashing green. I reinserted the battery and then turn on nos. I installed cynogem 7.1. By connecting to a PC is recognized for 2 seconds and then disconnects. I tried mcgiver mode but nothing is ever disconnected after 2 seconds. The battery is charged.
What can I do? help me please
Sorry for my english
Help me please
Try installing Froyo Official [don't use custom ROM until you get back to normal state]
and as you are saying, it disconnects after 2-3 seconds, probably your battery is done [not sure but you may check another battery]
so Install Froyo Official 2.2 [from Defy Android Development section] & hopefully you'll get your phone back in action.
PS: Defy can't be dead as far as it got locked bootloader
I have tried with other battery on a shop but don't turn on.
Try using some Universal Charger to charge your battery [or buy new one]
otherwise Best option would be to try it on some other PC, or change USB slot but trying on different PC will be good.
Hey i am having a similar problem. i just put CyanogenMod 7 on my defy and went to install the Google apps. All went good then rebooting i am now stuck on the Motorola logo. The led lights are not coming on it just sits there frozen. i have tried getting it into the boot menu and to use RSD lite but nothing is working. Please help as if freaking out.
1. Pull the battery, wait, and reinsert
2. Push and hold Volume Down button, tap the power button, while still holding the volume down. (This will boot you into the stock recovery)
3.Now, push both Volume Up, and Volume Down buttons to allow for more options than, just the triangle screen.
4. From Stock recovery, Wipe and Factory Reset.
5. Reboot once it is finished wiping
That's all I can say.
If still not work, head back to Quarx's CM7 thread & mention your problem there.
Just make sure you followed all directions properly.
PS: CM team have not officially released any ROM for DEFY, so this is MODs work, ask them further for any help.
Best of Luck
all good now after a hour of yelling at the phone i got boot loader to work.
Mr_hell said:
all good now after a hour of yelling at the phone i got boot loader to work.
Click to expand...
Click to collapse
Congratulations,
Take Care
Today i have tried with a new battery charced completely but the defy unplug from pc after 2 second no led.Help me please
Today the cell connected to pc has a white led but pushing the power and volume up is recognized in rsd lite as blank omap360 but starting flash at 67% the cell is disconnetted. Naturally the process fail .Help fo my defy please
So i was flashing a new AOKP rom with cwm 6.0.1.0. My phone dropped and the battery fell out. it only dropped like one foot, not enough to break just enough to cause the back to pop off and the battery to fall out. Now my phone is a complete ****. It didnt turn on at first. Then it finally did but cut off after about five minutes. Now it wont turn on. Occasionally you will see the battery charged logo that appears when your phone is completley off and charging. And occasionally it will start to turn on but never make it past the bootlogo. neither is enough time for me to try and flash or wipe or use adb to restore. It seems to be somethingw ith the battery. There is the smallest crack in the screen so i cant return under warranty. Please say someone knows whats wrong
I believe (and someone with more knowledge would have to correct me if im wrong) but if the screen is able to turn on then that means that you are completely screwed. Your phone isnt hard bricked but soft bricked. If you can get into the bootloader then you should be able to use fastboot commands or the toolkit to get yourself back to stock or flash a recovery and new rom onto your phone.
Dri94 said:
So i was flashing a new AOKP rom with cwm 6.0.1.0. My phone dropped and the battery fell out. it only dropped like one foot, not enough to break just enough to cause the back to pop off and the battery to fall out. Now my phone is a complete ****. It didnt turn on at first. Then it finally did but cut off after about five minutes. Now it wont turn on. Occasionally you will see the battery charged logo that appears when your phone is completley off and charging. And occasionally it will start to turn on but never make it past the bootlogo. neither is enough time for me to try and flash or wipe or use adb to restore. It seems to be somethingw ith the battery. There is the smallest crack in the screen so i cant return under warranty. Please say someone knows whats wrong
Click to expand...
Click to collapse
Can you get to the bootloader? Turn your phone off, hold down the Vol Down and Power button.
If you get to the bootloader, you can flash your ROM again and you'll be fine.
the7thson said:
Can you get to the bootloader? Turn your phone off, hold down the Vol Down and Power button.
If you get to the bootloader, you can flash your ROM again and you'll be fine.
Click to expand...
Click to collapse
no ic ant boot into that. i already tried, it wont stay on for no more than ten seconds no matter what i try to boot into. when plugged into the computer (without battery where it should install the omap driver) it just connects and disconnects every three seconds.
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
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!!