Any help or guidance will be appreciated.
I just got a replacement phone from Verizon with 46A and these are the steps i followed to try and restore a stock rooted lollipop rom from my old phone.
-flashed to 10B by TOT method
-rooted with Stump
-downloaded TWRP from play store
-flashed and got to TWRP recovery successfully
-created a new backup with just the boot.img
-placed the old nandroid backup in that folder
-wiped cache and dalvik/art
-flashed XDABBEB's VS985 24B bootstack
-restored my nandroid backup
...and then i kept getting a "secure boot error" at startup. Boot verification error. I could only get onto TWRP and download mode. I don't know what i did wrong. I looked through this forum for solutions but couldn't find any. So long story short, i ended up flashing back to 10B via TOT method. Any solutions to restore my old backup?
also another strange thing was when i moved my old backup to the new folder, it wouldn't show the checkboxes for boot, data, system etc to restore. i had to place the old backup in the same folder with the boot.img and i had to copy and replace it with the old backup for it to show when trying to restore it.
Hi! Please in the future don't post the same question in two different threads. Since your other post in the toolkit thread didn't mention you having actually used the toolkit, here was the appropriate place to post it so I'll answer this one. I can't keep track so if your previous questions when I gave you advice were in the toolkit thread, it would've been fine to only post this question in that thread instead of making a new post. Obviously, if you didn't use the toolkit at all then this post here would be the more appropriate place.
You could wipe, re-flash the 24B Bootstack, flash whatever ROM (presuming Android 5.0.1 since you determined the 24B Bootstack was the correct one) it was you were using (the same one the TWRP backup was of), then restore only the data partition from the TWRP backup.
The other thing isn't necessarily strange although the way you explain it is confusing, so depending on what you mean.
i.e. This is an example of the folder structure of what I meant in whatever the original thread where you asked and I gave you my advice.
Original phone, original TWRP backup:
External MicroSD card:
TWRP/BACKUPS/VS985q34134pdygf/2016-04-06--11-43-58_MRA58K (random letters and numbers after the VS985)
New phone, new TWRP backup:
TWRP/BACKUPS/VS985adf346zdldd/2016-05-11--09-58-00_MRA58K (different set of random letters and numbers after the VS985 because of the new phone)
On the new phone, move your original backup folder "2016-04-06--11-43-58_MRA58K" from "TWRP/BACKUPS/VS985q34134pdygf/" to the new backup folder "TWRP/BACKUPS/VS985adf346zdldd/". The purpose of creating the new small backup of just your kernel (boot.img) or anything was just to create the new "VS985adf346zdldd" folder.
So now you'd have:
TWRP/BACKUPS/VS985q34134pdygf/ (empty folder)
TWRP/BACKUPS/VS985adf346zdldd/2016-05-11--09-58-00_MRA58K (new small backup)
TWRP/BACKUPS/VS985adf346zdldd/2016-04-06--11-43-58_MRA58K (your original TWRP backup from your old phone)
From there, you should be able to flash the 24B Bootstack and restore the "2016-04-06--11-43-58_MRA58K" backup.
I hope that clears things up.
Thanks for your response. My apologies regarding the double posting. I wasn't sure if you saw the questions i asked yesterday so i just needed some assistance.
So just wipe, flash the bootstack again and just restore the data? I will do that now. I just wasn't sure if it was the bootstack causing the issue or my backup. Some one mention the oversharpening mod. would that help or no?
Regarding the TWRP backup structure. I did what you did last night regarding placing the old backup in that folder but when i went to restore it, it didn't have any partitions to select. It wasn't until I copied the old backup to the exact location and overwrote the new and copied/replace the boot.img with the one from my old backup. then i was able to select the partitions. It was strange to me too. i didn't know if that caused the issue either.
soulfulb said:
Thanks for your response. My apologies regarding the double posting. I wasn't sure if you saw the questions i asked yesterday so i just needed some assistance.
Click to expand...
Click to collapse
You're welcome!
I can't speak as to others but most of the time when I check the forum, I check all the Verizon G3 sections to see if there's anything new anywhere. I probably won't see a post in a CM or a CM-based ROM thread, but probably everywhere else.
So just wipe, flash the bootstack again and just restore the data?
Click to expand...
Click to collapse
No. Wipe Cache, Dalvik/ART and Data, flash the bootstack, flash the original ROM zip that matches what you were running when you made the original TWRP backup, then restore the TWRP backup of only the Data partition.
I will do that now. I just wasn't sure if it was the bootstack causing the issue or my backup.
Click to expand...
Click to collapse
Unable to tell what's causing the issue but to paraphrase House M.D. "It's never the Bootstack."
Some one mention the oversharpening mod. would that help or no?
Click to expand...
Click to collapse
Help with what specifically? Help with the problem you're having booting the ROM you restore from the TWRP Backup? No. Help with oversharpening? Maybe. I've never felt a need to bother with it. I'd worry about getting your system working at all first, then think about additional modifications. Just do a new backup before any further modifications, once it's running fine.
Regarding the TWRP backup structure. I did what you did last night regarding placing the old backup in that folder but when i went to restore it, it didn't have any partitions to select. It wasn't until I copied the old backup to the exact location and overwrote the new and copied/replace the boot.img with the one from my old backup. then i was able to select the partitions. It was strange to me too. i didn't know if that caused the issue either.
Click to expand...
Click to collapse
Strange but I wouldn't think too much about it - as long as you found a way which worked for the partitions to show up. If I was there and could see everything it's possible I could figure out what happened. I don't know if you knew, but you can take screenshots in TWRP. Then, of course, you could mount your phone to the PC via USB with TWRP's mount menu to transfer the screenshots. Just out of curiosity, which TWRP did you install? 2.8.7.0 or 3.0.0? And which did you make the original backup in on your old phone? Either works fine but just in case ther was some kind of small change in behavior that I'm not aware of yet...
Also, what precise ROM were you running when you made the old TWRP backup?
roirraW "edor" ehT said:
You're welcome!
I can't speak as to others but most of the time when I check the forum, I check all the Verizon G3 sections to see if there's anything new anywhere. I probably won't see a post in a CM or a CM-based ROM thread, but probably everywhere else.
No. Wipe Cache, Dalvik/ART and Data, flash the bootstack, flash the original ROM zip that matches what you were running when you made the original TWRP backup, then restore the TWRP backup of only the Data partition.
Unable to tell what's causing the issue but to paraphrase House M.D. "It's never the Bootstack."
Help with what specifically? Help with the problem you're having booting the ROM you restore from the TWRP Backup? No. Help with oversharpening? Maybe. I've never felt a need to bother with it. I'd worry about getting your system working at all first, then think about additional modifications. Just do a new backup before any further modifications, once it's running fine.
Strange but I wouldn't think too much about it - as long as you found a way which worked for the partitions to show up. If I was there and could see everything it's possible I could figure out what happened. I don't know if you knew, but you can take screenshots in TWRP. Then, of course, you could mount your phone to the PC via USB with TWRP's mount menu to transfer the screenshots. Just out of curiosity, which TWRP did you install? 2.8.7.0 or 3.0.0? And which did you make the original backup in on your old phone? Either works fine but just in case ther was some kind of small change in behavior that I'm not aware of yet...
Also, what precise ROM were you running when you made the old TWRP backup?
Click to expand...
Click to collapse
Thanks again.
I'm on 2.8.6.0. Should i uninstall and do 2.8.7? Is there a way to tell what my backup was on? Sorry i don't know off hand.
I know i''ve been a bit of a bug, but which/where can i find/should i flash 24b rom ? i was looking through and only saw the jasmine but i just wanted to flash the stock.
i'm at work now but when i get home i will try again and if errors show, i will mount and upload the screenshots.
roirraW "edor" ehT said:
Also, what precise ROM were you running when you made the old TWRP backup?
Click to expand...
Click to collapse
Stock 24c rom
soulfulb said:
Thanks again.
I'm on 2.8.6.0. Should i uninstall and do 2.8.7? Is there a way to tell what my backup was on? Sorry i don't know off hand.
I know i''ve been a bit of a bug, but which/where can i find/should i flash 24b rom ? i was looking through and only saw the jasmine but i just wanted to flash the stock.
i'm at work now but when i get home i will try again and if errors show, i will mount and upload the screenshots.
Click to expand...
Click to collapse
You're welcome!
You don't have to uninstall anything. Just download 2.8.7.0 (or 3.0.0) and flash it from inside your current TWRP. Don't know if that would've necessarily caused a problem, though.
JasmineROM 8.x is the closest you're going to get to completely stock 24B. In the case of JasmineROM and SkyDragon, ALWAYS flash the Bootstack AFTER flashing the ROM. It won't hurt if you flash any bootstack before flashing either ROM, but you MUST flash the bootstack after flashing the ROM. This most especially pertains to 35B of both ROMs, but might as well just get used to it on any version of those two ROMs.
You can also always upload the TWRP log although it doesn't sound like you're having a problem actually flashing or restoring anything. I mainly meant for showing the organization of the TWRP backup files, you could've used screenshots but I doubt if that's an issue so I wouldn't worry about that.
I hope you don't mind me adding that 35B runs a lot better than 24B or 23C. You can always use the built-in LG Backup to backup your user apps, user data and limited system data, to move between different versions of Android on stock LG ROMs. @xdabbeb 's VS985 v2.0.0 in particular is the schnitzel.
roirraW "edor" ehT said:
You're welcome!
You don't have to uninstall anything. Just download 2.8.7.0 (or 3.0.0) and flash it from inside your current TWRP. Don't know if that would've necessarily caused a problem, though.
JasmineROM 8.x is the closest you're going to get to completely stock 24B. In the case of JasmineROM and SkyDragon, ALWAYS flash the Bootstack AFTER flashing the ROM. It won't hurt if you flash any bootstack before flashing either ROM, but you MUST flash the bootstack after flashing the ROM. This most especially pertains to 35B of both ROMs, but might as well just get used to it on any version of those two ROMs.
You can also always upload the TWRP log although it doesn't sound like you're having a problem actually flashing or restoring anything. I mainly meant for showing the organization of the TWRP backup files, you could've used screenshots but I doubt if that's an issue so I wouldn't worry about that.
I hope you don't mind me adding that 35B runs a lot better than 24B or 23C. You can always use the built-in LG Backup to backup your user apps, user data and limited system data, to move between different versions of Android on stock LG ROMs. @xdabbeb 's VS985 v2.0.0 in particular is the schnitzel.
Click to expand...
Click to collapse
Thanks to you I just was able to restore my backup! I followed your steps and flash jasmine, then the bootstack, and then my backup data only and boom....back in service.
I can't thank you enough. I was nervous yesterday, but much relieved now.
In the future, lg backup would be my best option if i wanted to save my apps and data and switch to a newer rom (ie xdabbeb, 46a)?
soulfulb said:
Thanks to you I just was able to restore my backup! I followed your steps and flash jasmine, then the bootstack, and then my backup data only and boom....back in service.
I can't thank you enough. I was nervous yesterday, but much relieved now.
Click to expand...
Click to collapse
Awesome! Nothing makes me happier on XDA than to hear everything went as planned and it works.
In the future, lg backup would be my best option if i wanted to save my apps and data and switch to a newer rom (ie xdabbeb, 46a)?
Click to expand...
Click to collapse
Absolutely, in my opinion yes. LG Backup has a small quirk or two but it works so fast and painless. It can't replace TB completely but for the usual work of just backing up and restoring your user apps/data and just a little bit of system data I think it's far superior an experience.
If I move away from LG whenever I upgrade then I sure will miss LG Backup.
Related
EDIT 3/30: This problem should be solved with the updated version of CWR found here: http://forum.xda-developers.com/showthread.php?t=1017817
Remember that until devs start bundling it with their roms, you will need to flash it after you flash a new ROM. (Superclean 2.9.2 and before includes the broken recovery).
The problem was in the fact that cwr didn't have root access. The updated one now contains this fix.
If you are trying to restore a nandroid from an old backup, you might have issues. I'll try to see about this scenario to see the easiest way to do it (the steps from the previous post in this thread should work.)
Also, it looks like dbdata doesn't auto-mount, so you need to go into the mount menu and mount it before being able to run the fix_permissions script, if you want to run that.
I think I got it fixed so that it will auto-mount it in the script, but it won't be recompiled until JT does it.
Original thread:
Info and links:
http://forum.androidcentral.com/ver...s/72212-warning-trouble-nandroid-backups.html
http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/72185-3-days-hell.html
This seems to explain a lot of the issues people have been having. Probably best to check that thread for updated info, but copying and pasting for those who are other forum-phobic:
Landshark said:
Do not try to restore a themed nandroid backup for the time being!!
DroidXcon has done a great job of putting together the thread about clockworkmod recovery (cwm), how to install it, use it, and how to fix permissions since that is not working in cwm right now. That is not the only thing not working in cwm right now. Right now you are also unable to wipe battery stats and restore a nandroid backup that includes a theme through cwm. What is a nandroid backup? Well you can check out posts 6, 7, & 8 of DroidXcon's clockwork mod thread for a detailed description with visual aids:
DroidXcon's Clockwork Thread Here
The problem seems to stem from not being able to fix permissions in cwm. If you read DroidXcon's thread it should make more sense and I can only do an injustice to his work by trying to explain it here myself. Bottom line is like I said above we are unable to successfully restore nandroid backups that include a theme at this time without ending up in a force close loop of hell (FCLOH) at boot animation, a.k.a. boot loop. Jaekar99, Suicide Shift, and I have been working at this for some time without any solution. We have only been able to successfully restore a nandroid backup of only the base ROM. Which is basically pointless since in basically the same amount of time it takes to restore a nandroid backup of just the base ROM, I can boot into cwm, flash the base ROM, reboot, boot into cwm, wipe cache and dalvik, flash a theme, reboot, boot to cwm, wipe cache and dalvik, flash a patch or two, and reboot my phone.
There is also a problem trying to flash a ROM and a theme in the same cwm session. Doing so will almost certainly put you into a FCLOH at boot. Best advice is as always try to only flash ROMs when your battery is at or near 100%. I have also had fewer problems when I flash while my phone is plugged in, either to an outlet, or into the usb on my computer. In addition to that, you will have fewer problems, if any, flashing the ROM by itself, rebooting, booting back into cwm, wiping cache and dalvik cache, flashing a theme if you want one, rebooting, booting back into cwm, then flashing any additional patches or mods, then rebooting. I know that is a lot of steps to take, but it's better than the alternative, which is ending up in a FCLOH, THEN having to take all those steps. You know, it's that whole ounce of prevention thing.......
For more information about flashing themes, patches, mods, and boot animations, you can get great information in Jaekar99's Themes, ROMs, Kernels, Boot Animations thread. I believe he is also covering some of this warning material in an effort to get it to as many people as we can.
Jaekar99's Themes Thread Here
So for the time being, do not try to restore a themed nandroid backup through cwm. If you have already created nandroid backups in cwm, I would think you can just leave them there for when we figure out a solution or fixing permissions gets repaired in cwm.
Any questions about this, you can usually find Jaekar99, Suicide Shift, or me here in the forums. Post your questions here and we'll do our best to answer them. I will also keep this updated with any new information or results of what we are testing. Thank you, and sorry to anyone who ended up in a FCLOH because I didn't get this information out sooner. (davey11)
Also for instructions on how to wipe battery stats since it can't be done in cwm, check out Gunnermike53's [How to] [Discussion] Improve Battery Life thread. It also involves commands entered in Terminal Emulator.
Gunnermike53's Battery Life Thread Here
And let's get one more plug in here. If any of this terminology is confusing to you, or you are new to rooting and want a great guide to get you started and better informed, check out Sheepdog Elite's [How to] First time rooting walk-through.
Sheepdog Elite's First Time Rooting Thread Here
Click to expand...
Click to collapse
There is a workaround in process of being written up.
The workaround is to reflash your theme over the nandroid once you get the restore finished. It's been mentioned that after a few days some one had it go bad that way, but it's what we've got for now.
Thanks GizmoDroid,
I was going to post the same info here when I woke up this morning. A group of us over at AC were up til the wee hours working on solutions and I was falling asleep at the keyboard. I'm trying to be more active over here and will update my OP at AC and this thread here.
For now a solution that gets you past the FCLOH is to boot back into cwm and flash whatever theme you have in the nandroid. That will get you past the FCLOH, but some patches and mods are being overwritten by doing that. So far, Adrynalyne's nuance patch stayed, but the mod settings patch did not. We are still working on other possible solutions. For now, other than doing this testing, I am not even bothering with nandroid backups as I can boot to cwm, flash ROM, reboot, boot to cwm, wipe cache & dalvik, flash theme, reboot, boot to cwm, wipe, flash patches and mods, and reboot all in about the same amount of time it takes to safely restore a nandroid of just the base ROM to avoid the FCLOH.
Right now I am going to see if restoring a nandroid, then flashing the theme in the same cwm session avoids the FCLOH.
Result of latest test - PASS
So flashing the theme over the nandroid restore in the same cwm session resulted in a clean reboot with no FCBLOH (Added in the B for Boot -Force Close Boot Loop of Hell.) Same problem as before though as Adrynalyne's settings mod was overwritten by the theme. So while this takes care of the FCBLOH problem, but it involves extra steps. Which like I said before kind of defeats the purpose of having a nandroid backup to restore - creating a complete build you can then restore all at once instead of having to do it piecemeal. Well at least for now there is a way to get around the FCBLOH when restoring a themed nandroid backup. Thanks Sheepdog Elite for all the help and for finding this workaround. Everyone just remember if you use this workaround and have any additional patches or mods included in your themed nandroid backup, after you restore check to see if all of your mods and patches are still in place.
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
GizmoDroid said:
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
Click to expand...
Click to collapse
Thank you sir. I will pass this along and see what we can find out.
landshark68 said:
Thank you sir. I will pass this along and see what we can find out.
Click to expand...
Click to collapse
Actually, after some preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
GizmoDroid said:
Actually, after some from preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
Click to expand...
Click to collapse
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
JaeKar99 said:
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
Click to expand...
Click to collapse
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
landshark68 said:
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
Click to expand...
Click to collapse
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what I did to fix it.
Nandroid backed-up a themed install.
Nandroid restored same themed install.
Rebooted.
Eternal bootloop ensued.
Rebooted to CWM.
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
Did some other stuff
Rebooted and was greeted with a successfully working phone!
Now, I did some other things too, so I'm not sure if this was the only thing it needed. If this is all it was, then it should be an easy CWM fix. Someone want to try that and let me know?
If that's not it, I'll tell you the other things I did. It's got to be one of them
Things to remember: nandroid doesn't back up your kernel or modem at this time. If you try to restore an nandroid backup with an incompatible kernel or modem, you will have problems. Flash these first.
GizmoDroid said:
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what did it.
Here's what I think I did:
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
If this is what did it, then it should be an easy CWM fix. Someone want to try that and let me know? If that's not it, I'll tell you the other things I did. It's got to be one of them
Click to expand...
Click to collapse
I will try it and let you know.
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
landshark68 said:
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
Click to expand...
Click to collapse
Nothing happened... at all? Like it just went back to the prompt without saying anything?
If that's the case, we have bigger fish to fry, because it should have at the very least complained or showed some text.
GizmoDroid said:
Nothing happened... at all?
Click to expand...
Click to collapse
Never mind. Jut took a while for it to start rolling in adb. stand by for results.
Boot loop city
landshark68 said:
Boot loop city
Click to expand...
Click to collapse
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
GizmoDroid said:
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
Click to expand...
Click to collapse
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Actually, hold off a second. I just redid the steps myself, and that wasn't all of the commands needed, apparently.
Before you jump through a bunch of hopes again, let me try some stuff.
landshark68 said:
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Click to expand...
Click to collapse
Ya, best bet would be to start clean, flash ROM and theme, nandroid backup, nandroid restore, then do the manual nandroid restore from adb. Try to eliminate all the variables.
If that's not it, then it had to be some funky mounting stuff I was doing. But I'd rather not get into that if I don't have to, because I tried a bunch of stuff all at once.
Standing by. I just made a build of sc 2.9.2v and ultimate honeycomb 3.1.1. I'll make a nandroid backup of that while waiting.
ETA - And don't worry about the appearance of being facetious or hurting my feelings or insulting me. I'm a grown person with thick skin. And I've read a bunch of your posts and have the same mind set. Don't insult, but tell it exactly like it is.
First - want to thank ALL THE DEVs that put in who knows how much time and effort to make us users happy!!!
My phone:
LG G3 running android 5.0.1 on VZW
Build: LRX21Y
Software Version: VS985 23C
I got this phone off Ebay, as I wanted to keep the unlimited data plan through VZW and also wanted a more updated phone that could be rooted. I am replacing a Razr HD that I had rooted, but that phone was so underpowered it was crazy. Anyhow, I gathered all the root methods and tried to make sense of it all; apparently there has been an explosion of smartphones over the last few years.......... First two days I thought this phone could not be rooted, but I started to see some important parts in these forums related to build numbers, software versions, and android versions, and what root methods seemed to work best, or not at all. What eventually worked for me was getting the right USB drivers for the LG G3 for my Win-7 system. The older driver actually worked for me, the LG VZW United WHQL v2.14.1 - I was then able to at least get the One-Click root to see my device, but I did have to connect/reconnect a few times, and also had to do this procedure twice - the first time the device rebooted back to login and not the download mode. I saw where some were saying you needed to switch between PTP an MTP, but I found that once you found the right one (Think that was MTP) you could just disconnect the USB and reconnect. After the second reboot using One-Click root, the device did go into the download mode and finished the root process. Did a root verification and that confirmed the phone is rooted properly.
I swapped the SIM this morning into the LG G3 and powered on and still have root; however, Verizon is bugging me to update the system software and I am delaying that until I get some clarity on WHAT is getting upgraded, and if I will still have root afterwards (I'm thinking probably not), or if there is a way to "protect" the root I currently have on the device before I do the system upgrade from VZW.
I was hoping someone(s) here who understand more about the VZW upgrades and how that affects root on the LG G3s. THANKS!!!
Kevin
Hi Kevin. Good name (mine too)!
Welcome to the Verizon LG G3 section!
1. The update is 24B, which fixes a few important problems with 23C. Personally, I recommend it.
2. First, since you're rooted, trying to apply the 24B OTA will fail because it'll recognize that your system partition is changed.
3. The easiest way for you to keep root and yet be on 24B is to:
a. Use LG Backup in Settings/Backup & Reset to back all of your data and system settings to an external MicroSD card.
b. Search the Play Store for:
Code:
autorec VS985
This'll install TWRP v2.8.6.x for you. Then update to 2.8.7.0 using a TWRP flashable zip available in the non-variant specific Developement or non-Development subsection - I forget which - of the LG G3 forum.
c. Make a TWRP nandroid backup of your current setup.
d. You can try dirty flashing JasmineROM 8.0 to get updated to 24B, be nearly completely stock as it just adds a few conveniences unless you flash other stuff after. If dirty flashing didn't work well, wipe Data, System, Cache & Dalvik, flash JasmineROM 8.0 then once booted use LG Backup to restore the backup you made in step a above.
kd1966 said:
First - want to thank ALL THE DEVs that put in who knows how much time and effort to make us users happy!!!
My phone:
LG G3 running android 5.0.1 on VZW
Build: LRX21Y
Software Version: VS985 23C
I got this phone off Ebay, as I wanted to keep the unlimited data plan through VZW and also wanted a more updated phone that could be rooted. I am replacing a Razr HD that I had rooted, but that phone was so underpowered it was crazy.
Click to expand...
Click to collapse
Welcome Kevin to the world of the G3. You won't be disappointed. I myself also came from the Razr HD and mine was unlocked (bootloader exploit before it was patched). But the G3 is worlds above the Razr HD (which still was one of my favorites phones).
As @roirraW "edor" ehT stated, you have a couple of options, but I will say, Jasmine ROM with the SkyDragon 4.2 kernel is great. You are still using the stock image which is what I prefer due to the stock camera that comes with it. Anything else (Google camera, AOSP camera) just pales in comparison to the G3 stock camera.
If you do decide to just flash the Jasmine ROM, then you can do as roirraW stated which is to install the autorec VS985 app which will do all that is necessary to get you up and running with TWRP which will allow you flash custom kernels and ROMs (very similar to having an unlocked bootloader). Once you have TWRP, you can go and download the latest Jasmine ROM and then the SkyDragon kernel. Here are the links to the ROM and the kernel (the kernel gives even better battery savings):
Jasmine ROM 5.0: http://forum.xda-developers.com/showpost.php?p=61844561&postcount=4128
SkyDragon Kernel 4.2: https://www.androidfilehost.com/?fid=24052804347775438
Then do the following:
Run the autorec VS985 app (if not already done) to install TWRP
Copy the Jasmine ROM and SkyDragon kernel files to your external SD card (or internal if you don't have an external SD card installed)
Use either LG Backup or TitaniumBackup and backup all of your downloaded apps and settings.
Backup anything located on the internal SD card (photos, music, etc). This will get wiped later on.
Boot into TWRP (download Quick Boot app from Play Store and select "Recovery" in the app. Much easier this way)
Wipe system, data, cache and dalvic. You don't need to wipe internal which would wipe your internal SD card as well as the internal memory.
Flash the Jasmine ROM. This takes some time and it may appear to be doing nothing. Mine took about 5 minutes, so be patient.
If you want to debloat some of the stock apps, you can download and flash the debloating zip from the Jasmine ROM thread I linked you to but it's not necessary. You can also do it later on if you wish.
Reboot into the ROM. Be patient. It sits at the LG logo for awhile and it may appear hung, but it's not. Give it about 5 minutes.
Go to settings and do a factory reset. This needs to be done within the ROM. This WILL wipe your internal SD card, but you should have backed up anything important as stated in step 4 above.
Reboot again and profit in the glory of Jasmine ROM. Now you can use Quick Boot to boot back into recovery (TWRP) and flash the SkyDragon kernel.
Now really profit in performance and battery life that you won't get with pure stock 24B.
roirraW "edor" ehT said:
Hi Kevin. Good name (mine too)!
Welcome to the Verizon LG G3 section!
1. The update is 24B, which fixes a few important problems with 23C. Personally, I recommend it.
2. First, since you're rooted, trying to apply the 24B OTA will fail because it'll recognize that your system partition is changed.
3. The easiest way for you to keep root and yet be on 24B is to:
a. Use LG Backup in Settings/Backup & Reset to back all of your data and system settings to an external MicroSD card.
b. Search the Play Store for:
Code:
autorec VS985
This'll install TWRP v2.8.6.x for you. Then update to 2.8.7.0 using a TWRP flashable zip available in the non-variant specific Developement or non-Development subsection - I forget which - of the LG G3 forum.
c. Make a TWRP nandroid backup of your current setup.
d. You can try dirty flashing JasmineROM 8.0 to get updated to 24B, be nearly completely stock as it just adds a few conveniences unless you flash other stuff after. If dirty flashing didn't work well, wipe Data, System, Cache & Dalvik, flash JasmineROM 8.0 then once booted use LG Backup to restore the backup you made in step a above.
Click to expand...
Click to collapse
Thank you! I appreciate the tips and technical stuff. I've been catching bits here and there about this TWRP, and it seems there are a lot of people that are having issues with it, for whatever reasons. I was thinking that I might not need it unless I wanted to flash to a custom ROM, which I have not done, as I'm not sure how that would work on my carrier (VZW), or if that even matters. Again, I really appreciate the info and I will definitely do some more reading/studying what I need to do next; that would be pretty cool if I could keep root and still have the 24B.
Kevin
kd1966 said:
Thank you! I appreciate the tips and technical stuff. I've been catching bits here and there about this TWRP, and it seems there are a lot of people that are having issues with it, for whatever reasons. I was thinking that I might not need it unless I wanted to flash to a custom ROM, which I have not done, as I'm not sure how that would work on my carrier (VZW), or if that even matters. Again, I really appreciate the info and I will definitely do some more reading/studying what I need to do next; that would be pretty cool if I could keep root and still have the 24B.
Kevin
Click to expand...
Click to collapse
Well, you can definitely keep root on 24B, but probably the main reason people are having issues with TWRP is they are trying to use it incorrectly on LP. That's why the app riorraW suggested will take care of ensuring your phone is set up correctly to use TWRP, even on 24B. But, as I stated, if you are going to run 24B, I would suggest going to Jasmine ROM and then use the SkyDragon kernel. You'll get much better battery life out of it. I can attest to that.
In any case, welcome once again to the G3 family.
Thx for the welcome and great info!
iBolski said:
Welcome Kevin to the world of the G3. You won't be disappointed. I myself also came from the Razr HD and mine was unlocked (bootloader exploit before it was patched). But the G3 is worlds above the Razr HD (which still was one of my favorites phones).
As @roirraW "edor" ehT stated, you have a couple of options, but I will say, Jasmine ROM with the SkyDragon 4.2 kernel is great. You are still using the stock image which is what I prefer due to the stock camera that comes with it. Anything else (Google camera, AOSP camera) just pales in comparison to the G3 stock camera.
If you do decide to just flash the Jasmine ROM, then you can do as roirraW stated which is to install the autorec VS985 app which will do all that is necessary to get you up and running with TWRP which will allow you flash custom kernels and ROMs (very similar to having an unlocked bootloader). Once you have TWRP, you can go and download the latest Jasmine ROM and then the SkyDragon kernel. Here are the links to the ROM and the kernel (the kernel gives even better battery savings):
Jasmine ROM 5.0: http://forum.xda-developers.com/showpost.php?p=61844561&postcount=4128
SkyDragon Kernel 4.2: https://www.androidfilehost.com/?fid=24052804347775438
Then do the following:
Run the autorec VS985 app (if not already done) to install TWRP
Copy the Jasmine ROM and SkyDragon kernel files to your external SD card (or internal if you don't have an external SD card installed)
Use either LG Backup or TitaniumBackup and backup all of your downloaded apps and settings.
Backup anything located on the internal SD card (photos, music, etc). This will get wiped later on.
Boot into TWRP (download Quick Boot app from Play Store and select "Recovery" in the app. Much easier this way)
Wipe system, data, cache and dalvic. You don't need to wipe internal which would wipe your internal SD card as well as the internal memory.
Flash the Jasmine ROM. This takes some time and it may appear to be doing nothing. Mine took about 5 minutes, so be patient.
If you want to debloat some of the stock apps, you can download and flash the debloating zip from the Jasmine ROM thread I linked you to but it's not necessary. You can also do it later on if you wish.
Reboot into the ROM. Be patient. It sits at the LG logo for awhile and it may appear hung, but it's not. Give it about 5 minutes.
Go to settings and do a factory reset. This needs to be done within the ROM. This WILL wipe your internal SD card, but you should have backed up anything important as stated in step 4 above.
Reboot again and profit in the glory of Jasmine ROM. Now you can use Quick Boot to boot back into recovery (TWRP) and flash the SkyDragon kernel.
Now really profit in performance and battery life that you won't get with pure stock 24B.
Click to expand...
Click to collapse
I must say that these rooting and root protection procedures have gotten extremely complex..... but that's technology I suppose. Thank you very much for the well documented steps, which I will definitely take serious look at as I piece together my own plan. I don't seem to have too much issues with the stock rooting, but when it comes to the flashing stuff, I get a little hesitant; I just don't want to make the wrong move and wind up with a paperweight......
Gotta say that my old RazrHD was by far my most well liked smartphone device; I started on a DroidX, then the X2, and finally the RazrHD. I'm moving away from the "Moto" devices cuz they seem to be going the way of Apple - you can't add SD storage cards; you get what they give you and I don't like that. I think they are trying to push you into cloud storage or something. As for my new best, awesome smartphone device................ the LG G3 is pretty damn awesome, considering there is a G4 model out there.
Kevin
Okay guys I need some help here. VS985 was running TWRP 3.0.0-0, with latest cm nightly. The phone began running very slow and hot. In the attempt to update to another newer nightly, the install in TWRP just causes recovery to restart itself. This happens no matter what I attempt to flash. Making a backup also never progresses past the start. At this point I could still boot into the rom, but now nothing was working right... couldn't open most apps or download anything. I flashed twrp again in twrp as an .img just to see if that fixed it and obviously it did not, I also tried to flash CM Recovery but it failed. I took everything I needed off of the phone and then wiped the phone- system/data/cache but still could not flash a rom or anything so currently I have no OS, I have access to Firmware Update mode (download mode i think?) and my messed up TWRP. What should I try next? My guess is to use LG Flash Tool and start from scratch? I'm having trouble gathering all of those resources... thanks for the help friends!
-bschmidy10
bschmidy10 said:
Okay guys I need some help here. VS985 was running TWRP 3.0.0-0, with latest cm nightly. The phone began running very slow and hot. In the attempt to update to another newer nightly, the install in TWRP just causes recovery to restart itself. This happens no matter what I attempt to flash. Making a backup also never progresses past the start. At this point I could still boot into the rom, but now nothing was working right... couldn't open most apps or download anything. I flashed twrp again in twrp as an .img just to see if that fixed it and obviously it did not, I also tried to flash CM Recovery but it failed. I took everything I needed off of the phone and then wiped the phone- system/data/cache but still could not flash a rom or anything so currently I have no OS, I have access to Firmware Update mode (download mode i think?) and my messed up TWRP. What should I try next? My guess is to use LG Flash Tool and start from scratch? I'm having trouble gathering all of those resources... thanks for the help friends!
-bschmidy10
Click to expand...
Click to collapse
I assume you let it cool down by pulling the battery and leaving it like that for a couple hours?
You might be facing a return to stock by either .kdz or .tot method and begin again. I do this every now and then just to keep things fresh. This is where I would start. I've never had this problem so I'm not sure if this will be successful or not. Good luck!
lakingslayer said:
I assume you let it cool down by pulling the battery and leaving it like that for a couple hours?
You might be facing a return to stock by either .kdz or .tot method and begin again. I do this every now and then just to keep things fresh. This is where I would start. I've never had this problem so I'm not sure if this will be successful or not. Good luck!
Click to expand...
Click to collapse
Thanks for the info. Would you be able to guide me to a current kdz/tot flashing guide? i have the tot file from way long ago still, but have changed pc's so my system and flash tool program are not set up, i believe i need some sort of .dll?
bschmidy10 said:
Thanks for the info. Would you be able to guide me to a current kdz/tot flashing guide? i have the tot file from way long ago still, but have changed pc's so my system and flash tool program are not set up, i believe i need some sort of .dll?
Click to expand...
Click to collapse
The stickied return to stock thread in the General section. At the very bottom of the first post there's a link to my KDZ/TOT section for the VS985 on Android File Host.
roirraW "edor" ehT said:
The stickied return to stock thread in the General section. At the very bottom of the first post there's a link to my KDZ/TOT section for the VS985 on Android File Host.
Click to expand...
Click to collapse
Thanks man!
Sent from my m8 using Tapatalk
I need help desperately. I made a backup a few weeks ago of all of the partitions using TWRP on my htc one m8. I'm running stock 5.0.2 rom, unlocked bootloader, rooted. I also tried a different version of TWRP (the latest one), same results!
Today I wanted to try and update to marshmallow using the OTA so I unrooted and proceeded to load it. Well it worked fine but wouldn't get passed the HTC One white screen.
So I tried a nandroid and it flashes everything except DATA.. When it gets to the data part it finishes in 2 seconds and does no writing!
I tried wiping (not a full wipe of data/media) data and no luck. I copied my backup from my PC of the same nandroid to the internal storage (thinking the restore from external where it originally saved wasn't reading) and no change.
No luck. P.S. The OTA update was only 77mb from AT&T and it caused all of this. I had unmodified stock rom, and only had it rooted for root required apps.
Please need help fast!
I guess this is a dead forum. At any rate it appears my nandroid backup created by TWRP was corrupted somehow and on the data files specifically. All is lost and phone is blank now with marshmallow. Sometimes even making a backup isn't enough I guess.
Also I have the files but they won't open as an archive in anything (and I've tried lots of ways) but show the size and take a long time to copy like there is quantifiable data in them data.ext4.win files. I'm guessing it just made blanks and takes up 4 gigs total for nothing....
One thing sure I did learn a lot in the process about nandroid files and now I have a system to check to make sure the files aren't corrupt (I open as an archive and inspect the info). Might not be 100% but at least will clue me in quickly.
blackbolt22 said:
I guess this is a dead forum.
Click to expand...
Click to collapse
A few folks still on here helping others, but yes its a pretty quiet forum. I'm personally never online during the weekends (and especially not July 4th Weekend).
I've had some TWRP backups fail to restore from time to time. It happens, nothing is perfect.
Was the main point to migrate user data across an OTA update? TWRP is one way to to that, but I've never done so (and not much of an OTA person, at that) ; so can't speak much to that. I usually migrate app data using Titanium Backup, and also backup by other means.
---------- Post added at 11:24 AM ---------- Previous post was at 11:22 AM ----------
blackbolt22 said:
Today I wanted to try and update to marshmallow using the OTA so I unrooted and proceeded to load it. Well it worked fine but wouldn't get passed the HTC One white screen.
Click to expand...
Click to collapse
Unrooted how? Only a never-rooted stock ROM will work with OTA (such as a TWRP system backup made before root). You also need stock recovery, but I think you know that if you eventually got OTA to work (its not clear in your description).
Hey folks. I'm stuck at the lollipop loading screen and can't get my ROM loaded, nor can I get into recovery.
I was on SkyDragon 6.x with the 35 bootstack. I wanted to load the stock 47A by xdabbeb, and all was good. I got into 47A, loaded things and then realized that I didn't have my Nova Launcher settings saved. I went back into recovery, wiped, flashed my most recent working backup, and then rebooted. Now I'm stuck at the ROM's loading screen (the four weird rotating artworks). It won't go past that even after leaving it for 30 minutes. It's possible the cause for my error was not wiping dalvik/cache after restoring, but regardless, my problem is now that I CAN'T FIND A WAY TO GET BACK INTO RECOVERY!!!
I tried the power+volume down, release at logo, then power+volume down like 20 times, but to no avail.
I tried adb in download mode, but my device isn't found in the list (maybe because the rom is not setup properly??)
What options do I have to get into recovery? I haven't backed up my photos in a while and it would be a TERRIBLE loss to have those photos go missing.
PLEASE HELP (at 3 AM!!!)!!!
Attempting adb again. My phone shows in Device Manager under USB as "LGE Mobile for VZW USB Composite Device" as well as under Portable Devices as "LGE Android MTP Device", but it won't list as an adb device when typing "adb devices"
Argghhh.
Mother plucker. I wasn't holding the buttons down long enough!!! Rebooting to recovery is working.
I should lose all of my rep for this thread.
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
roirraW "edor" ehT said:
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Click to expand...
Click to collapse
my.ads0 said:
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
Click to expand...
Click to collapse
LOL, you're welcome! Restore a backup or flash a ROM and then flash the Bootstack after the flash or restore. For SD6, you can flash either the 24B or 35B Bootstack although 35B might be preferable. I believe encryption and Advanced/HD Calling on 35B ROMs don't work with the 24B Bootstack but do with the 35B Bootstack.
Just get used to flashing the appropriate Bootstack after and you don't have to bother thinking about when you can get away without doing it.