Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I had the same issue you don't need to toggle the option on marshmallow. The error looks like you need to do a sudo fastboot if your using linux.
The only other thing to remember is you need to remove the factory reset protection (frp) see here http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
Just because that option is not available does not mean your bootloader is locked, plus you can unlock using ADB.
Just enable usb debug only
Sent from my KIW-L24 using XDA-Developers mobile app
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
This option is not there in Marshmallow. not sure if there is still a way to unlock as this option itself is not there...try enabling USB debugging couple of times and see if it prompt you for authorisation. if it does, you can still do the required things.
did u unlocked bootloder???
did u unlocked bootloder???
i m having same problem
princereshim said:
did u unlocked bootloder???
i m having same problem
Click to expand...
Click to collapse
What problem?
no oem unlock option
no oem unlock option
in developer option
princereshim said:
no oem unlock option
in developer option
Click to expand...
Click to collapse
If you are in lollipop it will be there but if u r on marshmallow then it wont be there. Just enable usb debugging and you r good to proceed.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Harsh007agrawal said:
, I always get stuck at
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Click to expand...
Click to collapse
Try Chinese site to get same.
And which rom are u sing could you give me link to latest twrp and rooting files needed
Harsh007agrawal said:
And which rom are u sing could you give me link to latest twrp and rooting files needed
Click to expand...
Click to collapse
See the pinned post in the guides tab... It has all the information and links
Sent from my KIW-L21 using Tapatalk
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Harris Aamir said:
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Click to expand...
Click to collapse
Just enable the usb debugging if you r on stock mm. Try changing the usb port amd see if it work
seams rolling back is the only solution ! .
Romiui said:
seams rolling back is the only solution ! .
Click to expand...
Click to collapse
Why what happened?
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Tamoghna Chowdhury from Android.stackexchange TOO NEW CAN'T POST LINKS said:
To unlock the boot loader you need to have the ADT with all the packages installed and configured.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
Download Modaco’s Superboot files and save them to your computer.
Once downloaded, extract it by right clicking and extract all.
On your phone, click on Settings > Developer Options > Turn USB Debugging On.
Plug the device in to your computer via USB cable.
Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
Now, select open command window here.
In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot)
fastboot-windows oem unlock
(If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it)
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Click to expand...
Click to collapse
Leftcatcher said:
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Click to expand...
Click to collapse
Never mind, I did unlock my bootloader. Thanks for your help though.
Fixed !!!
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
It's Ok,In Adb Write "adb enable oem unlocking"
I Learned That From A Video
Called:
"How To Unlock Bootloader-Huawei GR5 & Honor 5X EMUI 4.0"
From The Channel Called:"NoNDrOiD"
Related
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Did you enable developer settings and enable the option to unlock bootloader?
Sent from my ONE A2005 using XDA-Developers mobile app
hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Follow this guide, It will work https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?
As I understand you have follow that guide and now you have
enabled in settings, developer options,
OEM unlocking.
Then in fastboot mode device is discovered by "fastboot devices" that means drivers are properly installed.
Whenever your try to execute "fastboot OEM unlock" your device restart but don't unlock the bootloader.
What I would do is different things first to factory reset and try to unlock again.
Try on different computer.
Flash latest official signed rom and try the unlocking procedure again
Sent from my ONE A2005 using Tapatalk
hrvw said:
Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?
Click to expand...
Click to collapse
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.
abenguru said:
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.
Click to expand...
Click to collapse
I have not tried yet, but go do it within short and then I'll let you know if it worked.
This did not work. do you have any more tips?
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
What variant s6 do you have?
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
It's not that easy, the option is called "Allow OEM unlocking" which I already have turned on. All that option does is allow the bootloader to be unlocked.
sofir786 said:
What variant s6 do you have?
Click to expand...
Click to collapse
920T Unlocked.
I know. A rare S6 model, bought in Panama.
iLoveMuffinz said:
920T Unlocked.
I know. A rare S6 model, bought in Panama.
Click to expand...
Click to collapse
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
Click to expand...
Click to collapse
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
iLoveMuffinz said:
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
Click to expand...
Click to collapse
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
Click to expand...
Click to collapse
Thanks for pointing that out. I don't know why I expect people to be grateful on XDA, just because someone tries to help them.
Using a Mac, you flash files using Heimdall: http://glassechidna.com.au/heimdall/
Ok so I think I'm good to go:
I attached some screenshots checking if everything is correct. Also, is http://glassechidna.com.au/heimdall/ the correct and official site to get Heimdall? And my device's build is G920TUES5DQD1 which was released a few days ago, and I'm not sure if the CF auto root file was based on an earlier update. Will I still be able to use it?
is g920v bootloader unlockable?
is it possible to downgrade thanks to this oem unlock?
sofir786 said:
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
Click to expand...
Click to collapse
My phone has the front tripped, is there any way to reset it? I can't even figure out how to pull up the system info, I can pull up the recovery menu and hard reset but I don't know how to, if possible, reset the front. Any advice?
Sent from my LGE LG-LS777 using XDA Labs
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
Install Windows in a Virtual Machine, Use ODIN to flash TWRP, flash Magisk.
help with unlock bootloader s6 920v
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
joeknz said:
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
Click to expand...
Click to collapse
As far as I know, and what has been the fact since the release of the 920V, there's has been no known case where the bootloader has been unlocked. Due to Verizon's restrictions, the S6 is hardlocked. The only way that it might ever be unlocked is if someone reverse engineers the bootloader software, creating an unlocked version that can be flashed, and that will still pass the phone's security checks. I wouldn't hold your breath for it though, because it's been 3 years and no solution yet.
i had same issues
i have been trying to unlock my s6 smg 9208 everything that i tried failed need really your help i can't use my keyboard and mouse ????
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
mzayd786 said:
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
Click to expand...
Click to collapse
That is incorrect, what you are referring to is carrier locked. and is done to most phones sold in the US. Most can be unlocked once fully paid for and after 90 days of service.
Bootloader lock has nothing to do with sim cards at ALL!! It does have everything to do with being able to install other roms and firmware via non official sources.
Sprint Samsung Galaxy S6 model SM g920p FRP lock is blocking me from enabling OEM unl
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
Hello to you super techs I'm a newbie to this hope i'm not posting out of place but my question is how do I set up my Windows PC with ADB to use ADB fastboot unlock to unlock my bootloader because FRP protection has me locked out of the phone and I can't use the build number 2 unlock OEM or is that even possible I have been searching the web and XDA 2 try and find a way to open this phone I bought for myself for Christmas not knowing anything about a phone being FRP locked to a Google account is it possible to unlock this phone so that I can Flash it and maybe be able to use it I checked the IMEI number and it comes back good so say Sprint customer service but they couldn't help me with the FRP because I bought the phone second hand could you guys please point me in the right direction if I'm in the wrong spot posting my apologies to the thread host
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says
FAILED (remote: unknown command)
finished. total time: 0.008s
Click to expand...
Click to collapse
.. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is old.
If in Android -> Settings -> Developer options -> OEM unlock option isn't present then unlocking phone's bootloader is denied, you can't unlock it by means of Fastboot.
May be you can obtain from OEM/Carrier an unlock-key. Contact them.
BTW: You always can check Android's system file named build.prop for device's bootloader-unlock capability
Code:
adb devices
adb shell "getprop ro.oem.unlock_supported"
If the device supports "fastboot flashing unlock", then the returned value is 1
Soham41 said:
Hey All!
I recently(2 days back) purchased a Yu Yutopia running android 5.1.1. I enabled developer options, but it didn't have the OEM unlock option. And whenever i go into fastboot, and type
Code:
fastboot -i 0x2A96 oem unlock
it says .. Any help would be appreciated. I went through tons of documentation. the only thing missing for now is the Yutopia Drivers. Is that the problem? If so, can someone share the driver packs? This thread had it, but the link is broken, and is ol
Click to expand...
Click to collapse
Same here tried everything from flashing in EDL mode to downloading Yuware and trying to unlock bootloader. The adb commands
Code:
getprop sys.oem_unlock_allowed
getprop ro.oem_unlock_supported
both return blank. Using Miracle box software to check device info returns Bootloader : unknown. Trying to root via Miracle Box, Kingroot and other methods fails. The original Signed Android 5.1.1 based CM signed zips also won't flash via Recovery and the links are also almost non existent for those. Any hope of finding a original CM firmware to flash via QFIL is very slim. There has to be some way to get it working, there was a YouTube video showcasing the YU Yutopia on Stock Android 5.1.1 Engineering build that now doesn't have the OEM Unlock option only if someone would help. Getting it rooted somehow god knows how is the only option to get started.
Don't waste more time with trying to unlock phone's bootloader: it's NOT supported.
if anyone interested, I made some modifation in stock rom, so it is rooted, without unlocking bootloader, here is the link of my thread
Yu Yutopia (Yu5050) (Sambar) Stock engineering rom, rooted (Android 5.1)
For those interested, this is exactly engineering rom, with added modified patched boot, so it is rooted with magisk. v23 This is the detailed install procedure: You need to download the following: 1. YU_Yutopia_YU5050_V1_24.12.15 rom, link give...
forum.xda-developers.com
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.
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 .