Related
Hi guys,
Sorry I've not been around for a while - been having a little issue testing Kernels at the moment as I've managed to re-lock my bootloader! (Doh!). Posted what happened below in case anyone has any thoughts - can't say I'm happy it looks like I'm going to have to pay money to get the simlock removed again!
It started when I was looking into changing the MTD sizes so I could reclaim wasted space in /system and /cache so I could get ~620MB of usable space in /data for apps etc. To do this I had to first know what the current partition sizes are so I wouldn't screw up the partitions needed to boot the phone.
Unfortunately trying 'fastboot oem listpartition' was giving me:
Code:
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
and when I tried to unlock the bootloader the SE way with
Code:
fastboot.exe -i 0x0fce oem lock 0xMy_Code
I was getting
Code:
FAILED (remote: Phone is already unlocked!)
"No problem!" thought I, fired up S1Tool and pressed the 'Restore' button thinking this would lock the bootloader using the testpoint method. Then I could unlock it the SE way over fastboot and perhaps the OEM commands would work.
It was a partial success, the phone lost bootloader but wouldn't power on. I couldn't get anything to work, and finally had to re-flash it using the FlashTool. From here I noticed the Sim-lock seemed to be re-enabled and I couldn't get in to FastBoot mode.
When attempting to unlock the bootloader I can't via the SE method because I can't get to FastBoot, and I can't through the S1 Tool method as it complains:
Code:
SETOOL2 SIMLOCK CERTIFICATE, SEMCBOOT ALREADY PATCHED
I've a feeling I'm going to have to go back to the shop that unlocked it in the first place and get them to perform their magic again - no doubt costing me more money! Thought I'd post it here in case there's something I've not tried?
...Seems that Simlock isn't enabled as such, but putting in two different sim-cards makes it display "Emergency Calls Only | No Sim Card" :S
Starting to think I've really broken it!
Hello,
Let me tell you my story and perhaps someone will come up with a miracle solution for my problem.
I was trying to flash my device so: I opened developer options and enabled enabled USB debugging.
I though this was enough, but in the middle of the process I got some errors like "Preflash validation failture". So I went back and discovered that I had the fastboot locked and that in order to unlock it I should get a code from Motorola. I got the code, but when I was going to unlock it, I got another error saying that I can't unlock my flash boot since I didn't enable the check "Enable OEM Unlock" and at that moment was when I discovered I was screwed.
Someone said, that I was just a matter of downloading a Stock room, and repeat the process but I have downloaded tons of them and no luck.
At this point, I would try anything just to be able to open my phone in recovery mode because I can't do anything with it is dead,
I have read tons and tons of posts and all off them lead me to the same point, flash through fastboot repeat all the commands, but I have been there almost 100times. I'm about to get crazy.
If someone knows something, I will really appreciate it.
So i wanna root my phone with magisk, i have the boot.img prepared. But i cant unlock the bootloader. fastboot oem unlock and fastboot flashing unlock does not work.
Code:
fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: 0.004s
Please help, im desperate.
bump
I have the same issue.
I know mostly everyone should know this but ...........I have to say it I am sure some new people don't know or someone just forgot but ...
Have you enabled OEM Unlock ? Have you enabled USB Debugging ?
If you have not then of course your commands will not work or will return with error and ect.....
Have you done adb devices and see what comes back?
Dose it come back with your devices ID or is it come back blank for device info?
One reason you Run that command is to know the state of your phone or USB Debugging ect...
Even if you have enabled the OEM and or USB in developers options before you must check it every time always...now if you haven't for one or both then several things will happen....
Your adb or fastboot commands will not work or or will return with errors.Don't be fooled or confused that some adb and fastboot commands do and will work even if you didn't enable the two options or just one option.
I won't explain that you can Google why you may learn something when doing so if you have t already ... ......
Now if your reading this then. You fit in one of 4 catergories In my Opion .
1.Newbie ( Team entire post it will explain a lot you need to know)
2 Lazy and try to cut corners
( Don't know what to tell you.... ..do it right and quit being lazy)
3 Soft Bricked , Hard Bricked , Bootloop ect.
( Something happens by acident or whatever reason maybe sideloading firmware,recovery,bootloader,ect... ** If not a newbie Skip to
*?*?*?* Section
To advoid a lesson on what to do and what not to do as a newbie.
4 Your using incorrect OEM or ADB and Fastboot commands not for your devices .....
Now I won't beat you up to bad about your post or question or whatever you call that what you did I don't know just looked lazy as hell I won't get to worked up over it no one is perfect and we all been a Newbie or rookie in something but you need to know the importance of what is missing or why your post is crappy as hell ok. So you can learn and or not do it aging. The solution or helping is faster for everybody .
Further reference put as much info as possible . Just most will not ask you 100 questions about . What have you done or not done. Ect...
You should let us know how you ended up in the position what did you do before remember it's not my job to ask you 100 questions to find out what's going one with your device its not our phone that is the problem it's yours
So do us the favor and youraelf and everyone else that comes into contact with the same or similar issue and provide as much info as possible.
So I don't know what you have done other that run 2 fastboot commands and honestly I don't even know think they are correct for That device.
Most phones. Use the same or simar adb or fastboot Commands but there are OEM specific commands for certain android versions or devices and that don't work on other devices .
I will let you. Google more about that also maybe you learn something...
*?*?*?*?*?*?*?*?*?*
to restart your phone into fastboot mode or bootloader mode:
adb devices
adb reboot bootloader
fastboot devices ( just like earlier it's important that device info returns after command )
Now when your bootloader / fastboot mode
fastboot oem unlock
This will Unlock the bootloader and delete all user data present on the phone.
If you still having issue then USB Debugging and OEM unlock was not the issue then your problem is not just the bootloader and needs more detailed approach to fix specific to your device.
I have the same issue impossible to unlock the bootoader on this device and i am not a newbie !
On android 9, device branded orange neva play, 2gb and 32 gb ,Unisoc SC9863A , usb debug on and oem unlock on, all commands not work, i try with your phone tool , the same issue. Nothing on google that can work with this device, seems to be a specific command for this device,
Devildog0351 said:
I know mostly everyone should know this but ...........I have to say it I am sure some new people don't know or someone just forgot but ...
Have you enabled OEM Unlock ? Have you enabled USB Debugging ?
If you have not then of course your commands will not work or will return with error and ect.....
Have you done adb devices and see what comes back?
Dose it come back with your devices ID or is it come back blank for device info?
One reason you Run that command is to know the state of your phone or USB Debugging ect...
Even if you have enabled the OEM and or USB in developers options before you must check it every time always...now if you haven't for one or both then several things will happen....
Your adb or fastboot commands will not work or or will return with errors.Don't be fooled or confused that some adb and fastboot commands do and will work even if you didn't enable the two options or just one option.
I won't explain that you can Google why you may learn something when doing so if you have t already ... ......
Now if your reading this then. You fit in one of 4 catergories In my Opion .
1.Newbie ( Team entire post it will explain a lot you need to know)
2 Lazy and try to cut corners
( Don't know what to tell you.... ..do it right and quit being lazy)
3 Soft Bricked , Hard Bricked , Bootloop ect.
( Something happens by acident or whatever reason maybe sideloading firmware,recovery,bootloader,ect... ** If not a newbie Skip to
*?*?*?* Section
To advoid a lesson on what to do and what not to do as a newbie.
4 Your using incorrect OEM or ADB and Fastboot commands not for your devices .....
Now I won't beat you up to bad about your post or question or whatever you call that what you did I don't know just looked lazy as hell I won't get to worked up over it no one is perfect and we all been a Newbie or rookie in something but you need to know the importance of what is missing or why your post is crappy as hell ok. So you can learn and or not do it aging. The solution or helping is faster for everybody .
Further reference put as much info as possible . Just most will not ask you 100 questions about . What have you done or not done. Ect...
You should let us know how you ended up in the position what did you do before remember it's not my job to ask you 100 questions to find out what's going one with your device its not our phone that is the problem it's yours
So do us the favor and youraelf and everyone else that comes into contact with the same or similar issue and provide as much info as possible.
So I don't know what you have done other that run 2 fastboot commands and honestly I don't even know think they are correct for That device.
Most phones. Use the same or simar adb or fastboot Commands but there are OEM specific commands for certain android versions or devices and that don't work on other devices .
I will let you. Google more about that also maybe you learn something...
*?*?*?*?*?*?*?*?*?*
to restart your phone into fastboot mode or bootloader mode:
adb devices
adb reboot bootloader
fastboot devices ( just like earlier it's important that device info returns after command )
Now when your bootloader / fastboot mode
fastboot oem unlock
This will Unlock the bootloader and delete all user data present on the phone.
If you still having issue then USB Debugging and OEM unlock was not the issue then your problem is not just the bootloader and needs more detailed approach to fix specific to your device.
Marc530 said:
I have the same issue.
Click to expand...
Click to collapse
Oi! When was the last time you unlocked a bootloader? 2014? "FAST OEM UNLOCK" LOL, Any question is a valid help people don't get angry the
The greatest flaw that any intelligent person has is
to think they're smarter than everyone else,
Click to expand...
Click to collapse
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.