Related
I havent rooted a phone since the galaxy s3 so i'm completely lost, I followed the steps for dirtysanta, but since it never booted into fastboot, I did a little more research and realized that it only works for Dec 2016 security patches and under
So is there anyway to root this thing, ****ing is like ALWAYS hot, I force stop apps and the battery just gets drained quick as hell, my iphone 6s plus kicks this things ass right now
Unfortunately not right now
What model?
-- Brian
You need to downgrade to firmware version before 31 december. You can do that with LGup tool just follow procedures
runningnak3d said:
What model?
-- Brian
Click to expand...
Click to collapse
997
Theres no way to root cause theres no kdzs avaible and all ls997 devs are gone
The LS997, F800L, H910, H915 all have the same RSA key in QFPROM. So, if you are still on ARB 0, then grab an old F800L (that will probably give you the least grief) KDZ, and flash it, after backing up your phone (using the DUMP option from the patched LG UP) of course -- you will need that backup to fix your phone.
If you are still on ARB 0, then your phone is rootable. If you are on ARB 1 or greater, then your phone is not rootable, and probably will only be rootable if a kernel exploit is found since you can't unlock your boot loader.
-- Brian
runningnak3d said:
The LS997, F800L, H910, H915 all have the same RSA key in QFPROM. So, if you are still on ARB 0, then grab an old F800L (that will probably give you the least grief) KDZ, and flash it, after backing up your phone (using the DUMP option from the patched LG UP) of course -- you will need that backup to fix your phone.
If you are still on ARB 0, then your phone is rootable. If you are on ARB 1 or greater, then your phone is not rootable, and probably will only be rootable if a kernel exploit is found since you can't unlock your boot loader.
-- Brian
Click to expand...
Click to collapse
Is this for real? And how do I find my ARB?
runningnak3d said:
The LS997, F800L, H910, H915 all have the same RSA key in QFPROM. So, if you are still on ARB 0, then grab an old F800L (that will probably give you the least grief) KDZ, and flash it, after backing up your phone (using the DUMP option from the patched LG UP) of course -- you will need that backup to fix your phone.
If you are still on ARB 0, then your phone is rootable. If you are on ARB 1 or greater, then your phone is not rootable, and probably will only be rootable if a kernel exploit is found since you can't unlock your boot loader.
-- Brian
Click to expand...
Click to collapse
How can I find my arb?
First the cool. I have wondered for a while if you check ARB via the SVC -> Version menu, and it says: "non-fusing device" exactly what that meant. Today I found out.
If you are lucky enough to have a non-fusing device, ARB isn't checked, you can run any ARB you want, and roll back to any version.
That leads to the question(s). I currently don't have device that is rooted with the engineering aboot. Can someone that is rooted, check to see what ARB version is displayed in that menu? I don't remember.
Which leads to the next question. Is there anyone that is currently running ARB 1 or greater firmware with the engineering aboot? For example, and LS997 with ZV8 or higher.
-- Brian
I'll check, but can't remember how to get into SVC for the H990
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
H910 running alpha 10T here, rooted with your tutorial (H915 -> H910 10R)
still showing non-fusing device.
runningnak3d said:
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
Click to expand...
Click to collapse
Thanks! My H990 is showing ARB 0
Some more info that may or may not be helpful:
• SW = H990 10e ZAF
• Kernel = DOTS 1.4
• SEPolicy = "Should be implemented" (guessing this means off)
• Bootloader Unlock Check = Bootloader Locked
Hope this helps in some way!
runningnak3d said:
*#lgmenu#*990#
Replace lgmenu with the numbers that correspond to the letters.
Is the H990 ARB 1 or greater?
Click to expand...
Click to collapse
My LS997 doesn't do anything when I type in *#lgmenu#*997#
@pro_granade Sprint pulled that menu, but I know for a fact that ZV8 is ARB 1, so if you are rooted and running ZV8 then you are ARB 1.
I am only interested in rooted ARB 1 or greater.
-- Brian
runningnak3d said:
@pro_granade Sprint pulled that menu, but I know for a fact that ZV8 is ARB 1, so if you are rooted and running ZV8 then you are ARB 1.
I am only interested in rooted ARB 1 or greater.
-- Brian
Click to expand...
Click to collapse
I'm non rooted locked bootloader on ZV9. Wanted to check if I had a non-fusing device
Well, you can always flash ZV7 or lower, and if you don't have a brick, you have a non-fusing device
On a serious note, I am looking to see how that is determined. It isn't pulled from the firmware, because the devices that I have checked all have some ARB version in the firmware, and yet ARB isn't respected.
Also, a non-fusing device can be turned into a fusing device via some method, but I don't believe the opposite is true. However, as long as the device reports non-fusing, ARB is ignored.
-- Brian
runningnak3d said:
First the cool. I have wondered for a while if you check ARB via the SVC -> Version menu, and it says: "non-fusing device" exactly what that meant. Today I found out.
If you are lucky enough to have a non-fusing device, ARB isn't checked, you can run any ARB you want, and roll back to any version.
That leads to the question(s). I currently don't have device that is rooted with the engineering aboot. Can someone that is rooted, check to see what ARB version is displayed in that menu? I don't remember.
Which leads to the next question. Is there anyone that is currently running ARB 1 or greater firmware with the engineering aboot? For example, and LS997 with ZV8 or higher.
-- Brian
Click to expand...
Click to collapse
I got unlocked & rooted H910 running 10T and it says "non-fusing device'. This would be a treat if Oreo increments ARB and we are still able to flash it without having second thoughts!
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
runningnak3d said:
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
Click to expand...
Click to collapse
My h910 shows the antirollback version as 0 instead of non-fusing device. So maybe only some h910's are non-fusing?
Also I'm currently running full stock so I do not have the eng aboot installed.
runningnak3d said:
My H910 is also non-fusing. I am starting to think that all H910s are non-fusing and that is why AT&T hasn't incremented ARB -- they can't. There is no way to change from a non-fusing to fusing via firmware, it requires a firehose.
Anyone that has a non-fusing device can safely take any update they want, ARB will never be incremented.
EDIT: also you can run any firmware you want (if it will actually work on your device -- except H918 -- different RSA key there). As a test, I took an LS997 ZV8 modem (ARB 1) and flashed it on my H910. Under normal circumstances that would have incremented ARB, and I would have had a brick since the rest of the firmware was ARB 0. As it was, it just boot looped because it didn't like the modem. I flashed the H910 modem back, and all was good.
-- Brian
Click to expand...
Click to collapse
pretty sure its related to the aboot. I ran zv8 all arb1 except i had the eng aboot installed.
Very interesting. I flashed my H910 back to stock, so no engineering aboot, and it is still non-fusing. So there are definitely phones that don't have the "respect ARB security" qfuse blown.
But it looks like maybe the engineering aboot may ignore it. So now the question is, if you have the engineering aboot installed, and you flash a higher ARB boot stack, does ARB get incremented?
Another question is what happens if you are ARB 1 or 2 and install the engineering aboot? As far as I can tell, it will work with any ARB version, but I have no way to test that since I have an H910 that is ARB 0 even if it wasn't non-fusing, and an H918 that can't use it.
More questions than answers. Lol.
-- Brian
It's been a while for me and I have a H918 that is running a rooted H91810p rom, I'm thinking my ARB is still 0, I want to install Super Rom 4.0 but I'm hesitating because I just don't want to brick my phone.. What is the current ARB for my model or how can I find it in my Hidden Menu settings..
Thank you in advance..
JustZaphod said:
It's been a while for me and I have a H918 that is running a rooted H91810p rom, I'm thinking my ARB is still 0, I want to install Super Rom 4.0 but I'm hesitating because I just don't want to brick my phone.. What is the current ARB for my model or how can I find it in my Hidden Menu settings..
Thank you in advance..
Click to expand...
Click to collapse
Im 99% sure that 10P is arb1 as I remember 10k was the last arb0 firmware. You could always just flash the latest stock ROM that dimmock is hosting in here somewhere. 10u is latest but I think he still had about 2 more versions behind that. It's an easy zip you flash in TWRP that is modified so it doesn't flash stock recovery
KUSOsan said:
Im 99% sure that 10P is arb1 as I remember 10k was the last arb0 firmware. You could always just flash the latest stock ROM that dimmock is hosting in here somewhere. 10u is latest but I think he still had about 2 more versions behind that. It's an easy zip you flash in TWRP that is modified so it doesn't flash stock recovery
Click to expand...
Click to collapse
Yeah, I checked the Service Menu and noticed it was ARB 1...
I just forgot how to get into that Hidden Menu...
Hello,
I Just bought from a website a " refurbished " LG V20 and sadly when I turned it on I was shocked it was on att but it's unlocked, but sadly since it's at&t I can't get software updates, is there a way that I can have a stock rom on it instead off at&t? if yes can you guys show me how ?
Note: I have 0 experience and how to do these kind of things but I can follow guide lines.
Search for backup EFS. Do it.
Then feel free to flash the US996 KDZ. Again, if you search, there is plenty of info.
-- Brian
runningnak3d said:
Search for backup EFS. Do it.
Then feel free to flash the US996 KDZ. Again, if you search, there is plenty of info.
-- Brian
Click to expand...
Click to collapse
Yep no spoon ? feeding
Sent from my LG-H910 using XDA Labs
thank you fr the reply!
I did this set uphttps://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 and i finshed it but now I am a bit confused on which rom to download follow guide lines , giving a help wull be nice >.>
MrSalue said:
thank you fr the reply!
I did this set uphttps://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 and i finshed it but now I am a bit confused on which rom to download follow guide lines , giving a help wull be nice >.>
Click to expand...
Click to collapse
Again no spoon ? feeding, try them out and find the one you like
Sent from my LG-H910 using XDA Labs
cnjax said:
Again no spoon ? feeding, try them out and find the one you like
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
MrSalue said:
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
Click to expand...
Click to collapse
No one is making anything difficult, search the forum, read the OP of rom threads until you find what you're looking for, how difficult is it to do some reading,? #NoSpoonFeeding
Sent from my LG-H910 using XDA Labs
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
runningnak3d said:
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
Click to expand...
Click to collapse
Lmao with a nick starting with Mr, you might be in for a surprise
Sent from my LG-H910 using XDA Labs
He got spoon fed
runningnak3d said:
Download patched LG UP
Download US996 10p KDZ
Place your phone into download mode. With the phone off, hold vol up and plug in the USB cable.
In LG UP, use the DUMP option and select modemst1, modemst2, persist, persistent and misc
Then while still in LG UP, use partition DL mode, select the US996 KDZ, select all partitions, and flash.
Enjoy your H910 converted to a US996.
If you have data or voice problems after the conversion, then you will have to root to fix it. You can't root on 10p firmware, so you will have to flash older firmware. Even though you will have flashed the US996 firmware, you can use the H910 root procedure here. Once you are rooted, you can flash a US996 stock ROM via TWRP to return to stock US996 (with or without keeping root -- tis up to you).
Once rooted, you can flash modemst1 and modemst2 (ignore the others, it is just a good idea to have backups of them) that you backed up in step 3.
Boot to flastboot. With the phone off, hold vol down and plug in the USB cable
fastboot flash C:\path\to\modemst1 modemst1
fastboot flash C:\path\to\modmst2 modemst2
Again, those steps will ONLY be required if for some reason you get unlucky and your EFS gets hosed.
@cnjax Hope that is a chick, cause I decided to hold her hand good.....
-- Brian
Click to expand...
Click to collapse
Thank you, your post is the first one I found that makes it seem fairly simple.
I have 2 V20 h910s I want to unbrand, one running AT&T version 10m and one running 10r (which complicates matters further), and I would like to avoid installing a bootloader/root/etc. which prevents future updates/upgrades to later software versions (so other existing guides have put me off for multiple reasons).
Is what you listed all I need to do (in both cases), or do I need to root (or bootloader unlock etc.) first?
Can I install any future stock US996 ROMs (ie when Oreo is released) once I have done this, or will I have to reverse the steps and start over with h910/ATT software?
MrSalue said:
I don't want to "try" I just want to know which is a normal stock rom with no bloatware that I can have root on x.x!!
you are making it so difficult on me xD
Click to expand...
Click to collapse
Edit: Brain explained to you rather more profoundly. I rest my case of explaining it further
dark_prince said:
Edit: Brain explained to you rather more profoundly. I rest my case of explaining it further
Click to expand...
Click to collapse
Hi.
I also have a few questions (as I'm new to this and have found conflicting information, and in addition I have two h910 phones running different firmware versions, one v10m and one v10r).
1) My phone's aren't rooted - Is what Brian explained all I need to do, or does his explanation require a bootloader-unlocked/rooted phone to work?
2) Are there any requirements/restrictions (eg. original firmware must be above/below version XYZ - if yes, does it make any sense to update the firmware to the latest AT&T version first)? Can I install any future versions of US996 KDZ that way too?
Thanks in advance.
AWT86 said:
Hi.
I also have a few questions (as I'm new to this and have found conflicting information, and in addition I have two h910 phones running different firmware versions, one v10m and one v10r).
1) My phone's aren't rooted - Is what Brian explained all I need to do, or does his explanation require a bootloader-unlocked/rooted phone to work?
2) Are there any requirements/restrictions (eg. original firmware must be above/below version XYZ - if yes, does it make any sense to update the firmware to the latest AT&T version first)? Can I install any future versions of US996 KDZ that way too?
Thanks in advance.
Click to expand...
Click to collapse
1. For 10m one, follow Brian's guide, for v10r, follow Brian's guide. Once you have unlocked bootloader/rooted, you have conceded official updates. Also there are no stock KDZ restoring methods to revert back to H910 but you can try a method to go bone-stock H910 if you're rooted and have TWRP recovery.
2. For H910? no, and no need to upgrade to latest att firmware. You can just jump the gun to US996
Edit: Make sure you take full backup dump with patched LGUP (from Brian's guide as well).
Thanks
dark_prince said:
1. For 10m one, follow Brian's guide, for v10r, follow Brian's guide. Once you have unlocked bootloader/rooted, you have conceded official updates. Also there are no stock KDZ restoring methods to revert back to H910 but you can try a method to go bone-stock H910 if you're rooted and have TWRP recovery.
2. For H910? no, and no need to upgrade to latest att firmware. You can just jump the gun to US996
Edit: Make sure you take full backup dump with patched LGUP (from Brian's guide as well).
Click to expand...
Click to collapse
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
AWT86 said:
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
Click to expand...
Click to collapse
1. Make a backup dump and flash US996 rom.
2. I havent known anyone who ran into corrupted EFS after crossflashing between H910/H915/US996. The restoring of modemst1,modemst2,modem, misc solves the problem of No baseband/IMEI. Do that at your own risk, there is no guarantee that you'll be safe from apocalypse
AWT86 said:
Thanks a lot.
Two final questions (sorry to bother you):
1) Do I need to root/bootloader-unlock the device BEFORE proceeding to use Brian's guide, or can I just dump & then flash US996 straight away without rooting? (I read somewhere that root is only required if the signals fail after US996 conversion, but I'd rather ask than to skip root / just flash and then realize I messed up).
2) Will EFS be backed up in the process of dumping everything using patched LGUP, or do I need to back up EFS manually/seperately? If the latter is what I need to do, what is the best method? (I've found multiple, but most of them require root, which I'd rather avoid unless necessary)
Click to expand...
Click to collapse
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
Hi.
I'm having trouble with LGUP. When I try to dump all phone files, it gives me an error 0x2000 saying "not enough hard disk space", even though there should be more than enough.
Device Manager recognizes the device under Ports as "LGE AndroidNet USB Serial Port (COM8).
Help would be highly appreciated.
Thanks in advance.
EDIT: I managed to dump the files you recommended, but what about the rest? shouldn't I back those up too?
---------- Post added at 11:51 AM ---------- Previous post was at 11:24 AM ----------
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
UPDATE: I flashed the first device, but it asked for a password that wasn't set up. UPDATE 2: solved w/ factory reset.
Thanks a lot and sorry for bothering you guys.
Glad you were able to do it.
As far as backing the other files up -- no, you can get those from a KDZ, so no reason to back them up. The partitions I had you backup are specific to your phone(s).
-- Brian
runningnak3d said:
You do not have to root, just follow my post for flashing the US996 KDZ.
You only have to root IF you have signal issues, because that is the only way to fix them. Even then, you don't have to stay rooted.
I doubt you will have signal issues, but make sure you backup those partitions before you flash the US996 KDZ.
-- Brian
Click to expand...
Click to collapse
Now flashed both devices, but noticed that the signals are unstable. Network jumps randomly from no network to 4G and back to no network etc - not in high frequency, but often enough for me to have noticed.
Does that mean I now have to go the route of rooting or is there anything else I can try?
Thanks and sorry to bother you once more.
PS: just noticed it seems to run stable with only 3G enabled, but once 4G is enabled the problem starts.
Good day!
I have a V20 Sprint right after DirtySanta. I want rooted Oreo, I live in Europe (sorry for my English) and use a local telecom operator (CDMA2000 1xEV-DO). There are many incomprehensible I did not find it on the forum.
1) Updating which firmware components increases ARB? I.e. aboot, modem etc.
2) How, having an img file or a kdz file, can I find out the ARB version?
3) Does ARB increase when flashing with any of these methods: "partition dl", "fastboot flash", kdzwriter?
4) Can someone share a Sprint V20 Oreo MODEM and SYSTEM dump?
5) Did someone try to cut the leads on motherboard @runningnak3d https://forum.xda-developers.com/t/...t-to-brick-your-phone-for-funsies-v1.3673622/ ?
6) It seems to me that the best option is to use SYSTEM (and MODEM?) from US99620f (US99620f_00_1120.kdz) . Both LS997 and US996 support CDMA2000 1xEV-DO frequency. US996 contains no bloatware. Does only vs995, us996 and ls997 support СDMA and they all have ARB 1 on Oreo?
7) How best to try:
a) Flash (Installing KDZ US996 7.0 via patched LGUP "partition dl" -> Re-installing the same KDZ via "update") LS997 7.0 to US996 7.0; then flash SYSTEM.img US996 8.0 (+ core mk2000 Oreo US996)? If there is no connection, flash MODEM.img US996 8.0?
Or
b) The same without prior full flashing to US996. Which kernel @askermk2000 and TWRP @Phoenix591 in the case of such a "Frankenstein" to use - LS or US? Which kernel is better to use in this case: LS997_v2.1, US996Santa_v2.2 or US996Santa_v2.2-BETA38? Would it make sense to flash the LS997 8.0 modem?
8) What is the best way to flash the SYSTEM and MODEM? kdzwriter, LGUP "dl partition", "fasboot flash"?
Thank you guys for your work and time!
An LS997 on Oreo is on ARB1 and therefore completely locked down and unrootable, so I don't think anyone has made any dumps from it. No idea which specific portion causes the ARB to change.
I would not recommend cross-flashing a modem unless someone else reported it to be working. You have a much higher risk of completely losing all cellular signal. Does your phone in its current state have signal reception problems?
The rootable LS997 on ARB0 is generally assumed to be stuck on Nougat for stock-based ROMs, and I haven't seen anyone try to flash any stock US996 Oreo parts, so that could be quite risky. If you really want Oreo or higher, then you should consider looking at the LineageOS-type ROMs.
For more things on the LS997, I've written up a bunch of general information in this post on the V20 Subreddit.
how to check ARB status?
nevermind, i got it back how do i confirm ARB?
xxTECRAxx said:
how to check ARB status?
nevermind, i got it back how do i confirm ARB?
Click to expand...
Click to collapse
As far as I know, only the H918 (software version H91810p or later, includes all on Oreo) and LS997 (software version LS997ZV8 or later, includes all on Oreo) have ARB enabled. So you don't have to worry about it on any other model, including the US996. Or did you actually cross-flash the US996 Oreo KDZ onto the LS997?
C D said:
As far as I know, only the H918 (software version H91810p or later, includes all on Oreo) and LS997 (software version LS997ZV8 or later, includes all on Oreo) have ARB enabled. So you don't have to worry about it on any other model, including the US996. Or did you actually cross-flash the US996 Oreo KDZ onto the LS997?
Click to expand...
Click to collapse
I did cross flash my LS997 with US996 10f kdz
xxTECRAxx said:
I did cross flash my LS997 with US996 10f kdz
Click to expand...
Click to collapse
Is it 10f or 20f (your screenshots show 20f)? It's certainly interesting to see US996 stock Oreo cross-flashed onto an old LS997 as I have never seen anyone do it before. Do things actually function normally on it?
Anyway, everything's still on ARB0, so you can downgrade any way you like. If you haven't already done so, you'll need to be on 10f in order to do the rooting procedure.
First, I made a backup of all partitions using LGUP. I flashed the unlocked LS997 with US99620f firmware in the "Partition DL" mode via patched LGUP . I have selected all sections except aboot and abootbak. Then, in fastboot mode, I flashed recovery 3.2.2-1. I`ve tried 3.3.1-1, 3.2.3-5, 3.2.3-4, but they can't do format data correctly. Then I flashed modem, modemst1 and modemst2 from the backup in fastboot mode. Then in recovery I flashed the last mk2000 kernel for Oreo - LS997_v2.1-mk2000.zip . Then magisk 19.5
P.S. I need SDMA, so I was flashing the kernel and modem from LS997. For GSM it may not be necessary.
kokos76 said:
First, I made a backup of all partitions using LGUP. I flashed the unlocked LS997 with US99620f firmware in the "Partition DL" mode via patched LGUP . I have selected all sections except aboot and abootbak. Then, in fastboot mode, I flashed recovery 3.2.2-1. I`ve tried 3.3.1-1, 3.2.3-5, 3.2.3-4, but they can't do format data correctly. Then I flashed modem, modemst1 and modemst2 from the backup in fastboot mode. Then in recovery I flashed the last mk2000 kernel for Oreo - LS997_v2.1-mk2000.zip . Then magisk 19.5
P.S. I need SDMA, so I was flashing the kernel and modem from LS997. For GSM it may not be necessary.
Click to expand...
Click to collapse
Very interesting. So all CDMA signal reception from your carrier and all root functions are working?
And did you use TWRP made for the US996 or LS997?
Any particular reason you went with Magisk 19.5 instead of a later version?
Also, there are a few more stock Oreo kernels for the LS997 that you could try (of course they've never really been tested since the regular LS997 on Oreo is unrootable):
- Phoenix591 has converted some of the mk2000 2.2 versions here
- ezzony's ezV2020 kernel also has an LS997 version here
C D said:
Is it 10f or 20f (your screenshots show 20f)? It's certainly interesting to see US996 stock Oreo cross-flashed onto an old LS997 as I have never seen anyone do it before. Do things actually function normally on it?
Anyway, everything's still on ARB0, so you can downgrade any way you like. If you haven't already done so, you'll need to be on 10f in order to do the rooting procedure.
Click to expand...
Click to collapse
it's 20f, not 10f. I had swapped toms to darn near everything on XDA but never happy with any of them. always something not working or I couldn't remove some built-in crap from so-called "stock" roms.
this last go I forget what I was trying to put on it but she stuck in the warning screen and wouldn't boot. i threw so many commands at inside fastboot mode, I am surprised it's not a paperweight. honestly, you name it, I sent it! wipe, format partition, didn't have a concern in the world, and I don't because I have a pixel 4a as the daily driver.
it should be noted, prior to this, I could never get LG Up to work as the app never recognized the phone. after fastboot mode not getting results booting into anything, I said f*ck it and put it into download mode. tiny bit of reading here and shortly after pulling the US996 20f KDZ file from LG, I had a stock RUNNING Oreo!
bro, seriously though, this Oreo runs the best that I've seen! it's smooth and fast! just a little on the heavy side. she's bloated and I need to trim the fat away. LG poisons the phone bad with all their garbage. runs like a champ though
I am extracting stock ls99720a Oreo from ls997 and will test it well before uploading it.
So I converted my US997 to an H873 to mess around with stock Pie to see if I could root it somehow. I did this in the past, but the one thing I never tried was to unlock the bootloader while using the H873 firmware. I flashed my unlock.bin file and now the bootloader is unlocked again. Unfortunately, maybe due to how the H873 differs from the US997, I experienced some weird behavior. Mainly data encryption issues inside of TWRP and I had to monkey around with the fingerprint id to pass SafetyNet with Magisk. Before I really bothered doing any of this (getting Magisk to work), I mainly wanted to ditch stock and revert back to the official firmware then go back to Havoc. The only problem is, despite multiple attempts at trying to flash the stock Oreo KDZ, my phone simply wouldn't boot into Android. After it exits download mode, it goes straight to fastboot mode and refuses to boot into anything else. I used "partition dl" in LGUP to flash over the Canadian firmware, but unlike the last time I did this, nothing worked. I tried with the bootloader locked and unlocked. I thought that perhaps the KDZ I was using was corrupted, but the issue with that is that by now I've downloaded multiple KDZs from different sources. The MD5 on all of them were exactly the same despite not matching the MD5 hash provided on whatever given source I obtained them from. I attempted flashing the same exact version of firmware that I did the first time I converted and I even tried older versions. Nothing.
I'm currently running my Frankensteined US997 with Magisk. I would just flash a custom ROM while keeping the H873 partitions, but I got write errors for /system with any recovery I used. As I'm writing this, I'm wondering what would happen if I maybe flashed the KDZ again after using partition dl, though I might've already tried that. Could this be an issue with the KDZ itself (downloaded on a different PC and it still had the same MD5 as all the others), perhaps the boot.img didn't go through?
Maybe if someone has a US99721e KDZ I could try, I could rule out that being an issue. I could try using partition dl then upgrade in LGUP, but you'd think that It'd still boot after doing it over and over.
If anybody has any idea of what could be happening here, your input would be greatly appreciated.
Thanks