Related
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
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:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??
Hello friends.
I got my Pixel XL 2 yesterday and today I'm in trouble already.
I unocked the bootloader, installer twrp and rooted with magik succesfully, but I had trouble installing my apps (titanium backup gave me a parcing error and the googgle play store wanted me to pay again for my purchases for some reason), so I figured I do a factory reset so I get prompted to restore from my old phone via cable. So I went to settings -> factory reset.
The problem is that when android rebooted to erase the data, I instead got dumped into twrp on a screen that says Mount Decrypt Data and is asking me for a lock pattern. But the screen doesn't responds, so I can't proceed. The power hard button just toggles the screen on and off but it does not reboot or turns the phone off when I hold it, so I don't know how to get to my bootloaded to maybe reinstall a factory image or what else to do.
I'm just stuck on that screen without options.
I would very much appreciate any advice.
Hold power, vol up and down buttons until your device turns off.. then go into bootloader by holdind vol down and power
I thank you very much for your reply.
I did booted succesfully into bootloader, but now I'm affraid I jumped from the frying pan into the flame because now my phone doesn't power up at all. If I connect it to the charger I don't get the battery with a lighting bolt that I'm supposed to get. The only life sign I get is if I plug it via USB to my computer, I do get the sound that windows plays when yoy connect something, but other than that, the phone seems to be dead.
I'm guessing it's something with the hardware?
hold the power button till it shuts off
flex360 said:
hold the power button till it shuts off
Click to expand...
Click to collapse
It is off. I can't turn it on at all. It's unresponsive.
BreadedChicken said:
It is off. I can't turn it on at all. It's unresponsive.
Click to expand...
Click to collapse
Was the battery low when you started this?
Are you familiar with ADB? When plugged into the computer type adb devices or fastboot devices does it return your device serial number? If so type adb reboot bootoader.
If not I would hold the power button for a good 20-30 second and see if you can force it to turn on or reboot and immediately hold volume down to get back to bootloader.
BreadedChicken said:
It is off. I can't turn it on at all. It's unresponsive.
Click to expand...
Click to collapse
Did you get anywhere with this? Just curious. I know you're probably upset, we're here to help if we can. :good:
Thank you very much to everyone for your time and help.
Thanks to your advices I was able to solve it. In case anyone ever finds himself or herself out in a similar situation, here's what ended up happening:
After holding the power button for about 30 secs as Namolas sugested the phone did reboot itself and brought me back to that twrp mount decrypt data screen asking me for a lock pattern. It was then just a matter of adb booting to the bootloader and install a factory image as usual.
Thanks again. I appreciate it guys.
Device is OnePlus 9 Pro (LE2123); stock Rom, locked bootloader, never modified anything. Currently I am in very strange and scary situation. I discovered, that when the phone is plugged into anything via cable (so when it is connected to charger, PC, laptop), when I shut down or try to reboot it, it goes black and completely bricked. It doesn't react on plugging into charger, it doens't react fot plugging into PC, it can't enter EDL mode via buttons combination (PC doesn't even recognize it, like I never plugged anything to it). However, after few minutes (usually at least 10), and after trying many, many diffrent key combinations, by some random combination (I think it's holding all buttons for at least 20 seconds, but not sure about that too, because it sometimes boot to recovery, sometimes to bootloader) it somehow comes back to life. Has anyone ever experienced anything like that?
In that situation, I'm scared of trying to modify anything, because everything includes having phone plugged in into PC, and rebooting it. And in my case, the phones then bricks itself.
Yes, I've tried different USB cables (3 of them), tried all of USB ports, and tried different PC's.
EDIT: I started to try to modify this phone. I mean unlocking bootloader, rooting, etc.
Found out that being in fastboot and "fastboot boot something.img" works fine with the cable plugged in. Another interesting thing is that, when I want to install root via Magisk app, when I hit "Direct Install (Recommended)", it reboots and goes brick (without cable connected).
Currently I'm on OOS11, bootloader unlocked and kind of rooted. Why kind of? Because I extracted boot img via MSM, then patched it via Magisk app, then booted this patched image via fastboot. And now I'm stuck in that state, because I as said earlier, when I try to do "Direct Install" it reboots and bricks. After some time when I'm finally able to boot up again, it again says I can "Direct Install"
Make sure the C port is clean and intact.
Defective C port pcb (if they use them) and/or maybe battery is where I would start.
blackhawk said:
Defective C port pcb (if they use them) and/or maybe battery is where I would start.
Click to expand...
Click to collapse
Transfering files, and charging works fast, and perfectly fine, tho
Klusio19 said:
Device is OnePlus 9 Pro (LE2123); stock Rom, locked bootloader, never modified anything. Currently I am in very strange and scary situation. I discovered, that when the phone is plugged into anything via cable (so when it is connected to charger, PC, laptop), when I shut down or try to reboot it, it goes black and completely bricked. It doesn't react on plugging into charger, it doens't react fot plugging into PC, it can't enter EDL mode via buttons combination (PC doesn't even recognize it, like I never plugged anything to it). However, after trying many, many diffrent key combinations, by some random combination (I think it's holding all buttons for at least 20 seconds, but not sure about that too, because it sometimes boot to recovery, sometimes to bootloader) it somehow comes back to life. Has anyone ever experienced anything like that?
In that situation, I'm scared of trying to modify anything, because everything includes having phone plugged in into PC, and rebooting it. And in my case, the phones then bricks itself.
Yes, I've tried different USB cables (3 of them), tried all of USB ports, and tried different PC's.
Click to expand...
Click to collapse
To clarify, this is not called a hard brick. A hard brick would not allow you to boot the os without using a MSM recovery tool.
Klusio19 said:
Transfering files, and charging works fast, and perfectly fine, tho
Click to expand...
Click to collapse
Interesting. On Samsung's the C port can cause havoc in seemingly unrelated systems.
Possible malware ie rootkit. Try in safe mode to rule out any 3rd party apps. 3rd party apps with Administrator permissions may persist in safe mode though. Deactivate them in security.
If you have the option to clear the system cache do so.
Take any system instability on an Android seriously as that maybe the only warning before it boot loops on you. Back up all critical data, now. Logcat might help you track it down, not sure as I never had to use it.
Also try turning off Developer options if active.
If that doesn't work, factory reset.
If that fails it's likely hardware.
TheSayaMan said:
To clarify, this is not called a hard brick. A hard brick would not allow you to boot the os without using a MSM recovery tool.
Click to expand...
Click to collapse
Well, it is kinda "hard brick" but it lasts only for a while, so I probobly I should call it temporary hard brick. Anyway in that state as I described device stays completely dead, no reaction for charging, plugging, can;t boot to anything including edl.
blackhawk said:
Interesting. On Samsung's the C port can cause havoc in seemingly unrelated systems.
Possible malware ie rootkit. Try in safe mode to rule out any 3rd party apps. 3rd party apps with Administrator permissions may persist in safe mode though. Deactivate them in security.
If you have the option to clear the system cache do so.
Take any system instability on an Android seriously as that maybe the only warning before it boot loops on you. Back up all critical data, now. Logcat might help you track it down, not sure as I never had to use it.
Also try turning off Developer options if active.
If that doesn't work, factory reset.
If that fails it's likely hardware.
Click to expand...
Click to collapse
It's fresh device, so nothing malicous is not present here for sure, and in the meantime I did the factory reset too. So I guess it's some hardware problem, but as we can see, it's very, very strange
I had same issue few times on 9Pro le2123. I noticed it when I discharged my battery to 0% and the phone was powered off. Then I connected it to cable and waited some time to charge it before try to power it up, but I got same behavior you described (it was not possible to turn on the phone). There was no indication for charging (usually there is an indication when phone is charging when powered off and battery is not enough to power it up). After several attempts with different combinations I managed to boot in recovery, then waited to charge the phone (thankfully there is battery level indicator on recovery), then disconnected the charger and rebooted the phone using the recovery options. Since then I never leave my phone battery below 10-15% . As I am rooted with unlocked bootloader I decided it could be because of that, but it seems it is not.
sshriss said:
I had same issue few times on 9Pro le2123. I noticed it when I discharged my battery to 0% and the phone was powered off. Then I connected it to cable and waited some time to charge it before try to power it up, but I got same behavior you described (it was not possible to turn on the phone). There was no indication for charging (usually there is an indication when phone is charging when powered off and battery is not enough to power it up). After several attempts with different combinations I managed to boot in recovery, then waited to charge the phone (thankfully there is battery level indicator on recovery), then disconnected the charger and rebooted the phone using the recovery options. Since then I never leave my phone battery below 10-15% . As I am rooted with unlocked bootloader I decided it could be because of that, but it seems it is not.
Click to expand...
Click to collapse
My case is worse, because EVERY time when it's connected to anything it brakes. I literally have to remember not to shut down or reboot while it's plugged to anything.
And even worse part is, I sometimes notice, that it bricks even when it's not plugged, and I simply try to reboot it!
Also noticed, that for example, when it's connected to PC, it doesn't brick when "fastboot boot anything.img".
Next thing I noticed, it bricks, (also when NOT connected) when I try to install root via "Direct install (recommended)" from Magisk app.
My case is super strange
Need to change title because a phone doesn't hard brick itself and if you can still get it to boot into the os without using MSM, its not hard bricked.
TheSayaMan said:
Need to change title because a phone doesn't hard brick itself and if you can still get it to boot into the os without using MSM, its not hard bricked.
Click to expand...
Click to collapse
It is in the hard bricked state for quite some time. So how should I call it then?
Klusio19 said:
It is in the hard bricked state for quite some time. So how should I call it then?
Click to expand...
Click to collapse
If its not booting into system then yes its bricked but probably soft bricked. A hard brick means it won't boot into recovery, fastboot, bootloader, and system, none of those and requires MSM tools to recover the phone.
If your phone is under manufacturer warranty, would you consider that route?
AndyC76 said:
If your phone is under manufacturer warranty, would you consider that route?
Click to expand...
Click to collapse
If you can get into EDL mode with a hard brick then it can still be fixed with MSM.
TheSayaMan said:
If its not booting into system then yes its bricked but probably soft bricked. A hard brick means it won't boot into recovery, fastboot, bootloader, and system, none of those and requires MSM tools to recover the phone.
Click to expand...
Click to collapse
Have you read my post? That's exactly what is happening. The device is completely dead. No reaction for charger, no reaction for any buttons, can't boot to anything, can't even enter MSM. Please read with understanding before posting something, thank you sir