Related
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
noamo48 said:
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
Click to expand...
Click to collapse
As of now, I'm going to be bold with my statement about the G4: The AT&T cannot and will not ever have an unlocked bootloader. I would also assert the likelihood of root on Marshmallow is slim to none. I'd say "none", except there's always a remote chance that someone with the time/money/know-how will decide not to give up until they've figured it out.
When you say "downgrading", I presume you mean going back to a previous build? If so, it is not possible. It would require the level of access that only an unlocked bootloader could provide, from what I understand. I think there was mention of some sort of bypass option that works on other devices, but it doesn't work with this one.
Long story short: get comfortable with your current experience, because it isn't likely to ever change with this device. I too had to replace my device under warranty (for the 2nd time), and was bummed when the replacement arrived having Marshmallow on it.
noamo48 said:
I had to make an insurance claim on my AT&T G3 recently and they sent me a G4 Android 6.0 / h81020n, build MRA58k. From what I understand, there's no way to root it and many don't expect there will be for a while...is that right? If so, what are my best options to downgrade and then root it? It's my only phone, and though I'm extremely competent with this stuff, I need to be sure it's a surefire method of downgrading. Thanks
Click to expand...
Click to collapse
I have not been able to downgrade H81020n since I got a replacement phone due to the infamous bootloop issue. I'm starting to wonder if somehow AT&T with or without support of LGE figured out which phones were rooted and injected some network packets to stress the radios in this device causing failures.
What's really unfortunate is the replacement devices all come with Marshmallow 6.0 on the H81020n ROM. That locked-down image, with the locked bootloader have made this device much less fun.
I've tried several downgrade paths with no success; the low-effort Root method, TOT downgrades with the LG flash utility, and good old fashioned send_commands.exe for image restoration to stock.
You need to use LGUP
http://forum.xda-developers.com/showpost.php?p=66316842&postcount=113
smknutson said:
You need to use LGUP
http://forum.xda-developers.com/showpost.php?p=66316842&postcount=113
Click to expand...
Click to collapse
I have LGUP and the .tot file. LGUP just won't allow me to flash it for some reason ?....
Sent from my LG-H810 using XDA-Developers mobile app
BTMoneyGang said:
I have LGUP and the .tot file. LGUP just won't allow me to flash it for some reason ?....
Sent from my LG-H810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you load the.tot, close the LGUP program then reopen it and attempt the flash?
Did you change the Port # in Device Manager?
Can the same downgrade be done on 21y for h810 I miss root
This is a thread for the progress of MM root on the AT&T variant of the LG V10. I am working to find a way to root it, even if it is not through a TOT, but a exploit.
I know some of you were wondering about my donate info, and so I decided to go and set up a Paypal if you felt so obliged haha. (Its in my info in my profile)
Right now I am examining a TOT that someone sent me and I will determine if it is corrupted too, or if we have a shred of hope. Wish me luck! Will update later if it is found that it is bad, which I expect.
Ok, so I just compared this TOT to the one that iBowToAndroid sent me, the 2nd time. They are practically identical, regardless of them having different MD5s. Although if anyone feels like actually testing it before they go to better phone, feel free. ha
If it will be possible (and when you will find a way), please, make possible for H960a too.
Well, i am happy to see someone is making progress on the root development on MM, at least, make the community alive.
However, MM needs systemless root and the old way by injecting su binary to the TOT will not work at all.
I am not going to discourage you, unlocking bootloader should be the only way to root MM.
ivangundampc said:
Well, i am happy to see someone is making progress on the root development on MM, at least, make the community alive.
However, MM needs systemless root and the old way by injecting su binary to the TOT will not work at all.
I am not going to discourage you, unlocking bootloader should be the only way to root MM.
Click to expand...
Click to collapse
Unlocking bootloader is something else I currently working on, if the su binary inject does not. Right now I am planning to pull the entire systems contents by soldering off the storage chip and reading it using some hardware of mine. Once I copy all of the partitions over, then the fun begins
ZVNexus said:
Unlocking bootloader is something else I currently working on, if the su binary inject does not. Right now I am planning to pull the entire systems contents by soldering off the storage chip and reading it using some hardware of mine. Once I copy all of the partitions over, then the fun begins
Click to expand...
Click to collapse
The KDZ files used by LGUP include an image of most of the flash used by the system. A few portions are missing, but not very many, notably the "misc" portion is absent. I believe the missing portions are ones that would be unaffected by rooting, so you could get most of the data out of a KDZ file and then root to get the rest of the data.
Aside from the key for the bootloader potentially being in the "misc" area, I also noticed there is noticeable amount of space reserved by the GPT, but unused. There is also a noticeable amount of unallocated space between the GPT and first slice (the "modem" area; this could be for alignment purposes, but it could have other uses as well).
Hopefully LG will be persuaded to unlock the bootloader of all V10 models, but I'm a bit on the pessimistic side at this point. I also hope the unlock mechanism will be shared by all V10s, so we don't need to reproduce it for each device. I haven't done cracking before, but I hope to target the H962 and be able to install full mods in the future...
How goes the progress ZVNexus? Thanks so much for embarking on such a journey for the sake of us all. I loved the flexibility of my Nexus 6, but it was so much weaker than the V10 in so many areas...especially the camera functionality and the ridiculous amount of sluggishness during normal tasks. I went through around 10 of these phones due to QC issues. I'm happy with my V10 (at&t gave me a replacement since I warranty returned the nexus so many times). But, it's just not the same without root and unlocked bootloader. Thank you again!
I found this today..I am sure you have seen it but I figured I would put it here anyway. I downloaded it but figured someone smarter should look before I tried to flash it. I cannot post it. Someone posted it on the original mm tot download thread..it was posted by radical.
In Theory...
In theory...
Are stock MM KDZ files available for the AT&T V10? I haven't seen them in the KDZ thread, but they may be posted in the AT&T area. If so, it should be possible to use my KDZ tools to unpack the KDZ, then install Superuser in the image and then repack the KDZ and tell LGUP to install the modified KDZ.
At the moment I'm cautiously optimistic about the KDZ tools. I've got all of the fields inside the files identified, but there some hazardously big ones in the DZ header that are unknown. My tools simply copy those, but I worry. Also SEEK_DATA/SEEK_HOLE are available on Linux, but likely not on Windows. (hack: replacing SEEK_HOLE with io.SEEK_END at the top of image2chunks.py should work around errors)
any update on this project?
I follow the V20 threads and all the V20s have root now. From what I read they used a debug boot.img from a Developer V20 and extracted the boot.img and used an exploit from the DirtyCow Root method to flash it. You have to really be involved to root it.
Just seeing where this can take the V10.
Any Update?
Sir is there any update on the root for at&t LG v10? Waiting anxiously!!
SH4DOW ASSASSIN said:
Sir is there any update on the root for at&t LG v10? Waiting anxiously!!
Click to expand...
Click to collapse
Nope. The hope of root for this phone was crushed long ago. Almost time for everyone to get new ones.
I am going to upgrade my phone from lg v10 to v20. Can you confirm me that is every lg v20 mobile carrier version ROOTABLE or i should buy a specific version?
SH4DOW ASSASSIN said:
I am going to upgrade my phone from lg v10 to v20. Can you confirm me that is every lg v20 mobile carrier version ROOTABLE or i should buy a specific version?
Click to expand...
Click to collapse
Don't do it. I'm done with LG. But a pixel or something, they are much better.
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Can u share the link I wanna try it also
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Is it a 8.0 kdz to update to 9.0 or directly a 9.0 kdz?
Did it work?
MishaalRahman said:
Did it work?
Click to expand...
Click to collapse
Lack of response, I'm gonna guess no? LoL
dah brick dah bricks.
???
The suspense is killing me. Personally I'm waiting for the official, but it would be nice to know...
i guess i would be able to flash it on my g7 , but i only have a .up file instead of a kdz and that doesnt work
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Edit: Apparently this was (mostly?) wrong. At least some confirmed models can be cross-flashed.
askermk2000 said:
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Click to expand...
Click to collapse
I thought that was only for TMoile but not the rest of variants?
GROOVYJOSHCLARK said:
I thought that was only for TMoile but not the rest of variants?
Click to expand...
Click to collapse
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
askermk2000 said:
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
Click to expand...
Click to collapse
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
askermk2000 said:
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
Click to expand...
Click to collapse
All good, I dont know for sure myself so I cant confirm nor deny anything except for my personal Octoplus flashing. I just want ROOT, thats what I am pressing through to figure out how to achieve. I HATE that LG locks the bootloaders, if I had known prior, I would NEVER have switched from HTC!
LG mobile will go out of business soon enough if they dont cut the crap.
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
askermk2000 said:
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
Click to expand...
Click to collapse
Exactly, hopefully the drop in sales will be enough to kick their butt's in gear BEFORE they become the next Blackberry! If they would simply give us a restore KDZ, we would love LG, instead, they lock us out, and make it damn near impossible to restore or recover our devices from normal things, such as a bad OTA updates. BUT NO, for some dumb A$$ reasons, they dont so it WILL be their demise. Its almost like being able to see the future. If they took notice of all the predecessors before them, all their mistakes, made changes then history wouldn't have to repeat itself. If not, LG will be another forgotten company no one gives a crap about.
GROOVYJOSHCLARK said:
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
Click to expand...
Click to collapse
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
runningnak3d said:
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
Click to expand...
Click to collapse
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
EM (European Model - bootload unlockable approved by LG):
G710EM10b_00_0521.kdz
https://drive.google.com/file/d/1W14Y-jbvnwDt4UOfitni8hDGfwYsXesV/view?usp=sharing
ULM (US Unlocked Model):
G710ULM10g_00_NAO_US_OP_0913.kdz
http://pkg02.lime.gdms.lge.com/dn/d...XADM55F9FR80/G710ULM10g_00_NAO_US_OP_0913.kdz
I flash ALL partitions through Octoplus EXCEPT the modems (MODEM1/2), I left those from Sprint (stock), not sure if it helps or not, but I have service so I like to think it did. There are lots of users who have also used the LGUP (somehow) to cross flash the KDZ's to the ULM (unlocked) model but I haven't personally used this LGUP method so I cant comment if its valid or not. Octoplus, most definitely works though (and I have the logs to show the partitions if one was interested).
GROOVYJOSHCLARK said:
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
<snip>
Click to expand...
Click to collapse
There will never be a Sprint KDZ -- neither Sprint or AT&T release KDZs (I don't think they even use them internally).
I am downloading them now, and I will pull the certs / post the results as soon as they are done.
Thanks!
-- Brian
Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?
Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.
Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.
Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked
It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way