Related
Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin
msticlaru said:
Alright.. This is a new one for me.
I have read almost all the threads on the incredible vibrating 3 and 5 times while booting on XDA and incredibleforum and tho the problems are similar they are not the same so I am unable to find a fix.
I have rooted the incredible , both the amoled and the SLCD version half a dozen times each and am pretty familiar with all aspects of it.
The setup...
Stock Dinc SLCD running latest OTA. totally 100% stock. This is my wifes phone, and she wanted me to root it.
I used Unrevoked 3.3.
The unrevoked process went perfectly. I plugged in the phone, hit "start" , unrevoked did its thing. It rebooted the phone, did what it does.. said "waiting for reboot", it rebooted fine. It said "this has been a triumph!" and then it said it was uninstalling unrevoked processes, then it rebooted the phone again. It did its hboot thing one more time, screen said "doing preboot sequence" it sat for a sec and then said "done!". The incredible vibrated 3 times and the screen was black.
I thought that was odd, I disconnected the USB cable and rebooted the phone (had to battery pull). when i pushed the power button it vibrated 3 times and nothing happened.
I pulled the battery again, held volume up and power , it vibrated 5 times and had a black screen. Battery pull, held optical button and power, vibrated 3 times and black screen.
This is where I sit.
I did nothing more than run unrevoked 3.3.. that is totally it.
when i "boot" the phone and get the 3 or 5 vibrations, and then plug the phone into the PC, the device manager says "qualcomm CDMA device" under unrecognized devices.
I have read that this is some sort of diagnostic mode, but I dont know anything about that.
Let the troubleshooting begin
Click to expand...
Click to collapse
call for a refurb. I had it happen twice.
ACD168 said:
call for a refurb. I had it happen twice.
Click to expand...
Click to collapse
I have a refurb sitting next to me lol. I wanted to root the old one so that I could do a backup and then restore that backup on the new phone. Wife saves pictures and videos to the phones memory (i know) so i would like to recover this if possible.
Also, it seems like this is something that has to be recoverable. Some sort of software is telling it vibrate 3 or 5 times. I am still doing research on this
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
For referance. I just 5vibed my last inc last week, i know all about it.
k_nivesout: oj + power boots fastboot
For the OP, your device is now in qualcomm diagnostic download mode. Hence qualcomm devices in device manager.
To date this is still a none recoverable issue. NO ONE has ever recovered from this.
Good news is if your still in warrenty VZW will send you out another one for free over night. Just call Tech support directly. Just tell them your phone vibed 3 times and shut off. They'll have you do some things to it over the phone. If what they have you try dosn't work, they'll send you one out over night.
Hope this helps a little and hopefully this will save you from countless hours researching. Took me three days, before I realized I had been beaten, lol.
k_nivesout said:
Well if you're trying to get into hboot you need to hold volume down and power, not volume up. Also not sure what trackpad+power does, I do know you can basically do the same thing as a battery pull by pressing volume down + power + trackpad. Have you tried booting the phone up normally too?
Click to expand...
Click to collapse
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device
msticlaru said:
ive always used optical key plus power to boot into hboot, volume down and power works too, but ive alyays just used optical key (easier to press)
hwoever..
volume up + power - 3 vibrates
volume down + power - 5 vibrates
optical key + power - 3 vibrates
and power alone - 3 vibrates
with all of these, the screen is always black
When i plug in the phone after any of these scenarios, the PC recognizes it as Qualcomm CDMA device
Click to expand...
Click to collapse
Wait, wait, wait just a minute. i wanna talk to you in private. check your pm
msticlaru said:
The 3 vibrate brick - Please Help {SOLVED}
Click to expand...
Click to collapse
Glad I could help you fix this. Don't forget to post what we did to solve this so others can learn from us
This is written for the HTC incredible, please ensure you get the proper ruu image for your particular phone. For example, the HTC wildfire will be PG76IMG.zip, not PB31IMG as I have written below. the rest of the steps are applicable to all HTC phones.
Click to expand...
Click to collapse
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download (see above comment)
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about
Nicely done! I've never encountered this issue but I'm remembering this for future reference just in case.
Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....
nate2830 said:
Is that just the stock ROM? I had this problem a few months ago, unrooted through Hboot using the stock image placed onto the SD card.....it never fixed the issue though, the phone would still not recognize the SD card once booted but since I was unrooted I could at least return it.....
Click to expand...
Click to collapse
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.
wildstang83 said:
Yes, this is the stock image method.
nate2830, your case is more typical because your phone was in full-blown Qualcomm Diagnostic Mode. Your device did this because you lost eMMC to corruption. OR you hade hardware failure.
The OP's device '3 Vibed' because when they had rooted with unrEVOked the wrong recovery for there device was installed.
A device with version 0002=Amoled must have CWM Recovery version 3.0.0.5
A device with version 0003=SLCD must have CWM Recovery version 3.0.0.8
If your device is not set-up like above, I highly suggest getting it there now.
Your device has a higher chance of "5 vibe" brick otherwise.
I am led to believe this is the case for our OP do to immediately after root (well actually during the root process if you will) they lost all screen function and the screen would not light. This meens of course: wrong recovery for the device. Also in there post above They had mentioned that Device Manager mentioned Qualcomm CDMA Device. Had there device been a total loss they would have seen Qualcomm CDMA Diag in Device Manager.
We were able to save the OP by doing what we call a 'Blind Recovery'. One must know the steps to take and how long to wait between those steps. Without being able to see the screen. Doing the dougpiston PB31IMG wipes the faulted recovery and reverts back to oem recovery which brings back phone screen function and the device it self.
End result being a device that
A) Functions properly that is now stock s-on ready to root again or whatever
B) Is now s-on with stock image and no trace of ever being rooted that now can be sent back to VZW for warranty replacement.
In any case, if you ever find yourself with a device with a screen that won't light, always try the steps above in this thread.
Things that are important to know:
1. Your devices Hardware version (Reference Above)
2. The md5 sum of ANYTHING your about to flash to your device. Test this after its on your SD Card with any md5 checker for best results.
3. If anything your about to download and flash does not have a posted md5 sum, ask the dev to please post one for verification.
4. A '5 vibe' is 'non-recoverable' and is generally 'hardware related'
5. A '3 vibe' is generally 'software related' and can be recoverable 'most' of the time. We must be careful how we proceed to take action to be succcessful.
I hope that the OP and I have saved someone from a future headache.
Click to expand...
Click to collapse
Oh sorry!! Thought it was a similar problem, but had a feeling it wasn't since the stock image didn't resolve my issue. Thanks!
My DINC was suffering from the 5 vibe syndrome. If I used it for anything that stressed the system or even used the phone for a few minutes it would result in a reboot that ended with a black screen, 5 vibes, and the indicator flashing green. At first I could pull the battery for a few minutes and it would recover. Eventually I ended up putting it in the freezer for a bit to get it running again. This progressively got worse until it was nearly unusable. Then I stumbled upon this thread..
http://forum.xda-developers.com/showthread.php?t=982454
Turns out mine was a hardware failure as the processor's BGA grid was failing. I heated the processor and now have a fully functional DINC. I had nothing to lose by trying this as I bought it second hand and didn't want a fancy paperweight on my desk.
Thanks guys, for helping me out with a 3-vibe brick i just had for no reason at the gym today. Was listening to music, texting, working out. All of a sudden, music stops, phone completely unresponsive. Battery out, 30-second wait, restart gives me boot-screen boot loops. Volume up + power gave me a 3 vibe brick.
Thanks to you guys, I discovered that i could get into hboot, boot into recovery from there, do a full wipe, reflash of CM7.0.3 and get the phone to start again. However, that's when the next BIG PROBLEM started. Screen went to sleep while restoring apps from the Market and now when i press the power button, the soft buttons light up but the screen doesn't. This is just super-duper to have problems like this on the same day I was telling a friend that I wouldn't trade this phone for anything else VZ has right now. Anyone have any advice?
PS - The only thing I did today besides "normal" use, is i updated Handcent and changed the LED flash rate.
msticlaru said:
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about
Click to expand...
Click to collapse
Sounds good, I'm hearing a RUU will work just as well?
This got my phone to turn on, but now im in a boot loop. How could i fix this? I appreciate all the help.
I actually recovered from a 5 vibrate error. I had flashed the leaked GB over a stock sense without doing a wipe and got stuck in a boot loop. Every time I tried to either power up into hboot or recovery (- vol and power, or + vol and power) I would get 5 vibrations and then a blank screen. If I tried to power up normally nothing but boot loop after the white htc screen. So I just kept trying to get hboot to load and then after about 5 tries it worked and I was able to get into recovery and flash a backup ROM. I still have problems getting hboot to load properly and it appears its a problem with how hard I press the volume keys. If I press it too hard I get five vibrations followed by the blank screen and it still takes a number of tried to get it to work right. Getting into recovery from ROM Manager is no problem it works flawlessly and I can flash ROMs with it no problem, just have problems when I manually try it. Otherwise the phone works great.
Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.
k_nivesout said:
Well if you're doing volume up and power I believe that puts it into a diagnostic mode where it vibrates three times (I think) and flashes the led. Also, I'm not sure how the pressure with which you press the button would matter, I'd think it either recognizes the button press or doesn't.
Click to expand...
Click to collapse
Like I said it does it with the - volume and power combination too, + volume and power used to go straight into recovery bypassing hboot.
Its not so much the amount of pressure but the length of time I press the buttons, if I hold them too long I get the 5 vibrates, if I press them both then quickly relase them the phone will usually boot normally into hboot but not always. The button psuhing could all be coincidence and the phone just randomly works right after so many tries so I don't want to mess with the phone too much as I'm sure that eventually it will stop responding at all some day. I've never had problems flashing through ROM Manager so I will just use this and skip trying to do anything manually.
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
Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.
re: recovery-root issues
Triplingcs said:
Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.
Click to expand...
Click to collapse
Since you seem to be having multiple issues with your phone your best bet
would be to Odin flash the stock official Tmobile firmware/rom for your phone.
You can download it from http://SamMobile.com .
After Odin flashing the stock firmware, use CF-Autoroot to root the phone.
Once it's rooted, you will need to Odin flash a custom recovery like TWRP
or CWM.
The stock official Odin flash firmware at Sammobile.com includes Odin
in case you need it.
You can try other ways to fix the problems you are having, but you will
most likely be wasting your time and effort and will need to Odin flash
the stock official firmware in any case.
Good luck!
Are you on KitKat? Kingo doesn't seem to work with 4.4.2. I tried the same thing- pulled the battery and got to download mode, then rebooted and used cf autoroot and have no problems. Good luck.
Sent from my SM-N900T using XDA Free mobile app
Triplingcs said:
Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.
Click to expand...
Click to collapse
I actually JUST had this same issue. Thank God further research in another post helped me out. I took these steps:
1. Pull the battery
2. Wait for about a minute or so
3. Reinsert battery
4. Hold volume down + home + power button
5. A warning message will come up (forgot what it said) but choose the 2nd option (that you don't want to continue)
6. Phone will boot normally as before
I rebooted the phone again and have no further issues. I don't know if it is actually rooted (at this point, I don't care...haven't actually checked). I'm just happy this 3 hour ordeal is over!
Good luck!
Firstly, yes, I am sure that the info that I need is on here somewhere, but I have spent the last hour reading threads and I am not a developer and I cannot tell the difference from a soft brick or a hard brick or a boot loop.
Also almost all of the tutorials to root / unbrick involve enabling USB debugging on the phone first, but I can't boot my phone to do this anyway....
So, I got 2.19 OTA update and installed it normally. Phone is not rooted, totally stock 550ML WW model.
But in the last update I got a few bugs so I wiped the cache from recovery mode by following a tutorial, no problems and the bugs went away. So I decided to do the same this time....
I got to the boot menu OK and selected Recovery Mode, then got the Error / sleeping droid screen, so I tried to hold power / vol up to get into the recovery mode and the phone turned off. It was at about 35% battery and plugged into the charger so I'm pretty sure it wasn't a battery issue.
Now I can't get it to turn on / boot at all. If I hold the power button down it just vibrates once and does nothing else, same for vol up and power.... Is this some kind of brick?
Problem is I am going travelling for a month tomorrow and I can't be without my phone so I have to fix it in less than 24 hrs.
Can anyone help me without using terms like "flash image" or "sideload" unless you explain exactly what they mean?
Thanks in advance. :silly:
Can you press vol down and power and see if it turns on?
Sent from my ASUS_Z008D using Tapatalk
Vol down and power has done something!!
The phone vibrated twice and the led has lit up showing that it is charging!! Also I have the battery graphic on the screen.
Should I just now turn it on normally?
Sorry to sound so dumb but I really don't want to screw this up...
Thanks for answering by the way.
You can try to boot like normal but my guess it would still be stuck with the android logo. Happened to me when I rebooted my phone while wiping cache.
Anyway go to the link and follow his instructions. Let me know if there's any problems. Cheers!
http://forum.xda-developers.com/showthread.php?t=3101556
Sent from my ASUS_Z008D using Tapatalk
i experienced shutting down during wipe cache.bad times then.i resolved with this : forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
remember for bootloader press power+volume up.when it vibrates release power and keep pushing volume up.you should be in booloader.scrolling with volume up volume down you can choose recovery..may will be wrote installing update and then an error message.just press power and immediately after volume up for a bit.you should be in recovery.if you reached recovery do a wipe cache.REMEMBER IT CAN TAKE 15-20 MIN TOO ! check if it power on.
if you still cat access bootloader...for me you have to use warranty.say to asus you just did an ota and then phone bricked.dont use the word brick say just it won't power on.approach is the key in this cases.approach to them like a total noob.call them,don't email them.if you are young,let someone older to talk,a relative or someone like this and give to him a text to follow.is difficult to think a noob thinks to do some difficult moves as root,unlocking bootloader....they think "this is a noob.he never thinked to root or modify phone" .so they can think your seller sold to you a rooted device (updating with root takes to brick,bootloop etc.) and so they will give to you a new phone.if it not power on they cant see if it is rooted or not
good luck bro
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Overandout said:
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Click to expand...
Click to collapse
happy for you :good:
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
HTC Desire 526G
I have problem like this ....cant fix it
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset) press power button to select, let it finish clearing /data/ and /cache/
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Still have problems
wassti said:
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset)
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Click to expand...
Click to collapse
i've done the procedure but unluckly i'm still having this problem, did someone fix the loop with this method? should i just wait for custom roms? :crying:
I had it happen to me after trying to root with just about every tool out there, mine would boot up but wouldn't go past the htc boot screen white background green htc. After I cleared the data a few times (at least 3) it came back up, try the procedure more than once. Also be patient and wait the full 10 minutes for it to come back up, sometimes it can be slow to load for the first time after this kind of wipe.
wassti said:
I had it happen to me after trying to root with just about every tool out there, mine would boot up but wouldn't go past the htc boot screen white background green htc. After I cleared the data a few times (at least 3) it came back up, try the procedure more than once. Also be patient and wait the full 10 minutes for it to come back up, sometimes it can be slow to load for the first time after this kind of wipe.
Click to expand...
Click to collapse
Try to root with "PhilZ Recovery by Ajit", search on google, i don't remember where i have download it, but it is an .exe file.
After you install it on your computer, you select USB debugging, and connect your phone to the computer, the rest of the process is auto.
After the installation process, the phone will autoreboot in recovery, here you will select ---> Advanced Function---> RE-root System (SuperSU).
After that, reboot, and install SuperSU from GooglePlay.
Success.
Root without boot loop (you may want to wipe Dalvid Cache before reboot after selecting root).
I hope this works for you ( it worked for me HTC desire 526g ).
Have a nice day.
IF you dont find the Philz, contact me, i wil send it to you.
Philz Recovery by ajit is designed for devices using the Mediatek processor; Sadly our 526 (no g, no +) uses a qualcomm processor. I do not recommend anyone to attempt to use "Philz recovery by Ajit" to attempt to root their HTC 526 as at best it will fail and at worse it will flash a non-compatible recovery and turn your device into a hard-brick.
wassti said:
Philz Recovery by ajit is designed for devices using the Mediatek processor; Sadly our 526 (no g, no +) uses a qualcomm processor. I do not recommend anyone to attempt to use "Philz recovery by Ajit" to attempt to root their HTC 526 as at best it will fail and at worse it will flash a non-compatible recovery and turn your device into a hard-brick.
Click to expand...
Click to collapse
I know...i said it is for HTC 526G.
Yep, I know you said it; just needed to clarify for other members so there is no confusion if someone comes here from a google search or what not
This forum is for 526 only, not the g or +
Bricked
I tried to wipe, but it still staing on htc screen...can someone do a backup or something and send me a link and reply me. i need it
sorry for bad english
I have the same problem please help us
emwakishi said:
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
Click to expand...
Click to collapse
I've exactly the same problem... does anybody have a rom for this model?
emwakishi said:
Hi guys, months ago i rooted my HTC 526G with Kingoroot. I later tried to update the software over wifi. It updated but in restarting its now stuck in boot screen and sometimes goes into recovery by itself. Is there a way I can revive the firmware? Any help appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/chef-central/android/htc-desire-526g-bootloop-solution-t3241938
solve it by flashing rom using re recovery mode
I also got 526g+ totally finished only restarting I asked so many mobile repairing places no luck at all
PodolskiMeki said:
i've done the procedure but unluckly i'm still having this problem, did someone fix the loop with this method? should i just wait for custom roms? :crying:
Click to expand...
Click to collapse
Similar bootloop condition HTC 526g
wassti said:
Warning/Disclaimer: This will erase everything you have on the phones internal memory. (if you have play store set up right, you can just log back in afterwards and it will pull all your data/apps back, however if you don't, make sure to backup any contacts, data, ect that may be on the phones storage before attempting this) (then again, if you were already trying to root, you should have had everything backed up already anyway )
Charge the device to at least 50% (or an hour or two at least if the battery was completely dead)
Hold the Volume Down Button, Press power button, keep holding the volume down button
Phone should boot into HBOOT or Download mode,
use the volume up and down buttons to highlight Recovery Mode
press power button to select Recovery Mode
Phone will reboot with a red triangle icon, press all three buttons at the SAME time (vol up, vol down, power)
use the volume up and down buttons to highlight Clear Data (Factory Reset) press power button to select, let it finish clearing /data/ and /cache/
Once this has completed, Pull the battery out, let it sit for like 30 seconds without the battery
Put battery back in
hold power button for a while until it vibrates, release power button
let it sit at the htc boot screen for 10 minutes phone should eventually move to the verizon boot screen (if it goes over 10 minutes on the htc screen, try procedure again)
Post here if you have any trouble.
Click to expand...
Click to collapse
My phone was also rooted using kingroot. I received an OTA update and I downloaded it. Once the download was complete, the phone restarted and got bootlooped. Occasionally, it goes into recovery. I tried factory resetting it several times as mentioned in the solution. But each time I turn the phone ON again after factory reset, it is looping. Its not stuck at the boot logo. Instead it reboots automatically and in some cases to recovery. So the wait-for-10-mins thing is not working for me.
1. I received a stock ROM from the Russian section of XDA. Will flashing that ROM using the stock recovery using "install update from SD card" help me recover my phone from bootloop?
2. Will flashing the stock ROM unroot the phone? Presently, even after the factory resetting, "check the software partition" option in recovery returns a message "error - system has root". So I was hoping that unroofing might fix the problem. Will it?
3. If the above method fails, is there any other method? Like flashing a custom recovery or flashing a custom ROM etc?
Please help me fix the phone. Thanks in advance.
I am experiencing the same problem and have tried everything to avail, will this devise ever work again its still stuck with a white screen and green HTC
negomo said:
I am experiencing the same problem and have tried everything to avail, will this devise ever work again its still stuck with a white screen and green HTC
Click to expand...
Click to collapse
Hey negomo. I just fixed the phone yesterday. It seems that installing an OTA update while the phone is rooted can result in a bootloop or bricking(as in my case). I fixed this issue by flashing a stock ROM of the HTC 526g which I got from another Russian forum in XDA. Anyway I am posting the link of that stock ROM here.
( I am not allowed to post link. So please delete the spaces to get the actual link)
h t t p s :// yadi.sk/ d/gNKBahgZiwGmo
Once you download it do the following procedure
1. Copy it to an SD card and insert the card in your phone.
2. Press power button+volume up key button to enter HBOOT menu (while turning on the phone, press power and vol up button instead of power button alone)
3. Choose recovery option and press volume down to enter
4. Press power button once to enter recovery
5. Choose "install update from SD card"
6. Wait till it finishes installation
7. Wipe cache
8. Reboot phone
PS: I had already done a factory reset from recovery menu. I don't know if that had helped.
This will bring your phone back to life. Give around 10 mins for the first boot.
I hope I was able to help you.
Hit thanks if I did.
how to know my device 526g or 526
---------- Post added 24-06-2016 at 12:05 AM ---------- Previous post was 23-06-2016 at 11:51 PM ----------
https://www.imageupload.co.uk/image/ct0U
thx you are pro ??my problem solved ??