Database Users

Question on upgrading to 5.0 from 4.4.4 when i was rooted.

hey guys i recently rooted my phone and then saw that 5.0 came out i wasnt able to find any reputable info on un rooting my phone so i could do the over the air update from verizon. however there was 2 updates available from OTA , one took me to another version of 4.4.4 and un rooted me. my boot screen still says custom but i no longer have root. however the ota 5.0 keeps failing. i figured maybe i can up date manually but the only site that has 5.0 for dl is sammobile and their site is down. all the other sites i found seem to be scams or want you to pay for faster dl. i dont care if i even have root any more i just want my phone on 5.0 with out loosing all the data on my phone. does any one have a link for instructions to do this? and a working link for 5.0? thanks

bump for help

Can you not boot into custom recovery twrp/safestrap? I Just re read your post, I'm assuming you can. So do that, and make a backup of /data. In addition it wouldn't hurt to use a usb drive or computer to back up any important files.
You say you want to be able to update without losing your data, I don't know if that's possible.if that is a real problem for you,I'd advise against modifying your phone in the future.
You didn't say why the update is failing, what is the given error message? Have you read the Verizon s5 forum?

[Q] Quick Question If Someone Has a Moment, Please

I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1

Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk

There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.

bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...

N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help

Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.

Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.

mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?

Still on jellybean...want to update to either kit kat or lollipop

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.

"Software status: Modified" and the OTA updates...

Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?

Totemic_tHiRp said:
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Click to expand...
Click to collapse
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.

scottdanpor said:
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
Click to expand...
Click to collapse
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....

Totemic_tHiRp said:
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Click to expand...
Click to collapse
It's not necessary that if your friend has received the OTA then even you will receive it within few days. The OTA is rolled batch wise and no one knows which phone is in which batch except Moto of course. [emoji4]
Sent from my XT1562 using Tapatalk

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

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.