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).
Related
It has come to light that a new update has been released for the Prime version stock ROM. This update is called V6.6 (duh), and the update replaces the preloader. Some people have reported bootloops, one has gotten a brick, and I am all but certain that Amazon is trying to patch the preloader to remove any chance of rooting or converting to OEM ever again. It also replaces the boot image, which we believe is a way to re-lock the bootloader, or possibly even make fastboot ignore the unlocked status. This could also destroy your ability to root, run TWRP, or run any custom ROM ever again. If you are on the Prime stock ROM, DO NOT take the OTA to V6.6. It's really not worth it for the security patch. I also encourage all users of V6.1, V6.4, or V6.5 to go ahead and convert your phone to the non-Prime variant while you have the chance. Amazon is known for jamming updates down people's throats so I would not be surprised if they have a way of installing that update without your approval.
The conversion guide is here: http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
There is some discussion about the OTA in the last few pages of the general discussion thread here: http://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-t3418354/post68565531#post68565531
We can use this thread to further dissect and discuss the update.
The boot img can lock the Bootloader.
Thanks for the warning. I would have taken it as I think V6.5 was a good update and improved performance (at the expense of battery life).
DarkBlood. said:
The boot img can lock the Bootloader.
Click to expand...
Click to collapse
No, but some kernel/ramdisk shenanigans could lock it at boot.
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
With the fire tablet they disabled the preloader and changed the pid
ColtonDRG said:
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
Click to expand...
Click to collapse
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
DarkBlood. said:
With the fire tablet they disabled the preloader and changed the pid
Click to expand...
Click to collapse
You cannot simply "disable" the preloader. We discussed what exactly Amazon did with the Fire a little bit in the private hangout the other day. The bottom line is that we still don't know exactly what shenanigans Amazon is up to, or what tricks they have up their sleeve. Knowing Amazon, it can't be good for us.
jacewt said:
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
Click to expand...
Click to collapse
It has the August security patch and some things that lock things down. Nothing else that I'm aware of.
bionictoothpick said:
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
Click to expand...
Click to collapse
If you unlocked your bootloader (fastboot style) via one of the methods before, you should still be able to gain root. If not, you are probably hosed, at least for now. Weather or not you will end up regretting that is up to you, but I certainly would.
kal250 said:
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
Click to expand...
Click to collapse
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
ColtonDRG said:
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
Click to expand...
Click to collapse
Fortunately, I had OTA blocked and as I said the other day when i get downtime(hopefully Sunday), I'm back to OEM, to hell with security patches!!
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
The zip is available in https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
Go for it, but I'm not interested in taking any of Amazon's **** either way.
As @DarkBlood. said, the zip file is mirrored on https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
ariesgodofwar said:
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
Click to expand...
Click to collapse
A handful of people around here actually got their phone bootlooped just after taking the upgrade straight from 6.5 to 6.6. At first I figured it was a fluke because their phones were altered, but at this point it's getting very suspicious (almost like it's a hit or miss thing for everyone, even those that haven't touched anything). I hope this doesn't damage the device's reputation too bad, and Amazon better get their **** together. Chopping off their nose in spite of their face. I guess I shouldn't be surprised at this point. This is Amazon we're talking about here.
bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
If the zip can be modified, can we inject the 6.1 preloader and bootloader into the 6.6 OTA and modify it to run over current 6.6 installs allowing those who have been locked to at least unlock themselves?? I'm not savy enough to try....
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!
LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.
V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.
Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT="]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk
Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT="]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.
Can someone run this:
Code:
fastboot getvar all
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable
PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).
Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.
acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable
PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.
Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
vijn said:
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
Click to expand...
Click to collapse
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Tarima said:
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Click to expand...
Click to collapse
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
vijn said:
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
Click to expand...
Click to collapse
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Tarima said:
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Click to expand...
Click to collapse
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
vijn said:
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
Click to expand...
Click to collapse
I use Magisk myself. I prefer it to flashing the classic supersu for root.
Install latest twrp (make sure its the latest twrp for the 10), then flash Magisk. Then install Magisk manager app. As simple as that.
Read the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You rock man. Thanks for all the help.
vijn said:
You rock man. Thanks for all the help.
Click to expand...
Click to collapse
No worries, glad it worked.