Recently I bricked my phone after flashing wrong boot.img. I can't get into bootloader and once the device turns on, I can't do anything except of waiting until the battery runs out of power. Is there any way to recover this phone?
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
It worked! Thanks for help!
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
a) I can't tell from the link alone, what that boot.img even is, and it seems that you don't either. Even if stock boot.img, what version number (there are many - and that matters). My advice (maybe already a lesson learned) is not to flash things, if you aren't 100% sure what they are.
b) I'm not a Lineage user, so I'm not familiar whether that is a known error or not. AFAIK, Lineage should be compatible with Magisk, so as you already figured, the error may be a result of custom kernel, another previously installed root method (SuperSU?) or some other mod. In which case, there are better ways to get back to a "clean" and correct boot.img, rather than flashing files which you are unsure of. Easiest way, is to simply dirty flash the Lineage ROM again. Either just the boot.img (which is included with the ROM.zip) of the whole ROM. Whole ROM is probably the best, as it will give you a clean ROM baseline, in case there is anything else modified (besides boot.img) that is interfering with Magisk. Dirty flash means flashing the file while keeping user data, only wipe cache and Dalvik.
---------- Post added at 09:12 AM ---------- Previous post was at 09:10 AM ----------
DarkKnightComes said:
It worked! Thanks for help!
Click to expand...
Click to collapse
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
Click to expand...
Click to collapse
I forgot about the Power+VolDown combination. I launched Recovery from bootloader and I just installed ROM on top of the previous one. The ROM that I have has Magisk integrated.
Related
Okay, stupid and impatient me wanted to update to CM12.1 without realizing some of the technical issues that I have now discovered....
Long story short, the last thing I did (and first really) , was flashing the boot.img from the CM12.1 zip using fastboot:
Code:
fastboot flash boot boot.img
What I now have is the white HTC boot screen with the red development build text block, and that's it. No recovery, no bootloader, no love.
Am I screwed?
jasonk910 said:
Am I screwed?
Click to expand...
Click to collapse
No, you are not. Nor do I think you did anything stupid, as simply flashing boot.img (as long as you are sure its the right one for the M8) will almost certainly not cause any permanent damage to the phone.
This is simply a no-boot condition; not a brick. Hold power + vol up for 10 seconds or more, until the phone reboots. The moment the screen goes dark to reboot, let go of the buttons, and just hold vol down. Do not let go of vol down, until you see the bootloader screen. Failure to get into bootloader by this method is almost always a matter of just not doing the button combo correctly (the timing if a bit tricky) so just repeat until you get into bootloader.
From there, boot into recovery, restore your nandroid, flash a ROM, etc.
redpoint73 said:
No, you are not. Nor do I think you did anything stupid, as simply flashing boot.img (as long as you are sure its the right one for the M8) will almost certainly not cause any permanent damage to the phone.
This is simply a no-boot condition; not a brick. Hold power + vol up for 10 seconds or more, until the phone reboots. The moment the screen goes dark to reboot, let go of the buttons, and just hold vol down. Do not let go of vol down, until you see the bootloader screen. Failure to get into bootloader by this method is almost always a matter of just not doing the button combo correctly (the timing if a bit tricky) so just repeat until you get into bootloader.
From there, boot into recovery, restore your nandroid, flash a ROM, etc.
Click to expand...
Click to collapse
Fantastic! Recovery backup is restoring as I type. Now to Sunshine, S-OFF, updated HBOOT and THEN CM12.1.
Thanks!
jasonk910 said:
Thanks!
Click to expand...
Click to collapse
There's a button for that.
And you are quite welcome. Happy to see it was that easy.
Hello,
I installed a custom ROM (ViperOneM8+4.6.1) on my M8, which is the international edition M8QL_UL.
I now suspect this ROM is not compatible, as the phone is stuck in a reboot loop - the white screen with the red text at the bottom appears, and then about 35 seconds later the screen goes blank and it restarts.
I've tried holding the power button down to try and turn it off, but it won't stop restarting.
I've tried holding the volume down + power buttons to enter recovery and it doesn't work.
Adb and fastboot don't work either - the phone isn't on long enough to appear on my PC.
Please let me know if there's anything I can do at this point?
Cheers.
jmh55 said:
Hello,
I installed a custom ROM (ViperOneM8+4.6.1) on my M8,
Click to expand...
Click to collapse
Your device is not a M8 but a different device called M8s ....
Read this thread and get help there if you need to.
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
ckpv5 said:
Your device is not a M8 but a different device called M8s ....
Read this thread and get help there if you need to.
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
Click to expand...
Click to collapse
Oh dear, I think this is the issue. The ROM I used was for the M8, not the M8s.
Thanks, I'll try posting in that thread.
jmh55 said:
I've tried holding the volume down + power buttons to enter recovery and it doesn't work.
Click to expand...
Click to collapse
There is no button combo that boots into recovery for this device. I believe you mean the button combo to enter bootloader. Folks will often call this recovery, but bootloader and recovery are 2 completely different things (and this is an important distinction), and folks need to stop thinking they are the same.
Since the phone is bootlooping, just hold the vol down button during the next "loop" and you will enter bootloader.
Once in bootloader, then you can select to boot into custom recovery. Then restore your stock nandroid, if you made one before flashing the custom ROM (and you should always make a nandroid of the stock ROM before flashing a custom ROM).
If you didn't make a stock nandroid, you'll need to use RUU or find a stock nandroid that matches your firmware number.
jmh55 said:
Adb and fastboot don't work either - the phone isn't on long enough to appear on my PC.
Click to expand...
Click to collapse
Fastboot only works in bootloader-fastboot mode; adb only works in OS or recovery. So neither is ever going to work while in a bootloop. Get into bootloader as I've described above (and select fastboot); and you should at least be able to use fastboot.
redpoint73 said:
There is no button combo that boots into recovery for this device. I believe you mean the button combo to enter bootloader. Folks will often call this recovery, but bootloader and recovery are 2 completely different things (and this is an important distinction), and folks need to stop thinking they are the same.
Since the phone is bootlooping, just hold the vol down button during the next "loop" and you will enter bootloader.
Once in bootloader, then you can select to boot into custom recovery. Then restore your stock nandroid, if you made one before flashing the custom ROM (and you should always make a nandroid of the stock ROM before flashing a custom ROM).
If you didn't make a stock nandroid, you'll need to use RUU or find a stock nandroid that matches your firmware number.
Fastboot only works in bootloader-fastboot mode; adb only works in OS or recovery. So neither is ever going to work while in a bootloop. Get into bootloader as I've described above (and select fastboot); and you should at least be able to use fastboot.
Click to expand...
Click to collapse
Thanks for the suggestions and advice - I've got the Pandora Rom back on it now and won't be fiddling anymore I think.
I actually managed to get it sorted by holding vol-up and power for a good 15 seconds based on advice from the M8s thread, just in case any one has the same problem and vol-down doesn't solve it: http://forum.xda-developers.com/showpost.php?p=63177320&postcount=658
Thanks again everyone, I'm been amazed by how helpful people on this forum are.
jmh55 said:
I actually managed to get it sorted by holding vol-up and power for a good 15 seconds based on advice from the M8s thread, just in case any one has the same problem and vol-down doesn't solve it: http://forum.xda-developers.com/showpost.php?p=63177320&postcount=658
Click to expand...
Click to collapse
Power+vol up reboots the phone. You stated the phone was already in a bootloop, which means it was already rebooting over and over.
Vol down (just vol down, no need to hold power button) during any reboot will put you into bootloader. If it doesn't, its because you didn't hold vol down long enough.
I have a HTC one M8 Sprint.
I unlocked the bootloader and flash new TWRP recovery.
After that i installed the CM13 Official nightly zip from my SD card. It succeeded and boot into the new os.
But it does not reconise my simcard.
I changed my CID to SuperCID before that but it still can't reconise my sim.
so i got frustrated and decide to go back to the stock HTC rom.
Being the idiot that i am i forgot to take a NANDROID backup.
So i relock bootloader,take the FIRMWARE and change it to 0P6BIMG and let the bootloader scan my SD card.
i flashed the Firmware and reboot. and now the phone is stuck on the Cyanogenmod bootanimation .
I tried to hold the power and the Volume down button to hard reboot it but it doesn't work.
Now it just stuck there. Not recognized by the computer. Can't use ADB commands to restart the phone to Bootloader.
What should i do now? Wait the battery to run out and then recharge and boot to bootloader ?
Update. I solved it by holding all 3 buttons at once and the phone can be turned off.
so I used the RUU to bring back my htc to stock. Problem solved :l
ChristopherXI said:
I tried to hold the power and the Volume down button to hard reboot it but it doesn't work.
Click to expand...
Click to collapse
That button combo only works (to boot into bootloader) when the phone is fully powered down. It won't work if the screen is on (including stuck on the boot splash screen).
To force a reboot (and go to bootloader) when the screen is on (including stuck on the boot splash screen), you need to:
1) Hold power + vol up for a minute or so, to force a reboot.
2) Once the screen goes dark to reboot, immediately let go of those buttons, and only hold vol down until you see the bootloader screen
3) If the phone just gets stuck on the boot splash again, you got the timing wrong, either started pressing vol down too late, or let go too early - just repeat the process until you get it.
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
ChristopherXI said:
So i relock bootloader,take the FIRMWARE and change it to 0P6BIMG and let the bootloader scan my SD card.
i flashed the Firmware and reboot. and now the phone is stuck on the Cyanogenmod bootanimation .
Click to expand...
Click to collapse
This is the normal and expected result of flashing FIRMWARE.
Firmware is not the same as an RUU or ROM, so that may be the confusion there (somewhat common mistake).
Firmware is a very small package, and does not include the stock OS (ROM or system partition); but just a small collection of other partitions needed for the OS to work (hboot, recovery, radio, etc.)
Flashing stock/signed firmware renders the phone unable to boot as it expects RUU to be run afterwards. Alternately, flashing TWRP and installing a flashable ROM.zip also will get the phone running after flashing firmware.
redpoint73 said:
That button combo only works (to boot into bootloader) when the phone is fully powered down. It won't work if the screen is on (including stuck on the boot splash screen).
To force a reboot (and go to bootloader) when the screen is on (including stuck on the boot splash screen), you need to:
1) Hold power + vol up for a minute or so, to force a reboot.
2) Once the screen goes dark to reboot, immediately let go of those buttons, and only hold vol down until you see the bootloader screen
3) If the phone just gets stuck on the boot splash again, you got the timing wrong, either started pressing vol down too late, or let go too early - just repeat the process until you get it.
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
This is the normal and expected result of flashing FIRMWARE.
Firmware is not the same as an RUU or ROM, so that may be the confusion there (somewhat common mistake).
Firmware is a very small package, and does not include the stock OS (ROM or system partition); but just a small collection of other partitions needed for the OS to work (hboot, recovery, radio, etc.)
Flashing stock/signed firmware renders the phone unable to boot as it expects RUU to be run afterwards. Alternately, flashing TWRP and installing a flashable ROM.zip also will get the phone running after flashing firmware.
Click to expand...
Click to collapse
I knew about the firmware. So i followed it up by using the RUU
EDIT: For the solution to this particular issue, head to this post.
Hi, yesterday I successfully did a clean install of OOS 4.0, including Magisk and systemless root. I had everything set up as I wanted it.
Today, I tried the 4.0.1 OTA, after using a Canadian VPN server. It downloaded fine (the full zip), and I launched the OTA.
Phone reboots... into nothing. Now the phone won't boot into recovery mode, or start the system. I thought it was odd, so I flashed stock recovery again (which is what was installed). Still can't boot. Then tried just booting into recovery over fastboot mode. Still no luck.
Then I managed to boot into a modded TWRP. That's something... But tried flashing the OTA from its temp location in TWRP. A couple of "command log" errors, but appeared to patch nonetheless.
Reboot to system though: black screen of nothing, again.
Anyone know what might be the issue, and why it happened after just launching an OTA through the stock dialogue?
Cheers :/
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
abobobilly said:
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
Click to expand...
Click to collapse
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
ememeh said:
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
Click to expand...
Click to collapse
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
abobobilly said:
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
Click to expand...
Click to collapse
I can get to a point of backing up if I want to. Though at the moment, I don't know what I'd backup (maybe just the system partition? I dunno).
I have the same thing: Can get the white 1+ logo, both capacitative button backlights show, the android text logo, but then black screen. Very frustrating. Let me know if you have any luck! I'll update here too.
wierd
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
canceric said:
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
Click to expand...
Click to collapse
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
abobobilly said:
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
Click to expand...
Click to collapse
good thing it worked for you, it bugs me that i cant root the phone since the device doesnt get recognised in fastboot ,reinstalled all the drivers and all, nothing works
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
ememeh said:
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
Click to expand...
Click to collapse
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Shayded said:
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Click to expand...
Click to collapse
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
ememeh said:
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
Click to expand...
Click to collapse
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Shayded said:
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Click to expand...
Click to collapse
Weird. Could be a different problem...
Did you get the install success message?
ememeh said:
Weird. Could be a different problem...
Did you get the install success message?
Click to expand...
Click to collapse
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Shayded said:
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Click to expand...
Click to collapse
Can you still boot back into fastboot and/or recovery?
ememeh said:
Can you still boot back into fastboot and/or recovery?
Click to expand...
Click to collapse
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Shayded said:
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
Click to expand...
Click to collapse
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Shayded said:
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Click to expand...
Click to collapse
Just seen the edit. Okay, makes sense. Good luck :good:
ememeh said:
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Click to expand...
Click to collapse
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Shayded said:
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Click to expand...
Click to collapse
Luckily for you, it doesn't sound like a true hard brick. Sometimes power buttons are just funny like this. In my experience at least (I've come back from near death experiences in a similar way to you before).
In any event, well done! Always such a relief to get things working again.
Hi! So I have been rolling with the marshmellow version of RR for quite some time and figured I was due for an upgrade. I went to update to the Nougat version, and did everything correctly, firmware, wipe, rom, then gapps. Much to my dismay I was greeted with a screen prompting me for my pattern to start android, I thought this a bit odd but went with it and my pattern did not work. I tried again thinking I may have done it wrong but nothing worked. I didnt think much of it and went to flash again to make sure I did it right, but my recovery never booted. Afterwards I got an error that was very quick and I was not able to read. It came just after the "your phones bootlader has been unlocked" etc. It was a very similar screen as well. After this, I was not able to boot up the phone at all. Once I was able to power up the phone but it simply gave me the same error and now its not starting at all. Any help would be much appriciated and thank you if you made it through this post.
First of all, you need to flash the very latest version of TWRP. If you are suffering from encryption issues and cannot decrypt TWRP, you will need to press back on the TWRP screen, and press wipe -> Format data
You will lose all your data and will be unencrypted. Make sure you have the latest TWRP, as this is vital for Nougat.
FriendWithin said:
First of all, you need to flash the very latest version of TWRP. If you are suffering from encryption issues and cannot decrypt TWRP, you will need to press back on the TWRP screen, and press wipe -> Format data
You will lose all your data and will be unencrypted. Make sure you have the latest TWRP, as this is vital for Nougat.
Click to expand...
Click to collapse
Thank you for the help, but I cannot even get into my device to update TWRP.
Try holding the power button for a minute, or try volume down + power to get into the bootloader.
FriendWithin said:
Try holding the power button for a minute, or try volume down + power to get into the bootloader.
Click to expand...
Click to collapse
Already did, it doesnt work. Black screen.
Im facing the same problem too. Cant even get adb to work ?
If you can still get into your bootloader, use fastboot commands to flash the latest TWRP.
Either hold Vol Up + Power when you phone is off, or turn it on normally and click any volume button during the "bootloader unlocked" warning screen to access the boot menu.
If you can't access the bootloader at all, then I believe the unbrick guide is your only option.
I can get to the bootloader, but when i flash recovery, it just restarts again and again.
Wipe the recovery partition first before you flash the new one.
Also, what version of TWRP are you using?
Yeah I will look into brick guides. Also going to try and let my phone charge to see if that may help. As far as I can tell it isnt charging but I might as well try.
Thank you for all the help guys, eventually what worked for me was indeed an unbrick guide. I will now be sure to read up entirely on what exactly I need to upgrade to fix this issue. For any wondering https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ This was the guide I used to fix my phone.