Question about OnePlus 8T KB2003_11_F.15 bootloader - OnePlus 8T Questions & Answers

I'm running rooted KB2003_11_F.15 with Magisk-Delta + USNF.
Just asking if it is possible to remove warning about unlocked bootloader (Orange warning) or re-lock bootloader without losing data ? I remember that with C33/C35 android 12 there wasn't any warnings on my system even though I rooted it.
I might remember wrong but so is it possible to flash something from extracted payload.bin (latest F15) to remove that warning?
Whats the partition where this warning resides and what are the possibilities to remove the warning and 5sec pause from boot?

Sorry, I didn't look too well... There's an answer to my question:
[GUIDE] ROOT KB2003 OOS13
OnePlus 8T OOS13 (KB2003_11_F.13) Bootloader must be unlocked Instructions: 1: Run CMD and reboot to bootloader with "adb reboot bootloader". 2: Run CMD and write "fastboot flash boot magisk_patched-25200_4cwAM.img". Ready! You're rooted.
forum.xda-developers.com
It's possible at the moment as I understood.

kopsu said:
It's possible at the moment as I understood.
Click to expand...
Click to collapse
By flashing bootloader image (abl.img) from OOS12 or OOS13 beta.
[GUIDE] ROOT KB2003 OOS13
OnePlus 8T OOS13 (KB2003_11_F.13) Bootloader must be unlocked Instructions: 1: Run CMD and reboot to bootloader with "adb reboot bootloader". 2: Run CMD and write "fastboot flash boot magisk_patched-25200_4cwAM.img". Ready! You're rooted.
forum.xda-developers.com

Related

[GUIDE] How to install Global Android 10 into TA-1054 (Need unlocked bootloader)

