Question About Rooting the Note 2 - Galaxy Note II Q&A, Help & Troubleshooting

Hi guys,
Considering switching to the Note 2 on AT&T. I've been debating it but think I'm going to make the switch with the comfort of AT&T's return policy. My concern is this: What if I take the phone, root it, flash a custom rom and something goes wrong. Is this like iPhone jailbreaking which voids the warranty or what? I'd hate to switch and then brick the phone and have no recourse. Just wondering, thanks.

Trust me nothing will go wrong rooting or flashing - all you have to ensure is that you take your time to read and understand the instruction (not to mention that you'll have to follow em precisely). Even if you get into soft bricks its easily re storable. Hard bricks are rare these days and happen only when some people do utter senseless (no offense) things like flashing Rom of another origin . Moreover you can always open threads of this sort for any help if you get stuck somewhere
leap before you think

Yeah, just a little nervous because after rooting my Nexus 7 I almost bricked it somehow. I'm not tremendously technologically advanced, but I'm no slouch.
I have a Mac. Is this a guide you'd recommend?
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/

JJ2525 said:
Yeah, just a little nervous because after rooting my Nexus 7 I almost bricked it somehow. I'm not tremendously technologically advanced, but I'm no slouch.
I have a Mac. Is this a guide you'd recommend?
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/
Click to expand...
Click to collapse
At this point you can entirely root and flash new roms without the use of a computer. There's an apk on here, exynos exploit, that will root you in a snap. From there, you install a new recovery (cwm or twrp), and then flash yourself silly.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html

Related

[Q] Quick summarize [yakju+bootloader+root]

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.

[ADVICE] How to avoid a hardbrick

Recently, i experienced the drama of having a hard bricked phone. Its a real headache, because you know that you wasted money into a useless brick, and if you send it to the assistence, you arent going have your cell phone for weeks, or even months. So, maybe you already heard those advices, but you need to make sure you never will never commit such an error.
Im not talking that root may damage your phone. If you do it right, it will not. But what can brick your phone is your attitude after root. Flash roms or kernels can brick your phone, but only using avast anti thief root options can not. Have this in mind.
1- NEVER (repeating, never) flash something that ISNT for your phone. It may be to the HNA-G7533339LS, but if you flash it on the HNA-G7533339 without those LS, you can get into touble. The firmware were for GT-S7500, but i flashed it in a GT-S7500L. Result: Brick
2- Dont think that if you have Clockworkmod backup or something like that, you cant brick anyway. If your bootloader gets corrupted, nothing will save you. Nothing. And you may corrupt it by flashing roms the wrong way.
3- Read the comments at the ROM that you are going flash, at less. Or make a search at Google. It may save your ass. Recently, lots of Galaxy S II owners had trouble with a leaked ICS kernel, and they bricked their phones, so read before doing ****.
4- I dont recommend flashing homemade custom roms or flashing untested ROMs, but someone needs to be the first. Only do this if you are really sure of what you are doing.
5- Asking dont hurts. If you are uncertain, ask. Its the best way to avoid problems.
6- For security reasons, always flash having a recently charged cell phone, seated on something, to avoid a falling smartphone. Also, if flashing throught ODIN, its preferable using a charged notebook.
7- Have a usb jig at your home. It may save you at some cases. You can buy one at www.dealextreme.com , or make your own.
8- And the last, after a hard brick, dont think your game is over. If you are under warranty, and your cell phone is truly bricked, send it to a assistance, and play dumb, like "I dont know what happened, but it turned off and isnt rebooting anyway". It isnt right to lie, but it may be necessary, for serious. Thay arent going cover a custom flashed phone. If it isnt under warranty, find someone with a riff box at your city. It may fix your phone.
I hope those advices can help you to avoid headaches.And know that Im not saying "dont flash roms". They may wonderfully boost your phone, and give it a new face. Only be sure of what you are doing Sorry by my bad english (it isnt my native language) , and bye!
gabriel2anjos said:
Recently, i experienced the drama of having a hard bricked phone. Its a real headache, because you know that you wasted money into a useless brick, and if you send it to the assistence, you arent going have your cell phone for weeks, or even months. So, maybe you already heard those advices, but you need to make sure you never will never commit such an error.
Im not talking that root may damage your phone. If you do it right, it will not. But what can brick your phone is your attitude after root. Flash roms or kernels can brick your phone, but only using avast anti thief root options can not. Have this in mind.
I hope those advices can help you to avoid headaches.And know that Im not saying "dont flash roms". They may wonderfully boost your phone, and give it a new face. Only be sure of what you are doing Sorry by my bad english (it isnt my native language) , and bye!
Click to expand...
Click to collapse
Hey Thanks a lot for this.. I really needed this.. if it is possible then please help me with my doubts...
OK.. I will directly get to the point... I want to do "something" for my phone, the Galaxy S Advance... like create a custom Kernel or a ROM for this device... Now I'm a total "newbie" in all these.. so this will be my first time... now my question is: Which will be easier and SAFER to make; a custom ROM or a kernel?... Because I will obviously be the first one to try my own creation so like please tell me which one will be safer for me to try out? So that even if I do something wrong - I will still be able to fix it without spending any money on Repairing from shops...
Sami Kabir said:
Hey Thanks a lot for this.. I really needed this.. if it is possible then please help me with my doubts...
OK.. I will directly get to the point... I want to do "something" for my phone, the Galaxy S Advance... like create a custom Kernel or a ROM for this device... Now I'm a total "newbie" in all these.. so this will be my first time... now my question is: Which will be easier and SAFER to make; a custom ROM or a kernel?... Because I will obviously be the first one to try my own creation so like please tell me which one will be safer for me to try out? So that even if I do something wrong - I will still be able to fix it without spending any money on Repairing from shops...
Click to expand...
Click to collapse
If it's your first time and you don't know a lot about these, the safer(and easier) would be, for sure, trying to create a custom ROM. A kernel requires lots of knowledge, you need to compile things, code, make magic.... It's hard and dangerous, cause it's the bridge between firmware and hardware. If something go wrong, you are gonna have a bad time. But the rom creation process is much more easy, there are lots of tutorials, and if u know how to use Linux there is even a tool called dsxda kitchen(or something like that). The chances of bricking are smaller(but are still present) and it usually makes the device better.
So, if u are really need it, first get experience creating a ROM. Only think about kernels later.
Hope I helped, and good luck :thumbup:
Enviado de meu GT-P5110 usando o Tapatalk 2
Useful video for newbies
I've uploaded one video on YouTube last January, that should help beginners what to do, as well as read in the text step by step and translate it (many people who visit this forum don't understand very well english, so they can copy&paste it into their translators). Here is the link:
http://www.youtube.com/watch?v=0NXBN9Z63TY
Last January I've read in different forums that many people had issues with "E: signature verification failed" even after successful root, as sometimes they just rooted but didn't have CWM recovery yet.
There were no good explainations how to solve it so I did that video, on the example of Samsung Tab 2 GT-P5110.
The video has helped many people, meanwhile it's clicked nearly 50K times....
Cheers!
My Micromax Bolt Q370 doesn't have any custom recovery available. But I am rooted, Xposed Installed. (Installed using terminal), Dolby Atmos installed (Installed through Flashfire).
Yeah, but I soft bricked it many times (6 times) and have to fix it in service centre.
Now I know what's healthy for my phone, and what bricks my phone. Now I'm stopped playing with root apps, until somebody make a custom recovery for my phone.
gabriel2anjos said:
If it's your first time and you don't know a lot about these, the safer(and easier) would be, for sure, trying to create a custom ROM. A kernel requires lots of knowledge, you need to compile things, code, make magic.... It's hard and dangerous, cause it's the bridge between firmware and hardware. If something go wrong, you are gonna have a bad time. But the rom creation process is much more easy, there are lots of tutorials, and if u know how to use Linux there is even a tool called dsxda kitchen(or something like that). The chances of bricking are smaller(but are still present) and it usually makes the device better.
So, if u are really need it, first get experience creating a ROM. Only think about kernels later.
Hope I helped, and good luck :thumbup:
Enviado de meu GT-P5110 usando o Tapatalk 2
Click to expand...
Click to collapse
yet the lineage OS devs STRONGLY advise AGAINST me doing this since i dont know what im doing, so how tf is this easier 0.0 (as my device is unsupported)

