Hi all,
I've finally got a Desire heading my way from Orange. I'll be wanting to purge the Orange branding for a variety of reasons, but I'm unsure of the most up to date, clean/stock ROM to go for.
I'm new to the Android platform, so rather than try out a custom/tweaked rom that requires rooting, I thought I'd just use the goldcard method to flash a clean rom across (May try rooting/customs later).
I've been reading through some of the threads and have a fair idea of what to expect, my questions to you fine people:
What is the most up to date 'stock' htc rom going? - I was going to try the one listed in the T-mobile thread, or 'RUU_Bravo_HTC_Europe_1.15.405.3'.
Presumably I'll still receive over the air updates for such a stock rom?
If/When I root, does all the phone data require backing up? How many of your settings persist?
Thanks for any replies.
Generic ROM and MD5SUM:
d51566508430cd7edec7c9d4b51b6fd1 RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
I think it is always better to start at the lowest version possible and then let the phone update by itself. This will help to ensure all original updates directly from the factory.
Cheers, I think that's the one I've gotten hold of.
question from a new guy
where can i download this rom from? as i'd like to install this stock rom on my desire too i've looked on the forum but can't seem to spot it anywhere.
thanks for any help in advance
Tsjoklat said:
Generic ROM and MD5SUM:
d51566508430cd7edec7c9d4b51b6fd1 RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
I think it is always better to start at the lowest version possible and then let the phone update by itself. This will help to ensure all original updates directly from the factory.
Click to expand...
Click to collapse
Doesn't that mean it uses up more memory?
as you'll have the old files overlaid by the newer ones
I might be wrong but if a factory reset returns it to a pre-updated state then it's
not using the same area that the rom flash does
personally I'm holding off till Froyo is available before I buy a Desire
Gary
JayceAndTheNews - Let me know how you get on would you? any chance of hooking me up with what ever methods you've used? I've got an orange branded Desire on T-mobile and want rid of all the Orange bollox but don't feel the need to root yet.
JAmes.
understanding (although possibly incorrect) is that I'm overwriting the current Orangey rom with a cleaner one. So although the factory reset may remain somewhere, the actual os I'm running will be a similar size if not smaller than what I've got atm.
Sounds like I've got some more reading to do =D
jamfitz86 - I'll let you know what I end up doing and if it works, just got my shiny black desire yesterday, I intend to clean out the Orange garb on a weekend.
Cheers all.
Update for jamfitz86 / anyone else who may find it useful (although most of this is repeated in other threads).
Effectively followed this guide "http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/" to the letter. Encountered no problems/difficulties whatsoever.
Formatted the goldcard afterwards to use as my SD card until I get a larger one on the go.
Phone up and running, installed back missing apps etc. Performance seems about the same, potentially a little better certainly no worse. Removing all the
Orange crap makes things much more enjoyable overall, I'd definitely do it again given the choice.
Good morning
I have:
LG G Pad 8.3 with LG's custom interface OS
Android version 4.4.2
Kernel version 3.4.0
Build number KOT49I.V50020b
Software version V50020b
Here is an image of the software information:
http://s30.postimg.org/taiyvu2k1/201...8_14_31_41.png
I have already:
The LG drivers installed and updated -
Rooted the G Pad with towelroot's tr.apk (many thanks to the guy who made that method!)
Root checker and SuperSU installed and verifying the device is rooted
Google USB drivers (after rooting, the device refused to be recognized through the USB - installing the Google USB drivers seemed to fix that, although occasionally it dissappears again and I have to unplug/replug the USB cable)
Google ADT Bundle (adt-bundle-windows-x86_64-20140624 - although to be honest, my knowledge of using this program is limited)
Flashify (and Rashr - uncertain which is best to use, although both look good)
My goal:
Install TWRP
Use TWRP to install Cyanogen Mod
I'm using Windows 7 64-bit. My G Pad has a micro SD card, which it can also write to (thanks to the G Pad being rooted). I'm a competent Windows and Android user, but by no means a hacker. If I want to upgrade or fix something, I read read read and try try try. But installing a new OS on my tablet is a new experience and I don't want to turn my tablet into a permanent brick! I have done all my homework, and think I know all the concepts, and generally the procedure. Now I just need the specific files and procedure for my G Pad.
My questions are:
1) Which TWRP recovery/boot image should I use to flash my device? (I tried a version, and briefly turned my G Pad into a brick! Fortunately I tried some power+volume combinations that I discovered, and that seemed to return to the original system.) My best options I have found seem to be:
http://forum.xda-developers.com/show....php?t=2551499
plus using step 3 here (a loki-exploitable ABOOT and TWRP)
http://forum.xda-developers.com/show....php?t=2698267
...or only:
http://teamw.in/project/twrp2/213
2) Do I need to use an aboot/loki file first? (Apparently 4.4.2 doesn't have a loki exploit? I'm a little unclear about this tbh.)
3) Can/should I use ROM Toolbox or ROM Manager?
4) If you try to flash a TWRP, and it doesn't work, does/can the device just return to the standard OS? (This is what seems to have happened with my G Pad.)
5) Should I wait until the community has more experience TWRP-ing and modding the G Pad Kit Kat 4.4.2, V50020b device? (There seem to be a lot of posts with people installing TWRP and installing another OS.)
Many thanks in advance. And while I am decent with computers and technology in general, I humbly ask to speak/explain it to me including steps you probably already know are obvious(!) - I don't want to miss anything, and it is probably not obvious for me, as this is more or less my first time! If I can make this question clearer, or can provide better information, I will update this comment. Again, many thanks in advance!
Sorry - no questions in this forum?
Looking at a post by an admin, it looks like there shouldn't be any questions here. I've put this post in the troubleshooting Q&A forum section...
i have the same device firmware... I have root access, but cannot install TWRP!
Any ideas?
look at this instructions, they worked fine for me
http://forum.xda-developers.com/showpost.php?p=53612227&postcount=3
notice step 8 that states to disconnect the tablet
Thanks
don_ernesto said:
look at this instructions, they worked fine for me
http://forum.xda-developers.com/showpost.php?p=53612227&postcount=3
notice step 8 that states to disconnect the tablet
Click to expand...
Click to collapse
Thanks for the link and information. I'll look at that carefully later. I want to be very careful (and know as much about what I'm doing as possible first) when I do this.
hmm... I believe I have the same build and software version as yours. I could recall a thread in the forums to flash the TWRP for the Korean version of the ROM, which actually worked fine for me. I have a SEA region tablet. If you still have issues, ill have a look when I get home.
jarod004 said:
hmm... I believe I have the same build and software version as yours. I could recall a thread in the forums to flash the TWRP for the Korean version of the ROM, which actually worked fine for me. I have a SEA region tablet. If you still have issues, ill have a look when I get home.
Click to expand...
Click to collapse
Thank you very much, I'd appreciate the link, and any extra info you could give. I don't know if I'll have time to try it this weekend, but I'm collecting all the pages and info I can over the next few days, and I'm looking for a free time in my schedule to try this thing.
Now I have 20d : /
Apparently LG saw fit to update last night, and now I have 20d!
Does this change anything?
Cause I was all ready to try to load TWRP with 20b on my tablet. Now it's 20d and I don't know if that messes everything up.
Hello,
I've bought an HTC One M8 at ebay a few days ago.. the device was sold as a Google Edition one, although, after I bought it, I realized that it was an unlocked HTC One M8 with a Google Edition rom (description in english wasn't so complete as the german one ).. for me that wouldn't be a problem, although I would prefer to have the genuine firmware (I like the original HTC software)..therefore, I asked the user to change the firmware before sending the phone to me.
After receiving the phone, I've noticed that firmware version is "Android Revolution HD 8.1 by mike1986".. therefore,.. not the original rom from HTC.. besides this, there's also some "leftovers" of the google edition, as you can see in the image below (appears when I reboot the phone) .
The user told me that he has spent almost three hours to install that rom,.. and that he couldn't ger rid of the "Google" symbol whenever reboot the phone, as he had almost bricked the phone when he was trying.
What I would like to know is if there is the possibility to change the firmware to the original HTC firmware, exactly as if I was getting the phone from the store (with all the applications that comes with it) and that also allows me to benefit from HTC warranty?
If so, is there any step by step guide to safely do it?
I'm a novice in this area (never rooted or unrooted a phone).. and I just want to have the phone as if it was out of the box (do not need to have it unlocked to update roms or to delete any applications that comes with the phone, or something like that).
My HTC has a CID-HTC__102 (based on what I searched in the forum...it looks like an unlocked international version (German) device) and it has an IMEI SV 01 (I don't know if this info is needed, but I could not attach any more images, so I post this info here).
I will leave some info screen images as attachments so it becomes easier for you to help me.
Thank you in advance for your help.
Best regards,
SkElEtIkO
http://forum.xda-developers.com/showthread.php?t=2735235
you might not need to do all the steps, but this works 100%
confusion and more confusion in my head... :S
RossMacgill said:
http://forum.xda-developers.com/showthread.php?t=2735235
you might not need to do all the steps, but this works 100%
Click to expand...
Click to collapse
Hello Ross,
I've already read that post, however, for a noobie in this area, I believe that there's a lot of things that might not be so easy as they're for who flash firmware a lot of times.. for example.. "flash (...) ROM in TRWP"...I never flashed anything ..
I've roughly seached in the forum for "flash in TWRP"..and there's a lot of people with problems in flashing things with it (get stuck in some point)...
Besides this..EddyOS post mentions to use "odexed package provided by @Mike1986".. is that post only about applying that ROM or can I use another one? I already have a ROM by mike1986.. the one that I want to get rid off .. I want a completely original ROM as if the phone came from HTC... I was thinking on this..but even this one looks like was also provided by mike1986... (and probably has the same name that the one that I have).. isn't there any ROM by HTC without any modification???
I haven't got anything against ROMs made by mike or someone else.. I just want a manufacturer ROM which allows me to have full warranty and the functionalities that originally came with the phone. For example, with this firmware that I currently have, I cannot add my google account (says "cannot connect to google server") and I cannot see if there are new phone software updates (it keeps searching and searching)... and if I look into phone's software name.. it appears "Android Revolution HD 8.1 by mike1986"..well.. if I would take the phone to HTC under warranty.. they certainly wouldn't do anything with that software
Another thing, you told in your reply that I may not need to do all the steps.. Why not (?) and.. in that case, which steps shall I need to do?
My final question of this post...since the user that sold me the phone had already made a firmware update (google edition) before the current one, and now.. the phone has things from two firmware updates (the initial logo from google edition firmware, as you can see in the attached image, and the firmware from mike1986), don't you think, that it would be necessary to make another steps to clean all this mess?
Thank you in advance for your help.
Regards,
SkElEtIkO
skeletiko said:
Hello Ross,
I've already read that post, however, for a noobie in this area, I believe that there's a lot of things that might not be so easy as they're for who flash firmware a lot of times.. for example.. "flash (...) ROM in TRWP"...I never flashed anything ..
I've roughly seached in the forum for "flash in TWRP"..and there's a lot of people with problems in flashing things with it (get stuck in some point)...
Besides this..EddyOS post mentions to use "odexed package provided by @Mike1986".. is that post only about applying that ROM or can I use another one? I already have a ROM by mike1986.. the one that I want to get rid off .. I want a completely original ROM as if the phone came from HTC... I was thinking on this..but even this one looks like was also provided by mike1986... (and probably has the same name that the one that I have).. isn't there any ROM by HTC without any modification???
I haven't got anything against ROMs made by mike or someone else.. I just want a manufacturer ROM which allows me to have full warranty and the functionalities that originally came with the phone. For example, with this firmware that I currently have, I cannot add my google account (says "cannot connect to google server") and I cannot see if there are new phone software updates (it keeps searching and searching)... and if I look into phone's software name.. it appears "Android Revolution HD 8.1 by mike1986"..well.. if I would take the phone to HTC under warranty.. they certainly wouldn't do anything with that software
Another thing, you told in your reply that I may not need to do all the steps.. Why not (?) and.. in that case, which steps shall I need to do?
My final question of this post...since the user that sold me the phone had already made a firmware update (google edition) before the current one, and now.. the phone has things from two firmware updates (the initial logo from google edition firmware, as you can see in the attached image, and the firmware from mike1986), don't you think, that it would be necessary to make another steps to clean all this mess?
Thank you in advance for your help.
Regards,
SkElEtIkO
Click to expand...
Click to collapse
odexed package provided by @Mike19 and the system dump you linked to are the same stock, more than likely the very same file. You can use any rom, that is a stock dump and the correct version, but i would use mikes, or from the list of stock dumps thread on here.
Mike is a rom developer, he makes custom roms, but also has sources for his roms, which he then supplies for us to go back to stock.
with your google flash screen, i did read that if you flash 1.54.401.5 then reflash 1.54.401.10, it fixes that issue, not sure how true it is.
Please see solution in here
Thank you
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.