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?
I have ROM manager premium, and I just downloaded CM7 through it, and was about to flash it, but remembered I dont have s=off.
Also, I cannot get past this screen no matter what. htt p://img145.imageshack.us/i/20110222142411.jpg/
Any help will be appreaciated I really want to be able to run CM7
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
epsix said:
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Root access alone is not enough. You need S-Off as well.
jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
Is that why I always get this screen when I try to make a back up or boot into recovery.
jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
This Statement is correct.
jessek17 said:
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Click to expand...
Click to collapse
for short terms "s" Means security protocol. If your S=ON that means the phone will do a search each time you boot the phone on to see if anything as been tampered with. and if it has it will revert back to a factory status. Just like you first bought the phone. Which includes rooting, recovery images, boot images, engineering screens. What ever you do to your phone that isn't factory will be undone.
It is impossible to do. Because you need to flash the ROM from the recovery image. And since one you boot your phone it will replace Clockwork ROM manager with the factory style recovery image, you cannot not even get to the place you need to flash it from.
jessek17 said:
Is that why I always get this screen when I try to make a back up or boot into recovery.
Click to expand...
Click to collapse
Correct because you flashing the Clockwork Recovery image will not STICK unless you have s=off.
They system will replace the aftermarket image with the original EVERYTIME you turn off the phone.
That is the Stock Recovery. You need S-Off and ClockworkMod Recovery. And the right release of CWM Recovery, also. Use CWM Recovery 2.x to back up, restore, and install Android 2.2 (Froyo) based ROMs, including stock, and CWM Recovery 3.x to back up, restore, and install Android 2.3 (Gingerbread) based ROMs, such as CM7.
There is a special version of CWM Recovery that can manage both Froyo and Gingerbread ROMs: 3.0.0.6. Search for it in the Development subforum.
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
jessek17 said:
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
Click to expand...
Click to collapse
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
neidlinger said:
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
Click to expand...
Click to collapse
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
jessek17 said:
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
Click to expand...
Click to collapse
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
neidlinger said:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
Click to expand...
Click to collapse
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
jessek17 said:
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
Click to expand...
Click to collapse
That's kind of my point. People don't read.
If you take your time and read and do the entire process you won't have a problem. but you need to read all the way through something prior to jumping in the ring. There is a very strict set a rules that need to be followed.
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.
I am looking into rooting my Nexus S so I can install an ICS ROM. This is my first time rooting so got a question.
How will OTA updates work for me? Will the ICS update just work or will I have to in root to get the official OTA update?
Sry if this has been asked before couldn't find a clear answer.
Sent from my Nexus S using XDA App
Don't do OTAs. Any update released by Google or your manufacturer will be released here, rooted, within hours.
If you take an OTA you will lose root and could even find your phone locked again (as unlikely as that is with the NS, better safe than sorry. Ask the EVO users who took the GB OTA )
Sent from my Nexus S 4G using Tapatalk
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Alright, thanks alot for the quick responses guys.
Sent from my Nexus S using XDA App
Once the ota is downloaded.....
* Put the zip on sdcard
* Reboot into custom recovery
* Manually flash it
* Directly after that, in the same recovery session, flash latest superuser zip
* Wipe cache
* Reboot
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
OTA's will work with CWM installed (The OTA will however remove CWM and needs to be manually applied)
OTA's will remove root access (the permissions on the binary get changed)
I have never seen an OTA on XDA that was pre-rooted. i have seen ROM packages that incorporate the OTA that are pre-rooted (installing these usually means a wipe of the device is needed)
if you replace the ROM on the phone, you will not get OTA updated. you must remain mostly stock to obtain them.
Custom kernels or custom google apps on stock roms will cause the OTA update to fail, however you will notified that the update is available.
I hope this answers your questions.
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
snandlal said:
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
Click to expand...
Click to collapse
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Matridom said:
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
I hope this answers your questions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
onthecouchagain said:
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Click to expand...
Click to collapse
OK, let's clear a few things up here.
CWM or ClockWorkMod is a custom recover that can be installed on the phones. This step is needed because the default recovery on the nexus does not allow for updates to be installed that are unsigned. CWM does, so it's a necessary step to installing the SU binary (aka root your phone) or installing custom ROMs
The bootloader is the basic system on your phone that reacts to the power on and hands over operations to Android. The equivalent in the PC world would be a BIOS.
fastboot is a utility that is provided by google that allows you to send commands to the bootloader and direct it's operations. It's needed to unlock the bootloader (so you can replace parts of it.. like recovery with CWM)
Interestingly enough, you can boot your phone to a custom recovery WITHOUT replacing your existing stock recovery by using fastboot.
Rooting your phone is simply installing and providing the proper rights to the SU binary to allow you to have full administrative rights to the phone, the superuser application is almost always bundled with it as it allows for a form of control as to what applications can use root access. Rooting your phone allows you to install some very interesting application, most popular are titanium backup (let's you back up app data and restore them after a reset) and removing advertising (adfree/adaway or it's like) Root can also be used by some applications that allow you to "cheat" at games.
rooting your phone is reversable, though not always the easiest to do. With the stock ROMS, it's fairly easy, you just re-apply the latest OTA and it will kill Root access on your device.
When it comes to custom ROMs the vast majority come pre-rooted to save you the hassel of doing it yourself.
On other phones where the bootloader remains locked, you have to use an exploit to gain root access, this then allows you to modify the OS and install custom roms and CWM while keeping the bootloader locked. Since the Nexus line can be unlocked, it's not needed.
Please note, root access is NOT required to install a custom ROM.
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
MaxCarnage said:
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
Click to expand...
Click to collapse
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Matridom said:
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Click to expand...
Click to collapse
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The key here is that SPRINT released an OTA for a SPRINT branded device. This has zero relevance to updates provided by Google for Nexus devices.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The issue at heart here is that fact that the OTA for the nexus line of phones comes straight from google and are not "tweaked" in any way by the carriers. (exception nexus 4g has additional applications required for CDMA support)
One of the selling features of the nexus phones is the fact that unlocking the bootloader is officially supported.
In regards to other phones getting their bootloader locked, I've experienced first hand the pains of that, having a galaxy S and the 2.3 installing a new bootloader and really screwing things up for me. In those cases, i agree with you whole heartily and to wait for pre-cracked roms that can be installed.
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
onthecouchagain said:
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Click to expand...
Click to collapse
All you would need to do is to unlock the bootloader, install CWM, then apply the .zip associated with the ROM you wish to install. I would however carefully read the installation instructions for the rom as in some cases, it might be a multi-step process (such as going from a 2.2 rom to a 2.3).
Many ROMS also do not come with the google apps and secondary zip file needs to be applied to get those running (cyanogenMod does this)
I wanted to add, that the process of unlocking your bootloader will erase EVERYTHING on the phone, including the SDcard partition. So make sure you back up anything of importance.
Matridom said:
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
Click to expand...
Click to collapse
I can't provide an example because, as I have already stated, this was a precautionary suggestion only.
I'm not going to get into a debate with you over this; I've made my point and you've made yours. Thanks.
Matridom said:
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
Click to expand...
Click to collapse
Good point again but the trick is to put your apps in /system/framework
Along with framework-res.apk.
This will add a dex file to /data/dalvik-cache, which is needed for saving upon reboot
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
suksit said:
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Click to expand...
Click to collapse
Rooting doesn't require flashing custom recovery.
iboj007 said:
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
Click to expand...
Click to collapse
No. It doesnt
I have just recently started my journey into rooting, I've been in research mode for about a week trying to learn as much as I can but it's SO overwhelming trying to keep up with all the old and new techniques - trying to find out what is the best method to use.
Before discovering this place I asked a few questions on reddit and was able to get a cheat sheet on all the terms one needs for rooting:
https://www.reddit.com/r/androidroo...ingroot_considered_true_rooting_where_is_the/
and while browsing Xda I found this short guide:
http://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748
However both of theses sets of instructions miss out a few starting points.
I've watched a few videos on how to root a htc but they've all been made around the time of the phones release, and as we all know each year things get bigger and better in computing, so new techniques might have arrived. So I wanted to ask here what are the full sets of instructions to root a htc one m8 in 2016, starting from watch software to use to back up your phone, how to unlock the bootloader, etc... and using whatever new rooms and kernels people have been using and would recommend.
My aim is, with your help, to make this post a place beginners can go to learn how to do their first root. thankyou in advance.
My phone:
service provider: Orange/EE (UK)
Android: 6.0 (Marshmallow I think)
HTC sense version: 7.0
Sofware number: 6.12.61.4
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
ieatabiscuit said:
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
Click to expand...
Click to collapse
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
3mel said:
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
Click to expand...
Click to collapse
Just rechecked into it to refresh my memory, as I've been S-off so long I forgot the method I had used. It was in the pre-Sunshine days. I used Firewater to get S-off (thought Sunshine sounded odd to me for some reason). Didn't cost me anything but a couple minutes of my time. Hope that helps. I wouldn't want to pay for S-off either, it's not really something that I think many people would want to do...
---------- Post added at 06:53 AM ---------- Previous post was at 06:47 AM ----------
GreiverX said:
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
Click to expand...
Click to collapse
If you have a way to revert it and become S-on again (assuming you're S-off also) I would say you could hide the fact it's been rooted by unrooting and removing any root apps, but don't quote me on that. I rooted back when mine was new, and never looked back at the warranty. Now my phone would have had the warranty expire anyway, so it still doesn't matter. When in doubt, assume the warranty to be void upon rooting, but research a way to revert if it's possible. Not like we have to bother with KNOX at least.
only way is USD $25 for sunshine....can't S-OFF it without other ways.
WingZer0n said:
only way is USD $25 for sunshine....can't S-OFF it without other ways.
Click to expand...
Click to collapse
then why does firewater say different?
grrmisfit said:
then why does firewater say different?
Click to expand...
Click to collapse
firewater doesn't work anymore unfortunately. Only way to get S-Off now is sunshine @ USD 25.
3mel said:
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
Click to expand...
Click to collapse
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Nebster7 said:
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Click to expand...
Click to collapse
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
redpoint73 said:
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
Click to expand...
Click to collapse
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
---------- Post added at 02:56 AM ---------- Previous post was at 02:38 AM ----------
Nebster7 said:
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
Click to expand...
Click to collapse
Just one thing my PC doesn't see my phone now.???
Nebster7 said:
Just one thing my PC doesn't see my phone now.???
Click to expand...
Click to collapse
Meaning what exactly? Doesn't see storage (did you select the option on the phone to allow data transfer?) or adb or fastboot? Booted to the custom ROM, or something else (bootloader, recovery)?
When asking for help, please give as much information as possible. One sentence is really never enough info to go on.