[Q] Rooting and ROM

Hello, this is the first time posting on this forum and relatively new on the android platform after jumping ship from blackberry. So, i have afew questions i hope you guys can help me with.
1. I heard/read alot regarding rooting to bring out the full potential of an android(s4) phone. What is the full advantage of rooting my phone? How does granting administrative access affect my phone performance?
2. I often see the jargon of bloatware on this forum, what does it exactly mean?
3. What is the function of ROM?
Sorry if these qns are repeated, please direct me to the answer if it is already present in the forum. thanks
1. Ans
2. Ans
3. Ans
---------------------------------
Still confused between Samsung Galaxy S4 and 10 acres of land in London
Rooting your phone gives you access to do anything you want ie (Apps 2 sd) that the phone dosent permit you to do.
A ROM is just a different feel, and its a faster alternative in upgrading your android ios. (S4 has touchwiz, can change it to Htc Sense)
Bloatware is a bunch of unnecessary apps that Carriers know youll never use but have it just cause. Its annoying and it takes up space. Rooting allows you to delete these apps, cause if its not you wont be able to remove it.
I hope this helped, ask again if you have any more questions.
Sent from my SGH-M919 using xda app-developers app
I was wondering if there is a sort of rooting guide for dummies out there. I want to root my phone to get rid of some of the bloatware that I will never use, and also to delete the annoying start up and shut down sounds. Other than that, I'm happy with Touchwiz so far, but I suppose adding custom themes would be fun.
I rooted my last phone (Samsung Vibrant) over 2yrs ago and don't remember how I did it. I know I installed a custom ROM, but don't remember how to do that either. I remember following a really good guide with pictures and step by step instructions though. It's early days yet with the S4, but I really hope someone will do the same kind of guide because it's very helpful for those of us who like to customize but don't have the time or knowledge to seriously get into it. When I look at some of the threads on rooting it just seems like a foreign language to me!
Sent from my SGH-M919 using xda app-developers app
mahgnillig said:
I was wondering if there is a sort of rooting guide for dummies out there. I want to root my phone to get rid of some of the bloatware that I will never use, and also to delete the annoying start up and shut down sounds. Other than that, I'm happy with Touchwiz so far, but I suppose adding custom themes would be fun.
I rooted my last phone (Samsung Vibrant) over 2yrs ago and don't remember how I did it. I know I installed a custom ROM, but don't remember how to do that either. I remember following a really good guide with pictures and step by step instructions though. It's early days yet with the S4, but I really hope someone will do the same kind of guide because it's very helpful for those of us who like to customize but don't have the time or knowledge to seriously get into it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Try the motochopper method - the guide is pretty simple and self explanatory however if you're on latest kernel then rooting is a no go as of now
---------------------------------
Still confused between Samsung Galaxy S4 and 10 acres of land in London
nikufellow said:
Try the motochopper method - the guide is pretty simple and self explanatory however if you're on latest kernel then rooting is a no go as of now
Click to expand...
Click to collapse
Thanks I looked at that and it seems straightforward, but I'm concerned about what to do after the actual root. Things like how to back the phone up in case I mess it up, how to delete things, how to add things. Also I find a lot of the terminology confusing... not quite sure what all the acronyms stand for either, like ODIN or CWM, or what each thing does exactly. This is the kind of thread which would be totally useful: http://forum.xda-developers.com/showthread.php?t=849028 (this one is for the Vibrant though, so I think a lot of it would be different on a different device?)
As far as the kernel... as far as I know nothing has been updated. I got the phone on the first day it came out so I'm assuming it doesn't have the latest kernel. How would you find out? Not even sure what the kernel is or what it does :\ I would like to find out though!
^^^then you might be on an earlier kernel version anyway trying to root by motochopper method won't brick your device even if it doesn't go successful so no worries.
ODIN is the same software that service centres use to revive your bricked device - as a matter of fact with Samsung drivers, a usb cable and stock rom downloaded from online sources like sammobile, you can revert almost any instances of soft brick. Simply saying ODIN will flash back factory/stock rom anfd make your device as it was when you bought it. And yeah flashing via ODIN and all are more or less same procedure for all Samsung devices
Cwm is a custom recovery. If you don't know what recovery means it might be worth googling for better understanding the concept as even my knowledge is limited and my explanations might fall short of your expectations
---------------------------------------------------------
" Maximus Decimus Meridius, commander of the Armies of the North, General of the Felix Legions and loyal servant to the TRUE emperor"
with regards to rooting my s4 which is running on 4.2.2 jellybean, does motochopper actually brick my phone? In addition, can i root my phone to remove the bloatwares and afterwhich, unroot my phone again, with all the bloatwares already permanently removed? Is it possible to download the full list of softwares of the s4 online such that if i accidentally remove an important software, i will be able to restore it. As I am someone who is not into very much customization and over-clocking, i believe i dont need my phone rooted for custom ROM right? I can use stock ROM when my phone is unrooted and clear of bloatware?
Mami-dalous said:
with regards to rooting my s4 which is running on 4.2.2 jellybean, does motochopper actually brick my phone? In addition, can i root my phone to remove the bloatwares and afterwhich, unroot my phone again, with all the bloatwares already permanently removed? Is it possible to download the full list of softwares of the s4 online such that if i accidentally remove an important software, i will be able to restore it. As I am someone who is not into very much customization and over-clocking, i believe i dont need my phone rooted for custom ROM right? I can use stock ROM when my phone is unrooted and clear of bloatware?
Click to expand...
Click to collapse
Steps
#1. Locate GS4 box, place phone inside box.
#2. Return to store and get iPhone.
Serious tho. Best thing you can do is READ. SEARCH and READ. SEARCH and READ.
If you are unsure about something, READ again. Most questions have already been asked and answered.
If you find yourself lost......SEARCH and READ. Believe me this is this most useful advice you will ever get here.
Stuff is so easy now compared to when android 1st started. I remember rooting my G1 on a terminal prompt and installing recovery with wicked long commands. Now everything is automated and the hardest (NOT) part is reading the step by step instructions provided on almost every mod and tweak.
Welcome and goodluck !

[Q] Preparing to root

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ยข.

Rooting without exploding the device? Have not had an HTC in a long time.

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.

Categories

Resources