I recently used the correct msm tool to flash back to android 10 stock for this device and everything worked perfectly it showed IN2017 all is well , however even with auto update disabled the phone is auto updating to android 11 and in the process of this its changing the model number to IN2015. i was trying to unlock my bootloader but fastboot oem get_unlock_code is just saying it doesnt understand the command, so i cant get a code at all , the only command it will take is fastboot oem oproot which gives an "unlock code" but it says incorrect on the oneplus site also. If i use msm tool to go back to 10 all these commands work and give me an unlock code but the oneplus website is still saying incorrect code, what can i do i dont understand how its changing models because of an OTA update
Hi--did you ever figure this out? I'm looking to buy an OP8 and am going to want to root; there's a 2017 available at a good price in that gorgeous shimmery color, but I'm wondering if I should stick with the IN2015. Any advice (I'll actually need it if I do get the IN2017, not just to piggyback on your thread, but since no one was responding...)?
Thx and gl
Related
Hi guys, I'd really appreciate your help so I can get OEM unlock back on my Samsung S8+ dual sim SM-G955FD here in Canada. I'm on Android 8.0.0.
I've tried many of the methods described on this forum and elsewhere without luck. I've even left my phone charging for over a week, with and without a sim. Also no luck.
My guess is that since the model of my phone is not a model imported into Canada by Samsung, and since I understand Samsung unlocks the OEM security feature by sending a signal, Samsung won't send that OEM unlock signal to an unofficial phone.
This mess started when I unsuccessfully tried to root my phone. I must have made a mistake, so I figured the best way to try again would be to reinstall a stock image. Instead of the original Android 7 I installed Android 8 (which also changed the "Samsung Experience" version from 8 to 9). The phone now happily works, but no OEM unlock and so I cannot root.
Please help me get OEM unlock back on my phone.
Thanks so much
D, stuck in Toronto
Did you succeed
the same for me more oem unlock
When I received it it was already on Oreo version bootloader v3 and updated to v5
in v3 oreo oem unlock is turn on
update v5 7 day wait
i have message erasing recovery without admin to odin
As Mr.mayb2 requested...here a rooted boot.img from the US Verizon LG Velvet.
Pulled the original boot.img directly from the kdz that was provided to me via
http://lgegdmswdl.s.llnwi.net/dn/do...5CAIKAED3DRMO/G900VM10e_00_VZW_US_OP_1009.kdz
Then did un'kdz and un'dz.
loaded it into magisk and patched the file.
Please note that LG Velvet has 2 bootloader partitions. so be sure that you patch it to a/b.
How to unlock bootloader
29y6145 said:
How to unlock bootloader
Click to expand...
Click to collapse
Thats the thing where everything will stand and fall.
To unlock the bootloader you need an unlock-code from the vendor.
For the EU-Version i got that via mail from LG.
But i've no clue if LG does this for US too.
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
WELCOMETOOCEANIA said:
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
Click to expand...
Click to collapse
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
MikGx said:
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
Click to expand...
Click to collapse
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Sry.
Dont know about lg´s politics concerning this.
Just reacted on the request to produce an rooted boot.img.
Maybe plead lg via mail to the bones givin other regions possibility to root...?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Maybe try getting into fastbootd by rebooting in fastboot to fastbootd
Fastboot reboot fastbootd
Worth a shot.
you cant root without a bootloader unlock and you arent getting it with the verizon version. the velvet is down to $120 and although its tempting, i wouldnt do it without the unlock.
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Mr.PvT said:
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Click to expand...
Click to collapse
Hava you been able to unlock yours? Im on Korea version and if you can unlock yours with exploit then I can also do the same with LG token
I can't unlock bootloader for my lg velvet LM-G900VM
Please suggest how to root?
Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?
You probably need to unlock your bootloader?
fastboot flashing unlock
AlmightyGrapefruit said:
Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?
Click to expand...
Click to collapse
You will get fastboot errors about unlocking critical partitions if you try to flash partitions other than boot, recovery and a few others while you're in bootloader mode.
For the rest you must be in fastbootd mode.
Chances are you need the unlock token from OnePlus themselves it takes a week
I got the Unlock Code from Moto with no problem, but can't get the phone to take it. FAIL, over and over again. I've tried several times, rebooted the phone, powered off, even tried an FDR. I keep getting a 'FAIL" message trying to push the code to the phone.
Just got the phone (used) today and I do have Unlock enabled in Dev Options. CID is 0x0032, obviously unlockabled since I did get the code from Moto. Twice. I redidthe Unlock request with a new string and got the same code again. Nothing is working. I've unlocked 15 or more Moto phones and never had anything like this happen before.
Using "fastboot oem unlock UNIQUE_KEY [20-character unlock code string]". Copied it, typed it manually, etc etc. FAIL FAIL FAIL.
Frustrating. Any clues/suggestions?
- - - - -
Edit to add: This phone has (I presume) the newest firmware on it, QZKS30.Q4-40-95-9 (RETUS), which has not been uploaded to lolinet yet.
Could this newest update be the problem? If so, can I safely roll back to 95-6 or even something older?
= = = = = = = = =
SOLVED. There was apparently an issue with the first phone I tried. Bought a second XT2113-2 relatively cheap (64GB) which came with the same 40-95-9 firmware, and it took the unlock code without a hitch.
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
notmyrealhandle said:
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
Click to expand...
Click to collapse
Thanks for replying. This phone has 40-95-9 firmware (March 1, 2022) which looks to be the latest OTA.
I have wondered if I'm stuck in another one of the newer Moto's (or Android's) mysterious holding patterns. Maybe it'll work in a few days. I will certainly post here if that's the case. . . . But why give me the Unlock button plus the Unlock Code, but then hold me back from actually pushing it to the phone? That wouldn't make a lot of sense.
This is the exact message returned by the bootloader every time:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
I believe I'll try reflashing the 40-95-9 firmware, downloaded this morning via Rescue and Smart Assistant.
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Moondroid said:
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Click to expand...
Click to collapse
Two other things you can try:
1. make sure you are using an up to date fastboot exe (I'm using fastboot version 33.0.1-8253317 on ubuntu linux).
2. Try from both the bootloader mode and fastbootd mode on the device - I forget how to get to fastbootd from stock `adb reboot fastboot` might do it.
EDIT I'm pretty sure you want to be in the bootloader mode. Just thought I'd mention it as fastbootd was new to me and some fastboot commands seem to like the device to be in one mode or the other.
HTH
notmyrealhandle said:
Two other things you can try . . .
Click to expand...
Click to collapse
Still nothing.
I found some newer adb & fastboot utils (2021 vs 2018) and tried those. That just changed the error message a teensy bit (replaced "remote failure" with a couple of bare quote marks).
I also uninstalled & reinstalled my Motorola drivers before trying the newer adb & fastboot. That didn't help either.
Trying to boot twrp gives me a "permission denied" error.
So all I can think to try now is to run another firmware reinstall via LMSA (Rescue and Smart Assistant), just to see if that hiccups anywhere as much as anything. (I manually flashed all the files the first time.)
I think it's past time for me to say something like "this doesn't just suck, it SUPER-sucks." Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Moondroid said:
Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Click to expand...
Click to collapse
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
slipchicken said:
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
Click to expand...
Click to collapse
I tried the unlock code 5 minutes after I got it. Why would I wait 48 hours? Lol . . .
If this is another "time-delay" thing it doesn't make any sense at all. OEM Unlock was already enabled, the phone gave me an unlock string to send Moto, and I got the unlock key from Moto with no delays at all. Within an hour after unboxing the phone I was trying to push an unlock code to the phone.
I also tried getting another code from Moto, generated a new string and all, but the second code Moto sent me was exactly the same as the first. I did try it (again) on the phone but got the same "FAILED" message as before.
This is just nuts. Unless the latest OTA 95-9 is in fact the culprit. Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Moondroid said:
Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Click to expand...
Click to collapse
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
slipchicken said:
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
Click to expand...
Click to collapse
I was in that thread you quoted and I don't remember anything about having to wait AFTER getting the unlock code. Wait for OEM Unlock to show as enabled in Dev Options, yes, I'm thoroughly familiar with that. But I have never-never-never had to wait for an unlock code to work after receiving it from Moto. If that's in there somewhere please point more specifically? because I've unlocked a whole bunch of Moto phones and as I said, I've never heard of being able to enable OEM Unlock, getting the unlock code from Moto and then having to wait to use it.
See bottom of top post. The phone had some kind of problem that wouldn't allow it to accept the unlock key.
After further testing (well actually I mean bricking my device a few times) it turned out that rebranding is not needed for the update from mm to nougat, although your device will boot into a "test" system instead (This is likely due to the vendor information being mismatched). Your p9 would still work with HWOTA7.
The original post has not been changed.
I got hold of an EVA-AL10 model from China. However it was still stuck on emui 4.1 Android 6.
Spoiler
After some research, I found out that Chinese internet was ridiculously unreliable and riddled with useless information, and the fact that most Chinese are tech-illiterate does not help either. Then I turned to good old XDA and found out a few (pretty obsolete posts) that had similar problems and got them solved. However, they all (unsurprisingly) involved the European model (EVA-L0X), which had different firmware.
I then got in contact with a former Chinese colleague. With his help, I managed to send an email to Huawei China and get a representative. After giving him his phone number and all information in the about section of the phone (IMEI and stuff) they took an entire day only to phone him back saying he needs to go to a repair shop. They told him that the oldest version of EMUI available for update was for emui 8 (Android 8) so that was a dead end.
After more searching, I stumbled across a thread about rebranding an European model into the one I got to get to, ironically, emui 8.
Spoiler
According to a Chinese nationalist blogger, it turns out that Huawei severely displeased our international community due to halting the provision of bootloader unlock codes, and they dicided to get us back by not updating us to emui 8. Although there might be more reasons than that, the fact is clear that they had to change their model.
Luckily, XDA is the perfect platform to find help.
Spoiler
Although the in-house search engine is relatively good at dealing with the Chinese e-thefts which take the hard work of this community and sell it shamelessly in China,
a fair amount of time was taken to Google search, however it was definitely worth the effort. Soon, I drew out a simple flowchart to update my p9:
1. Unlock bootloader
2. Rebrand the phone to European model
3. Update to Android 7
4. Rebrand back
5. update to Android 8
(6. Do cool stuff)
Unlocking the bootloader is now a hard part for some. (make sure you have backed up your data on the phone because it will do a factory reset)
Spoiler
While unlocking services here are mostly genuine, it is 75% scam in China. My friend maaged to get my bootloader unlocked from a (crazy) shopping site in China named Taobao, which is well-known for selling fake sneakers and even Uranium. It only costed me two dollars.
Make sure to keep the unlock code. You need it later. If you forgot your unlock code but have it unlocked, no worriess. You can root your phone (I used good old supersu) follow this guide (the commands are the important part, I personally have not verified this method though)
You can also try this tool:
Huawei Nova 2 Plus Bootloader Unlock (Solution)
Hello Developers! I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have...
forum.xda-developers.com
However it was intended for another device so your luck may vary.
After that, I used SRKtool to rebrand the phone, although the software of the phone itself has not changed. Keep in mind after the rebrand not to reboot into the system, as it will cause an error. (see below post) If you do manage to get into the system unfortunately, it will ask you for your password (bootloader unlock code) Do not enter the code, shut down your phone and get into fastboot by holding down power and volume down WHILE cable is attached to computer.
After trying hard to get into TWRP, I used this guide to boot into it (turns out I was not quick enough)
I then used this file to update it to the European android 7, which worked perfectly. You do need to enter the unlock code again though, and you need an SDcard or an USB disk that supports OTG(so the device can recognise it in twrp).
After that, you can follow this guide to get it to Android 7 Chinese version(399). I got my friend to set up a vpn connecting to China, where the Chinese system recognized that it could update to android 8. If yours does not, follow the guide to update it to android 8. It already contains the firmware, so do not download other firmware (unless you prefer). If you already got the firmware, use the androidfilehost link he provided and find in the older versions V1.1, which did not have the firmware to save time (and possibly bandwidth)
You will have your bootloader locked at this stage. If you want to stay on the Chinese firmware (Which has a lot of bloatware and needs you to manually sideload playstore apk) do not unlock it. If you do want to go further and install a custom treble GSI, go ahead and unlock the bootloader, and follow the instructions,
Error after force rebranding location with SRKtool:
After using SRKtool to rebrand, your system boot warning will turn from unlocked to unverified (text color orange to red)
If you continue to boot, it will go to a screen where you have to enter a password (the bootloader unlock code) you should not enter the code.
If you still proceed to enter the code, you will be "greeted" with a message telling you that the data on your phone is corrupt and you have to factory reset. after you boot into the OS, you will see this "mix" of the classic nexus 2012 style wallpaper with some android app icons (such as settings) in the aosp style, with everything else that are Huawei-branded seen in 2012-style icons. This has to do with a theme engine bug.
In the about page you might also notice that the system version has been slightly changed. the "al10" part has been deleted but the c00 still remains. The page where the CE and FCC stuff are displayed (forgot precise wording) now lists the phone as "eva-l09"
Go into settings and developer options as usual. You should now see that there is an oem unlock opion that has been toggled off. turn it on.
Reboot into fastboot again. You would see that most commands you would usually use such as flash recovery and erase would not work anymore(returns command not allowed) This has to do with the bootloader locked although it technically unlocked. Unlock it as you would normally do. If this does not work, reboot and turn off oem unlock, go to fastboot and enter the unlock command (it would obviously not work but it registers that wants to be unlocked), reboot and turn on oem unlock again and reboot into fastboot, then you should unlock the bootloader and flash recovery again.