To Content farms like GETDROIDTIPS: DO NOT REPOST OR REFORM MY TOPIC ON YOUR WEBSITE WITHOUT INFORMING ME!
Recent Android 10 update fixed support for TA-1054 hardware, so we can do global conversion right now. Anything older will break the phone and you have to disassemble the phone and utilize EDL to unbrick it (test point indicated below).
Therefore, we have to install Android 10 directly, but for some reason, the bootloader will be reverted back to locked state, so it has to be unlocked again via some tricks.
This guide will tell you how to install Android 10 into TA-1054. If you don't have unlocked bootloader, you have to unlock it first.
If you don't have unlocked bootloader, you may need to look for Global conversion service online.
PLEASE MAKE SURE YOU HAVE BACKED UP EVERYTHING BEFORE YOU DO SO.
Step 1: Change SKUID
To change SKUID, you need to ensure your phone is rooted, or your phone booted to TWRP (official TWRP for Nokia 6.1 is OK to use) to allow us change SKUID written in deviceinfo partition.
If you booted to TWRP via these commands under Download mode:
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.4.0-0-PL2_sprout.img
Once phone booted to TWRP (even if stuck at splash screen is OK), then you can dump the devceinfo and securefs partition:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/deviceinfo of=/tmp/deviceinfo.img
adb shell dd if=/dev/block/bootdevice/by-name/securefs of=/tmp/securefs.img
adb pull /tmp/deviceinfo.img
adb pull /tmp/securefs.img
The reason why I suddenly mentioned securefs partition is, it contains Widevine DRM key that related to video-on-demand services like Netflix.
You have to back it up just in case.
Then follow this guide to edit SKUID written in deviceinfo into 600WW:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520
Once SKUID changed, write the deviceinfo partition back:
Code:
fastboot flash deviceinfo deviceinfo_600WW.img
After SKUID changed, you'll find the launcher becomes weird, which is expected behavior.
Step 2: Install Android 10 full OTA
Please download it from here:
https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
And rename it into PL2-9999-0-00CN-B99-update.zip. Copy it to root directory of internal storage, and dial *#*#874#*#* to install it.
Once install complete, you might be asked for erasing userdata, just erase it.
Step 3: Unlock bootloader again (optional)
If you think it's OK to use Android 10 without unlocked bootloader, then that wraps up the procedure and enjoy it.
But if you want to unlock the bootloader again, you have to follow some trick.
Once the phone booted to welcome screen again, power it off, boot to Download mode by using this command:
Code:
fastboot oem alive
And connect the powered off phone to PC, it will be booted to Download mode again.
Next, check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot-bootloader
Once slot changed, you'll be switched back to the previous version with unlocked bootloader.
Now you have to downgrade the abl/xbl to allow it being unlockable again.
Now check which slot is Chinese Nokia 6.1 Android build installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Code:
fastboot flash unlock unlock.bin
fastboot flashing unlock_critical
(confirm bootloader unlock on the phone)
(while waiting for erasing, execute this immediately)
fastboot oem alive
fastboot flash unlock unlock.bin
fastboot oem unlock-go
(confirm unlock again)
(while waiting for erasing, execute this immediately)
fastboot oem alive
After we unlocked the bootloader, we have to switch back to previous Chinese Nokia 6.1 Android build to reinstall Android 10.
Check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot
Repeat the step 2 to reinstall Android 10 Full OTA, and enjoy Android 10 on Chinese Nokia 6.1 with unlocked bootloader.
Under Android 10, if bootloader unlocked, you'll lose Widevine DRM key permanently, that's why I asked you to backup securefs partition.
Is the shorting wires solution to unbrick the phone or to change china to global version?
Ok, pins shorted. Whats now?
Spacepl said:
Ok, pins shorted. Whats now?
Click to expand...
Click to collapse
flash nbo Nokia 6 2018 firmware with OST LA
Sent from my TA-1054 using Tapatalk
juwelrana091 said:
flash nbo Nokia 6 2018 firmware with OST LA
Click to expand...
Click to collapse
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
J0NS3N said:
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
Click to expand...
Click to collapse
Is your phone already bricked? Then shorting the pins will trigger EDL mode and then you can use Qualcomm tools to flash the abl and xbl. That can make the phone usable again, but yes you will still need to flash the CN firmware as Global will not be usable on this device.
help
hello i tried shortening all 4, or one of the 2 sets but it did not trigger EDL, my phone is stuck in Download mode as soon as it turns on, my pc only recognizes it as Fastboot device, my bootloader is locked, i have the exact same model, can you help me??
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
vanechka25 said:
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
Click to expand...
Click to collapse
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
hikari_calyx said:
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
Click to expand...
Click to collapse
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
vanechka25 said:
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
Click to expand...
Click to collapse
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
hikari_calyx said:
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
Click to expand...
Click to collapse
Thank you very much for the answer. You clarified a lot of things!
Downgrade from android 10 to android 9
vanechka25 said:
Thank you very much for the answer. You clarified a lot of things!
Click to expand...
Click to collapse
Hey can you help me for downgrading android 10 to android 9 with locked bootloader .i want to unlock bootloader to downgrading to android 9 and also i am facing wifi disconnected and mobile restarting issues .also what this ss show is that bootloader locked or unlocked
hikari_calyx said:
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Click to expand...
Click to collapse
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
21prods said:
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
Click to expand...
Click to collapse
Yes it will work on both Nokia 6.1 and 7.
hikari_calyx said:
Yes it will work on both Nokia 6.1 and 7.
Click to expand...
Click to collapse
Thank you
Hello, Everyone​​My Nokia 6.1 2018 Hmd Global TA-1054 with Build number - 00WW_3_270 will receive a global system update and security update. Will this method described above work for me? So you will get a global version of version 10 or have to wait. My latest security fix for Android is from October 1, 2018. Can you explain in detail what steps to take to make the updates.​

[Realme 5i] HOW TO unlock bootloader && access fastboot

