Related
This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App
wynthewun said:
This morning I excitedly got a notification to update to 4.02. Installing update failed when phone rebooted to recovery and I got a red exclamation mark over the little Android.
My phone has been rooted with CMW installed. I know I lot of you will be thinking "just flash a different ROM" but the truth is I don't like any of the Roms currently available.
Did my update fail because of CWM? Or am I making a super noob mistake? Please help
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
badassirocz said:
yes CWM will cause update to fail the install. Flash the stock recovery img through fastboot if you want OTA's
---------- Post added at 03:13 AM ---------- Previous post was at 03:05 AM ----------
download the stock system image files from google and extact it to find the recovery.img
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you very much, i had the same problem this morning, the update disappeared so will it get back when i flash the recovery?
plus my launcher is modified will it affect the update?
it should come back if you check for updates in the system menu. If not it might take a few days to show back up from what I have heard. The launcher will not effect OTA's.
Please hit the thanks button if I helped
having this issue
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.
formula1210204 said:
I am having this issue also, but I didn't flash cwm into my phone, I only fastboot it, will this also cause this problem, or because I rooted my phone and on locked it, really need help.
thanks.
Click to expand...
Click to collapse
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.
jd1001 said:
It won't work because you are rooted. The install looks for the stock bootloader. You don't have the stock bootloader because you rooted.
Click to expand...
Click to collapse
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.
jhuynh said:
You are WRONG. Stop telling people wrong info. CWM is what caused the failure. Root doesn't mean you changed your bootloader.
Click to expand...
Click to collapse
Yeah apologies! I got my wires crossed. Thanks for clearing it up for me. I wasn't sure if it was the bootloader or the custom recovery. Thanks again and sorry for misleading anyone.
reply
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?
So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks
The update won't work because you will be using a different recovery when you root. So the update does not install at all.
However the benefits of rooting will allow you to have the latest Google updates thanks to the hard work of devs here. So root and get romming!!!
formula1210204 said:
thanks for reply, but as I said, I didn't flash CWM into my phone, I just boot it, in this case, it will also making this problem?
Click to expand...
Click to collapse
brypie said:
So, to clear this up for noobs (like me!)
If I root my Nexus, but keep it all stock, will I still get OTA updates?
If so, will an OTA update remove the root?
Thanks
Click to expand...
Click to collapse
If you just root the Phone and keep it complete stock (including Stock recovery, so not CWM) then OTA should work. I'm not sure about removing root though but I guess the OTA would not remove root. And if it does: It is easy to re-root isn't it?
The OTA should work if you didn't install CWM recovery or something like flashing a different radio. It removes root but you can easily re-root. I have not received 4.0.2 yet but when I received the volume fix update OTA I did not have any issues with it even though I was rooted. I just had to re-root after the update.
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
I would like to upgrade to the latest OTA update for my S3 but since I've rooted using towelroot, how can I update without messing anything up?
CrossBones3129 said:
I would like to upgrade to the latest OTA update for my S3 but since I've rooted using towelroot, how can I update without messing anything up?
Click to expand...
Click to collapse
First step is to figure out what bootloader and modem you're running. There are a couple of different ways to go about this, and knowing what firmware you're on will help with path to take.
To check your bootloader enter this in a terminal:
Code:
getprop ro.bootloader
To check your modem enter this in a terminal:
Code:
getprop gsm.version.baseband
Alternately install an app called Phone Info Samsung from the Play Store by vndnguyen. The app will tell you all the same stuff.
---------- Post added at 07:51 AM ---------- Previous post was at 07:48 AM ----------
And whatever you do, do not try to Odin back to stock until you know what bootloader version you're on.
i removed root. flashed stock recovery for the version i was on ie 4.1.2. then let OTA update me to the latest version. 4.4.2 then used odin to flash custom recovery and used a root zip from www.galaxys3root.com.
jason2678 said:
First step is to figure out what bootloader and modem you're running. There are a couple of different ways to go about this, and knowing what firmware you're on will help with path to take.
To check your bootloader enter this in a terminal:
Code:
getprop ro.bootloader
To check your modem enter this in a terminal:
Code:
getprop gsm.version.baseband
Alternately install an app called Phone Info Samsung from the Play Store by vndnguyen. The app will tell you all the same stuff.
---------- Post added at 07:51 AM ---------- Previous post was at 07:48 AM ----------
And whatever you do, do not try to Odin back to stock until you know what bootloader version you're on.
Click to expand...
Click to collapse
Bootloader & Modem: I747UCUNFE4
I believe this is the latest ROM: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
savagephoenix said:
i removed root. flashed stock recovery for the version i was on ie 4.1.2. then let OTA update me to the latest version. 4.4.2 then used odin to flash custom recovery and used a root zip from www.galaxys3root.com.
Click to expand...
Click to collapse
So I'd have to factory reset because I already have CWM Recovery? I'm not sure the steps to take.
You cannot use Odin to flash stock ROM since you are on a KK bootloader. Any attempts to flash a stock ROM that tries to downgrade the bootloader could brick your phone.
audit13 said:
You cannot use Odin to flash stock ROM since you are on a KK bootloader. Any attempts to flash a stock ROM that tries to downgrade the bootloader could brick your phone.
Click to expand...
Click to collapse
So what are my options?
Have a look at this thread: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
Is there a way to update from NE4 to the latest firmware keeping root via ODIN? Or do you have to use clockwork mod / TWRP?
audit13 said:
Have a look at this thread: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
Click to expand...
Click to collapse
K well I got up to the part aftwr you do the ota update. SuperSU keeps saying there's no binary installed. So I'm kind of stuck. Do I need to flash a custom recovery then flash supersu again through that custom recovery?
CrossBones3129 said:
So I'd have to factory reset because I already have CWM Recovery? I'm not sure the steps to take.
Click to expand...
Click to collapse
no reset required.. be sure you unfreeze any apps and or re install that pertain to OTA . use SU to unroot. either use odin to flash stock recovery per your android version or reboot into CWM and reboot without it fixing root. then let OTA update. use the tut at www.galaxys3root.com to get root after you update.
savagephoenix said:
no reset required.. be sure you unfreeze any apps and or re install that pertain to OTA . use SU to unroot. either use odin to flash stock recovery per your android version or reboot into CWM and reboot without it fixing root. then let OTA update. use the tut at www.galaxys3root.com to get root after you update.
Click to expand...
Click to collapse
Got it thanks! My USB Cord/Ports are messed up. Also like it says in that thread linked earlier, you have to hold the buttons down when Odin restarts your phone or you will definitely lose the custom recovery.
When flashing a custom recovery via Odin, uncheck auto reboot.
When you see reset in the status window, remove USB cable from phone, pull battery, replace battery, boot into recovery.
These steps will prevent the stock recovery from returning.
Flashing supersu from your custom recovery should give you root access.
CrossBones3129 said:
Got it thanks! My USB Cord/Ports are messed up. Also like it says in that thread linked earlier, you have to hold the buttons down when Odin restarts your phone or you will definitely lose the custom recovery.
Click to expand...
Click to collapse
no need to uninstall su just unroot in settings. what android version you on?
savagephoenix said:
no need to uninstall su just unroot in settings. what android version you on?
Click to expand...
Click to collapse
I've got everything working fine as well. Seems better than the towelroot method so far.
CrossBones3129 said:
I've got everything working fine as well. Seems better than the towelroot method so far.
Click to expand...
Click to collapse
Right on. Glad it worked out for you. It seems the quickest and easiest.
Hi I m really new to this so excuse me ...
i got many updates by flashing with fastboot prerooted system.img i was on 2.19.40.18 prerooted but i would like to go to a stock no rooted to be able to apply OTA now
I tried an erase of my phone, but i came back to prerooted ...
I tried to install tethered TWRP and to install the.zip from asus download page but it was stuck on updating IFWI .... ( 2.19.40.20 zip file from asus )
What can i do ?
Plz help me
You need to go into the SuperSU settings, scroll to near the bottom and choose "Full unroot."
I did all on this post : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
I did unroot, flashed all 4 line before but i think my recovery is corrupted, it end in error with the green guy instantly and flashin via fastboot recovery.img isnt doing anybetter ...
I m really stuck ..
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
shinjy87 said:
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
Click to expand...
Click to collapse
Protocol fault is because you don't use latest ADB. Google it.
i successfully did this but now adb is stuck on serving 13 % and on the phone : verifying update package , it stopped like 15 min ago ...
Here's what I did to go from pre-rooted system back to stock.
1. Download the official latest image from Asus http://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
2. Rename the zip to MOFD_SDUPDATE.zip
3. Unroot via SU
4. Uninstall Xposed and modules if you have them busybox etc. (uninstall.bat for xposed it's easy)
5. Copy MOFD_SDUPDATE.zip to an SD card and insert into phone or copy to internal memory
6. Boot into recovery by holding power and volume up
7. If you get dead android press power button and volume up button and release.
8. Auto installs new image
I went this route after unrooting via SU and uninstalling xposed framework still wouldn't let me run OTA updates for some reason. I imagine I did something along the road or removed a system app or something. It wouldn't let me manually sideload or update and would error out halfway through the process. I cleared fastboot cache and even reset the device to no avail. I was on 2.19.40.18. I installed the 2.19.40.20 image then the OTA update to .22 yesterday.
If I root the device again which is likely I'll use method 3 and the rootkit tool.
i will try your way, installing the 22 now.
But i dont remember in recovery the auto installs new image ?
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
shinjy87 said:
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
Click to expand...
Click to collapse
I installed the 2.19.40.20 full system image (1.1GB) from Asus yesterday. They didn't have the full image for .22 up but they do now. I was on the .18 pre-rooted image. When you hold power and volume up choose recovery and it should install the MOFD_SDUPDATE.zip automatically (mine did). I had issues trying to manually update the phone from .18 to .20 and .22 via ADB (the patches are like 30MB). It would start the update with the android robot then fail about halfway.
Download the correct system image for your device. The new update is available as a full image now so download the .22 image from Asus and then rename it to MOFD_SDUPDATE.zip. Copy it to an SD card and insert it back into your phone. Phone is powered off so hold power and volume up to get the recovery screen. It will say Normal in a big green arrow. Change it to recovery via the volume buttons then hit power button and it should find and automatically install the MOFD_SDUPDATE.zip image.
FYI this is on a ZE551ML 4GB/64GB US WW firmware based phone. I imagine the other models are the same or very similar.
I wish I could articulate this better. Hopefully someone more knowledgeable comes along and lends a hand.
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
wlbwlb said:
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
Click to expand...
Click to collapse
Yes.
Induced_Apathy said:
Yes.
Click to expand...
Click to collapse
Thank, another question. will it wipe all my data?
wlbwlb said:
Thank, another question. will it wipe all my data?
Click to expand...
Click to collapse
Flashing the entire system image you want to wipe everything anyways in this case. If you mean using the one click rootkit (method 3) to root then no it will not.
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
madmike23 said:
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
Click to expand...
Click to collapse
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Harfainx said:
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Click to expand...
Click to collapse
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
madmike23 said:
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
Click to expand...
Click to collapse
What does the recovery log say?
Harfainx said:
What does the recovery log say?
Click to expand...
Click to collapse
Only thing that caught my attention is: Unable to open '/sdcard/MOFD_SDUPDATE.zip': No such file or directory.
This was last attempt unrooted and this morning's OTA
I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.