What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Most of the root methods involve unlocking the bootloader with the "fastboot oem unlock" command as the first step.
That's the command that erases your phone.
Any method that has you do that command will erase your phone.
If the method above works as expected, it will root you without erasing your phone. Shrivelfig did it without harm to his phone, but he had already been rooted the old-fashioned way.
I would certainly backup my data that I could before doing any root method, but this one seems like it's 99% safe.
Use at own risk, of course, but that's true of all the methods.
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
distortedloop said:
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
Click to expand...
Click to collapse
Your the man thanks bro I'll let you know if it works. Hope my phone doesn't crash on me
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
B3arfruit said:
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
Click to expand...
Click to collapse
You're putting the phone in fastboot mode? It's got the white screen?
You're using the proper commands fastboot? What message does your computer show? Are you Win, Mac, or Linux?
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
Just tried it on a new Nexus S, worked perfectly
I rooted using this method last night. From start to finish, 10 minutes. I have full root capabilities.
Sent from my Nexus S using XDA App
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
zorak950 said:
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
Click to expand...
Click to collapse
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
kenvan19 said:
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
Click to expand...
Click to collapse
Because it's the fastest, cleanest, most up-to-date Android device of its class on the market. Custom ROMS are all well and good, but they're hardly the only reason to get the phone. Indeed, there are a ton of phones out there with arguably equal or better third-party ROM options at present. Anyway, to say Google designed the NS to be hacked to pieces is perhaps a bit of an overstatement; to my knowledge all they said is that they deliberately left open a way to root the phone, and even at that, it wasn't exactly a consumer marketing point.
Not that I'm badmouthing rooting, installing custom ROMS, or whatever else people do to their phones. On the contrary, I think it's fantastic. But ultimately, I object to the idea that there's a "wrong" choice when it comes to making those modifications. Different people have different priorities, concerns, and levels of comfort with various procedures, and the NS is a great phone no matter what you choose to run on it. I'm probably on the low end of the spectrum with respect to my interest and comfort in modding as far as people who post with any regularity on these forums go, but bear in mind I'm also probably a great deal more engaged with it than the majority of users, many of which may not even make full use of their phone's basic features, let alone think to try making their phone do anything that the top-layer UI doesn't facilitate.
Clockwork link not working
suhas_sm said:
Clockwork link not working
Click to expand...
Click to collapse
Try this one: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.5-crespo.img
or go straight to koush's blog: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
worked for me as well, on 2.3.2 without erasing anything.
thanks!
I concurr, the nowipe method works here (UK SNS fro Carphone Warehouse on 2.3.2).
All we need now is google to fix the issues (rebooting in particular).
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Paparasee said:
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Click to expand...
Click to collapse
It works. Try it. Full thread on it that I'll update as things change here.
Paparasee said:
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
Click to expand...
Click to collapse
We won't know for sure until the 2.3.3 update comes out and we can examine its contents and what it does. There's no reason to expect that Google will do much differently in terms of the bootloader or recovery than they have in the last two updates, especially since they've said in the Google blog that the NS was designed to be easily unlocked and rooted.
In the prior two OTA updates, you could update with no issues other than your root being broken, but it was as easy as just rebooting into clockwork and reinstalling the su update zip.
The only people who had issues updating prior OTAs after this kind of root were folks who had messed around with applications in the /system folder (such as replacing the Market or Gmail apps with some modded one). That can be worked around easily and is discussed numerous times in a couple of threads.
Paparasee said:
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Click to expand...
Click to collapse
All rooting with this method does is add the su binary to /system/bin, the superuser.apk file to /data/app and change permissions on /system/bin. If you install busybox (which you really need to do for root to be most effective) it will add it's own files and some symlinks.
Several easy ways to reverse the process:
Restore/flash a nandroid or stock rom image that's not rooted. (Try making one after getting into Clockwork and before flashing su-update.zip.)
Use terminal/adb, the Settings/Applications app or the Market to rm and/or uninstall the su binary, the busybox install, and the superuser.apk as well as any root-enabled apps you installed.
There's more details if you need them in another thread here or Q&A section. You should be able to find them with a search on the terms "rm /system/bin/ root".
Related
i run unrevoked and nothing happens. this a new problem with the new update? this is my replacement phone anwaysy so.
anyone know anyways to root? i can't downgrade to old version. please help..
if you have s-off you just need to flash a custom recovery.
if you don't then i have no idea if the updated rom is rootable.
that would have been something to look for before upgrading
Good luck!
Having custom recovery is not the same as rooting (Superuser acess). Unfortunately, at the moment, Unrevoked won't work on the new OTA and if you install SU pack after the OTA it will just hang during boot up and you'll be in reboot hell. You can have Clockwork with the new OTA, just not root access.
downgrading to stock then s-off and upgrading work?
update. i tried downloading the super back to stock thread and the hboot says the file is older and i can't by pass it.. so hmm
I am in the same boat. Just got the phone and the f-ing salesman decided to install the OTA for me while he was setting it up. So do I return this thing in the hopes of getting one without the OTA or is it likely it will be rooted?
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
dadsterflip said:
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
Click to expand...
Click to collapse
Nope, can't downgrade...I'm out of ideas. Pretty pissed off actually to the point where I'm ready to take it back and get one that doesn't have the god damn OTA applied. I HATE owning devices that I don't really own.
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
caleris said:
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
Click to expand...
Click to collapse
press Volume Up + Power I think when you see the triangle
magneticzero said:
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
Click to expand...
Click to collapse
But???????????? This will only work if you are already s-off, correct?
blackwolf77 said:
But???????????? This will only work if you are already s-off, correct?
Click to expand...
Click to collapse
if you have clockwork mod installed with S-On and updated the ota already, you can flash unrevoked forever through clockwork recovery... that will take S-Off to off. I was messing around earlier and did that..
I am not sure how you got clockwork installed. Everytime I try it recognizes the PB31IMG and then just skips over it. It never asks about installing it.
The file name has to be PB31IMG.ZIP right? Also the LCD works different right?
SLCD PB31IMG.ZIP
Sent from my ADR6300 using XDA App
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Nitrogenus said:
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Click to expand...
Click to collapse
in for answer
tried it out, didn't work. the su trick with rageagainstthecage-arm5.bin does not work.
how to see page 3
Standing by!!!!! Will it work with s-on?
It shouldn't matter s-on or off. I have the SLCD screen don't know if it will make a difference. Just FYI
Sent from my ADR6300 using XDA App
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
geronimo711 said:
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
Click to expand...
Click to collapse
What is the end result you are trying to get to?
If you are wanting S=off so you can flash custom ROMs.
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/; do that and it will lead you to perma root the easy way.
if you are wanting s=off so you can have complete control over your phone, which will enable the possibility of a brick. including SuperCID, ./gfree and some other goodies...... But this will give you the option to severally screw up your phone including up to a 500.00 paper weight.
http://forum.xda-developers.com/showthread.php?t=858996
If you haven't screwed up the HBoot and the bootloader you can use this to get back to a factory spec.
http://forum.xda-developers.com/showthread.php?t=863899&highlight=level
But if this is your first android, and your first time rooting i would HIGHLY suggest doing alot of reading before you jump in head first. There are alot of people who have tried to do and get stuck. This phone is confusing once rooted with 2.2 ROMs and 2.3 ROMs and different recovery images you need to read and make sure you understand everything before jumping in feet first.
Temp root with visionary is the easiest and safest way, but gfree is pretty simple as well. The hardest bit is getting the drivers and ADB to work, and thats not overly difficult. (remember to use the command "ADB devices" to know if the drives are working) It just matters what you plan on doing, stock root or custom ROM.
There is really only two points that risk a hard brick, flashing the radio or hboot.
The gfree method does not require either, but you can flash the engineering hboot as optional.
The biggest thing with recoveries and ROMs is know that gingerbread based ROMs (like CM7) use ext4 file system and froyo ROMs use ext3. So it is important to use the right version of Clockwork recovery. Use v2.5.1.2 for froyo ROMs and v3.0 for gingerbread ROMs. Soon clockwork mod will support both on the same version.
Just read the instructions well and have all files downloaded and ready to go.
If you want to use gfree and a custom ROM, there is no need to get perm root on the stock ROM first. After the steps that get s=off, just run visionary as temp root with system r/w access and install ROM manager from the market, then use ROM manager to flash a new recovery. Reboot into recovery backup your stock ROM then flash a new ROM.
If you never touch the hboot or radio firmware, then at worse you can bootloop or soft brick the device. That can be fixed with varying amounts of work, depending on the exact issue.
Read and learn how the different parts work, learn how to use ADB and you will be better prepared.
newbie here
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
ibnird said:
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
Click to expand...
Click to collapse
Temp root is just that, temporary. It creates a copy of the essential files in the system partition that it runs from rather than the actual system partition. If you allow it r/w access, (an option you can choose when using visionary) it can uninstall apps that normally can not be. (and more, but causing big changes would require more work on your part)
Because it is temporary, there is no need to get nervous. Unless you are doing some major changes, ones that need a root explorer app or terminal emulator, then you can't really hurt the phone. Download terminal emulator from market and run it, then type in the super user command "su" (no quotes) then hit enter, if the cursor changes to a # symbol then you have root. (you may get a popup asking for root permission, choose to allow) If it works after a fresh reboot, you either ran perm root in visionary, or you have the option checked to temp root every reboot.
S-ON means that the bootloader security is still in place. You need it off to install custom software. While you can root the stock software with S-ON you can not install any software that has potential to brick your phone, so no need to worry at all. If you are really that worried, keep a copy of the stock software on your SD card. Make sure it is named PD15IMG and at any time you get nervous, you can boot into hboot (the bootloader) and it will run automatically. It will wipe your phone and return it to complete stock. The irony is, that flashing this stock image file does things that can brick a phone if it goes wrong. It flashes more than just the OS, it also flashes hboot and recovery as well, and if the process is messed up in anyway like loosing power at the wrong time, it can brick the phone.
Really as long as you make sure you have the phone charged and you follow instructions you should be fine. The only times you can brick a phone to the point it can not be brought back is when flashing hboot and the radio firmware. Both of which you would rarely flash. Hboot only needs flashed to the engineering version once (OEM testing/DEV version) and only if you choose to, as it is not required. The radio will only need flashed if an update for it comes out, and that isn't often, and it is rarely mandatory.
The chance of truly bricking your phone is not very high, unless you just can't follow the directions. Now you can put it into a bootloop or soft brick it. (bootup stuck on mytouch screen) But if you can boot the phone into hboot (vol down + power on) then you can fix it. Even if you can not boot into recovery (an option in the hboot menu) you can even fix that with a good hboot.
theres a video on youtube by mackster its awesome and it gives you all the links very easy to use.
it wont let me post the link but just search root mytouch 4g on youtube and it should be the first or second one.
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
ibnird said:
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
Click to expand...
Click to collapse
Uninstalling an app will not hurt anything. OTA updates will still work fine. You can temp root and then perm root the stock ROM and revert easily. Heck, even perm rooting stock doesn't break OTA I believe.
Voiding the warranty is one of those grey areas. As long as you can revert to stock, then they will never know. Temp root does not void warranty at all, because you do not alter the system files. (unless you want to, and enable the ability to read/write system) Just uninstall terminal emulator and super user apps and there is no evidence.
The only time you might get caught, is if say the screen stops working, and you can not see to revert back. Though even then, just putting the stock OTA image on the sd card then booting up the phone in hboot will restore without needing to actually see anything. It does ask for confirmation to restore, just wait several minutes then hit the power button and it would do it on its own.
The set of circumstances needed to prevent you from restoring to stock, are rare. Basically a borked hboot or radio firmware, and you never need to touch those to get full root and custom ROMs. If you never touch them, the chance of issue is almost zero.
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
goldfish524 said:
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
Click to expand...
Click to collapse
You dont need apps2sd, as the mytouch 4g has Froyo installed, and you can move some apps to the SD card. Just go into settings-Applications-chose the applicaiton you want on your SD card, and look for "move to SD". If it's grayed out, then you cant move it.
Also download appfreezer from the market, and just "freeze" the bloatware. That's what I do, and it gets rid of those annoying looking apps they installed.
Question about clockworkmod
OK i just rooted my phone, flashed the rom, and installed all the goods... it works perfectly and looks great.
Ty for all the guides/ instructions.
My only question is about the clockworkmod. When I turn off my phone and plug it in to charge the recovery screen always appears when off and connected. Is this suppose to happen? Or is there a solution to this?
If there is a solution can some one post a link or provide instructions so it doesn't constantly boot to clockworkmod recovery.
Thanks.
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.
Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.
Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!
Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.
With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.
Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?
Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.
This method uses KINGROOT, no mingling with the bootloader.
STEP 1
Just google "kingroot" (kingroot.net) and dowload the latest apk, open the app and after the initial welcome screens click on the button in the bottom that says "TRY IT", give it some time 4-5 minutes.
Thats it, your device is rooted, just like that.
BENEFITS OF THIS METHOD.
Since you have not unlocked the bootloader once you choose to unroot the device(why would anyone ) no one will be able to tell if you actually rooted the device.
RECOMMENDED (Like seriously recommended)
Once you get the root access install the app "Partitions Backup" by the one and only "wanam" and backup the partitions highlighted in yellow(at least these three modem, modemst1 and modemst2) these are your devices efs partitions. They will be the only thing that will save a lot of trouble if you manage to corrupt your efs partitions(I've been there people, trust me not a pretty situation!:crying, copy these safely to your ext sd, computer, email yourself a compressed copy(this way The NSA will also get a copy which they off course never looked into, so now it's like completely safe).
One more optional thing is to uninstall the sister app of kingroot "PURIFY" its really an annoying little app(imo at least).
OTA
This method also disables ota updates.
So the only way to update is to dirty flash the base stock rom dump throught stock recovery(which i forgot to mention as a benefit you have not mingled with) and then go ahead and sequentially update your device and then eepeat the root process in the aforementioned manner.
If I've made any mistake please do correct me(my first thread, my first guide) , if you have anything to add please let it out.... Thanks for reading, and be kind to each other. :angel:
Will this wipe my device?
I'm going to close this thread based on the fact that there are multiple threads on this same topic, including an active thread that can be found linked below.
http://forum.xda-developers.com/oneplus-x/general/guide-root-oneplus-x-twrp-pc-t3251027