EDIT: phone is currently unlocked/rooted
I've had a G2 since it almost came out, i don't have nearly the time to spend on here as i used to. Thus i've stuck with jellybean because everything works well and i have it set up how i want but it's a bit long in the tooth and the phone needs to have a full clean factory wipe so i figured i'd take the time to update to something newer.
My thought process is the following:
Save everything i want to keep and take off phone (including titanium backups)
Factory reset phone
Allow OTA updates to download and install
Then root
Then install custom roms (if i so choose)
Now fellow XDAers, anything wrong with my logic? I did do some reading and some searching and it seems like lollipop is rootable with a script and i can install customer recoverys with a script as well. I'd like the phone to still be able to unlock and root my device.
Thanks for any help and/or links to tutorials.
I am not sure but I think OTA updates need a unrooted system with stock recovery.
I had a rooted KK and I could not OTA to LP because the download was over 1.5 GBs!
The best solution may be to back everything up, connect the phone to LG Tools, and choose the upgrade recovery method to get the latest ROM for your phone.
Related
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
bumpity
dmo580 said:
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
Click to expand...
Click to collapse
You can't flash the OTA via Odin but you can sideload it by placing it on your ext-sdcard then sideloading from stock recovery. And by MDM I am assuming it's the modem that is not passing verification. Here is the G900V_NE9_Stock_Modem.tar.md5. Flash in PDA slot in Odin(AP in Odin v3.09+) then attempt to take the OTA again.
dmo580 said:
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
Click to expand...
Click to collapse
go to google play
and download Helium - App Sync and Backup
options for rooted and non rooted try it i used it to backup a app data locally without gmail cloud on my rooted note3 and save the file did the same on my rooted s5 and had it Manuel restore that file just need to create the same file folder and drop the file in it if you do Manuel
so stupid i had passed a ton of level on chuchu rocket i didnt wanna redo
i also used this to do the sms altho helium may have done that for me too SMS Backup & Restore (Kitkat)
INFOLIFE LLC - February 25, 2014
Business
there is non kitkat and kitkat labeled one does it good just doesnt backup pics in the mms txts
I have a GS4 on version 4.3 rooted and I have a custom bootloader, clockwork. I've recently tried to ota update but it makes my phone reboot into recovery mode asking if I want to install an unknown package, paraphrasing here. Last time I accepted this install and softbricked my phone so I'd like to figure out the problem so I can fix it and update to KitKat. If I have to flash the original recovery or Rom I'd very much appreciate links on how to do so given I haven't done either in a year or so. Thanks in advance.
The problem is you cannot take an OTA unless you are 100% bone stock.
This problem and the solutions have been discussed many many times. Please search and you will find everything you need.
Hey all,
Having a small issue with my Verizon LG G2.
When I first got it on launch, I rooted it, installed loki (to bypass the locked boot loader) and have been running custom ROMs.
This is the way I ahve been running it since, on 12B, with loki and CM11.
Before I installed custom roms I did a image backup using Clockwork.
Yesterday I bought a Droid Turbo, so it was time to restore the G2 in preparation for sale.
I attempted to restore my original backup of the stock image, but it failed (stating something about an inability to restore/system, resulting in a soft bricked phone.
I fixed this by downloading the LG Flash tool, and the stock 24A .kdz image, putting the phone in download mode and flashing it.
The LG flash tool seemed a bit buggy, complaining about not finding servers, but eventually flashed the phone with the .kdz.
Everything seems to have worked well. Root is gone, clockwork is gone, (and I assume loki is gone as well, but I can't tell) but now I can not do the latest OTA updates, and am stuck on 24A.
It's not that it downloads the OTA, and then fails to install it, but rather it complains that it is unable to download the updates at all.
I was thinking this might have something to do with the fact that the CDMA radio is now unactivated (since I got a new phone) and it somehow needs to verify with the Verizon network prior to downloading, so I grabbed a working SIM and popped it it in. Even with 4G via the SIM, the OTA downloads don't succeed.
Does the CDMA radio need to be activated in order for a phone to receive OTA updates? If not, I ahve something else wrong going on, and would appreciate any suggestions regarding fixing it.
The plan was to sell the LG G2 to pay for my Droid Turbo upgrade, but I don't want to sell the phone to someone if I think it may be having issues.
I would appreciate any thoughts and suggestions from you guys!
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.