Firstly, huge props to all the devs here for making it possible for me to continue using my Note 3 the way I would prefer! The OTA downloaded to my phone and I wanted to avoid it. Being new to the root process, I spent several days reading here before getting my courage up, but I finally did it yesterday!
SM-N900V - MJE build now rooted via Vroot
SU replaced with SuperSU
Still running my stock 4.3 as I had no issues with it (as I become more comfortable with the process, I'll try other ROMs and perhaps the kitkat NC2, but I'm too green at the moment and would need hand-holding)
Now using Titanium Backup Pro and ES File Explorer
I have a few total N00B questions ...I could not find answers to in my searches, if someone would be so kind as to help (and please don't laugh )
1) USB debugging: do I leave it on or only turn it on when I need to do some type of operation, and if the latter, how will I know when to turn it on? Are there any risks to leaving it on?2) Security: unknown sources, I unchecked again after root. Any reason to keep it checked?3) Titanium Backup: Seems very complicated, but I did manage to freeze SDM. Any specific settings I should consider?4) How secure is root once it's done, is there anything that can undo it? Anything additional I should do to protect it?Thanks so much in advance for any additional guidance, I'm loving learning here!
Welcome to the world of phone freedom - it's a whole new world once you're out from under the thumb of Big Red...!
Your questions are all excellent and I'll give you my $0.03 (inflation, you know...):
1) TiBu requires USB debugging be enabled for proper functioning. I don't know why. But if you've not got it enabled, TiBu will throw up a splash screen warning you that it's not gonna be able to do what you want it to do.
2) No reason to keep unknown sources checked. A nice new process in one of the updates (don't know whether it's a Sammy thing or a 4.x.x thing) is that it will go back to unchecked when you side load (it'll flash a warning about unknown sources in setting when you try to side load and you've not checked ok to unknown sources. When you go to settings to allow the install, it'll have as default to go back to secure, not accept from unknown sources after this initial install - works very well). So just keep it off and you'll only check it when you need to. While it's not an issue just yet, this makes sure no one can install some malware without your doing the dumb thing and saying yes to it.
3) Use TiBu to make a schedule or two. I have it renew all my backups twice weekly. It's not something you HAVE to do, but if you want to wipe and flash, you've got access to you most recent apps and settings. Be sure to be careful with TiBu though - it's powerful and with that power, you can f*** your phone up pretty badly. I recently had a schedule to wipe cache 3x/week and it ended up killing my alarms... Try to explain to your boss your late because you're a geek...
4) Root is pretty secure. You can lose it in an update but assuming you've loaded MJE 4.3 and you're happy with that, you'll never lose root unless you purposely rescind it. You'll likely not if/when you update to 4.4 either but I've heard tales of people changing ROMs or updating and losing root. It's never happened to me but stranger things have, so I guess it's possible.
Welcome to the cutting edge! It's freaking awesome up here!
You just changed your smart phone to an effing genius phone! Congrats!
"I've got a revolution behind my eyes..."
--Battle Flag
lazarus0000 said:
Welcome to the world of phone freedom - it's a whole new world once you're out from under the thumb of Big Red...!
Your questions are all excellent and I'll give you my $0.03 (inflation, you know...):
1) TiBu requires USB debugging be enabled for proper functioning. I don't know why. But if you've not got it enabled, TiBu will throw up a splash screen warning you that it's not gonna be able to do what you want it to do.
2) No reason to keep unknown sources checked. A nice new process in one of the updates (don't know whether it's a Sammy thing or a 4.x.x thing) is that it will go back to unchecked when you side load (it'll flash a warning about unknown sources in setting when you try to side load and you've not checked ok to unknown sources. When you go to settings to allow the install, it'll have as default to go back to secure, not accept from unknown sources after this initial install - works very well). So just keep it off and you'll only check it when you need to. While it's not an issue just yet, this makes sure no one can install some malware without your doing the dumb thing and saying yes to it.
3) Use TiBu to make a schedule or two. I have it renew all my backups twice weekly. It's not something you HAVE to do, but if you want to wipe and flash, you've got access to you most recent apps and settings. Be sure to be careful with TiBu though - it's powerful and with that power, you can f*** your phone up pretty badly. I recently had a schedule to wipe cache 3x/week and it ended up killing my alarms... Try to explain to your boss your late because you're a geek...
4) Root is pretty secure. You can lose it in an update but assuming you've loaded MJE 4.3 and you're happy with that, you'll never lose root unless you purposely rescind it. You'll likely not if/when you update to 4.4 either but I've heard tales of people changing ROMs or updating and losing root. It's never happened to me but stranger things have, so I guess it's possible.
Welcome to the cutting edge! It's freaking awesome up here!
You just changed your smart phone to an effing genius phone! Congrats!
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
Thank you so kindly for your excellent and thorough response! (Please forgive my rude delay in replying back, I have been slammed planning for a month long road trip)
I'm relieved to know my questions weren't silly ones; I figure if it's a question in my mind, it may help others as well. For now the only added benefit I have experienced with root is avoiding the kitkat upgrade and ridding myself of that dang nag screen, but this alone is enough to thrill me! When I return from my travels, I look forward to seeing what more this "genius phone" of mine can do!
Related
You guys must be tired of people asking the same over and over, and to be honest that is because information is so scattered newcomers often get confused.
But Anyways.
I've got myself a motorila Droid 2 a few days ago, poking around internet i found about rooting and roms and all that stuff, however I've got a question that's yet to be answered!
I'm currently residing in Mexico, my Droid 2 is unlocked and activated on a mexican carrier, however on the guides I've red so far it says that one of the requirements for installing custom ROM's one must wipe all data from the phone and return to factory settings, this means i will have to pay AGAIN to get it unlocked and activated?
As i said before, information is scattered, and is not always accuarate.
Somewhere on the net i also found a post that states customs ROM's come unlocked... whats with that?
And one last question.
What will happen if i only root my phone, no custom rom added? will this be harmful in any way? could i be able to overclock and get rid of the annoying verizon apps or do i forcefully need to install a custom ROM?
Thanks for all answers in advance.
Rooting itself would not harm your device, however rooting allows you to do pretty much anything on the device. So, in other words, rooting wont hurt it, however what it allows you to do CAN hurt it.
As far as the roms being unlocked, as far as I have read, all roms are unlocked. However I could be mistaken. But there is an easy way to find out for sure: give it a try. What I would do first root the device and install the Clockwork Recovery Mod and then boot into recovery and make a backup. This way you can restore the phone back exactly as it was when you backed it up (using the restore option), as if you never made any changes. Then I would go ahead and install whatever rom you wanted to try out, and see if everything works as intended. If you dont like it, or it doesnt allow you to access the network, etc then all you need to do is boot back to recovery and restore your backup and when it's done you'll phone will be back to it's old self.
Links:
Root: http://forum.xda-developers.com/showthread.php?t=782556 (This is the process I used)
Clockwork: http://www.addictivetips.com/mobile/how-to-install-clockwork-recovery-to-your-android-phone/
Not sure how experienced you are - or aren't - so if you have any deeper questions about the process or need more detailed instructions just let me know.
EDIT: Oops, I completely skipped some of your questions. With just rooting you can uninstall SOME of the preloaded crap, however there is allot of the preloaded applications and such that you cant uninstall without crippling your phones functionality. My originally plan when I first rooted my device was just to remove the bloatware. However after I saw just how much there was I couldn't remove I decided to jump to a custom ROM. Just to give you an example, I have the Fission ROM installed on my device, and it's packaged filed were about 70ish mb, while the packaged files to restore it back to stock/factory was nearly 300mb. And yes, rooting alone would allow you to overclock your phone.
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
RoboCuz said:
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
Click to expand...
Click to collapse
Why not just unroot get the OTA and reboot? It's so easy with the toolkit you could even relock and unlock at the same time if necessary
Sent from my Nexus 7 using Tapatalk 2
That's a good idea...I guess I hadn't thought of that...but unlocking and relocking would wipe the device, no? If I am going to wipe the device to get the OTA, then I would just proceed through the "normal" way of waiting for someone to release the update in a ROM and flash it. I would just like, in some way, to treat this device like an appliance, and not worry about OTAs bricking my phone, or needing to reinstall everything to get the latest...I just want to start off restoring some of my apps from another device, and then (maybe) just let the updates take their course. I know I could change my mind later and start ROMing, but I just wanted to understand my options....I know I wipe the device when I unlock, so assumed that would happen each time. And I wasn't sure if I needed to unlock to JUST get root, if I am not planning on flashing ROMs. And can I just root,and then use OTA rootkeeper if necessary, and allow updates?
So I guess the questions are:
- Do I need to unlock to root?
- Once I have done what I need to use Titanium (unlock and root or just root), can I take an OTA update, or do I need to undo some or all?
- If I undo some or all, will that incur a wipe?
I think I figured this out...I found the manual for the Nexus Root Toolkit (www.wugfresh.com/dev/nexus-root-toolkit/), and that spells out a LOT of really clear information.
I think I would:
- unlock
- root and install CWM
- use Titanium, etc.
Later, if an OTA comes out I want to allow:
- probably do full CWM backup
- flash stock recovery
- install and run OTA Rootkeeper
- allow the OTA, knowing I might loose root
- reflash CWM
I think this shouldn't cause any issues. This assumes I am basically running stock, and just using root for backup/restore app stuff with Titanium and maybe Root Explorer.
Make sense?
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
I ve rooted s3s note 2 etc... BUt I just tried to root my GS4 on Sprint, and it said write protected, now even though I was able to install super user on the device but it isn't working properly, and I cant flash any rom's any advice would be very much appreciated, I also noticed when I out the device into download mode to push cwm recovery it said write protection enabled, how can I disable this. thanx ahead XDA members...:fingers-crossed:
Are you on MF9 or MDL?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Mf9
Sent from my SPH-L720 using Tapatalk 4
Which root method did you use?
Sent from my SPH-L720 using xda app-developers app
I don't know how members mess up rooting a device. We have great and VERY easy methods. Plus tutorial vids from QBKing77.
Sent from my SPH-L720 using Tapatalk 4
You're supposed to use ChainFire's auto root method: CF-auto-root
Sent from my SPH-L720 using XDA Premium 4 mobile app
PearlS4 said:
I ve rooted s3s note 2 etc... BUt I just tried to root my GS4 on Sprint, and it said write protected, now even though I was able to install super user on the device but it isn't working properly, and I cant flash any rom's any advice would be very much appreciated, I also noticed when I out the device into download mode to push cwm recovery it said write protection enabled, how can I disable this. thanx ahead XDA members...:fingers-crossed:
Click to expand...
Click to collapse
The write protect is normal and does not impact rooting or flashing anything. So any issues you are having are unrelated. It would be a problem with something you installed or are trying to install.
As Salil999 said, cf auto is the preferred rooting method if you aren't installing an already rooted Rom.
Sent from my SPH-L720 using Tapatalk 4
an updated method/step by step procedure "how to root" IS really needed.
Salil999 said:
You're supposed to use ChainFire's auto root method: CF-auto-root
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
(Sorry but this is NOT directed at you i am simply quoting to prove a point)
This is something I have had an issue with as well. Despite how easy it might be for most not everyone catches on as quickly because of common misconceptions or how they might perceive the information because everyones mind works differently. I have used the CF root method and it is NOT the best method to use considering even after I used it i still had NO root. Top that off and add the fact that i even downgraded the version I had several times and i have searched countless times how to do a manual root and just havent had the time to complete a full root. Not everyone has the option to tinker all day (not saying that you do) to understand or figure it out IE real life - kids work school etc. what ever the case is. I have flashed a bootloader several times after establishing root to do nandroid backups/iso imgs and actually completed several come to find out that for some reason my Root did not stick at all when i had thought it did and i followed everything many times step by step to no avail achieve a permanent root. There is a problem with the process and I am sorry but everyone else that has gotten root is just fortunate the latest update has really put a damper on doing root the way it is described and is NOT current to fit everyones needs ATM. I am sure there are MANY others like the OP myself and others that are having the SAME EXACT ISSUE. I am not new to ADB and have been rooting my phones since the HTC came out with the original Supersonic Evo 4G using the ADB method and some people without providing any options just have to think that because some of us are having problems that we (or I) are not "intelligent" enough to figure it out and i have worked with computers since windows for workgroups 3.11 and construct my own Gaming RIGs, Servers, Laptops (and phones recently as of the last 2+ years) never having any issues because its just second nature to me at times with PCs and Laptops. Phones on the other hand are much more complicated because of incompatibility issues with OTA updates from the manufactures and cellular service providers either because they dont want people messing with their brands and wish to be a pain in the butt for whatever the reason, financial or whatnot. I am seeing it ALL over XDA for Sprint Users mostly since thats where i am confining my search patterns. I am actually going through ADB to manually archive root because im tired of searching through countless postings to find nothing on the subject and do not enjoy the dumb comments people think they have to leave on my post and others posters. Im sure im going to get a stupid comment or a flame of some type because even when im just "venting" at my frustrations as im sure everyone does from time to time no one enjoys being messed with when they are already pissed off and frustrated that just makes matters worse for the OP and the community. Eventually the problem works itself out, but c'mon people, seriously not everyone gets to have the opportunity to get the root achieved right because of the stupid OTAs released time and time again that make the latest root option obsolete because thats what it IS RIGHT NOW OBSOLETE. It is being a pain in my ass because KNOX was tripped with a custom rom and even though the custom ROM sticked the ROOT DID NOT. they (cell manufactures or providers) prevent rooting in the first place by ADDING additional roadblocks in OTAs just to slow down/prevent users or people that enjoy the ability of having the option to use root to their technical advantages (because they lose money, which really is more profit on top of original costs inflated to a ridiculous amounts not fair to consumers). Even with development, future development, paying employees, etc. its not even close to being fairly priced market for consumers and already the rate are increasing at a rate to costly and unfair to consumers with little to no option of maxing the potential life of a product. I dont know about everyone but not all can afford to keep updated with the latest gear. We have great developers that probably get no where NEAR the amount of donations that they SHOULD be receiving to keep up when they are devoting their own personal time and currency to making apps and ROMs but the fact remains that it is easier for a huge company to crank out software because they PAY people to do it knowing that freeware developers are not going to have the time or resources to keep up. If anyone knows of an updated method or a manual method to root or another option the help is very much appreciated by myself others and the OP. Thank you to the people that have taken the time to help everyone else in a positive manor.
VenomousViper said:
(Sorry but this is NOT directed at you i am simply quoting to prove a point)
This is something I have had an issue with as well. Despite how easy it might be for most not everyone catches on as quickly because of common misconceptions or how they might perceive the information because everyones mind works differently. I have used the CF root method and it is NOT the best method to use considering even after I used it i still had NO root. Top that off and add the fact that i even downgraded the version I had several times and i have searched countless times how to do a manual root and just havent had the time to complete a full root. Not everyone has the option to tinker all day (not saying that you do) to understand or figure it out IE real life - kids work school etc. what ever the case is. I have flashed a bootloader several times after establishing root to do nandroid backups/iso imgs and actually completed several come to find out that for some reason my Root did not stick at all when i had thought it did and i followed everything many times step by step to no avail achieve a permanent root. There is a problem with the process and I am sorry but everyone else that has gotten root is just fortunate the latest update has really put a damper on doing root the way it is described and is NOT current to fit everyones needs ATM. I am sure there are MANY others like the OP myself and others that are having the SAME EXACT ISSUE. I am not new to ADB and have been rooting my phones since the HTC came out with the original Supersonic Evo 4G using the ADB method and some people without providing any options just have to think that because some of us are having problems that we (or I) are not "intelligent" enough to figure it out and i have worked with computers since windows for workgroups 3.11 and construct my own Gaming RIGs, Servers, Laptops (and phones recently as of the last 2+ years) never having any issues because its just second nature to me at times with PCs and Laptops. Phones on the other hand are much more complicated because of incompatibility issues with OTA updates from the manufactures and cellular service providers either because they dont want people messing with their brands and wish to be a pain in the butt for whatever the reason, financial or whatnot. I am seeing it ALL over XDA for Sprint Users mostly since thats where i am confining my search patterns. I am actually going through ADB to manually archive root because im tired of searching through countless postings to find nothing on the subject and do not enjoy the dumb comments people think they have to leave on my post and others posters. Im sure im going to get a stupid comment or a flame of some type because even when im just "venting" at my frustrations as im sure everyone does from time to time no one enjoys being messed with when they are already pissed off and frustrated that just makes matters worse for the OP and the community. Eventually the problem works itself out, but c'mon people, seriously not everyone gets to have the opportunity to get the root achieved right because of the stupid OTAs released time and time again that make the latest root option obsolete because thats what it IS RIGHT NOW OBSOLETE. It is being a pain in my ass because KNOX was tripped with a custom rom and even though the custom ROM sticked the ROOT DID NOT. they (cell manufactures or providers) prevent rooting in the first place by ADDING additional roadblocks in OTAs just to slow down/prevent users or people that enjoy the ability of having the option to use root to their technical advantages (because they lose money, which really is more profit on top of original costs inflated to a ridiculous amounts not fair to consumers). Even with development, future development, paying employees, etc. its not even close to being fairly priced market for consumers and already the rate are increasing at a rate to costly and unfair to consumers with little to no option of maxing the potential life of a product. I dont know about everyone but not all can afford to keep updated with the latest gear. We have great developers that probably get no where NEAR the amount of donations that they SHOULD be receiving to keep up when they are devoting their own personal time and currency to making apps and ROMs but the fact remains that it is easier for a huge company to crank out software because they PAY people to do it knowing that freeware developers are not going to have the time or resources to keep up. If anyone knows of an updated method or a manual method to root or another option the help is very much appreciated by myself others and the OP. Thank you to the people that have taken the time to help everyone else in a positive manor.
Click to expand...
Click to collapse
Wow, sounds like you are having a bad day. Not trying to piss you off or anything. But cf autoroot works, and works very well. And all knox does is trigger a warranty flag that can not be reset and limits you going backwards on firmware. It doesn't do anything to prevent rooting. I think the best method for you would be to reset and start with a clean phone. By reset, I mean downloading and installing the full MJA tar file and doing a factory reset. This way you have a clean phone with nothing that might be blocking your rooting process. Next, grab cf autoroot and make sure you are using a newer version of odin. I use odin3 ver. 3.07. Run cf autoroot and let it boot all the way up. Now go into your app drawer and see if supersu is installed. If it isn't install it from the play store. Open cf autoroot and install the binaries, use the normal button. Now, if it errors on the binary install don't panic. Redo the cf autoroot and repeat the install of supersu again if it is not in the app drawer. If it is in the app drawer open it and install the binaries if it asks. It's basically a rinse and repeat operation. On MJA it sometimes takes a few attempts for it to stick. After you successfully have root, then use goo manager to install twrp or install the latest philz recovery. It takes a little patience but cf autoroot does work, and it is the best method available. Remember, starting with a clean slate is best. And if you want to be the most up to date, take the MK2 OTA before you start the root process. CF autoroot works on MK2 also.
Thanks for the useful help
cruise350 said:
Wow, sounds like you are having a bad day. Not trying to piss you off or anything. But cf autoroot works, and works very well. And all knox does is trigger a warranty flag that can not be reset and limits you going backwards on firmware. It doesn't do anything to prevent rooting. I think the best method for you would be to reset and start with a clean phone. By reset, I mean downloading and installing the full MJA tar file and doing a factory reset. This way you have a clean phone with nothing that might be blocking your rooting process. Next, grab cf autoroot and make sure you are using a newer version of odin. I use odin3 ver. 3.07. Run cf autoroot and let it boot all the way up. Now go into your app drawer and see if supersu is installed. If it isn't install it from the play store. Open cf autoroot and install the binaries, use the normal button. Now, if it errors on the binary install don't panic. Redo the cf autoroot and repeat the install of supersu again if it is not in the app drawer. If it is in the app drawer open it and install the binaries if it asks. It's basically a rinse and repeat operation. On MJA it sometimes takes a few attempts for it to stick. After you successfully have root, then use goo manager to install twrp or install the latest philz recovery. It takes a little patience but cf autoroot does work, and it is the best method available. Remember, starting with a clean slate is best. And if you want to be the most up to date, take the MK2 OTA before you start the root process. CF autoroot works on MK2 also.
Click to expand...
Click to collapse
No Sir, not pissed off and maybe what i wrote was misconstrued since I left out some pertinent information listed here now... very pleased with your answer. Probably some of the most productive and useful information thus far and the best I have received/come across yet. I was currently trying to update the post when I saw your comment to me. I had failed to mention some important facts to include what I have had successfully completed listed down here:
KNOX tripped of course 0x30 Custom ROM via Odin Flashed/Stuck; MDC/MDL downgraded from a MF9 Baseband Modem Flashed via Odin/Stuck; Custom Recovery CWM 6.0.6.6 touch Flashed via Oden/Stuck PASSED; Root I HAVE TRYED MANY DIFFERENT WAYS POSTED VIA POSTS ON THE SPRINT COMMUNITY and FAILED TO KEEP ROOT. HOWEVER, it was succesful according to ODIN 1.85 & 3.07 many times over and over with CF-Auto-Root it stated as it PASSED via Odin... DID NOT STICK OR STAY when the reboot restarted the phone and loaded the Custom ROM every time I look up with root checker as stated still NO ROOT!
There isn't much I can possibly be missing but I am hoping there is some kind of solution via information you have provided by MK2 OTA root
I certainly am going to try posting all of this information for others to see in an easier to read/find post to benefit the community sometime before the new year. I was able to gain more by reading the posts to Unlock SIM which helped a lot since it was a refresher on ADB commands/steps for me.
Thanks again. i will update as soon as I figure it out or do not figure it out.
I LOVE YOU!!!! I feel the same way. Like im smart ok i am not near as knowledgeable as u r but i have messed with phones since iphone 3g came out and since the first ibm desktop cost 4000.00 lmao my dad and i are alike in that we cant just leave **** alone lol i dont understand a damn bit of what these posts say. Sometimes u have someone who has no knowledge of how these damn phones work mentally but u give me one i can tear it appart and fix anything on it even waterdamage thats my favorite. But no one tells you what these files are what they do and why u want it and then in like odin what the abrev mean what file goes there and why like if a rom is basicay windows but custom what slot does it go in then what are the rest for? Do u need to fill all or just one u need, why? Would it mess it up, why will one mess it up n the other not? What is this mk9 bs and how do i know what mine is? Ya know and im a single mom with 2 kids and my phone is important and the damn thing is stuck cause its update jacked up and now its in a boot loop and i cant get it out. It wont recongnize it in kies it wont take the md5 update through odin it wont even let me get to the menu that lets me clear cache or factory reset it. Ive done all sorts n got no where.
I've been rooting devices since my first android device. And using Titanium Backup, to always restore my app data across devices. Or restoring Nandroid backups at times. But it seems with that, upgrades to new OS have become more of a hassle. Since I can not simply let the OTA apply its self.
Having to change to stock recovery depending on the device and in some more recent cases, having to wipe data for the update to go well. It has become a bit of a pain, harder than it used to be.
With Marshmellow doing app data backup. I'm going to try keeping things virgin, no rooting. I may not need to continue with Titanium Backup and since OTAs will work flawlessly, I won't have much personal need to get into the system file area.
So what about you? Respond to the poll and give your take .
I've always done clean install of ROMs, and I always start from scratch with each ROM flash. I'll root as soon as there's a root out.
I mistakenly marked "Yes" to my poll .
Sent from my Nexus 10 using Tapatalk
Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.
rockerrock said:
Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.
Click to expand...
Click to collapse
+1. I got rid of my Verizon S6 because it was way too locked down.
lol asking this on a dev forum... I'd be surprised if anyone says no. It's more than just app back ups. I think phone should ship with root, just enable it/ disable it in the development options. It's like being a standard user on your own laptop instead of administrator... I mean why?
I can see this option on Nexus devices and non-carrier branded devices, but it would never be allowed with a Carrier device. It would be like a work laptop being allowed on that network with software meant to bypass firewalls. Bigger companies will never allow it because of security risks. That being said, I do agree that it should be an option for everyday users.