Hello,
Did anyone managed to unlock bootloader on Realme 5i ?
I flashed the latest Android 10 firmware from RealMe website, everything went ok, but now I want to unlock bootlader to root the device, and it seems that nothing helps.
Please help, thanks
how to unlock the bootloader in Realme 5i RMX2030
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
G0bl1n said:
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
Click to expand...
Click to collapse
I've done the in-depth test and it's on the Fastboot screen but when I type fastboot flashing unlock in a command window it just shows me the help text for fastboot, which doesn't show any command or option for either flashing or unlock, so how can I get it to work if those aren't valid commands?
fastboot devices shows my phone, so the device is recognised.
EDIT: I'm still on Android 9 A.15. I understand that there's no unlocked for Android 10 yet.
EDIT: Nevermind. I was using adb/fastboot from the link in this guide, which is v1.3 https://www.ytechb.com/how-to-root-realme-5i-and-unlock-bootloader/
After I updated to minimal v1.43 from here it worked https://androidmtk.com/download-minimal-adb-and-fastboot-tool
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
How did you downgraded to colour os 6?
I'm trying to root my realme 5i that i upgraded to 10.
Can you help me?
M. Farhad said:
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
Click to expand...
Click to collapse
what's the next step

How to Remove Warning Bootloader Unlocked Message

Recently rooted my new Zenfone 7. Is it possible to remove Bootloader unlocked Warning message at the start up of the system? Thanks for an answer.
re-lock the bootloader
Boot into fastboot, then send this command from your pc.
fastboot oem asus-lock
how did you get root to work? I followed the instructions listed and it would not work for me.
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Jkm15 said:
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Click to expand...
Click to collapse
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Jkm15 said:
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Click to expand...
Click to collapse
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Joeb2000 said:
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Click to expand...
Click to collapse
Had locked bootloader on device with magisk. Result is fastboot loop =|
Same wish here. that warning screen is ugly....

relock bootloader but no OS help please

hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz
in case anyone has the same problem.
i did solve it by flashing the (raw) firmware via fastboot ( Flash_AFT method )
M-772007 said:
hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz
Click to expand...
Click to collapse
There are new guides on how to get volte if you want to try again.
[Guide] Easy method to Enable Volte (with root) on Tmobile and maybe other networks on Android 11 and maybe 10
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around. Then once you do that, follow these directions, What I did was manually entered all of these setprop commands below, on the...
forum.xda-developers.com
This is one but there are others if you need the help.
After relock bootloader i can send phone to warranty?
I tried to relock the phone with the command "fastboot oem asus-lock", but it shows "waitting for any device" and my phone just sit there and do nothing..
Any other method to relock the Zenfone 7 pro?
M-772007 said:
hello,
i did unlock the bootloader for my zenfone 7 pro
and installed twrp recovery then rooted via magisk
cuz I wanted voLTE but it didn't work for me so I wanted to be back to stock
I relock the phone using fastboot command
fastboot oem asus-lock
it did relock my phone
but there is no OS nor Recovery !
when I power my phone on the fastboot UI appears. even if I select recovery nothing changes. opens fastboot only
how to re install the firmware ? help plz
Click to expand...
Click to collapse
I believe that relock is impossible and but to make the device recovery to installed status of stock rom keeping with unlock bootloader.
Please see my post. May make it help or not.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com

Sony Xperia L3 install Xposed Framework.

How do i install framework on Android 8.1? I have my bootloader locked and my root to. I have check and my phone can be unlocked, i have downloaded fastboot. I got to https://mobilewithdrivers.com/unlock-bootloader/sony-xperia-l3-32gb-3gb-ram i got it into fastboot mode but no commands works, fastboot flashing unlock, fastboot oem unlock. Unknown command, command not allowed.
Do i need TWRD? i have my bootloader locked so i guess it is not possible?
What is TWRD? either use Riru 25.4.4 and EdXposed with older Magisk, or LSPosed with latest Magisk.
Oldschool297 said:
Do i need TWRD? i have my bootloader locked so i guess it is not possible?
Click to expand...
Click to collapse
Did you succeed at unlocking bootloader?

Categories

Resources