Hey guys,
I've seen some solutions for my kind of problem but none of them seems to start at my frustrating point.
After I rooted my HTC One S I was able to reboot my device and everything went fine.
The problem occured just when my battery was depleted and the phone got turned off I had no chance to restart it.
The LED did not show me it was charging and it did nothing, when I pressed the power button or the volume/power combination.
So i connected it to my laptop and tried to check my devices through adb.
It says my device is in recovery mode.
Using the fastboot reboot command I was always able to reboot my phone and everything was just fine.
I thought it was alright, as I just had to pay attention not to use up my battery, when not at home.
Today my phone just decided to turn off. It refuses to boot up even with the fastboot help from my PC.
It just says: < waiting for device >
certainly I'm unable to post a link to a screenshot I made of my cmd.
Thank you for all kind of help
My phone is stuck at the boot logo, and won't fully boot. The boot with the volume down button pressed doesn't work, or even the volume up thing, in order to enter fastboot I need to let it boot up to the logo then run the
Code:
adb reboot-bootloader
command. when i try the
Code:
adb reboot recovery
command, it boots to the oneplus logo, then reboots normally, and I am back to where I was. I cannot flash a new image, because my bootloader is locked, and in order to unlock it, the phone needs to boot up. Is there a way to unlock the bootloader without a full boot? Can I flash without an unlocked bootloader? Is it bricked? please, any feedback would be appreciated.
Beast_Boy said:
My phone is stuck at the boot logo, and won't fully boot. The boot with the volume down button pressed doesn't work, or even the volume up thing, in order to enter fastboot I need to let it boot up to the logo then run the
Code:
adb reboot-bootloader
command. when i try the
Code:
adb reboot recovery
command, it boots to the oneplus logo, then reboots normally, and I am back to where I was. I cannot flash a new image, because my bootloader is locked, and in order to unlock it, the phone needs to boot up. Is there a way to unlock the bootloader without a full boot? Can I flash without an unlocked bootloader? Is it bricked? please, any feedback would be appreciated.
Click to expand...
Click to collapse
So you can't boot into fastboot with the power + volume up button combo after shutting the phone down (hold power)? No you can't unlock bootloader without successfully booting into fastboot. No you can't flash without unlocking the bootloader.
Heisenberg said:
So you can't boot into fastboot with the power + volume up button combo after shutting the phone down (hold power)? No you can't unlock bootloader without successfully booting into fastboot. No you can't flash without unlocking the bootloader.
Click to expand...
Click to collapse
i can only turn the phone on in the normal mode. does this mean it's bricked? do I have to send it in?
Beast_Boy said:
i can only turn the phone on in the normal mode. does this mean it's bricked? do I have to send it in?
Click to expand...
Click to collapse
I would think it's bricked, it's virtually impossible to brick this device. So it'll turn on when the power button is pressed, but it won't actually boot, right? Nothing at all happens when using the fastboot button combo? A little background info would be good, what lead to this situation?
Heisenberg said:
I would think it's bricked, it's virtually impossible to brick this device. So it'll turn on when the power button is pressed, but it won't actually boot, right? Nothing at all happens when using the fastboot button combo? A little background info would be good, what lead to this situation?
Click to expand...
Click to collapse
The button combos do nothing, not even boot the device normally.
So, what happened is this: I was trying to root my phone, I plugged it into a windows 8.1 machine, and I was following a tutorial by C4Etech. It was working fine, until I unlocked the bootloader, after the it was unlocked, my machine could no longer recognize my device. I uninstalled and reinstalled countless drivers multiple times in an attempt make my machine recognize my device, rebooted my phone, my computer., the adb server, and anyhting else I could. Nothing worked. Angry and frustrated, I plugged it into my Linux Mint machine, and it recognized perfectly! because I am a noob, and have never done anything like this before, I began to panic when I saw that my phone wouldn't reboot like they did in the tutorials right after they unlocked the bootloader, so I skipped that part, and continued with the flashing. after flashing, my phone would no longer boot, so I thought I messed up with the unlocking portion because my phone wouldn't reboot after the "fastboot oem unlock" ( because I am a noob, I thought that the unlock was temporary, and that my many reboots of the phone managed to undo it.). thinking the unlock was the culprit to my broken phone, and thought adb must be glitched since it doesn't reboot after "fastboot oem unlock" like it did in the tutorials, like a genius, i typed in "fastboot oem lock" rebooted into fastmode, then typed in "fastboot oem unlock". I was filled with joy when I saw my phone reboot like it did in the tutorials, but my joy began to fade, as the phone was still booting after several minutes. And thats when I died inside, and began posting on many online forums, because google couldn't find anything that matched my situation.
the button combos stopped working after the flash.
Beast_Boy said:
The button combos do nothing, not even boot the device normally.
So, what happened is this: I was trying to root my phone, I plugged it into a windows 8.1 machine, and I was following a tutorial by C4Etech. It was working fine, until I unlocked the bootloader, after the it was unlocked, my machine could no longer recognize my device. I uninstalled and reinstalled countless drivers multiple times in an attempt make my machine recognize my device, rebooted my phone, my computer., the adb server, and anyhting else I could. Nothing worked. Angry and frustrated, I plugged it into my Linux Mint machine, and it recognized perfectly! because I am a noob, and have never done anything like this before, I began to panic when I saw that my phone wouldn't reboot like they did in the tutorials right after they unlocked the bootloader, so I skipped that part, and continued with the flashing. after flashing, my phone would no longer boot, so I thought I messed up with the unlocking portion because my phone wouldn't reboot after the "fastboot oem unlock" ( because I am a noob, I thought that the unlock was temporary, and that my many reboots of the phone managed to undo it.). thinking the unlock was the culprit to my broken phone, and thought adb must be glitched since it doesn't reboot after "fastboot oem unlock" like it did in the tutorials, like a genius, i typed in "fastboot oem lock" rebooted into fastmode, then typed in "fastboot oem unlock". I was filled with joy when I saw my phone reboot like it did in the tutorials, but my joy began to fade, as the phone was still booting after several minutes. And thats when I died inside, and began posting on many online forums, because google couldn't find anything that matched my situation.
the button combos stopped working after the flash.
Click to expand...
Click to collapse
Have you seen this?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Might be worth a try.
Hey guys off the forum,
my phone wont turn on anymore and is stuck on the boot picture.
I was running stock android 10 with unlocked bootloader. somehow it wasn't running smoothly and was planning on doing fresh install.
was running cmd then adb reboot bootloader then I did flash-all.bat ( I did not change the file just stock) everything went good until I restarted and cmd said error on the end. now cmd wont see the phone and phone wont turn on.
I was hoping if someone can please help me out I really appreciate it.
webjo said:
Hey guys off the forum,
my phone wont turn on anymore and is stuck on the boot picture.
I was running stock android 10 with unlocked bootloader. somehow it wasn't running smoothly and was planning on doing fresh install.
was running cmd then adb reboot bootloader then I did flash-all.bat ( I did not change the file just stock) everything went good until I restarted and cmd said error on the end. now cmd wont see the phone and phone wont turn on.
I was hoping if someone can please help me out I really appreciate it.
Click to expand...
Click to collapse
I had the same exact issue when it switched to slot B and stopped showing up on my computer when the device was in fastboot and I had no access to recovery mode. Try powering the phone down from fastboot with the power off menu. Then turn the phone on by holding the power button down and keep it pressed (it should cycle on and off b/w fastboot and a black screen. Keep holding until you feel a short vibration after about 30s - 1 min) It should then show it in adb and fastboot on your computer.
EDIT: If the phone isn't powering on, try charging it and if that doesn't work, try hard resetting it by holding the power button down for 30s-1 min. Can't imagine a bad flash would completely cause the phone to at least not load the bootloader.
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not
I was charging my mi 4 it had around 70% charge when it completely went black and started to vibrate again and again like it was rebooting the screen is lighting up but there is no logo and the phone is not booting up completely, i cant access recovery mode as it wont stop rebooting. I have not done anything special to the phone.
SilverXDA said:
I was charging my mi 4 it had around 70% charge when it completely went black and started to vibrate again and again like it was rebooting the screen is lighting up but there is no logo and the phone is not booting up completely, i cant access recovery mode as it wont stop rebooting. I have not done anything special to the phone.
Click to expand...
Click to collapse
Back up your data if you can.
If you still have adb, try adb pull your userdata partition.
If you can still access to fastboot mode, try
- flashing a fastboot rom if you can find one.
- flashing a recovery in fastboot could help as well (so you could flash recovery rom).