Sorry if this has already been posted.
Superboot for N1 GRI40
Tested and working
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/298782/08-mar-superboot-erd79-gri40-rooting-the-nexus-one/
super easy method for rooting.
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Worked on my phone like a charm. Bootloader unlocked.
flixos said:
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Click to expand...
Click to collapse
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
jimbobalu said:
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
Click to expand...
Click to collapse
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Hi I am an new user with a rooted N1 running GRI40, I want to root mine to enable navigation outside US and install the latest release of Google Maps.. but I don-t want to mess with the bootloader.. is there a z4root kinda method yet?
No z4 style method available yet, but you can roll back to an older version of android and use z4 or whatever. Once rooted you can install a pre-rooted version of 2.3.3...
Sent from my Nexus One using XDA Premium App
flixos said:
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Click to expand...
Click to collapse
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
efrant said:
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
Click to expand...
Click to collapse
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
flixos said:
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
Click to expand...
Click to collapse
I don't think you understand what I'm trying to say: It's superboot that is likely messing things up with people's phones, NOT unlocking the bootloader.
Like I said, unlock your bootloader, and flash ChainsDD superuser package, and you will have a stock ROM with root, perfectly stable. (The only thing that the package does is adds two files to your device that give you root. That is all.)
If you don't want to unlock (and I can't understand/imagine why people would not, given that many folks have already shown that HTC still honors the warranty), then ignore everything I'm saying.
Thanks so much, got it
By the way, i will wait for another SuperOneClick...developer said that it's just a matter of time to make it work on Gingerbread.
Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
Potential first time Nexus user coming over from Desire Z.
I intend to transfer my old data from my DZ to the nexus4 when I get it via Titanium Backup. My DZ is rooted with S-off, so it's all good.
I've stumbled over instructions on how to unlock the nexus4 via ABD, but if I'm not wrong, that's only to allow flashing of custom bootloaders and ROMs, right?
Which is to say, unlocking != rooting, and in order for Titanium Backup to work properly, the n4 will have to be rooted as well as SU, busybox etc installed.
Am I on the right track?
Cheers.
nexus come unlock.
unlock = to be use with any carrier
rooting = giving beyond standard permissions such as changing how android does things. EG overclocking, changing your sound "quailty" etc and you said. TB (titanium backup)
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
Click to expand...
Click to collapse
Thanks Unlawful. Yes, I meant bootloader unlocking.
Unlawful said:
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I doubt it. Be cool if it did
Once you have it unlocked you enter the recovery mode and root it there. I'm probably guessing shortly after its release someone is going to make a program so it does it in few steps.
There won't be anything really out that really requires root, other than TB.
endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
Nexus 4 does not come rooted. You have to root it.
NeverAlwaysEver said:
Nexus 4 does not come rooted. You have to root it.
Click to expand...
Click to collapse
Thanks guys. I guessed as much.
Yeah, I'll probably have to do without the backup of my apps for a few days until some kind soul manages to root it and posts instructions. Maybe it'll just be a day or a few hours even! :fingers-crossed:
You will be able to unlock the bootloader right away.
Root maybe not. In order to root it you will need either need a custom recovery for the device or a software exploit.
It won't take long but a custom recovery needs to be built and tested first.
It's easy to root a nexus
First you unlock the bootloader=fastboot oem unlock.
Then you use fastboot to flash a recovery. Once recovery is flashed you have to use adb to make it stick(delete the script that overwrite custom recovery with stock) then you flash su. Zip in recovery. Very simple to do
Sent from my SCH-I535 using xda premium
Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
USSENTERNCC1701E said:
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
Click to expand...
Click to collapse
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
endlesstrail said:
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I think Chainfire meant that in case you wanted to switch from Superuser to SuperSU or if you're just installing the APK (the application). If you do want to root, you should just flash the zip file found here in a custom recovery which does everything for you.
Unlawful said:
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
Click to expand...
Click to collapse
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
I just want to clear up some terminology to stop people getting confused...
Bootloader a.k.a HBoot - This is the piece of software that runs before anything else on the phone. It basically packages it all up, tells what to run in what order e.t.c Every computer device has a bootloader in some form or another, be it an Android Phone, iPhone, Windows PC, iMac e.t.c. The HBoot is accessible by switching your phone off, then holding down volume down as you turn it back on. The first line of the HBoot will tell you if you are S-OFF or S-ON.
Recovery - The recovery is the piece of software that allows us to write files to partitions while they aren't being used. It is the portal to allow us to flash custom ROM's and kernels. There are custom recoveries with more options than the stock such as ClockworkMod.
Superuser a.k.a su or Root - This is a user that is present on all linux distros that allows higher permissions than standard users have access to. Certain apps need superuser permissions to function, such as Titanium Backup.
A bootloader is traditionally locked. This means it stops you from writing to any partition on the device other than data. What is always true of Nexus devices, and now true of most consumer devices, there is an offical method for unlocking the bootloader. With HTC, you have to download some software, with Nexus devices, it is as simple as booting into fastboot mode, and typing the command "fastboot oem unlock" (assuming you have fastboot installed on your connected PC / mac).
Although this unlocks the bootloader (which by the way resets your device to factory settings), you still aren't rooted. You now have the ability to flash images to the previously locked partitions. Once you have access to write to partitions, the easiest method of rooting is installing a custom recovery (fastboot flash recovery recovery.img, and then using that to flash a superuser zip.
There are exploits for rooting, which either eman the recovery partition gets written to without the bootloader unlocking OR the su files get pushed to the system partition while the bootloader is locked. These exploits are more tricky and are getting harder to find, but allow you to gain root access without voiding your warranty.
To answer someone else's question, when you unlocked the bootloader on the Nexus One you got a watermark on the bootsplash, I don't know about any Nexus after that.
EDIT - Unlocked Phone: To throw some further clarification, when people talk about "unlocked phones" what they actually means is carrier. This term pre-dates smartphones, and a locked phone just meant that if you bought your phone through a carrier, you could only use it on their network, so no other SIM would work unless you bought a code off them to unlock it. This only applied to GSM phones (not CDMA) and s still practised today. The Nexus 4 will not be carrier locked wherever you buy it.
l0st.prophet said:
I just want to clear up some terminology to stop people getting confused...
Click to expand...
Click to collapse
Thanks for the excellent clarification. It's much clearer now.
USSENTERNCC1701E said:
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
Click to expand...
Click to collapse
Both the Galaxy Nexus and the Nexus 7 don't have anything changed when you unlock the bootloader (apart from an unlocked lock image on the boot screen beneath the Google logo and then it disappears after going to the boot animation). I would assume this was the same with the Nexus S . Also another good thing about Nexus devices is that you can relock the bootloader after unlocking it and it will be back to a stock configuration (assuming you're on the Google-built ROM).
PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
I beg to differ; DroidWall is the one utility I refuse to live without, and that requires root.
Other than that and TitaniumBackup though, you're quite right; the new stock features of JellyBean mean I likely won't even bother with any major third-party modifications. Indeed, I'm thinking this'll be the first 'phone in many a year which I won't be installing a custom ROM on for at least the first six months of use.
PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
Lol, the irony is I really only use TB because I'm switching ROMs. I disagree though, I really like the extra customization that comes with a lot of custom ROM's. But I've run phones for a few months with OEM skins, while waiting on an exploit. I agree there won't be a pressing need for root.
I guess you guys like to actually see ads on your phones.
albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I actually don't find many apps to have very intrusive ads at all. I also feel better knowing I'm not ripping off the devs
albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I've never actually ended up with an air push app, and the rest of the ads really don't bother me, sometimes I'll go on a clicking spree to support devs. If it really bothers me I buy the full version or uninstall it.
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app
noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)
comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?
NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.
timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.
clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2