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 there, I am currently running B383 on my P9, and really want to root it. However when I do, will I still be able to get future updates to the software? Do I need to unroot and lock bootloader first?
Also when the bootloader is unlocked, a message is displayed at boot about your phone being unsecured and non-trustworthy, is it possible to remove this message? (I used to have a moto g with an unlocked bootloader, and I flashed some file to remove the warning).
Thanks
I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.
..
benjamen50 said:
I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.
Click to expand...
Click to collapse
Thanks for the quality answer, I have no doubts anymore!
If I have a P9 on Nougat B391, I receive an OTA, am currently rooted on Magisk v14. If I install the OTA anyway? What will happen? I know I will lose root, but will my bootloader be relocked? Am I going to lose any data?
Would like to know what will happen next as I am thinking of installing it. thanks!
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Arnys said:
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Click to expand...
Click to collapse
IMO, (2) is most possible utcome. (3) may happen if you force DLOAD and other manual methods.
Better:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/showpost.php?p=74913863&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
Of course, you will loose root and TWRP but bootloader will remain unlocked and you will not risk bricking the phone.
Arnys said:
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Click to expand...
Click to collapse
thanks, this roughly gives me an idea on what would happen and the risks it contains! thanks a lot!
zgfg said:
IMO, (2) is most possible utcome. (3) may happen if you force DLOAD and other manual methods.
Better:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/showpost.php?p=74913863&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
Of course, you will loose root and TWRP but bootloader will remain unlocked and you will not risk bricking the phone.
Click to expand...
Click to collapse
thanks a lot! it's useful to know how to unroot my phone as there isn't any particular guide for this phone model haha. anyway, is there a way to unroot and lock my bootloader without wiping my phone?
roottree said:
thanks a lot! it's useful to know how to unroot my phone as there isn't any particular guide for this phone model haha. anyway, is there a way to unroot and lock my bootloader without wiping my phone?
Click to expand...
Click to collapse
Magisk Uninstaller does not wipe your phone.
However, unlocking or relocking Bootloader (from Fastboot) triggers Factory restore
Hey Guys
So I've finally waited out to have OEM Unlocking again, after having to flash stock, after recieving the 'Only official released binaries are allowed to be flashed' error.
My question is just to check the correct method, this is what I have so far :
1) Root device
2) Edit build.prop, remove RLC folder & flash RMM-State_Bypass
3) Flash TWRP, wipe data & reboot
Am I missing anything? I'd rather do it properly this time, and I'll be flashing with stock firmware (Australia, SM-N950F)
Cheers!
Hi guys,
I have a big issue with my S10, probably it's a deadlock...
Successfully rooted with magisk and installed TWRP as described in all the tutorials.
Had some issues with wifi concerning one router and debloated too many apps, so I decided to flash stock rom with TWRP and Magisk again.
Wiped /data and /system and flashed that prepatched AP of G973FXXU2ASF3 again by Odin.
Worked well, flashed multidisabler-g97x-1.2 via TWRP, wiped /data and rebooted to recovery.
Android started, all well and then let Magisk do it's job. It asked for a reboot and then I got locked.
The message "only official released binaries are allowed to be flashed" appeared after that reboot, so I tried to install AP again.
Also in download mode "only official released binaries are allowed to be flashed" appears now, KG state is "Prenormal" and OEM Lock says "OFF (U)".
I know i have to get to the system to skip the 7 days but accesing the system is my problem now.
I can install unmodified AP of G973FXXU2ASF3 but the boot fails.
I can also reach android recovery with options reboot system now, reboot to bootload, apply update from ADB etc.
And I can lock the bootloader in download mode, but I'm not sure to do that.
Thanks in advance if someone can tell what to do best.
Ok i managed it already by myself.
I locked the bootloaded by long pressing vol+ in download mode and locking the bootloader, so I could start the stock firmware.
Then I had to do the date trick by setting date 7 days in past, searching for update manually, putting date back to today, search again for update and oem lock was visible again in dev options.
Afterwards again to download mode, long pressing vol+ and unlocking bootloader one more.
Then I was able to flash AP with Magisk and TWRP again.
EDIT: The issue was that I didn't check if the OEM Unlock was greyed out in dev options, so the VaultKeeper didn't let me install the unofficial image in download mode as described by topjohnwu.