Hello everyone.
I am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, Currently on oreo android 8.
PROBLEM THE NETWORK IS LOCKED AND NO SERVICE ...i have tried TO FLASHE WITH THIS FILE '' LG_V20_Lte-A_H918_LGH918_H91810j_00_1216.zip'' when i finish it my PHONE don't turn on '' HARD BRIK ''
MY QUESTION IS can this device BE UNBRIKED OR NOT
any help will be appreciated.
regards.
Hello and welcome to XDA!
Unfortunately, I have a very bad news for you. AFAIK your device cannot be unbricked other than by LG service center. Here is why:
H918 uses "anti roll back" versioning. This is so-called ARB version. The supposed reason is to prevent an attacker from rolling back your device to a version of firmware older than that where a significant security patch was once issued. At that point the ARB version is incremented. So, like from ARB0 to ARB1. (I am not aware of ARB2 yet for H918.)
When the ARB version is incremented (by flashing a newer KDZ that contains the update or by OTA), the process literally destroys some small fuses in a special memory chip called QFPROM (Quick Fuse Programmable Read Only Memory). After this point the fuses are burnt for good and cannot be restored, and this is the intent of the entire ARB system.
Now. If you decide to actually do what this ARB was designed to prevent in the first place, and load an earlier version on a device that had already been loaded with a later version of ARB, during the boot the device will check the new version and compare it with the one that a row of burned and remaining fuses just like ones and zeroes represent. If the fuses represent a later version than the version currently loaded the boot is stopped.
As far as I understand, the boot process is stopped at such an early stage that even the re-flash back to an older version is not possible as the system wasn't allowed to boot far enough to work with the flasher.
What you did wrong was you were on version 20h (which is ARB1), and you flashed (loaded) the firmware version 10j (which was ARB0). (Look: G_V20_Lte-A_H918_LGH918_H91810j_00_1216.zip. The ARB version was incremented from firmware version 10o to 10p, so 10p and all versions after that were already an ARB1. So, you did exactly what ARB was intended to prevent and now it killed your device.
I do not know if a QFLASH is a separate chip and could be replaced for a new one or not. Maybe this is exactly what a LG Service Center does. Don't know how much that cost. Don't know if there is LG service anymore as they just announced that LG is no longer in phone business.
I am not someone who knows everything. This is what I know so far. This could be wrong, but by all I've read here this is true. I suggest searching more, now that you know what happened. Now you know at least what to search for and how to explain what happened. Maybe there is some sort of exploit found that would allow to at least flash back to older release, ARB1, which is any firmware version from 10p and thru 20h that are available from here: https://lg-firmwares.com/lg-h918tn-firmwares/
Don't throw the phone away. On eBay, even a dead h918 is for sell at $40 for parts. Just so you know.
Good luck
Descent2 said:
Hello and welcome to XDA!
Unfortunately, I have a very bad news for you. AFAIK your device cannot be unbricked other than by LG service center. Here is why:
H918 uses "anti roll back" versioning. This is so-called ARB version. The supposed reason is to prevent an attacker from rolling back your device to a version of firmware older than that where a significant security patch was once issued. At that point the ARB version is incremented. So, like from ARB0 to ARB1. (I am not aware of ARB2 yet for H918.)
When the ARB version is incremented (by flashing a newer KDZ that contains the update or by OTA), the process literally destroys some small fuses in a special memory chip called QFPROM (Quick Fuse Programmable Read Only Memory). After this point the fuses are burnt for good and cannot be restored, and this is the intent of the entire ARB system.
Now. If you decide to actually do what this ARB was designed to prevent in the first place, and load an earlier version on a device that had already been loaded with a later version of ARB, during the boot the device will check the new version and compare it with the one that a row of burned and remaining fuses just like ones and zeroes represent. If the fuses represent a later version than the version currently loaded the boot is stopped.
As far as I understand, the boot process is stopped at such an early stage that even the re-flash back to an older version is not possible as the system wasn't allowed to boot far enough to work with the flasher.
What you did wrong was you were on version 20h (which is ARB1), and you flashed (loaded) the firmware version 10j (which was ARB0). (Look: G_V20_Lte-A_H918_LGH918_H91810j_00_1216.zip. The ARB version was incremented from firmware version 10o to 10p, so 10p and all versions after that were already an ARB1. So, you did exactly what ARB was intended to prevent and now it killed your device.
I do not know if a QFLASH is a separate chip and could be replaced for a new one or not. Maybe this is exactly what a LG Service Center does. Don't know how much that cost. Don't know if there is LG service anymore as they just announced that LG is no longer in phone business.
I am not someone who knows everything. This is what I know so far. This could be wrong, but by all I've read here this is true. I suggest searching more, now that you know what happened. Now you know at least what to search for and how to explain what happened. Maybe there is some sort of exploit found that would allow to at least flash back to older release, ARB1, which is any firmware version from 10p and thru 20h that are available from here: https://lg-firmwares.com/lg-h918tn-firmwares/
Don't throw the phone away. On eBay, even a dead h918 is for sell at $40 for parts. Just so you know.
Good luck
Click to expand...
Click to collapse
I am very grateful to you for your very clear answer... I should have researched before flashing my phone .. thanks
mohcenl said:
I am very grateful to you for your very clear answer... I should have researched before flashing my phone .. thanks
Click to expand...
Click to collapse
Did you try to remove the battery, hold the volume up button, and connect USB?
Related
Hi I'm looking for h915 users of the Canadian v20 that have successfully rooted their phones. I have many questions and concerns to ask concerning the h915.
I don't know if in 2018, will there still be h915 Users since not much developments for the h915.
Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*
murph187 said:
Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*
Click to expand...
Click to collapse
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?
darkknight200 said:
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?
Click to expand...
Click to collapse
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.
darkknight200 said:
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/how-to/h915-guide-fix-lagg-signal-root-lg-v20-t3699540
Freedom/wind functioning just fine according to this thread.
As for the V30; Oreo beta release is already out to the entire country of South Korea for the V30, for a few weeks. A small select few of American users have already received this beta as well.
G6; China has already been testing 8.0.
Seeing as 8.1 is already released, it's highly presumed by a many sources that LG will likely skip 8.0 altogether and push 8.1 to our devices. 8.0 merely serves as a means to identify larger incompatibilitys/bugs.
i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.
darkknight200 said:
i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.
Click to expand...
Click to collapse
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?
murph187 said:
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?
Click to expand...
Click to collapse
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.
the op of that thread @dksoni411 will be including a separate guide for h915 users in that thread since it has additional steps to follow. In the meantime, i can help you if you want to get root on the h915.
murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means .
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
Could you share the link where announcement was made about releasing Android Oreo for LG V20?
dksoni411 said:
Could you share the link where announcement was made about releasing Android Oreo for LG V20?
Click to expand...
Click to collapse
i made this thread https://www.reddit.com/r/lgv20/comm..._v20_canadian_update/?st=jeh88vej&sh=d1dca001.
keep in mind i asked for info on the h915 since its been stuck on may security patch.
Lge security product is suppose to be the best accurate info compared to the customer rep of lg social media accounts.
darkknight200 said:
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.
Click to expand...
Click to collapse
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?
murph187 said:
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?
Click to expand...
Click to collapse
no i used patched lgup to flash us99610f kdz to get working signal and then did the whole guide again to get a working signal rooted h915 phone. Afterwards no need to do any baseband installing as the signal is strong as how it was on normal h915.
Wifi calling working on freedom after root?
EnIXmA said:
Wifi calling working on freedom after root?
Click to expand...
Click to collapse
No wifi calling.
Hey there devs and V20 users alike.
As if there wasn't already hesitation enough to root this headache of a phone, and just when I was about ready to take the dive, I received the Oreo OTA update about three weeks ago.
Since updating, I've been enjoying the phone thoroughly.
If I'm going to be honest, this is the first phone I've owned (out of MANY since the Galaxy Captivate S days) that I have been satisfied using without root. It's an absolute multimedia powerhouse. However, little things like the inability to utilize ad blockers, tweak kernels, access root storage, etc. Does bother me now and then, although infrequently.
I'm looking through the forum here, and I'm beginning to think that due to LG's unbelievably long release of oereo, and the difficulty of root, devs have long left this device in the dust.
Unless I'm missing something, is there any rooted Oreo ROM available ATM? I absolutely will not revert to 7.1 again.
Thanks in advance!
Murph.
murph187 said:
Hey there devs and V20 users alike.
As if there wasn't already hesitation enough to root this headache of a phone, and just when I was about ready to take the dive, I received the Oreo OTA update about three weeks ago.
Since updating, I've been enjoying the phone thoroughly. If I'm going to be honest, this is the first phone I've owned (out of MANY since the Galaxy Captivate S days, that I have been satisfied using without root. It's an absolute multimedia powerhouse. However, little things like the inability to utilize ad blockers, tweak kernels, access root storage, etc. Does bother me now and then, although infrequently.
I'm looking through the forum here, and I'm beginning to think that due to LG's unbelievably long release of oereo, and the difficulty of root, devs have long left this device in the dust.
Unless I'm missing something, is there any rooted Oreo ROM available ATM? I absolutely will not revert to 7.1 again.
Thanks in advance!
Murph.
Click to expand...
Click to collapse
No root yet. we still have a handful of devs around although it is slowly becoming more of a ghost town as far as Dev work.
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Phoenix591 said:
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Click to expand...
Click to collapse
Relax slim, it's just a question.
Phoenix591 said:
Oreo hasn't even been released for most variants yet. Just chill out and wait.
Click to expand...
Click to collapse
^^^
I can confirm the ls997 has oreo. and i've seen a few other people talking about their oreo updates here on XDA on different models.. Idk how many models there are of the v20 though..... Still waiting for ls997 root I'd love to OC this phone for even better performance Or at least manage its cpu to avoid overheating 24/7
texas7412 said:
^^^
I can confirm the ls997 has oreo. and i've seen a few other people talking about their oreo updates here on XDA on different models.. Idk how many models there are of the v20 though..... Still waiting for ls997 root I'd love to OC this phone for even better performance Or at least manage its cpu to avoid overheating 24/7
Click to expand...
Click to collapse
Have Oreo: F800 LS997 H915 H910
Not yet: H910PR H918 H990{N,DS several regions getting otas at different times within those variants} US996(BPT USC USA) VS995
Phoenix591 said:
Have Oreo: F800 LS997 H915 H910
Not yet: H910PR H918 H990{N,DS several regions getting otas at different times within those variants} US996(BPT USC USA) VS995
Click to expand...
Click to collapse
VS995 already got the update 1 or 2 days ago, still it is too late already
root please
please dev, find a way to root my LG V20 F800S Korean version, Oreo. :crying:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
runningnak3d said:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
Click to expand...
Click to collapse
Hey Brian, glad to see you still around these parts lol
Edit
I thought the key to root on oreo with eng bootloader was the 996 oreo release or has that changed?
Sent from my LG-H910 using XDA Labs
Yea, I am definitely still around -- just nothing I can do right now.
I am pretty sure I can get it working with a modified kernel, but I need to be able to see logs -- so that means I need my H910
-- Brian
runningnak3d said:
Yea, I am definitely still around -- just nothing I can do right now.
I am pretty sure I can get it working with a modified kernel, but I need to be able to see logs -- so that means I need my H910
-- Brian
Click to expand...
Click to collapse
hi brian,
if there's something i can help you or if you need something to do with rooting lg v20 oreo, just let me know. i really want to root my F800S
Dirtysanta eng aboot works on oreo now
runningnak3d said:
In order to get root with Oreo on any model besides the H918, a custom kernel will be needed -- and I don't mean just compiling up the sources from LG.
I am going to try and migrate from my H910 over to one of my H918s .. but that is going to take a bit. Then I will have a phone that can use the eng. bootloader, and can actually start to work on it.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/h910-att-lg-v20-stock-oreo-rooted-t3846384
Recently they have found out that to get eng aboot to work with oreo firmware, it was just a simple zip making modifying 2 files.
1. stock aboot changed to common dirtysanta eng aboot
2. stock v20 variant oreo boot changed to magisk patched stock oreo v20 variant boot
We have to keep the recovery as stock recovery so letting the previous twrp get flashed over.
The key is letting the oreo firmware boot up first time with stock recovery and then data will work like normal
Then we boot it up first time and it will get to system and then do quick setup and then go into fastboot (thanks to the eng aboot intact) to push the twrp recovery back to working order again.
So it was just simply doing that instead of using patchd lg up to partition dl to ignore the 3 things : aboot, boot, recovery.
That means eng aboot is still good to be able to use on oreo for all dirtysanta v20s .
I am personally running h910 oreo root with very early build of mk2000 beta 2 oreo kernel. My phone gets full lte data like normal. The battery drain is much improved from nougat while still having the same kind of performance I was used to on rooted nougat.
Asked this on other threads but no answers yet, let me see if I get my answers here
I have a f800l lg v20 not Rooted
Android 7.0
Updated security patch 1st september 2016
Kernel 3.18.31
Build no Nrd90m
Software version F800L 10g
My question is that can I update my Android to Oreo 8.0 which is available via Software update and then gain root access? If no, what is the last update limit for me to not lose rooting possibility. Or is it possible to downgrade to a previous update state after updating it to either Oreo 8.0 or other updated security patch levels? What would you suggest? I've heard Oreo is good with little battery drainage percentage as compared to Nougat which is my primary interest. I don't want to make a move to lose my rooting ability. Are there any other means available to upgrade to oreo without using lg software update in order to achieve both Oreo and root? And if it is not possible to achieve both Oreo and root are there any custom roms or kernels available with good battery drainage percentage? What would suit me the best. Sorry in advance for asking so many questions and not knowing if these questions have already been discussed and answered.
Thank you
Your phone is still ARB 0, so you can do whatever you want.
As for rooting Oreo, now that I know that it expects stock recovery on first boot, I will be posting zips for every model that has a KDZ.
You will need to root your phone first. Since you are on September 2016 patch, use DirtySanta.
-- Brian
runningnak3d said:
Your phone is still ARB 0, so you can do whatever you want.
As for rooting Oreo, now that I know that it expects stock recovery on first boot, I will be posting zips for every model that has a KDZ.
You will need to root your phone first. Since you are on September 2016 patch, use DirtySanta.
-- Brian
Click to expand...
Click to collapse
by the way, no point in making the zip for h915 oreo.
I have tried with the same new method zip that was made with the 2 modified files + stock recovery.
The h915 modem just doesn't want to work with eng aboot whatsoever just like how it was on h915 nougat rooted.
please post oreo zip file for F800L, i can't wait to have oreo rooted on my F800L
darkknight200 said:
by the way, no point in making the zip for h915 oreo.
I have tried with the same new method zip that was made with the 2 modified files + stock recovery.
The h915 modem just doesn't want to work with eng aboot whatsoever just like how it was on h915 nougat rooted.
Click to expand...
Click to collapse
Perhaps this is something that can be circumvented in the kernel, like runningnak3d was talking about earlier, and like emdroidle did for H990.
I don't know how it works, but I could try enabling the same fix that's used for h990, for h915 oreo.
thank you runningnak3d
Ok I'll llet you know once I root my F800 L
Update: I managed to flash twrp via DirtySanta method. I can get into recovery twrp and use it but i haven't flashed SuperSu yet. I can't get comfort view working and the battery is draining relatively fast, So by flashing super su will I get Comfort view and old battery drainage rate back or do I have to do something else? Shall I flash supersu? I get a red triangle mark every time I restart my phone which takes longer than it used to in order to boot, which means I have Bootloader unlocked, can unlocking bootloader ignite problems like long booting duration, inability to use comfort view and fast battery drainage? What do you suggest I do? flash supersu? or relock the boot loader without getting Supersu? Will doing so even fix these problems becasue I planned on rooting to get better battery drainage percentage, instead I get more battery drainage, please help @[runningnak3d]
Hello!
I have a rooted LG V20 H990DS running nougat. Can I upgrade to Oreo without loosing root?
If yes, could you please tell me what is the best way to do so?
Phone: LG V20 H990DS
kernel: 3.18.90-DOTS_H990_kernel-leicxan_jahlex-v1.4
ROM: stock
Build Number: NRD90M
OS Version: Nougat (7.0)
I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option
Hi,
I currently have LS997 with ZV3 firmware which is rootable and dumped the whole system using LGUP before I do the dirtysanta on this.
Is it possible to use this dumped files to downgrade other LS997 phones with non-rootable firmware? (ex. ZV8 and up)
Did anyone try this before?
Thanks for reading!!
lentm said:
Hi,
I currently have LS997 with ZV3 firmware which is rootable and dumped the whole system using LGUP before I do the dirtysanta on this.
Is it possible to use this dumped files to downgrade other LS997 phones with non-rootable firmware? (ex. ZV8 and up)
Did anyone try this before?
Thanks for reading!!
Click to expand...
Click to collapse
This would be a definite game changer if so that I could use myself. But unfortunately if I am not mistaking, I think (could be wrong) that firmwares are baked on the chips themselves so ARB is still an issue after implementation on ZV8.
Mysticblaze347 said:
This would be a definite game changer if so that I could use myself. But unfortunately if I am not mistaking, I think (could be wrong) that firmwares are baked on the chips themselves so ARB is still an issue after implementation on ZV7.
Click to expand...
Click to collapse
I understand. Thanks for the reply!
arb is done with tiny electronic fuses that are part of the SOC (basically cpu) itself. Once the fuses are burnt there's no going back, the same fuse system also tells the SOC other very important things like "This is LG's signature and don't run bootloaders without it"
Hello, I apologize for the noobish question in advance.
I don't have an LG V20 myself, my friend has one and wants to unlock the bootloader. Normally Verizon devices are NOT bootloader unlockable but when I looked on this site (could be fake but who knows till they ask) it appears the Verizon variant of the LG V20 is in fact unlockable. As someone who is unfortunately very familiar with Verizon variants of phones, this is unusual news to me. Usually Verizon locks their stuff down with no hope of unlocking.
Anyway, just wanted to ask if that site's guide was correct for how to unlock the bootloader on the LG VS995 variant from Verizon. His Android version is 8.0.0, build number OPR1.170623.032. Software version VS99520c. Security patch October 1st, 2018. Security software version MDF v2.0 Release 4. Do I need to downgrade the firmware at all or can I just do it?
Any help would be greatly appreciated. He wants LineageOS on that thing (to get the latest security patches) and I don't blame him.
It's not that easy unfortunately.
The first thing that would need to be done is to revert the phone back to Nougat 12a or 13a. I have not done this part (both my VS995 were on some version of Nogat, I reverted the version to 12a by flashing the kdz), but guides are available to revert to Nogat from Oreo on XDA in the
https://forum.xda-developers.com/v20/
Section.
Then what is on that site would most likely work. I would suggest using this guide instead as I have rooted two VS995 with it. It is less confusing that the Dirty Santa or Dirty Elf guides IMHO, but it is later and builds on those guides.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278.
Good luck, although if you plan to use the phone on Verizon, it's only a matter of time before a stock ROM with VoLTE is a requirement for using the phone. I guess he can switch back at that point (or go to one of the GSM providers).
Dread1111 said:
The first thing that would need to be done is to revert the phone back to Nougat 12a or 13a. I have not done this part (both my VS995 were on some version of Nogat, I reverted the version to 12a by flashing the kdz), but guides are available to revert to Nogat from Oreo on XDA in the
https://forum.xda-developers.com/v20/
Section.
Then what is on that site would most likely work. I would suggest using this guide instead as I have rooted two VS995 with it. It is less confusing that the Dirty Santa or Dirty Elf guides IMHO, but it is later and builds on those guides.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278.
Good luck, although if you plan to use the phone on Verizon, it's only a matter of time before a stock ROM with VoLTE is a requirement for using the phone. I guess he can switch back at that point (or go to one of the GSM providers).
Click to expand...
Click to collapse
Just to clarify this isn't just a root this is a full on bootloader unlock right? I assume it is because TWRP gets flashed, but then again there were custom recoveries in the past that were just Safestrap and weren't full on recoveries (still locked BLs). Because the end goal here is to install Lineage or something like that to the phone. I'm not interested in just rooting stock.
Also, wasn't aware about the stock ROM requirement thing for Verizon, I thought it was only VoLTE they were implementing. That's a bummer. Thanks for the heads up