So anyone who's rooted knows that the device will take longer to boot than normal. This seems to be largely down the unsecured boot warning screen. I've timed mine to be 30 seconds and I'm just wondering if there's a possibility of fixing this. My LG G5 shows the same screen just for at most 5 seconds.
Firstly would anyone know why this is. It would seem nothing is going on in the background rather there seems to be a timeout function keeping it alive for so long. Does everyone's last 30 seconds and if so is it also the case for the US996 usa version which has an official bootloader unlock method? I'm hoping the official doesn't last as long as it might indicate a workaround is possible.
Any info of your personal experience of this I'd appreciate.
I don't know the exact reason for the delay, so hopefully someone else can weigh in. So far, no one has been able to bypass it; you can only replace the warning image with something else while you wait.
From my observations (I have LS997, US996 USA, and H918 variants), the red triangle warning delay from all the models going through the Dirty Santa procedure is a bit longer, maybe twice as long as the yellow-orange triangle one seen on the US996 USA and H918.
C D said:
I don't know the exact reason for the delay, so hopefully someone else can weigh in. So far, no one has been able to bypass it; you can only replace the warning image with something else while you wait.
From my observations (I have LS997, US996 USA, and H918 variants), the red triangle warning delay from all the models going through the Dirty Santa procedure is a bit longer, maybe twice as long as the yellow-orange triangle one seen on the US996 USA and H918.
Click to expand...
Click to collapse
Been thinking about this again. I'm wondering If I took the aboot.img from an official us996_usa that has been officially unlocked and flashed it on dirty santa device would this make any difference to boot up time? I'm willing to be the guinea pig! It seems to me the hardware is exactly the same anyway and If anything goes wrong I could always restore with lgup patched.
I'm wondering if anyone would be so kind as to dump official unlocked aboot.img and pass it on to me. Preferably the us996 rather than the H918.
There is an app to do this. https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en-GB that I've just tested. Select img format rather than the default zipped option.
If anyone could help with this I'd greatly appreciate it. I'm obvious just experimenting here I've no idea if if aboot has anything to do it with. Maybe if it does I'd need to apply unlock.bin too. Or maybe other partitions are involved I don't know. But I like to experiment.
ezzony said:
Been thinking about this again. I'm wondering If I took the aboot.img from an official us996_usa that has been officially unlocked and flashed it on dirty santa device would this make any difference to boot up time? I'm willing to be the guinea pig! It seems to me the hardware is exactly the same anyway and If anything goes wrong I could always restore with lgup patched.
I'm wondering if anyone would be so kind as to dump official unlocked aboot.img and pass it on to me. Preferably the us996 rather than the H918.
There is an app to do this. https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en-GB that I've just tested. Select img format rather than the default zipped option.
If anyone could help with this I'd greatly appreciate it. I'm obvious just experimenting here I've no idea if if aboot has anything to do it with. Maybe if it does I'd need to apply unlock.bin too. Or maybe other partitions are involved I don't know. But I like to experiment.
Click to expand...
Click to collapse
Interesting idea. Sure, I'll have a look at my US996 later when I get home.
Update: I've attached it from my US996 USA. Hopefully, I did this correctly as I know nothing about this kind of stuff.
Related
Hey guys just picked up this phone after it looked like it had root and a unlockable bootloader.
However it seems that we are in the same boat as the tmo g5 unlockable bootloader, but no fastboot/ boot/flash commands seem to work.
(just tried to flash the 428 metro twrp to try to get supersu.)
how it was fixed on the g5 was flashing a custom tot with LGUP the had twrp built into it.
waited three months on that phone for root. I really don't wanna have to fall back to it. as it has pretty bad image burn from my trying to flash a deodexed rom. Long story. I'm willing to try to help anyway I can. At this point I don't care if it gets bricked. phone is useless to me with only 8 gigs of storage. if anyone could get a tot or possibly kdz file. maybe @tungkick could help us out like with the g5?
Unless anyone else has any ideas. I'll continue to help but I'll prob try to pull $275 outta thin air and upgrade to the v10 next friday.
So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
TheDantee said:
So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
Click to expand...
Click to collapse
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
Already picked up another just forgot to update this post thanks for the help though
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
Sorry, I should have clarified my friend. I have a VS995. Deleted everything without making a backup so now I am running US996 stock deodex rom with konverged kernel.
However if your stuck in a twrp loop, the instructions in the quote is what I'd try first as I seemingly exhausted everything else to no avail. And it turned out to be the easiest of the solutions and the only one that worked haha.
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
TheDantee said:
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
Click to expand...
Click to collapse
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
SHABBA JOTS said:
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
Click to expand...
Click to collapse
Could you not just reflash a H915 modem from a backup?
TheDantee said:
Could you not just reflash a H915 modem from a backup?
Click to expand...
Click to collapse
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
AllGamer said:
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
Click to expand...
Click to collapse
LOL yeah i came from a Note 7 to a G5 to the V20 so idk much about LG Phones yet...
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
SHABBA JOTS said:
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
I took many steps and got a Working TWRP Recovery and had a bootloader however when i went to flash in the ROM and then reset the phone it failed and I got stuck and had to get the model replaced... However I do know for sure that you can get TWRP and a bootloader working on the H915 using the DirtySanta Method from there is the hard part if your willing to take those steps lol.... MAKE BACKUPS! I have not tried to root my New V20 yet... If I get around to it I will be sure to let you know, some people have confirmed it has rooted but you do need the modem all high risk for the reward lol
Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach
juicemane141997 said:
Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach
Click to expand...
Click to collapse
Unfortunately there is no current fix for this. I am not sure what exactly is needed for this to be fixed, but I would assume that those people who are developing roms for the V20 have already exhausted what ever options there are.
Would be nice to have fixed, but since that screen is only during initial boot up I don't think anyone is terribly concerned with getting this corrected.
Hope this helps.
No fix
It is related to google
Not lg
I would imagine the reason for this is both for security and to let manufacturers know when a phone has been modified.
I don't believe there is a workaround for it either because it can't be done (doubtful as I am sure its software based) or people just don't care (honestly I am sure some developers were annoyed enough to look into it). I just don't think anyone has found a way around it.
This "feature" was introduced in marshmallow.
Edit: further research shows the Nexus 5x developers were able to work around it by replacing the image. So while it doesn't remove the function it hides it.
https://forum.xda-developers.com/nexus-5x/help/to-remove-corruption-warning-message-t3248441
Please note this is a marshmallow phone not nougat so I am not sure the same concept would work on our phone.
Sent from my LG-H918 using XDA-Developers Legacy app
That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk
Dark Jedi said:
That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.
androiddiego said:
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.
Click to expand...
Click to collapse
I can confirm it is located in aboot itself.
Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?
ssgsunny said:
Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?
Click to expand...
Click to collapse
We need a link to actually see the file.
me2151 said:
We need a link to actually see the file.
Click to expand...
Click to collapse
https://lg-firmwares.com/lg-h910pr-firmwares/#more-4385
What is it for?
Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.
This is a nice way to brick.
Cross-flashing radios, and/or bootloaders = GG
me2151 said:
Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.
Click to expand...
Click to collapse
I tried it and now I am on a island by myself. I got service, made a phone call and got text. It run through about every service possible and then dropped them all!!! It was such a kick in the ballz. Come swim with me the water great!
h910pr
i can confirm i have flashed the h910pr rom to my att h910 and it worked fine for me. stuck on the claro software but its actually better than atts lol. maybe someone could work on this firmware version since we have a kdz of it.
@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?
Not sure.
runningnak3d said:
@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?
Click to expand...
Click to collapse
I was originally on the h910 att firmware, then used dirty santa to open the bootloader and root. I found a rom that i really like and ran fast as heck, but it wouldn't sync with my watch. I tried a factory reset with led me to a twrp boot loop and nothing i did would get me out of it. so i tried to reflash twrp and it led me to a bricked phone that wouldn't power on past the boot loader unlocked notification. After tons of research and a little tweaking to a few things i got lgup to recognize my phone and flash the h910pr kdz to my phone. if anyone needs i can make a zip of the tools i used and post it somewhere.
edit- uploading to mega right now. will post a link in a little bit to a zip with my lgup folder configured exactly as it needed. install lgup2016 and the lg drivers then copy the lgup from this zip over the lgup folder in your programfiles(x86). essentially all you really need here is the lgup_common.dll which is actually just the h918.dll with the name changed. i had read the fccid's on the h910,h910pr and the h918 were the same, which meant by a measurable standard they are the same hardware. so i took the assumption the dlls would be compatable. by pure blind luck with the folder layout as shown in the zip and the kdz included as well it took. i was a little worried because i had read someone tried this and could not get carrier service. i thought id at least make the phone usable in case a fix was found.my phone reports itself as an h910pr now but is connected to the att network with no issues, text, talk and web all work fine as well as att services.
I had checked a while back and saw that the h910 and h918 had the same FCC ID, which, as you stated, means they have to be the same hardware. I am using my h910 on T-Mobile, so now that I know (if it fails for some reason) that I can flash the h910pr KDZ, I am going to try the h918.
Sorry that you almost had a brick, but thanks so much for verifying that this works.
hi to everyone concerned, i have begun monitoring this thread;
https://forum.xda-developers.com/v20/help/lg-v20-h910-kdz-t3612524/page2#post72599368
please direct any inquiry's to my experience there. there is also a link and directions there to restore any bricked lgh910 to the h910pr version, as well as development on using the h915 and h918 firmware.
Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?
Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.