Related
Do we know if the Marshmallow update updates the bootloader?
Our current root method uses an exploited 5.1 system, so it will not work on 6.0. Someone will need to use a similar exploit on the 6.0 system if the exploit does indeed still work.
If the bootloader is not updated with 6.0, we will be able to go back to 5.1 simply by flashing the 5.1 system. If it is updated, we may have lost root for forever. I will stick with 5.1 for now and I will take the Marshmallow update this Sunday if there is no additional information.
Any way to update to MM if you are using a Verizon V10 on AT&T?
jabreu203 said:
Any way to update to MM if you are using a Verizon V10 on AT&T?
Click to expand...
Click to collapse
you can use the kdz but it's nowhere to be seen
I'm in the same boat with a T-Mobile sim. Waiting for a kdz to get onto Marshmallow.
If you tell me how I can do it.
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
jalthejew said:
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
Click to expand...
Click to collapse
You should be able to find the bootloader version in a benchmark app, then I could do the same
The bootloader does not actually need to be unlocked at all to root the device. All you need is the KDZ file and some experienced hacking to do it. That's how we got root for the V10 anyways.
i have a weird question to ask. i am using att sim card on a Verizon v10. can i flash a kdz att or even the unlocked version system on the Verizon variant ?
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
hann1balk1ng said:
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
Click to expand...
Click to collapse
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
Lets hope so.....
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
They might not be so inclined. IIRC, they were rightly agitated when someone open-sourced their work, potentially making it easier for manufacturers to prevent in the future, despite them specifically advising against it.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
NetworkingPro said:
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
Click to expand...
Click to collapse
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
kjcsg said:
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
Click to expand...
Click to collapse
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
NetworkingPro said:
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
Click to expand...
Click to collapse
My only question then is why would they leave the original, the lg recovery, there when you would power on while holding volume down and have to go through the factory reset button to get to twrp instead of just overwriting the original with twrp completely? Not that it matters too much, I just wish I knew how to do it so I could get the vs990 bumped or somehow get twrp on it. But I think I'd need a good bit of exploit schooling to understand it all haha.
I hope we get at least recovery soon, but I've never understood why recoveries never have a text editor included! (and often not even shell access, much less SU shell access!)
Can this brick your phone/void your warranty? Of course it could! I wouldn't be posting it on XDA if it couldn't!
TeutonJon78 said:
Just be aware that once you unlock, you won't get anymore OTA updates at the current moment, and there's not full factory images to fall back on. They will still try to push OTAs if anyone does this bootloader unlock method, but they will always fail due to version checking.
Click to expand...
Click to collapse
So as it stands right now, if you do this, you're not going to get further updates from ZTE, unless they change their stance.
Here's a method that should work for any brave souls. It's the method I used so far.
My understanding is this update only makes the required patches to allow the command fastboot oem unlock to actually unlock the bootloader. That being said, I do not know for sure that this is not specific to my phone's IMEI. If someone would supply me with the file/link they get from using adb shell logcat > ota.txt while checking for updates, then grep ota.txt | ZDMLog (if you use linux) or do a find for https:// in ota.txt it would be useful for this verification.
For microSD card method:
Take this (Thanks DrakenFX) or this file and put it in /sdcard/, making sure extension is .zip
Enable OEM unlock from the settings->development menu.
Reboot phone (or boot phone) while pressing volume up. This will get you into stock recovery. From here, apply update from SD card, P996A01B20Fastboot_ssl.zip
No microSD card method:
This may also be possible without an SD card using the adb sideload option in stock recovery and "adb sideload P996A01B20Fastboot_ssl.zip" on your desktop. If you are successful using this method, send me a PM so I can update this post.
Now if you reboot into bootloader (which you can do right from recovery), you will hopefully find that "fastboot oem unlock" actually brings up the bootloader unlock prompt on your phone.
You should be able to verify to this point as per below.
Without using the fastboot oem unlock command I have not lost any user data (but it's still a good idea to back it up!) If you do unlock, you will lose your data!
This method requires 20B to already be installed, correct? If so, is there a way to sideload the 20B update (so one can go from launch firmware -> sideloaded 20B -> sideloaded 20B_boot)? Juuuust in case ZTE puts out a 20C or something that blocks sideloading and renders "unofficial" bootloader unlock attempts like this invalid.
xtermmin said:
This method requires 20B to already be installed, correct? If so, is there a way to sideload the 20B update (so one can go from launch firmware -> sideloaded 20B -> sideloaded 20B_boot)? Juuuust in case ZTE puts out a 20C or something that blocks sideloading and renders "unofficial" bootloader unlock attempts like this invalid.
Click to expand...
Click to collapse
It does require 20B to be installed. It appears 20B can sideloaded as well. The only error message I received was 20B expects 20160624 or 20160707 (and I'm now at 20160805). Maybe someone can try to sideload 20B on 20B?
So looking through the update script, it seems to check for SHA1 matches for certain parts of the boot, system and recovery partitions. I'm not sure if the patch itself has content specific to an IMEI or if this is just a simple check to make sure the phone has the correct build installed.
Looking at this, it seems the purpose of the part of the script before # ---- start making changes here ---- is used to verify a correctly configured system, with no apparent relation to the IMEI. It looks like the script itself is completely generic, and the checks could probably be removed so this will work on any build. Now we just need another update package to compare the other content (fastboot.img, patch\boot.img.p, patch\recovery.img.p) with to see if they're generic as well. This makes me wonder if flashing fastboot.img alone is enough, as that's what is used to interface with the bootloader unlock.
Helpful references:
Built-in functions in update binary
range_sha1
dennis96411 said:
So looking through the update script, it seems to check for SHA1 matches for certain parts of the boot, system and recovery partitions. I'm not sure if the patch itself has content specific to an IMEI or if this is just a simple check to make sure the phone has the correct build installed.
Looking at this, it seems the purpose of the part of the script before # ---- start making changes here ---- is used to verify a correctly configured system, with no apparent relation to the IMEI. It looks like the script itself is completely generic, and the checks could probably be removed so this will work on any build. Now we just need another update package to compare the other content (fastboot.img, patch\boot.img.p, patch\recovery.img.p) with to see if they're generic as well. This makes me wonder if flashing fastboot.img alone is enough, as that's what is used to interface with the bootloader unlock.
Helpful references:
Built-in functions in update binary
range_sha1
Click to expand...
Click to collapse
Man I hope so, then the rest of the world can get a bootloader unlock even if ZTE won't unlock the bootloader for us.....
Has anyone captured 20B and has it for others to try?
My phone won't come until next week (first wave of grays), but I'll try capturing it if it's not already installed. We just have to wait 5 days
rczrider said:
Has anyone captured 20B and has it for others to try?
My phone won't come until next week (first wave of grays), but I'll try capturing it if it's not already installed. We just have to wait 5 days
Click to expand...
Click to collapse
I think this is it: http://forum.xda-developers.com/showpost.php?p=68109239&postcount=5
There are no full system images available for the US model yet, unfortunately.
xtermmin said:
I think this is it: http://forum.xda-developers.com/showpost.php?p=68109239&postcount=5
There are no full system images available for the US model yet, unfortunately.
Click to expand...
Click to collapse
So in theory, the process would be to sideload the 20B update, reboot, then sideload the file in the OP?
Hopefully someone will get around to testing this method (or at least the OP's file) before my phone comes next week, but if not, I'll do it first thing.
rczrider said:
So in theory, the process would be to sideload the 20B update, reboot, then sideload the file in the OP?
Hopefully someone will get around to testing this method (or at least the OP's file) before my phone comes next week, but if not, I'll do it first thing.
Click to expand...
Click to collapse
In theory, yes (You could also update to 20B normally, but good to have it as a backup). Hopefully 20B_Boot is not device-specific.
xtermmin said:
In theory, yes (You could also update to 20B normally, but good to have it as a backup). Hopefully 20B_Boot is not device-specific.
Click to expand...
Click to collapse
I assume the most likely outcome is that it simply wouldn't flash. Even so, I'm willing to be a bit reckless as I can just return the phone for new one (via the retailer, not ZTE)
rczrider said:
I assume the most likely outcome is that it simply wouldn't flash. Even so, I'm willing to be a bit reckless as I can just return the phone for new one (via the retailer, not ZTE)
Click to expand...
Click to collapse
Haha same but never dealt with B&H so we'll see how that goes. Still waiting for the grey one.
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
So everyone should update to B20 as soon as possible and then not update to anything else.
reddrago said:
Haha same but never dealt with B&H so we'll see how that goes. Still waiting for the grey one..
Click to expand...
Click to collapse
They're fantastic. 30-day (from delivery) no-questions-asked return policy on smartphones. If there's an actual problem with the phone, they'll even pay for return shipping. No restocking fee in either case.
If there is a problem with the phone itself, you can exchange it and the 30-day return policy resets from delivery of the replacement unit.
jkuczera said:
Reboot phone (or boot phone) while pressing volume up. This will get you into stock recovery. From here, apply update from SD card, P996A01B20Fastboot_ssl.zip
Click to expand...
Click to collapse
I was trying but Can't use " apply update from SDCard " but the "apply update from ADB " seems to be enable just didn't try cuz i don't have my laptop with me at the moment (till i get home) , check picture.
P.S. just to clear things up when i select "apply Update from SDCard" is when i get that message, so the ADB option is the only way for me to apply this and yes I'm in B20.
DrakenFX said:
I was trying but Can't use " apply update from SDCard " but the "apply update from ADB " seems to be enable just didn't try cuz i don't have my laptop with me at the moment (till i get home) , check picture.
Click to expand...
Click to collapse
Did you have an update file in /sdcard/ ? Since this is the stock recovery, I'm quite certain it's looking for a physical microSD for this usage scenario.
jkuczera said:
Did you have an update file in /sdcard/ ? Since this is the stock recovery, I'm quite certain it's looking for a physical microSD for this usage scenario.
Click to expand...
Click to collapse
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
DrakenFX said:
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
Click to expand...
Click to collapse
Try changing the filename to P996A01B20Fastboot_ssl.up. The direct-link from ZTE for the 20B update has that extension.
DrakenFX said:
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
Click to expand...
Click to collapse
It's got to be another issue altogether because I can pull up the SD card menu even if I don't have files in there.
jkuczera said:
It's got to be another issue altogether because I can pull up the SD card menu even if I don't have files in there.
Click to expand...
Click to collapse
I got this from the recovery log from the Recovery menu.
sd_upgrade_disable = 1
Check image
DrakenFX said:
I got this from the recovery log from the Recovery menu.
sd_upgrade_disable = 1
Check image
Click to expand...
Click to collapse
You're also getting a
Code:
get_oem_unlock_statut oem_unlock_enabled=0
that isn't looking good .
TeutonJon78 said:
See, it's bull**** like this that prevents OEMs from wanting to support third party development in the first place with things like bootloader unlocks. In the ZTE forums aren't you arguing that it's fair to not cover software related problems after unlocking, but here you are wanting them to cover that as well. B&H just charges the defective unit back to ZTE in the end.
Click to expand...
Click to collapse
It's all the same to ZTE in this instance because they will reflash their stock software upon return of the phone since it's not for a warranty repair.
djona12 said:
You're also getting a
Code:
get_oem_unlock_statut oem_unlock_enabled=0
that isn't looking good .
It's all the same to ZTE in this instance because they will reflash their stock software upon return of the phone since it's not for a warranty repair.
Click to expand...
Click to collapse
That's because i haven't been able to flash the file from OP and enable OEM after
I bought a LGL43AL tracphone. I tried to root it with several root apps and PC programs. I was finally able to root it with Kingo Root via PC. However, When I tried to run SuperSU I get a message "There is no SU binary installed and Super SU cannot install it. This is a problem!". Also, when I reboot my phone, it becomes unrooted. After trying many things, I have come to the conclusion that my bootloader is locked. On this phone, recovery is merely to reset to factory mode. There are no other options. I did find a tutorial on how to unlock European lg tracfones by getting a code. I am in the US and was leary to try it. Which led me here to get some advice. Any help or suggestions would be great.
Ok, so I've been looking into this some more and have found that the For LG Optimus Zone 3, LG K4 LTE, LG Spree, and the LG Rebel LTE are basically the same phone. Does this mean that I can use the same method to root my phone (mine being the Rebel LTE)? I ask because there are ample threads on the Optimus zone 3. I don't really care about the warranty on my phone. I just don't want to brick it.
@becksterorange
This was the method I used to replace KingUser with SuperSU on a few different devices.
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Sent from my SM-T230NU using XDA Labs
becksterorange said:
Ok, so I've been looking into this some more and have found that the For LG Optimus Zone 3, LG K4 LTE, LG Spree, and the LG Rebel LTE are basically the same phone. Does this mean that I can use the same method to root my phone (mine being the Rebel LTE)? I ask because there are ample threads on the Optimus zone 3. I don't really care about the warranty on my phone. I just don't want to brick it.
Click to expand...
Click to collapse
Did you get anywhere with rooting your rebel? Waiting to see what others come up with so i don't run into a brick.
forlani101 said:
Did you get anywhere with rooting your rebel? Waiting to see what others come up with so i don't run into a brick.
Click to expand...
Click to collapse
I haven't tried again yet. Been too busy at work. I might get a chance to try if it rains today because I won't have to go to work. I'll get back to you when I do though.
Fail. I can get my phone to root. But, when I try to install the su binary by any method, I lose my root. ?
Sent from my LGL43AL using Tapatalk
becksterorange said:
Fail. I can get my phone to root. But, when I try to install the su binary by any method, I lose my root. ��
Sent from my LGL43AL using Tapatalk
Click to expand...
Click to collapse
I tried also with kingo and kingroot and lost root also. Bummer. Not a big deal but root is always welcomed. Main thing i use root for is to use the adaway app and delete that god aweful tracfone boot and shutdown logo, which requires root. Maybe someone else will figure it out and share with us.
I disabled most of the google apps as they are useless to me. Very snappy for what it is. I got it on a good deal at walmart. They had it priced wrong at $19.98 and had to sell it to me because of their goof up. Was suppose to be like $79.99.
Nice price for your phone. I really just like to get rid of the bloat and to use lucky patcher. Maybe someday on this phone. ?
Sent from my LGL43AL using Tapatalk
I got the LG L44VL version for tracfone. Looks like there is no root for this device. Like anything newer than 2014 and low end is a no go.
utahman1971 said:
I got the LG L44VL version for tracfone. Looks like there is no root for this device. Like anything newer than 2014 and low end is a no go.
Click to expand...
Click to collapse
I'm having the same challenges, too.
Has anyone tried oem unlock?
Nope...still researching.
I was wondering if anyone has tried " fastboot oem unlock-go" command.
We need a way to access our bootloader. Can some one please assist?
Just wondering if this device has been rooted yet? I'd like to install the latest google dialer?
very unlikely you will ever see root, unless someone finds an exploit.
definitely not looking good currently. Honestly the only thing I want root for is so that I can remove carrier bloat and get my ad blocker. Everything else on the phone is fine (I can even deal with LG's skin if I had to)
rodcpierce said:
definitely not looking good currently. Honestly the only thing I want root for is so that I can remove carrier bloat and get my ad blocker. Everything else on the phone is fine (I can even deal with LG's skin if I had to)
Click to expand...
Click to collapse
AFAIK you do not need root for either of those things. I have no tried it myself, but you should be able to remove bloat by adb.
As for ad blocking maybe try this?
poncespr said:
AFAIK you do not need root for either of those things. I have no tried it myself, but you should be able to remove bloat by adb.
As for ad blocking maybe try this?
Click to expand...
Click to collapse
I tried one of the ad removal tool that uses adb, the only package that comes up is the LG setup package. Nothing else. I'll try it manually maybe. I'll have to search as I'm not sure how to do that.
I'll look into that ad blocker.
rodcpierce said:
I tried one of the ad removal tool that uses adb, the only package that comes up is the LG setup package. Nothing else. I'll try it manually maybe. I'll have to search as I'm not sure how to do that.
I'll look into that ad blocker.
Click to expand...
Click to collapse
This screenshot is the short version on how to remove apps via ADB. I have not tried and remember, if you remove something you should not, you might screw up your phone.
poncespr said:
This screenshot is the short version on how to remove apps via ADB. I have not tried and remember, if you remove something you should not, you might screw up your phone.
Click to expand...
Click to collapse
OK, so the DNS one is what I tried before, its pretty **** compared to actual adaway or adblocker.
And you cannot do anything with ADB as you cannot boot to fastboot or bootloader. So that wont work eithe.r
rodcpierce said:
OK, so the DNS one is what I tried before, its pretty **** compared to actual adaway or adblocker.
And you cannot do anything with ADB as you cannot boot to fastboot or bootloader. So that wont work eithe.r
Click to expand...
Click to collapse
My guess is that you use ADB on your pc with developer options activated on the phone. I have not tried it because I am happy with the phone the way it is. Only wish for timely software updates.
poncespr said:
My guess is that you use ADB on your pc with developer options activated on the phone. I have not tried it because I am happy with the phone the way it is. Only wish for timely software updates.
Click to expand...
Click to collapse
Yeah, you can't do anything with ADB shell without access to the bootloader/fastboot.
rodcpierce said:
Yeah, you can't do anything with ADB shell without access to the bootloader/fastboot.
Click to expand...
Click to collapse
Is that specifically for the H931? I mean, doesn't it it allow USB Debugging in Developer Options?
I trimmed a ton of bloat from my T-Mobile H932 using ADB uninstall, and I've never loaded fastboot on this phone. (Some day I will, assuming the H932 gets root, but today is not that day.)
TheDannemand said:
Is that specifically for the H931? I mean, doesn't it it allow USB Debugging in Developer Options?
I trimmed a ton of bloat from my T-Mobile H932 using ADB uninstall, and I've never loaded fastboot on this phone. (Some day I will, assuming the H932 gets root, but today is not that day.)
Click to expand...
Click to collapse
I'm not sure. I have USB debugging enabled. I literally cannot get ADB to recognize the device.
rodcpierce said:
I'm not sure. I have USB debugging enabled. I literally cannot get ADB to recognize the device.
Click to expand...
Click to collapse
Try toggling UDB Debugging on the phone and give permission (again) for your computer to access it.
Which driver are you using?
I am on Windows 10 and using LGMobileDriver_WHQL_Ver_4.2.0. It can be downloaded from the following LG web site:
http://www.lg.com/us/support/product-help/CT10000025-20150179827560-software-version-update
If you are using a different driver, I suggest uninstalling it first and thoroughly removing remnants of it it by repeatedly deleting the device in Device Manager and choose "Delete driver software", then "Scan for Hardware", until it no longer gives you the option to "Delete driver software". Now unplug the phone and install the driver anew.
TheDannemand said:
Try toggling UDB Debugging on the phone and give permission (again) for your computer to access it.
Which driver are you using?
I am on Windows 10 and using LGMobileDriver_WHQL_Ver_4.2.0. It can be downloaded from the following LG web site:
http://www.lg.com/us/support/product-help/CT10000025-20150179827560-software-version-update
If you are using a different driver, I suggest uninstalling it first and thoroughly removing remnants of it it by repeatedly deleting the device in Device Manager and choose "Delete driver software", then "Scan for Hardware", until it no longer gives you the option to "Delete driver software". Now unplug the phone and install the driver anew.
Click to expand...
Click to collapse
I just got done doing this and it worked. I was just going to come back here and reply. I couldnt get the device to recognize in ADB at all. Ended up having to uninstall google's universal USB drivers, uninstall LG's drivers and then reinstall LG's drivers and now it comes up as a recognized device! Lets get this party started
---------- Post added at 07:01 PM ---------- Previous post was at 06:45 PM ----------
Alright, all of LG's apps and ATT's **** is gone. nice!
Dns66 is decent considering no root access
rykr said:
Just wondering if this device has been rooted yet? I'd like to install the latest google dialer?
Click to expand...
Click to collapse
INSANEMODE said:
very unlikely you will ever see root, unless someone finds an exploit.
Click to expand...
Click to collapse
Exploit found by @TxanMoe on LG Oreo. All LG V30/V30+/V30S can be bootloader unlocked and rooted -- EXCEPT for the T-mobile H932.
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
________________________________________________________________
oceansoul said:
Dns66 is decent considering no root access
Click to expand...
Click to collapse
All AT&T H931 have root if you want it. See the WTF bootloader unlock and root thread.
Many people on here have rooted their AT&T H931 V30. And run them on AT&T as converted US998.
1) And please don't start with the no LTE thing you tried to say in other threads. All carrier unlocked North America V30 get LTE on AT&T -- especially US998. I've proven it over and over. Your particular AT&T store (and you didn't seem to get a second opinion?) seemed obsessed by your IMEI. (Other stores couldn't care less.)
AT&T allows BYOD from anywhere. You do NOT have to have an AT&T phone to be on AT&T. We've NEVER NEVER NEVER owned an AT&T branded phone, and my wife and I have been on AT&T since 2012.
Well, you now HAVE an official AT&T IMEI. So, convert it to US998, unlock the bootloader and ROOT it. You already have a working AT&T SIM card and AT&T IMEI (which doesn't really matter, but for some reason it matters to you).
2) Point is, you NOW have an AT&T phone and AT&T IMEI and AT&T SIM card (which you THINK you needed for AT&T, but you don't) -- so go unlock your bootloader and root your AT&T phone! I would suggest never going back to that particular AT&T store any more, and they are totally incompetent.
Here's some of my AT&T LTE speeds on my non-AT&T US998:
duplicate
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.