Related
Hey guys, need some help. I've searched around and tried to do different things but I'm afraid that I might be stuck (due to my limited knowledge of working with androids).
So I rooted my Fascinate and installed ROM manager and clockwork recovery onto it. Well, after fiddling around with it for a few weeks, I feel like I’ve gotten my self into a position where I’ve lost the way back. So now, I’ve tried unrooting using a couple of methods (update.zip and one click unroot) but it fails every time. This led me to believe that root/super user was not gone from my system (Super User icon/app is still there). This morning, I installed Titanium Back up and it said it couldn’t start because my phone is not rooted. I go into the Super User app and no app has requested it. I’m just kinda lost at this point and want my phone back to the state when I had first purchased it.
Now I know there is the Odin way, however, his post says that his files include superuser and busybox already installed – this I don’t want. I want the unrooted factory Samsung Fascinate state back. I was thinking about using the “factory reset” option in the settings but wanted to get your opinion on this before proceeding (since several posts said to do it where as others said don’t do this way).
Can someone help this clueless android n00b? Please?
If you do a factory reset superuser will still be installed.
When I did Oden restore i think I had to re-root my phone.
You could also root your pone again, then un-root to remove superuser.
Why do you care? My wife and I both have gotten replacements because of hardware defects. Both phones were rooted and they never questioned it either time.
This thread contains ODIN files for a completely stock device:
http://forum.xda-developers.com/showthread.php?t=782204
No root/bb/su.
NKT said:
This thread contains ODIN files for a completely stock device:
No root/bb/su.
Click to expand...
Click to collapse
Actually, the system file in that thread does have SU/Superuser.apk/Busybox, but otherwise it's stock.
atrich0608 said:
You could also root your pone again, then un-root to remove superuser.
Click to expand...
Click to collapse
This did the trick!!
I used the the z4root app from appbrain, rooted and unrooted. SU = Gone!! Amazing!
Thank you!!
I hope I dont ask something that has been asked a milion times, but I didnt find very clear answers to this...
I got my A500 a few weeks ago, updated right out of the box to 3.2 and am happy so far BUT would now, after some use like to root it.
I see that its possible by downgrading, also read somewhere about an modified official updater that would work - what I want to know, how can I root that thing without any data loss?
Is the downgrading variant completely safe for that? Or, in any case, is there anything that can make a full backup without root?
Oh, and when finished - is there a ROM that basically just gives me root and throws out all of the crap ACER installed on the system?
Thanks ^^
Pray to the Acer Gods usually helps.
But really, if you synch your contacts to Google, then you have little to worry about. If.... you trust the cloud.
Paid apps, are always able to be re-installed through the Market.
If you have a recent version of the market, then you should be able to restore most of the free apps.
But hey, they were free, so who really cares....
SD card (photos and such) are not effected.
I've been researching this as well, but have yet to find a solution. It appears that there is no way to make a backup of your stock ROM before flashing a custom ROM, since you have to downgrade in order to root.
Since there are stock 3.2 rooted ROMs in the dev section, I'm tempted to just make that my initial flash after downgrading/rooting, set it up, then do a backup.
And fyi, astro file manager can backup your apps similar to titanium backup. I plan on doing that to restore the apps I've already installed.
Hope that helps a little. I mostly commented in case someone provides you with a solution...then I'll see it.
Chemo84 said:
I hope I dont ask something that has been asked a milion times, but I didnt find very clear answers to this...
I got my A500 a few weeks ago, updated right out of the box to 3.2 and am happy so far BUT would now, after some use like to root it.
I see that its possible by downgrading, also read somewhere about an modified official updater that would work - what I want to know, how can I root that thing without any data loss?
Is the downgrading variant completely safe for that? Or, in any case, is there anything that can make a full backup without root?
Oh, and when finished - is there a ROM that basically just gives me root and throws out all of the crap ACER installed on the system?
Thanks ^^
Click to expand...
Click to collapse
I must have been lucky. I followed the easiest path to downgrade on the tutorial from this forum. After I applied root and used acer recovery installer to install taboonay 2.2. I didn't clear cache or do a factory reset, and everything worked. Only lost the acer apps, which I was able to get back painlessly from either tabootools or gameloft. I am sure that people would not recommend going my route though.
Taboonay 2.2 is a pretty clean rom, and I feel it's nice with Richardtrip's 3.4 kernel.
just revert to 3.0.1 with the 2nd method of this thread http://forum.xda-developers.com/showthread.php?t=1276227 and you won't lose anything.
superfrancy97 said:
just revert to 3.0.1 with the 2nd method of this thread http://forum.xda-developers.com/showthread.php?t=1276227 and you won't lose anything.
Click to expand...
Click to collapse
Also works with 3.2.1 Australian default rom. Only problem is I lost default rom as I jumped into custom stuff at 3.2.1 and could not find info on how to back up the operating system without root.
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
Hey everyone,
I put a stock image of 4.3 on my phone - T Mobile to remove root, update to 4.4.2; then realized that it's really not worth the issues I'm dealing with in customizing the phone. I really regret doing this!!! I have no idea how to roll it back because when I do so in odin 3.07 or 3.09 with UVUEMK2 I have to reflash the "stock boot img" in order to get my S4 back alive as trying to roll it back that way "FAILS" in odin and breaks the stock boot and the phone asks me to plug it in and use kies to troubleshoot; when I just flash the bootloader and it's fine again.
ULTIMATELY:
1- Can ANYONE tell me how I can roll it back to 4.3 until I JUMP to my S5 in April?
2- If not how does one go about removing - ROOT - by Chainfire or CF-AutoRoot?
=> so I can at least trade in my phone for the 5 and be done with this mess in a month.
Reason I want 4.3 is because I had much more control over the system and was able to perform tethering tasks and APN tricks that have been blocked by the Kitkat update.
Thank you to whomever has the capacity to help me I've spent all day trying to figure it out and I have a 4 page grad paper I'm postponing because I gotta figure this out first, for some apparent reason. So any help APPRECIATED!!
I may be giving you bad news but last time I checked the ota notice said you cannot roll back ... I have yet yo see anyone roll back from KitKat official on the 9500
The new boot loader is pretty persistent at rollback prevention.
Sent from my Nexus 4 using Tapatalk
How about in terms of Unrooting? CF-Autoroot has the option in SuperUser app to unroot. I'm guessing this will do the trick for when I hand the phone back over to T-Mo? Or have they added things to circumvent removing SU?
I basically don't want to do it now (Figure out how to unroot) if I don't have to quite yet.
Gillion said:
I may be giving you bad news but last time I checked the ota notice said you cannot roll back ... I have yet yo see anyone roll back from KitKat official on the 9500
The new boot loader is pretty persistent at rollback prevention.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
zz1049 said:
Hey everyone,
1- Can ANYONE tell me how I can roll it back to 4.3 until I JUMP to my S5 in April?
2- If not how does one go about removing - ROOT - by Chainfire or CF-AutoRoot?
=> so I can at least trade in my phone for the 5 and be done with this mess in a month.
Reason I want 4.3 is because I had much more control over the system and was able to perform tethering tasks and APN tricks that have been blocked by the Kitkat update.
Click to expand...
Click to collapse
Once you have installed 4.4.2 with the matching boot loader, you cannot install 4.3 with Odin. However you can restore an Nandroid backup of your old 4.3 setup from recovery, so the phone will be back to how it was before the upgrade.
If you want to unroot, you can fire up SuperSU and select the "Full Unroot" option from the settings tab.
In order to restore APN settings on 4.4.2, I have always taken a backup of them on earlier versions using this great app:
https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore
In order to make it work on 4.4.2, you move the APK from /Data/App to /System/priv-app using Root Explorer or similar, then reboot. Disable the ICS check in the settings section of APNBackupRestore, and you're good to go!
For tethering by USB, this works very well for me:
https://play.google.com/store/apps/details?id=com.koushikdutta.tether
Good Luck!
Nandroid recovery
Hi VogonP0et,
I have a Sprint S4. I also upgraded OTA to 4.4.2 and am regretting it. I was not rooted when upgrading. Haven't been rooted for a few months. I do not like 4.4.2 restrictive sd card. Screwed up my Doc's to Go and Sygic nav.
I do have a nandroid recovery back up from last summer. MDL i believe.
Do I understand you correctly, I can root 4.4.2 reinstall TWRP. Then do a recovery back to my earlier version. Is this correct?
Thanks in advance.
Jim
Clean install rooted 4.4.2
BrickBait said:
Hi VogonP0et,
I have a Sprint S4. I also upgraded OTA to 4.4.2 and am regretting it. I was not rooted when upgrading. Haven't been rooted for a few months. I do not like 4.4.2 restrictive sd card. Screwed up my Doc's to Go and Sygic nav.
I do have a nandroid recovery back up from last summer. MDL i believe.
Do I understand you correctly, I can root 4.4.2 reinstall TWRP. Then do a recovery back to my earlier version. Is this correct?
Thanks in advance.
Jim
Click to expand...
Click to collapse
Hi Jim
You can only restore a 4.3 or 4.4.2 backup, not an earlier version.
I have an International i9505 jfltexx, although I believe the process would be the same for you. Here's what I did:
- Nandroid backup to the external SD card first job! Copy to the PC for safety.
- Power off the phone, and manually re-start in Download mode.
- Flash original factory KitKat 4.4.2 firmware of choice using Odin (I used V3.09), which will include the matching boot loader.
- Allow the phone to start up, which will take some time.
- Power off the phone, and manually re-start in Download mode.
- Use Chainfire's CF-Auto-Root to root it, using the Odin that comes in the package. Find it here (3rd post):
http://forum.xda-developers.com/showthread.php?t=2219803
- phone will re-start when the process is complete
- I did a full wipe at this point, and although it's a bit of a pain to restore all your data with Titanium backup it gives a problem-free start.
- Full wipe made my Sygic work properly again!
- Before you drop in a custom recovery, it is a good idea to use Chainfire's Triangle Away to reset the flash counter. It seems that the Flash Counter needs to be zero for successful operation of Mobile Odin in future.
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
- once you have set up your Google Play account, download SGS4Flasher here:
https://play.google.com/store/apps/details?id=nl.bvgemert.flasher
- SGS4Flasher will drop in the recovery of your choice. I use and recommend TWRP personally.
- You're good to go, and Flash Counter is still zero!
- Now you can restore an earlier Nandroid backup of a 4.3 ROM, or install a new custom 4.3 or 4.4.2 ROM
After this I installed the custom ROM of my choice, which is Echoe V16 based on 4.4.2. Echoe makes all the limitations and restrictions of 4.4.2 go away, but there must be a custom ROM suitable for you. I don't think you can use Echoe on your phone, but you may have a favourite. I have to say that doing the full wipe was an important step to make it all work well, so worth the hassle.
The only concern I have is that your backup at version at MDL may actually be Android 4.2, which I don't think you can use directly. However Titanium Backup can extract the data from a Nandroid backup to restore. I have spent quite a bit of time understanding the 4.4.2 limitations and restrictions, and found ways to make it do what I want now. Overall I'm happy, but it has taken some time to get there.
Good Luck!
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.