Hi,
I purchased my wife a google nexus 7 last christmas and it has android 4.4.2 on it.
Wifi version only
It is 100% unmolested in anyway. She simply uses it for web surfing
I purchased her a new 10.1" tablet that will be here shortly so I will take the nexus 7 from her LOL.
To preface the rest of this post, my phone is a samsung galaxy s3, probably close to 2 years old, and am quite famaliar with rooting and installing custom roms, etc all with help of xda of course.
Once my wife gets her new tablet, I would like to root the nexus 7 and install a clean, simple, basic new rom that is de-oxed and rooted. I'm a pretty basic user and like to keep a clean minimal os, etc.
#1 The nexus 7 shows that there is a system update, I assume it's an os update but she never bothered to install it? Should I before doing anything else? Will this have an impact on rooting and installing newer roms?
#2 I assume the wug's toolkit is what I should to root, etc
#3 What is latest version that I can install that meet my needs for a basic, clean, rooted and de-oxed android version. I don't need anything fancy. Just quick and clean and maybe something that aids with battery life? I assume custom recovery is similar to the phones and that one can still use titanium free version to uninstall unwanted programs.
#4 Since I never used her tablet, is flash an issue these days with android and tablets?
I will use the nexus 7 for basic web surfacing and things of that nature. I would love to eventually install ubuntu touch as I only use linux on my home laptops but that is a convo for another day.
Any suggestions and comments are appreciated.
If there is something you need to ask to give me some suggestions, please do ask.
Thanks
1.- Yes, it's a system update. It's a Nexus so installing it won't have any effect on your ability to flash a custom ROM in the future.
2.- NO! Never, never, NEVER use toolkits to do anything, ESPECIALLY on a Nexus device. More problems are caused by toolkits than any other reason, and relying solely on toolkits will hinder your ability to fix anything should something go wrong, simply because you just won't know how to fix anything. Nexus devices are the absolute easiest devices to root, and are the perfect devices to use to familiarize yourself with ADB, fastboot, and just the basic ins and outs of that side of Android. You will want to use fastboot to unlock your bootloader, and install a custom recovery. From there, rooting is as simple as flashing SU, and you will likely be prompted to do so after flashing recovery. The whole process only takes a few minutes and will provide an invaluable learning experience. Read the stickies, that's where you will find the guide and the bulk of the information you'll need.
edit- this thread should get you started- http://forum.xda-developers.com/showthread.php?t=2381698
3.-Read the OPs of all the ROM threads in development and flash whatever you think has the features you are looking for. The functionality of custom recoveries are near identical across devices, just make sure you flash one that is specific for your device. You will find the threads for recovery in the Dev section as well, possibly in original development. Yes, you can still use Titanium.
4.- No issues with flashing, as long as you flash the proper files for your device. Nexus devices are VERY difficult to brick, so don't be afraid to get your feet wet.
I hope this helps, and if you have any more questions, don't hesitate to ask. Happy flashing!
Edit: and just an FYI, Ubuntu Touch is absolutely horrible and isn't even close to being a viable mobile OS. You can use MultiROM to install and dual boot it so you can try it out very easily but trust me, you won't like it one bit.
Thanks for the info, anything I need to be aware of before I start having fun once I take hold of the tablet. I get the small one she gets the larger one, hahahaha. Happy wife happy life.
I keeping reading about the boatloader needing to be a certain version before going to the newest os? No?
And I will stay away from touch, since I am a purely linux guy for anything computer or laptop thought it would be worth asking.
Also, what's the deal with odin and tablets. I use it all the time for my phone.
kero4 said:
Thanks for the info, anything I need to be aware of before I start having fun once I take hold of the tablet. I get the small one she gets the larger one, hahahaha. Happy wife happy life.
I keeping reading about the boatloader needing to be a certain version before going to the newest os? No?
And I will stay away from touch, since I am a purely linux guy for anything computer or laptop thought it would be worth asking.
Also, what's the deal with odin and tablets. I use it all the time for my phone.
Click to expand...
Click to collapse
The only caveat I can think of is to make sure you unlock your bootloader BEFORE you set up your device, as the unlocking process wipes everything.
I'd much rather have to deal with a smaller screen than an unhappy wife, you're making the right decision . And actually, I personally prefer smaller tablets as they are easier to manage and are better for gaming. With the exception of my Surface Pro 3, all my tablets are smaller sized. I have the 2013 Nexus 7, the iPad Mini Retina, and a Dell Venue 8 Pro which is an awesome 8" x86 Windows tablet that runs full Windows, not the dumb RT version.
I'm not the right guy to ask about the bootloader. I don't like Lollipop so all my Android devices are staying on KitKat. I haven't flashed any ROMs on the N7 in ages so I haven't done any research on bootloader compatibility. If you have a link to where you read about it, post it and I'll look into it for you.
Trust me, Ubuntu Touch is not worth your time. I flashed it on both my N5 and N7 just to mess around with it and promptly deleted it. It isn't worth the space it takes up on your device. It's that bad. But if you want to see for yourself, just install MultiROM, it has a built-in option to install Ubuntu Touch as a secondary ROM. You should install MultiROM anyway, as it gives you a painless method for trying out new ROMs without losing your current daily driver setup.
Odin is specifically for Samsung devices so it doesn't apply here. Familiarize yourself with ADB and fastboot, as that's how you'll be doing a lot of your mods.
When you say wipes the device, do you mean installed apps and date but nothing OS related right.
Since I don't do anything major with it (once I get it) and my wife didn't either I don't think wiping is an issue.
kero4 said:
When you say wipes the device, do you mean installed apps and date but nothing OS related right.
Since I don't do anything major with it (once I get it) and my wife didn't either I don't think wiping is an issue.
Click to expand...
Click to collapse
It just wipes all your user data, the OS is still there. It's basically a factory reset.
Related
Hey guy, sorry if this is going to be a bit of a noob question but please try and bear with me. In lieu of the recent nexus 5x which i found to be a huge disappointment I decided to pick myself up an lg g4. I'm not the biggest fan of the stock lg Rom and immediately looked for Cyanaogenmod.
I know that no stable build has yet been release for this phone yet and that i just need to have some patience, but I have some questions regardless. I'm wondering if there is a difference between root and an install of cyanogenmod. By this i mean that there are certain installer which will complete the process for you without you having to do any rooting yourself. If i understand correctly the phone is still being rooted but just by a program. My question is, is it only this latter feature that is not yet available for my phone. Like, if I were to root it myself would I then be able to install a cyanogenmod ROM. Or is it that there is not yet any compatible ROM for my device. If it is of any help I have the LG-H812 version of the phone.
Also, I recently saw a video on the XDA developers YouTube channel where it was discussed how TWRP is now available for the G4. what exactly does this mean and is it something that I would want.
Thank you very much for putting up with me.
Sounds like you need to do a bit more research before you do anything. I don't think TWRP is available for your model at the moment, which rules out custom roms/cyanogenmod. You just have to be patient and hope TWRP becomes available, then wait for a stable rom to come along. Or trade/sell your H812 for the international H815 (careful there are a few variants of the H815).
Nickvek9 said:
Hey guy, sorry if this is going to be a bit of a noob question but please try and bear with me. In lieu of the recent nexus 5x which i found to be a huge disappointment I decided to pick myself up an lg g4. I'm not the biggest fan of the stock lg Rom and immediately looked for Cyanaogenmod.
I know that no stable build has yet been release for this phone yet and that i just need to have some patience, but I have some questions regardless. I'm wondering if there is a difference between root and an install of cyanogenmod. By this i mean that there are certain installer which will complete the process for you without you having to do any rooting yourself. If i understand correctly the phone is still being rooted but just by a program. My question is, is it only this latter feature that is not yet available for my phone. Like, if I were to root it myself would I then be able to install a cyanogenmod ROM. Or is it that there is not yet any compatible ROM for my device. If it is of any help I have the LG-H812 version of the phone.
Also, I recently saw a video on the XDA developers YouTube channel where it was discussed how TWRP is now available for the G4. what exactly does this mean and is it something that I would want.
Thank you very much for putting up with me.
Click to expand...
Click to collapse
He's right man you Really should start hammering google especially with a more technically involved root with our g4s. No matter what anyone tells you TWRP or another custom recovery is the number one absolute most important thing to do with any root and immediately after you root before you make any modifications beyond normal app installs whatsoever. Custom recovery is what is going to save your ass in a bootloop or brick situation where you cannot get to the OS or even get a response from the device. As long as you have a backup in storage, you can use hardware key combos to enter TWRP and wipe the system and the problem and reflash the backup. Recovery is completely separate from the Rom that's how you can get around a total Rom disaster when nothing else works. The main reason there's no Roms for them yet is cuz only that one variant's bootloader can be unlocked which is required in most devices to flash a Rom or recovery and the reason that even with my capabilities I won't even bother rooting my expensive ass main important phone I'm still paying for every month lol I just fulfill my flash addiction on an l70 on a daily basis and daily I get outta bootloop and bricks thanks to TWRP... The g3 is perfect for playing with and I'm considering buying a used one and o I recommend the same until the g4 is fully cracked......also CM only comes pretty rooted because it does the same thing as normal just by flashing supersu which is a breeze with TWRP also
Through my ancient eyes comes the certainty of decay... LG G4 & L 70
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.
after much hell and high water i finally got my note 4 to root and unlock bootloader(as far as i know)so what do i need to do to prevent it from screwing up?i tried running debloater but it shows nothing......im on 5.1.1...is theyre a safe way to update or is it worth it?all i want is a stock rom rooted so i can use xposed to use stock wifi hotspot
dcjeeps said:
after much hell and high water i finally got my note 4 to root and unlock bootloader(as far as i know)so what do i need to do to prevent it from screwing up?i tried running debloater but it shows nothing......im on 5.1.1...is theyre a safe way to update or is it worth it?all i want is a stock rom rooted so i can use xposed to use stock wifi hotspot
Click to expand...
Click to collapse
hey, would you be able to help me with rooting the note 4 verizon? it's on 6.0.1 please
theyre are plenty og guides that can explain it way better than ican.....its a real pain in the a## to do
dcjeeps said:
after much hell and high water i finally got my note 4 to root and unlock bootloader(as far as i know)so what do i need to do to prevent it from screwing up?i tried running debloater but it shows nothing......im on 5.1.1...is theyre a safe way to update or is it worth it?all i want is a stock rom rooted so i can use xposed to use stock wifi hotspot
Click to expand...
Click to collapse
First and foremost, make a TWRP backup! That way if you run into any complications, you have a solid fall back to start fresh; I try and make a backup at least once a week, in the event that something were to go wrong I don't lose too much information.
2) Never take an OTA (Over The Air) update, it'll reset your bootloader and you'll have to re-root your Note (I may be wrong, but I'm pretty sure that's what will happen from all I have read).
3) Check out the Verizon Note 4 Development page (http://forum.xda-developers.com/note-4-verizon/development) and take a look at the ROM's they have to offer. Any CyanogenMod ROM is going to be a custom ROM, so you'll probably want to look for ones built off the stock ROM from the Note 4 (Like JasmineROM). The main advantages of a custom ROM versus a modified stock ROM are the abilities to customize pretty much anything, and allows you to have a more customizable environment. The main downside, in my opinion, is the loss of the stock Samsung apps like the use of your S-Pen, Camera app, etc..
4) Do plenty of research before deciding on a ROM; I've found it particularly helpful to not only read the main post itself and see if the author has updated it recently, but to also jump to the last few pages to see if anyone is experiencing issues recently.
I'm not a developer or anything, and just like you it took me a good long while to finally root my Note. Just try and read as many articles as you can to make understanding some of the terms easier on yourself (like AOSP, Deodex, nandroid, and so on), and watch videos on YouTube! Best of luck.
Sent from my SM-N910V using XDA-Developers mobile app
bertmag said:
First and foremost, make a TWRP backup! That way if you run into any complications, you have a solid fall back to start fresh; I try and make a backup at least once a week, in the event that something were to go wrong I don't lose too much information.
2) Never take an OTA (Over The Air) update, it'll reset your bootloader and you'll have to re-root your Note (I may be wrong, but I'm pretty sure that's what will happen from all I have read).
3) Check out the Verizon Note 4 Development page (http://forum.xda-developers.com/note-4-verizon/development) and take a look at the ROM's they have to offer. Any CyanogenMod ROM is going to be a custom ROM, so you'll probably want to look for ones built off the stock ROM from the Note 4 (Like JasmineROM). The main advantages of a custom ROM versus a modified stock ROM are the abilities to customize pretty much anything, and allows you to have a more customizable environment. The main downside, in my opinion, is the loss of the stock Samsung apps like the use of your S-Pen, Camera app, etc..
4) Do plenty of research before deciding on a ROM; I've found it particularly helpful to not only read the main post itself and see if the author has updated it recently, but to also jump to the last few pages to see if anyone is experiencing issues recently.
I'm not a developer or anything, and just like you it took me a good long while to finally root my Note. Just try and read as many articles as you can to make understanding some of the terms easier on yourself (like AOSP, Deodex, nandroid, and so on), and watch videos on YouTube! Best of luck.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
So which ROM are you on? I'm currently on
bertmag said:
First and foremost, make a TWRP backup! That way if you run into any complications, you have a solid fall back to start fresh; I try and make a backup at least once a week, in the event that something were to go wrong I don't lose too much information.
2) Never take an OTA (Over The Air) update, it'll reset your bootloader and you'll have to re-root your Note (I may be wrong, but I'm pretty sure that's what will happen from all I have read).
3) Check out the Verizon Note 4 Development page (http://forum.xda-developers.com/note-4-verizon/development) and take a look at the ROM's they have to offer. Any CyanogenMod ROM is going to be a custom ROM, so you'll probably want to look for ones built off the stock ROM from the Note 4 (Like JasmineROM). The main advantages of a custom ROM versus a modified stock ROM are the abilities to customize pretty much anything, and allows you to have a more customizable environment. The main downside, in my opinion, is the loss of the stock Samsung apps like the use of your S-Pen, Camera app, etc..
4) Do plenty of research before deciding on a ROM; I've found it particularly helpful to not only read the main post itself and see if the author has updated it recently, but to also jump to the last few pages to see if anyone is experiencing issues recently.
I'm not a developer or anything, and just like you it took me a good long while to finally root my Note. Just try and read as many articles as you can to make understanding some of the terms easier on yourself (like AOSP, Deodex, nandroid, and so on), and watch videos on YouTube! Best of luck.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Great advice,
So which ROM are you on? I'm currently on 5.0 1 I want to stick with a modified stock and want to upgrade (if there is something better). I'm terrified of losing root and not being able to get root again with all of the kingo and king root issues I've been Reading about.
I do have twrp and a backup.
I will check out the dev link you posted.
Sent from my SM-N910V using Tapatalk
Droidatar said:
So which ROM are you on? I'm currently on
Great advice,
So which ROM are you on? I'm currently on 5.0 1 I want to stick with a modified stock and want to upgrade (if there is something better). I'm terrified of losing root and not being able to get root again with all of the kingo and king root issues I've been Reading about.
I do have twrp and a backup.
I will check out the dev link you posted.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
That was the biggest fear that I too had after rooting and unlocking my boot loader. Right now I'm running CyanogenMod 13, and I have to say I love it. Personally, the stock Touchwiz ROM is just too cutesy.
I'd suggest before going into flashing a new ROM, reboot into TWRP and familiarize yourself with the layout and functions (if you haven't had the chance yet). Then, as I suggested in my post above, just watch as many videos and read as many forum, blog, and article posts as you can.
As long as you follow the guide for the ROM you're flashing carefully, there isn't too much that can go wrong. It is hella nerve racking the first time you flash phone (or at least it was for me), but the first time you boot into your new custom ROM is a pretty awesome one.
P.S.,
If any of that didn't make any sense, I apologize. I've been at work since 6 this morning, and wrote it in snippets when I could since this afternoon. Best of luck!
Sent from my SM-N910V using XDA-Developers mobile app
bertmag said:
That was the biggest fear that I too had after rooting and unlocking my boot loader. Right now I'm running CyanogenMod 13, and I have to say I love it. Personally, the stock Touchwiz ROM is just too cutesy.
I'd suggest before going into flashing a new ROM, reboot into TWRP and familiarize yourself with the layout and functions (if you haven't had the chance yet). Then, as I suggested in my post above, just watch as many videos and read as many forum, blog, and article posts as you can.
As long as you follow the guide for the ROM you're flashing carefully, there isn't too much that can go wrong. It is hella nerve racking the first time you flash phone (or at least it was for me), but the first time you boot into your new custom ROM is a pretty awesome one.
P.S.,
If any of that didn't make any sense, I apologize. I've been at work since 6 this morning, and wrote it in snippets when I could since this afternoon. Best of luck!
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry its been a month and I just saw this post on Tapatalk.
I have cyanogen on my nook. I want to keep stock so I can use the pen. And other programs. I use Nova launcher to bypass touch wiz.
Sent from my SM-N910V using Tapatalk
Hello there,
I would like a more secure and private OS on my phone. Copperhead OS is interesting but I don't have the money to buy a device from them nor the know how to use the source. So my question, what is a good alternative. It seems like there are a lot of options here on XDA. It's my first time here and I'm not the most technical when it comes to software. I was able to switch all my home computing to linux/tails but working with my phone seems much harder. Any advice would be a huge help at this point.
What I think I know:
-I need to unlock my phone, and I have a Verizon Pixel XL. I found this article, (turns out new people can't post links but it is the page with the depixel8 tool), that I think will help me to unlock. Step one of this article mentions fastboot and adb which I think I get from Android SDK. So I'm pretty sure I first download the SDK (gonna find a guide to be safe) and then I do these steps through the terminal.
-Back up everything! I've removed all my pictures, I don't have a ton of contacts but I saved those else where too. Everything at this point can be lost, so when we say "back up everything" is there something I am missing? In my Desktop experience this also meant back up my old windows install, is this the case here? If so how do I do that?
-When the phone is unlocked, I then load a ROM on to it and select it in bootloader?
In summation, very lost, slightly confused, willing to learn! I'm just looking for an OS where I can use open source software, including the OS. Call me paranoid (fixes tin foil hat) but I'd rather try to keep my life private if even a little. Thank you for any help you can provide me in taking my first steps into something new.
If you are already on latest Verizon there is no way to unlock.
So no way to flash any custom roms.
But if security is what you want an unlock bootloader is just the other way. Less security.
Darn, I am on the latest version. I'm not able to unlock using the depixel8 tool? If that's the case I may just pick up a nexus and try to use Copperhead.
Lost And Confused said:
Darn, I am on the latest version. I'm not able to unlock using the depixel8 tool? If that's the case I may just pick up a nexus and try to use Copperhead.
Click to expand...
Click to collapse
If you're past 7.1 then sadly depixel8 won't work
Guess that's a done deal then. Instead of making a new thread I guess I'll just ask here. The way I understand it, Android is open source, but that doesn't mean the OS on my phone is open source. Seeing that the community here works with Android so much, are there any major privacy concerns running the latest version. As an example, Windows, especially Windows 10 is a privacy nightmare. I can't imagine Android is that bad, but what can you tell me?