I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Instead of using the toolkit, try just doing it manually.
fastboot oem lock IS the correct way to lock the bootloader.
If you're running into all those issues, try to reflash the stock rom from the official site. OR try this
NOTE: This WILL wipe everything on your phone so make a backup first!
First Unlock booloader1. On your phone go into Developer screen (Settings --> Developer Options)
If you don't have this go back to Settings --> About Device. Tap "Build number" 7-10 times to unlok developer options
2. In Developer Options turn on "USB Debugging" and "OEM Unlock"
3. Open ADB in command prompt and go to the directory where ADB is.
Type adb reboot bootloader
4. Once your device is in fastboot mode, type in fastboot devices to make sure your device is listed
5. Type in fastboot oem unlock to unlock your device bootloader
You can check to make sure it was properly unlocked by typing in fastboot oem device-info.
6. Reboot into your system
Files we need7. Download the following files:
TWRP - https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.2-0-oneplus3t.img
No-verity-opt-encrypt - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
Magisk - http://tiny.cc/latestmagisk
Phh-Superuser - https://forum.xda-developers.com/attachment.php?attachmentid=3988488&d=1483407725
Latest Stable Nougat Rom - http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
8. Copy all the files to your phone (keep the original on your pc just in case)
9. Load back up to fastboot mode
In ADB type adb reboot bootloader
10. Flash twrp img we downloaded above by typing
fastboot flash recovery twrp-3.0.2-0-oneplus3t.img
11. After this reboot into the system
Install all of our downloaded files through TWRP12. Now boot into recovery by issuing the following ADB command
adb reboot recovery (you should go into TWRP)
13. Once you're in twrp flash the "no-verity-opt-encrypt-5.0.zip" file OR you can format the data partition to f2fs to prevent the dm-verity error.
14. Now install the stock stable nougat rom we downloaded above
15. Do a factory system wipe / cache & dalvik
16. Install magisk through TWRP
17. Wipe cache/dalvik
18. Install phh SuperUser
19. Now reboot into the system normally.
NOTE: This *COULD* take a while since you did a clean install of nougat so just be patient and you should be good to go after this.
Thanks for the reply.
I did do fastboot oem lock, and it results in an unbootable system. fastboot oem unlock makes it bootable again. Not sure why. Also, whenever I do adb sideload <any_rom> it fails after about 45%. Not sure what's happening. Your instructions would get me to Nougat with TWRP and an unlocked bootloader, which may be what I end up doing, but I was trying to get back to fully stock, and locked again, so that OTA's will work properly. If nothing else works, I will go the route you suggest above.
Thanks again!
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
TXRangerXDA said:
I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Click to expand...
Click to collapse
I also have the same problem, after the bootloader lock the phone does not start.
I tried with all the possible procedures, also even the rom flash in local and sideload it does not work, It comes to 45% and then fails.
we will highlight the problem, so everyone will know and maybe there is a solution
m0d hipp¥ said:
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
Click to expand...
Click to collapse
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
That's what I figured. Thanks for the confirmation.
Use the unbrick tutorial to go back to stock
This is what i did
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
pitrus- said:
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
Click to expand...
Click to collapse
I'm sorry, even with the stock recovery but does not work, it was the first thing I did
You can a unbick tutorial. It worked for my OnePlus 3T. Just search up How to unbrick (whatever OnePlus device you have) on Google. Then follow all the instructions carefully. If you need help with it I could try to do a remote session with you. Edit: It will erase all data and you will boot with oos 3.5.3 ( I also had the same issue as you. But I couldn't install any zip with stock recovery or adb side load.
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Only if you have modified the phone in some way or another (like rooting and installing twrp) before trying to re-lock.
If you keep it stock, you should be able to re-lock. Or else, just use the Qualcomm restore method to re-lock.
tried this
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
I think the problem in re-locking it is the modified boot image. Locked bootloaders don't support those.
re-locking bootloader will getback the warranty ???
No solutions till now
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Its three easy steps, no need to use any toolkit just follow the instructions. https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Abrar123 said:
re-locking bootloader will getback the warranty ???
Click to expand...
Click to collapse
Unlocking the bootloader does not void the warranty on this device:
https://oneplus.net/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
Once I have root, is there a command to re-lock and later eventually unlock the bootloader again?
I remember this was possible with google nexus devices, there was a shell command (require root) that was able to change bootloader status
Hi
The device is Samsung Galaxy Tab S2 8.0 SM-T713.
Following is what happened:
1. Installed TWRP and then Installed Lightning ROM v1.0.
2. Restarted the tablet without turning on OEM Unlock.
3. Did not boot by giving error "custom binary blocked by frp lock"
4. Tried installing stock firmware with odin. Firmware installs successfully but when the tablet reboots, it keep showing the glowing samsung logo.
5. Tried multiple different firmwares and eventually tried the latest firmware for the XAR region. Now only that firmware can be installed and all other older firmwares fail in the installation step giving the error "sw rev check fail aboot fused 2 binary 1"
Would really appreciate if anyone could help.
I assume that flashing pit file with the latest XAR region firmware will help boot the tablet but i cannot find the pit file to use.
Please HELP!
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
lewmur said:
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
Click to expand...
Click to collapse
The problem is that the TWRP recovery is long gone. Its not on the tablet anymore. I cannot flash TWRP because of FRP lock. I can access stock recovery but it also does not allow me to wipe data and factory reset due to FRP lock.
Any other suggestions.
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
rafayzq said:
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
Click to expand...
Click to collapse
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
lewmur said:
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
Click to expand...
Click to collapse
All the problems started when i restarted the tablet running a custom rom without enabling the OEM Unlock option in Developer Options in settings.
The lesson i learned the hard way is that you should always keep the OEM Unlock enabled
Firstly I need to say that I've read the forums from top to bottom before posting this, so I'm pretty sure no one here experienced this particular issue here on a P9 Plus at least.
I've tried tried to flash TWRP in order to be able to root my P9 Plus.
To do this I did the following steps:
1. Enable Developer Options in settings
2. Enable USB debugging
3. Successfully unlocked my bootloader using a code from Huawei
4. Entered fastboot mode and flashed the latest TWRP 3.1.1 recovery from their website
5. After Huawei's eRecovery kept opening I (after a suggestion in another post in the forums) flashed TWRP on recovery2 as well.
6. Phone stuck in "Your device is booting now..." screen and only booting in fastboot mode is working.
Any ideas what I've broken and how I could possibly fix it?
EDIT: At this point I'm willing to flash everything back to stock, however I'm not sure if I've got the VIE-AL10C00 or VIE-AL10BC00. I'm using the 64GB Dual SIM Chinese version of the phone with Android N and got both firmwares downloaded (updatebc183 for BC00 and 198 for C00 which are the latest for both versions) and ready.
EDIT2: I downloaded the correct latest full update 198 for my VIE-AL10C00 (as it turns out) and extracted the recovery and recovery2 images, then flashed them along with boot.img. Still having the same issue. (I need to say that in fastboot I can't flash anything other than recovery, recovery2 and boot images)
Hi I'm a new Android user and don't know much about it :'( I recently got my OnePlus 3T and I wanted to root it
so I followed a tutorial video from YouTube successfully unlocked bootloader and flashed twrp recovery then I tried to install SuperSU... well it installed but the device got soft bricked when I rebooted after finishing the installation and wiping cache/dalvik
then I format/factory reset everything using twrp recovery and it's working now but the device isn't rooted :'( tried to install SuperSU again and it got bricked again
Also I'm getting these messages on the startup screen-
1st one: Your device has been unlocked and can't be trusted. If you don't want to see this screen please lock your device by "fastboot oem lock" and erase user data.
2nd one: The dm-verity is not started in enforcing mode and may not work properly.
(My os version is 4.1.7)
device OP 3t A3010
plz help me :'(
The 1st and the 2nd msg that gets displayed is shown because the bootloader is unlocked..
Bootloops are common while flashing su...when I flashed super su for the first time, I got 3 or 4 random reboots and took almost 7 to 10 mins for the phone to boot up..
I would suggest using Magisk as a rooting method instead of SuperSU. If you use SuperSU then some apps can detect root and object to you being rooted and Google's SafetyNet gets triggered. Magisk solves this by trying to hide root from apps and Google so that you can use your device as if it wasnt rooted at all (but in fact is rooted). Go the the Magisk forum and download Magisk 13.3 zip from there.
I am assuming you are using OxygenOS (Oneplus's software) and not a custom ROM. Download the Open Beta or Stable build from here/
These steps will erase all the data on your phone permanently (including internal storage) so please backup anything in there.
To fix the DM verity error youll have to follow the steps outlined here
Once you have fixed that, flash oneplus recovery via fastboot which you can download here
To flash it go to fastboot mode, and cd into the folder where you downloaded it. Run the command 'fastboot flash recovery <RECOVERY_NAME>'.
Then run the command 'fastboot oem lock' to lock the bootloader. After you confirm the prompt on screen, the phone will boot into the recovery and youll see a progress bar. Once the progress completes and the screen turns off, be ready to immediately go back to fastboot mode by pressing volume up and power.
When you enter fastboot mode again, run the command 'fastboot oem unlock' and follow the same steps as before.
Once you are in fastboot mode, the phone is now in a clean state with no OS.
Follow the steps outlined on the oneplus website to flash a clean OxygenOS build (stable or open beta as per your taste)
Once the flashing is complete you have to let the phone boot up completely once. When you get to the setup screen, go through it and reach the launcher.
Now we flash TWRP recovery. Reboot to fastboot again. Flash TWRP recovery (I personally use blu_spark's twrp but you can use one of your choice). When it is done, boot into the recovery. Youll now be able to copy magisk zip into the internal sd. Do that, and flash it. Reboot.
Youll now be rooted. If you have any problems holla at me.
Got official notification and have installed Pie (9.0.1.163) on my VTR-L09C432 P10.
Downloaded the Full OTA (9.0.1.163), extracted the RECOVERY_RAMDIS.img, patched with Magisk 7.1.1 and flashed using fastboot to the recovery_ramdisk partition. When rebooted with Vol+ have root. Played around with Pie and have decided to revert back to Oreo.
HiSuite (v9.0.3.300_OVE) did offer me rollback to 8.0.0.365. So I have decided to pursue this option. The firmware download went OK (100%), the programing went OK (100%) and the phone rebooted, as said the popup, but ... it was still on Pie as before.
Decided to try to "upgrade" via eRecovery. It wasn't able to determine and download any package. So I tried factory reset. No error, but it seems to do nothing. The phone rebooted and the situation is: Pie works, Magisk reports root 18.1 and root apps work.
From this moment I am unable to enter fastboot. The phone just boots normally with Magisk root. As I have just written eRecovery is present but is useless (can't download an upgrade package and can'r factory reset).
Advice?
Should I try writing from a term using dd the extracted RECOVERY_RANDISK.img and ERECOVERY_RAMDISK.img ? This way will loose root (Magisk) but don't know if it "resolve" access to fastboot and "fix" eRecovery.
EDIT:
No reply so decided to go ahead with what I thought was happening. I didn't know that a firmware upgrade (or downgrade) needs recovery to complete. I thought erecovery was the key.
So when I used HiSuite to rollback to Oreo what happened was it downloaded the Oreo firmware, uploaded it to the phone, prepared for a firmware flash and did a reboot. The firmware downgrade was supposed to happen in recovery but since the recovery code was changed by Magisk the flashing was never happening.
The same when from erecovery I tried to do a factory reset. Seems that erecovery just prepares things but recovery code does the actual reset. And once again I was observing that nothing was happening. The phone was simply root booting exactly as the Magisk code is supposed to do.
So I just flashed (from a term) the original recovery_ramdisk.img. After reboot got the factory reset welcome screen.
Of course got back fastboot.
Hope this can be of of help someone is a similar situation
Dude can you please guide us how to actually use DD command.
edit: I did this a different way. much easier & safer for less experienced users.
1. Open magisk manager. At the bottom of the first screen there is a button "UNINSTALL". Press uninstall & click "restore images".
2. Magisk will remove itself and restore your original boot image. Worked for me