I don't create threads on xda very often and 95% of my posts are me trying to help people out, but this is something I wanted to get off my chest.
It seems like everyday in this forum there are about 5 new threads of people "stuck in a bootloop" or "stuck on Google screen." The majority of these people don't know the difference between adb and fastboot or bootloader and recovery.
I bought the G1 on launch and there weren't tool kits. We had to use telnet and command prompt to do everything manually. I knew nothing about linux or coding, but I followed instructions and learned what was happening when I entered these commands. Through owning the G1 and then moving on to the Nexus One I don't remember seeing so many threads about people "soft bricking" their device. I think the reason for this is the tool kits and other scripts that make it almost too easy to unlock and root your phone. While I respect the people who write these scripts (and I think they do serve a purpose in some situations) I think it's causing more harm than good.
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Weigh in with your thoughts, criticisms or tl;dr comments.
Thanks.
EDIT 8/9/12: Link to efrant's Android Galaxy Nexus 101 guide. All the info you need to know. http://forum.xda-developers.com/showthread.php?t=1812959
EDIT 11/14/12 My Thank you & Goodbye post.
I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus
There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk
Leaving good enough alone.
It's getting pretty comical when you see a "help me" post and before you even start reading the post you can correctly predict that the post will start something like this: "so I flashed *****'s custom ROM and now my phone's f****d".
This thread is so full of #winning. The easy way is not always the best way.
I used the manual methods for my Atrix so now after getting a good feel for Fastboot and ADB, the GNex Toolkit was really painless to use.
I understand what you're saying though. I guess some people just want easy routes to get what they want, completely scrolling past the giant red text that tells them exactly what could (and most likely will) happen.
phaze one said:
I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm going to second this, as long as the toolkits are well documented (showing what they did where, and why it was done) they can save people time typing the commands and looking them up if they forget them.
It's very similar to creating a GUI front end for a program. If done properly they're nothing but useful and time saving.
Im guilty of using the wugfresh kit. I could have easily done everything myself, but it contained everything I needed.
I agree with pretty much everything you said though. I see people offering money for them to root their phone over team viewer, etc. Those are the same people that warranty their phone that they, themselves messed up.
Thanks for your feedback everyone.
I just wanted to clarify I'm not ripping toolkits. They are a great way to get where you want to go quickly. If you know what you are doing by all means use it. But, to me it seems like they are just the cheat sheet to the test. Yeah, you aced the **** out of the test, but when asked to apply what you should have learned from that test in a real life situation; you are screwed.
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.
The hardest part is just those drivers, not that I call it hard, just Windows can be a pita.
Once that part is working then using adb and fastboot comands I think is fairly straightforward and don't need the toolkit.
Im hardly experienced with Android or Linux. Ive used both for the past year or so only, and did take time to learn what abd commands there are etc. but also will use the toolkits to save time and headaches.
Anyways, its always like this. iOS hacking forums are similar.
Also, if you can get into recovery why do a nandroid? On SGS I was told by devs its not really needed as long as you dont mix up kernels. Do that, and what help is the nandroid? Cant flash it if you cant get into download mode. If you can, thats what stock images are for? I sync everything I really care about to cloud/PC.
El Daddy said:
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.
Click to expand...
Click to collapse
LOL...I wouldn't be here if I could
Toolkits for the nexus is kinda unnecessary because it is so easy to unlock, but there are devices that one the 1%(?) could unlock without a toolkit.
Sent from my HTC Desire HD using XDA App
I
adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
One-click rooting on my Fascinate:
I used z4root to root my phone before I flashed my first ROM (back then I just used ROM Manager for everything and didn't even bother looking at the ROM threads on XDA until the late DJ05/DL09 days when I got used to flashing manually in Clockwork Recovery). With z4root I didn't even need to use my PC to root, but it didn't always work when I had to go back to stock.
One-click Odin pitfalls:
My first experience with Odin was using a one-click version to flash a stock Froyo leak on my Captivate when they had just started making custom ROMs for Froyo. I had a bad experience using one-click Odin so I soon learned how to manually use Odin to do much more than simply flash a Froyo leak with one click. I soon discovered that Odin could be used to do much more than simply going back to stock - I could flash different versions of Clockwork Recovery, different Captivate and Fascinate modems, etc.
Learning adb for myself:
When I got my Gnex I used the exact method adrynalyne posted, and I found it more gratifying than any one-click root (I got my Gnex before there even was a 1-click, and I had long gotten used to adb. There's actually a lot more you can do with adb than simply rooting. If you only use it for rooting it's like going to a four-star restaurant and always ordering the hot dog from the kids menu - you're barely scratching the surface of what adb can do. I highly recommend reading up on adb and learning the different commands you can use. For example, it got me out of a bootloop more than once on my Fascinate when I was running AOSP MTD ROMs (long before jt1134 made 3-button recovery work on them).
The tl;dr:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Terminators run on Android
skynet11 said:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Click to expand...
Click to collapse
This is exactly my sentiment.
android01 said:
There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You just used 5 rhetorical sayings that make very little sense, in the context of this topic. Be helpful or don't post, maybe?
OP, I couldn't agree more. Too many people post here (and other places) about being stuck in a bootloop even though they should already know how to fix it, if they knew anything about the process they had gone through. It's utterly insane that people are making heavy modifications to a device that costs $650+ without knowing *what* they're doing.
It's like someone going outside to change the oil on their car without knowing a thing about it and following the most basic instructions from some random person on the internet, then freaking out when someone tells them they poured the oil into the power steering reservoir.
No-ones forcing you to help people who have screwed up their phone so I don't see the need to be all holier than thou about it. Why should people have to understand everything that goes on when they use a one-click method? People should just make sure they read the instructions so they don't screw things up. That's the problem, not the tools they use.
As has been stated before in this thread.. you can't stop the stupid, or protect people from their own stupidity.
After far too many years helping out "stupid" users (here and on other forums), unfortunately, I find it far better to pick and choose who I want to help these days. Then, if I get frustrated, I only have myself to blame.. for even responding in the first place.
Related
Hey everybody,
I'm planning on getting my GN in the next two weeks and wanted to ask a simple question:
first of all - I will want my GN to be a yakju, I will want to root it and I will want to unlock the bootloader.
Now, I believe I have everything understood just wanted to be sure if you could help me..
these are the steps I will take:
1. Check if GN is yakju
1.1 If GN is yakju simply use the gnex toolkit to unlock bootloader and root.
FINISH.
2. If GN is not yakju -
2.1 Use step-by-step (http://forum.xda-developers.com/showthread.php?t=1391881) to change rom to yakju 4.0.4.
2.3 Then use gnex toolkit to root (already unlocked bootloader in 2.1).
FINISH.
Am I good to go?
TNX!
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
deepayanneogi said:
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
Click to expand...
Click to collapse
Thanks mate! can't wait already
More replies are welcome.. I just want to feel certain I'm on the right track here..
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Jubakuba said:
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Click to expand...
Click to collapse
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
omricn said:
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
Click to expand...
Click to collapse
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Theshawty said:
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Click to expand...
Click to collapse
Tnx Actually I'm not going to flash custom roms\radios\BL's just yet (if ever), just going to flash the official 4.0.4 yakju from Google, including the radio that comes with that bundle
Jubakuba said:
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
Click to expand...
Click to collapse
I catch your drift, and I know exactly what you mean.. I'm an IT guy, and apart from my job, I always learn everything there is to know about anything before I buy\change it in any way, to always be super safe and know what to do in every situation I can encounter.
Before I do something I will triple check what could and can happen so that I'm always 3 steps ahead. Thats the reason I already know almost everything there is to know about this phone, about rooting it, about unlocking it, ADB, fastboot etc. even before I bought it call me crazy..
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
The 4.0.4 radio and bootloader will do for many more releases, I think. I don't think it's the radio's fault for the signal drops as a simple overclocking counters it.
Jubakuba said:
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
Click to expand...
Click to collapse
Best. Reply. Ever.
I've been using the GNex toolkit since I got my nexus and never had one issue. Even flashed stock 4.1.1 on it. My question is, why is everyone so against the toolkit? Why is it so dangerous? Please don't bash me because I came from an Atrix 2 and have only been using the nexus for a couple weeks but I'm just curious. Thanks.
Sent from my Galaxy Nexus using xda premium
http://forum.xda-developers.com/showthread.php?t=1469909
basically, the toolkits sometimes fail.. and fail hard. like at one point, the toolkit wanted to flash a verizon firmware on to a GSM phone (which can brick the phone). or something goes wrong, and the user has no idea how to fix it so the thread begins with "i used such and such toolkit, but i have no idea why my phone wont boot. HALP!"
I would like to say that the Toolkit actually is a shell of the adb command and fastboot command. That's all.
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
DarkJatrix said:
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Jubakuba said:
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Click to expand...
Click to collapse
I'm very familiar with ADB I had an HTC amaze and a couple days after the release I had to learn adb really quick in unlocking the boot loader and flashing custom Roms. I just like convenience of having everything in one folder and one program. I do trust ADB but my issue has always been putting files in right folders and pushing and pulling files etc. Lol. But I appreciate the info you guys. I'll think twice before using toolkits again.
Sent from my Galaxy Nexus using xda premium
Zepius said:
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Click to expand...
Click to collapse
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
withbloodskies said:
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm saying. I am plenty smart enough to read before I flash, therefore I wouldn't of flashed that and I wouldn't of had an issue but if someone else would've flashed it then it would've technically been their fault for not paying attention. I understand that the toolkit had the mistake but if I pay close attention than I'll notice the mistakes and avoid them. Does that sou d pretty knowledgeable?
Sent from my Galaxy Nexus using xda premium
Hi,
I want to root my Galaxy Nexus (T-Mobile) but the WugFresh root toolkit wants to know if my device is "TAKJU-MAGURO" or "YAKJU-MAGURO".
My settings don't mention either one: http://db.tt/SlNoG0Yi (screen shot)
How can I find it? I'm using the latest stock ROM from Samsung.
Thanks in advance...
Go into maps, check about, and it will list your make
root your maguro the right way.. fastboot OEM unlock, fastboot flash a custom recovery, flash either the su binaries or a custom ROM in your new recovery, reboot and profit. this is a nexus device, google made it easy for us to unlock our bootloader and root our devices.
simms22 said:
root your maguro the right way.. fastboot OEM unlock, fastboot flash a custom recovery, flash either the su binaries or a custom ROM in your new recovery, reboot and profit. this is a nexus device, google made it easy for us to unlock our bootloader and root our devices.
Click to expand...
Click to collapse
How is that easier than WugFresh?
BarryF said:
Hi,
I want to root my Galaxy Nexus (T-Mobile) but the WugFresh root toolkit wants to know if my device is "TAKJU-MAGURO" or "YAKJU-MAGURO".
My settings don't mention either one: http://db.tt/SlNoG0Yi (screen shot)
How can I find it? I'm using the latest stock ROM from Samsung.
Thanks in advance...
Click to expand...
Click to collapse
There's an option on wugfresh that says yakju-takju any build, when you select your build use that instead, then wugfresh will automatically find what build your gnex is an select the right one for you, I had wugfresh toolkit 1.5.5 version which is the latest, I assume you do to.
Sent from my Galaxy Nexus using xda premium
BarryF said:
How is that easier than WugFresh?
Click to expand...
Click to collapse
you can type three words right? "fastboot OEM unlock" unlocks you bootloader. then the four words "fastboot flash recovery recoveryname.img" flashes your recovery. then in your recovery you just select your file that you want to flash, then reboot. hows that harder than Wugs? then when you mess up your device, you will be familiar how to fix it, with your recovery or fastboot.
simms22 said:
you can type three words right? "fastboot OEM unlock" unlocks you bootloader. then the four words "fastboot flash recovery recoveryname.img" flashes your recovery. then in your recovery you just select your file that you want to flash, then reboot. hows that harder than Wugs? then when you mess up your device, you will be familiar how to fix it, with your recovery or fastboot.
Click to expand...
Click to collapse
That sounds way harder to me.
Sent from my Galaxy Nexus using Tapatalk 2
It's slightly harder but really great to know how to do in case you run into issues in the future. IMO a basic knowledge of fastboot is essential.
Sent from my Galaxy Nexus using xda premium
It seems a little intimidating at first, but with a little reading and patience it's not too difficult. I used a toolkit to root my Evo 4G and ended spending around 3 hours sorting out the problems it caused. I used the method simms22 is describing to root my GNex and even going slow it only took about 45 minutes. The biggest problem I had was getting drivers installed. Take a little time to read the stickies and get familiar with the process. I literally laughed at myself when I was finished and realized how simple those commands are.
Sent from my Galaxy Nexus using xda premium
BarryF said:
That sounds way harder to me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No it's actually easier. Really, just open an adb/command prompt and just type what simms said. Really basic. BTW it will be good to learn this so u can get the CWMR Touch for free and flash it via fastboot.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
As much as I would love to learn fastboot (really), I don't have the time, and now I'm scared of using WugFresh. I guess I will root my device another time.
Thanks for all the replies!
BarryF said:
As much as I would love to learn fastboot (really), I don't have the time, and now I'm scared of using WugFresh. I guess I will root my device another time.
Thanks for all the replies!
Click to expand...
Click to collapse
Nothing wrong with waiting until you are a bit more comfortable. Keep reading here at XDA. The more of that you are willing to do, the less scary it is. Check out the threads asking questions about problems. Even if you don't have the problem, you will be getting familiar with the terminology and problem solving methods.
Sent from my Galaxy Nexus using xda premium
Pierceye said:
It seems a little intimidating at first, but with a little reading and patience it's not too difficult. I used a toolkit to root my Evo 4G and ended spending around 3 hours sorting out the problems it caused. I used the method simms22 is describing to root my GNex and even going slow it only took about 45 minutes. The biggest problem I had was getting drivers installed. Take a little time to read the stickies and get familiar with the process. I literally laughed at myself when I was finished and realized how simple those commands are.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It's definitely a little intimidating at first. For me the hardest part was getting the sdk set up properly (I'm sure the alcohol didn't help ) but now I can't imagine using a kit or a "1-click" method.
TomBall718 said:
It's definitely a little intimidating at first. For me the hardest part was getting the sdk set up properly (I'm sure the alcohol didn't help ) but now I can't imagine using a kit or a "1-click" method.
Click to expand...
Click to collapse
Lol! Yeah, liquor and technology can make things unpleasantly interesting.
Sent from my Galaxy Nexus using xda premium
The truth is, I am an Android dev and quite comfortable with adb and the sdk. However I've never flashed a ROM or know anything about bootloaders, and only have one device to experiment with, which is my development device, and I can't take the chance of bricking it. The only reason I want to root right now is because I need to run an app that requires it (Screencast Video Recorder).
I wish I had another device to experiment with!
slayr76 said:
There's an option on wugfresh that says yakju-takju any build, when you select your build use that instead, then wugfresh will automatically find what build your gnex is an select the right one for you, I had wugfresh toolkit 1.5.5 version which is the latest, I assume you do to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Agreed! Its terribly easy to install SDK from Google, Download a recovery, download the SU (superuser) and a ROM of choice and be done with it within 3 minutes. The one-click stuff is convenient but always ends up with more problems. One step out of place and you brick your phone. Furthermore, if you can't run a simple command line on your computer, should you really be rooting your phone? Just common sense man.
andrewjt19 said:
Agreed! Its terribly easy to install SDK from Google, Download a recovery, download the SU (superuser) and a ROM of choice and be done with it within 3 minutes. The one-click stuff is convenient but always ends up with more problems. One step out of place and you brick your phone. Furthermore, if you can't run a simple command line on your computer, should you really be rooting your phone? Just common sense man.
Click to expand...
Click to collapse
I'm perfectly comfortable at a command line but this "simple command" just seems easier to you because you're very experienced and you can make assumptions that I can't. For example you make "download a ROM of choice" sound so easy, but I wouldn't even know where to start to choose and then find the right ROM. (Besides, I only want to root my current ROM, not change ROMs).
I also have no doubt that "one step out of place and you brick your phone" applies as much to fastboot as it does to WugFresh. No?
Anyway, in my personal experience there is always critical information missing or major assumptions in the docs for custom mods (even the one-click WugFresh docs assumed I knew if my phone was takju or yakju. What the hell is a takju or wakju???). Incomplete docs seems to be the #1 complaint around here when modding.
I wish I knew fastboot as well as you guys, and maybe one day I will, but right now I just need a rooted phone so I can video capture my screen. And I can't risk bricking my only device.
Thanks again for the advice!
You're right about basic assumptions regarding a new user's level of knowledge. It was what made me the most nervous about rooting. If you are already familiar with adb and the command line interface you have a pretty good head start. In the stickies section, Jubakuba, efrant and mskip all have some great information and guides about rooting. Some of the information is a little outdated but worth the read. Start with efrant's Android 101. That will answer a lot of your questions. Oldblue also has a good summary of all of the different firmware versions (takju, yakju). Most of us appreciate that you aren't just diving in and making a mess. Very few us have the money to risk screwing up a several hundred dollar device for the sake of curiosity or experimentation. If you are developing you have even more reason to be cautious. So take your time. As far as bricking the phone goes, you're in luck. The GNex is intended as a developers device and is difficult (not impossible) to hard brick. You've already found your way here to XDA, now it's just a matter of reading and learning. And, I know it's difficult, but try not to let your feathers get ruffled. A thick skin seems to be a prerequisite around here.
Sent from my Galaxy Nexus using xda premium
.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
NightHawkUndead said:
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
NightHawk hit the nail on the head. It would be best for you right now to read up and learn as much as you can about how the forum works as a whole and how development and custom roms recoveries etc work in general.....Here is a good place to start!
My note 2 is on its way,in the mean time ill be reading alot.
Sent from my Desire HD using xda premium
lamartino said:
.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
Click to expand...
Click to collapse
A lot of us would suggest you take a bit of time to read up on what you will need. I short a safe bet is to read twice and flash once. Doing any sort of flashing will void your warranty and you run the risk of damaging your phone. Granted most mishaps are fixable with knowledge and experience. For you however, having a bootloop or a soft brick would not be fun.
I suggest you get the proper drivers for your version of the n2
I suggest you read up on how to root the note 2: read the entire thread...yes it is repetitive,but at least you get an idea of what can go wrong and how to fix it be reading what happened to others. Then decide on what recovery you would like....read up on cwm or twrp and how to install them properly. once you have done all that...then it is time to flash a custom rom.
I think I would recommend you do a bit more reading before deciding wether rooting and flashing a custom rom is for you
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
topshelf95 said:
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
Click to expand...
Click to collapse
well done and i completely agree, but for someone who's so new you musn't forget to install the drivers for the device you have onto your pc or laptop or whatever is going to run Odin for you.... no drivers is the easiest and fastest way to ensure your shiny new device is on the short bus to not working right
it is often overlooked and ppl presume that they just do it - installing the drivers that is - and it's often mentioned in the rooting thread, but only in passing.
if you do not have the proper drivers your 700+ dollar device will not last long so do yourself a favor and make sure you have them installed properly and that your computer detects the device properly
when you plug into odin you should see a yellow background with COM and a number in it (changes depending on the usb port you are plugged into) if you don't have that, don't click the start button cuz you gonna be in the hurt locker in all likelihood even if you follow the instructions to a T.
I'm relatively new to all of this, only rooting my Evo, and now my Note 2.
I cannot stress enough how correct all the previous replies are. Read everything you can about your device and rooting in general. Use Youtube. Use this forum, use any information you can find. Learn the language(it can be tricky). Learn as much as possible and ask questions....just make sure you look for the answers before asking them.
Once you feel comfortable, the Devs do a solid job of making it easy for us, follow the steps and you should have success.
Here is a link to some terminology.....make sure to thank ThC23!
http://forum.xda-developers.com/showthread.php?t=1394458
You will make mistakes then become a pro. We all battled endless nights of fixing our devices after misreading one line.
Sent from my GT-N7105 using xda premium
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Edit: I'm using a lexar 128gb 633x U1 micro sd and all is well. Worked with adoptable storage also but felt a little sluggish so I went back to using it as external storage.
AndroiderM said:
I was in the same boat haven't owed an HTC since the Fuze running Windows lol and have been a loyal Samsung user since the S1 so the whole adb fastboot thing was a little overwhelming. I followed the guide in the forum and had a few hiccups but overall went pretty smooth. Adb is definitely not as user friendly as Odin on a Sammy device but not to difficult. My only tips would be make sure you have all the latest drivers, twrp, and adb installed. It seems pretty hard to permanently brick a device these days from my experience so I wouldn't worry to much. As far as the radio not working, as long as you keep your device encrypted you won't lose your radio. I'm sure the devs will find a fix for this soon enough. Enjoy your new 10!
Click to expand...
Click to collapse
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Locklear308 said:
Well I am comfortable in adb :3 so that's not a worry. So un-enecrypting it is just an option, and I should just avoid it for now? What is the advantage of un-encrypting it?
What guide did you use? Also, what about all this firmware and ruu stuff?
Sorry for so many questions... Lol this thing wasn't cheap and I am nervous , BTW what setup do you have? Root? ROM?
Thanks for replying :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
AndroiderM said:
http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
From what I understand unencrypting breaks the radio. With it unencrypted you would get slightly better performance and boot times I think. I would definitely avoid it for now. I'm currently using twrp with Viper 10 rom. I've also used leedroid and still trying to find which one I prefer. I've only had my 10 for 3 days lol so I haven't found my sweet setup just yet. I left s-on for now as I don't really need it off.
No idea about the firmware and ruu stuff. I made a backup of stock rom before I started flashing. I'm pretty sure there is or will be a repo with factory firmware, radios, etc. I don't know what ruu stands for either lol.
---------- Post added at 06:56 AM ---------- Previous post was at 06:51 AM ----------
Did you get carrier or unlocked version
Click to expand...
Click to collapse
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Locklear308 said:
Unlocked, at least that's what the guy on Swappa marked it as. *fingers crossed*
Got it for 510. One scratch on the metal
Alright so I will back things up and avoid the radio breaking stuff. I will check that link, thanks man
Click to expand...
Click to collapse
No problem, mine has two scratches on metal too lol but guy gave me $200 and unlocked htc 10 w uh oh protection and original receipt for my s7e at&t branded locked bootloader ?. Was a no brainer for me
Locklear308 said:
Just ordered my HTC 10, excited...and nervous as I've not had a new device (like long term) in... like over 1.5 years. :S I'm mainly hoping the microSD card slot likes my 128GB U1 x633 card so I can finally have enough space for all my vinyl rips, and then I hope the DAC is as good as they say.
So anyway, I've been reading all of this stuff about rooting and loosing the radio connection and something about the data encryption breaking everything O.O!!! Holy crap. I just wanna root it, find a good rom and dev to support and enjoy it. This is what I do on my current daily driver, my old OPO. I've been trying to look around, search, and read to make sure that I avoid all of these issues mentioned but so far I've not found a concrete explanation of why said issues happen. Not new to rooting/flashing at all, but HTC devices always seemed to of been touchy when it came to custom stuff, and I don't want to explode this thing. My main problem is that I've been away from HTC for.... well since early 2014.
My current knowledge of android stuffz tells me to:
1) Unlock Bootloader via ADB
2) Flash TWRP/Other Customer Recovery
3) Find sweet rom, flash and spend hours customizing
4) Flash xposed and go crazy with modules until the phone explodes and then scale it back to a realistic level
5) Enjoy Phone
6) Cake
HOWEVER... I remember HTC devices having a bit more complication due to things like... RUU and firmware.. I don't even remember what RUU means lol... But I remember when I had my M8 I was always fighting these dang firmware issues. While I ended up with a fantastic experience, I remember fighting for almost 2 months or so to get it to behave. Battery was out of control, phone was crashing, camera exploding. Oh man it sucked, but finally someone really cool was like... "Yo dude I had these issues, this is what you have to do with HTC stuff" , and after a full hour of flashing shiz I had the phone running smoothly and behaving correctly. Something about... you had to flash each level of the firmware and then reboot and...something. Like you couldn't just skip to the latest firmware? I don't remember exactly.
So anyway, the main question I have is. Could someone either
A.) Point me in the direction of a post or something to study to understand what to do and not do. I've searched but not really found anything solid. Something for folks who've been off the HTC scene for a while.
B.) If there isn't really a single post on this, perhaps if someone doesn't mind explaining this (even pm is fine) to me so I don't explord this expensive mofo and cry.
C.) Give me a hug, because I am nervous about having a new device O.O , it's been so long and I'm so used to Cm13 and xposed and all that jazz. I is be scared.
I would be grateful to any and all help/support.
Anyway, thanks in advanced guys and gals. :3
Click to expand...
Click to collapse
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
purple patch said:
I'm on my third htc10. Exploded last two after rooting haha. Really not hard mate. Just read the guides provided and ask any questions you need. Most ppl on XDA will be helpful, and some will reply like me lol.
BTW, simple answer, unlock phone via HTC Dev, then flash Viper. Done.
Click to expand...
Click to collapse
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Locklear308 said:
Alright neato, so do I need to ensure I let it download any and all OTA's for the firmware before doing anything? Is s-off safe to get as well in regards to the issues I referred to in my OP above?
And his is this viper? Does it allow things like settings similar to cm and also allow for xposed?
Thanks for replying man, I feel more comfortable now as it sounds like there isn't anything crazy required to safely root this thing . Phew!!
Click to expand...
Click to collapse
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
DroidIt! said:
I got an M9 for my wife not that long ago and just had my 10 show up today and gonna root. Just do like the other dude said. Find a guide that says how to use HTC dev to unlock the bootloader. You can't just enter a command in adb like "unlock bootloader" and have it work. Go to the HTC dev website, make an account, pick your device and it walks you through the steps of unlocking the bootloader. That's really the only semi-difficult part IMO. Then proceed as normal. Download twrp, make a stock nand, download ROM, su binaries, kernel, etc. etc. go to recovery and flash. I'm sure there's a couple other steps in their but that's the basics.
As for Viper, it tends to come with so many mods built in, I'd personally be kind of reluctant to use xposed with it to to much modifying. It's a great ROM, but so is leedroid You can try each and see what you like, but if you want to more safely use xposed I'd personally go with leedroid.
Click to expand...
Click to collapse
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Locklear308 said:
Oh right, I do remember about the whole HTC dev website thing. I was mainly just concerned with the firmware issues and stuff that I had before.
Is there any kind of limitations for reasons not to upgrade to the highest available firmware? Something like, maybe the highest one can't be rooted yet or something like that. I just want to make sure that I don't shoot myself in the foot haha.
Thank you all for your help
Click to expand...
Click to collapse
Hey, I'm not sure about firmware not being able to be rooted but the best way to go about it (what I did anyway) is to unlock the phone via htcdev.com, flash a custom recovery (Latest TWRP which has also worked around the encryption stuff?) and then back up everything other than the data partition. That way, no matter what you do, you always have something to revert back to. The reason for not backing up data is due to the encryption. From my understanding, restoring an encrypted data partition would break things. Once you have the phone unlocked and recovery sorted, you are free to flash viper etc. and root the phone using SuperSU. I'm sure you are aware unlocked devices are quite easy to root so whatever you flash will most likely be on latest firmware, already rooted.
As for installing OTAs etc., you need unmodified system and recovery which is where the backups kick in. Simply back up your data on an SD card (pictures etc. not the actual partition) and restore the system-image and recovery. This should reset the phone although I'm not sure if it'll wipe anything and allow you to do OTA updates. Alternatively, get the latest firmware for your device from htcdev (again, not sure if they have firmware on there) and use that instead.
If any of the information above is incorrect or missing steps, someone feel free to correct me.