Related
Hey guys! I'm picking up an Xperia Play in a couple of days and was looking for some general advice about the phone. This will be my first Android device, I've been on WebOS/Garnet for my last two phones. I'm just a little overwhelmed with the options presented by the Play and Android in general. For instance, I'm not sure if I should root my phone or not - what are the advantages?
Any other general guides to Android/the Play would be wonderful if any such guides exist. I'm looking to deck this thing out with every emulator on the market as well as get the PSXperia hack up and running (I've downloaded the program, but can't figure out how to use it).
You can sense my overall noobishness in general, I'm sure. Any advice or tips about this device would be great. I'm really excited about the Play and getting comfortable with Android. Thanks everybody!
kershner25 said:
Hey guys! I'm picking up an Xperia Play in a couple of days and was looking for some general advice about the phone. This will be my first Android device, I've been on WebOS/Garnet for my last two phones. I'm just a little overwhelmed with the options presented by the Play and Android in general. For instance, I'm not sure if I should root my phone or not - what are the advantages?
Any other general guides to Android/the Play would be wonderful if any such guides exist. I'm looking to deck this thing out with every emulator on the market as well as get the PSXperia hack up and running (I've downloaded the program, but can't figure out how to use it).
You can sense my overall noobishness in general, I'm sure. Any advice or tips about this device would be great. I'm really excited about the Play and getting comfortable with Android. Thanks everybody!
Click to expand...
Click to collapse
congratz im waiting for mine is the mail right now lol
rooting allows you to have full access to the file system sorta like a administrator
on a windows machine since out the box you cant edit files or remove bloatware without root you cant install certain programs from the market without root
also having root and unlocked bootloader allows you to flash a custom recovery image which will allow you to flash customs roms(a custom version of android dev by a user here on xda or anywhere in general)
yes i highly recommend but if you ever plan on returning the phone to verzion for example you will have to revert it back to stock
and for the program psxperia you need to install the latest version of java from java.com
and if your on a windows machine you double click the psxperiatool.JAR file
and it should run not sure on OSX
in the end you made a good choice on choosing android as mainstream as it became its still a powerful system way better IMO than ios or even webos
since android has so many developers theres gonna be an endless amount of programs
will post new finds myself etc
edokassiah said:
and unlocked bootloader allows you to flash a custom recovery image which will allow you to flash customs roms(a custom version of android dev by a user here on xda or anywhere in general)
Click to expand...
Click to collapse
You cannot flash the recovery image directly or you will mess up boot partition, you need to flash a kernel with embedded recovery built in
Thanks for the info. I'm confused about the locked/unlocked bootloaders. How do I know which one I'll have? And how "easy" of a process is rooting the phone if I don't plan to install any custom roms or anything?
Also, how does transferring .apk files from my PC to the device work?
kershner25 said:
Thanks for the info. I'm confused about the locked/unlocked bootloaders. How do I know which one I'll have? And how "easy" of a process is rooting the phone if I don't plan to install any custom roms or anything?
Also, how does transferring .apk files from my PC to the device work?
Click to expand...
Click to collapse
If you havent unlocked your bootloader yourself it is locked there are many risks and advantages to unlocking your bootloader, but if you dont intend to flash custom roms there really is no need, just like with root, if you dont know what it is, you probably wont need it
transfering .apk's from your pc is easy, just copy the .apk to your sd card, then use a file manager to find the .apk, tap on it and the installer will pop up , you need to tick unknown sources in settings though
http://forum.xda-developers.com/showthread.php?t=1176367
AndroHero said:
You cannot flash the recovery image directly or you will mess up boot partition, you need to flash a kernel with embedded recovery built in
Click to expand...
Click to collapse
hes asking about android in general not aiming specifically at the xperia play
If I root my phone, do I have to switch everything back in order to get updates? All I really want to root my phone for would be to remove bloatware/speed it up a bit, is there a better way than rooting?
There is plenty of tutorials here, I suggest that you read, read, and then......read some more
_terror_ said:
http://forum.xda-developers.com/showthread.php?t=1176367
Click to expand...
Click to collapse
Thanks so much for this link, it's seriously going to help me while rooting my phone. This might be a dumb question, but bear with me - better safe than a bricked phone. The guide to rooting in that link says that I need to flash my Play to the .184 Generic UK firmware...am I understanding it correctly that I need flash this firmware onto my American Verizon Play? I want to make sure nothing is going to get screwed up regionally, as I'm going to want to keep getting OTA updates and all that.
Just to share my own experiences since I'm new to the Xperia Play (previously had an Acer Liquid.. crappy hardware but great community of devs.. anyways..)
I'd recommend rooting your phone off the bat - the simple reason is rooting will involve wiping your phone's data, so if you already have a few months of use that means having to restore everything which is tiresome. First thing when my phone arrived was follow the rooting guide here - http://forum.xda-developers.com/showthread.php?t=1116090
After that however I wouldn't recommend messing around TOO much with custom firmwares and such etc.. get used to the phone as it is and figure out what you like, don't like. if your like me within a few weeks or months you'll want something new - this is when you might want to start looking at messing around with the phone - new home launchers or even a new ROM (if your phone can have it's boot loader unlocked, from what I understand mine can't). The games and Emulators should keep you busy as is
The only customizing I've done to my phone is rooting it with Gingerbreak and using the leaked Sony Launcher.
I realize this is a pretty nooby thing to do that annoys all the veterans, but I consider this to be a fairly crucial piece of information I need before I attempt to root my phone, so I'm just gonna go ahead and bump this thing before it gets lost in the shuffle.
In order to root with a locked bootloader on an American Verizon XPlay, I need to flash to the .184 generic UK firmware, then root, then OTA update, correct?
kershner25 said:
I realize this is a pretty nooby thing to do that annoys all the veterans, but I consider this to be a fairly crucial piece of information I need before I attempt to root my phone, so I'm just gonna go ahead and bump this thing before it gets lost in the shuffle.
In order to root with a locked bootloader on an American Verizon XPlay, I need to flash to the .184 generic UK firmware, then root, then OTA update, correct?
Click to expand...
Click to collapse
No. That method will not work on the r800x (verizon xplay) to root yours you will need to see [How-to] R800x Root
Dont worry about annoying people lol . Who cares what others think? Everyone has to start somewhere.
But it would be better with a stickied thread for new users to look @.
So now, instead of the 3 step process linked previously in this thread, I have to unlock the bootloader and do a whole bunch of other stuff? This method is like 100x more complicated. Is there no other way? I don't intend to install any custom roms, I strictly want to root solely for freezing bloatware.
No i dont think so. You would be better asking for help from other r800x owners in that thread.
The exploit gingerbreak uses on 2.3.2 was patched in 2.3.3 (worldwide) and was also patched by verizon before they released the handset on 2.3.2. Up untill the bootloader was unlocked on the r800x rooting was not possible.
Ask in that thread and you should recieve the help/info you are after.
hiya mate right ive rooted and put on custom recovery but now its screwed up my cam , wifi , and the market so be warned im trying to fix this problem as we speak
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
im new to this to really but having a play with no cam and no wifi and no market. the market is there but cant dwnload nothing is taking the piss can anyone help me please
Mozza2k11 said:
But it would be better with a stickied thread for new users to look @.
Click to expand...
Click to collapse
There is one already stickied in the Q&A section.That it has gone practically unnoticed counters this statement.
kershner25 said:
Thanks so much for this link, it's seriously going to help me while rooting my phone. This might be a dumb question, but bear with me - better safe than a bricked phone. The guide to rooting in that link says that I need to flash my Play to the .184 Generic UK firmware...am I understanding it correctly that I need flash this firmware onto my American Verizon Play? I want to make sure nothing is going to get screwed up regionally, as I'm going to want to keep getting OTA updates and all that.
Click to expand...
Click to collapse
Their is not such thing as a bricked phone
always is a way to fix it and usually its as simple as flashing a FTF
or whatever stock rom your device uses takes like 5 minutes tops lol
and logsemans guides will tell you anything you need to know
just use them for refrence
Xperia Play Super Compilation (Q&A Sticky)
and if you head down the path of rooting and stuff
messing with files
you wont be able to get ota updates lol.
it will "brick you"
I recentally made a quick video with tips for android users/beginners if you want to watch it. Thought it would help people. http://youtu.be/Pd5DerUoEcY
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)
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 !
Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.
Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.
it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.
Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.
_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.
_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.
redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.
I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?
I should mention that I'm working on a Windows 10 computer.
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.