Related
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"
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
You have to apply here: http://en.miui.com/unlock/ in order to unlock your bootloader (can take a bit to get verified)
In addition add the phone number you apply with to your mi clound & login to your mi account on your phone.
Download the software for windows --> login --> connect your phone via fastboot --> hit unlock.
If it still does not work, please go ahead and flash the latest china developer rom on your phone and try everything again.
Good luck and please tell me if it worked
you can unlock unofficial bootloader with edl mode:
http://en.miui.com/thread-2049615-1-1.html
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Today, when I try to access the thread on the miui forum i get this error message :/
Sorry, you don't have the permission to access this thread.
[ Xiaomi MIUI Official Forum Home ]
Can you still see it ada12?
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?[/QUOTE
You try different rom to flashing,I mean your device is RN5A Prime(Ugg)not Ugglite
Sent from my ugg using XDA Labs
Click to expand...
Click to collapse
[Help] Flash global rom my redmi note 5a that i recently bought is tampered
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
Did you try bounding mi account?If yes try 3 day to try agains to UBL and dont forget to visit mi community,in there many guides to UBL your devices,good luck..
Sent from my ugg using XDA Labs
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
I had the same problem - the phone came with a 'fake' global rom installed and it was impossible to bind the phone and account. The way I got around it was to flash the latest Chinese stable rom (it isn't possible to flash the global rom while the bootloader is locked) onto the phone and then I was able to bind the phone and account. Once I got to this stage I was then able to request unlock permission which now takes 360 hours (15 days). Once the 15 days have elapsed the bootloader can be unlocked and you are then free to install the latest global rom.
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
I agree with everything here, good job. Just want to add something to "unlock bootloader": if you recieve some error "it can't be added", download a VPN with the location in china. There is one app (at least) where you can create an fake account (e.g. 10 minute mail) and have 1 day of premium. Point it onto china and try to add your mi account again, that should do the trick.
Good luck and have fun ^^ ask if you have some problems!
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Click to expand...
Click to collapse
The answer is: NANOMACHINES, SON!
Just kidding, you have to point onto the root folder, if the system can't find the "flash.bat" you might be one folder too deep. If you get an error message during flashing then you might have a problem in terms of compatibility.
I still don't know yet, what the NSF means by mentioning the computer system with the "blue face for an interface" as an solution to xiaomis bootloader incompatibility issue. It seems suspicious, that some valuable forum posts have gone missing... wondering what the NSF is up to.
:highfive:
md.safayat said:
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
Click to expand...
Click to collapse
Hi to all. i have problem with redmi note 5a after remove micloud wifi and bluetooth unaviable. i try many official roms, but no luck. Please help to resolve this problem.
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
How will you run these commands on a locked bootloader? And no erasing modemst1-2 won't fix imei's.
Having trouble rooting my LG K40. I have the same problem as this person when trying to boot into fastmode: https:// youtu.be/yQ99lQv0rQk?t=26
You can find his post here explaining the process more in detail: https:// lgk20.com/root-lg-k40-lm-x420-bootloader-unlock-twrp/
MODEL #: LM-X420MM
Any help is appreciated,
Thanks in advance.
im having the same problem. i must have a proclivity towards phones with what seems impossible rooting methods. the first was the samsung j7 prime and now the lg k40 lmx420mm. ive gotten as for as adb reboot-bootloader, just restarts device, fastboot commands are either not recognized or i receive "waiting on device". Ive updated drivers, followed a diff. method found on reddit posted by jamesrascal (i cant post url here because of my newb status). Phone just stays stuck in firmware update. i feel as if ive exhausted all resources, any direction or help would be appreciated, im not educated on rooting ive been successful a few times on other phones and jailbroken some iphones, im mostly doing this to learn and teach myself so it isnt urgent but i need help to continue any further. thank you
Same problem for me. Because the device has good value for the money it would be nice someone can help us here.
Further this device seems to be full android treble conform I like to know how benefit from this circomstance.
I have LG K40 LM-X420EMW with dualsim.
Thanks for every hint!
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
jwoegerbauer said:
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
Click to expand...
Click to collapse
OK, but it is not possible to get into fastboot mode to enable the OEM unlocking. I marked the slider in developer option butz still there is no chance to get in fastboot mode.
After command "adb reboot bootloader" the device always reboots in normal system mode.
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
jwoegerbauer said:
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
Click to expand...
Click to collapse
Hm,
may be it is "allowed" to unlock but in the "LG K40 (LM-X420EMW) real world" it is not possible.
You dont reach fastboot mode which could enable using the order you proposed.
Device reboots into standard mode instead of wanted fastboot mode after sending "adb reboot bootloader"
I think thats the problem.
Code:
[email protected]:/# adb devices
List of devices attached
LMX4205P4TU4S4HEOJ device
[email protected]:/# adb reboot bootloader
[email protected]:/# fastboot flashing unlock
< waiting for any device >
^C
[email protected]:/#
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
baerenbisch said:
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
Click to expand...
Click to collapse
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
roycrt said:
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
Click to expand...
Click to collapse
Device can be bootloader unlocked now. MtkClient on github. I have the Harmony 3 bl unlocked and twrp for it
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
BenTheTechGuy said:
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
Click to expand...
Click to collapse
Please elaborate steps taken to unlock bootloader using mtkclient. Thanks
I wrote a guide as part of my porting of postmarketOS to my K40.
LG K40 (lg-mmh4x) - postmarketOS
wiki.postmarketos.org
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock
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.