So I decided to try out the new root that was found. Restored my phone to stock ZV8 then ran the one click. Flashed the Twrp recovery(didn't fail when flashing), and rebooted. Comes up with Secure boot error. So just saying out there that recovery does not work with the new root method.
I wonder if it's related to the bumping process, and that we don't have a truly unlocked bootloader.
That's what I was originally thinking but then I remembered that zv8 uses a newer bootloader than ZV4. So we need . Updated version of TWRP to work with the bootloader.
That's what I was originally thinking but then I remembered that zv8 uses a newer bootloader than ZV4. So we need . Updated version of TWRP to work with the bootloader.
New root method only allows root at ROM level. LG closed the boot loader security flaw in zv8. U have to go back to zv4, stump the ROM then bump for custom recovery.
Fixed
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Related
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
stumcmahan said:
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
Click to expand...
Click to collapse
You need to flash stock recovery, or the OTA won't install. In fact, you might even get stuck in a bootloop as the phone repeatedly boots into TWRP, looking for stock recovery (to install the OTA) and not finding it.
Also, if any system files have been modified by root, you need to return them to "stock" state. Otherwise the OTA will fail to install, saying the system has been modified. You can either return any system files to stock manually, or flash a stock ROM, nandroid, or RUU.
You will lose root when you OTA. But its an easy manner to just flash TWRP again, and flash SU/SuperSU to gain root. Unlocked bootloader is okay for OTA, so you don't even need to relock, unlock again, etc. to flash TWRP. But locked bootloader is required for RUU (unless you have s-off) if you choose that route in the paragraph above.
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
I would check the Verizon LG G3 forums where there are many instances of your questions having been already thoroughly answered.
What you will find is that you must be on v10b firmware, which you can downgrade to using either the .kdz or the .TOT method, then you can root v10b (only) with StumpRoot, or ioRoot, or PurpleDrake, before the phone updates back to v12b. With SuperSu in survival mode root can be retained through either of the current OTA updates (which provide very little enhancement beyond patching root exploits), so far, and with root you can install a specially modified TWRP recovery which will allow the flashing of unsigned kernels and roms.
There. You are on your own from hete on.
Sent from my VS985 4G using Tapatalk
use flashify to install the bumped version of twrp (get it from the original development section). Worked like a charm. Plenty of bumped roms to grab in the dev section.
gothicasshole said:
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
Click to expand...
Click to collapse
There is no unlocking of the bootloader. Bumping doesn't unlock the bootloader. However, it fools the phone into allowing the flashing of custom ROMs and kernels without unlocking the bootloader. Basically, the phone "believes" that whatever is being flashed (via TWRP) is acceptable and allows the image to pass the "security check" that is done when flashing. It's the same thing as IF the bootloader were unlocked, but in reality, it isn't unlocked. It's a security exploit, kind of like rooting this phone is a security exploit.
However, a quick OTA patch from Verizon or LG could make either or both no longer work. In fact, some OTAs have fixed the root exploit on some models, so you have to flash back to a previous version to root.
You have to root first, then you can flash TWRP.
As stated, there are plenty of FAQs in the general G3 section that help explain all of this.
OK thanks guys. Um just used to seeing a sticky on root under original android development I have no idea what firm ware he's running ik how restrictive big red can be at&t is no better but that's why when they offered a nexus I went and grabbed it
He's wanting a lollipop rom
gothicasshole said:
He's wanting a lollipop rom
Click to expand...
Click to collapse
Go here which gives a whole list of things, including how to root, how to bump, how to flash, etc:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
It's where I went before I got this phone to be sure I could do all the things I wanted to.
Thank you
I'll definitely refer him
I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
natec806 said:
I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
Click to expand...
Click to collapse
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Thanks redpoint73. Worked liked a charm
Redpoint -
I used the RUU to update, and now I can't get the SU Binary to update.
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
I'm trying a clean install (wiped cache, dalvik), so I'll see if I can get rid of the original SU app I had installed (chainfire).
Edit: Still can't get rid of SU app.
Any ideas?
DanGeorges said:
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
Click to expand...
Click to collapse
Latest being what number? I would suggest SuperSU 2.46.
redpoint73 said:
Latest being what number? I would suggest SuperSU 2.46.
Click to expand...
Click to collapse
That was, indeed, my problem. I was being directed to an older version of SuperSU update.zip.
Once i grabbed the REAL latest version, it worked like a charm!
Thanks, Redpoint.
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
What is required to run a RUU? I'm completely stock 4.4.4
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
polar2792 said:
What is required to run a RUU? I'm completely stock 4.4.4
Click to expand...
Click to collapse
Backup your personal data (RUU will wipe the phone), and own a PC. That's it. RUU is intended to be run on a stock device, so nothing special is required.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Boudjelal said:
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
Click to expand...
Click to collapse
Are you saying you are still using your AT&T account while living in a foreign country? In that case, you will usually not get the OTA. I think there are a few exceptions, such as roaming in Mexico or Caribbean areas. But otherwise, not OTA.
The RUU method noted above will work anywhere.
Hey Everyone! So i will be receiving my M8 i got used in the mail on monday and i'm doing some research because it is softbricked due to no OS being installed. It is (presumably) S-Off with Bootoader locked and "possibly" no custom recovery. What i'm planning to do is once the battery is charged completely.
-Connect it to my PC (windows)
-Power into fastboot
-Run the stock AT&T RUU and get everything running and up to date.
From there i will be unlocking the bootloader, custom recovery, root, and all the good stuff.
I'm just wanting to know from the way more knowledgeable folks then i when it comes to this stuff, is if this is the proper procedure. Is there anything else i should do first or after? Any help will be great! I'll know more tomorrow night on if recovery is installed or not, but i'm going with the opinion that there is no custom recovery, as i feel this would be harder.
any help would be GREATLY appreciated!
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
redpoint73 said:
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
Click to expand...
Click to collapse
Thank you so much Redpoint! I only have a small amount of knowledge with this area. I've sideloaded an OS over ADB due to a mistake i made with no OS on an old tablet, but never had to deal with possibly stock recovery with a locked bootloader, so knowing my approach will presumably work is a real relief.
Thank you again!!!:good::fingers-crossed: