Develop Bugs

Rooting and Modding questions. Final Check

So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201

You dl'ed android sdk yet or all the fastboot files you need?
Sent from my Galaxy Nexus using xda premium

You have it correct. Use titanium backup to save all your app data. And you have to restore a nand backup if you want to undo a mod you flashed. The mod usually instructs you to backup right before flashing, so you can just revert right back if you want.
I wouldn't worry about ota anymore. Being rooted always leads to you being able to flash the latest ota quicker than if you were stock and waiting for your number to be called. Trust me after years of this that's how it always happens.

corban227 said:
So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.

efrant said:
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.
Click to expand...
Click to collapse
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus

corban227 said:
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you are asking that question, more reading is likely in order before you start flashing things.
But anyway: a stock ROM is the ROM Google puts out. They are found here, and instructions on how to flash are in my signature. All other ROMs are custom ROMs.

Gotcha. Ill look it up tonight
Sent from my Galaxy Nexus

I ended up reading more which lead to me unlocking and installing 4.0.4
Im happy with this now and I dont feel the need to custom mod. I need my phone to be functional all the time with out being too time consuming =D thanks for the help and leading me to my conclusion

I would seriously give aokp a try, I promise its worth it. Its the same as stock there's no extra work needed or anything to worry about or deal with. Its that good.

Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.

biffsmash said:
Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.
Click to expand...
Click to collapse
I wouldn't recommend re-locking your bootloader if you have unlocked it. Actually, I would recommend that, every time you buy a Nexus device, the first thing you should do is unlock the bootloader. Don't forget, having an unlocked bootloader does not mean you are not "stock". An unlocked bootloader doesn't affect anything (aside from what I mentioned below).
Why you ask? Good question:
Advantages of a locked bootloader
If you lose your device, no one can easily access your data, but only if, in addition to your bootloader being locked, you have the stock recovery installed AND you have USB Debugging disabled AND you have a password on your device. However, this "risk" (if you can call it that) can be mitigated by many apps that can remotely wipe your device.
Disadvantages of a locked bootloader
You cannot use fastboot commands, so you cannot flash or boot images, which can save your butt in certain occasions.
You cannot try out new radios (assuming no root).
You cannot backup your data (i.e., make an image of your device's memory (assuming no root).
You cannot root (on 4.0.4 and later).
You cannot manually update to the latest version of Android once Google starts rolling it out. You have to wait until Google decides it's your turn, which could be minutes to months after the update becomes available.

+1 to working without me thinking. I'm leaving the boot loader unlocked to install any updates Verizon doesn't push through but other than that its staying stock. Plus I really like vanilla ICS AS IT IS
Sent from my Transformer Prime TF201 using Tapatalk 2

What will interfere with OTA updates?

Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!

sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.

gooberdude said:
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
Click to expand...
Click to collapse
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!

sashusmom said:
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
Click to expand...
Click to collapse
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.

gooberdude said:
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
Click to expand...
Click to collapse
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required

sashusmom said:
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
Click to expand...
Click to collapse
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.

gooberdude said:
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
Click to expand...
Click to collapse
Great info! Thank you Gooberdude! And I don't Jump .LOL. I just take it one step at a time....Smoothe, then if things are screwed up, I jump around!!! And call out for help!!! And duh- I forgot custom recovery is a problem.
I think I have access to both recoveries. Is that possible? I think I can get into the stock recovery by holding down the correct buttons sequence, but can get into Philz by using my cheat app that I really love, Flapps PowerTool. I'll review what I have and how to do the button sequence to pull up stock recovery and post back.
Thank you for the detailed instructions...Appreciate it. It will probably be awhile before kit kat is put out for our Note 8's anyway.
*********************************************************
Nope. Just Philz custom.

sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?p=50156744
Sent from my SM-N900V using Tapatalk

Restoring Stock boot.img & Stock recovery.img then taking OTA

I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!

AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.

Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.

It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.

AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125

Where can i found the stock boot.image and stock recovery.img

bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...

Thanks

Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!

laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!

AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!

No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!

AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....

[Q] TWRp can't restore backup/wipe cache.dalvik.etc

I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ

If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.

PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve

The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.

PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.

Rooted Firetv 1 standby to TWRP recovery screen

I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.

Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/

Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:

Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.

Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!

Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.