Hoping someone with a rooted Ls997 is willing to help the current rooting effort.
If you are please check out this thread
https://forum.xda-developers.com/v20/help/want-help-rooting-security-patches-t3680397
Thanks
To try an alleviate any fears, there is a near zero percent chance that anything bad will happen to your phone. I say near zero, because things can always go wrong.
With that said, there are only a couple of ways to brick a V20:
* Flash firmware with a lower ARB version than what is burned into your QFPROM
* Flash firmware with a different RSA key than what is burned into your QFPROM
* Wipe your XBL or ABOOT partitions
* Wipe RECOVERY, LAF *AND* SYSTEM all at the same time.
As long as you have a working XBL, ABOOT and RECOVERY you can recover your phone.
What I need is someone with a rooted LS997 that is willing to flash firmware from a model that has a KDZ. I haven't checked yet, but as soon as someone can get me the XBL from the LS997, and I can compare it to the VS995. They seem to be the closest in specs, and have the greatest chance of actually booting -- and that is all we need is for the phone to boot so that it can be rooted. Once rooted, we will put the LS997 firmware back on the phone.
This is the same procedure that I did for rooting the H910 with an H915 KDZ. As far as I know, all LS997s are ARB 0, so even the latest firmware should be rootable if we can find a model's firmware that will boot.
EDIT: ZVA firmware is ARB 1 so you need ZV9 or older.
-- Brian
We just need one. You don't even need to be a "brave" person. Anyone? Tap tap tap........is this mic on????
Please?
Is this post still going on... Also my Sprint LS997 isn't at VZA anymore, its at VZB. Im not sure if that means anything.
Any updates for zva and zvb .....
runningnak3d said:
To try an alleviate any fears, there is a near zero percent chance that anything bad will happen to your phone. I say near zero, because things can always go wrong.
With that said, there are only a couple of ways to brick a V20:
* Flash firmware with a lower ARB version than what is burned into your QFPROM
* Flash firmware with a different RSA key than what is burned into your QFPROM
* Wipe your XBL or ABOOT partitions
* Wipe RECOVERY, LAF *AND* SYSTEM all at the same time.
As long as you have a working XBL, ABOOT and RECOVERY you can recover your phone.
What I need is someone with a rooted LS997 that is willing to flash firmware from a model that has a KDZ. I haven't checked yet, but as soon as someone can get me the XBL from the LS997, and I can compare it to the VS995. They seem to be the closest in specs, and have the greatest chance of actually booting -- and that is all we need is for the phone to boot so that it can be rooted. Once rooted, we will put the LS997 firmware back on the phone.
This is the same procedure that I did for rooting the H910 with an H915 KDZ. As far as I know, all LS997s are ARB 0, so even the latest firmware should be rootable if we can find a model's firmware that will boot.
EDIT: ZVA firmware is ARB 1 so you need ZV9 or older.
-- Brian
Click to expand...
Click to collapse
Hello bro! Appreciate your efforts! Any updates regarding possibility to root ls997 with ARB>0
I'm still using my LG V20 and I really love it and not planning to switch to another phone anytime soon :'(
Yes. If your arb is 0 you can root. There is a thread about it. Sorry don't have link.
https://forum.xda-developers.com/v20/how-to/root-ls997-to-zv9-t3696488
Sorry miss read your post. You said greater then 0. Look for a post that about. LAF. That's where all the action is
First the cool. I have wondered for a while if you check ARB via the SVC -> Version menu, and it says: "non-fusing device" exactly what that meant. Today I found out.
If you are lucky enough to have a non-fusing device, ARB isn't checked, you can run any ARB you want, and roll back to any version.
That leads to the question(s). I currently don't have device that is rooted with the engineering aboot. Can someone that is rooted, check to see what ARB version is displayed in that menu? I don't remember.
Which leads to the next question. Is there anyone that is currently running ARB 1 or greater firmware with the engineering aboot? For example, and LS997 with ZV8 or higher.
-- Brian
I'll check, but can't remember how to get into SVC for the H990
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
H910 running alpha 10T here, rooted with your tutorial (H915 -> H910 10R)
still showing non-fusing device.
runningnak3d said:
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
Click to expand...
Click to collapse
Thanks! My H990 is showing ARB 0
Some more info that may or may not be helpful:
• SW = H990 10e ZAF
• Kernel = DOTS 1.4
• SEPolicy = "Should be implemented" (guessing this means off)
• Bootloader Unlock Check = Bootloader Locked
Hope this helps in some way!
runningnak3d said:
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
Click to expand...
Click to collapse
My LS997 doesn't do anything when I type in *#lgmenu#*997#
@pro_granade Sprint pulled that menu, but I know for a fact that ZV8 is ARB 1, so if you are rooted and running ZV8 then you are ARB 1.
I am only interested in rooted ARB 1 or greater.
-- Brian
runningnak3d said:
@pro_granade Sprint pulled that menu, but I know for a fact that ZV8 is ARB 1, so if you are rooted and running ZV8 then you are ARB 1.
I am only interested in rooted ARB 1 or greater.
-- Brian
Click to expand...
Click to collapse
I'm non rooted locked bootloader on ZV9. Wanted to check if I had a non-fusing device
Well, you can always flash ZV7 or lower, and if you don't have a brick, you have a non-fusing device
On a serious note, I am looking to see how that is determined. It isn't pulled from the firmware, because the devices that I have checked all have some ARB version in the firmware, and yet ARB isn't respected.
Also, a non-fusing device can be turned into a fusing device via some method, but I don't believe the opposite is true. However, as long as the device reports non-fusing, ARB is ignored.
-- Brian
runningnak3d said:
First the cool. I have wondered for a while if you check ARB via the SVC -> Version menu, and it says: "non-fusing device" exactly what that meant. Today I found out.
If you are lucky enough to have a non-fusing device, ARB isn't checked, you can run any ARB you want, and roll back to any version.
That leads to the question(s). I currently don't have device that is rooted with the engineering aboot. Can someone that is rooted, check to see what ARB version is displayed in that menu? I don't remember.
Which leads to the next question. Is there anyone that is currently running ARB 1 or greater firmware with the engineering aboot? For example, and LS997 with ZV8 or higher.
-- Brian
Click to expand...
Click to collapse
I got unlocked & rooted H910 running 10T and it says "non-fusing device'. This would be a treat if Oreo increments ARB and we are still able to flash it without having second thoughts!
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
runningnak3d said:
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
Click to expand...
Click to collapse
My h910 shows the antirollback version as 0 instead of non-fusing device. So maybe only some h910's are non-fusing?
Also I'm currently running full stock so I do not have the eng aboot installed.
runningnak3d said:
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
Click to expand...
Click to collapse
pretty sure its related to the aboot. I ran zv8 all arb1 except i had the eng aboot installed.
Very interesting. I flashed my H910 back to stock, so no engineering aboot, and it is still non-fusing. So there are definitely phones that don't have the "respect ARB security" qfuse blown.
But it looks like maybe the engineering aboot may ignore it. So now the question is, if you have the engineering aboot installed, and you flash a higher ARB boot stack, does ARB get incremented?
Another question is what happens if you are ARB 1 or 2 and install the engineering aboot? As far as I can tell, it will work with any ARB version, but I have no way to test that since I have an H910 that is ARB 0 even if it wasn't non-fusing, and an H918 that can't use it.
More questions than answers. Lol.
-- Brian
It's been a while for me and I have a H918 that is running a rooted H91810p rom, I'm thinking my ARB is still 0, I want to install Super Rom 4.0 but I'm hesitating because I just don't want to brick my phone.. What is the current ARB for my model or how can I find it in my Hidden Menu settings..
Thank you in advance..
JustZaphod said:
It's been a while for me and I have a H918 that is running a rooted H91810p rom, I'm thinking my ARB is still 0, I want to install Super Rom 4.0 but I'm hesitating because I just don't want to brick my phone.. What is the current ARB for my model or how can I find it in my Hidden Menu settings..
Thank you in advance..
Click to expand...
Click to collapse
Im 99% sure that 10P is arb1 as I remember 10k was the last arb0 firmware. You could always just flash the latest stock ROM that dimmock is hosting in here somewhere. 10u is latest but I think he still had about 2 more versions behind that. It's an easy zip you flash in TWRP that is modified so it doesn't flash stock recovery
KUSOsan said:
Im 99% sure that 10P is arb1 as I remember 10k was the last arb0 firmware. You could always just flash the latest stock ROM that dimmock is hosting in here somewhere. 10u is latest but I think he still had about 2 more versions behind that. It's an easy zip you flash in TWRP that is modified so it doesn't flash stock recovery
Click to expand...
Click to collapse
Yeah, I checked the Service Menu and noticed it was ARB 1...
I just forgot how to get into that Hidden Menu...
Hello,
I Just bought from a website a " refurbished " LG V20 and sadly when I turned it on I was shocked it was on att but it's unlocked, but sadly since it's at&t I can't get software updates, is there a way that I can have a stock rom on it instead off at&t? if yes can you guys show me how ?
Note: I have 0 experience and how to do these kind of things but I can follow guide lines.
Search for backup EFS. Do it.
Then feel free to flash the US996 KDZ. Again, if you search, there is plenty of info.
-- Brian
runningnak3d said:
Search for backup EFS. Do it.
Then feel free to flash the US996 KDZ. Again, if you search, there is plenty of info.
-- Brian
Click to expand...
Click to collapse
Yep no spoon ? feeding
Sent from my LG-H910 using XDA Labs
thank you fr the reply!
I did this set uphttps://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 and i finshed it but now I am a bit confused on which rom to download follow guide lines , giving a help wull be nice >.>
MrSalue said:
thank you fr the reply!
I did this set uphttps://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 and i finshed it but now I am a bit confused on which rom to download follow guide lines , giving a help wull be nice >.>
Click to expand...
Click to collapse
Again no spoon ? feeding, try them out and find the one you like
Sent from my LG-H910 using XDA Labs
cnjax said:
Again no spoon ? feeding, try them out and find the one you like
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
MrSalue said:
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
Click to expand...
Click to collapse
No one is making anything difficult, search the forum, read the OP of rom threads until you find what you're looking for, how difficult is it to do some reading,? #NoSpoonFeeding
Sent from my LG-H910 using XDA Labs
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
runningnak3d said:
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
Click to expand...
Click to collapse
Lmao with a nick starting with Mr, you might be in for a surprise
Sent from my LG-H910 using XDA Labs
He got spoon fed
runningnak3d said:
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
Click to expand...
Click to collapse
Thank you, your post is the first one I found that makes it seem fairly simple.
I have 2 V20 h910s I want to unbrand, one running AT&T version 10m and one running 10r (which complicates matters further), and I would like to avoid installing a bootloader/root/etc. which prevents future updates/upgrades to later software versions (so other existing guides have put me off for multiple reasons).
Is what you listed all I need to do (in both cases), or do I need to root (or bootloader unlock etc.) first?
Can I install any future stock US996 ROMs (ie when Oreo is released) once I have done this, or will I have to reverse the steps and start over with h910/ATT software?
MrSalue said:
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
Click to expand...
Click to collapse
Edit: Brain explained to you rather more profoundly. I rest my case of explaining it further
dark_prince said:
Edit: Brain explained to you rather more profoundly. I rest my case of explaining it further
Click to expand...
Click to collapse
Hi.
I also have a few questions (as I'm new to this and have found conflicting information, and in addition I have two h910 phones running different firmware versions, one v10m and one v10r).
1) My phone's aren't rooted - Is what Brian explained all I need to do, or does his explanation require a bootloader-unlocked/rooted phone to work?
2) Are there any requirements/restrictions (eg. original firmware must be above/below version XYZ - if yes, does it make any sense to update the firmware to the latest AT&T version first)? Can I install any future versions of US996 KDZ that way too?
Thanks in advance.
AWT86 said:
Hi.
I also have a few questions (as I'm new to this and have found conflicting information, and in addition I have two h910 phones running different firmware versions, one v10m and one v10r).
1) My phone's aren't rooted - Is what Brian explained all I need to do, or does his explanation require a bootloader-unlocked/rooted phone to work?
2) Are there any requirements/restrictions (eg. original firmware must be above/below version XYZ - if yes, does it make any sense to update the firmware to the latest AT&T version first)? Can I install any future versions of US996 KDZ that way too?
Thanks in advance.
Click to expand...
Click to collapse
1. For 10m one, follow Brian's guide, for v10r, follow Brian's guide. Once you have unlocked bootloader/rooted, you have conceded official updates. Also there are no stock KDZ restoring methods to revert back to H910 but you can try a method to go bone-stock H910 if you're rooted and have TWRP recovery.
2. For H910? no, and no need to upgrade to latest att firmware. You can just jump the gun to US996
Edit: Make sure you take full backup dump with patched LGUP (from Brian's guide as well).
Thanks
dark_prince said:
1. For 10m one, follow Brian's guide, for v10r, follow Brian's guide. Once you have unlocked bootloader/rooted, you have conceded official updates. Also there are no stock KDZ restoring methods to revert back to H910 but you can try a method to go bone-stock H910 if you're rooted and have TWRP recovery.
2. For H910? no, and no need to upgrade to latest att firmware. You can just jump the gun to US996
Edit: Make sure you take full backup dump with patched LGUP (from Brian's guide as well).
Click to expand...
Click to collapse
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
AWT86 said:
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
Click to expand...
Click to collapse
1. Make a backup dump and flash US996 rom.
2. I havent known anyone who ran into corrupted EFS after crossflashing between H910/H915/US996. The restoring of modemst1,modemst2,modem, misc solves the problem of No baseband/IMEI. Do that at your own risk, there is no guarantee that you'll be safe from apocalypse
AWT86 said:
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
Click to expand...
Click to collapse
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
Hi.
I'm having trouble with LGUP. When I try to dump all phone files, it gives me an error 0x2000 saying "not enough hard disk space", even though there should be more than enough.
Device Manager recognizes the device under Ports as "LGE AndroidNet USB Serial Port (COM8).
Help would be highly appreciated.
Thanks in advance.
EDIT: I managed to dump the files you recommended, but what about the rest? shouldn't I back those up too?
---------- Post added at 11:51 AM ---------- Previous post was at 11:24 AM ----------
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
UPDATE: I flashed the first device, but it asked for a password that wasn't set up. UPDATE 2: solved w/ factory reset.
Thanks a lot and sorry for bothering you guys.
Glad you were able to do it.
As far as backing the other files up -- no, you can get those from a KDZ, so no reason to back them up. The partitions I had you backup are specific to your phone(s).
-- Brian
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
Now flashed both devices, but noticed that the signals are unstable. Network jumps randomly from no network to 4G and back to no network etc - not in high frequency, but often enough for me to have noticed.
Does that mean I now have to go the route of rooting or is there anything else I can try?
Thanks and sorry to bother you once more.
PS: just noticed it seems to run stable with only 3G enabled, but once 4G is enabled the problem starts.