Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.
Related
I have a Samsung Galaxy S4 on AT&T. This is my first android and I'm trying to get a grasp on rooting as an ex-jailbreaker. I've tried reading and searching but unfortunately I just need to ask some specifics.
My understanding is that the current root for this phone is derived from a Motorola root and that it does not include a way to make backups. I am eager to root but I really don't want to take extra risk than is necessary. Is something like CWM required to backup your phone in a way that protects you against accidentally messing up the filesystem? And is there any way to get something like CWM on this phone yet?
I see that there is now a custom recovery for this phone on galaxys4root dot com but can I even use it without something like CWM.
I'd appreciate any info, thanks for your patience.
HardOnChairs said:
I have a Samsung Galaxy S4 on AT&T. This is my first android and I'm trying to get a grasp on rooting as an ex-jailbreaker. I've tried reading and searching but unfortunately I just need to ask some specifics.
My understanding is that the current root for this phone is derived from a Motorola root and that it does not include a way to make backups. I am eager to root but I really don't want to take extra risk than is necessary. Is something like CWM required to backup your phone in a way that protects you against accidentally messing up the filesystem? And is there any way to get something like CWM on this phone yet?
I see that there is now a custom recovery for this phone on galaxys4root dot com but can I even use it without something like CWM.
I'd appreciate any info, thanks for your patience.
Click to expand...
Click to collapse
We cant have CWM until bootloader is unlocked (assuming you have the US AT&T version)
That being said, seeing how there is no custom ROMs you can use ODIN as a kind of backup. It'll wipe and then install factory /system partition, leaving /data alone (you can wipe /data in stock recovery if needed).
CWM works better as it backs up YOUR phone (including mods and /data).
_Dennis_ said:
We cant have CWM until bootloader is unlocked (assuming you have the US AT&T version)
That being said, seeing how there is no custom ROMs you can use ODIN as a kind of backup. It'll wipe and then install factory /system partition, leaving /data alone (you can wipe /data in stock recovery if needed).
CWM works better as it backs up YOUR phone (including mods and /data).
Click to expand...
Click to collapse
Would a stock firmware be enough to get me back up if I mess up my phone with root access? That's my main concern.
HardOnChairs said:
I have a Samsung Galaxy S4 on AT&T. This is my first android and I'm trying to get a grasp on rooting as an ex-jailbreaker. I've tried reading and searching but unfortunately I just need to ask some specifics.
My understanding is that the current root for this phone is derived from a Motorola root and that it does not include a way to make backups. I am eager to root but I really don't want to take extra risk than is necessary. Is something like CWM required to backup your phone in a way that protects you against accidentally messing up the filesystem? And is there any way to get something like CWM on this phone yet?
I see that there is now a custom recovery for this phone on galaxys4root dot com but can I even use it without something like CWM.
I'd appreciate any info, thanks for your patience.
Click to expand...
Click to collapse
The answers to all of the questions you asked are in these threads...
http://forum.xda-developers.com/showthread.php?t=2261573
http://forum.xda-developers.com/showthread.php?t=2252248
http://forum.xda-developers.com/showthread.php?t=2257058
http://forum.xda-developers.com/showthread.php?t=2259933
http://forum.xda-developers.com/showthread.php?t=2261232
http://forum.xda-developers.com/showthread.php?t=2254274
I found a few of those threads, they are what prompted my additional questions. But the second to last one seems to answer my question. Thanks.
HardOnChairs said:
I found a few of those threads, they are what prompted my additional questions. But the second to last one seems to answer my question. Thanks.
Click to expand...
Click to collapse
You can use either Kies or Odin and the stock factory firmware to completely return to factory stock, but be careful with ODIN, if you check the wrong options it can hard brick your phone.
MotoChopper
I would like to know ...
I rooted my S4 with Motochopper and I realized that my boot animation changed (to the one Samsung used in older models...) Is it easy to put back the new one ?
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide
Thanks again!
DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock
TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.
TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.
TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help
I think everyone gets the picture.
Sent from my GT-I9505 using xda premium
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Not at the moment. There is a root method, but no factory image to flash back to.
http://forum.xda-developers.com/showthread.php?p=43890414 check here for recovery updates.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
sheek360 said:
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Click to expand...
Click to collapse
We all just have to be patient! It's not the end of the world, rooting it allows you to remove some bloatware, then you can install themes and launchers to make it a little better!~
You can still tweak the device so it's enjoyable!
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
jd1639 said:
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
Click to expand...
Click to collapse
You get around alot, have you seen any update to the MF3 bootloader issue?
TheAxman said:
You get around alot, have you seen any update to the MF3 bootloader issue?
Click to expand...
Click to collapse
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Tons and tons of uninformed people are messing up their phones. You're right, it's sad.
It will be great when people can comfortably root their device knowing there is a way back when all is said and done.
In the mean time, to the OP, playing the waiting game will not kill anyone in this situation.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Agreed, if most would have read just a little, they would not be having this issue. For me, I always wait until a dev gets a hold of an update and does their thing, and then I update to the newest...I have NEVER updated direct on the phone, even with all the phones I have ever owned.
Not happening OP, do a search on MF3 in the search bar you will find all kinds of things related to it.
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
ThePerson98 said:
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
Click to expand...
Click to collapse
I just wanna plus 1 that for the OP
Sent from miPhone using XDA Premium HD app
As long as you're a smart cookie and don't go around attempting to mod your twframework and other important inner system files, I wouldn't get too disheartened and held back from touching the partition. Simply be intuitive and anything you intended on replacing, rename instead to the file with a *.temp extension. Wouldn't be that hard to roll back then (as long as you can still boot). Rooting itself mods the system, so people have already jumped ship in that regard.
Just don't go around trying to enable verbose boot or flash a recovery from some kind of mobile ODIN or GooManager.
BE SMART, not eccentric and living by the standards of yolo.
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
mikeprius said:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
Click to expand...
Click to collapse
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
cruise350 said:
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
Click to expand...
Click to collapse
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
mikeprius said:
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
Click to expand...
Click to collapse
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
cruise350 said:
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
Click to expand...
Click to collapse
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
mikeprius said:
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
Click to expand...
Click to collapse
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
cruise350 said:
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
Click to expand...
Click to collapse
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
mikeprius said:
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
Click to expand...
Click to collapse
Every thing in the data partition(titanium backup) will remain and everything in the system partition (SuperSU & stuff modified via xposed installer) will be gone and replaced with the bloatware.
Sent from my SPH-L720 using Tapatalk
Ok, so it appears to have worked. I flashed the 4.3 prior version however it was hooked up to wifi and automatically downloaded the new version and removed root (not a big deal). My status says custom still, but I am assuming that I can OTA after the flash b/c it updated to the most recent 4.3 in Dec 2013. I re-rooted so it is back to prior, but I know now how to do it.
Is there anything that I may delete or uninstall that cannot be replaced by flashing the stock firmware ? For example I was thinking about getting rid of the 'help' on the phone and Titanium Back up said it is odexed or something to that extent and can only be replaced by using Titanium Backup and the exact same copy ?
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Being able to flash the stock .tar through ODIN gives me peace of mind from screw ups, even if it removes root and takes time.
mikeprius said:
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Click to expand...
Click to collapse
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
nobody291 said:
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
Click to expand...
Click to collapse
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
mikeprius said:
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
Click to expand...
Click to collapse
To me, one of the hardest parts of this whole thing is getting to the point where the basic terms make sense. I've been at this for a couple of years with an HTC Evo and now the GS4 since October, and sometimes it still makes my head spin. Here is an attempt to explain my understanding of a few things:
1. Booting...you can boot into Download mode, recovery, or system. Download mode is what you use with ODIN, you need the correct drivers on your computer (which can be found lots of places), so that ODIN and your phone can communicate. In download mode, the phone just accepts whatever ODIN sends it, so it's the easiest way to totally brick your phone. Don't mess with partitions and follow the instructions for whatever you're doing very carefully, because I think this is the only way to "hard brick" your phone.
2. Recovery - something you use to create images of your phone's ROM (nandroids), flash ROMs and mods, and restore past nandroids. The stock recovery will only flash approved updates from the carrier, so to do any of the things I listed you need a custom recovery. Most people use Philz (which is based on the ClockworkMod recovery) or TWRP. To flash the custom recovery, use ODIN and follow the instructions in the thread exactly. There is a way to flash recoveries without ODIN, but I've never done it. I was using TWRP, and switched to Philz to flash the rooted stock 4.3 update because the thread suggested it. They both seem to do the same thing, and I have been happy with both. I'm sure there are technical differences, but I couldn't explain what they are. You can switch back and forth as much as you'd like between the recoveries with ODIN. Recoveries can flash a complete ROM or just partial changes (like the hotspot mod). In a custom recovery (or the stock) you can also do factory resets and cache cleaning (most ROMs suggest you do this before flashing). Factory reset doesn't return the ROM to the factory original, it just clears out all of the user data (including user apps). A nandroid is the fastest way to restore a phone if you screw it up...I always make one before making significant changes to the phone. It takes several minutes to do, but I think it's well worth it. The operating system can't be running when you make one, that's why you need to boot into recovery mode. You create a Nandroid in Philz by selecting "backup and restore" then "backup to" which will allow backup to the internal storage or external SD card.
3. ROM - the actual operating system used by the phone when you actually use it as a smartphone. There are 2 basic flavors for the GS4...touchwiz and AOSP (Android Open Source Project). Touchwiz is Samsung's "flavor" of Android, AOSP is the "pure Google" version of Android. A lot of the things the GS4 will do rely on touchwiz (multiwindow is one example...but there are several). Some people really like the AOSP ROMs (Cyanogen is AOSP), but make sure you understand their limitations. I've never used one on the GS4. There are several touchwiz custom ROMs which have various features. I've tried a few and just settled on the stock rooted touchwiz ROM, but there are lots of options from great developers. I think most custom ROMs require you to use a custom recovery to flash them, but there might be ways to do it using ODIN. I like having a custom recovery, so I've only used ODIN for flashing modems and recoveries.
4. Firmware - as far as I can tell, there are two important parts of the firmware...the modem (sometimes called "radios" or "baseband"...find your version by looking in "about device"->"Baseband version"...the different modems are described by the last 3 letters you see) and the bootloader. The modem and the version of the ROM you flash need to match or you'll have problems with the radios in the phone (wifi seems to be the biggest problem if you have a mismatch). MF9 was the last modem version based on 4.2.2, and 4.3 has had MJA and MK2 (MK2 is the latest). The bootloader is what the phone uses to initially decide how to boot up. If you have the 4.3 version of the bootloader it will include "Knox", which will prevent you from flashing older versions of the modem, so you'll have to use a 4.3 ROM. Knox also "trips" a counter if you flash a custom ROM and Samsung claims they won't honor the warranty on a phone with the "Knox flag" tripped. If you have the 4.3 bootloader you're stuck with it (for now at least). I still have the 4.2.2 bootloader, so I don't have much more to offer on this subject. There are ways to get the 4.3 modem and ROM without the 4.3 bootloader. There is a lot here (and lots on youtube) on how to navigate the Knox minefield if you care about it. If you still have the 4.2.2 bootloader you can flash older (and newer) modems as much as you'd like without getting the updated bootloader using ODIN.
Hopefully this helps...this is a great place with lots of great people. Sometimes the scale of the amount of information here is overwhelming. But, search is your friend along with lots of time! Feel free to keep asking questions.
thanks for explaining this nobody-
The information does help quite a bit and I am still learning, however; I do enjoy the process of messing with the phone. My GS4 now runs the RAM at 750-800mg instead of a bloated 1.2GB which was happening quite a bit. I had to originally not use a lot of apps I wanted to like Facebook bc the programs themselves bloated up to accomidate the existing bloatware which was also running. I did flash my phone back with the stock firmware today and it looks like it installed all the stock software. My status said 'custom' when I looked at it however I was already connected to wifi and it went from 4.3 (Oct 2013 version which I flashed) to Dec 2013 version automatically so it appears that the OTA feature works.
I assumed if I accidently delete something from the phone that I really need to affects the phone, I can always flash the stock ROM to fix it. Losing the root is not that big of an issue, but I did lose Superuser and had to re-root the phone. I suppose I do have a few more questions, one was when I was reading another carrier provider thread.
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
mikeprius said:
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
Click to expand...
Click to collapse
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
Click to expand...
Click to collapse
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
nobody291 said:
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
Click to expand...
Click to collapse
It was good that you mentioned the Knox bootloader issue with the 4.3 upgrade. When I purchased my cell phone back in Nov, I believe it had the 4.3 (1st) version loaded, but it already had Knox features as I do recall seeing them. If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ? This may have been the error I read about due to the new Knox feature.
I think since my phone is currently rooted and I altered some of the bloatware system files that the update if it were made available OTA should not update anyway due to the root. Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ? With that, if I were to load 4.4 and not like it, could I flash back 4.3 ? I am guessing this is the part where you mentioned that the carrier may decide differently later on.....I suppose I will just keep an eye out in the meantime.
Good good............, I'm picking up this pretty well so far.............
mikeprius said:
If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ?
Click to expand...
Click to collapse
I'm not sure what symptoms you'd see if you installed 4.2.2 with the 4.3 bootloader. Most likely the phone would fail to boot. ODIN will flash whatever you tell it to, I don't believe it does any compatibility checking on its own. You can still get the wifi hotspot feature to work even with Knox and the 4.3 bootloader, I don't think that was what they were trying to do with the update. There are threads discussing 4.3 and what changed, but there wasn't much obvious to the user. For now you can't go back if you're on 4.3, but there might be an exploit discovered down the road that lets you get the old bootloader and go back.
Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ?
Click to expand...
Click to collapse
Yes, they won't be available immediately though. It can take some time for the community to re-obtain root too, depending on how big the changes are.
With that, if I were to load 4.4 and not like it, could I flash back 4.3 ?
Click to expand...
Click to collapse
I think you alluded to the answer already, but it depends. It took a month or two before you could flash the stock 4.3 without the 4.3 bootloader. There were custom ROMs available that used custom kernels sooner, but there was a problem trying to use the stock kernel with the 4.2.2 bootloader. So, always read and read and read some more before flashing updates.
So far i think i got the hang of it. I have been modifying the phones original touchwhiz. I ended up freezing alot of files instead of deleting them so the ability to turn them back on is there. Some of the files while there are not meant to be frozen/disabled/turned off. I tried a few methods for keeping SuperSU over an ODIN with no luck. I do have a question though. If i turned off (but did not delete) alot of system files and were to run ODIN again will all of them including the bloatware be turned back on and restored? That would be bad if i flashed, lost root, then simultaneously had all the system files disabled with no way to turn them back on......
This also a dumb question but what exactly am i flashing with ODIN? Its a 1.5 GB file with Sprint and it is a tar that restores all bloatware and turns the phone status back to official so i can get OTA updates. Am i flashing the entire stock ROM or just the firmware? Its nice that i have not lost any existing apps or data. It just restores the bloatware and removes root
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
mikeprius said:
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
Click to expand...
Click to collapse
The .tar you are flashing from sprint is what we would call stock firmware image. This is the image that shipped on the phone from the factory. I'm an avid flasher and would highly recommend installing twrp or philz touch, creating a nandroid backup and giving some debloated touchwiz roms a shot. You'll see some significant improvement in battery life and performance and some really cool upstream features. I use odin as a last resort, when I need to go back to stock for whatever reason (ie domestic sim unlock) or have fubar'd my current setup past a point of no return.
Hello,
A few months ago, I was able to successfully root my AT&T S4 (SGH-I337, builld LRX22C.I337UCSGOK3) using KingRoot. The KNOX warranty bit was not set at the conclusion of the root process.
After wrestling with storage problems, including the "system memory" taking up 6.29 GB out of the meager 16 GB that is on this phone (preventing practically any Google Play updates from occurring, as the available space would always dip below 500 MB periodically), as well as performance problems (very long delays for some touch events and a general resentment of TouchWiz), I decided that enough was enough, and I decided to change my ROM/OS out for LineageOS.
LineageOS offers builds for jfltexx, which is reported to work for jflteatt since they are similar enough. I am not really willing to try "older" builds, as one of my goals is also to bring the security of the operating system up to date, so I am not exactly inclined to go for old CyanogenMod builds. The LineageOS install guide stipulates that I install TWRP to successfully install the OS via a supported recovery; however, the message SECURE MAGICCODE FAIL: recovery appears, as the upgrade process seems to be expecting something signed by Samsung (right?). Other guides warn that the stock recovery only allows stock OS installation and not custom operating systems, so I decided not to try that route. This effectively prevents me from installing LineageOS due to a problem that is inherent in OK3.
Why did I make the mistake to install OK3? More than a year ago, I decided to do the final update that AT&T pushed out for this phone. Thinking that it would be something significant, I went for it, only to find out months later that it was a minor update whose purpose was also to add an additional lock to the bootloader. As this phone is "fairly old" (is 2013 already considered ancient times?), I have not found many guides that cover OK3, and those that do pertain to either rooting the S4 (already done) or something about downgrading (but I can't really do that, seemingly due to the OK3 lock-in). Oops.
That said, is there any hope to bring more life out of my phone, or is it time to throw the phone out and buy a Pixel or related product like any typical consumerist would do? My goal is to move to another OS to end the storage problems and other quirks of this phone that I have grown to deplore; that is all I wish to attain.
The phone is relatively reliable: it had ~1200 hours of uptime before I had to reboot it a few days ago to fix a data connectivity problem. The battery is also very manageable and can last a day and a half in regular use, but it can last 2-3 days under maximum power-saving mode.
I have read the rules and done some research on this forum, among some others. Thank you for your assistance.
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
audit13 said:
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
Click to expand...
Click to collapse
I see; so I was already screwed when I had OK2?
oldmud0 said:
I see; so I was already screwed when I had OK2?
Click to expand...
Click to collapse
Yes, anything past MDL has the bootloader flaw patched. MDL firmware and below have a flaw in the bootloader that allows loki doki to be installed bypassing the bootloader lock so you can install TWRP recovery and custom AOSP ROMs.
Since you're on OK3, you're forced to use safe strap recovery and can only install custom touchwiz ROMs like golden eye and albe95.
If you want to read up on the MDL bootloader, I have written a guide here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
oldmud0 said:
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
Click to expand...
Click to collapse
If you want away from touch wiz, I think there's a Google play edition ROM for the galaxy s4 that you can use with OK3, but I am not too sure. I would just check the galaxy s4 ROM section for it. I'm on the MDL bootloader which allows me to use TWRP, so I don't know too much about safe strap recovery.
Even if one wanted to do a TouchWiz-based ROM, I don't think we on OK2/OK3 even have the option to install SafeStrap, so far as I can gather
Hold the phone, I think I've found something. Evidently we can Odin back down to NB1 and go from there! Experiments, here we come.
Yes, NB1 is as far back you can go I believe without bricking your phone.