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
Related
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
P.Dub said:
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
Click to expand...
Click to collapse
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
P.Dub said:
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
Click to expand...
Click to collapse
This is what I would do. First odin flash back to NC5 stock unrooted. Then boot into stock recovery and do a factory reset. Next odin flash NC5 stock unrooted .tar again, then boot into download mode it should look like this
with official on both lines, sometimes it shows official on one line and custom on the other. That will give you headaches later. Now go ahead root, and install a recovery, beloat the stock rooted rom, for use as a daily driver, and make sure nothing crashes. Next make a backup so you have base to work from. Follow the instructions on the thread I listed above. I know this seems like a pain, but somewhere part of that AOSP rom is being left behind and causing your install of a stock rom to crash.
So I searched and found a ROM its nice and simple but now WiFi doesn't work ?
Sent from my SM-N900P using XDA Free mobile app
P.Dub said:
So I searched and found a ROM its nice and simple but now WiFi doesn't work ��
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod? Can you upload a screenshot of what your device is running? Like 4.4.2 or 4.4.4? Do you have custom recovery?
Goat1378 said:
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod?
Click to expand...
Click to collapse
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
P.Dub said:
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So you like aosp roms? Ok are you on NC5 or NH7? The screenshots in my last post will show you what you look for under setting/general/about device
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you have a pc with odin?
Yes sir I do
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you want update your firmware to NH7 or stay NC5?
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hey Pedro,
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
Since you're looking for AOSP ROMs, I'd recommend looking into this section of the forums. You need to make sure whichever ROM you are looking into works for the Sprint version of the phone (HLTESPR).
Alright so I used the last posts links and upgraded to 4.4.4 but now my data doesn't work
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs
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.
Verizon LG G3 with 24b firmware. Yesterday it started lagging massively, refusing to open most apps that weren't google, random reboots where it gets stuck on the red Verizon splash page that either resolve after 10 minutes or I pull the battery. Wiped the cache and did a factory reset. The phone is in the process of restoring stuff but now NOVA launcher freezes/quits. Any idea what this is?
I'm probably just going to attempt to upgrade until 46a or whatever is the most current since factory reset did not help and erased all my data already anyway.
Flash the 10B TOT after you move stuff you want to keep from your internal storage (if you have anything). TOTs flash more partitions than KDZs and can fix problems that nothing else can.
I had a weird problem months ago and no wiping, KDZ or ROM I flashed helped. The TOT did and after talking to @xdabbeb, that's when I found out there's a reason TOTs can help when nothing else does.
Then root with the Stump app on XDA, use TWRP Manager from the Play Store to flash TWRP, wipe Cache, Dalvik /ART and Data, flash the ROM that you want and appropriate Bootstack.
35B and 47A ROMs like both of @xdabbeb 's work great, and better than 24B and 23C.
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
APeter001 said:
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
Click to expand...
Click to collapse
Great! Shouldn't be too hard with Xposed these days, they've taken care of incompatibilities with LG weather apps, etc.
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.