Related
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
Hi,
I appeal for the community help to try to get rid of my tablet "boot-loop" !
Here is the situation today :
My tablet no more boots on Android. It starts on what I believe is the bootloader (see screenshot) but this original bootloader doesn't allow me (through volume +/-) to choose between the usual recovery/boot/reboot choices. I can't do anything except a long press on power to switch off the device. On this "bootloader" screen, I fortunately can send fastboot commands.
What I can do :
- fastboot reboot => ok, the device reboots and comes back to the same screen
- fastboot continue => most of the time (if not always) it does nothing, but some few times (I can't manage when exactely) it continues the boot and goes to the loading screen with ASUS image and loading spinner, but the boot doesn't go further : I let it a full night and the device was still on this screen.
- fastboot flash boot boot.img => ok. The image (from a zip downloaded on ASUS website asus.com/Tablets/ASUS_Transformer_Pad_TF303K/HelpDesk_Download ) is flashed successfully.
- fastboot erase xxx => ok, clean the partition
- fastboot oem unlock => FAILED (remote: Invalid signature, fail to unlock!!)
How I finally get here :
I wanted to root/unlock my device, except I may acted as a newbee ! Finally, today, I don't really know what is the whole set of commands I have sent.
I saw too late that ASUS provide an unlocker tool. The problem was I was under an official but too recent android version to run this tool.
Some information :
A few month ago, I had this issue, and, by insisting I managed to boot normally and fully on android. At this time, I told myself that I will never switch off the device, but, this happened !
So, today I need your help :
Do you know how I can get rid of this bootloop ?
Does the screenshot is really what is called the bootloader ? (even with no volume +/- control ?)
I saw it exists a tool named "ASUS Flash Tool" but it needs "raw" images and not zips like we can download on the ASUS website. Does anybody know what are this raw files made of, and how I could eventually convert a zip to this raw format ?
If anybody have original backups of the TF303k, they may be very helpful for me !
Thanks for any help or advices ! :fingers-crossed:
An ultime little up... :crying:
Edit : Or if anybody have a TF303K, if you can send me a backup of your system partitions, I'll really apreciate it ! :fingers-crossed:
virtcs said:
Hi,
I appeal for the community help to try to get rid of my tablet "boot-loop" !
Here is the situation today :
My tablet no more boots on Android. It starts on what I believe is the bootloader (see screenshot) but this original bootloader doesn't allow me (through volume +/-) to choose between the usual recovery/boot/reboot choices. I can't do anything except a long press on power to switch off the device. On this "bootloader" screen, I fortunately can send fastboot commands.
What I can do :
- fastboot reboot => ok, the device reboots and comes back to the same screen
- fastboot continue => most of the time (if not always) it does nothing, but some few times (I can't manage when exactely) it continues the boot and goes to the loading screen with ASUS image and loading spinner, but the boot doesn't go further : I let it a full night and the device was still on this screen.
- fastboot flash boot boot.img => ok. The image (from a zip downloaded on ASUS website asus.com/Tablets/ASUS_Transformer_Pad_TF303K/HelpDesk_Download ) is flashed successfully.
- fastboot erase xxx => ok, clean the partition
- fastboot oem unlock => FAILED (remote: Invalid signature, fail to unlock!!)
How I finally get here :
I wanted to root/unlock my device, except I may acted as a newbee ! Finally, today, I don't really know what is the whole set of commands I have sent.
I saw too late that ASUS provide an unlocker tool. The problem was I was under an official but too recent android version to run this tool.
Some information :
A few month ago, I had this issue, and, by insisting I managed to boot normally and fully on android. At this time, I told myself that I will never switch off the device, but, this happened !
So, today I need your help :
Do you know how I can get rid of this bootloop ?
Does the screenshot is really what is called the bootloader ? (even with no volume +/- control ?)
I saw it exists a tool named "ASUS Flash Tool" but it needs "raw" images and not zips like we can download on the ASUS website. Does anybody know what are this raw files made of, and how I could eventually convert a zip to this raw format ?
If anybody have original backups of the TF303k, they may be very helpful for me !
Thanks for any help or advices ! :fingers-crossed:
Click to expand...
Click to collapse
Exactly the same here!! Any news? How to fix this 'always boot to fastboot but I can still get into system by using fastboot boot boot.img command'?!
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!
fastboot oem reset-dev_info
Click to expand...
Click to collapse
Yeah, this did it for me too! Thanks a lot!
How did you get knowledge of this flag?
Je\/er
hackwerk said:
Exactly the same here!! Any news? How to fix this 'always boot to fastboot but I can still get into system by using fastboot boot boot.img command'?!
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!
Click to expand...
Click to collapse
Jever2000 said:
Yeah, this did it for me too! Thanks a lot!
How did you get knowledge of this flag?
Je\/er
Click to expand...
Click to collapse
If you are thankful, please press Thanks button under my posts
The Tampered Flag is an OEM specific thing, and all fastboot oem commands are specific per brand and type.
As the ASUS TF303K is a clone of the (ASUS) Google Nexus 7 (2013)(Flo), I read ALL stuff on the Nexus 7 (2013) everywhere. You'll see this command a lot.
Unfortunately the Nexus is unlockable (fastboot oem unlock), and ours is NOT in any way.
One of the best posts is this one.
Still hope ANY one can help us unlocking the bootloader, or help us on how to flash another ROM (Nexus 7 2013?) to our device using Qualcomm tools (QPST / QFil / MiFlash etc etc)? :'(
hackwerk said:
EDIT 1: This ASUS specific fastboot command seems to be a big life saver because it RESETS the Tampered Flag to False: "fastboot oem reset-dev_info"! Hurray!
Click to expand...
Click to collapse
It didn't do the job for me
I still get an endless waiting screen when fastbooting boot.img.
Can anybody would accept to dump its partitions ? (system, boot, and recovery) ? This should do the trick and may not require root ! Thanks so much !
Stuck on splash screen "Your device has been unlocked and can't be trusted."
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
gabrce said:
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
Click to expand...
Click to collapse
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
mrmazak said:
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
Click to expand...
Click to collapse
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
gabrce said:
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
Click to expand...
Click to collapse
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
mrmazak said:
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
Click to expand...
Click to collapse
Thank you but "fastboot get prop" is not the right command. If anybody has a solution it will be awesome.
Download the latest full ota package for your device (around 2gb)
Extract the contents of the update. App using huawei firmware extractor and
Flash
kernel
Ramdisk
Recover ramdisk
System and cust images using fastboot
After that flash the correct version of twrp for your device and then install images of version and vendor(found in update. App file) partitions using twrp.
.
This method worked for me
It didn't worked for me... Do you know any other method?
I tried many TWRP versions but the phone doesn't boot into TWRP...
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).
Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.