My husband just got his s4 and it is asking him to update. He is at stock has not routed or any thing yet. So should he update and than route. . ??
If this update fixes anything we would prefer to have the latest update but we still want to route.
What would you all recommend
Sent from my SPH-L900 using Xparent Purple Tapatalk 2
From reading, it sounds like you could still root the phone after you take the update. So I would just take the update.
Yes you can still root after the update and yes it fixes some major issues.
Sent from my SPH-L720
Thanks I had him upgrade. Will root this weekend.. thanks for the input
Sent from my SPH-L900 using Xparent Purple Tapatalk 2
Before You Root
I updated the other day while rooted and after the device rebooted I still had root access, so as far as root goes, this update is safe (it was for me at least)
I know that every root method or youtube tutorial will say this, but before you root, make sure you have all of the proper files, drivers, and applications to do a complete restore. For the GS4 this is the ODIN flashing software, and the proper tarball to flash.
Also, the current rooting methods *shouldn't* mess with the userdata on the phone, but things can always go wrong. If you have anything that isn't "in the cloud" or backed up else where, make sure you back it up somewhere.
Happy rooting!
I updated stock before rooting... was able to root without any hiccups. I am now rooted with MDL. good luck
kenshi1023 said:
I updated stock before rooting... was able to root without any hiccups. I am now rooted with MDL. good luck
Click to expand...
Click to collapse
Kenshi, which method did you use? I tried motochopper with MDL but kept failing. I finally just ODIN flashed stock MDC and rooted that way. I've also heard of others losing root after updating.
odin flashed recovery "shabby" cmw
cmw flashed "shabby" modified kernel / flashed supersu
pretty much like this thread: [HOW TO] Install Latest Stock MDL Firmware with Modem, Custom Recovery and Root.
note: i was not rooted before MDL; my phone updated to MDL during activation; so rooted straight from stock MDL.
i read motochop doesn't work with MDL
PS: detection information warning; i freeze seaandroid and Samsung knox... not sure what will happen down the road, but it is preventing the warning.
As the Title states I have been trying to flash to Lollipop using the thread Update to lollipop and keep root using Flashfire app. I have downloaded and followed the procedure (yes I am rooted and confirmed with RootBasic) with it failing.
What happens is I load the files in order stated per the guide hit the lightning bolt, does the reboot and then gives error no command and then sits at stock flash update where you can either reboot, flash file or few other choices. I have tried numerous times with each time same result. What is going wrong? As I stated on am on MK2 firmware with ATT update frozen so not sure why this is. When put in download mode I confirm Knox 0 and Offical software with it having 0x30 for bootloader. Any suggestions or should I ODIN update but with what?
Frankpjr said:
As the Title states I have been trying to flash to Lollipop using the thread Update to lollipop and keep root using Flashfire app. I have downloaded and followed the procedure (yes I am rooted and confirmed with RootBasic) with it failing.
What happens is I load the files in order stated per the guide hit the lightning bolt, does the reboot and then gives error no command and then sits at stock flash update where you can either reboot, flash file or few other choices. I have tried numerous times with each time same result. What is going wrong? As I stated on am on MK2 firmware with ATT update frozen so not sure why this is. When put in download mode I confirm Knox 0 and Offical software with it having 0x30 for bootloader. Any suggestions or should I ODIN update but with what?
Click to expand...
Click to collapse
We just discovered this morning on the Vz S4 that FF does not function properly on their MK2(4.2) firmware which is likely also the issue here. You will first need to update to KitKat using the following file then root with towel root before updating to 5.0: https://www.androidfilehost.com/?fid=23501681358548937
Before I proceed to KitKat with file linked to is there a guide to properly performing this and then rooting? I will update from MK2 to NB 1 then I need to root, then do the FlashFire and Lollipop undate. I see the guide to use ODIN but then I will have to root I also have not used towel root either so any guide would be awesome. This should not change KNOX either correct (although I guess it does not matter since I am long out of warranty)?
I want to have a clear understanding of procedure so I don't brick the phone! I have not used ODIN before since I haven't really done much rooting other than when I first got the replacement phone last year
I'd suggest [GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap by guut13, and of course [How-To] Update to I337_OC3 - 5.0.1 and KeepRoot (4/7/2015) by muniz_ri for rooted Lollipop. Look in the I337 General forum for both.
Thanks Creepyncrawly and muniz_ri for both of your help it was easy to update from MK2 for this noob!
Ok I followed the guide and did update to stock nb1 and rooted, used towel root and then used flashfire to Lollipop and all seems to be working (I still am in process of setting phone up but it is running lollipop).
Since this is oc3 rooted is there anything else I have to do such as freeze att update? Anything else I should do right away?
Hello all.
I know some (maybe all) questions of mine have been answered somewhere, but I just couldn't find them in a concise list, so to say...so please be gentle if I am asking something that's already been answered somewhere.
Here goes:
I bought a second hand Samsung S5, G900F, with SEE firmware G900FXXU1BOH5, still one year in warranty (it was bought from Telenor Serbia, but I can see it is actually with SEE firmware, no operator bloatware, logos etc and sha256sums are equal for SEE and MSR LP firmwares, both taken from Sammobile).
Since it is a rather fresh LP build, as we all know there is no way to root it and keep warranty (knox will trip), unless you go way back to KK with ANE2 firmware (or earlier).
Now, there are 2 versions of instructions for doing that:
- just flash SEE firmware build ANE2, reboot, wipe, install towelroot
- flash SEE firmware build ANE2, use PIT file, reboot, wipe, install towelroot
First confusion is here: do I need to use PIT file? Did partition layout change and will official KK firmware do it on it's own or not?
If PIT file is required, at what moment I should use it? First PIT, then firmware or the other way around?
Also, are bootloader, kernel and CP files required for anything (I do have full official KK image for SEE, so I guess I don't need these files separately, but...)?
Do I need to flash bootloader at some point because KK has different bootloader than LP, or the full firmware will take care of that too?
Next set of questions regards going back to LP, which does not seem to be answered precisely:
if I downgrade to KK (using one of the procedures mentioned), and successfully install root and SuperSU, how do I upgrade back to LP?
- do I install latest LP firmware for SEE through Odin?
- or, do I activate OTA upgrade and let the phone upgrade/update itself back from KK to LP?
I am pretty sure that the first method will again destroy root access, but is the second method even viable now? Will OTA work or I'd need to go through KIES?
Finally, since I'm dealing with stock firmwares all along, knox should stay at 0x0, but what about status? Will it change at some point from official to custom (shouldn't, but than again...)?
If it is not possible to do what I need, the solution seems to be to go to custom LP rom that has been rooted already, and has knox deactivated etc etc. - is it really the only way?
If so, can you propose which ones will not change the status of the phone (knox, official/custom)? How about Galaxy project, that one seems pretty stock-ish to me...
Sorry again if asking wrong/already answered questions and thank you.
Cheers, Andrea
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, your plans A and B for downgrade are more or less like I thought they should be...
But, on the subject of returning to LP after the rooting of KK with towelroot...regular firmware with Odin will erase everything and ofcourse kill su, like I said in my original post - but, why do you think OTA won't work?
If the downgrade does not change knox (stays 0x0) and status (stays Official) why would OTA upgrade fail? It changes some components, removes some and adds some new, why would it touch /xbin/su if OTA process does not know about its existance in the first place?
Kies should do the same like OTA (at least so they say) but I don't like it also, so I'd use it as a final resort.
Then we have Flashfire - I'm not quite clear how that works...would I be able to install latest LP over downgraded KK, and at the same time install supersu (from where?) during the installation of the original LP firmware? Because that's what I'm understanding from your post, that the process goes like that...
If not, what kind of firmware does Flashfire use? Custom ROM with su, disabled knox etc, simply allowing you to install it from the phone, or original firmware as well? What would be the procedure with it and would it change knox (shouldn't) or status from Official to Custom if I use it with original LP firmware to return from rooted KK to LP?
At last, the pit file - I could obtain only one for 16GB version that is not specifically marked as for some region or country, and I don't know if there is a pit file for 16GB SEE (South East Europe) G900F to be found. I tried searching but the best I could find was for BTU, which is for UK but seems to be usable for all of North Europe, everything else was much more specific.
Does somebody have/know where to find pit file that would be suitable for my device?
Again, thanks
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, Flashfire part now confuses me...if I use that (already downloaded) only with LP firmware tarball, do I need to go back to KK to obtain root with towelroot or not?
I mean, if Flashfire will install SuperSU (which I already have installed, but not working obviously) during the flashing of full firmware tarball, why would I need to root before using Flashfire? Or it won't even work if you don't already have root...? Flashfire thread does not give specific requirements, although it makes sense that you need to have root before being able to use Flashfire...
Secondly, I thought that using towelroot will not change the status of the device in any way - no custom status, no knox=0x1? Now, you say that it did change your status to custom...do you think that if that happened to me, flashing original LP firmware tarball through Flashfire would return status to official?
Ah, so many questing that link to each other...and just when you think you've got one answer, it generates another question...
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hm, I've seen couple of solutions to that official/custom problem, although for Note3...basically, it's cache/dalvik clean, and deinstalling and reinstalling some app that uses root therefore triggering something that changes status to custom.
Which app that would be - it's a guessing game. Sometimes it's Titanium backup, might be Root explorer, Battery Monitor Widget...usually, reinstalling it fixes the problem.
But, now there is a second problem here - it seems that you need to have customized LP firmware to keep root using Flashfire...
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
and
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Do you think this is true and stock LP rom can't be flashed with Flashfire, getting rooted along the way?
There is an xposed module which will trick the phone into displaying 'official' rather than 'custom' though how deep into the OS this mod goes, I don't know.....
It *may* be enough to restore OTA functionality, but OTA isn't your 'best solution' anyway.......
It was always (and still is) my understanding, that Flashfire was/is able to flash regular 5.0 firmwares and 'inject' them with root......
But as I said, having not actually used it, I'm the first to admit, I'm probably not the best (most informed) person to answer your questions......My advice would be to visit the Flashfire thread and ask there.....You'll get answers from people who have actually used it
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you, I've seen your other post in Flashfire section and already replied to the one you refer to, but just to be sure, let's ask here too:
how to extract BL and modem from original LP tar.md5 file, because that's all I have?
Cheers.
This thread explains how to do it.....
http://forum.xda-developers.com/showthread.php?t=2864264
It's been written with the S3 in mind but I should think the procedure is exactly the same for the S5.
The thread mentions winRAR or similar as the extraction tool and goes on to say that it's 'paid' software.......as a free alternative, I've always used 7 zip and have never had any problems with it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Winrar has a 30 day trial, and still works fine once that has expired, but gives a nag screen popup when you use it
I use both Winrar & 7zip
Yep, just seen it, reading now...actually, it was also mentioned in a reply to my post in Flashfire thread, so I have to try what's written in this howto and see how it goes...