Related
Hi everyone,
These factors are my mobile parameter
--------------
PRODUCT NAME - HERRING
HW VERSION -REV 52
BOOTLOADER VERSION -I9020XXKL1
BASEBAND VERSION -I9020XXKI1
CARRIER INFO -EUR
SERIAL NUMBER -383140F65F2500EC
LOCK STATE -LOCKED
Although doing many method through threads,My lock state has not been changed to unlocked state.
Is there any other to unlock it? When I use fastboot oem unlock.UI appear to select yes and no option to unlock.I have selected yes.But
Bootloader return to original state with locked state as above description.Nexus toolkit,Odins and some recovery image have been used. Bootloader and command prompt said that it was due to "LOCKED "Problem.The relevant driver loaded already for both fastboot and ADB .How can I solve it?Please Excuse me someone.
Thank.
this worked for me: http://www.wugfresh.com/dev/nexus-root-toolkit/
Wouldn't it be nice to have a keygen to unlock the bootloader without obtaining the key from motorola?
I have been investgating the relationship between the bootloader return code and unlock key and have discovered the following:
Note: For security I have replaced my IMEI and serial number, all other numbers are real. I'm not sure if anyone else has had a go at this but found nothing on XDA.
Code:
fastboot oem get_unlock_data
1A23457698214365#54413839303042
42443700585431303332000000#140A
858731D55F3B5DF78F0F6BB9EAE32A2
B8945#3D372B020F000000000000000
0000000
If I use the # character as a separator I get:
Code:
1A23457698214365
5441383930304242443700585431303332000000
140A858731D55F3B5DF78F0F6BB9EAE32A2B8945
3D372B020F0000000000000000000000
Line 1: With the exception of the 2nd character 'A' inserted, these characters are my IMEI number re-arranged a little.
The last 5 pairs of digits are swapped so an IMEI of 123456789123456 converts to 1A23457698214365
Line 2: Converting this line from hex to ascii gives me TA8900BBD7�XT1032���
This is serial and model number with a 00 byte as a spacer and 3 filler at the end.
Line 4: This is my bootloader UID (obtained from 'fastboot getvar uid' command)
Lines 1&2&4 I suspect have no relationship whatsoever with the unlock key.
Probably used to validate and log you on the motorola server when you request the unlock key, ultimately serving the purpose of voiding the warranty.
Line 3: Coincidence? Could this 20 byte string be relative to the 20 byte unlock key via some simple algorithm assuming lazy programming and/or limited space for code in the bootloader hardware? I couldnt tie this number to anything on my phone so I am guessing this code is derived from the unlock code during the 'fastboot oem get_unlock_data' command.
I tried online with varied IMEI and serials in the code and also using original values but with varied numbers in line 3 but could not get another unlock code. I don't think I can progress without more examples.
This was my unlock code: W4ZUEO2TZALOGJJWPRMO
Converted to hex: 57345A55454F32545A414C4F474A4A5750524D4F
Code:
So somehow 140A858731D55F3B5DF78F0F6BB9EAE32A2B8945
becomes 57345A55454F32545A414C4F474A4A5750524D4F
Could possibly involve the UID in the equation but I wouldn't bother if I were writing the bootloader and if so, then why have line 3 anyway?
I tried, a few sums but now I have a headache so I return to my life assisted by alcohol. Surely the solution has to be simple. Just thought I would post and see if anyone else could pick up from where I left off.
Have fun.......
I love the idea. I didn't unlock my phone because of the warranty but if we can find a way to unlock without allow Motorola to know it, it would be great...
Envoyé de mon Moto G en utilisant Tapatalk
Great thread. Hope in something of new
I can confirm that the first is the IMEI somehow swapped and an A added; the second one is the serial number with the model.
Certainly would help us Verizon Moto G users who currently are stuck with locked bootloaders :/
Takenover83 said:
Certainly would help us Verizon Moto G users who currently are stuck with locked bootloaders :/
Click to expand...
Click to collapse
I agree
Sent from my XT1028 using Tapatalk
Please, someone figure this out!
Help required!
What is needed is more examples. If people post the line 3 and unlock code in hex, then the problem can be solved. Unless you are the kid from mercury rising or rain man, the best that can be acheived with only one example is a headache. Trust me!
Those of you that have unlocked, please provide the required info. Maybe we need a new thread title to draw the atttention of those already unlocked.
"Request: Unlocked? Share your info here" etc..
Really nice that someone is trying to hack the bootloader protection. I intend to root my phone one day, but I am reluctant to use the official way because of warranty issues.
trifonius said:
Really nice that someone is trying to hack the bootloader protection. I intend to root my phone one day, but I am reluctant to use the official way because of warranty issues.
Click to expand...
Click to collapse
Same here. I was actually surprised to learn about this when I got this phone. I unlocked my Nexus 7 and assumed (my mistake) that I wouldn't have to get the manufacturer involved to unlock the bootloader.
Hope in some help from devs really
hey, i'm looking forward to this, actually i come from a device that had a locked bootloader but i could root it just with an exploit made with ics. maybe if someone finds an exploit in jellybean we will be able to root our phones but, that will be difficult
Hi.
Code:
My line 3: 5D0E47A39BBB9DA7B9632E8C19BD2873B018B7BA
My unlock code in hex: 4B415947324C4A424B454E414654573256544A45
I think of the possibility that all data used.
I am not an expert on algorithms, but the lines 1 2 3 and 4 are 64 bytes (whitout the #), groups of 8 or 16 bytes required for any algorithm.
The SHA1 with 64 bytes return 20 bytes hex the result.
Although I can be wrong, sorry for my bad english, i using g translator.
vientodearena said:
Although I can be wrong, sorry for my bad english, i using g translator.
Click to expand...
Click to collapse
Your English writing skills are better than many individuals from English speaking countries.
Thanks for your input. Hopefully, the people with the right skills can solved the problem.
My Unlock Code
I really couldn't stand to be without root, so here's my information:
Code:
fastboot oem get_unlock_data
3A55000805631104#54413931393030
364F4A00585431303334000000#FF1E
8DC44A01DC00C5CA53DB553418873A7
50D1C#5FABFE010F000000000000000
0000000
Code:
Unlock code:
BEXHELCKBBJZKZ5GYUWE
I hope this information can be of some use.
Aldo6 said:
I really couldn't stand to be without root, so here's my information:
Code:
fastboot oem get_unlock_data
3A55000805631104#54413931393030
364F4A00585431303334000000#FF1E
8DC44A01DC00C5CA53DB553418873A7
50D1C#5FABFE010F000000000000000
0000000
Code:
Unlock code:
BEXHELCKBBJZKZ5GYUWE
I hope this information can be of some use.
Click to expand...
Click to collapse
Converted to the following.
Line 3: 42455848454c434b42424a5a4b5a354759555745
Unlock Code: FF1E8DC44A01DC00C5CA53DB553418873A750D1C
Hope I did that right. Just trying to help.
Even if a keygen of sorts is created, won't the unlock still be flagged in the bootloader?
theoneofgod said:
Even if a keygen of sorts is created, won't the unlock still be flagged in the bootloader?
Click to expand...
Click to collapse
it would but you might be able to remove this flag and as long as motorola dont know that you have unlocked the bootloader all would be fine
Maybe it's need some help also from devs i think..
Hello
I'm trying to identify what is the correct stock firmware for my Moto G (XT1032). The phone was purchased from a Puerto Rican eBay seller. When the phone arrived I immediately unlocked the bootloader and flashed the Google Play Edition firmware. Didn't even have a look at the About Phone screen to note which firmware was originally installed. I've included a picture of the side of the box and I'm hoping that someone with the same phone may be able to tell me which firmware came pre-installed on their device.
From what I have read if I flash the correct stock firmware image then I should be able to lock the bootloader. Is this correct?
Thanks for your help.
Firstly, you can never undo unlocking of bootloader. There is a fastboot command: oem relock - but your phone is forever unlocked.
You have an XT1032 Global GSM phone, which means you can flash any XT1032 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25 - you don't need to flash a firmware for a specific region of the world.
Thanks for your response lost101. I've asked this question as there are forum posts discussing the use of the oem lock command and several members in these threads have reported successfully locking the bootloader. The thread I'm referring to can be viewed here. http://forum.xda-developers.com/showthread.php?t=2575586
Is it your suggestion that flashing any firmware on my phone will work with the oem lock command?
I have personally never used the OEM lock command. It isn't necessary and I see no value in it.
Cool. Glad you could be of help. While its not totally necessary to my existence, it's something I would like to do. Not really sure why you would respond to a question you can't answer though. Im not that interested in how you would like to use your phone. Still hoping someone who may know what they're talking about can answer my questions.
Apologies, I only wanted to make it clear that you didn't need to use the 'oem lock' command in order to flash stock firmware image.
seaninoz said:
Thanks for your response lost101. I've asked this question as there are forum posts discussing the use of the oem lock command and several members in these threads have reported successfully locking the bootloader. The thread I'm referring to can be viewed here. http://forum.xda-developers.com/showthread.php?t=2575586
Is it your suggestion that flashing any firmware on my phone will work with the oem lock command?
Click to expand...
Click to collapse
Perhaps you can narrow it down using
fastboot getvar cid
your cid shouldn't change no matter which firmware your running
That command returns the following information:
cid: 0x000C
Not sure what that means.
seaninoz said:
That command returns the following information:
cid: 0x000C
Not sure what that means.
Click to expand...
Click to collapse
cid is the carrier code, I though there was a list somewhere but I couldn't find one.
Lets see... just guessing most of this...
So 0x000C hexadecimal converted to decimal is 12, so looking through the factory images for cid12. Lets start eliminating options. First I made a list of all the firmwares from http://www.filefactory.com/folder/c6cdedc45a775d27/
Then I deleted all that aren't XT1032 unless the model wasn't listed in the filename.
Then I deleted all non cid12, again unless the cid wasn't listed.
So you've updated to to GPe which mean you have a bootloader for 4.4.3 at least so I deleted all 4.3 from the list.
Down to 33 now, I bolded only the Porto Rico ones, good luck
Code:
CLARO-BR-SS_4.4.2_KXB20.9-1.10-1.18_cid12_CFC_1FF_v7.xml.zip
CLARO-CL-SS_4.4.2_KXB20.9-1.10-1.9_cid12_CFC_1FF_v7.xml.zip
[B]CLARO-PR_FALCON_KXB20.9-1.10-1.9_cid12_CFC_1FF_v7_SVC.xml.zip[/B]
MOVISTAR-CL-SS_4.4.2_KXB20.9-1.10-1.9_cid12_CFC_1FF_v7.xml.zip
MOVISTAR-CO-SS_4.4.2_KXB20.9-1.10-1.18_cid12_CFC_1FF_v7.xml.zip
OI-BR-DS_4.4.2_KXB20.25-1.37_cid12_CFC_1FF_SVC.xml.zip
RETAIL-BR-DS_4.4.2_KXB20.25-1.37_cid12_CFC_1FF_SVC.xml.zip
RETAIL-BR-DS_4.4.3_KXB21.14-L1.32_30_cid12_CFC_1FF.xml.zip
RETAIL-BR-DS_FALCON_KXB20.25-1.31_cid12_CFC_1FF.xml.zip
RETAIL-BR-SS_4.4.3_KXB21.14-L1.32_34_cid12_CFC_1FF_SVC.xml.zip
RETAIL-BR-SS_FALCON_KXB20.9-1.10-1.18_cid12_CFC_1FF_v7_SVC.xml.zip
RETAIL-LA-DS_4.4.2_KXB20.25-1.31_cid12_CFC_1FF.xml.zip
RETAIL-LA-FALCON_14.10.0Q3.X-76-LCG-8-2_cid12_CFC_1FF_SVC.xml.zip
TELCEL_MX-FALCON-KXB20.9-1.10-1.9_cid12_CFC_1FF_v7_SVC.xml.zip
VIVO-BR-FALCON_14.10.0Q3.X-76-LCG-8-3_cid12_CFC_1FF_svc.xml.zip
VIVO-BR-SS_4.4.2_KXB20.9-1.10-1.18_cid12_CFC_1FF_v7.xml.zip
XT1032_AMERICAMOVIL-CO_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF.xml.zip
XT1032_AMERICAMOVIL-MX_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF.xml.zip
XT1032_AMERICAMOVIL-PE_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF.xml.zip
XT1032_CLARO-AR-SS_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF.xml.zip
XT1032_CLARO-BR-SS_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF_SVC.xml.zip
XT1032_CLARO-CL_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF.xml.zip
[B]XT1032_CLARO-PR_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF.xml.zip[/B]
XT1032_MOVISTAR-CL_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF.xml.zip
XT1032_MOVISTAR-PE_4.4.4_KXB21.14-L1.40_40_cid12_CFC_1FF.xml.zip
XT1032_PER-AR-SS_4.4.4_KXB21.14-L1.40_36_cid12_CFC_1FF.xml.zip
XT1032_RETAIL-BR_4.4.4_KXB21.14-L1.40-1_1_cid12_CFC_1FF.xml.zip
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip
XT1032_VIVO-BR_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip
fastboot_falcon_amxar_user_4.4.2_KXB20.9-1.10-1.9_7_release-keys-cid12-AmericaMovil_AR.tar.gz
[B]fastboot_falcon_amxpr_user_4.4.2_KXB20.9-1.10-1.24-1.1_1_release-keys-cid12-AmericaMovil_PR.tar.gz[/B]
fastboot_falcon_retar_user_4.4.2_KXB20.9-1.10-1.9_7_release-keys-cid12-Latam_AR.tar.gz
fastboot_falcon_perar_user_4.4.2_KXB20.9-1.10-1.9_8_release-keys-cid12-Personal_AR.tar.gz
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?
Good day, Devs. So, I have been trying to unlock my Vivo Y22s' bootloader recently and tried every which method; from fastboot to modified binaries. However, after looking into some threads, some Vivo phones have what's called an lk.img. My phone's firmware doesn't have that but after looking into one in particular, I found one interesting command: "fastboot oem reboot-edl". Maybe this was my ticket. But, after inputting that into fastboot mode on my phone, the bootloader returns "emmcid=xxxxxxxxxxxxxxxxxxxxxxxxx&extra=UNKOWN&key=chocolate&op=edl0&ver=Alpha0.lk1" (note: I censored the emmcid). Basically, I don't know what that string means and if it even leads anywhere near entering EDL mode on my phone.
Phone: Vivo Y22s
Chipset: SD680
Model: V2206
OS: Funtouch 13 (Android 13)