[Q] General questions about motochopper - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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 ?

Related

[Q] regarding: Loki + TWRP + Motochopper CASUAL

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

just got my s4 :(

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.

Root Question

Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
wholocked10 said:
Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
Click to expand...
Click to collapse
first, rooting your voids the warranty, so technically, they (either VZW or Motorola) are not obligated to replace it. that being said, you can always play dumb and say that you accepted some OTA install, and now the phone won't boot up. usually, VZW will try to restore the phone, and if not, they'll replace it - no worries.
2.) I believe there is an unroot method, but I have not explored this. try doing a search on this forum for "unroot razr m"
3.) restore factory settings could unroot - check the threads
4.) you can still install a custom ROM, but you'll need to install Safestrap first. however, the custom ROMs available for SS are out-dated, and I don't think that any devs will be providing any going forward. however, I would not be too discouraged by this, as the phone is very solid stock. so rooting is the key to remove the bloatware to help increase battery life, increase performance, and reduce excess data usage.
hope this helps.

finally rooted sph-l720 mk2

im on sph-l720 had 4.3 mk2 all methods was not working for me either would fail right off the bat or go thru the proccess say it was rooted then when doing root checker i wasnt rooted..... finally after messing with this for about a week i finally found a way to do it i used kingoapp.... this method was very simple and easy to use and i am now rooted..... just thought i would post this if there was those out there that was having the same trouble that i have been having
sk907 said:
im on sph-l720 had 4.3 mk2 all methods was not working for me either would fail right off the bat or go thru the proccess say it was rooted then when doing root checker i wasnt rooted..... finally after messing with this for about a week i finally found a way to do it i used kingoapp.... this method was very simple and easy to use and i am now rooted..... just thought i would post this if there was those out there that was having the same trouble that i have been having
Click to expand...
Click to collapse
newbi (to s4)here and still looking... went to there site and didnt see the i720 on there list... did it trip knox when u rooted?
root
ibcenu said:
newbi (to s4)here and still looking... went to there site and didnt see the i720 on there list... did it trip knox when u rooted?
Click to expand...
Click to collapse
My Knox was tripped by one of the failed attempts. ... As far as I know the kingo route did not trip Knox unless the counter only stays on 1... If it adds up then no kingo did not trip my Knox that is something I'm not to sure of may be something to ask one of the ppl that know a lil more but I do know that Knox only voids the Samsung warranty. ..If something does happen u can still pay the deductible to replace ur phone... wich is only $150 that's as long as u have the insurance coverage on ur plan... As long as u follow the steps wich is really simple u won't brick... sph-l720 is not on the list for kingo but it does work that's what I used... All the other ways says that the su is out of date so I recommend if u are going to do it use kingo after I did that I downloaded rom manager n installed a CWM my phones working fine
What's up team,
still getting used to things around here and I apologize for the stupid questions in advance! However, you all have been amazing and helpful to me thus far and I appreciate it.
So, I finally decided to root my Sprint GS4 thanks to the helping hand of the great QBKing77
I was trying to go even further and be able to do the free hotspot which QBKing77 had a video for as well. However, I noticed that the download links that he had supplied us folks with did not include baseband version is MK2 - which is what I am currently running (whatever that means.)
So among several other questions, first and foremost; what can I do to get the free hotspot/tether with MK2? Should I simply download one of the other links instead or will this damage my device?
Also, as said, I am new to this. I just rooted my device for the first time and am unaware what the difference is between odexed and deodexed? What does this mean, what is the difference, and how do I know which one I am?
Leading in to that, I installed TWRP custom recovery. I tried to click on back up then select "boot," "system," and "data." However, it is saying that the attempt was failed. I am going to assume that this is because the whole back up would be roughly 3gb's and it says that I have only 502mb's available on my phone.
I read somewhere a while back that I could delete stock apps from my phone after I route. How can I do this? I am guessing that this would free up a significant amount of storage and thus could accomplish the back up. Is it safe to delete stock apps? How can I know which apps I can safely uninstall?
Thanks guys! Any other tips or tricks or words of advice...even constructive criticism are welcomed!
erquiagomon said:
What's up team,
still getting used to things around here and I apologize for the stupid questions in advance! However, you all have been amazing and helpful to me thus far and I appreciate it.
So, I finally decided to root my Sprint GS4 thanks to the helping hand of the great QBKing77
I was trying to go even further and be able to do the free hotspot which QBKing77 had a video for as well. However, I noticed that the download links that he had supplied us folks with did not include baseband version is MK2 - which is what I am currently running (whatever that means.)
So among several other questions, first and foremost; what can I do to get the free hotspot/tether with MK2? Should I simply download one of the other links instead or will this damage my device?
Also, as said, I am new to this. I just rooted my device for the first time and am unaware what the difference is between odexed and deodexed? What does this mean, what is the difference, and how do I know which one I am?
Leading in to that, I installed TWRP custom recovery. I tried to click on back up then select "boot," "system," and "data." However, it is saying that the attempt was failed. I am going to assume that this is because the whole back up would be roughly 3gb's and it says that I have only 502mb's available on my phone.
I read somewhere a while back that I could delete stock apps from my phone after I route. How can I do this? I am guessing that this would free up a significant amount of storage and thus could accomplish the back up. Is it safe to delete stock apps? How can I know which apps I can safely uninstall?
Thanks guys! Any other tips or tricks or words of advice...even constructive criticism are welcomed!
Click to expand...
Click to collapse
You can find the MK2 hotspot mod in this thread post #337: http://forum.xda-developers.com/showthread.php?t=2256950&page=34
Make sure you download the correct one. If you only rooted the stock rom then you need the odexed version, if you downloaded and installed a custom rom then you need the deodexed one. As you guessed, if you use the wrong one you will brick your phone.
TWRP backup, you need an external sdcard if you want to make backups or your internal memory will max out. If you have an external sdcard, look on the twrp backup page closely and you should see an option to switch to the external sdcard.
Stock apps delete, you can delete stock apps if you are rooted but be careful, if you don't know which ones can safely be removed then search on here to make sure you don't delete one that is required. You will need a file explorer app that has root permissions to access the system partition. I would recommend an app like titanium backup to remove these apps so that you can first back them up so you can replace it if you mess up. Again, you should use an external sdcard or it doesn't make sense to back up if you are doing it to save space.

Need a little confirmation....

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.

Categories

Resources