Trying with ADB but i'm not able to even get passed the first step, here's my cli:
C:\adb>fastboot devices
C:\adb>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>fastboot devices
LGH9189ef6091f fastboot
C:\adb>adb push dirtycow /data/local/tmp
error: device '(null)' not found
C:\adb>
C:\adb>adb push twrp.img /sd/twrp.img
error: device '(null)' not found
C:\adb>fastboot devices
LGH9189ef6091f fastboot
C:\adb>adb devices
List of devices attached
C:\adb>fastboot devices
LGH9189ef6091f fastboot
C:\adb>adb push dirtycow /data/local/tmp
error: device '(null)' not found
C:\adb>
Anyone have any thoughts? Any easier way to install twrp?
Yeah.... Don't!!! Read forums.
emeianoite said:
Trying with ADB but i'm not able to even get passed the first step,
...
Anyone have any thoughts? Any easier way to install twrp?
Click to expand...
Click to collapse
You're lucky you didn't brick your phone. Last version able to successfully install a recovery/root was update 10p IIRC.
Keep an eye on this thread and keep your fingers crossed. It's the most promising work I'm aware of to crack a V20. It also happens to be a fascinating read - so I'd recommend starting at the beginning.
:good:
Cheers!
Actually 10j was the last version that was rootable with DirtySanta, and 10k was last version that was ARB 0 so you could roll back to 10j. 10p was the first version that was ARB 1 so you can't roll back to 10j on 10p or higher.
-- Brian
I'll check the thread, is there a way to roll back or am i stuck? I guess I can re oem lock the phone. I have the message about not being able to verify bootloader but it boots just fine.
I tend to have good luck not bricking devices.
storm68 said:
Yeah.... Don't!!! Read forums.
Click to expand...
Click to collapse
Lol I know. Reading is hard these days
Sent from my LG V20 using XDA Labs
BROKEN1981 said:
Lol I know. Reading is hard these days
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
That's a little condescending. Beating a dead horse there, bud.
SMTB1963 said:
You're lucky you didn't brick your phone. Last version able to successfully install a recovery/root was update 10p IIRC.
Keep an eye on this thread and keep your fingers crossed. It's the most promising work I'm aware of to crack a V20. It also happens to be a fascinating read - so I'd recommend starting at the beginning.
:good:
Cheers!
Click to expand...
Click to collapse
Wait, i am so confused on the LG V20 side of things, so i would love it if someone took the time to reply back, but right now i am on H91810q (T-Mobile), does that mean i can successfully install TWRP with no issues ? (I have not done the Dirty Cow Exploit nor have i rooted yet, Still waiting for it to possibly happen on the update i am on.
Another thing i am confused on is finding the right answer as to whether or not the update that i have currently on my phone (H91810q, T-Mobile) has ARB implemented ( AKA Anti-Roll Back)
Thank you if you have replied, if not it doesn't matter.
Take Care : )
ROOT67 said:
Wait, i am so confused on the LG V20 side of things, so i would love it if someone took the time to reply back, but right now i am on H91810q (T-Mobile), does that mean i can successfully install TWRP with no issues ? (I have not done the Dirty Cow Exploit nor have i rooted yet, Still waiting for it to possibly happen on the update i am on.
Click to expand...
Click to collapse
I think runningnak3d summed up the situation pretty succinctly a couple of posts ago, but I'll try once again.
There is no known way to install twrp or gain root on any H918 running update 10p or later.
(hope I didn't screw that up this time lol)
ROOT67 said:
Another thing i am confused on is finding the right answer as to whether or not the update that i have currently on my phone (H91810q, T-Mobile) has ARB implemented ( AKA Anti-Roll Back)
Click to expand...
Click to collapse
I believe 10q has ARB implemented.
runningnak3d is working on a method that looks pretty promising, AFAICT. Watch his thread and hope he's successful!
MY KID UPDATED MY PHOEN THIS WEEK.... I'm in 10t, do I remove her from this world now or later?
Related
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!
Is there any way to downgrade to 4.5.3 without going through Amazon?
what is the command line to disable auto update ?
and does it auto update ?
alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?
alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak
Yeah it was an OTA update. Literally just as is was getting my laptop out to block them
otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process
UPDATE Thanks to @thjubeck for testing this, it seems that this userdebug kernel actually works on all devices running antirollback v0 and running Marshmallow! I only have the Sprint variant, so be careful!!! Enjoy root guys
A bit of a disclaimer is that this is root through adb. dm-verity is off and system is rw, so you can install apps as root, get a hotspot hack to work, and anything through a shell but I am having trouble installing SuperSU. Please try yourself though as I am probably doing something wrong! If there are any bugs you have found please post them, as this phone is my backup and not my daily driver.
So okay, here is the guide:
PLEASE MAKE SURE YOU HAVE A WAY TO GO BACK INCASE THINGS GO WRONG. DO NOT ATTEMPT TO ROOT THIS WITHOUT HAVING A KDZ/TOT FOR YOUR DEVICE THAT YOU KNOW YOU CAN FLASH BACK TO. I AM NOT RESPONSIBLE FOR THINGS GOING WRONG.
1. Download this zip
2. Install Terminal Emulator from the Play Store
(This is modified from the V20 bootloader unlock, HUGE thanks to all of those devs for sharing their dirtysanta code with me and allowing me to modify it!)
3. Copy all the files from inside the "dirtysanta-boot" and paste it into your active ADB directory
4. Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
(When you run The sh or Bat files there may be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.)
5. Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
6. Open Up Terminal Emulator on your phone
Type:
Code:
id
Check if context is "Untrusted_app". If it is then we're good to go!
7. Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
8. Watch the RUNMEFIRST dialog for when it tells you to run Step2 (we don't have a step 2)
9. Reboot the phone into recovery mode and wipe data again
BOOM! Now the you have a userdebug kernel running on a userdebug system Time to turn off dm-verity, otherwise you will have a red triangle on reboot (Your device is corrupt. It cannot be trusted and may not boot) and cannot edit /system.
1. Finish setting up the phone and enable USB Debugging in developer options (you should know how to do this)
2. Plug the phone into your computer, and run these commands
Code:
adb root
adb disable-verity
3. Reboot the phone
4. Run
Code:
adb root
adb shell
mount -o rw,remount,rw /system
Bam. Enjoy your FULL UNLIMITED root shell with system set to rw and dm-verity off!!! Just make sure to type "adb root" before "adb shell"
If you ever want to go back, just flash your stock TOT/KDZ with UPPERCUT and you'll be all good!
BUY ME A PIZZA FOR THE HARD WORK: BTC 197ct1uti4zutJu76bYAW51H8NZ6zXeoEV PayPal: [email protected]
THANKS:
@tungkick for the userdebug boot and helping me with the ZV4 TOTs
@autoprime for UPPERCUT
@me2151 @glitschi667 @EMSpilot @elliwigy for their AMAZING work on the V20 and sharing their code!
Thanks for the mention. Since you didnt say anything else i thought you bricked. Glad it works for you guys
I'm assuming this won't work if I'm on nougat, is that right?
fenguepay said:
I'm assuming this won't work if I'm on nougat, is that right?
Click to expand...
Click to collapse
Nougat is the latest update (ZV8 I think), this only works on ZV4.
Glad I stayed on ZV3 since July.
Happy this is out now. There was some sass going on in another thread but it seems there's still some civility among us. I'll check this out and report anything of note. I'm most interested in a viable hotspot mod, so if I can figure out how to modify the APN settings I'll be quite happy. Will donate as soon as I figure out how.
SilverZero said:
Nougat is the latest update (ZV8 I think), this only works on ZV4.
Glad I stayed on ZV3 since July.
Happy this is out now. There was some sass going on in another thread but it seems there's still some civility among us. I'll check this out and report anything of note. I'm most interested in a viable hotspot mod, so if I can figure out how to modify the APN settings I'll be quite happy. Will donate as soon as I figure out how.
Click to expand...
Click to collapse
Lucky you! Make sure you flash the stock ZV4 TOT before trying this
An unlimited Hotspot is definitely possible. I'm on mobile right now but I'll see what I can do when I get home.
Honestly Annoying said:
Lucky you! Make sure you flash the stock ZV4 TOT before trying this
An unlimited Hotspot is definitely possible. I'm on mobile right now but I'll see what I can do when I get home.
Click to expand...
Click to collapse
I'd be first in line to give this a whirl in the real world but I'm leaving in the morning for a week or so on the road. Maybe I'll be able to do some playing around at the hotel. Hotspot is the brass ring, adblock is a close second. I've survived this long, so hopefully a few days of testing and squashing bugs won't kill me. I do want to be of service to the community if possible. It will be interesting to see how these new developments affect the development of the various G5 variants.
My apologies if I insinuated that I'm at all peeved with anybody working on this device or just offering encouragement. I know there are some conflicting personalities in the mix right now, so I hope everybody benefits and sees the value in what you're potentially onto with this.
SilverZero said:
I'd be first in line to give this a whirl in the real world but I'm leaving in the morning for a week or so on the road. Maybe I'll be able to do some playing around at the hotel. Hotspot is the brass ring, adblock is a close second. I've survived this long, so hopefully a few days of testing and squashing bugs won't kill me. I do want to be of service to the community if possible. It will be interesting to see how these new developments affect the development of the various G5 variants.
My apologies if I insinuated that I'm at all peeved with anybody working on this device or just offering encouragement. I know there are some conflicting personalities in the mix right now, so I hope everybody benefits and sees the value in what you're potentially onto with this.
Click to expand...
Click to collapse
I will absolutely be in touch with you for an adblock and hotspot hack, PM me your Skype
I think I found a way to get the hotspot hack, waiting for a tester...
I'm on z5, can I still follow this guide on the dot and flash z4?
btw, gratz and great job on your achievement!
bigid said:
I'm on z5, can I still follow this guide on the dot and flash z4?
btw, gratz and great job on your achievement!
Click to expand...
Click to collapse
Thank you!
Unfortunately ZV5 has antirollback enabled, so you can't downgrade to ZV4. If you really want to try it you can attempt to flash the ZV4 userdebug boot without the userdebug system (just follow the guide past the TOT steps) but I believe it will bootloop. I have not personally tried this so I have no way of saying for sure, but it'll probably bootloop.
Honestly your name does you justice! Thanks for your hard work
So bummed that I updated...
Sent from my LGLS992 using XDA-Developers mobile app
Honestly Annoying said:
Thank you!
Unfortunately ZV5 has antirollback enabled, so you can't downgrade to ZV4. If you really want to try it you can attempt to flash the ZV4 userdebug boot without the userdebug system (just follow the guide past the TOT steps) but I believe it will bootloop. I have not personally tried this so I have no way of saying for sure, but it'll probably bootloop.
Click to expand...
Click to collapse
so should i just update to nougat now?
EDIT: No items in the Google Drive folder? Am I missing something?
I'm definitely hoping to spend some time testing this out, but it's bad timing that I just got the family out on vacation. Hopefully I'll spend some time tonight or tomorrow, and quite likely after the 25th I'll have some time.
Meanwhile, I've got to figure out a solution to getting ADB working on my MacBook. It's EFI locked so I can't install the full SDK, and my windows VM isn't working either. Since I'm pretty sure I need a windows environment that will be my first hurdle. I wish I could sit down right now and just try it out for the community's benefit, but hopefully we'll get there soon.
Man I feel like buying a G5 just to try this on nougat! Does this also unlock the boot loader or allow twrp to be flashed?
chippinganimal said:
Man I feel like buying a G5 just to try this on nougat! Does this also unlock the boot loader or allow twrp to be flashed?
Click to expand...
Click to collapse
It only works if you still have version ZV4 or lower, so forget about nougat. At best you'll be rooted on ZV4 forever with a wonky system.
It will not unlock the bootloader since it's just a user-debug upgrade for tinkerers, but nonetheless useful to some.
Wait. Where did you get the userdebug build for G5?
Plug your device into the computer and verify ADB is working
Could this be a means for (or a step closer to) getting full root, or is that basically off the table?
Sent from my LGLS992 using XDA-Developers mobile app
Error: Error Code = 0x2000 when trying to flash.
So Ive been trying to root v20 for some time now. Ive followed instructions up to point of step 4. I type in terminal emulator applypatch /system/bin/atd /storage/emulated/0/dirtysanta. Nothing happens
Next it reads
Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...
to specify reading from or writing to an MTD partition.
Have I done something wrong? Has something changed? any help would be greatly appreciated.
You are patched. No root for you.
ZV5 or earlier only.
Lg v20 vs995
So I"ve been trying to root v20 for some time now. I've followed instructions up to point of step 4. I type in terminal emulator applypatch /system/bin/atd /storage/emulated/0/dirtysanta. Nothing happens
Next it reads
Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>: ...
to specify reading from or writing to an MTD partition.
I've tried it alot of times again and again but it says same all the time
Please help me
Roll back to a version that has the December 2016 security patch or earlier. There are several threads around here that tell you what version you need to be on (heck I wrote one of them) -- search is your friend.
-- Brian
runningnak3d said:
Roll back to a version that has the December 2016 security patch or earlier. There are several threads around here that tell you what version you need to be on (heck I wrote one of them) -- search is your friend.
-- Brian
Click to expand...
Click to collapse
Can I roll back from ZVD? I SEARCHE AND COULDN'T FIND ANYTHING. Multiple sources have told me its impossible.
rayulove69 said:
Can I roll back from ZVD? I SEARCHE AND COULDN'T FIND ANYTHING. Multiple sources have told me its impossible.
Click to expand...
Click to collapse
No you can't roll back and if you try anyway you will brick. Theres basically no hope of post zv7 ls997 getting rooted ever
runningnak3d said:
It has been confirmed that If you have the engineering bootloader, AND have a fusing device (which AFAIK all LS997 are), AND install firmware that is ARB 1 or greater, it will brick your phone.
If you are ARB 1 or greater, and install the eng. bootloader -- brick.
When I was doing testing on ARB and the engineering bootloader, I was doing it on a non-fusing device, so my results are null and void.
So, we need a method of unlocking the production bootloader -- and there is, just not the LS997 aboot. It would require flashing either the H915 or US996 aboot, and you can't do that due to ARB.
Unless an engineering aboot leaks that is ARB 1 or an engineering boot leaks that has dm-verity disabled, or a flaw is found in the current aboot, I do not see the LS997 getting root.
EDIT: not trying to keep too much hope alive, but if when Oreo is released, they increment ARB on either the H915 or US996 and DON'T increment it on the LS997, then you would be able to flash either aboot and root....
-- Brian
Click to expand...
Click to collapse
Well, in the words of Gomez Addams -- "Now you've done it!"
Here's what happened. My V20 was running just fine, rooted, with TWRP, on H91810k. I got a notification of an OTA update from T-Mobile.
I'm still a bit unclear on what happened next, but I'm pretty sure I hit the wrong sequence of buttons without even thinking about it. Next thing I know, the phone's rebooting with 10p, but I've lost both TWRP AND my root access!
The only good news is my bootloader's still unlocked, and I still have fastboot capability through ADB. Outside of that, I'm currently stuck with an OS update for which there does not appear to be, at this time, any kind of root exploit. Recowvery doesn't work. I went as far as trying KingRoot, and not even it had any luck (it did, however, file an automatic request with the developers).
The one key problem: Root access is gone. I've tried using fastboot to flash TWRP to the recovery partition, but I keep getting an error which looks like this.
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24188 KB)...
OKAY [ 0.842s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.858s
If I could just get root access back, I'm sure this would work! Once I get TWRP back, it's an easy step to load SuperSU and whatever ROM I want... Arrgh!
I think, next time I see word of an OTA update, I'm going to IGNORE it!
Wish me luck...
UPDATE, same day, 21:29 PDT: I just tried using the pull-the-battery/replace-battery/hold volume up/plug in USB method to try and get the phone into raw upload mode, preparatory to trying to dump 91810j back in. No such luck! Whatever 10p did to these things to lock 'em down, they succeeded!
Hoping someone can find an exploit. It's beyond my meager skill set...
whatever you do, do not go back to 10j or any version < 10p. you will end up with no device
Yeah you screwed the pooch as there is no exploit to root 10p at the moment. You should have been more careful, there's even a 10p zip you could have flashed and kept root.
Yeah, I know...
Still_living714 said:
Yeah you screwed the pooch as there is no exploit to root 10p at the moment. You should have been more careful, there's even a 10p zip you could have flashed and kept root.
Click to expand...
Click to collapse
Which just goes to show I'm still human.
I'm not giving up yet. I'll keep trying KingRoot periodically. Someone's bound to figure out something eventually!
Once I do get TWRP back in, it should be easy enough to flash the de-bloated 10p zip.
Let me know if you figure it out...I'm stuck on 10p with no root or recovery
Theres an efuse bow if u try to root it youll destroy your phones motherboard
pbedard said:
Theres an efuse bow if u try to root it youll destroy your phones motherboard
Click to expand...
Click to collapse
From my understanding, the efuse only blows if you trip the ARB, not from rooting itself. If you try to force a rollback to get root, then yes you will trip the fuse, but it's not root itself that blows the fuse. There's quite a few users who have manually flashed 10p who still have working phones, twrp, and root.
Got it swapped out...
I got exceedingly lucky. T-Mobile allowed me to do an in-warranty swap-out. Got my replacement V20 today, and whaddaya know... It came with 10j! Recowvery, here I come!
And, for the record: I'm not having ANYthing more to do with 10p until (a); A version without anti-rollback is pushed, or (b); A viable root exploit is found. Once bitten twice shy!
Keep the peace(es).
kc7gr said:
I got exceedingly lucky. T-Mobile allowed me to do an in-warranty swap-out. Got my replacement V20 today, and whaddaya know... It came with 10j! Recowvery, here I come!
And, for the record: I'm not having ANYthing more to do with 10p until (a); A version without anti-rollback is pushed, or (b); A viable root exploit is found. Once bitten twice shy!
Keep the peace(es).
Click to expand...
Click to collapse
I might have to do the same thing myself. Mine was purchased certified refurbished from Amazon and came with older firmware, but I stupidly went ahead and installed the OTAs without reading the forums first... Anyways, it's still within the return window. I'll give it until next week to see if someone has a breakthrough on rooting 10p, but otherwise I'll be buying a new one and returning this one as an item that's no longer needed.
After that, maybe I'll send a letter to LG's US headquarters expressing my disappointment with their behavior. I emailed LG tech support about this issue, and they responded back saying they don't know how to enable fastboot either, and that I should send a written letter to LG with my concerns. Maybe if we can get enough people to write letters we'll get the attention of someone there.
Here's the address they gave me:
LG Electronics
P.O. Box 240007,
Huntsville, AL
35824
Resolution Reached...
OK -- The moral of the story, at least to my eyes, is 'Be wary of ANY OTA update, especially if it's for an LG!'
T-Mobile stepped right up to the plate and got my phone swapped out. I've since rooted the replacement, and flashed in texasaggie's stock H91810k image. I've finished replacing my apps, and everything is as it should be.
Despite the hassle, the learning experience was invaluable. I find I'm much more comfortable using TWRP, now, and I have a better understanding of which files affect which part of the phone.
I'm staying away from 10p, or further updates, until one comes along which is not anti-rollback.
Keep the peace(es).
Hello,
So I've had this S7 Edge for a few years, never thought about rooting it until recently when I wanted to download a nice firewall app that requires a rooted phone.
Well, I'm a complete newbie to this, never rooted a phone before, and I've been digging through the forums for a few days trying to figure out how to root this phone. From what I've been seeing, it's much more complicated to root the Verizon variant of this S7 Edge.
From what I understand, the only way to root this phone is to unlock the bootloader. I was researching and figured I had to download ADB, so I did, and I got it working. Using the command prompt on Windows, ADB communicated with the phone successfully. But, before I could continue messing with it further, I tested to see if the Fastboot was working aswell (apparently I'm supposed to have both ADB and Fastboot working). I tried using the Fastboot command to test it. What happened was that it sent my phone into a different screen, but the screen was not the typical bootloader screen that I've been seeing other people get. It was a fairly blank screen with nothing but an android logo with the word "Downloading" in the middle. Typing the "fastboot -devices" command returned no devices. After waiting 5 minutes the screen stayed the same and I just gave up on that part, deciding I should consult the experts here =]. Not sure what I should do next.
I am no expert, by any definition. I used the method described here and it works perfectly for me (SM-G935V). However, if you are on the absolute latest version of Verizon's firmware you might be out of luck- and no, you can not downgrade bootloader versions.
http://https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Hope this helps.
SkylineDriver said:
I am no expert, by any definition. I used the method described here and it works perfectly for me (SM-G935V). However, if you are on the absolute latest version of Verizon's firmware you might be out of luck- and no, you can not downgrade bootloader versions.
http://https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Hope this helps.
Click to expand...
Click to collapse
By latest firmware, does that mean the latest security updates from verizon? Like the ones that automatically pop up on the phone and you can't delay them forever? Well, I could try that link out and see if it works, but I'm scared I'll brick my phone, was hoping for a bit of a step by step guide. Thanks for the suggestion though.
Also may I ask how long ago you used this method for yours?
If you took the latest OTA update from Verizon you are probably out of luck. You will have to check your firmware bootloader version (5th digit from the RIGHT). If is 8 or under you should be able to root using the thread mentioned above. If it is 9 or a letter then you can not root as of right now. As mentioned earlier, you can not downgrade bootloader versions.
FWIW, you can not get any more of a step-by-step guide than what that thread lists. And I have not heard of anyone bricking a S7e using that method- worst case scenario you flash stock and move on.
I have been rooted for at least 9 months now and have not had one issue. Only thing I wish we had was Pie but that will never happen.
SkylineDriver said:
If you took the latest OTA update from Verizon you are probably out of luck. You will have to check your firmware bootloader version (5th digit from the RIGHT). If is 8 or under you should be able to root using the thread mentioned above. If it is 9 or a letter then you can not root as of right now. As mentioned earlier, you can not downgrade bootloader versions.
Click to expand...
Click to collapse
Got sidetracked for a couple months there haha, but I'm still determined to root this thing.
I figured out the bootloader version. It has the letter A (Baseband version: 5th digit from the right).
So now what? This version isn't the latest I don't think. Haven't had an OTA update for months now. Do I cross my fingers hoping someone has a rooting method for this particular Bootloader version?