Related
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Considering the 915 isn't even a supported device no. If someone has gotten the 915 please let me know.
Until FREEDOM Mobile allows the LG V20 LOCKED bootloader to be UNlocked, there will be no FREEDOM to have a custom ROM anytime soon
That is what I got the T-mobile version with the unlockable bootloader which works great on NON-freedom.
lumberguy1028 said:
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Click to expand...
Click to collapse
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
markbencze said:
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
Click to expand...
Click to collapse
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
lumberguy1028 said:
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
Click to expand...
Click to collapse
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
markbencze said:
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
Click to expand...
Click to collapse
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
me2151 said:
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
Click to expand...
Click to collapse
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
markbencze said:
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
Click to expand...
Click to collapse
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
me2151 said:
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
Click to expand...
Click to collapse
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
markbencze said:
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
Click to expand...
Click to collapse
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
lumberguy1028 said:
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
Click to expand...
Click to collapse
Correct but it's useless to use since the phone doesn't function properly afterwards. If there was a confirmed way to have data and signal working then that would be great but there is nothing confirmed to work yet.
I've just moved to a V20 from a Note 4. All my Note4 ROMS were T-Mobile versions. I believe Rogers/Fido phones are basically the same as T-Mobile, which uses freq. channel 66 as well.
Has anyone tried a T-Mobile (918) ROM on the 915 yet? Might just work...
no root yet for freedom????/
whats the method
whats the method to root the lg h915
diehard2013 said:
no root yet for freedom????/
Click to expand...
Click to collapse
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
GerardSamija said:
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
Click to expand...
Click to collapse
Why Wouldent you just use the secret # in the hidden menu to change bands to get signial. Also you could try searching for exsisting bands that are near by, this dont require the hidden menu.
Sent from my [device_name] using XDA-Developers Legacy app
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
GerardSamija said:
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
Click to expand...
Click to collapse
Oops my bad i was sleeping while i read that. You can fix your sim card reader just use a soder tool. Also there maybe a root for this phone but i don't think it is safe enough yet.
Sent from my [device_name] using XDA-Developers Legacy app
So pretty much what I am wanting to do is flash a custom ROM or KDZ so I can run the T-Mobile software on my V20, with the unlocked one I am missing out on Wifi Calling as well as Advanced Calling and wanted to take advantage of it. Is there anyway to be able to do this?
Sometimes you got to be the guinea pig.
sapplegater said:
So pretty much what I am wanting to do is flash a custom ROM or KDZ so I can run the T-Mobile software on my V20, with the unlocked one I am missing out on Wifi Calling as well as Advanced Calling and wanted to take advantage of it. Is there anyway to be able to do this?
Click to expand...
Click to collapse
Did you figure out if this was possible?
sapplegater said:
So pretty much what I am wanting to do is flash a custom ROM or KDZ so I can run the T-Mobile software on my V20, with the unlocked one I am missing out on Wifi Calling as well as Advanced Calling and wanted to take advantage of it. Is there anyway to be able to do this?
Click to expand...
Click to collapse
If you want to be in the same position as this guy/girl lol!
Here is one thread:
https://forum.xda-developers.com/v20/help/lg-f800l-doesnt-h918-kdz-installation-t3548272
RE: US996 to T-Mobile Version
The short answer to this question is No you CAN NOT flash the T-Mobiile KDZ or ROM to your US996 phone. Although it is possible to do this with US996 to/from H910 to/from VS995(these are just those that I have actually performed the flash successfully on), even with these you stand a good chance of breaking something, and my successful attempts were done using STOCK KDZs i.e H910 to US996 and VS995 to US996 and return(the return for the former was via H915 KDZ). The reason you cant do this with the T-Mobile KDZ in EITHER DIRECTION is BECAUSE THE SIGNING KEY on the chipset used for the T-Mobile H918 and therefore on its KDZ, is unique in the LG V20 family. LG used the same keys on most/all the other variants that I am aware of EXCEPT for the H918.
So even though you can NOT flash the H918 KDZ to any of the Non H918 LG V20s, there is a possible work around for what you are wanting to accomplish. This work around, would be to extract the System image from the H918 KDZ that matches the Android version you are running on your US996, and overwrite the System partition with this System Image file. By doing this you would be adding all the configuration files, along with any T-Mobile apps and Framework files that would be needed on your US996. I have not done this before, but I do not believe there is any reason this would not work. Your other option is to reconfigure your config files found in /system/etc/ such as the featureset.xml, among dozens of other files that would need to specify that you are running a TMO profile, and then manually move over any Framework, and APK files that would be needed. The latter option would assume you are running as root, where the former could be performed either through fastboot or using LGFlash or LGUP.
tristac-airitech said:
snip
Click to expand...
Click to collapse
dude, don't dig up old threads from 2 years ago. This is universally frowned upon in any forum.
Hello, I was searching for KDZ and was able to stumble into this model LG V20 H910PR.
Since I don't have a H910 model to test this. Anyone here who has a bricked ATT H910 that would like to test if this KDZ would work.
Link: https://lg-firmwares.com/lg-h910pr-firmwares/
Its been tested. It breaks radio
me2151 said:
Its been tested. It breaks radio
Click to expand...
Click to collapse
Can you unroot / get it back to stock though? *even if it breaks radio?*
tcanute said:
Can you unroot / get it back to stock though? *even if it breaks radio?*
Click to expand...
Click to collapse
Yes but its pointless without radio. BTW when I say radio I'm talking about cell service. You will get no service and its impossible to fix while in the stock state. That's why its pointless
me2151 said:
Its been tested. It breaks radio
Click to expand...
Click to collapse
glad to hear that. there's still hope for those who bricked their device from faulty OTA updates
Edit: aww i thought it was music radio. too bad.
h910pr
i have successfully restored to the h910pr kdz with working radio (cell signal). id love to get back to a rooted firmware but for now it was at least a viable way to debrick my phone.
HOW!
predheadtx said:
i have successfully restored to the h910pr kdz with working radio (cell signal). id love to get back to a rooted firmware but for now it was at least a viable way to debrick my phone.
Click to expand...
Click to collapse
How!? Is your phone an h910 running on at&t? Is there anything specific you did when restoring the kdz or did you follow a specific guide? What does your "About Phone" show your phone as being?
Sorry for all the questions, that's just kinda exciting to hear
tcanute said:
How!? Is your phone an h910 running on at&t? Is there anything specific you did when restoring the kdz or did you follow a specific guide? What does your "About Phone" show your phone as being?
Yes im on at&t and have had no issues with data, text, or calling. my damn watch still wont sync to my phone but that was a prior issue as well. i scoured the internet for everything i could get my hands on and what i received was a bunch of guesses mostly lol. so i modified the h918 lgup dll to allow me to flash my h910. it accepted the h910pr software without issues. other than being back on a locked boot-loader with no way out in sight. if you can deal with a rare instance of a notification being in spanish then go for it. ask and ill post my tools folder somewhere, so you can try the exact versions of lgup i used and the tweaked dll
Click to expand...
Click to collapse
predheadtx said:
Yes im on at&t and have had no issues with data, text, or calling. my damn watch still wont sync to my phone but that was a prior issue as well. i scoured the internet for everything i could get my hands on and what i received was a bunch of guesses mostly lol. so i modified the h918 lgup dll to allow me to flash my h910. it accepted the h910pr software without issues. other than being back on a locked boot-loader with no way out in sight. if you can deal with a rare instance of a notification being in spanish then go for it. ask and ill post my tools folder somewhere, so you can try the exact versions of lgup i used and the tweaked dll
Click to expand...
Click to collapse
Sure if you don't mind. That would be great.
tcanute said:
Sure if you don't mind. That would be great.
Click to expand...
Click to collapse
okay, uploading at 600kb/s :/ ill edit this post with the link when its done. just install lgup and the lg mobile drivers, then paste this lgup folder over the lgup folder in your program files. what ive done is used components from different version of lgup and renamed the h918.dll to lgcommon.dll and placed it in a common folder, then created an h910 folder as well. then put the phone in download mode and lgup will recognize it as an h910 but will allow you to flash the h910pr.kdz. it was a simple little hack together that anyone can replicate. maybe someone could write up a good tutorial on it.
@predheadtx Just curious why you didn't flash the H915 KDZ since the H910 and H915 are the same phone: https://fccid.io/document.php?id=3134555 <-- notice additional model names.
At least you can root H915...
-- Brian
This thread doesn't belong in development. Needs to be moved to general.
runningnak3d said:
@predheadtx Just curious why you didn't flash the H915 KDZ since the H910 and H915 are the same phone: https://fccid.io/document.php?id=3134555 <-- notice additional model names.
At least you can root H915...
-- Brian
Click to expand...
Click to collapse
hmm hadn't realized the h910/918/915 were all the same. i only knew about the 918 being the same. does it use the same mobile bands as att? i guess ill give it a try.
With the stock firmware installed, they must use the same frequencies, or the FCC would have to test them separately.
As far as I know the H915 (In addition to being the Canadian model) is also the AT&T Go Phone. So it is to AT&T was the MSXXX (for example MS631 (Metro) and H631 (identical phone with T-Mobile firmware) are to MetroPCS / T-Mobile.
When I had MetroPCS, I would flash T-Mobile firmware because they usually got the updates quicker than Metro did.
In this case it looks like LG made generic GSM/LTE model for the H910/H915/H918. What is funny is that their carrier free phone US996 is different.
This weekend I plan on flashing H918 since I use T-Mobile, and then I can root without having this effed up bootloader.
On a different note, I 100% agree with @12MaNy that this thread does not belong here.
runningnak3d said:
With the stock firmware installed, they must use the same frequencies, or the FCC would have to test them separately.
As far as I know the H915 (In addition to being the Canadian model) is also the AT&T Go Phone. So it is to AT&T was the MSXXX (for example MS631 (Metro) and H631 (identical phone with T-Mobile firmware) are to MetroPCS / T-Mobile.
When I had MetroPCS, I would flash T-Mobile firmware because they usually got the updates quicker than Metro did.
In this case it looks like LG made generic GSM/LTE model for the H910/H915/H918. What is funny is that their carrier free phone US996 is different.
This weekend I plan on flashing H918 since I use T-Mobile, and then I can root without having this effed up bootloader.
On a different note, I 100% agree with @12MaNy that this thread does not belong here.
Click to expand...
Click to collapse
im attempting to flash the 915 .kdz right now, im looking for a workaround to lgup telling me the model numbers are mismatched. ill make attempts with the 918 firmware as well.
predheadtx said:
im attempting to flash the 915 .kdz right now, im looking for a workaround to lgup telling me the model numbers are mismatched. ill make attempts with the 918 firmware as well.
Click to expand...
Click to collapse
to anyone concerned here is the files i promise. ive hat not luck with the 915 or 918 firmware from the 910pr, maybe im missing something but nothing i do works.
https://mega.nz/#!YLxDlDBA!4SNhULZB-5rWCIUk6EJK0GB9Yul3uxGx3d_vSa4TnI8
Have you tried: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
I have not found a phone yet that can't be spoofed with it...
honestly now that ive seen that post, i had mistakenly thought the version of lgup i was using had been patched WITH LGuppercut. thank you for correcting me!
have been messing with uppercut. not finding any way to "spoof" anything.
edited again- luckily i had already gotten att to warranty the phone for a defect it had, but trying to flash h915 using the port 41 trick has officially bricked my phone. IT does absolutely nothing now. when plugged in to a computer windows recognizes as a qualcom usb qloader but the phone does nothing else.
Spoof was probably the wrong word to use. I mean that I have never had an LG phone that LGUP alone would not recognize, but when launched with Uppercut also would not be recognized.
You may have a corrupt misc partition. I have had to wipe the misc and the fota partitions several times due to bad flashes:
If using a confirmed working device with UPPERCUT but your device is still not detected in LGUP you may have a "corrupted" misc partition...
as a last resort it has been confirmed in post #70 that wiping misc then booting into download mode allows the device to be detected with UPPERCUT + LGUP 1.14. This may not always work. And without root you cannot do this.
Click to expand...
Click to collapse
Since that requires root, you may be in a pickle.
runningnak3d said:
Spoof was probably the wrong word to use. I mean that I have never had an LG phone that LGUP alone would not recognize, but when launched with Uppercut also would not be recognized.
You may have a corrupt misc partition. I have had to wipe the misc and the fota partitions several times due to bad flashes:
Since that requires root, you may be in a pickle.
Click to expand...
Click to collapse
having lgup recognizing the device has never been the issue. its cross flashing firmware's that it refuses to do.
If you have a v20 that has ARB 0, and are on a security patch greater than Dec 2016, I can help you root it if you want. The model doesn't matter, but it must be on ARB 0
To find your ARB, on the keypad dial: *#LGMENU#*model#
So for example, a H990: *#LGMENU#*990#
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.
Also, please include your model and current firmware version.
If you are ARB 0, and you have a KDZ for your model:
US996 (unlocked or US Cellular) KDZ
VS995 KDZ
H915 KDZ
H918 KDZ
H990(DS / N / T) KDZ
F800 (S / K / L) KDZ
Grab the patched LG UP, and before starting use the DUMP option to dump your current firmware (select ALL partitions). You will need it if there wasn't an exact KDZ for your phone. Not to mention that it makes it real easy to get back to the firmware you are on.
Download the KDZ for your model, flash it with LG UP (use partition DL mode), and then you can then root with dirtycow -- use the method that is specific for your model.
That leaves:
H910 - I already made a post for this model here.
LS997 - The post for the LS997 (up to and including ZV7, but NOT ZV8 or above) is here.
If you don't know what you are doing, send me a PM *BEFORE* you start. For example, the H990 can use the firmware from the other models, but everything may not work until you get the proper firmware back onto the phone.
If you have an H918 and are on 10p or later (ARB 1+), then you can use lafsploit 1.0
-- Brian
ARB 0
runningnak3d said:
The model doesn't matter, but it must be on ARB 0
-- Brian
Click to expand...
Click to collapse
I have ARB 0, how can I do this?
What do you think about a US Cellular V20? April 2017 security patch, software US99610h, build NRD90M.
Trying to figure out if it is still possible to root this thing, and what the optimal way is. Thanks for any help!
I have arb 2 on zv9 on my second ls997
ABR 1
@JerichoAbles You have to be willing to factory reset your phone. Unfortunately we need some files off of it before it ever boots. I will update the first post with that bit of info. If you are OK with that, I will post the full details when I am back at a PC. @TFKt44 The version, and security patch don't matter. The ARB version does. I don't know what ARB version us996 10h is. You will have to look.
For you folks on ARB 1 or 2, sorry, your carrier effed you good.
It will be possible to root ARB > 0 ... but that will take some time.
runningnak3d said:
@JerichoAbles You have to be willing to factory reset your phone. Unfortunately we need some files off of it before it ever boots. I will update the first post with that bit of info. If you are OK with that, I will post the full details when I am back at a PC. @TFKt44 The version, and security patch don't matter. The ARB version does. I don't know what ARB version us996 10h is. You will have to look.
For you folks on ARB 1 or 2, sorry, your carrier effed you good.
It will be possible to root ARB > 0 ... but that will take some time.
Click to expand...
Click to collapse
Yeah, I am abr01
Sent from my LG V20 using XDA Labs
runningnak3d said:
@JerichoAbles You have to be willing to factory reset your phone. Unfortunately we need some files off of it before it ever boots. I will update the first post with that bit of info. If you are OK with that, I will post the full details when I am back at a PC. @TFKt44 The version, and security patch don't matter. The ARB version does. I don't know what ARB version us996 10h is. You will have to look.
For you folks on ARB 1 or 2, sorry, your carrier effed you good.
It will be possible to root ARB > 0 ... but that will take some time.
Click to expand...
Click to collapse
My ARB is 0. Should've put that in my initial post.
@TKFT44 Yours is easy. There are two models of US996, the unlocked, and the US Cellular. You can flash either, but your phone may not be able to make calls if you flash the wrong one. Lucky for you, there are KDZs for both, so fixing your phone after it is rooted is a no brainer. Flash this. It is a KDZ for the unlocked US996 version that is still rootable. After you get your phone rooted, you can switch back to the 10h firmware manually, so that you keep root -- and then your modem will work. If you need step by step instructions, send me a PM.
Actually, I am pulling both down just to make sure that LG didn't use a different RSA key. That would brick your phone. I will send you a PM and let you know if it is safe.
As for everyone else. Please include:
Model
ARB version (even if it is > 0)
Current firmware version
I may not be able to help you right now, but if I don't have all of that info, I can't even try.
runningnak3d said:
Actually, I am pulling both down just to make sure that LG didn't use a different RSA key. That would brick your phone. I will send you a PM and let you know if it is safe.
Click to expand...
Click to collapse
I previously flashed an unlocked 996 on my usc v20 and it worked fine it was just a little wonky but it was safe
okay I tried flashing with DirtyElf but when I get to the factory reset part it still gives me the triangle and no boot how can I reflash
Mine is:
H990ds
ARB Version 0
Software Version H990ds10g-IDN-XX
I don't even get a menu to pop up or anything.
@JerichoAbles You flashed the 10f KDZ and then followed DirtyElf?
@myisn Yours is easy as well, you have a KDZ: link. Flash it, and then root with the standard H990DS root procedure. Then if you want to upgrade to the latest firmware, you can do it manually and keep root. Again, I will be glad to help with that part.
Help rooting
I have an unlocked US996 (non US Cellular) V20 with the December 2016 patch (no surprise there). I understand the device is rootable and that I can get more recent patches by rooting it, but even reading up on the subject I don't feel confident that I have the knowledge and background to do so.
For instance are we talking about entering *#LGMENU#*996# on the dialer keypad?
---------- Post added at 04:03 PM ---------- Previous post was at 03:56 PM ----------
I might add that I can't enter alphabetical characters on the dialer keypad.
SFrsfair said:
I have an unlocked US996 (non US Cellular) V20 with the December 2016 patch (no surprise there). I understand the device is rootable and that I can get more recent patches by rooting it, but even reading up on the subject I don't feel confident that I have the knowledge and background to do so.
For instance are we talking about entering *#LGMENU#*996# on the dialer keypad?
---------- Post added at 04:03 PM ---------- Previous post was at 03:56 PM ----------
I might add that I can't enter alphabetical characters on the dialer keypad.
Click to expand...
Click to collapse
that's not how it works, you type the numbers that correspond with the alphabetical letters, Also, you can just unlock your bootloader at developer.lge.com
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
runningnak3d said:
@JerichoAbles You flashed the 10f KDZ and then followed DirtyElf?
Click to expand...
Click to collapse
Yes, but after the fastboot part I never took the battery out so I think the permissions disappeared but I can't reflash I don't know how please help
What happens when you try to enter download mode?
runningnak3d said:
What happens when you try to enter download mode?
Click to expand...
Click to collapse
Well originally it wouldn't work but it's become apparent to me that it was because my phone did not have enough charge because the corrupt triangle and charging from my computer would not work but I'll try again and get back to you
Yea, you have to make sure your phone is charged good, it disables charging when certain events are triggered, and I don't have a full list of them, so when you are flashing always make sure you have a full charge. If your phone dies part way through flashing part of the boot loader .... there is no fixing that right now. Luckily your phone is responding, so you should be OK.
Okay so I did everything right this time, but now it's not sending me to twrp, it's just booting like normal
I'm expecting delivery of 2 V20s in the next couple of days. These are "refurbs" of the VS995 variety. These are advertised from the seller as "unlocked." I will be using these on Verizon (or MVNO).
I did some basic research before I bought and I was pretty sure I saw info on rooting this model and the ability to do custom ROMS on an unlocked, but I am a little concerned.
I have 3 main questions:
1) I see there is both a VS995 and a US996. I'm having a hard time finding info on the differences spelled out exactly - but it appears that the VS995 is locked to verizon and US996 is unlocked for all GSM. Is this correct? If so, wouldn't an "unlocked" VS995 be equivalent to a US996? If not, what would be different.
2) I want to do a comprehensive check on these phones before I start tinkering to make sure everything works. My last HTC phone had a hidden diagnostics menu which would test everything (battery, compass, gps, sensors, buttons, etc, etc...). I would like to know if the V20 has something similar? Also I want to know what the "problem areas" of V20s are. Things I should check out to make sure they aren't wonky.
3) I need to know if I can root this phone. I've seen a couple methods but I'm not sure now if they apply to my model and if they still work and/or if they are safe (relatively speaking). I definitely need root and would also like to load custom recovery so I can do alternate ROMS, thought I probably will run with stock for a while to get used to it. I would like to upgrade to latest official ROM (for the newest features), but don't want to do any upgrades if it will ruin my chances to root/unlock/etc. What do I need to check on the phone and what is the method I should follow (links are fine for this).
I recently bought a refurb VS995 because I like my original VS995 so much and I am thinking that shortly after the Oreo upgrade comes out, any refurb might come with Oreo and may or may not be easily rootable. (and it is looking very unlikely any phone in the future will come with replaceable batteries) That said, mine came with 15A and I was easily able to roll back to 12A with the 'hacked' LGUP tool and then root it and flash the at-the-time current AlphaRom (now discontinued) without issue. AFAIK *all* current VS995 ROMs can be rolled back to 12A (rootable), up to the latest 1BA. This may or may not change soon (some versions of the V20 CANNOT be rolled back after they take specific updates) The SuperV20 ROM is running the almost up to date version 1AA (with hints of an update coming soon) so you'd be up to date with a close to stock ROM. I will say the rooting process on the V20 is a bit more convoluted than most other phones, which leads to the issue that the rooting threads are nearly incomprehensible anymore-- too many people not following directions, not reading, and complaining about tons of "normal" issues-- static screen (normal after rooting with stock kernel, once the phone boots up fully cover the proximity sensor until the 2nd screen blanks out and then the static will go away-- replace the stock kernel with the mk2000 kernel to fix), phone vibrates on boot after charging (no fix, but will stop the first time it's made to vibrate after booting). I would stay stick to the original rooting thread and READ CAREFULLY. I had issues trying to follow some of the "updated"/new threads where I had issues trying to get the phone to boot properly.
That said, if you do hit a roadblock, DON'T PANIC. The V20 is more resilient than you might think and you can almost always get it back from soft bricking with the LGUP tool (I had to reflash mine 2 or 3 times before I finally got root to stick with the ORIGINAL DirtySanta thread). Basically, the process is flash it back to 12A, use DirtySanta, **boot it once or twice after getting root via DS** (first reboo.t may take a while, with a static screen and vibrating phone, let it sit 10-15 minutes before panicking as it's rebuilding the app cache), then get into TWRP, do a factory reset, flash the new ROM and BTTF kernel, then it should work.
The VS995 has a more limited LTE band selection than the US996. While it can sort of work with other carriers (you'll have to search for instructions/compatibility), the US996 will provide a better experience.
Keep in mind, each version of the phone is SLIGHTLY different, so MAKE SURE you're always using VS995 builds of ROMs/kernerls/recoveries. Apparently you can use US996 ROMs as well but I've never bothered. (you gain a few things, you lose a few things [like wifi calling I think], do your research) Trying to use anything other than VS995 or US996 roms is asking for trouble/limited functionality/soft bricking.
I haven't really used my refurb all that much but it seems mostly fine. The only glitch I see is that the battery seems to drain faster than my original V20 but that might have more to do with the battery condition-- I need to get around to swapping batteries between the phones to see what happens. Given everything else is fine I am very hesitant to return it under warranty. I don't know if there is a way to run a self-test, I would hope there is..!
Good luck, the phone is amazing once you get it tamed...
Links:
Downgrade: the VS995 "all in one" thread has a good video for this. That said I think I had to piece together a working LGUP from a few threads since you need a tweaked DLL file. https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326 (when I tried to follow the root directions in that link I had issues and had to re-flash 12A and start over, YMMV)
DirtySanta: https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Once you get a working TWRP from DirtySanta, update it to this one: https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
SuperV20 ROM: https://forum.xda-developers.com/v20/development/rom-superv20-h918-t3764390
mk2000 kernel (I'd use the "back to the future" version of the kernel to start): https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Buzzy42 said:
Good luck, the phone is amazing once you get it tamed...
[/url]
Click to expand...
Click to collapse
thanks.
Been doing research for the past hour or two and am getting a little bit of a better handle. I've seen the downgrade tutorial and looks solid.
I'm not worried about "convoluted" and the phone seems pretty brick proof so I'm good there.
Just to confirm - if I want root I need to go no later than 13A firmware? My understanding is "firmware" in context of this phone is ROM+Kernel rolled into one.
So if I want root, I can't be on the latest stock ROM (18A), right? Looks like features are all the same - although I do like having the latest security updates, but I guess I will need to forgo those for root?
One other thing I'm looking at is that I prefer to root with Magisk. I've seen a couple threads dealing with this and they recommend to use the "reStock" kernel. My understanding is that you would flash the "reStock" after reverting to the 13A firmware. What I'm trying to understand is if the kernel can be separated from the ROM, could one not flash 18A and then the reStock kernel (which is based on 10b)?
Also, still really interested in the answer to my 2nd question in OP regarding accessing diagnostics for the phone and any problem hardware/screen/etc issues to look out for before I accept this "refurb" as golden.
Yeah, the phone is mostly brickproof and most issues you run into can be solved. If all else fails, just re-roll it back to 12Ain download mode (pull battery, hold down volume, plug in USB cord which will make the phone boot into download mode) and start over. I've seen very little signs of anyone TRULY bricking a V20 who wasn't really trying. (I.e., doing major hacking on it or totally throwing caution to the wind and flashing something they shouldn't have flashed)
You have to downgrade to 12A or 13A to root the phone and get TWRP properly installed the first time, but then you can flash any ROM/recovery you want, so you don't need to worry as much about security patches (just find a ROM that's as up to date as possible). There was AlphaRom up to 1AA which works great (and what both of my V20s are on), Super V20 is being updated but apparently has known issues on the VS995 that the developer has issued a patch for... you might want to skim the various ROM threads to know what works for you. My V20s are both using Magisk.
You can flash kernels and ROMs separately. Some ROMs have a kernel baked in-- I usually boot them once or twice and then re-flash the kernel if I want to. Some ROMs need a kernel flashed separately during the install process. So yeah, you could install an 18A based ROM and then the reStock kernel. (some ROM/kernel combinations work better than others, but you'll have to figure out what you want as some kernels do more than others-- specifically look for KCAL color adjustments, as you can slightly tweak the colors on the screen to help with the screen retention issue the phone has)
The kernel versions and ROM versions are different. I don't fully understand it myself either but AFAIK kernels based on 10b are the latest for the VS995. ROMs based on 1BA would be the latest (they're using hex numbers, so releases go 11A, 12A, 13A.... up to 1AA, 1BA). Some variations of the V20 seem to have more versions of the kernels than the 995 does.
Buzzy42 said:
...
You have to downgrade to 12A or 13A to root the phone and get TWRP properly installed the first time, but then you can flash any ROM/recovery you want, so you don't need to worry as much about security patches (just find a ROM that's as up to date as possible). There was AlphaRom up to 1AA which works great (and what both of my V20s are on), Super V20 is being updated but apparently has known issues on the VS995 that the developer has issued a patch for... you might want to skim the various ROM threads to know what works for you. My V20s are both using Magisk....
Click to expand...
Click to collapse
Thanks. I'm wanting to run stock for a while (with Root though) so I can get a feel for how everything is "supposed" to work.
I'm not sure if I will find benefit in the "Second screen", but if I do I would like to find a ROM that supports it.
I've been running latest LineageOS on my HTC M8 for a while now and wouldn't mind sticking with it. However I would like to find some ROMS that are still being actively developed. Honestly I plan to have this phone for at least 2 years so the most up to date stuff I can find now will hopefully future proof me a little from that angle.
TraderJack said:
Thanks. I'm wanting to run stock for a while (with Root though) so I can get a feel for how everything is "supposed" to work.
I'm not sure if I will find benefit in the "Second screen", but if I do I would like to find a ROM that supports it.
I've been running latest LineageOS on my HTC M8 for a while now and wouldn't mind sticking with it. However I would like to find some ROMS that are still being actively developed. Honestly I plan to have this phone for at least 2 years so the most up to date stuff I can find now will hopefully future proof me a little from that angle.
Click to expand...
Click to collapse
Yeah, totally understand not wanting to jump in to custom ROMs right away, especially if you're testing a refurbed phone. Flashable truly stock ROMs have been a weakness of the V20, but I think a version of 17A was floating around if you want something a bit newer than the 12A/13A that are rootable. Someone else might be able to help with that. Sadly there isn't a lot of development-- there have been big bursts of activity, then a lot of silence-- which mostly mirrors LG's seeming abandonment of the phone. You should still be able to flash other kernels (restock, mk2000, etc) over whichever rom you run, though. Be careful not to take any official OTA updates because the rooting process installs a debug-bootloader (someone got a hold of an engineering sample of the phone and dumped that phone's bootloader which is what allowed us all to get rooted with an unlocked bootloader) that gets wiped out and leaves the phone in a weird state.
The second screen is really useful once you look at it as a very powerful LED notification light. It takes a while to get used to but I don't know if would want to use a phone without it (or some sort of always-on feature) now. Unfortunately the Lineage ROMs lose a lot of the cooler functionality of this phone due to it having some many weird non-standard functions, but for some people that's not as big of a deal as staying current, so it's whatever your priority is. I am really hoping once the phone gets Oreo (which seems to be "real soon now"..) that we'll still be able to upgrade to it and use that as a base for a while, but keep root/etc..
Buzzy42 said:
...My V20s are both using Magisk....
Click to expand...
Click to collapse
Is there a special process to use Magisk instead of SuperSU? My search found some convoluted answers which "required" the reStock kernel to get it working.
I don't know if Magisk has been updated to make it easier...but is there any instructions/link you can forward on how to get rooted with Magisk after I do the 13A downgrade?
Also, it would appear that everything up to 1BA does *not* have anti rollback enabled (ARB=0). Is this correct?
I was told on reddit that you can only root firmware where ARB=0, but clearly this is not the case if you can't root anything past 13A.
Do you have any idea what specifically is the block as to why we can't root past 13A?
thanks
TraderJack said:
Is there a special process to use Magisk instead of SuperSU? My search found some convoluted answers which "required" the reStock kernel to get it working.
I don't know if Magisk has been updated to make it easier...but is there any instructions/link you can forward on how to get rooted with Magisk after I do the 13A downgrade?
Also, it would appear that everything up to 1BA does *not* have anti rollback enabled (ARB=0). Is this correct?
I was told on reddit that you can only root firmware where ARB=0, but clearly this is not the case if you can't root anything past 13A.
Do you have any idea what specifically is the block as to why we can't root past 13A?
thanks
Click to expand...
Click to collapse
I'm trying to remember what I did for Magisk. There wasn't anything particularly special. That said, I switched to Magisk when I re-flashed the phone (so I flashed the rom/kernel/Magisk together, in that order I think), I didn't try to just swap between SuperSU and Magisk on a running ROM. Once you get TWRP going you *should* be ok to just remove SuperSU and then reboot into TWRP and flash Magisk. I am on the mk2000 kernel with Magisk so you definitely don't need to be on Restock.
I am not sure if it is possible to do the rooting process without SuperSu and using Magisk instead, if that's what you're asking. I think it'd be safest to use SuperSu and then switch it out later once you're sure you're rooted in the first place.
As for the rollback, there are a few different issues here.
12A/13A have the Android vulnerability which allows DirtySanta to work to root the phone. This was patched after 13A, so DirtySanta can't run and you can't root the phone on a later version of the firmware. If you run anything later than 13A you can't start the rooting process (but you can upgrade your rooted phone past 13A using TWRP to flash an appropriate ROM, but not through the OTA process)
ARB (anti-rollback) prevents you from rolling back to a previous version of the firmware. It has nothing to do with rootable/non-rootable. But it prevents the phone from going back to a rootable firmware on SOME V20s. So far, no firmware on the VS995 has enabled this, so you are safe rolling back to 12A and trying to root with any firmware currently available up to 1BA (definitely 1AA but I have read a few comments that 1BA is still safe). On SOME other models of the V20, ARB *has* been set, which prevents you from rolling back to a previous version of the firmware with ARB=0 (if you try to roll back on a phone with ARB=1 you get an unrecoverable brick.)
So if tomorrow Verizon released a hypothetical update with ARB=1 and you updated, you could no longer roll back to 12A or 13A to root your phone, and you'd be stuck without root unless someone developed a new workaround.
Does that make more sense? Keep in mind that with all of the different versions of the V20, what is appropriate (or even relevant) for one model may not apply at all to another. Thankfully the VS995 still is pretty hackable at this moment. This could all change at any time.
Buzzy42 said:
...12A/13A have the Android vulnerability which allows DirtySanta to work to root the phone. This was patched after 13A, so DirtySanta can't run and you can't root the phone on a later version of the firmware. If you run anything later than 13A you can't start the rooting process (but you can upgrade your rooted phone past 13A using TWRP to flash an appropriate ROM, but not through the OTA process)...
Click to expand...
Click to collapse
Hold on.. So are you saying I can flash 13A, then root with Magisk, then upgrade the ROM itself to 18B to get all the latest patches?
If so, I haven't seen any instructions yet for doing that method, but that would be ideal for me for starters until I want to mess around with custom ROMS and Kernels.
TraderJack said:
Hold on.. So are you saying I can flash 13A, then root with Magisk, then upgrade the ROM itself to 18B to get all the latest patches?
If so, I haven't seen any instructions yet for doing that method, but that would be ideal for me for starters until I want to mess around with custom ROMS and Kernels.
Click to expand...
Click to collapse
Not quite that simple-- you have to downgrade to 13A if you're not already there when you get the phone.
When you run the DirtySanta rooting process, when it's done, you will end up with a rooted 13A with TWRP and SuperSu. I believe it will have the debug kernel which has a lot of issues, but you can flash any kernel you want at this point (like ReStock to get rid of the static screen you'll see at every boot). That way you'll have a 99% stock (except the ReStock kernel tweaks), rooted, 13A phone.
You can now flash any ROM you want in TWRP. If you want to stay truly stock, I'm not sure what is out there that is flashable, beyond I vaguely remember there was a 17A flashable. You do need to use a repackaged update in TWRP no matter what you want to update to, if you try to just take whatever OTA update the phone offers you (the "software update available" notification pops up and asks you to install while you're using it), you'll lose root and have to do everything over again. This is where you will most likely not be able to get to a truly stock 1BA unless it's floating around.
If I were you, I'd roll it back to 13A, get it rooted (with Supersu), flash the Restock kernel, disable updates (use Titanium Backup to freeze "FOTA Update 7.0") and stay there for a while for testing. If you want to try to switch to Magisk, remove SuperSu and flash Magisk through TWRP. The phone's functionality hasn't changed much/at all. When you're more comfortable, move forward to a ROM based on 1BA.
When you flash a new ROM most will include a kernel or ask you to flash a kernel along with it.
Basically, any updating you do has to go through TWRP. After you get root initially, though, it's really straightforward.
TraderJack said:
I'm expecting delivery of 2 V20s in the next couple of days. These are "refurbs" of the VS995 variety. These are advertised from the seller as "unlocked." I will be using these on Verizon (or MVNO).
I did some basic research before I bought and I was pretty sure I saw info on rooting this model and the ability to do custom ROMS on an unlocked, but I am a little concerned.
I have 3 main questions:
1) I see there is both a VS995 and a US996. I'm having a hard time finding info on the differences spelled out exactly - but it appears that the VS995 is locked to verizon and US996 is unlocked for all GSM. Is this correct? If so, wouldn't an "unlocked" VS995 be equivalent to a US996? If not, what would be different.
2) I want to do a comprehensive check on these phones before I start tinkering to make sure everything works. My last HTC phone had a hidden diagnostics menu which would test everything (battery, compass, gps, sensors, buttons, etc, etc...). I would like to know if the V20 has something similar? Also I want to know what the "problem areas" of V20s are. Things I should check out to make sure they aren't wonky.
3) I need to know if I can root this phone. I've seen a couple methods but I'm not sure now if they apply to my model and if they still work and/or if they are safe (relatively speaking). I definitely need root and would also like to load custom recovery so I can do alternate ROMS, thought I probably will run with stock for a while to get used to it. I would like to upgrade to latest official ROM (for the newest features), but don't want to do any upgrades if it will ruin my chances to root/unlock/etc. What do I need to check on the phone and what is the method I should follow (links are fine for this).
Click to expand...
Click to collapse
I found your thread her and on Reddit and was hoping you have found an answer to the hardware check feature you were looking for. I am having radio off issues with my V20 and was hoping to have the phone run a hardware check. It seems that someone posted the code "##22378" to do this but this does nothing for my older sprint v20 and my Verizon model has the MOBO back in a bag of rice. Is this only code?
redsphinx said:
I found your thread her and on Reddit and was hoping you have found an answer to the hardware check feature you were looking for. I am having radio off issues with my V20 and was hoping to have the phone run a hardware check. It seems that someone posted the code "##22378" to do this but this does nothing for my older sprint v20 and my Verizon model has the MOBO back in a bag of rice. Is this only code?
Click to expand...
Click to collapse
I had a Verizon V20 (VS995) and these are all the codes I found (from my notes):
Hardware Diagnostics
To run in-built hardware diagnostics use the following phone code:
##228378
Select Device Test > SAAT
Other Diagnostic Menus
##DEBUG
##PROGRAM
##PROGRAM995
##FEATURE
** Service codes for all above should be "000000" **
Click to expand...
Click to collapse
I'm pretty sure the ##228378 code was the one that brought up a pretty comprehensive hardware test menu. But, as you know each vendor does their own and this very possibly doesn't work on non-Verizon models. Sorry that's all I got!