This is concerning a moto g5s plus US variant, XT1806 32gb, 3gb ram phone.
2 questions I'm curious about.
1: I rooted this phone about a week after I bought it. I then decided to upgrade phones and am wanting to sell this phone now, but I wanted to lock the bootloader. For about 6 months, no matter WHAT I did, the bootloader just would not lock, regardless of what I did. Not sure why or what happened to make it not lock, so I just gave up until recently.
I decided to break out the phone again and give it one more shot, and to my shock and surprise, I think I finally got it locked. Perhaps I was using the wrong firmware, missing a command or something I'm not sure.
Symptoms I have now are
a: no unlocked bootloader nag screen at bootup and
b: in fastboot mode, it says at the bottom oem_locked
So to the question 1, if it says oem_locked, that is referring to the bootloader as locked, and if it was unlocked, it would say oem_unlocked instead, am I getting that right?
2: I am using firmware labeled as 116-64-11. I know they have different variants, and you should use the coresponding variant number. If I recall right the 64 varient is a global firmware, but will work on all variants of this phone, india and US variants alike.
If I again recall right the US variant number should be 116-45-x, 45 being the US variant. So does anyone know for sure what the corresponding numbers are for each one, and am I correct on my assumption?
easyrider77 said:
This is concerning a moto g5s plus US variant, XT1806 32gb, 3gb ram phone.
2 questions I'm curious about.
1: I rooted this phone about a week after I bought it. I then decided to upgrade phones and am wanting to sell this phone now, but I wanted to lock the bootloader. For about 6 months, no matter WHAT I did, the bootloader just would not lock, regardless of what I did. Not sure why or what happened to make it not lock, so I just gave up until recently.
I decided to break out the phone again and give it one more shot, and to my shock and surprise, I think I finally got it locked. Perhaps I was using the wrong firmware, missing a command or something I'm not sure.
Symptoms I have now are
a: no unlocked bootloader nag screen at bootup and
b: in fastboot mode, it says at the bottom oem_locked
So to the question 1, if it says oem_locked, that is referring to the bootloader as locked, and if it was unlocked, it would say oem_unlocked instead, am I getting that right?
2: I am using firmware labeled as 116-64-11. I know they have different variants, and you should use the coresponding variant number. If I recall right the 64 varient is a global firmware, but will work on all variants of this phone, india and US variants alike.
If I again recall right the US variant number should be 116-45-x, 45 being the US variant. So does anyone know for sure what the corresponding numbers are for each one, and am I correct on my assumption?
Click to expand...
Click to collapse
Okay so your device is sanders and not potter. This forum is for moto g5 plus not 's'. Post it in the g5s forum and u might get more help. And yes oem_locked is locked bootloader. And u will get the build version in the g5s section. GL.
easyrider77 said:
This is concerning a moto g5s plus US variant, XT1806 32gb, 3gb ram phone.
2 questions I'm curious about.
1: I rooted this phone about a week after I bought it. I then decided to upgrade phones and am wanting to sell this phone now, but I wanted to lock the bootloader. For about 6 months, no matter WHAT I did, the bootloader just would not lock, regardless of what I did. Not sure why or what happened to make it not lock, so I just gave up until recently.
I decided to break out the phone again and give it one more shot, and to my shock and surprise, I think I finally got it locked. Perhaps I was using the wrong firmware, missing a command or something I'm not sure.
Symptoms I have now are
a: no unlocked bootloader nag screen at bootup and
b: in fastboot mode, it says at the bottom oem_locked
So to the question 1, if it says oem_locked, that is referring to the bootloader as locked, and if it was unlocked, it would say oem_unlocked instead, am I getting that right?
2: I am using firmware labeled as 116-64-11. I know they have different variants, and you should use the coresponding variant number. If I recall right the 64 varient is a global firmware, but will work on all variants of this phone, india and US variants alike.
If I again recall right the US variant number should be 116-45-x, 45 being the US variant. So does anyone know for sure what the corresponding numbers are for each one, and am I correct on my assumption?
Click to expand...
Click to collapse
Oh...kay,
first ur phone lost its virginity, after a while u were dissatisfied so u decided to restore its virginity and u cudnt for about six months, u gave up.
Somehow u fixed it, now u wanna sell it to someone else!
Hmm interesting story eh..
But not here mate! Maybe the folks in the "Moto G5S Plus" forum can help u.
rajeshkoshti said:
Oh...kay,
first ur phone lost its virginity, after a while u were dissatisfied so u decided to restore its virginity and u cudnt for about six months, u gave up.
Somehow u fixed it, now u wanna sell it to someone else!
Hmm interesting story eh..
But not here mate! Maybe the folks in the "Moto G5S Plus" forum can help u.
Click to expand...
Click to collapse
Hilarious:laugh:
Related
Settings > General > About Phone > Software Info > Tap Build Number until you have Developer Options. Go back to About Phone and tap on Developer Options and Enable OEM Unlock is right there, simply check it off to fully enjoy your beautiful G4.
Just wanted to let everyone know carrying a Telus G4 that it is there in developer options incase they didn't know.
Spudnubs said:
Settings > General > About Phone > Software Info > Tap Build Number until you have Developer Options. Go back to About Phone and tap on Developer Options and Enable OEM Unlock is right there, simply check it off to fully enjoy your beautiful G4.
Just wanted to let everyone know carrying a Telus G4 that it is there in developer options incase they didn't know.
Click to expand...
Click to collapse
Awesome find! /kappa
Most models have this option, but it does nothing for us without fastboot, for now..
I saw this in the options, but wasn't sure how it helped us. What is the plus value of doing this? Does it permit to fasboot oem unlock?
**Edit** Read up on it. It only enables fastboot, which you could do once root was achieved anyway, so no big exploit. Anyone courageous enough to attempt to bootloader unlock the sucker?
I thought they all had this option but the T-Mobile variation was the only one where it actually did anything?
EDIT: I attempted to enter Fastboot with Vol-Up and Power without success.
To my knowledge the only G4s that are unlocked are the TMO (811) and International (815EU) everyone else, that option is a dummy option. the reason thats there is because that option is a default dev feature in LP. Checking this unless you have either of the two listed variants has no effect. It makes you able to use the fastboot oem unlock command which is only supported on these two variants.
djkinetic said:
To my knowledge the only G4s that are unlocked are the TMO (811) and International (815EU) everyone else, that option is a dummy option. the reason thats there is because that option is a default dev feature in LP. Checking this unless you have either of the two listed variants has no effect. It makes you able to use the fastboot oem unlock command which is only supported on these two variants.
Click to expand...
Click to collapse
Has it been confirmed that the Canadian version has a locked bootloader? Or would it be carrier dependant? There just isn't a lot of people, understandably, talking about the H812.
Usraek said:
Has it been confirmed that the Canadian version has a locked bootloader? Or would it be carrier dependant? There just isn't a lot of people, understandably, talking about the H812.
Click to expand...
Click to collapse
Connect your phone to your pc, and run this command in terminal: adb reboot bootloader
if it puts you in fastboot you can issue this command: fastboot oem unlock
if you can't even enter fastboot, then you device bootloader is locked.
Confirmed: Does not work. (Telus H812)
Confirmed locked, Rogers H812.
Worth a shot anyhow I suppose
Well... At least we're one step closer to getting root on Canadian variants. It's a step in the right direction at least.
This is a standard Android option. it only works on a couple of devices. T-Mobile is one. It's definitely not a quick and easy fix to unlock your bootloader for 95% of people.
the_scotsman said:
This is a standard Android option. it only works on a couple of devices. T-Mobile is one. It's definitely not a quick and easy fix to unlock your bootloader for 95% of people.
Click to expand...
Click to collapse
Ah well, I can certainly live without flashing a new ROM. LG's take on Android isn't as absolutely foul as Touchwiz was on my S3. I'll be perfectly sorted once we have access to Xposed, Viper, and the other incredible applications that require root.
I guess if it just restarts as usual after issuing the command then the bootloader is locked.
Talking about MTS H812.
Has anybody bugged LG about unlocking the bootloader recently. Last I see is that they unlocked 815 and others were to follow.
I did, however, find this: https://www.change.org/p/lg-electronics-unlock-bootloader-on-all-g4-devices
ETA ?
Is there some information about possibly having support for CM on the H812? It's suck that LG don't seem to want to unlock the locked Canadian and European variant of the G4. If I would have known that earlier I would have went for a Nexus 5 or 6 and not a G4 :/
Not sure where everyone is coming up with this uninformed bullcrap that if your able to boot into the bootloader you are unlocked. The boot loader on EVERY single G4 is LOCKED until you have LG provide you the unlock.bin, after giving them the Device ID from fastboot. If you own an H811 from T-Mobile you can unlock without the unlock.bin. If your lucky enough to be able to access fastboot on other models, it just means you are able to obtain your Device ID for the day LG decides to support the US models. End of discussion, nothing more to talk about!
urlyisis said:
Has anybody bugged LG about unlocking the bootloader recently. Last I see is that they unlocked 815 and others were to follow.
I did, however, find this: https://www.change.org/p/lg-electronics-unlock-bootloader-on-all-g4-devices
Click to expand...
Click to collapse
I've recently contacted LG Canada about releasing an unlock tool for the boot loader on the G4 Canadian variant. I conveyed to them that it is one of the primary features I look for in a phone (I have the G2, G3 and got the G4 in expectation of eventually getting to install other ROMS). I've not received a response yet.
Given that the hardware features are gradually becoming indistinguishable between vendors (and LG is no longer on the world wide market share short list), one way to differentiate yourself and place yourself apart from others is to permit the user the ability to do as they wish with the phone, especially when the costs to maintain future OS releases becomes onerous and unprofitable and developers and open source communities are willing to pick up where vendor left the phone to wither and die.
I had advised them that the G4 will be the last LG phone I will be buying if this is the stance they take.
I gave up on this phone, it's out for hardware repair right now, I'm not even anxious to get it back, I'm enjoying my old unlocked rooted s4
Sent from my GT-I9505G using XDA Free mobile app
Well, that is disappointing to say the least.
I am bought the Canadian LG G4 without even anticipating that it wouldn't be unlocked. I had a LG G3 previously and was generally happy with the phone. Lesson learned I guess. I'll make sure my next phone does not have a locked bootloader, and LG won't be on the list for my next device.
Azure1203 said:
I guess if it just restarts as usual after issuing the command then the bootloader is locked.
Talking about MTS H812.
Click to expand...
Click to collapse
Can this model be used in the United States?
Since theres no straight forward answer and the guides seem to be all over the place i was looking for a straight forward answer.can this be unbranded to like the dev edition or something else?
gillim74 said:
Since theres no straight forward answer and the guides seem to be all over the place i was looking for a straight forward answer.can this be unbranded to like the dev edition or something else?
Click to expand...
Click to collapse
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.
andybones said:
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.
Click to expand...
Click to collapse
Ive read this but theres no straight answer in theory it seems possible http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
gillim74 said:
Ive read this but theres no straight answer in theory it seems possible http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
Click to expand...
Click to collapse
Yea. I guess just gotta wait to see if anyone has tried it, or pull the trigger yourself.
Mods can you please delete this thread as i got my answer and it wont help me in what i was trying to do please
andybones said:
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.
Click to expand...
Click to collapse
I had asked you about this very same thing a couple days back in the Root thread. Glad you were able to find a reliable post, thanks.
Tarima said:
I had asked you about this very same thing a couple days back in the Root thread. Glad you were able to find a reliable post, thanks.
Click to expand...
Click to collapse
Very welcome, my friend. :good:
andybones said:
Very welcome, my friend. :good:
Click to expand...
Click to collapse
Reviving this to ask a related question:
Can I safely flash the latest U.S Unlocked radio to my VZW 10 which has the latest VZW firmware?
If you flash the unlocked radio you will most likely lose all your verizon features such as volte and so on I would not if you use verizon services. For what purpose would you want to may I ask ? If you want to run your Verizon version on At&t or Tmobile there are threads on both I believe, but you should have support for other carriers already I believe as I think you will just get a non Verizon sim message is all but AndyBones can direct you on how to remove that nag.
M9guy said:
If you flash the unlocked radio you will most likely lose all your verizon features such as volte and so on I would not if you use verizon services. For what purpose would you want to may I ask ? If you want to run your Verizon version on At&t or Tmobile there are threads on both I believe, but you should have support for other carriers already I believe as I think you will just get a non Verizon sim message is all but AndyBones can direct you on how to remove that nag.
Click to expand...
Click to collapse
I'm not actually using the phone on Verizon network, I bought it second hand and using it on Rogers network in Canada. Everything runs fine including LTE, but reception is weaker than on my M7 (purchased from Rogers) hence my wanting to try the U.S Unlocked radios to see if things improve. Similarly voice call quality is not that great though it has improved with the 1.82 firmware upgrade.
I don't mind testing out the radio myself, just need some assurance about being able to without bricking the device due to firmware mismatch or other incompatibilities. As pointed out in this thread very little information exists out there from people who have unbranded their VZW 10s or flashed non-VZW radios.
Have you tried running the latest RUU for the Verizon HTC 10 ? This may fix your issue if you have not already. Also I think on another thread Dottat posted a method to reset your bands of some some if you look on his thread for being able to use the unlocked 10 on Verizon he has it posted on there I believe. Resetting the bands or modem has worked for some people with issues with signal.
M9guy said:
Have you tried running the latest RUU for the Verizon HTC 10 ? This may fix your issue if you have not already. Also I think on another thread Dottat posted a method to reset your bands of some some if you look on his thread for being able to use the unlocked 10 on Verizon he has it posted on there I believe. Resetting the bands or modem has worked for some people with issues with signal.
Click to expand...
Click to collapse
I'm not having an "issue" per se, I just want to see if I can get improved reception with a new radio, so I don't think an RUU flash would change much (I have already reset my modem for a separate issue).
Thanks for your help, I'm hoping that andybones or another dev can answer my question about being able to flash a non-vzw radio safely.
Tarima said:
I'm not having an "issue" per se, I just want to see if I can get improved reception with a new radio, so I don't think an RUU flash would change much (I have already reset my modem for a separate issue).
Thanks for your help, I'm hoping that andybones or another dev can answer my question about being able to flash a non-vzw radio safely.
Click to expand...
Click to collapse
Is Rogers a CDMA based carrier (I legit don't know). You may need to do an entire us unlocked swap, not sure if anybody has tried that yet with a vzw phone.
No Rogers is a GSM network but my VZW 10 works fine on it.
If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.
GrimJoke said:
If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.
Click to expand...
Click to collapse
Hi GrimJoke,
Thanks your post! Since I last posted here I've managed to do exactly as you described and ran the Unlocked RUU, updated to 1.96. Now running stock ROM and everything works great, and in fact the phone runs better than it did on vzw software.
I've noticed the same regarding OEM Unlocking. I read from Captain Throwback here that we should now be able to unlock the bootloader with htcdev and with superCID 22222222. I won't try since it's pointless for me.
Tarima said:
Hi GrimJoke,
Thanks your post! Since I last posted here I've managed to do exactly as you described and ran the Unlocked RUU, updated to 1.96. Now running stock ROM and everything works great, and in fact the phone runs better than it did on vzw software.
I've noticed the same regarding OEM Unlocking. I read from Captain Throwback here that we should now be able to unlock the bootloader with htcdev and with superCID 22222222. I won't try since it's pointless for me.
Click to expand...
Click to collapse
Thanks a lot about the bootloader unlocking part. That was the only question I had. Now my life's complete.
GrimJoke said:
If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.
Click to expand...
Click to collapse
how about from Verizon to complete wwe using wwe radios for international gsm network?
does volte work with tmo, att etc after gsm?
Long story short, when I entered the IMEI and DeviceID information on their site to obtain the unlock.bin file necessary to unlock my bootloader, it says DeviceID mismatch, I contacted both customer support and [email protected], they asked to send them the picture of my IMEI label at the back of the phone, which I did and they said it's invalid and they were unable to get the production information of my phone, therefore my unlock.bin file cannot be found.
Now, i'm stuck. I bought US996 model for the main reason to be able to unlock this phone bootloader.
What are my options? can i follow guide to unlock USCellular US996?
It seems that you bought a non-original device.
Try to use Dirtysanta to unlock.
Anoneko said:
It seems that you bought a non-original device.
Try to use Dirtysanta to unlock.
Click to expand...
Click to collapse
Yeah, i'm afraid so. It might be refurbished/replaced motherboard kind of deal. That's a shame but then again I got it for cheap and is fully functional.
So should I use the guide for US996 USCellular?
I'm afraid I might be wandering onto unknown territory and will end up bricking my device
webslasher said:
Yeah, i'm afraid so. It might be refurbished/replaced motherboard kind of deal. That's a shame but then again I got it for cheap and is fully functional.
So should I use the guide for US996 USCellular?
I'm afraid I might be wandering onto unknown territory and will end up bricking my device
Click to expand...
Click to collapse
If you are referring to this thread, yes, you can follow it. Because it is actually written for the US996 Unlocked version.
In fact, even if your device has a replaced motherboard, LG's support will still help you modify the device ID in theirs database to make you unlock, provided this device has the original label.
Anoneko said:
If you are referring to this thread, yes, you can follow it. Because it is actually written for the US996 Unlocked version.
In fact, even if your device has a replaced motherboard, LG's support will still help you modify the device ID in theirs database to make you unlock, provided this device has the original label.
Click to expand...
Click to collapse
AH alright i'll read the thread and see if it'll unlock my phone just fine.
The thing is, I already contacted them regarding my label, and since i think my device has replaced motherboard and the place that replace the motherboard didnt renew the label, the serial number in the label is different than what i can check in setting -> about phone the people at [email protected] cannot check my production info or something (at least that's what they said in email)
They said they can't help me and i should contact customer support, I emailed them 2 days ago, no reply yet.
UPDATE
I sent them another email and talked to their customer service, They said nothing they can do about it.
Looks like i'll need dirtysanta's help. But the guides are for US996 USCellular edition while mine is US996 Unlocked. So far the guides for US996 Unlocked resolves around unlocking bootloader through LG site as it's the sane thing to do.
I would think. That you should be able to use the dirty santa method one way or another ...i would start by asking guestions in the dirty santa threads and maybe even the dev or a dev could help ya...i believe ive read elsewhere someone with a unlocked us996 did use dirty santa but i cant seem to find where i saw it...the us996 unlocked and uscellular versions are real close i believe they are even putting each others versions firmware on opposite version with little problems ....before you go to far setup lgup and make sure you can backup what ya got one way or another and can flash a stock kdz to assure if there is any problems you can at least try to get back to stock...ive seen several unbricking threadsaround and ... imho... it should be hard to hard brick your device..... If you got it cheap you have room to make a decision you can use it as is and enjoy or you can try to crack that egg and if you break that egg you arent out an 800 dollar phone....my 2 cents .....if you need any pointers im glad to help im no dev but ive been around for quite some time and i have a unlocked us996 rooted as well.....hope your venture ends well .....also seen dirty elf bootloader unlock and dev metions using it on unlocked versions to get arround losing warranty through lg bootloader unlock.
neofreek01 said:
I would think. That you should be able to use the dirty santa method one way or another ...i would start by asking guestions in the dirty santa threads and maybe even the dev or a dev could help ya...i believe ive read elsewhere someone with a unlocked us996 did use dirty santa but i cant seem to find where i saw it...the us996 unlocked and uscellular versions are real close i believe they are even putting each others versions firmware on opposite version with little problems ....before you go to far setup lgup and make sure you can backup what ya got one way or another and can flash a stock kdz to assure if there is any problems you can at least try to get back to stock...ive seen several unbricking threadsaround and ... imho... it should be hard to hard brick your device..... If you got it cheap you have room to make a decision you can use it as is and enjoy or you can try to crack that egg and if you break that egg you arent out an 800 dollar phone....my 2 cents .....if you need any pointers im glad to help im no dev but ive been around for quite some time and i have a unlocked us996 rooted as well.....hope your venture ends well .....also seen dirty elf bootloader unlock and dev metions using it on unlocked versions to get arround losing warranty through lg bootloader unlock.
Click to expand...
Click to collapse
Alright then it's decided, i'll start reading DirtySanta and ask around. I'm installing LGUP and LGMobileDriver as we speak
Without AT&T's help?
No, you can contact AT&T, https://www.att.com/deviceunlock
Yes you can. I've done it with a site called unlockplus.
Here you go. Flash one of these KDZ to carrier unlock the phone. You want the ones that say "open" -- which means they are not locked to a carrier.
https://lg-firmwares.com/lg-lmv350ulm-firmwares/firmwares/
https://lg-firmwares.com/lg-lmv350em-firmwares/firmwares/
Top link is for North America Google Fi variant.
Bottom link is for Central/South America -- but if you use that, you do NOT want Claro. You want the other one (carrier unlocked) MIA.
Yeah, flashing an unlocked firmware won't unlock this device. Why in the world would you post something ridiculous like this? How can you have 8185 posts and not know what unlocking means? smh
zeek6228 said:
Yeah, flashing an unlocked firmware won't unlock this device. Why in the world would you post something ridiculous like this? How can you have 8185 posts and not know what unlocking means? smh
Click to expand...
Click to collapse
So your saying that wont work.. I was just about to figure out how to flash it. Good thing i didnt or i would have more than likely bricked it.
zeek6228 said:
Yeah, flashing an unlocked firmware won't unlock this device. Why in the world would you post something ridiculous like this? How can you have 8185 posts and not know what unlocking means? smh
Click to expand...
Click to collapse
Just so you know, you're replying to a guy who (besides other feats) made it possible for anyone to carrier unlock virtually any LG V30 model no matter what carrier it was on previously. And that was made exactly by crossflashing. So yeah, I would kinda listen to him.
zeek6228 said:
Yeah, flashing an unlocked firmware won't unlock this device. Why in the world would you post something ridiculous like this? How can you have 8185 posts and not know what unlocking means? smh
Click to expand...
Click to collapse
Because that's EXACTLY how we carrier unlock the LG V30/V30+. We flash carrier unlocked firmware over carrier locked firmware -- specifically AT&T and Sprint variants. The principle should be the same with the AT&T LG V35.
Besides the two carrier locked North American LG V30 phones (AT&T & Sprint), some of the European LG V30 are also carrier locked. Cross flashing the region appropriate "open market" firmware carrier unlocks them.
I haven't done it on LG V35, but I've done it many, many times on the predecessor LG V30/V30+.
We flash V30 firmware and forth at will to carrier unlock the phones, get fastboot flash commands, bootloader unlock, install TWRP and root. The simplest of all these goals is carrier unlock.
____________
MorbidMonkey101 said:
So your saying that wont work.. I was just about to figure out how to flash it. Good thing i didnt or i would have more than likely bricked it.
Click to expand...
Click to collapse
He says it won't work. Whereas I've carrier unlocked several LG V30/V30+ doing EXACTLY that. And so have hundreds of other people. I've written a couple of guides on the subject.
While I've not done it on LG V35, I suggested this method because it seems reasonable and logical based on the immediate V30 predecessor.
Something similar (cross flashing) also worked on the LG V20. However, in both cases we had Dev Patched LGUP to use. IF it doesn't work for the LG V35, that would be why -- because perhaps the appropriate .dll has not been used to create LG V35 dev patched LGUP.
I can't guarantee it will work on LG V35, the way I can guarantee it does for the LG V30.
lg V35
You can flash it and it will boot (not dead, frozen or stuck in Qualcomm 9008 mode like when you normally flash mismatched firmware, picks up signal fine)
Yes I am aware of how to unlock G6, V30 and G7 by flashing a different firmware and I have unlocked several HUNDRED of them. Even LS998 on V22B firmware.
This will flash successfully (I use Octopus tool, the newest LGUP tool is not released so can't do it that way) but it will still show the V350AWM model and will still be locked to AT&T. Only it will remove the AT&T bloatware.
It is a good solution to flash these if you brick your device. But it won't unlock them.
zeek6228 said:
You can flash it and it will boot (not dead, frozen or stuck in Qualcomm 9008 mode like when you normally flash mismatched firmware, picks up signal fine)
Yes I am aware of how to unlock G6, V30 and G7 by flashing a different firmware and I have unlocked several HUNDRED of them. Even LS998 on V22B firmware.
This will flash successfully (I use Octopus tool, the newest LGUP tool is not released so can't do it that way) but it will still show the V350AWM model and will still be locked to AT&T. Only it will remove the AT&T bloatware.
It is a good solution to flash these if you brick your device. But it won't unlock them.
Click to expand...
Click to collapse
1) Well debloating V35 is at least one advantage others will like, even if it won't carrier unlock it -- and this answer is much better than your first attempt. Can you also now access the bootloader on the V35 and do fastboot flash commands work when, once you flash the open market KDZ? Cross flashing carrier locked North America V30/V30+ to open market US998 allows this, besides carrier unlocking them.
2) If you are aware of how to to carrier unlock AT&T H931 V30 and Sprint LS998 V30/V30+ by flashing different firmware -- like to the US998 V30 open market KDZ -- as well as other LG phone series (G6/G7) using the same technique, and you say you have carrier unlocked "several hundred" by using that technique (with Octopus box, it seems), then your previous insulting post looks like it was written by someone totally ignorant of this Frankenstein process which we use every day to carrier unlock phones like this...
zeek6228 said:
Yeah, flashing an unlocked firmware won't unlock this device. Why in the world would you post something ridiculous like this? How can you have 8185 posts and not know what unlocking means? smh
Click to expand...
Click to collapse
zeek6228 said:
You can flash it and it will boot (not dead, frozen or stuck in Qualcomm 9008 mode like when you normally flash mismatched firmware, picks up signal fine)
Yes I am aware of how to unlock G6, V30 and G7 by flashing a different firmware and I have unlocked several HUNDRED of them. Even LS998 on V22B firmware.
This will flash successfully (I use Octopus tool, the newest LGUP tool is not released so can't do it that way) but it will still show the V350AWM model and will still be locked to AT&T. Only it will remove the AT&T bloatware.
It is a good solution to flash these if you brick your device. But it won't unlock them.
Click to expand...
Click to collapse
I have pulled the RSA certs from every model V35, G7, and V40 that are currently available, and LG learned their lesson from the WTF V30 exploit .. they use different certs for every model.
If you have cross flashed the V35, or G7 .. you are only flashing boot and system. If you had flashed an RSA signed partition, you would have had a brick.
I will be glad to post the certs if you like.
-- Brian
Oh sorry I didn't mean it to be insulting at all but flashing these files will not unlock it.
I'm new on this forum. Sorry for being disrespectful.. Everyone is very thankful to you Only WTF? Why would you suggest to flash something if you never tried it before?
To flash I did flash these firmwares but I used Octopus box (super highly recommended)
Lets do something constructive here though. If you have signed cert files let me test it. I have a couple AT&T V350AWM, we can brick them, it is OK. I'll load anything and post results here.
Again sorry about insulting retort but a forum like this should have only 100% clean reliable info.
Hello everyone,
I just bought a LGV35 form eBay for a few bucks but has bad imei is there any chance that I can unlock the phone? I want to use it outside USA, any idea or can somebody help me?
Regards
runningnak3d said:
I have pulled the RSA certs from every model V35, G7, and V40 that are currently available, and LG learned their lesson from the WTF V30 exploit .. they use different certs for every model.
If you have cross flashed the V35, or G7 .. you are only flashing boot and system. If you had flashed an RSA signed partition, you would have had a brick.
I will be glad to post the certs if you like.
-- Brian
Click to expand...
Click to collapse
Interesting, since the G7 and even V35 was released before V30 WTF was discovered (mid-May 2018). @TxanMoe started the WTF thread with his "crazy" story May 14 -- and you helped him unbrick his phone soon after that. I wrote the WTF instructions on May 21.
Well, V35 was released beginning of June 2018, but it was already in the pipeline by May 2018.
The RSA stuff for every variant is probably more an extension of what LG started with T-Mobile H932...
Very sad.
ChazzMatt said:
Interesting, since the G7 and even V35 was released before V30 WTF was discovered (mid-May 2018). @TxanMoe started the WTF thread with his "crazy" story May 14 -- and you helped him unbrick his phone soon after that. I wrote the WTF instructions on May 21.
Well, V35 was released beginning of June 2018, but it was already in the pipeline by May 2018.
The RSA stuff for every variant is probably more an extension of what LG started with T-Mobile H932...
Very sad.
Click to expand...
Click to collapse
Well, let me clarify. I have only been able to check models that have a KDZ that I can pull the certs from. Any model that either never has KDZ (AT&T or Sprint), or if a KDZ isn't publicly available yet .. I haven't been able to check since I can't get anyone to dump abl.
I will try to post a list of the ones I have checked when the holidays are over.
-- Brian
Hi
I have a lg v35 at&t unlocked and I'm using another carrier(metro pcs) but i can't update it to the latest software version.
Is there any way to get the latest software version?
rapidrayo said:
Hello everyone,
I just bought a LGV35 form eBay for a few bucks but has bad imei is there any chance that I can unlock the phone? I want to use it outside USA, any idea or can somebody help me?
Regards
Click to expand...
Click to collapse
I bought one too. It's bad esn. So someone can help to unlock to use it outside USA? I already tried unlocking company but they didn't find the code... Thanks:good:
Klenti said:
Hi
I have a lg v35 at&t unlocked and I'm using another carrier(metro pcs) but i can't update it to the latest software version.
Is there any way to get the latest software version?
Click to expand...
Click to collapse
How did you go about unlocking it? Did you buy it from ATT without a contract.. Did you use an unlocking service or from att directly for unlock?
Klenti said:
Hi
I have a lg v35 at&t unlocked and I'm using another carrier(metro pcs) but i can't update it to the latest software version.
Is there any way to get the latest software version?
Click to expand...
Click to collapse
If you put an AT&T MVNO sim in it, it should update. When I put a Red Pocket Mobile (MVNO) sim in my v35 along with wifi working, it updated the software to version V350AWM10w even though the phone was not yet activated on the red pocket network. If you can find a pre-paid AT&T sim, it should also work, but I'm guessing there.
(note, my v35 is locked to AT&T, I wonder if your phone being unlocked might have some other 'thing' that might be stopping it from updating)
So, I happened to get my hands on a pair of V20's. Both were us996 models. One was the USA and the other was UCL (US Cellular). In the past, the UCL was not able to be unlocked on LG's website. I was able to unlock the USA model just fine this time. I've tried a BTP model in the past and was not able to, and knew also the UCL was not able to as well. However, I tried anyway. The first hurdle was the IMEI # is 14 digits, which you need 15 digits for it to unlock correctly. (Typically 14 is ONLY CDMA), which UCL is.
This gives the full 15... https://www.imei.info/calc I proceeded to follow LG's guide, going to fastboot, then fastboot oem device-id And guess what, I got a valid unlock.bin from LG and was able to fully unlock the previously unlockable model us996.UCL. (which is not on the list of unlocked still, only us996.USA).
I then flashed my us99610n.zip (The 20f was installed, so needed to downgrade). The phone boots just fine now and works for GSM/CDMA like any other us996.USA device. It presents the yellow warning, vs. the red stop alert.
With all the said, I'm not sure if ALL V20 models are now unlockable, but others will have to try. Ie.. vs995/h990/ls997/h910. I know the h918 was already was, but some fastboot commands were missing. So if anyone else wants to try and report back. You may not even need to really flash the unlock.bin file, more so LG's website initially would not even email the unlock.bin file if it was not able to be done.
LG's Guide: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev (you need an account)
You need to make sure in developer settings to enable OEM unlock. YOU may need to go back to stock to get this option to enable it. Not sure coming from Lineage what will happen.
EDIT: Fortunately I had saved my device-id and IMEI before I rooted so I didn't have to flash stock to test on VS995. I had a 15 digit IMEI without having to find the 15th digit.
Unfortunately it didn't work. I got a model not supported message on the LG developer website. Hopefully it will work for everyone with a UCL model.
Original Post:
I am unable to test this on my dirtycow rooted VS995 because "fastboot oem device-id" does not work presumably because of engineering aboot. EDIT: I see now you did mention this OP.
I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-id
...
FAILED (remote: unknown command)
finished. total time: 0.073s
Click to expand...
Click to collapse
I suppose I could flash stock to see if it works on my spare device if no one else tests this on non us996 variants in the meantime.
Would be fantastic if it works! Great as it is because at least UCL versions are easier to come by than the USA version from what I see for sale online.
I have LG V20 F800L. Fastboot mode is also not available in it. You can unlock the bootlader method DirtySanta ( XDA [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide )
This is interesting. Nice find. Hopefully the door can be unlocked. Ls997 for me lol. One fully rooted, one temp root on Oreo, and other Unrooted ZVD.
A user on the V20 Subreddit got the US996 BPT unlocked via LG. So now it appears that at least all US996 models (USA, UCL, BPT) can get their bootloaders officially unlocked through LG's website.
C D said:
A user on the V20 Subreddit got the US996 BPT unlocked via LG. So now it appears that at least all US996 models (USA, UCL, BPT) can get their bootloaders officially unlocked through LG's website.
Click to expand...
Click to collapse
Not all, but I wish. I have a US996 UCK model (US CELLULAR_TULSA(USA) that this doesn't work on:
"Unfortunately, your device( United States, (US CELLULAR_TULSA(USA)), LGUS996.UCK )does not support unlocking the bootloader. Your account will be locked if you enter the wrong information more than 9 times." (down to 7 now - LOL.)
My IMEI is already 15 digits (vs 14 as noted), so no need to convert/find the check digit. This is just a standby phone, but it would be nice to unlock it without using the engineering BL/DS method. Same holds true with a pair of VS995's that I have.
Perhaps I overlooked something?
EDIT: I have another US996 device coming next week that "appears" to be the real McCoy (Carrier Code: USA) according to the IMEI . Hopefully this one is legit.
fathergweedo said:
Not all, but I wish. I have a US996 UCK model (US CELLULAR_TULSA(USA) that this doesn't work on:
"Unfortunately, your device( United States, (US CELLULAR_TULSA(USA)), LGUS996.UCK )does not support unlocking the bootloader. Your account will be locked if you enter the wrong information more than 9 times." (down to 7 now - LOL.)
My IMEI is already 15 digits (vs 14 as noted), so no need to convert/find the check digit. This is just a standby phone, but it would be nice to unlock it without using the engineering BL/DS method. Same holds true with a pair of VS995's that I have.
Perhaps I overlooked something?
EDIT: I have another US996 device coming next week that "appears" to be the real McCoy (Carrier Code: USA) according to the IMEI . Hopefully this one is legit.
Click to expand...
Click to collapse
Interesting to know. I haven't heard of the UCK variant before. Does it say UCK next to the barcode on the sticker behind the battery?
According to the LG firmware page, it looks like there's even a 5th region called BPS (another Brightpoint model) for the US996. So I guess we still can't go buy US996s blindly for the official bootloader unlock. No surprise about the VS995 as Verizon (along with AT&T) had locked bootloaders on their phones for ages now.
C D said:
Interesting to know. I haven't heard of the UCK variant before. Does it say UCK next to the barcode on the sticker behind the battery?
According to the LG firmware page, it looks like there's even a 5th region called BPS (another Brightpoint model) for the US996. So I guess we still can't go buy US996s blindly for the official bootloader unlock. No surprise about the VS995 as Verizon (along with AT&T) had locked bootloaders on their phones for ages now.
Click to expand...
Click to collapse
Yes, UCK on the sticker. Just for kicks I flashed the USA firmware US99610f_00_1205.kdz in hopes it made a difference, but it returns the same unlock string.
I tried it with a H990ds TWN and it did not work ("Unfortunately, your device..."). That was to be expected, but I tried it anyway just in case.
I had a US996 that I previously could not unlock.
The error said something in the lines of this model US996Z is not supported.
I tried the LG developer site again today and it gave me an unlock key.
Thanks for the heads up ?
I noticed that the LG developer site now has a pop-up message saying that it will terminate at the end of the year, so all official bootloader unlocks will no longer be possible after that. Anyone who wants to root any of the supported US996 models after this year would need to do the DirtySanta process.