I need help rooting my device, I have tried some methods to do so but it always says it can not but done or not supported. I know an ideal option would be to get a new phone but in the time being I can't as of now. I'm new to all of the rooting stuff, so I am not sure if there is a root for my phone or not. I saw another thread talking about this but it was very confusing to me and I felt like I could have gotten lost doing it and may end up messing my phone up, as it didn't seem to go much into detail. Also wanted to know if there is a method of rooting it that doesn't require it be online the entire time, my phone has a hotspot and I don't have wifi here. If I do then I can try this when I do get some
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.
Sorry about the double post. i first posted this in the Q&A.....
So i am a iphone user moved to android. im trying to root my phone and just cannot seem to get it running.
I have download simple root .1
I click setp1, it does its thing, goes to the skating guys and i do what it says.
Next i do step 2, same thing. skating guys, i do what it says.
now when i click step 3 the phone reboots and on my phone i get a phone with a read ! and triangle over it. nothing happens after that......
reboot the phone nothing seems changed.... what am i doing wrong?
anyone have a more complete "walk through"?
Also, i am a little confused. some people are saying to put "roms" onto the phone. are the roms like the OS? how do i wipe the phone and put a new rom on?
i am looking to get 2.3 onto my phone and get free wifi hotspot tethering.
i am running windows 7 ult. 64.
also, any links where i can get apps that only rooted phones can get?
any help would be great. sorry for the noob questions
Root using Unrevoked. It is the easiest method by far. Once you have root and s-off, you can worry about flashing custom roms. I'm not sure what you mean by "simple root .1" so you may want to post a link to what you tried so we know where you stand.
Also, it'd be easier to help if you provide your phone info as far as which hardware version, what software is on it now, which hboot, etc. If this is all new to you, then read some more and get a better understanding of this before you mess up your phone.
Can you boot your phone normally or is it stuck somewhere?
Simple root it outdated, you can check out the following thread for info on how to root.
http://forum.xda-developers.com/showthread.php?t=865204
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.
S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).
You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.
Hello everyone, I am very new to all of this so please have patience with my noobness. I have heard of people rooting their devices, and flashing custom ROMs and what not. I really like the look of cyanogenmod, and the functionality it would bring to my locked up AT&T HTC One M8. I found this http://forum.xda-developers.com/showthread.php?t=2708628 thread that seems like a pretty promising and easy method to achieve root, S-off, and an unlocked boot loader. I almost went through with it today, but I really wanted to be more prepared. I am most scared about bricking my phone while it is still on contract and being stuck without a phone until march when my contract expires.
Basically what I want to know is is it possible to brick your device just by chance? Say I followed a trusted guide, did everything down to the dot, is there still a chance that my device could get bricked just by chance?
Also what are things that I should avoid to prevent getting bricked? Any veteran tips for a newbie? Anyway, thank you for your patience and help!
Hackentosher said:
Hello everyone, I am very new to all of this so please have patience with my noobness. I have heard of people rooting their devices, and flashing custom ROMs and what not. I really like the look of cyanogenmod, and the functionality it would bring to my locked up AT&T HTC One M8. I found this http://forum.xda-developers.com/showthread.php?t=2708628 thread that seems like a pretty promising and easy method to achieve root, S-off, and an unlocked boot loader. I almost went through with it today, but I really wanted to be more prepared. I am most scared about bricking my phone while it is still on contract and being stuck without a phone until march when my contract expires.
Basically what I want to know is is it possible to brick your device just by chance? Say I followed a trusted guide, did everything down to the dot, is there still a chance that my device could get bricked just by chance?
Also what are things that I should avoid to prevent getting bricked? Any veteran tips for a newbie? Anyway, thank you for your patience and help!
Click to expand...
Click to collapse
I would spend more time searching and understanding the phone first...Yes you can have a $600 bricked phone. Rooting is not hard, but there are always risks. Educate yourself thoroughly first, then make a decision.
Sent from my SM-P600 using XDA Premium HD app
I agree with GalaxyNotes, though it is rare to brick your phone just from rooting, its possible. You are more likely to brick it trying to flash an incompatible rom or kernal. Also there is ALMOST always a way to repair your phone should you hard/soft brick it. Spend a little more time researching and if you have questions a long the way there are people here who will help you out.
That first root/unlock/flash is always to most agonizing. Like everyone said take your time. If you don't understand something just a little bit, ask. Also the best thing to do is get your system unlocked and custom recovery installed so you can get your current image backed up. That way you have a known good working copy of your current system and pretty much makes you brick-proof. I've downloaded and have all necessary files etc. to root my device but I'm waiting on my warranty period to end. I just don't want to deal with customer service if something happens to my phone and I'm unlocked. I've seen people have no problems and others all kinds of problems trying to get service after unlocking.
Good luck.
I would recommend not going to CM. Not that CM isn't great, it's just not that great on our phones. The general concensus is Sense > GPE > CM/AOSP. Of course it's not like this for all devices... It's just that HTC does a VERY good job with Sense. You just can't beat it's features and stability. I've gone the route of switching to AOSP and GPE, but always ended up going back because it just felt like it was lacking something. To each their own of course, but I just wanted to share my 2ยข.
I'm actually pretty frustrated right now. This is not my first time messing with an Android phone. I've had several in the past, have dabbled in installing various custom roms, etc., but the guides for this phone seem to universally suck. I have a developer edition Note 4 that I rooted and unlocked the bootloader when I first got it. I bought the developer edition because I knew the bootloader could be unlocked easily, which I thought was supposed to make installing ROMs easier and less hacky. Now, It's been stuck on KitKat 4.4.4 for over a year and a half, and I wanted to update it to 6.0, but it seems like a massive pain in the ass. What gives? I'll link to all the guides I've followed thus far.
First, I found this: http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This is all I wanted to do. This guide told me to upgrade and (re?) unlock the bootloader via this guide:
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
This guide, for whatever the reason, tells me that even if I have a DE, I should install this other ROM for some inexplicable reason, then re-unlock the bootloader. Okay then. That points me to ANOTHER GUIDE:
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
And this guide tells me I have to root to unlock the bootloader (a reasonable assumption) but doesn't tell me how. I don't know how I did it the first time dude, it's been over a year and a half! So, with some searching I found this freaking 40 step guide:
http://forum.xda-developers.com/not...ide-how-to-root-verizon-galaxy-t3454593/page2
Now, not only is this guide stupidly long, its 'helpful' link to all of the software needed is broken. So I searched for the crap myself. I tried KingRoot, which rooted at first, but had other issues. I switched to Kingo Root, which seems to have worked better. I was able to get the n4-fix file to /data/local/tmp, change the permissions to be able to execute it, and run it. It seemed like I was finally making some progress. Except, when the phone restarted, it got stuck in a boot loop at the Verizon logo screen.
I don't know where to go from here, but I am really at my wit's end on this one. I've been working on this for 2 days. And before anyone asks, yes, I backed up my aboot, and I also have backups using TWRP from when I first got the phone and from its most recent state before I changed anything. Though, I don't know how to restore aboot, so if that's a problem, I'm pretty screwed.
Help would be greatly appreciated, before I throw my phone against a wall and buy a new one. I like this phone. But it really started to get bogged down and stop working right, so I thought it was time for an Android upgrade.
---------------------
I got it working, after hours. There were a couple things at play here, chief among them is the fact you have to remove the SD card from the device after attempting to unlock the bootloader, because it causes a boot loop. I also had to do a factory reset after flashing even in some cases where it wasn't specifically stated. Pretty frustrating. Anyhow, hopefully I don't have to ever go through this again any time soon. I made it to 6.0.1.