Related
I have ROM manager premium, and I just downloaded CM7 through it, and was about to flash it, but remembered I dont have s=off.
Also, I cannot get past this screen no matter what. htt p://img145.imageshack.us/i/20110222142411.jpg/
Any help will be appreaciated I really want to be able to run CM7
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
epsix said:
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Root access alone is not enough. You need S-Off as well.
jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
Is that why I always get this screen when I try to make a back up or boot into recovery.
jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
This Statement is correct.
jessek17 said:
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Click to expand...
Click to collapse
for short terms "s" Means security protocol. If your S=ON that means the phone will do a search each time you boot the phone on to see if anything as been tampered with. and if it has it will revert back to a factory status. Just like you first bought the phone. Which includes rooting, recovery images, boot images, engineering screens. What ever you do to your phone that isn't factory will be undone.
It is impossible to do. Because you need to flash the ROM from the recovery image. And since one you boot your phone it will replace Clockwork ROM manager with the factory style recovery image, you cannot not even get to the place you need to flash it from.
jessek17 said:
Is that why I always get this screen when I try to make a back up or boot into recovery.
Click to expand...
Click to collapse
Correct because you flashing the Clockwork Recovery image will not STICK unless you have s=off.
They system will replace the aftermarket image with the original EVERYTIME you turn off the phone.
That is the Stock Recovery. You need S-Off and ClockworkMod Recovery. And the right release of CWM Recovery, also. Use CWM Recovery 2.x to back up, restore, and install Android 2.2 (Froyo) based ROMs, including stock, and CWM Recovery 3.x to back up, restore, and install Android 2.3 (Gingerbread) based ROMs, such as CM7.
There is a special version of CWM Recovery that can manage both Froyo and Gingerbread ROMs: 3.0.0.6. Search for it in the Development subforum.
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
jessek17 said:
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
Click to expand...
Click to collapse
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
neidlinger said:
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
Click to expand...
Click to collapse
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
jessek17 said:
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
Click to expand...
Click to collapse
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
neidlinger said:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
Click to expand...
Click to collapse
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
jessek17 said:
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
Click to expand...
Click to collapse
That's kind of my point. People don't read.
If you take your time and read and do the entire process you won't have a problem. but you need to read all the way through something prior to jumping in the ring. There is a very strict set a rules that need to be followed.
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app
jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix
Hi all,
After deeply snorkeling in the whole forum I ended up realizing that (perhaps) there's no answer for my question. So, I think now I'm able to post it here (since I'm so new in this forum that I'm not able to post in Development thread).
Ok, here is my issue:
I recently got my brand new N716G (JB 4.2.1), so far so good it has everything I need, except by game playing experience in some games: using a touch screen for playing some games is really anoying... The good news is that my gamming experience could be improved a little bit if I use my PS3 joystick, but again I got frustrated by the (again) anoying USB cable... I didn't give up and continued my journey to joy, by doing some extra research. I ended up finding a really nice tool on google play: "sixaxis controller" but it is required to root my device in order to run this software in my N7.
Since I just want to root my N7 in order to allow "sixaxis controller" to work, I need something really simple.
I've found that "Asus google Nexus 7 Toolkit" from mskip could help me on this but I've to be honest: I've never rooted an android device before.
Of course, I read almost the whole thread (link) in order to learn what I'm going to do and now I'm pretty sure that I really need to root my tablet but I'm not interested (at least now) on putting a custom ROM nor tweak any configuration. Also, I want to keep my tablet stil able to keep updating by itself whenever a new android version is coming (OTA) after rooting it (I know I'd need to re root after OTA but I might avoid that by installing another tool from google play that avoids that).
So, by using that tool I guess I would need to perform the following steps:
a) 1. Install Google Nexus drivers on your PC
b) 2. Back up your device
c) 3. Unlock your loader
d) 4. Root your device
e) 4.2. Root device + Install busybox
f) 2. Restore backup
Steps a) and b) are done. I didn't continue because I don't know if there's something else I've to do... Do I really need to flash a recovery? How should I continue? In my specific case, what sequence should I have to follow in order to succeed? Just a,b,c,d,e,f and that's all?
I know there's a "1-click for all" option but I don't know if that will fit my needs...
By the way, thanks for reading up to here and many thanks in advance... For sure, any help or tip will be highly appreciated.
Nico.
easiest way to gain root, and without a toolkit.. fastboot oem unlock(unlocks the bootloader), fastboot flash a custom recovery, flash the su binaries in that custom recovery, reboot.
simms22 said:
easiest way to gain root, and without a toolkit.. fastboot oem unlock(unlocks the bootloader), fastboot flash a custom recovery, flash the su binaries in that custom recovery, reboot.
Click to expand...
Click to collapse
Hi simms22,
thank you for your reply!
Sorry but I don't understand. Do you mean that I can root my N7 manually by fastboot it and then flash a custom recovery? How?
I'd rather let an application (or script) to perform such actions for me since I'm really new on this and I just want to avoid any brick
Thanks again!
Nico.
IlNiCoLiNo said:
Hi simms22,
thank you for your reply!
Sorry but I don't understand. Do you mean that I can root my N7 manually by fastboot it and then flash a custom recovery? How?
I'd rather let an application (or script) to perform such actions for me since I'm really new on this and I just want to avoid any brick
Thanks again!
Nico.
Click to expand...
Click to collapse
thats the problem, since youre new. by letting something else do it for you, you learn nothing. so when it comes time for simple maintenance, you get stuck, possibly ruining your device. rooting any nexus is easy, it was designed to be easily "rooted". all you need is to install fastboot onto your computer, and make sure the drivers are installed. there are a few threads here that explain how to do it. then, with one line(three words), you unlock the bootloader. with another four word line you flash the recovery. then all youndo is flash the su binaries zip imnthat custom recovery and reboot. anyways, it still comes down to it being your choice how you want to root your device
Agree with simms. I used a toolkit when I first got my Nexus because I thought there's no way I'll be able to figure it out and I'll probably brick the thing. Then when I had to figure out how to use adb for something else I had no idea and was starting from scratch.
Basically, go ahead, it's easy.
+1 for no toolkit. My first rooting experience was on my HTC IncS which involved downgrading HBOOT, doing everything manually, and the like. I'm glad that was the case as it certainly provided me a challenge at the time but it forced me to learn at least the basics of adb and fastboot. (although I certainly know more now) You should try to gain root manually as it is actually very easy on the Nexus 7 and the basic knowledge you will gain will stand you in good stead if you ever have any problems or want to delve into custom ROMs or kernels in the future.
simms22 said:
thats the problem, since youre new. by letting something else do it for you, you learn nothing. so when it comes time for simple maintenance, you get stuck, possibly ruining your device. rooting any nexus is easy, it was designed to be easily "rooted". all you need is to install fastboot onto your computer, and make sure the drivers are installed. there are a few threads here that explain how to do it. then, with one line(three words), you unlock the bootloader. with another four word line you flash the recovery. then all youndo is flash the su binaries zip imnthat custom recovery and reboot. anyways, it still comes down to it being your choice how you want to root your device
Click to expand...
Click to collapse
You're right. I guess I'll give that tool a try and see what happens.
Thank you for your patience!
Nico
I'm going to throw one thing out there. If you install super user and busy box THEN restore a backup, all you have done is unlocked your boot loader and flashed custom recovery. Install super user/busy box after you restore your backup. Also, you posted in the right section. If you had posted this in development you would have been flamed. Big time.
Sent from my Nexus 7 using xda app-developers app
I think there are some basics that I must learn before even rise an opinion here
Is there any tutorial or something you'd recommend to start with?
I don't know, may be "android rooting for noobs" or "teach yourself android basics in 21 days"
Thanks!
Nico.
As a fellow noob, I thought you'd appreciate a simpler answer. I'd like to learn more but it can be confusing having all these different methods to consider. I've just unlocked the bootloader and rooted the device using the toolkit. You can go ahead with steps c, d, e & f Nico. You don't need to install a custom recovery unless you plan on flashing a custom rom. I'm sticking with the official OTA updates for now so I've stuck with the stock recovery.
Sent from my Nexus 7 using xda app-developers app
For future reference read all these links
http://forum.xda-developers.com/showthread.php?t=2070419
Used wugfresh toolkit with not one single problem and its simple...in fact I even rooted my galaxy nexus with the same toolkit.
Sent from my Nexus 7 using xda premium
FlexiPack said:
As a fellow noob, I thought you'd appreciate a simpler answer. I'd like to learn more but it can be confusing having all these different methods to consider. I've just unlocked the bootloader and rooted the device using the toolkit. You can go ahead with steps c, d, e & f Nico. You don't need to install a custom recovery unless you plan on flashing a custom rom. I'm sticking with the official OTA updates for now so I've stuck with the stock recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you, FlexiPack! You really made my day with your reply.
Regarding the back up, I was not able to back up the virtual SD from the back up menu (0 files were backed up) but I did a complete applications backup (including system files and SD card). I don't know what was the difference but at the end, the .bak file was noticeably bigger. Hence I assumed that in fact all SD contents were backed up.
How was your experience with the backup option and after restoring your data? Did you lost something?
Again, thank you!
Nico.
Hello there guys, I too am a utter android noob and this my my first android device. I'm basicly in the same boat as the poster, all I want to do is root. No custom ROM and flashing of any sort. All I want to accomplish is root to enable USB OTG.
I know there are apps that enable reading such as Nexus media importer but I want to be able to read and write data to external storage via USB (Flas drives, external hard drives and cameras and the sort)
What I've discovered the first big step (after installing drivers and the lot - which is all rather simple) is to unlock the bootloader if I'm correct? But in this process the device will format? I honestly dont want to format my device. I'm totally confused and put off by the whole process.
Another question, what is a good backup program to use - of course for unrooted devices.
Sent from my Nexus 7 using xda app-developers app
smartass145 said:
Hello there guys, I too am a utter android noob and this my my first android device. I'm basicly in the same boat as the poster, all I want to do is root. No custom ROM and flashing of any sort. All I want to accomplish is root to enable USB OTG.
I know there are apps that enable reading such as Nexus media importer but I want to be able to read and write data to external storage via USB (Flas drives, external hard drives and cameras and the sort)
What I've discovered the first big step (after installing drivers and the lot - which is all rather simple) is to unlock the bootloader if I'm correct? But in this process the device will format? I honestly dont want to format my device. I'm totally confused and put off by the whole process.
Another question, what is a good backup program to use - of course for unrooted devices.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Toolkit you can backup the whole thing to your comp
Sent from my Galaxy Nexus using xda app-developers app
VonEsch said:
Toolkit you can backup the whole thing to your comp
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Alright, and formatting to unlock the bootloader?
Sent from my Nexus 7 using xda app-developers app
This is kind of a rant but applies here: Don't be afraid to unlock, install custom recoveries, and root.
I hear so many people say, "I just want to be stock... but I want all these features". I can't understand why people hold on to this "stock" state so dearly. It's like device virginity (and it is since you "can't" [mentally] really ever go back). There are so many features and updates that are worth enjoying today. At least, a custom recovery is critical for backups.
I understand this stuff isn't for everybody... but if you are reading this, you aren't grouped with everybody.
player911 said:
This is kind of a rant but applies here: Don't be afraid to unlock, install custom recoveries, and root.
I hear so many people say, "I just want to be stock... but I want all these features". I can't understand why people hold on to this "stock" state so dearly. It's like device virginity (and it is since you "can't" [mentally] really ever go back). There are so many features and updates that are worth enjoying today. At least, a custom recovery is critical for backups.
I understand this stuff isn't for everybody... but if you are reading this, you aren't grouped with everybody.
Click to expand...
Click to collapse
For me vanilla android offers me everything I need at the moment. All I want more from it at the moment is USB OTG functionality - which it has its just been locked by Google for this device.
Sent from my Nexus 7 using xda app-developers app
For all people who call themselves noobs, you really aren't cuz you now know certain things better than the average user.
Trust me, I saw a Customer buying Note 2 today, and when the sales guy told him that it's jelly bean, the retort was "what's that!!!"
And yes, all nexus devices are the easiest lot to root, unroot, unlock and then relock.
Trust me, Google and xda are your best friends.
Just remember one thing, backup before anything, you can always revert then!!!
You guys (noobs as you yourself call) have already jumped, now swim...
One most important thing, search, read, and take the plunge...
All forums have at the least one tutorial stickied!!!
As regards adb, fastboot, google, read, and trust me, you'll not be stuck for more than an hour!!!
Just my 2 cents, actually more!!
Sent from my Galaxy Nexus using xda app-developers app
It really is like that. But once you start you can't stop. I started by rooting my original android phone ( there were no toolkits and no problems) and ended up with two nexus devices compiling unofficial nightlies for them. I didn't even boot stock on my 7 before I flashed twrp. There's a whole world of fun if you're willing to get your feet wet. If you can stop with just root you're a stronger person than I.
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