Official Global JoyUI 11 (Android 10) - SKYW2004221OS00MQ0 Factory OTA & Boot Image
Finally, Android 10, JoyUI11 is released officially yesterday. Thanks so much again to @ripiad, he shared me the big new version and I uploaded those(full update & boot image) at here.
If anyone receives the global EEA android 10 and shares it to me, I will upload that too.
Enjoy your BS.
wga0 said:
Finally, Android 10, JoyUI11 is released officially yesterday. Thanks so much again to @ripiad, he shared me the big new version and I uploaded those(full update & boot image) at here.
If anyone receives the global EEA android 10 and shares it to me, I will upload that too.
Enjoy your BS.
Click to expand...
Click to collapse
Can i update on locked bootloader and how? Sorry for asking dumb question
kumar abhishek said:
Can i update on locked bootloader and how? Sorry for asking dumb question
Click to expand...
Click to collapse
Put the update.zip file into /sdcard/ota/ directory, then dial *#*#1027#*#*. You don't need to unlock the bootloader only for that. You can find details from other thread.
Yep found it in another thread and updated sucessfully. Many thanks
Help joyui11
help I updated to joyui 11 with local update procedure but the lock does not work does not save the password even fingerprints. I'm without shermo locks you can help me thanks
babboooo said:
help I updated to joyui 11 with local update procedure but the lock does not work does not save the password even fingerprints. I'm without shermo locks you can help me thanks
Click to expand...
Click to collapse
It says it's compatible to android 9, reset is not required, but it's big upgrade. Plz backup and disable all locks before upgrade.
kumar abhishek said:
Can i update on locked bootloader and how? Sorry for asking dumb question
Click to expand...
Click to collapse
Hi bro i updated but thats not joy ui11
Can u share with me that threads..
.
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
cjscratch said:
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
Click to expand...
Click to collapse
Try hold volume down+power button wait until device restart
It will back to your previous version
cjscratch said:
hello, how long does the update in OTA take, because I am stuck on the start screen "black shark born to complete" need help please
Click to expand...
Click to collapse
If something goes wrong, and your phone doesn't booted, just try to reboot several times. It will change the slot automatically after several boot failure, and will be back to before the update. Or boot into the bootloader and change the slot manually, 'set active_slot x'. x is a or b. use a slot marked as successful.
Official Global JoyUI 11 (Android 10) - SKYW2004221OS00MQ0
hi friends I have tried several times to start joyui11 the problem in the start screen flashes several times and asks you to reset joyui 11 when I managed to start it anyway I noticed many bugs and system settings problems such as (lock screen) etc. that in my opinion I am not from the same region at the end I went back with my region with automatic update 01mp3-01mp4-01mp5 besides it does not update anymore I am with bootloader unlocked with joyui11 it blocks you bootloader if you see developer settings it is blocked maybe because new android 10? it's very nice however the new interface changes little from miui. I hope it arrives for my region of Italy thanks for the support #vga0
Invalid MMI code
wga0 said:
Put the update.zip file into /sdcard/ota/ directory, then dial *#*#1027#*#*. You don't need to unlock the bootloader only for that. You can find details from other thread.
Click to expand...
Click to collapse
Hey, several of my blackshark2 friends are not able to dial *#*#1027#*#*. It will prompt Connecton problem or invalid MMI code.
Fyi, I did successfully updated to Joy Ui 11 without issues, but not my friends.
Do you have solutions for that?
The upgrade worked flawlessly aand I am in awe in how much better it is now compared to the Android 9 one! One thing tough is not working; All the options for the light settings are grayed out. I was hoping that the side lights would finally work properly as a notification LED. Anyone else having this issue?
hello there,
do we still get stockish experience on the new joyui 11 update?
Attention skyw2004221os00mq0 ota
after various tests and various reboots joyui11 works only with blocked bootloader I discovered this I did not understand why the new update did not work it crashed and the system did not work well then I tried to block bootloader so starting from 1mp5 to 0mq0 to run no startup problem and now fingerprints also work.attention to update with unlocked bootloader
So joyui11 shifts from stock to miui as base. Would there be a stock variant of joyui11?
babboooo said:
after various tests and various reboots joyui11 works only with blocked bootloader I discovered this I did not understand why the new update did not work it crashed and the system did not work well then I tried to block bootloader so starting from 1mp5 to 0mq0 to run no startup problem and now fingerprints also work.attention to update with unlocked bootloader
Click to expand...
Click to collapse
Bro how do you lock the bootloader again? In any firmware (Mp3, mp4, etc) my bootloader stills unlocked. Only in the first time that I try JUI11 goes blocked
#Diex_7
it is better to start factory reset from settings
1 go back to mp3 depends on your region (global or EEA) so (0mp3 or 1mp3)
2 have the system perform automatic updates to the last
3 use pc adb and fastboot
4 enable usb debug developer settings
5 use pc command (adb reboot bootloader) and confirm usb debug notification
6 use pc adb command (fastboot flashing lock) gives you okay
7 press power button the phone asks you to reset foul otherwise you can't go on
8 once the system has started, activate developer settings and deactivate unlock oem
9 download joyui11 * # * # 1027 # * # * install and you're done only with locked bootloader does android 10 joyui11 work
babboooo said:
#Diex_7
it is better to start factory reset from settings
1 go back to mp3 depends on your region (global or EEA) so (0mp3 or 1mp3)
2 have the system perform automatic updates to the last
3 use pc adb and fastboot
4 enable usb debug developer settings
5 use pc command (adb reboot bootloader) and confirm usb debug notification
6 use pc adb command (fastboot flashing lock) gives you okay
7 press power button the phone asks you to reset foul otherwise you can't go on
8 once the system has started, activate developer settings and deactivate unlock oem
9 download joyui11 * # * # 1027 # * # * install and you're done only with locked bootloader does android 10 joyui11 work
Click to expand...
Click to collapse
Sorry for late answer and thank you for commenting. JoyUI11 changes its base and has lots of incompatible settings. Reset before/after, restore/disable all customs,locks are recommended strongly, and OEM unlock is also seemed as bug because MIUI and stockUI has completely different unlock management
Skyw2004221os00mq0 ota
it's true however there are some bugs that can be fixed in the updates.
the battery consumes more on 0mq0 games sometimes like COD skip screen and you have to re-enter the side led strips are off the s sign on developer settings some functions do not go the brightness when you unlock becomes strong however a great job is a real adapted miui stockui was boring now you can also install apk miui
Related
Hi,
I am trying to officially unlock for two weeks now.
I just get stuck at 50 with the Cannot Verify issue.
Opened a bug report here. Would be nice, if some of you with the same issues could support it.
http://en.miui.com/thread-364400-1-1.html
Thanks!
playitlouder said:
Hi,
I am trying to officially unlock for two weeks now.
I just get stuck at 50 with the Cannot Verify issue.
Opened a bug report here. Would be nice, if some of you with the same issues could support it.
http://en.miui.com/thread-364400-1-1.html
Thanks!
Click to expand...
Click to collapse
just don't make any change on your phone and your mi account for about a week
Just wanna clear things up! Kate can be officially unlocked,
I had already done that way back in July.
Steps taken by me.
1. Boot into EDL mode
2. Flash Global Developer Rom
3. Login to MI account on the phone
4. Boot into Fastboot mode
5. Unlock with official tool
Tried everything and now flashing Dev Rom in EDL Mode
Still no more than 50%
I have unlock permission but fails at 50%.
Gonna wait for a few days before trying it again.
Apparently you can flash TWRP/root via this method without unlock the BL.
http://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
karkand said:
just don't make any change on your phone and your mi account for about a week
Click to expand...
Click to collapse
Tried that, doesn't work.
Also tried logging into an different Mi account. "Couldn't verify device"
wtfjajaja said:
Just wanna clear things up! Kate can be officially unlocked,
I had already done that way back in July.
Steps taken by me.
1. Boot into EDL mode
2. Flash Global Developer Rom
3. Login to MI account on the phone
4. Boot into Fastboot mode
5. Unlock with official tool
Click to expand...
Click to collapse
I updated to Global Developer with the updater app.
Had to reflash the rom with EDL, because it didn't accept my passcode any more (two weeks ago).
Still doesn't work.
My bug report has attracted a few people with similar issues: http://en.miui.com/thread-364400-1-1.html
playitlouder said:
Tried that, doesn't work.
Also tried logging into an different Mi account. "Couldn't verify device"
Click to expand...
Click to collapse
Have you removed your lockscreen? fingerprint, pin, pattern, etc?
Please ensure that you've fulfill the requirements, because that point above is usually forgotten when doing this.
Kindly check it again.
Thanks.
wtfjajaja said:
Just wanna clear things up! Kate can be officially unlocked,
I had already done that way back in July.
Click to expand...
Click to collapse
Are you really using Kate device? Delivery outside Taiwan began 26th of August at geekbuying, AFAIK. When you bought it directly in Taiwan:
Was it originally equipped with Android 5? Which ROM did you use when you unlocked it? Where can we download it?
We other people received our RN3Pro Special Edition already with Android 6 installed, and after flashing all ROM fitting onto Redmi Note 3 Special Edition (not Redmi Note 3 Qualcomm China, not Redmi Note 3 Qualcomm Global) I *know* there is no working solution except unofficial bootloader unlock. For now, because I'm hoping Xiaomi is working on this issue.
karkand said:
Have you removed your lockscreen? fingerprint, pin, pattern, etc?
Please ensure that you've fulfill the requirements, because that point above is usually forgotten when doing this.
Kindly check it again.
Thanks.
Click to expand...
Click to collapse
Doesn't help.
Stayed on the same MIUI Version for over a week.
Messaged MI Support now, as my bug report with almost 30 likes doesn't even get recognized.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Avoid and pass by a fool and a madman
I guess we have to somehow unlock the bootloader again! when I switch slot and reboot the bootloader it says locked on Android 10 slot, and unlocked on Android 9 slot.
I tried :
Code:
fastboot oem bs_unlock
Code:
fastboot oem unlock
Neither worked I also tried MI unlock tool but it still can't unlock it. The only way was to reboot the bootloader into Android 9 slot then flash the patched boot.img but the phone won't load the OS it just keep rebooting very fast. (this is also happens when tring to flash stock boot which I pulled using TWRP)
I had to hold both volume keys buttons + power while connect it to the PC "USB. must be connected" and when it reboot into black screen then I hold volume down key + power for around 60 seconds to boot into bootloader again.
I will try again tomorrow with different approach.
Avoid and pass by a fool and a madman
wga0 said:
Yes.. MIUI has completely different unlock management from JoyUI. I didn't try it yet, but if JoyUI11 goes to perfect same unlock management of MIUI, I guess we need to sign in MI account, submit unlock request, waiting 360 or 720 hours, then we could receive the unlock key/permission. I didn't think they change it that much.... they could change the dm-verify or something else also... but, if they didn't change it so much, I guess we maybe can use the unlock key in Android 9 bootloader. (Certain MiUI devices have no key to unlock the bootloader even if we know the unlock command...)
I believe you will find the way. Good luck...
Click to expand...
Click to collapse
I tried using MUI but it doesn't work yet, maybe it future, but surely they changed the way of unlocking the bootloader, maybe they want to make it simpler so they can use MIUI unlock tool or maybe they want to make it harder since the unlocking code is available online :silly:.
I also tried to root it using Magisk manager while on Android 9 slot, but that didn't work either.
Other things to note, after updating to JoyUI 11 the phone takes significantly more time to boot, also you need to factory reset your phone to be able to boot it. Moreover, don't like the feel of the UI, the OS feel heavy and strangely some stock apps have ads in it. On top of all that, it is very difficult to root it right now if even possible at the moment.
Therefore, I don't recommend anyone to upgrade to Joy UI 11, and wait for further updates.
To anyone needs to downgrade Black Shark 2 Pro go to the bottom of the first post.
Thanks @wga0, I will let you know if I find anything new.
thank u so much im take maybe 1 month about this comm thx
wga0 said:
Avoid and pass by a fool and a mthank u so much im take maybe 1 month about this comm thxadman
Click to expand...
Click to collapse
thank u so much im take maybe 1 month about this comm thx
Hi everybody. Im a owner of a newly released "Redmi Pad" wifi only (4/128GB) model
It's a chinese version of
Redmi Pad | Xiaomi Global
Introducing Redmi Pad with a 90Hz buttery smooth display, High-performance MediaTek Helio G99 and a long-lasting 8000mAh (typ) battery.
www.mi.com
I've searched the whole of xda for this new model.
Im trying to unlock bootloader and having some problems.
I've been rooting/modding phones since galaxy tab(7) original with the help of XDA.
I already have installed (working)
1) usb driver
2) adb driver
3) fastboot driver
4) associated pad with MI account
***** when i connect to unlock the bootloader in fastboot mode, the device is NOT recognize/register
any help is appreciated. I'd gladly answer any questions regarding the new device as well.
Thanking in advance
--------------------------------------EDIT-----------------------------------
Updating on my newly unlocked (only the official version worked after a 7day wait), global Miflashed ROM...
Special thanks to NOSS8
Rambo Ninja said:
Hi everybody. Im a owner of a newly released "Redmi Pad" wifi only (4/128GB) model
It's a chinese version of
Redmi Pad | Xiaomi Global
Introducing Redmi Pad with a 90Hz buttery smooth display, High-performance MediaTek Helio G99 and a long-lasting 8000mAh (typ) battery.
www.mi.com
I've searched the whole of xda for this new model.
Im trying to unlock bootloader and having some problems.
I've been rooting/modding phones since galaxy tab(7) original with the help of XDA.
I already have installed (working)
1) usb driver
2) adb driver
3) fastboot driver
4) associated pad with MI account
***** when i connect to unlock the bootloader in fastboot mode, the device is NOT recognize/register
any help is appreciated. I'd gladly answer any questions regarding the new device as well.
Thanking in advance
Click to expand...
Click to collapse
Maybe because"Make sure your device can connect to the internet using mobile data."
https://new.c.mi.com/global/post/101245
there are other tools for Media Tek device.
https://www.technobuzz.net/unlock-bootloader/
Do a search.
NOSS8 said:
Maybe because"Make sure your device can connect to the internet using mobile data."
https://new.c.mi.com/global/post/101245
there are other tools for Media Tek device.
https://www.technobuzz.net/unlock-bootloader/
Do a search.
Click to expand...
Click to collapse
As far as using mobile data, MI account already recognized my device & successfully passed the "Add account and device"
During unlocking, I made sure to open a hotspot from the phone # which is registered with the MI account.
*edit: it's a Wifi only Pad.. so.. though I do have a choice of Wifi or hotspot during the unlocking process
I have also tried the exact unlocking method from technobuzz link you have provided. Thank you for sharing.
Maybe:
https://mobilewithdrivers.com/unlock-bootloader/xiaomi-mi-pad-4-plus-wi-fi-64gb-4gb-ram
NOSS8 said:
Maybe:
https://mobilewithdrivers.com/unlock-bootloader/xiaomi-mi-pad-4-plus-wi-fi-64gb-4gb-ram
Click to expand...
Click to collapse
I was ecstatic!!! when i first saw the pic
I've got this.. pic with an unlock. Does it mean bootloader is unlocked?
if i choose the second option and enter WiFi information, then choose the first option, it boots as though factory reset has been done (goes through the initial setup) BUT all the data is there. and status shows it's STILL LOCKED.
Now the 2nd time, i let the locked icon stay and boot into fastboot and try installing TWRP, it failed :-(
this is the error i get:
fastboot flash recovery twrp1.img
Sending 'recovery' (33812 KB) OKAY [ 0.842s]
Writing 'recovery' FAILED (remote: 'No support by lock control')
fastboot: error: Command failed
What now?
Thank you for any/all the help i can get
Rambo Ninja said:
I was ecstatic!!! when i first saw the pic
I've got this.. pic with an unlock. Does it mean bootloader is unlocked?
if i choose the second option and enter WiFi information, then choose the first option, it boots as though factory reset has been done (goes through the initial setup) BUT all the data is there. and status shows it's STILL LOCKED.
Now the 2nd time, i let the locked icon stay and boot into fastboot and try installing TWRP, it failed :-(
What now?
Thank you for any/all the help i can get
Click to expand...
Click to collapse
The bootloader is locked.
1st line activate the device
2nd line Wifi parameters
Can you post the Mi Pad version?
settings/about it or my phone/version.
Example:
22081283G, 22081283C
NOSS8 said:
Can you post the Mi Pad version?
settings/about it or my phone/version.
Example:
22081283G, 22081283C
Click to expand...
Click to collapse
It's a 22081283C, NOSS8
Thank you for trying to help me out
Try:
https://mifirm.net/downloadfile/55
https://mifirm.net/blog/mi-unlock-tool-bypass-otp-sms
NOSS8 said:
Try:
https://mifirm.net/downloadfile/55
https://mifirm.net/blog/mi-unlock-tool-bypass-otp-sms
Click to expand...
Click to collapse
Thank you for sharing me the links, NOSS8. I have tried that method too but to no avail.
I got the link through
Mi Unlock Tool mod bypass OTP SMS
Hi everybody Today I introduce a mod of Mi Unlock tool which is a patch to remove bypassing SMS OTP when logging in At this point, the original Xiaomi unlocking tool requires SMS OTP verification after logging in. So if you can't access the...
forum.xda-developers.com
the chinese version is pretty restricted.. but i've managed to download & install firefox, apkmirror and my favorite game on it. also can watch videos on youtube.. so im content w/ what i can do the tablet thus far. i hope soon, XDA will dedicate a forum for this model so many others like me can enjoy a rooted and custom ROM/s..
once again, thanks for trying to help me out
Rambo Ninja said:
Thank you for sharing me the links, NOSS8. I have tried that method too but to no avail.
I got the link through
Mi Unlock Tool mod bypass OTP SMS
Hi everybody Today I introduce a mod of Mi Unlock tool which is a patch to remove bypassing SMS OTP when logging in At this point, the original Xiaomi unlocking tool requires SMS OTP verification after logging in. So if you can't access the...
forum.xda-developers.com
once again, thanks for trying to help me out
Click to expand...
Click to collapse
If you use Mi Unlock what happens?
NOSS8 said:
If you use Mi Unlock what happens?
Click to expand...
Click to collapse
upon connecting the cable to the device (in a fastboot mode) the Unlock tool does NOT see it as being attached eventhough the bootloader drivers are there and shows that device is connected. when i type "fastboot devices" my device shows up as well
*the global Mi Unlock tool takes me to the account info (where i can change password/email/other details
i've tried various versions of MI Unlock tool.. (including batch unlock ones) all give the same result. Just like to add.. i have successfully unlocked Mi Note 7 using the Mi Unlock tool (at the time I didnt have to wait eventhough there was supposedly a 7 day wait)
Rambo Ninja said:
upon connecting the cable to the device (in a fastboot mode) the Unlock tool does NOT see it as being attached eventhough the bootloader drivers are there and shows that device is connected. it is confirmed by the sound when plugging/unplugging
*the global Mi Unlock tool takes me to the account info (where i can change password/email/other details
i've tried various versions of MI Unlock tool.. all give the same result. Just like to add.. i have successfully unlocked Mi Note 7 using the Mi Unlock tool (at the time I didnt have to wait eventhough there was supposedly a 7 day wait)
Click to expand...
Click to collapse
Have you enabled USB debugging?
Are you using a usb 2 port?
Is the Mi pad usb port 2 or 3?
The Mi Unlock folder must be at the root of the hard drive.
Try running Mi Unlock as administrator.
EDIT:
ANOTHER TOOL
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
Im so happy, NOSS8! Thank you ever so much!
moving the folder to C:\ must have done the trick AND running it as admin.
there's a 120hr wait then what recovery do i install when there are no officially supported ROMs either
Rambo Ninja said:
Im so happy, NOSS8! Thank you ever so much!
moving the folder to C:\ must have done the trick.
there's a 120hr wait then what recovery do i install when there are no officially supported ROMs either
Click to expand...
Click to collapse
Glad it worked but if there is no recovery or rom for this model, why unlock the bootloader?
You can install a stock Global or other rom but without locking the bootloader and rooting to have a certified play store.
https://xiaomirom.com/en/rom/redmi-pad-yunluo-china-fastboot-recovery-rom/
NOSS8 said:
Glad it worked but if there is no recovery or rom for this model, why unlock the bootloader?
You can install a stock Global or other rom but without locking the bootloader and rooting to have a certified play store.
https://xiaomirom.com/en/rom/redmi-pad-yunluo-china-fastboot-recovery-rom/
Click to expand...
Click to collapse
yes, you do have a point. I'll just have to wait it out.
in the meantime, I'll do what you have suggested..
i have the global version. it does not support themes. Which region has themes support?
iloyski said:
i have the global version. it does not support themes. Which region has themes support?
Click to expand...
Click to collapse
I have just managed to unlock n install global now. It doesn't have "multiple users" support as opposed to Chinese version
Repost
How to delete this?
Rambo Ninja said:
I have just managed to unlock n install global now. It doesn't have "multiple users" support as opposed to Chinese version
Click to expand...
Click to collapse
the global rom has lower version compared to chinese rom. maybe that's why?
does the chinese rom support themes?
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .