Hi all, I've done a fair bit of searching and reading up but not sure I can find definitive answers to whether there are any downsides to rooting my One X.
I am thinking similar to tethered jailbreaks in the iOS world, where if you run out of juice you have to cable up to get it to boot up etc.
I would like to root, so I have the freedom to use a few of the tweaks and mods on xda (such as the tweak to change the default - read too high - auto brightness levels), not sure I will actually replace my entire rom at this stage, just root so I can use some of these minor tweaks.
so, is there anything that I need to genuinely consider before making the leap, some specific questions that spring to mind are;
1. Can I always easily revert it ?
2. Read some posts where people are struggling to charge once it hits 0% ? Is this an actual problem if I just root ? I do not want to brick a phone or have to prize open the case to take batteries out etc
3. If I chose to replace ROM's in the future, are there actual apps that more or less backup all your apps and settings so you can just reload that one app after a new ROM is installed, restore a backup and I am good to go, or do you have to manually setup everything from scratch again ?
Thanks for any advice you guys can offer.
ta
Mart
The only downside to rooting is you get hooked on flashing. It's very easy to get back to stock. As long as you have proper RUU for your region that goes with your CID and all is fine.
At present, the only rooting method involves unlocking the bootloader. It can be locked again. But it's 'relocked' rather than 'locked'. So your warranty is still void in some cases.
I'm waiting for root method which doesn't require an unlocked bootloader. Or non HTCDEV Unlocked bootloader and S-OFF before I do mine, but that's just me
Sentinel196 said:
So your warranty is still void in some cases
Click to expand...
Click to collapse
HTC will only refuse your warranty if you balls up your phone as a result of flashing roms. Everything else such as hardware defects will leave the warranty in tact.
Related
In the N1 General forum there was a great post done - 100% Fool Proof Guide to rooting & ROMs, and I was hoping that we could start a similar thread here.
Please feel free to comment on this post - it is my hope that we can put together a great document for newbs like me in the future. THIS thread is for suggestions on what should be in the guide, not the guide itself. I will reserve the second post for compiling suggestions over the next couple of days.
I just ordered my Desire, and it should be with me in a week or two. I am disturbed by the USB/A2SD issues being encountered by some, and so when I root I want to get it right
imHo, the guide should include:
1) Definitions of Rooting, unlocking, goldcards, generic, kernel, radio and how these relate to future OTA updates. These are concepts which I am familiar with, but feel I know just enough to be dangerous to myself/my device
2) A ballpark comparison of the unique characteristics of ROMs available today (stock-like, minimalist, sense-free, tethering, etc)
3) A step-by-step guide to the most recommended flashing updates people are using today
4) Things to bear in mind if you are a win-x64 user (I understand this is a tripping point for some)
[Reserved for collating ideas]
1) Terminology:
Rooting
Unlocking
Goldcards
Generic
Kernel
Radio
OTA updates, and how they may be affected by flashing your Desire
2) Current ROMs available and their unique characteristics
3) Guide to flashing your desire
4) Win64 users - what to bear in mind
And a big warning that this rooting process can cause unexpected pain on your bank balance if you are unlucky at the minute
I'd say to use the TinyCore method as I had nothing but issues doing it using W7 x64 - there's a guide on MoDaCo that's simple as anything - only a fool would get it wrong!!!
Find it here:
http://android.modaco.com/content/h...inux-download-and-guide-easiest-and-best-way/
And my USB still works fine, not had any issues since rooting and am now happily using an MCRr2 ROM cooked to my liking
I'd have to agree. Tiny Core Linux was so simple to use. I'd never used Linux before and even I could do it!
I did see paul's tweet saying a new safer more reliable method was coming this week hopefully. If that's the case I'll be rooting like mad again!
New, safer, more reliable root method for Legend and Desire coming up next week (all being well). #mcr 7:28 PM May 14th via Tweetie http://twitter.com/PaulOBrien
Only issues I've had was flashing the radio as part of a ROM - wouldn't have it so gonna try it on its own later this evening. Would be nice to get it all in one ROM but meh
EddyOS said:
I'd say to use the TinyCore method as I had nothing but issues doing it using W7 x64 - there's a guide on MoDaCo that's simple as anything - only a fool would get it wrong!!!
Find it here:
http://android.modaco.com/content/h...inux-download-and-guide-easiest-and-best-way/
And my USB still works fine, not had any issues since rooting and am now happily using an MCRr2 ROM cooked to my liking
Click to expand...
Click to collapse
u guys are getting it wrong!!!!!!
me too i was saying the same thing last week when i was reading about the bricks and stuff. i didnt have any problems till 2 days ago. well let me tell you that the unrooting process went out wonderful... nothing wrong. i even flashed all the roms possible and even started cooking and porting some roms for my own use too.
the problem is not whether the method is complex or not. the ''brick'' does not happen while you are rooting the phone. nobody actually knows what triggers the damage. some get it on 1st attempt, some after 5-6 flashes, and some like me after numerous ones.
so in my opinion, i dont think you can say this is a safe method bla bla bla and i try to discourage ppl wanting to root ''for the moment''.
deeren said:
u guys are getting it wrong!!!!!!
me too i was saying the same thing last week when i was reading about the bricks and stuff. i didnt have any problems till 2 days ago. well let me tell you that the unrooting process went out wonderful... nothing wrong. i even flashed all the roms possible and even started cooking and porting some roms for my own use too.
the problem is not whether the method is complex or not. the ''brick'' does not happen while you are rooting the phone. nobody actually knows what triggers the damage. some get it on 1st attempt, some after 5-6 flashes, and some like me after numerous ones.
so in my opinion, i dont think you can say this is a safe method bla bla bla and i try to discourage ppl wanting to root ''for the moment''.
Click to expand...
Click to collapse
I totally agree, I try to at least warn people that there is a fair chance they will brick their device but this thread is about the best and easiest way to root.
At the end of the day if people know the risks and still want to go for it, then they may as well come here for the easiest method
just a quick question guys as im a total noob in android and rooting, does this method also works with the desire and does not require a goldcard?
cez10 said:
just a quick question guys as im a total noob in android and rooting, does this method also works with the desire and does not require a goldcard?
Click to expand...
Click to collapse
This method is for the desire!
If you choose to root, then you will only need a goldcard if your handset was network supplied and branded. If for example you bought it and it came in a plain box, and had no network branding on the software then you can do it without the gold card. I got mine from the Carphone Warehouse so it was unlocked and unbranded. I just rooted with the standard SD card.
The software number on my unbranded device is 1.15.405.4. Hope this helps.
Refer to this
1) Nothing is foolproof. If you're a fool, don't root.
2) Foolproof implies pragmatic. The N1 is designed (basically) to be rooted so there's a universal method for all. The Desire wasn't, so things liks different bootloaders, branded phones and goldcards makes everyone just that little bit different. I mean, the HTC memory protection mean things like Adfree don't work out of the box (causes phone to reboot) - if you create a foolproof method we're just going to get threads about "zomg why wont dis app wrk on my fone" because they expect to be spoonfed everything.
Apologies if this has been covered before- searched a couple of times with no joy...
Waiting for delivery of my Defy and still not sure what mods to do...Having read about a lot of UK models having the dreaded ear-piece fault, I'm just wondering:
1. what I can do that can be undone if my phone develops this fault?
i.e. Is it possible to root the phone, remove some of the Motoblur bloatware, overclock and scale, and still be able to return it to it's original state if the earpiece goes? (or at least make any mods undetectable!)
2. From what I've read it is possible to skip the Motoblur registration. Would I still be able to use the phone portal- what apps require the Motoblur registration?
Basically I'd love to tweak the phone but am paranoid about voiding the waranty!
Thanks in advance!
Once you are rooted and have recovery installed backup your system before doing anything else. If something happens restore the backup and unroot. Only problem might be if you have some type of hardware issue and can no longer boot the phone.
There is always risk, but that will help.
rbeier1221 said:
Once you are rooted and have recovery installed backup your system before doing anything else. If something happens restore the backup and unroot. Only problem might be if you have some type of hardware issue and can no longer boot the phone.
There is always risk, but that will help.
Click to expand...
Click to collapse
Thanks. Is it the case that you can mod the phone any way you like as long as you backup, restore and unroot before returning the phone for any possible warranty claim? Would a Mototola tech be able to tell that the phone had been modded and then reset to it's original state? Just wondering if I'd be better to wait a couple of months for any possible fault to appear...Thanks again.
cwhiggs said:
...am paranoid about voiding the waranty!
Click to expand...
Click to collapse
If that's your primary concern, tweaking isn't really an option.
As soon as you start fiddling with the software, you technically void your warranty.
That said, most fiddling can be undone and if the phone were to end up in a state that you couldn't boot it to fix your fiddling, there's a fairly good chance that the engineers wouldn't be able to boot it to discover what you've done.
Not to mention, from past personal experience, a lot of front-line engineers that actually deal with faulty handsets that are sent away for repair don't really care or may not be bright enough to be able to tell that you've messed with your phone.
Thanks. Think I'll go ahead and mod it. Been reading the relevent posts/stickies and from what I can see as long as I'm carefull and follow the various steps closely and in order, I'll be unlucky to brick it. Think I'd get pissed off waiting several months for any fault to show- just wary of the earpiece going and then being told I'm screwed coz I've played with the software! Thanks again.
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
I agree though, as people are responsible for their actions and so must know the consequences of modding their devices, they should just give another level of access to remove s-off. The warranty is void once you unlock the bootloader anyway.
More info around s-off/NAND/partitions etc:
http://forum.xda-developers.com/showthread.php?t=2619392
gsmyth said:
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
Click to expand...
Click to collapse
Now I simply voided my phone's warranty without any use.
Damn it HTC.
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
How did you unlock it? Do you have s-off?
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
Use sunshine to get s-off.
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
This
When you are S-on/BL locked, your carrier (or HTC/Google) is your system administrator. The carriers take this a bit further, and even manage some of your apps. In a lot of ways, you are a guest on the system, even though you "own" it. However, assuming you just want to use it to make phone calls and post to facebook, for most people this is fine. (my wife's phone isn't even rooted)
When you are BL unlocked, you take over some parts of that sysadmin job, and can now replace parts of the operating system and manage your own apps. You can also disable external control of your device by rooting and turning off certain services. However, the truly critical stuff, the stuff that could keep your phone from booting, are outside of your control. You are now no longer a guest, but you aren't exactly an owner either.
When you S-off, you are taking on the job of being the system administrator entirely. You are 100% responsible for what happens to your phone. Your '44, your Magnum rounds, your foot. Be careful.
gsmyth said:
How did you unlock it? Do you have s-off?
Click to expand...
Click to collapse
I unlocked my bootloader.
No, I don't have S-OFF
KJ said:
Use sunshine to get s-off.
Click to expand...
Click to collapse
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
MJ999 said:
I unlocked my bootloader.
No, I don't have S-OFF
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
Click to expand...
Click to collapse
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
BerndM14 said:
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
Click to expand...
Click to collapse
Thank the GPL for that last one. Android is essentially a very custom distro of Linux, and the Linux community has already shown that they will go after violators. It's how the Linksys WRT54G became the WIFI router to own. IOW, they release it because they have to, but they don't have to make it easy, or usable.
We have seen with the Samsung and LG devices that it is possible to lock down a device fully such that it won't boot anything that isn't cryptographically signed. They will do as little as necessary to comply with the license, without giving us the ability to actually use that knowledge. After all, what good is kernel source if you don't have a signing key the CPU will accept?
That is the primary reason I chose the M8. It was one of the few flagship phones that is still able to be fully owned.
Do google know that we've unlocked the bootloader? (as Sony do as they ask for email adresses etc and confirm the ulock)
Wondering about warranty.
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
dkryder said:
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
Click to expand...
Click to collapse
Ok thanks.
One last google noob question; does rooting usually need an unlocked bootloader?
On xperia root is more difficult to achieve with a locked bootloader, but can be done, thanks to the devs.
I guess I will read the 6P thread to get a feel for the situation.
Cheers again.
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
dkryder said:
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
Click to expand...
Click to collapse
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
mskip said:
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
Click to expand...
Click to collapse
I sure hope so. That's one of the only things keeping me from buying it already. It's kind of worrisome that the development forums are almost completely dead (save for the one thread trying to get root without a custom recovery, of course). I guess I'm just spoiled by using only Nexus devices, so having very active development is usually the norm.
well, the thing was only a rumor about sales start up until a report in a german site on 12/5 or so that sales would start 12/8 and then on 12/8 a confirm that at 1pm eastern u.s.a. sales would begin. talk about giving people a decent notice about a device this pixel c was a new low for google. it's almost they decided to sell them as android tablet at last moment instead of tossing in trash as a complete failure as chrome os tablet so, yeah, it will take a while for anyone that has skill to develop this device to ante up the funds and take delivery. if bootloader remains locked and boot temp recovery to flash supersu does that restrict the root in any way? i am just curious about this as my bootloader is unlocked.
Hey everyone,
I've tried to google around and search the forums on XDA but there is no straight up answer to some questions I have. This is the first HTC device I own and although I have been rooting/unlocking devices since the Nexus 4, I am afraid to go ahead with this one. I just wanted the answers to the following questions, if anyone here knows them please:
1. Unlocking the bootloader seems straight-forward and supported by HTC. I'm in the UK which means no Uh-Oh protection. If something was to happen to the device and I sent it back under warranty, would I be ****ed or would HTC replace/repair it? HTC UK's call center was worse than useless and HTC US' policy doesn't apply to us so I thought I should ask here.
2. Does unlocking the bootloader and rooting mean I will lose access to the fingerprint scanner, camera quality or anything 'stock'? I know Android Pay won't work but at the moment I am not too bothered either way because it's a hit and miss thing with it.
3. Finally, is there a way to completely revert unlocking the phone/s-off and going back to S-ON/Locked without any signs of having messed around with the device? I ask in relation to question 1. If unlocking the bootloader voids the warranty for UK users, is there a way to go back to stock and make the phone as though NOTHING was done to it?
Thank you to anyone who helps answer even 1 of these questions :victory:. I want to root and get xposed onto my new device but not at the cost of losing features on a brand new phone or losing warranty on it either :silly:
1. I can't comment on this simply because I don't know and don't want to spread false information.
2. You will not lose any features at all. In fact, I'm running a bootloader unlocked and rooted setup and Android Pay still seems to work fine for me. It let me add a debit card but I haven't yet been able to actually try to purchase something.
3. Yes, if you are S-Off you can completely revert back to a locked bootloader with S-On if you want to.
I'd recommend both unlocking and S-Off so you can revert back to stock in the future for a warranty claim just to be safe.
jaredkzr said:
1. I can't comment on this simply because I don't know and don't want to spread false information.
2. You will not lose any features at all. In fact, I'm running a bootloader unlocked and rooted setup and Android Pay still seems to work fine for me. It let me add a debit card but I haven't yet been able to actually try to purchase something.
3. Yes, if you are S-Off you can completely revert back to a locked bootloader with S-On if you want to.
I'd recommend both unlocking and S-Off so you can revert back to stock in the future for a warranty claim just to be safe.
Click to expand...
Click to collapse
Hey, thanks for the reply! Only just saw this, not sure why it didn't notify me.
Right no worries about point one seeing as point 3 makes it irrelevant if I can revert back and save my warranty anyway. Just to be sure on points 2 and 3, I can definitely 100% go back to Locked/S-On status and the system won't show I have messed around at all? As for Android Pay, that's cool! Did you set it up before or after rooting? And does your fingerprint scanner work? Can you make payments on google play by authorising with your fingerprint?
Thank you again for your help!
Devzz said:
Hey, thanks for the reply! Only just saw this, not sure why it didn't notify me.
Right no worries about point one seeing as point 3 makes it irrelevant if I can revert back and save my warranty anyway. Just to be sure on points 2 and 3, I can definitely 100% go back to Locked/S-On status and the system won't show I have messed around at all? As for Android Pay, that's cool! Did you set it up before or after rooting? And does your fingerprint scanner work? Can you make payments on google play by authorising with your fingerprint?
Thank you again for your help!
Click to expand...
Click to collapse
Yep, you can definitely 100% go back to Locked/S-On state assuming you were previously S-Off. There will be no signs that the device was messed with.
For Android Pay, I had initially set it up prior to rooting but the rooting process wiped my phone. I had no issues setting it up again on a freshly rooted install.
Google Play and every other app that uses it still fully supports authorization via fingerprint. From what I can tell, I have lost absolutely no features by rooting. There really is nothing to lose once you get past the initial phone wipe that occurs when you unlock the bootloader.
jaredkzr said:
Yep, you can definitely 100% go back to Locked/S-On state assuming you were previously S-Off. There will be no signs that the device was messed with.
For Android Pay, I had initially set it up prior to rooting but the rooting process wiped my phone. I had no issues setting it up again on a freshly rooted install.
Google Play and every other app that uses it still fully supports authorization via fingerprint. From what I can tell, I have lost absolutely no features by rooting. There really is nothing to lose once you get past the initial phone wipe that occurs when you unlock the bootloader.
Click to expand...
Click to collapse
Ah that's great! Would've thought HTC would implement some kind of security thing where rooting may cause the fingerprint scanner to not work like Samsung/Sony have. Good on HTC :highfive: I'm gonna start reading up now and unlock/s-off/root the phone in the next few hours! :fingers-crossed:
Devzz said:
Ah that's great! Would've thought HTC would implement some kind of security thing where rooting may cause the fingerprint scanner to not work like Samsung/Sony have. Good on HTC :highfive: I'm gonna start reading up now and unlock/s-off/root the phone in the next few hours! :fingers-crossed:
Click to expand...
Click to collapse
Yeah, it really is a great thing they've done! HTC is being really friendly to developers and power users. If you have questions or need some help with the unlocking or rooting feel free to drop me a PM!