Hello. As you can see, I'm a new member here and I'm also a new Android user; I bought my Nexus S (GT-i9020A) last week.
After a few days, I started thinking about jailbreaking my phone(rooting in Android's case) but I'm not really sure where to start, what rooting/flashing/ROM/etc means so I am just dumbfounded.
I want to customize my phone, make it look cool, etc.
Help would be greatly appreciated, thanks a lot in advance
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
anremi said:
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
'one more thing', root =! jailbreak, for god sake! android is 'jailbreaked' by default! =o)
bringonblink said:
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
Click to expand...
Click to collapse
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
3doncrack said:
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
Click to expand...
Click to collapse
The rooting process is the same for 2.3.3 & 2.3.4.
Maximilian Mary said:
The rooting process is the same for 2.3.3 & 2.3.4.
Click to expand...
Click to collapse
okay. Does phone model matter? Like i9020A or i9020T etc.?
3doncrack said:
okay. Does phone model matter? Like i9020A or i9020T etc.?
Click to expand...
Click to collapse
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Maximilian Mary said:
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
zephiK said:
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
Click to expand...
Click to collapse
Pray tell what this difference is.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
Click to expand...
Click to collapse
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
Click to expand...
Click to collapse
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Maximilian Mary said:
Pray tell what this difference is.
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Click to expand...
Click to collapse
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
zephiK said:
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Click to expand...
Click to collapse
I could only find two differences between these guides. One is a patch for the 9023 drivers. I'm assuming Google has fixed this by now. (Can anyone confirm this?)
The other difference is the recoveries they use. Thanks to j_r0dd, you no longer need a separate recovery for the 9023.
Perhaps I should have said "Any up to date GSM Nexus S guide should work."
.
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
Click to expand...
Click to collapse
That is freaking cool. I'm going to unroot and try it. Do you need to do anything special in recovery, or just put the zip in the right place?
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
Click to expand...
Click to collapse
The xda app doesn't show post counts. I figured thumping you in the chest would cover all the bases.
Related
Hi All,
Been doing reading of the various forums and about to delve into rooting and rom flashing from my transformer. Currently i am running stock 3.1
From what i have been able to tell there are two methods to root. CWM and NVFlash.
I haven't been able to determine what the major differences between them are.
my understanding is that CWM makes it easier to flash multiple roms with out losing data.
whereas if you use nvflash all the data on the device is wiped.
can anyone confirm/correct me?
CWM requires the use of a SD card, whereas NVflash does not
can anyone confirm/correct me?
I have seen that a ROM=OS+Kernel, so if you wanted a different kernel you have to do it after the ROM is installed.
Since I am on 3.1 my choices are:
A. use CWM. I would need to downgrade to 3.0 then i can install CWM and the normal root process
B. Flash with NVFlash directly?
can anyone confirm/correct me?
Thanks for any help anyone can provide.
CWM isn't a rooting method. It's a way to flash roms, kernels, make backups etc.
The root methods are the original cmd line method with the flashing blobs etc. and the nvflash rooting method.
Sent from my HTC Vision using XDA Premium App
Also since there is no cmd line way of rooting the original 3.1 rom you have two options.
1. Downgrade back to the original 3.0 rom and root using cmd line method. Not that hard.
2. Nvflash, which is straight up easy. DOWNLOAD a tar file with some images, get into nvflash mode and run a script to apply a rooted rom and it installs CWM for you.
Sent from my HTC Vision using XDA Premium App
So it definitely appears that I had a mis-understanding of CWM.
CWM !=Rooting.
Its the CLI rooting that after that allowed me to install CWM.
So I would DL NVFlash from: http://forum.xda-developers.com/showthread.php?t=1123429
Download my rom of choice, for an example lets say Prime.
http://forum.xda-developers.com/showthread.php?t=1052380 (the NVFlash version)
Hookup my tablet via USB and run the program and follow the necessary steps (AXP mode and what not). No SD Card is required.
Then I have CWM installed and my rom of choice installed.
My next question would be then what? My understanding would be now that i am rooted and CWM is installed i can switch Rom's much easier now using that tool?
SangreSlayer said:
So it definitely appears that I had a mis-understanding of CWM.
CWM !=Rooting.
Its the CLI rooting that after that allowed me to install CWM.
So I would DL NVFlash from: http://forum.xda-developers.com/showthread.php?t=1123429
Download my rom of choice, for an example lets say Prime.
http://forum.xda-developers.com/showthread.php?t=1052380 (the NVFlash version)
Hookup my tablet via USB and run the program and follow the necessary steps (AXP mode and what not). No SD Card is required.
Then I have CWM installed and my rom of choice installed.
My next question would be then what? My understanding would be now that i am rooted and CWM is installed i can switch Rom's much easier now using that tool?
Click to expand...
Click to collapse
everything is correct.
As for as then what....wait for the newest roms and flash that. try some kernels, roms and always make backups.
When you say make backups are you talking about making them with applications like titanium backup?
SangreSlayer said:
When you say make backups are you talking about making them with applications like titanium backup?
Click to expand...
Click to collapse
no CWM backups up your entire installed rom(system,data, etc). Basically a carbon copy of the rom your using.
He's talking about nandroid backups.
david279 said:
no CWM backups up your entire installed rom(system,data, etc). Basically a carbon copy of the rom your using.
Click to expand...
Click to collapse
these are called nandroid backups in CWM world...
Thanks everyone for your help. About to give the nvflash a go right now
SangreSlayer said:
Thanks everyone for your help. About to give the nvflash a go right now
Click to expand...
Click to collapse
Let us know how it went.
I am waiting for someone tomakeit real easy to root,like with an app or something like that.
Have rooted my galaxyS which was real easy.
Cheers.
I got a newbie question on android rooting/custom roms, currently mine is stock unrooted. Going through the rooting process would all of the current apps and everything be wiped? next if installing a custom rom is there a method to keep all of your applications without having to reinstall/lose of data?
Taxnl said:
Let us know how it went.
I am waiting for someone tomakeit real easy to root,like with an app or something like that.
Have rooted my galaxyS which was real easy.
Cheers.
Click to expand...
Click to collapse
What are you taking about? It doesn't get any easier then this. Try making a gold card and come tell me how hard this really is. Psssh make it easy
nvflash make it easy, but I enjoy flashing via CWM. Not sure why?
While we wait for the poster's update on how it went, I would appreciate it if someone would help me with two very simple rooting questions:
1) Is it possible to root my Transformer without flashing a new ROM? IE, just override the security to allow the user to have root access and use root required apps.
2) Is it true that the Transformer is still running the android cell standby service, eating up most of the battery life while in standby mode? Can this be removed with root access?
Many thanks
Sorry for the delayed response.
Flashed it and it was real easy as I suspected.
It updated the rom and rooted it and everything.
There are a couple of issues (Browser has crashed 3 times, whenever i press the home button it is putting me on the first screen instead of the middle one and the SOD) but I believe it has more to do with my ROM (Prime 1.5) than the actual flashing process.
Another question I have has to do with CWM, do i need a SD card to use that method to flash a new rom?
Thanks!
This thread convinced me to flash. Didn't know I could like my tf that much more.
OK...I've read the Wiki and the Glossary, I've searched the forums, I've been obsessively reading this forum for a week, and I still have some very basic questions that I'm hoping someone can either point me to a link or just drop some info for me. I know many of you have been at this since the Dawn of Android, but sometimes I feel like I'm walking into my first day of med-school when everyone else has been here for 5 years. Assume for a moment that I am a tabula rasa where the rest of you are now writing in the margins of a dense technical manual. Because that's what it feels like for me.
First, some background info: I want to learn how to do all this stuff, but this phone was expensive! I don't want to break it. So I'm cautious. I'm not a programmer but I'm not technically inept. I am good at following directions. I don't panic when things go wrong. So I think I can root, flash, and all the fun stuff that comes with having an Android device. But I have some questions that are still unanswered. I'll try to be as concise as possible (too late, I know):
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
4) Do any of the developers offer tech support?
I now throw myself to the mercy of the masses, prepared for flames, but hoping for help.
NoobyMcNoob said:
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
Click to expand...
Click to collapse
It's the same.
- fastboot oem unlock
- flash a custom recovery for your device (crespo4g) using fastboot
- boot into CWM, mount system and flash the su binary
NoobyMcNoob said:
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
Click to expand...
Click to collapse
No change unless you are trying to flash a modified boot.img for adb remount (this is not necessary if you merely want root access)
NoobyMcNoob said:
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
Click to expand...
Click to collapse
Yes, fastboot oem unlock wipes everything, including the SD card.
Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.
Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?
NoobyMcNoob said:
Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?
Click to expand...
Click to collapse
You will need the usb driver and platform tools.
Sent from my Nexus S using XDA Premium App
NoobyMcNoob said:
Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.
Click to expand...
Click to collapse
You could use something like titanium backup, but watch what you restore as some things cause issues.
Sent from my Nexus S using XDA Premium App
Awesome. I'm taking the leap now! So far, nothing screwed up...
So...I can't get the correct driver installed. In all the guides it says I should have the Bootloader Interface listed as the driver. But that is not one of my options - Allgamer's guide says there should be 3 choices, but I only have 2:
Android ADB Interface
and
Android Composite ADB Interface
How do I choose the Bootloader Interface?
You need to be in the bootloader on the phone I believe. I am new to the nexus s so I am not 100 percent sure.
Didn't work from the bootloader either - still showing Android ADB Interface.
I guess I'll uninstall everything and start from scratch.
Ok, finally got my first Android phone, the SGS+, now what?
1). My version is KG1 and most on this forum are other variants. Is this code just regional or what?
2). Rooting. This allows me to have full control over the system. What will this help me with? (Except OverClocking)
3). Custom ROMs. These little "toys" transform your phone and make it better (in a nut shell). How do you flash a ROM and how do you restore to Stock SGS+ FW?
4). Recovery Mode. I heard you need to replace it with a better one in order to OC and change ROMs. How do you do that exactly?
These are the main ones also,
5). My phone is slow at times... I think I have too many apps running at once (After reboot I have 220mb RAM used from 350mb). I think I should Hard Reset and see if that will work?
6). 2.3.3 -> 2.3.4. I can not find the Samsung Page where to get the upgrade (I heard that it`s called 2.3.3 but it`s 2.3.4 and bla bla bla)
So, I would apreciate it if you could help me a little,
Thanks in Advance!
I have the exact same question as you, so thanks anyone who can answer this hopefully.
crisdorya said:
Ok, finally got my first Android phone, the SGS+, now what?
1). My version is KG1 and most on this forum are other variants. Is this code just regional or what?
2). Rooting. This allows me to have full control over the system. What will this help me with? (Except OverClocking)
3). Custom ROMs. These little "toys" transform your phone and make it better (in a nut shell). How do you flash a ROM and how do you restore to Stock SGS+ FW?
4). Recovery Mode. I heard you need to replace it with a better one in order to OC and change ROMs. How do you do that exactly?
These are the main ones also,
5). My phone is slow at times... I think I have too many apps running at once (After reboot I have 220mb RAM used from 350mb). I think I should Hard Reset and see if that will work?
6). 2.3.3 -> 2.3.4. I can not find the Samsung Page where to get the upgrade (I heard that it`s called 2.3.3 but it`s 2.3.4 and bla bla bla)
So, I would apreciate it if you could help me a little,
Thanks in Advance!
Click to expand...
Click to collapse
1. Regional firmware, yes...you should stick to it or you might find gsm/3g problems...unless there's a custom firmware like CM7 which is universal like
2. Rooting? lots of advantages...one of them is to install "chainfire3D" get "tegra 2 plugin" and play most of tegra 2 games with high quality graphics...you can use titanium backup to permanently remove systems apps or backup your apps..e.t.c
3. No custom firmware is available, it's a shame, yes it is for the devs specially...ironic..but there's a tool called "odin multidownloader" it helps you flash firmwares...you can get your stock firmware from "samfirmware.com"
4. No such recovery is developed...the name for that recovery is "Clockworkmod" which is not yet developed for this phone. Shame on devs :/ using that you can backup whole firmware so you can restore it incase your device doesn't bootup properly (quite straightforward) also you can install custom firmwares in a .zip format which i really like because that way, you will never mess up your phone or brick it...well exagerated there but it's the best and easiest way to flash a custom firmware
5. Hardreset doesn't get rid of your system apps...you can delete them by rooting the phone then installing titanium backup from market which is free.
6. get 2.3.4 rooted from here....i'm using it and it has no problem whatsoever:
http://forum.xda-developers.com/showthread.php?t=1260707
Another good thing about 2.3.4 is that there is a battery drain bug in 2.3.3 which is fixed in 2.3.4 so i strongly recommend you to flash that...
Press thanks if i helped you
Thanks shad0wboss for the helpful information.
I do hope devs can make Custom ROMs and Custom Recovery a reality.
But until then, rooting will sufice.
Also, you said that you are using 2.3.4, is that a Universal or I should really stick with my regional-FW?
crisdorya said:
Thanks shad0wboss for the helpful information.
I do hope devs can make Custom ROMs and Custom Recovery a reality.
But until then, rooting will sufice.
Also, you said that you are using 2.3.4, is that a Universal or I should really stick with my regional-FW?
Click to expand...
Click to collapse
shouldn't be a problem since my stock firmware is also different than that one and everything's working fine...if it doesn't work out for you, you can always flash back to your stock firmware.
This might belong in the other "[Root] Jelly Bean" thread - I'll leave that to the moderators to figure out.
Can anyone vouch for the veracity of this method?
tutznet. com/ root-asus-transformer-tf700-android-41-jelly-bean. html (forgive the extra spaces - I'm too new to be able to post a URL.]
Honestly, I read all 39+ pages of that thread mentioned above, and I'm not confident I know what to do, and in what order, so I'm leery of trying it out. A noob like me can easily create an expensive brick if I screw it up. But this one seems sort of "plug-n-play" and is appealing for that reason. If you folks here validate it, I might try it out.
n4ogl said:
This might belong in the other "[Root] Jelly Bean" thread - I'll leave that to the moderators to figure out.
Can anyone vouch for the veracity of this method?
tutznet. com/ root-asus-transformer-tf700-android-41-jelly-bean. html (forgive the extra spaces - I'm too new to be able to post a URL.]
Honestly, I read all 39+ pages of that thread mentioned above, and I'm not confident I know what to do, and in what order, so I'm leery of trying it out. A noob like me can easily create an expensive brick if I screw it up. But this one seems sort of "plug-n-play" and is appealing for that reason. If you folks here validate it, I might try it out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1
That would be a portion of the method laid out in the above thread...
n4ogl said:
This might belong in the other "[Root] Jelly Bean" thread - I'll leave that to the moderators to figure out.
Can anyone vouch for the veracity of this method?
tutznet. com/ root-asus-transformer-tf700-android-41-jelly-bean. html (forgive the extra spaces - I'm too new to be able to post a URL.]
Honestly, I read all 39+ pages of that thread mentioned above, and I'm not confident I know what to do, and in what order, so I'm leery of trying it out. A noob like me can easily create an expensive brick if I screw it up. But this one seems sort of "plug-n-play" and is appealing for that reason. If you folks here validate it, I might try it out.
Click to expand...
Click to collapse
The instruction is assumed that you already unlocked and have custom recovery installed. If you provide your setup we can help.
1. Are you unlocked?
2. Do you have custom recovery installed like either twrp or cwm?
3. What os version you are running currently? I assumed you're on JB?
Thanks for the offer of assistance. I bought the TF700 on ICS, and immediately did the following (based on advice I hopefully gleaned correctly from this board):
- Factory Data Reset three times (by booting with the volume key held down, etc.), even wtih nothing personal done to it (like add my name as Owner, or install anything).
- Loaded the full update downloaded from the ASUS site and flashed (correct term?) accordingly. Those instructions, at least, I could figure out.
- Another FDR.
- Used as normal on the current version of JB. I believe it had a minor JB upgrade shortly after that, which I let it perform through the "You have an update" process.
As it sits, the TF700 works quite well for me, but I use Titanium Backup on my Droid Razr Maxx (for which I rooted using one of those "automated root" programs that worked well), and I'd like to use it here. And Root File Manager (also found on the Droid).
As a noob, the instructions for that other method (using CWM and SuperSU) look like they presume too much knowledge on my part of what to install and when, and I'm leery of creating an expensive brick. For example, there is something in there about "fastboot," but that is completely over my head.
buhohitr said:
The instruction is assumed that you already unlocked and have custom recovery installed. If you provide your setup we can help.
1. Are you unlocked?
2. Do you have custom recovery installed like either twrp or cwm?
3. What os version you are running currently? I assumed you're on JB?
Click to expand...
Click to collapse
n4ogl said:
Thanks for the offer of assistance. I bought the TF700 on ICS, and immediately did the following (based on advice I hopefully gleaned correctly from this board):
- Factory Data Reset three times (by booting with the volume key held down, etc.), even wtih nothing personal done to it (like add my name as Owner, or install anything).
- Loaded the full update downloaded from the ASUS site and flashed (correct term?) accordingly. Those instructions, at least, I could figure out.
- Another FDR.
- Used as normal on the current version of JB. I believe it had a minor JB upgrade shortly after that, which I let it perform through the "You have an update" process.
As it sits, the TF700 works quite well for me, but I use Titanium Backup on my Droid Razr Maxx (for which I rooted using one of those "automated root" programs that worked well), and I'd like to use it here. And Root File Manager (also found on the Droid).
As a noob, the instructions for that other method (using CWM and SuperSU) look like they presume too much knowledge on my part of what to install and when, and I'm leery of creating an expensive brick. For example, there is something in there about "fastboot," but that is completely over my head.
Click to expand...
Click to collapse
It's not that complicated, if you have someone leaded you. Again, I need you to answer the following question, so I can point you to the right direction; Do you plan to use custom rom/kernel? (if yes, you need to unlock your device, which void warantty) or you just want root?
buhohitr said:
It's not that complicated, if you have someone leaded you. Again, I need you to answer the following question, so I can point you to the right direction; Do you plan to use custom rom/kernel? (if yes, you need to unlock your device, which void warantty) or you just want root?
Click to expand...
Click to collapse
All I want to do is root it. While I know there are some advantages to a custom ROM or Kernel, that's NOT what I forecast doing*. I plan to leave it on JB.
* = Caveat: Eventually ASUS will stop supporting this tablet, at which time I will probably look at custom ROMs if I still own it (and haven't EBay'd it).
n4ogl said:
All I want to do is root it. While I know there are some advantages to a custom ROM or Kernel, that's NOT what I forecast doing*. I plan to leave it on JB.
* = Caveat: Eventually ASUS will stop supporting this tablet, at which time I will probably look at custom ROMs if I still own it (and haven't EBay'd it).
Click to expand...
Click to collapse
Since you already on JB, the only way you could root is to downgrade back to ICS (version .30). Here is general guide line:
1. Download full package firmware .30 from Asus site
2. Then use root tool to root,
3. Download and installed SuperSU to replace the old superuser
4. Download Voodoo OTA root keeper to preserve root (If you have a paid SuperSU version, you just have to click on "preserve root" and it automatically saved root for you).
5. Let the OTA upgrade to JB
6. Once done, use root keeper to restore root.
Here is the link to details:
http://forum.xda-developers.com/showthread.php?t=1833212
buhohitr said:
Since you already on JB, the only way you could root is to downgrade back to ICS (version .30). Here is general guide line:
1. Download full package firmware .30 from Asus site
2. Then use root tool to root,
3. Download and installed SuperSU to replace the old superuser
4. Download Voodoo OTA root keeper to preserve root (If you have a paid SuperSU version, you just have to click on "preserve root" and it automatically saved root for you).
5. Let the OTA upgrade to JB
6. Once done, use root keeper to restore root.
Here is the link to details:
http://forum.xda-developers.com/showthread.php?t=1833212
Click to expand...
Click to collapse
not true my friend
you can unroot without downgrading to version .30
just take a look in the general section there is a HOWTO
sent from my cutting board
jokapo said:
not true my friend
you can unroot without downgrading to version .30
just take a look in the general section there is a HOWTO
sent from my cutting board
Click to expand...
Click to collapse
I think he's looking to ROOT, but not to unlock!
I rooted and unlocked allready on JB
sent from my cutting board
Could you share the steps/sequence (in detail, not like the way they are described in that 40+ page thread, which is (IMHO) sparsely)?
jokapo said:
I rooted and unlocked allready on JB
sent from my cutting board
Click to expand...
Click to collapse
Might wanna try out this thread then http://forum.xda-developers.com/showthread.php?t=1969303
As the title suggest, does anyone else having such (one, more or all) issues on Nexus 5 after root?
1. Kitkat kinda initializes after every reboot. Not like the very first time starting the device (setup assistent) but installing/updating apps (which) are already on the device (same Verstion) and re-setting configuration to what it already should be.
2. Always showing H (internet connection) and at least two bars on signal strength even when there is no signal (accourding to chrome and (stock) dialer app.
3. Loss of signal but pretending there is one (like in 2.) and only regaining signal after reboot.
4. Loss of distance between apps within the appdrawer (more apps per page) until uninstallation of an app (remains normal after reinstall)
5. many app crashes (before and after rooting)
6. sometimes notification led keeps blinking after notification was dismissed, sometimes the notification led blinks very fast.
I rooted my device with cf auto root.
Except for 4 &5, yes.
I am glad that I am not alone but does anyone know whats the source of this strange behaviour or how this can be fixed?
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
Wugfresh's toolkit is imho the best and safest way to root and do most changes to all nexus devices. About the only difficult you may experience is usb driver/connectivity issues. The usb driver guides are well documented and easy to follow. It's no different than the standard adb usb drivers. Most have no issues, but that is the only thing that can cause problems with adb or Wugfresh's toolkit.
Read through Wugfresh's forum topic to acquaint yourself with mtp/ptp and driver installation and you should breeze through using his toolkit.
Sent from my Apple ] [e using ProTERM 2.2
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
custom recoveries do not prevent the OTA.. plus you can just fastboot boot recovery whateverrecovery.img
i blame your problems on the CF-autoroot as i have none of the symptoms you describe.
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Nik_B said:
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Click to expand...
Click to collapse
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
DreamLinker said:
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Click to expand...
Click to collapse
Go with this guy.
As soon as I read your thread title, I knew you rooted using an "auto root". Rooting a device is actually very simple, just takes a few minutes of your time to research the steps. As long as you have 10 minutes, a USB cable and a Windows Computer, it should be easy and result in a errorless experience.
Zepius said:
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
Click to expand...
Click to collapse
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Nik_B said:
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Click to expand...
Click to collapse
fastboot boot recovery recovery.img - this just boots into the recovery once, but leaves the stock recovery as the recovery that is written to the device
when you flash supersu.zip what it does is execute a script that places the su binary in /data/xbin i believe and gives it the proper permissions, and also places supersu app on your phone.
you do not need to make your own boot image, or anything of the sort.
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
joshnichols189 said:
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do I understand you correctly that neither wugfresh nor auto root are causing the problems in your eyes. I´m just curious because many people including me used Chainfire´s auto root but not all of them are reporting problems. In my case the Nex5 seems to forget already set default apps e.g. for tapatalk links, urls etc.
Cheers, T.