Related
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
You should try Fastboot EDL. search Google. Good luck
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Try reflashing stock firmware with fastboot.
fast69mopar said:
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Windows wont install the drivers on the thread so i cant proceed and the next available date for Oneplus tech is July 24th this is so urgent....any other options?
Nv1dia said:
Try reflashing stock firmware with fastboot.
Click to expand...
Click to collapse
I cant because says flashing isnt allowed
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Anybody?? Please help
scottwitha5 said:
Anybody?? Please help
Click to expand...
Click to collapse
Update: I followed the Mega Unbrick Guide for a hard bricked Oneplus 3, and now instead of even starting android, this appears, and I cant get into recovery or flash anything because it isnt allowed....please help me
I think your error was to relock the bootloader because if it was still unlocked, you could still reflash the boot.img (but your relocked your bootloader)
Solving it.
Don't worry I shall help you.
This happened to me too.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
To get the drivers and adb along with twrp and root use this toolkit.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Get the Oneplus drivers through this too.
It's not very complicated but ask me for any help.
Use the Method 2 in the Mega UnBrick Guide and download the stock image on to it.
You will lose data all of it.!
Make it boot.
Then tick OEM unlocking
Unlock bootloader through the toolkit.
flash twrp and root done..!!.
You messed up when you ticked off OEM unlocking and fastbooting it.
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
My Nexus 5X just corrupted itself a couple days ago and unfortunately I did not enable OEM unlocking before that happened. I was running stock, un-rooted and from looking online the past couple days I see no way to unlock the bootloader so I can wipe everything and re-flash. I can get into fastboot, but not recovery mode. Recovery mode just says "No Command" with the little android on its side. I have tried all the fastboot commands that one would normally try and they all return some version of "device is locked" error messages. Is there any way at all to unlock the bootloader or flash stock, or otherwise get into recovery without checking that OEM unlocking option in the Developer Options of the OS? I don't care about my data, I just want to get my phone working again. It's out of warranty so I am willing to try anything to get it working again.
I'm in the same situation
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
_Ghost said:
This is why I always enable Oem unlocking on all devices I own regardless of security for things like this .
Click to expand...
Click to collapse
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
How did you fix it?!
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I am in this exact situation. Phone out of warranty, just want to get it back on, don't care about the data on it.. but the "device state" is locked. I can get it into recovery but the sideload fails, I think because the device is locked. How did you get your phone to work again??
I've tried following these instructions (I'm new and can't post a URL: [ttps://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view) and it fails during step 19.
I've also tried these instructions (I can't post the URL but if you google this exact phrase, it's the first link: Nexus 5X Bootloop Fix - The Step-by-step DIY Guide - TechBii) but the phone is locked so I can't do it.
Help!
See this post please: https://forum.xda-developers.com/nexus-5x/general/petition-google-release-official-t3672987
Thanks
So did you ever get it to work or just thre the phone in the garbage, @coryrwest
See my latest post in the thread: https://forum.xda-developers.com/showpost.php?p=71241965&postcount=4
How?
coryrwest said:
Yeah, im going to be doing that from now on. I am pretty sure it was an OTA update that did it. It had just updated a day or two before. I was able to get into Recovery and sideload a different OTA update. The update failed and the phone rebooted, but it rebooted into Android. I was able to get my data off and all seems stable for now.
Click to expand...
Click to collapse
I'm having a similar issue, how did you exactly get it into recovery? Cause mine will simply keep rebooting if I select recovery mode from bootloader
My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?
also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)
I unlocked the bootloader on my phone because I was planning on flashing a different ROM on the phone and I never got around to it. Now I need to send it back because of a screen issue and I want to relock it so I don't get any grief from Google about it. So can I just run the lock command or do I need to flash a factory image first and then do the lock?
loki993 said:
I unlocked the bootloader on my phone because I was planning on flashing a different ROM on the phone and I never got around to it. Now I need to send it back because of a screen issue and I want to relock it so I don't get any grief from Google about it. So can I just run the lock command or do I need to flash a factory image first and then do the lock?
Click to expand...
Click to collapse
Be darn sure you are full stock!! No magisk or modules or custom kernels. I just did this for a trade in for my P4XL as well. After I uninstalled magisk and custom kernel, I factory reset, let it boot up, then went back and clean flashed the factory image. In essence, wiping the phone twice. Also, be sure and leave OEM unlocking and USB debugging turned on. Then just go to fastboot and run...fastboot flashing lock. And there ya go :good:
Badger50 said:
Be darn sure you are full stock!! No magisk or modules or custom kernels. I just did this for a trade in for my P4XL as well. After I uninstalled magisk and custom kernel, I factory reset, let it boot up, then went back and clean flashed the factory image. In essence, wiping the phone twice. Also, be sure and leave OEM unlocking and USB debugging turned on. Then just go to fastboot and run...fastboot flashing lock. And there ya go :good:
Click to expand...
Click to collapse
I was in the process of rooting it and somehow soft bricked the phone..so I has to reflash the stock image once. After that I didn't mess with uit again but I left it unlocked because I figured id try again at some point. So yeah Ill just reflash a factory image just to be extra sure and then relock it.
loki993 said:
I was in the process of rooting it and somehow soft bricked the phone..so I has to reflash the stock image once. After that I didn't mess with uit again but I left it unlocked because I figured id try again at some point. So yeah Ill just reflash a factory image just to be extra sure and then relock it.
Click to expand...
Click to collapse
This thread might help you :
https://forum.xda-developers.com/pixel-2-xl/help/lock-bootloader-steps-p2xl-t3968185
Yep I did that last night..worked fine, its all ready to go back now.