Related
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
same prob
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
Same problem as OP, and I can not get into download mode either. If I do as above, it still goes on booting .
saeidzzz said:
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
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 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 write 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 )
you are a life saver!
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
I thought I was going to have to factory reset my phone like other forums suggested and lose everything. Thanks to your suggestion I was able to get out of recovery reboot loop. Thank you!
Thanks for your help, you are a lifesaver lol! I saved so much money and time because of you. Have a great day
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
But how to enter recovery it still says set warranty bit recovery
i am facing problem with set warranty bit: recovery in samsung J5 model...
samsung j5 500f
i have the same problem when i flash twrp recovery..any solution ????
Ghats normal
Sent from my SM-N900T using XDA-Developers mobile app
My Fix
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
ulop3z said:
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
Click to expand...
Click to collapse
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Tmobilefan906 said:
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Click to expand...
Click to collapse
The phone is fine now, it was just stuck on the loop and spamming home was the only way out, its fine now I've had no problems and it boots up fine
This happens...
This happens to almost everyone at some point of time. There is no need to worry as you just need to flash recovery like TWRP or CWM. To shed some light on this issue... boot loops mainly happen when you uses the incorrect version of software with your ROM or stock firmware. By using youtube you can look at the videos of your phone model and find the recovery version number needed.
For anyone who has a Note 3 T-Mobile phone who is still stuck! I am willing to make a video to show how to fix this and provide all the firmware/version numbers + links in one bundled location to make it easier.
ALL PHONES ARE VERY specific... ONLY USE THE CORRECT FIRMWARE FOR YOUR MODEL PHONE
Again, if you have a Samsung Note 3 T-Mobile, model number SM-N900T and are still lost. Let me know so I can shot a video and bundle files needed.
---------- Post added at 08:44 AM ---------- Previous post was at 08:38 AM ----------
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), 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 write 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
Don't be scared by this... just choose the correct versions before blindly trying to install a ROM. Also, only use links from main sources if you dont fell like auditing the code!
Hi guys, sorry for might be late about helping you now years later... But recently I've found something interesting about fixing this issue.
*****
Fix: (100% working in Galaxy Grand Prime SM-G530H)
UPDATED: More detailed info!
# Before flashed Recovery or Root:
1. Root device using Odin or any other rooting known workaround.
2. Backup Recovery (optional), and Kernel using Rashr (available on PlayStore).
3. Flash Custom Recovery (TWRP), using Odin PC software or TWRP android app.
4. Flash backed-up Kernel.img file to Boot partition using TWRP install section.
5. Reboot system (It may take a few time to boot)
# After flashed Recovery or Root: (accidentally or without knowing)
1. Search online and download your exact Phone Stock Kernel.
2. Follow *before flashed* above ↑ from 3rd.
Bonus info:
Even after flashing TWRP, you might be able to Boot device yet, by going to TWRP → Advanced → Reboot system. (It bypass bootlooping to Recovery, while: “Set Warranty Bit : Recovery”).
That's all! Try at your own, then share it!
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,
I have received new zenfone 2 and it asked for software upgrade. After that it said it is optimizing applications and eventually got into reset loop with only showing ASUS logo. I have tried to get into recovery mode pressing the power and volume up and release on vibrate... nothing happend!!!
Now it vibrates every minute or so... but it even does not turn the screen on... just vibrating every now and then...
Please, help!
Zvika
Zvika Perry said:
Hi,
I have received new zenfone 2 and it asked for software upgrade. After that it said it is optimizing applications and eventually got into reset loop with only showing ASUS logo. I have tried to get into recovery mode pressing the power and volume up and release on vibrate... nothing happend!!!
Now it vibrates every minute or so... but it even does not turn the screen on... just vibrating every now and then...
Please, help!
Zvika
Click to expand...
Click to collapse
Power off completely, then hold volume up and power to get to bootloader. Press volume down until you get to recovery and hit power button. It should reset and then a android appears. If it then says error hold power and press up volume. You should get to recovery menu that way.
Wipe cache...
Reboot and see what happens...
ultramag69 said:
Power off completely, then hold volume up and power to get to bootloader. Press volume down until you get to recovery and hit power button. It should reset and then a android appears. If it then says error hold power and press up volume. You should get to recovery menu that way.
Wipe cache...
Reboot and see what happens...
Click to expand...
Click to collapse
I'm having the same issue, but no matter what I do the error stays on and if I hold the power and press up for too long the phone turns off.
chillpillv1 said:
I'm having the same issue, but no matter what I do the error stays on and if I hold the power and press up for too long the phone turns off.
Click to expand...
Click to collapse
Try tapping up volume 3 times but remember to let go of power at roughly the same time or 10 seconds later the phone will power off...
It just do not enter this recovery mode... no matter what
ultramag69 said:
Try tapping up volume 3 times but remember to let go of power at roughly the same time or 10 seconds later the phone will power off...
Click to expand...
Click to collapse
It just do not enter this recovery mode... no matter what.
After charging it all night, and having the battery icon, I have tried it once more. Now the screen remains black and the phone just vibrate here and there every minute - unless I turn it off...
i am facing the same problem. but my phone is not opening. its behaving like dead. when i press the power button sometimes its vibrate but noting on the screen. no charging logo while charging what to do?? please help !!!!!!!!!
Yes. this is the same with my device...
Anaxious Asheque said:
i am facing the same problem. but my phone is not opening. its behaving like dead. when i press the power button sometimes its vibrate but noting on the screen. no charging logo while charging what to do?? please help !!!!!!!!!
Click to expand...
Click to collapse
No solution so far.
Im having the same problem too
For wipe cache partition and hardware reset procedure, please see the following: http://www.asus.com/us/support/FAQ/1011956/
If possible, please send a private message to email below with case # N150638445 in the subject line. Please provide your serial number & if possible your build number (once you are able to boot) under Apps/Settings/About/Software information/Build number.
We would like to gather as much info as possible to help resolve any issues with ASUS Zenfone 2.
Sincerely,
Frank
ASUS_USA
[email protected]
Did anyone ever resolve this issue?
Mine is the same and won't boot up, just vibrates once and does nothing....
i resolved simply reflashing the old pre rooted firmware 2.19.40.18 and installing ota 2.19.40.20 with adb sideload after complete unroot with supersu.i forgot to uninstall xposed and this was the reason of my botloop after update to 2.19.40.20.luckily i had twrp so before reflashing i backupped all my stuff.that's it.you need to reflash droidboot,recovery,boot and system imgs from bootloader with the usually way.no other way out.hope you installed a custom recovery before loop,so you can backup
CenereZar said:
i resolved simply reflashing the old pre rooted firmware 2.19.40.18 and installing ota 2.19.40.20 with adb sideload after complete unroot with supersu.i forgot to uninstall xposed and this was the reason of my botloop after update to 2.19.40.20.luckily i had twrp so before reflashing i backupped all my stuff.that's it.you need to reflash droidboot,recovery,boot and system imgs from bootloader with the usually way.no other way out.hope you installed a custom recovery before loop,so you can backup
Click to expand...
Click to collapse
how did you do it ?
I have the same problem
---------- Post added at 12:33 AM ---------- Previous post was at 12:07 AM ----------
my device is in error screen, and with the dead robot.
Hi guys, please help, maybe some of you could do that for me... Problem is strange and I just did not find solution jet... So, I just can not power down my ZE551ML completly. Device is trying somehow to boot up, getting some kind of loop. First of all, phone came to me totaly dead - I have to plug it in to charger for 3-4 hours to ligh up notification led... After that it turned on normally. After first boot and setting things up, updates showed up. So I did update - for 4 times, OTA. It looks ok (now I have 2.20.40.90 clean, I mean no root or unlocked BL). But strange comes when I want to turn it off (power down) - device is shutting down, screean is going black and... bum! - the battery icon is showing up: emty for the very first few seconds, then it changeing to green (showing actually power state, I mean accu capacity), then device reboot itself and whole process starts over and over again... I can not stop it. Well, I think if the battery would be full, that could completly discharge it - couse is unstopable... I found, that when I press vol- when the battery is green, phone shuts off its screen, but after 20 seconds the process begins over again... i can boot it normally by pressing vol+ and power - it leads me to the bootloader manu, then boot normally - done. but it is very annoing... beside that phone is ok. Can someone help? BTW - I did factory reset from stock recovery, but it did not help...
hillvieira said:
how did you do it ?
I have the same problem
---------- Post added at 12:33 AM ---------- Previous post was at 12:07 AM ----------
my device is in error screen, and with the dead robot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I had the same problem. My solution was to unplug the usb charger. After that, the update was successfully.
on me Z007 I did a factory reset because my phone would not start and when it did it kept giving me messages about unfortunately this stopped and that stopped BBM, Zenui, google play store etc. Once i did the factory reset the phone worked again but I had no data so I thought I would just restart. Now all I get is ASUS and the spinning wheel. any suggestions??
Hello, I own model Asus Zenfone 2 laser 5.5 ( ZE550KL ) I have also same problem, phone keeps on rebooting....... Showing Asus logo and then vibrates and again start rebooting
I have installed asus firmware from SD card from recovery mode which was successfully installed .... did every thing after pressing volume and power button and even performed necessary actions by doing fastbood mode.
but phone is on same condition.... showed every where.. even service center people raised there hands
Kindly help me to recover my phone back.
Good evening All, It's been a long time since I last posted but want to start at custom roms again and I'm hoping someone can help me as I am now considering giving up on this device.
My sister-in-law gave me her old Galaxy A50 after it stopped working, gives the circle with lightning icon but not the normal charge notification. If it boots I just get the Samsung A50 start screen but no boot and no boot animation.
I have cleared cache, factory reset and tried flashing stock roms via Odin as the bootloader is currently locked so no custom ROM's for me to play with yet. I have tried a couple of stock roms but no joy.
The questions I have are below:
1, could a faulty battery cause the phone to not boot?
2, Is there a way to unlock the bootloader via ADB or some other alternative?
3, is there anything I've missed that I could try to get it to boot thus allowing me to perform number 2 from within Android?
Thanks all in advance. :good:
Maybe
No
Try flashing through ordin and see if it gives an error or completes, failing that - try flashing TWRP and see if you can boot into that maybe formatting data or wiping the system somewhere else might help?
Have you tried more than one charger / plug? - same thing? maybe bad wire / plug
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
InFam0us-1985 said:
Maybe
No
Try flashing through ordin and see if it gives an error or completes, failing that - try flashing TWRP and see if you can boot into that maybe formatting data or wiping the system somewhere else might help?
Have you tried more than one charger / plug? - same thing? maybe bad wire / plug
Click to expand...
Click to collapse
Thanks for the reply, I have tried a few different images via Odin but non of them work and I get stuck at the same place. I can't flash TWRP because the bootloader is locked, unless you know a way I can do it with a locked bootloader?
Abaddon said:
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
Click to expand...
Click to collapse
Thanks for your reply, unfortunately it still wont boot. It has charge as unplugged and currently sot on the android recovery screen. If you can think of anything else I could try I would be very grateful
You could try again with recovery mode, as it charges with that mode. I had to repeat the steps I took for a couple of times for it to boot. Or use another cable perhaps? that's what I did too. It's really frustrating.
Abaddon said:
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
Click to expand...
Click to collapse
works for me! great tip!! tnx
Same problem for me, when trying volume down + power till to reboot but this is not working
any idea please ?
Hi, I had this issue, phone was keep booting, nothing worked, I tried volume up/down button + power, but as you can see in the video, nothing worked. After 3 hours, battery died , charged my phone and worked like nothing happened before. What could I do , let's say if this happens next time, how can I solve ?
The video I took at that day.
File upload and sharing. Large file transfers. Free online cloud storage.
Visit this link to download: vid_20230106_132929.mp4
files.fm
What ROM are you using, stock or custom?
I can't attach video, here is video url that I took at that day.
File upload and sharing. Large file transfers. Free online cloud storage.
Visit this link to download: vid_20230106_132929.mp4
files.fm
ethical_haquer said:
What ROM are you using, stock or custom?
Click to expand...
Click to collapse
miui global 13.0.6
And what phone?
ethical_haquer said:
And what phone?
Click to expand...
Click to collapse
sorry, forgot to add, poco f3
The following steps will force a reboot, you can follow them if you get stuck in a bootloop again.
1. Press and hold power button for about 10 seconds or wait for several options to appear on screen.
2. Tap the Restart option. The phone should then restart.
I watched the video, did you already try pushing the restart button?
ethical_haquer said:
The following steps will force a reboot, you can follow them if you get stuck in a bootloop again.
1. Press and hold power button for about 10 seconds or wait for several options to appear on screen.
2. Tap the Restart option. The phone should then restart.
I watched the video, did you already try pushing the restart button?
Click to expand...
Click to collapse
yes, I already did those before. nothing changed.
Hi, exactly the same problem.
Resolved opening the phone, disconnect and reconnect the battery plug.-->resolved in my case
there are similar cases in other xiaomi phones.
francesco.brocero said:
Hi, exactly the same problem.
Resolved opening the phone, disconnect and reconnect the battery plug.-->resolved in my case
there are similar cases in other xiaomi phones.
Click to expand...
Click to collapse
Indeed, this seems like an issue that is solved by fully powering the phone down; perhaps something in volatile memory preventing recovery by other means?
Regardless, it would seem that the problem itself is resolved. Are you aware of what you were doing before this happened?