Phone info:
Virgin Mobile (Samsung S3)
SPH-L710
Android 4.1.2
BaseBand: L710VPAMG2
Build #: JZO54K.L710VPAMG2
Hardware: L710.14
Kernel: [email protected] #2 SMP PREEMPT Fri Jul 10 12:13:58 KST 2013
I was able to root and install CWM but it appears no ROM is compatible with this device. CM10 gave a build.prop error and failed to install. Slim ROM installed but never got past the kernel load.
Anyone able to install any ROM on this device? I dont even see it listed here:
http://samsung-updates.com/device/?id=SPH-L710
My wife and I just switched to Virgin Prepaid and I got the S3, my wife got the LG Optimus F3 4G LTE. Her phone is GSM (sim card), mine is CDMA (no sim). That seem odd to anyone? Same plan, same network, but different.
Found the issue
Per the build.prop
ro.product.device=d2vmu
Correct phone wrong product. Cant seem to find any d2vmu ROMs though - lol. At least I got root.
Same Here
Moped_Ryder said:
Phone info:
Virgin Mobile (Samsung S3)
SPH-L710
Android 4.1.2
BaseBand: L710VPAMG2
Build #: JZO54K.L710VPAMG2
Hardware: L710.14
Kernel: [email protected] #2 SMP PREEMPT Fri Jul 10 12:13:58 KST 2013
I was able to root and install CWM but it appears no ROM is compatible with this device. CM10 gave a build.prop error and failed to install. Slim ROM installed but never got past the kernel load.
Anyone able to install any ROM on this device? I dont even see it listed here:
http://samsung-updates.com/device/?id=SPH-L710
My wife and I just switched to Virgin Prepaid and I got the S3, my wife got the LG Optimus F3 4G LTE. Her phone is GSM (sim card), mine is CDMA (no sim). That seem odd to anyone? Same plan, same network, but different.
Click to expand...
Click to collapse
Ditto, my man, in so many ways.
My wife and I as well. Except we both got S3s. So, I'm not sure about the GSM/CDMA, though that does seem weird.
Your phone info is identical to mine, except my baseband is L710VPAMD7, and the date in my kernel is Jul 19. Otherwise identical.
What differing baseband and kernel numbers may be about, I'm not sure yet.
While I just came off of a relatively wonderful rooting experience, even in it's later years, with my ole' Evo 4G original, this phone makes me feel like a noob. That phone had a thriving root community behind it. This phone has a ghost town, and the S4 has been out for a while now.
And, even worse, I'm starting to realize our VM phones are a sort of mutant. At least, a form of unacknowledged outcast in the root world.
Your find in the build.prop confirms it. On just about every forum, if you inquire about our VM L710s, you get directed to their take on d2spr, because "it's exactly the same model." Even Cyanogenmod, even XDA, without a second thought.
But hardware alone does not make a working smartphone. Virgin Mobile clearly refers to their L710 as a separate branch of the S3 lineup. d2vmu. I kind of like it. But, you're right. Damned if I can find a ROM just for that.
It is also confirmed in a subtle clue in the link you posted, that seems to link so many other posts on the subject together. On the list of Samsung firmware, VPA equals ICS. VPB is JellyBean.
Our VM phones have ICS bootloaders. Jellybean can handle ICS bootloaders up until 4.1.2, but after 4.2 it needs JB bootloaders, and VM is in no rush on that.
I walked into this looking to root the thing, and maybe toss on CM 10.2, if only for the 4.3. But I had no idea of the strategic effectiveness of keeping your customers using old tech, while dropping new tech for the developers. Many devs jumped on the S4 and others, and now I'm trying to learn Android, to figure out why this crazy scheme didn't work for me, and help keep this nice little phone humming for a couple of years or so.
Prepaid rocks!
Our VM phones have ICS bootloaders. Jellybean can handle ICS bootloaders up until 4.1.2, but after 4.2 it needs JB bootloaders, and VM is in no rush on that.
Click to expand...
Click to collapse
Are you sure about that? The reason I ask is because our (mine) came factory stock with 4.1.2 which is JB (not ICS). I assumed that my phone (AMG2) thus came with JB bootloaders and not ICS. If you have flashed the Sprint JB bootloaders in the link you provided did it work? Because MD4 firmware is also 4.1.2 (like my AMG2) I felt that flashing Sprint 4.1.2 bootloaders over my VMU 4.1.2 bootloaders was unneeded.
The idea of flashing bootloaders never sat well with me.
You may be on to something though - can ICS bootloaders work with android up to 4.2.1 (JB)? Because Ive been able to flash numerous android 4.2.1 ROM but no higher (4.2.2 = nogo). At first the thought was it was hanging the kernel on bootsplash but the last experimental CM I think confirmed it more.
Sorry to blow up your thread. I responded like that, with so much behind it, because I'm in the same boat, and you sounded like you were asking the same questions I am. I imagine there are quite a few of us who took advantage of that great deal, and are trying to figure this out as well.
Moped_Ryder said:
Are you sure about that? The reason I ask is because our (mine) came factory stock with 4.1.2 which is JB (not ICS). I assumed that my phone (AMG2) thus came with JB bootloaders and not ICS. If you have flashed the Sprint JB bootloaders in the link you provided did it work? Because MD4 firmware is also 4.1.2 (like my AMG2) I felt that flashing Sprint 4.1.2 bootloaders over my VMU 4.1.2 bootloaders was unneeded.
The idea of flashing bootloaders never sat well with me.
Click to expand...
Click to collapse
Me neither!
Drop in on that link, other gus' tutorial, and read the Overview. I'm going by that, because it crystallized quite a few bare hints and known issues I'd found elsewhere, earlier in the search, into a coherent explanation that fits the device's behavior. As he explains, "The Sprint MD4 firmware uses a Jellybean bootloader, while Virgin Mobile’s firmware uses a bootloader for ICS. If you were eager to install CM10.1 and attempted to do so, the “assert failed” errors you saw were because all versions of CM after 10.1 require a Jellybean bootloader - and, like I said, our phones have an ICS bootloader. Thus, we need Sprint’s Jellybean bootloader to install CM10.1."
While some of the info may have become dated since July, and it's a little light on sources, the premise fits most of the Please Help! complaints in Sprint/VM ROM forums. The common thread I see running through most every VM forum is the inability of anyone with our brand and model to upgrade past a certain point. And system upgrades from VM seem to be deliberately keeping us behind the times, until they're good and ready to allow us their version of newer Android, whatever that may be. But, isn't that why we root and flash in the first place?
I'm not entirely sure, I'm no Developer. An advanced beginner on other phones, maybe, but a Samsung rookie, for sure. I've had this phone about a week, and I've wandered into forums blindly, picking up hints along the way, much the same way I did with the OG. Only then, there was a wealth of learning available, and it was pretty easy to sift through the good, bad, and expired, until I had a working body of knowledge that let me use the device safely.
In this case, most of what's to be had stems from d2spr. Truly good and current information on the VM L710 is rare, and scattered. (What I wouldn't give for a current comprehensive list of VM bootloaders, or VM Stock ROM changelogs, or... Something.)
Moped_Ryder said:
You may be on to something though - can ICS bootloaders work with android up to 4.2.1 (JB)? Because Ive been able to flash numerous android 4.2.1 ROM but no higher (4.2.2 = nogo). At first the thought was it was hanging the kernel on bootsplash but the last experimental CM I think confirmed it more.
Click to expand...
Click to collapse
I think you got it right, the line seems to be drawn at 4.2.1, or earlier builds of CM 10.1. While it looks like Google built in some overlap, Android past that point requires calls that only a JB bootloader can answer. The consistent explanation by devs or long time modders who visit these few forums, is that the information provided when the flash fails all point to 'ro.bootloader', and lists a set of four bootloader/modem/firmwares that it's looking for, for example L710VPBMD4, all VPB. (MD4 may be dated by now, but it was the new one back in July, and its still "newer" android-wise than L710VPAMD7. The crazy part of their method is to go into the d2spr MD4 update package and replace Sprint's modem with punkmaxx's extracted VM modem. DIY awesome.)
That illustrates part of the deeper problem right there. The VM SGS3 has only been around a few months, and it usually takes some time for experienced devs to gravitate to a device. But, that's considering new devices. The S3 is over a year old, it's replacement is already out, and while other models like the AT&T, Verizon, and T-Mobile versions, and the I9300, have gotten decent attention and support from the experienced mod community over the last year, Sprint's version has gotten a bit less. And our VM has barely registered, (here's Cyanogenmod's semi-official position on the VM L710), let alone been given it's own d2vmu page on any site. (Your original post was the first mention I found of that online.)
And, like the few folks providing us options, like other gus, and punkmaxx, and you, I hope I can help change that.
This is a good device, if we can get past Virgin Mobile, and make it our own.
---------- Post added at 05:41 PM ---------- Previous post was at 05:26 PM ----------
Crazy thing happened... In trying to replicate the failed install, to provide you with the ro. bootloader info, the install succeeded. It seems the modified bootloader worked, but only after a full reboot back into system, which was still my VM Stock (rooted). Once back into recovery (TWRP), it worked. Of course, I was trying CM 10.2, and it got caught in a bootloop, and I had to do a full restore into Stock, but it made it that far.
I remember your description of pretty much the same thing. Is that what happened, even without the bootloader install?
(I may try again with 10.1. I just miss Privacy Guard.)
rexograff said:
Sorry to blow up your thread. I responded like that, with so much behind it, because I'm in the same boat, and you sounded like you were asking the same questions I am. I imagine there are quite a few of us who took advantage of that great deal, and are trying to figure this out as well.
Me neither!
Drop in on that link, other gus' tutorial, and read the Overview. I'm going by that, because it crystallized quite a few bare hints and known issues I'd found elsewhere, earlier in the search, into a coherent explanation that fits the device's behavior. As he explains, "The Sprint MD4 firmware uses a Jellybean bootloader, while Virgin Mobile’s firmware uses a bootloader for ICS. If you were eager to install CM10.1 and attempted to do so, the “assert failed” errors you saw were because all versions of CM after 10.1 require a Jellybean bootloader - and, like I said, our phones have an ICS bootloader. Thus, we need Sprint’s Jellybean bootloader to install CM10.1."
While some of the info may have become dated since July, and it's a little light on sources, the premise fits most of the Please Help! complaints in Sprint/VM ROM forums. The common thread I see running through most every VM forum is the inability of anyone with our brand and model to upgrade past a certain point. And system upgrades from VM seem to be deliberately keeping us behind the times, until they're good and ready to allow us their version of newer Android, whatever that may be. But, isn't that why we root and flash in the first place?
I'm not entirely sure, I'm no Developer. An advanced beginner on other phones, maybe, but a Samsung rookie, for sure. I've had this phone about a week, and I've wandered into forums blindly, picking up hints along the way, much the same way I did with the OG. Only then, there was a wealth of learning available, and it was pretty easy to sift through the good, bad, and expired, until I had a working body of knowledge that let me use the device safely.
In this case, most of what's to be had stems from d2spr. Truly good and current information on the VM L710 is rare, and scattered. (What I wouldn't give for a current comprehensive list of VM bootloaders, or VM Stock ROM changelogs, or... Something.)
I think you got it right, the line seems to be drawn at 4.2.1, or earlier builds of CM 10.1. While it looks like Google built in some overlap, Android past that point requires calls that only a JB bootloader can answer. The consistent explanation by devs or long time modders who visit these few forums, is that the information provided when the flash fails all point to 'ro.bootloader', and lists a set of four bootloader/modem/firmwares that it's looking for, for example L710VPBMD4, all VPB. (MD4 may be dated by now, but it was the new one back in July, and its still "newer" android-wise than L710VPAMD7. The crazy part of their method is to go into the d2spr MD4 update package and replace Sprint's modem with punkmaxx's extracted VM modem. DIY awesome.)
That illustrates part of the deeper problem right there. The VM SGS3 has only been around a few months, and it usually takes some time for experienced devs to gravitate to a device. But, that's considering new devices. The S3 is over a year old, it's replacement is already out, and while other models like the AT&T, Verizon, and T-Mobile versions, and the I9300, have gotten decent attention and support from the experienced mod community over the last year, Sprint's version has gotten a bit less. And our VM has barely registered, (here's Cyanogenmod's semi-official position on the VM L710), let alone been given it's own d2vmu page on any site. (Your original post was the first mention I found of that online.)
And, like the few folks providing us options, like other gus, and punkmaxx, and you, I hope I can help change that.
This is a good device, if we can get past Virgin Mobile, and make it our own.
---------- Post added at 05:41 PM ---------- Previous post was at 05:26 PM ----------
Crazy thing happened... In trying to replicate the failed install, to provide you with the ro. bootloader info, the install succeeded. It seems the modified bootloader worked, but only after a full reboot back into system, which was still my VM Stock (rooted). Once back into recovery (TWRP), it worked. Of course, I was trying CM 10.2, and it got caught in a bootloop, and I had to do a full restore into Stock, but it made it that far.
I remember your description of pretty much the same thing. Is that what happened, even without the bootloader install?
(I may try again with 10.1. I just miss Privacy Guard.)
Click to expand...
Click to collapse
Ive tried a few things with no success yet. I still havent flashed the MD4 Sprint bootloaders though - I just hate messing with bootloaders.
For instance tried a CM 10.2 I changed the following:
cm-10.2-20130902-EXPERIMENTAL-d2spr-fixboothang\META-INF\com\android\metadata
I added the MG2 line at the end.
Code:
post-build=samsung/d2spr/d2spr:4.1.2/JZO54K/L710VPBMD4:user/release-keys
post-timestamp=1378143490
pre-bootloader=L710VPBLJ7|L710VPBMA6|L710VPBMB1|L710VPBMD4|L710VPAMD7|[SIZE="4"][B]L710VPAMG2[/B][/SIZE]
[B]pre-device=d2vmu[/B]\
cm-10.2-20130902-EXPERIMENTAL-d2spr-fixboothang\META-INF\com\google\android\updater-script
I added the D2VMU and MG2 to assert:
Code:
assert(getprop("ro.product.device") == "d2spr" || getprop("ro.build.product") == "d2spr" ||
[SIZE="4"][B]getprop("ro.product.device") == "d2vmu" || getprop("ro.build.product") == "d2vmu");[/B][/SIZE]
assert(getprop("ro.bootloader") == "L710VPBLJ7" ||
getprop("ro.bootloader") == "L710VPBMA6" ||
getprop("ro.bootloader") == "L710VPBMB1" ||
getprop("ro.bootloader") == "L710VPBMD4" ||
getprop("ro.bootloader") ==[SIZE="4"][B] "L710VPAMG2"[/B][/SIZE] ||
getprop("ro.bootloader") == "L710VPAMD7");
Still nogo
Related
Hello XDA!
I recently traded my iPhone 4S about 2.5 weeks ago. I am in love with the Samsung Galaxy SIII. I love the sleek style and touchwiz is much more active and more "fun" than iOS. I love the google integration and all the cool features out of the box.
Since I'm new to android I'm really overwhelmed in the amount of information available to "modify or root."
I was a constant jailbreaker and had over 50-100 tweaks/jailbroken apps. I would like to get the same functionality on the SIII.
I wasn't afraid of jailbreaking and it was a one-button press jailbreak.
With android there are so many different versions and terminology to jailbreak and so many instructions and updates and in general just a lot of stuff.
About my new phone:
- Samsung Galaxy SIII
- AT&T
- 8GB miroSD card
- Model: SAMSUNG-SGH-1747
- Android Version: 4.0.4
- Baseband Version: 1747UCLH9
- Kernel version: (IS THIS CONFIDENTIAL INFORMATION?)
- I have installed a couple of root apps that I didn't know where root apps and so they don't work obviously.
- Ones I installed: Lucky Patcher, Titanium Backup
- It's not rooted yet I haven't modified it at all besides themes and settings
The reason why I'm posting:
- Can anyone please tell me EXACTLY which updated guides I need to follow for my specific device?
- How can I backup my device? I'd like to keep all the apps (and app data), contacts, everything if possible.
- I read as much as possible but I'm still not sure which guide to follow and which steps I need to take as some are dated and not recent. I'm scared I'll mess up my phone what are the chances of messing up my IMEI, bricking, bad stuff happening.
- Anything else I should know?
- What are some popular ROMS I can install on my phone that are supported (preferrably with JB)?
- Can I always go back to my original settings and apps like a restore but with a backup?
- Once I root what BLOATWARE can I UNINSTALL on my AT&T SIII? How do I do this as well?
Thank you for your patience, I am definitely going to stick with Android (stock iOS sucks balls and android is so much more aesthetically pleasing) I just want to make sure I'm doing everything right and that there is a proper way to do this.
Bronos said:
Hello XDA!
I recently traded my iPhone 4S about 2.5 weeks ago. I am in love with the Samsung Galaxy SIII. I love the sleek style and touchwiz is much more active and more "fun" than iOS. I love the google integration and all the cool features out of the box.
Since I'm new to android I'm really overwhelmed in the amount of information available to "modify or root."
I was a constant jailbreaker and had over 50-100 tweaks/jailbroken apps. I would like to get the same functionality on the SIII.
I wasn't afraid of jailbreaking and it was a one-button press jailbreak.
With android there are so many different versions and terminology to jailbreak and so many instructions and updates and in general just a lot of stuff.
About my new phone:
- Samsung Galaxy SIII
- AT&T
- 8GB miroSD card
- Model: SAMSUNG-SGH-1747
- Android Version: 4.0.4
- Baseband Version: 1747UCLH9
- Kernel version: (IS THIS CONFIDENTIAL INFORMATION?)
- I have installed a couple of root apps that I didn't know where root apps and so they don't work obviously.
- Ones I installed: Lucky Patcher, Titanium Backup
- It's not rooted yet I haven't modified it at all besides themes and settings
The reason why I'm posting:
- Can anyone please tell me EXACTLY which updated guides I need to follow for my specific device?
- How can I backup my device? I'd like to keep all the apps (and app data), contacts, everything if possible.
- I read as much as possible but I'm still not sure which guide to follow and which steps I need to take as some are dated and not recent. I'm scared I'll mess up my phone what are the chances of messing up my IMEI, bricking, bad stuff happening.
- Anything else I should know?
- What are some popular ROMS I can install on my phone that are supported (preferrably with JB)?
- Can I always go back to my original settings and apps like a restore but with a backup?
- Once I root what BLOATWARE can I UNINSTALL on my AT&T SIII? How do I do this as well?
Thank you for your patience, I am definitely going to stick with Android (stock iOS sucks balls and android is so much more aesthetically pleasing) I just want to make sure I'm doing everything right and that there is a proper way to do this.
Click to expand...
Click to collapse
hey there welcome to XDA and more importantly to the world of android.
first off rooting can be relatively simple depending on the method you use. ive rooted mine twice using odin. i just followed the video here ON Galaxys3root . com all the things you need are in the description.
rooting your phone using this process will not wipe any data, contacts, pics, etc.
once you complete the root process and get rom manager installed it will allow you to make a back up of the current system with all your data like texts phone call logs etc.
the most popular roms are aokp based and cyanogen based roms. ( just look at threads with [ROM] before it ) roms are personal preference. if you flash a cyanogen based rom you will not have the features of touchwiz. stock based roms are always good too right not im just running stock i747uclh9 rooted.
going back to your original rom is simple all you do is boot to recovery (rom manager) and do a restore. before restoring you should wipe data, cache partition and dalvik cache. (dalvik is under the advanced menu.
removing bloatware just use no bloat free this will let you remove and also create a back up of all apps incase you have an issue.
for right now i personally just use ics based roms if you want to stick to stock since there has not been an att jb leak. however if you want jb i recommend cyanogen nighties basic jelly bean roms never had an issue personally.
if you have any more questions feel free to PM me.
IF THIS POST HELP YOU IN ANYWAY PLEASE CLICK THANKS
aboveusonlysky said:
hey there welcome to XDA and more importantly to the world of android.
first off rooting can be relatively simple depending on the method you use. ive rooted mine twice using odin. i just followed the video here ON Galaxys3root . com all the things you need are in the description.
rooting your phone using this process will not wipe any data, contacts, pics, etc.
once you complete the root process and get rom manager installed it will allow you to make a back up of the current system with all your data like texts phone call logs etc.
the most popular roms are aokp based and cyanogen based roms. ( just look at threads with [ROM] before it ) roms are personal preference. if you flash a cyanogen based rom you will not have the features of touchwiz. stock based roms are always good too right not im just running stock i747uclh9 rooted.
going back to your original rom is simple all you do is boot to recovery (rom manager) and do a restore. before restoring you should wipe data, cache partition and dalvik cache. (dalvik is under the advanced menu.
removing bloatware just use no bloat free this will let you remove and also create a back up of all apps incase you have an issue.
for right now i personally just use ics based roms if you want to stick to stock since there has not been an att jb leak. however if you want jb i recommend cyanogen nighties basic jelly bean roms never had an issue personally.
if you have any more questions feel free to PM me.
IF THIS POST HELP YOU IN ANYWAY PLEASE CLICK THANKS
Click to expand...
Click to collapse
will this Jellybean ROM work:
http://forum.xda-developers.com/showthread.php?t=1869300
Do you know if it has a lot of problems?
EDIT: Also does the root method at this website still work for my version which is UCLH9?
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Bronos said:
will this Jellybean ROM work:
http://forum.xda-developers.com/showthread.php?t=1869300
Do you know if it has a lot of problems?
EDIT: Also does the root method at this website still work for my version which is UCLH9?
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Click to expand...
Click to collapse
Hello, welcome to the android side of the world! Glad you decided to switch over! first things first, in order to root all you need to do is flash a root able kernel via Odin. Tutorial for this method can be found here http://forum.xda-developers.com/showthread.php?t=1739426 Second, I would not recommend that rom as I just came from it and while it is very stable for a leak it is still quite buggy as it is built from a sprint leak. If you are that anxious to have a jellybean I recommend using aokp by task650 in the original development forum, however this will take away all of the touchwiz things that you said you liked so much. I am currently running kyanrom which I have used before and find myself returning to quite frequently because it is originally bone dry and he has whatever files you would like to add back you can add them through flashing zips. I am assuming you are wanting jellybean primarily for the Google now feature? If you will go here http://forum.xda-developers.com/showthread.php?t=1823194 it is a thread by me on how to replace s voice with Google now and as far as I can tell it seems to be working just as well as with jellybean!
Lastly, have a bunny!
(\__/)
(='.'=)
(""_"")
Sent from my SGH-I747M using Tapatalk 2
This is a little advice that has helped me and some friends of mine that have came from iPhone. Don't root and rom unless you absolutely have to or willing to pay the price to learn the ends and outs of it. Stock Android or in our case touchwized android can provide a complete satisfactory experience alone without rooting. But some tweaks and mods require root and if that can be bundled in a single rom then great. But if you have jail broken before or ever have to restore an iPhone firmware then rooting will be relatively easy, it's just learning how to self troubleshoot when something goes wrong.
Sent from my SGH-I747M using Tapatalk 2
Take a look at this post for rooting LH9:
http://forum.xda-developers.com/showthread.php?p=32218479
The method is mrRobinson's thread (the one mentioned in a previous post) requires downgrading to an older stock version (LG1) so you would need to upgrade again after doing that. Also, people have reported problems downgrading from LH9 to LG1 without doing a factory reset.
Edit: The method in the post I referenced is roughly the same as the one from the galaxysroot site the OP mentioned.
Make sure when you root your device, that the files are for your current build, android version, carrier and etc. If one thing is out of place you can possibly brick your phone. I'm still learning myself. The most important thing is make sure that you read everything 3 times. Make a check list. It helps.
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 06:41 AM ---------- Previous post was at 06:38 AM ----------
Bronos said:
will this Jellybean ROM work:
http://forum.xda-developers.com/showthread.php?t=1869300
Do you know if it has a lot of problems?
EDIT: Also does the root method at this website still work for my version which is UCLH9?
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Click to expand...
Click to collapse
The best jellybean rom I think is ParanoidAndroid. It's CyanogenMod 10 based. CM10 is short hand.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hey guys when i switched to CWM recovvery and selected backup to external sdcard it said 'android.secure' couldn't be found skip backup of applications.
So it did not backup my app data, what should I do?
Titanium Backup. Make friends with it. In my opinion a must have for any Android device. For backing up everything you'd need when trying out roms to freezing/deleting (be careful with the latter) 'bloatware' (carrier nonsense) it will be a necessity. And life saver.
Sent from my SGH-T989 using xda premium
hompsar said:
Titanium Backup. Make friends with it. In my opinion a must have for any Android device. For backing up everything you'd need when trying out roms to freezing/deleting (be careful with the latter) 'bloatware' (carrier nonsense) it will be a necessity. And life saver.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I couldn't agree with this more. TB is an amazing piece of software and a real lifesaver. Also, since we have external sd cards, make sure to change the settings in TB so your backups are saved on it (if you save it to your internal storage your backup might get wiped during a session of flashing another ROM). If you purchase TB Pro, it includes an option to save your backup to Dropbox (it's well-worth the money and supports the developer too).
OP, I was a longtime iPhone user (I've still got the 4S in a drawer) and I always jailbroke too. Android can be confusing at first, because the terminology is different and just because it's a different operating system. But if you read (and read and read as someone suggested earlier), you'll get the hang of it. Once you do, you'll realize how much easier it is to root and play than it ever was with jailbreaking an iPhone. Another plus...you aren't in constant fear of losing your jailbreak (or root, in this case) because of an update. :good:
You think you know, but you have no idea...
First things first...
Did you understand what you were really doing when you were jailbreaking your iPhone?
What was going on in the background, how the jailbreak was working, what was involved in the jailbreak process or even what the different types of jailbreaks were e.g. userland vs. bootloader (hardware level) exploits [are you familiar with the term "exploit"].
If you think what I am talking about is confusing and if you weren't aware of these things, you might want to avoid rooting and/or flashing custom ROMs.
Android as a platform is much more open than iOS, so lots of features and functions don't require rooting or flashing custom ROMs.
Before I purchased my GS3, I was a die hard iPhone owner, year after year since the first iPhone (with the exception of the recently released 6th gen iPhone and a few diviations here and there to blackberry and old Android phones).
Before I even considered messing with my Galaxy, I read, read some more, and then a little bit more. Regardless of all the reading I did, I had a moderate level of understanding of what I was doing and how my actions were affecting my phone.
All the advice in the world won't save you from bricking your phone if you don't have a general understanding of what these tools are doing to your phone.
In the iOS jailbreak community, the developers behind the tools leverage Apple's fall-back restore features to nearly eliminate the possibility of bricking your phone. But that is also inherent to the platform since there aren't custom ROMs available to install to an iPhone (for many reasons).
To summarize,
It sounds like you need to learn a little more about the world you've been playing in previously before you start playing in the Android world.
Bronos said:
Hello XDA!
I recently traded my iPhone 4S about 2.5 weeks ago. I am in love with the Samsung Galaxy SIII. I love the sleek style and touchwiz is much more active and more "fun" than iOS. I love the google integration and all the cool features out of the box.
Since I'm new to android I'm really overwhelmed in the amount of information available to "modify or root."
I was a constant jailbreaker and had over 50-100 tweaks/jailbroken apps. I would like to get the same functionality on the SIII.
I wasn't afraid of jailbreaking and it was a one-button press jailbreak.
With android there are so many different versions and terminology to jailbreak and so many instructions and updates and in general just a lot of stuff.
About my new phone:
- Samsung Galaxy SIII
- AT&T
- 8GB miroSD card
- Model: SAMSUNG-SGH-1747
- Android Version: 4.0.4
- Baseband Version: 1747UCLH9
- Kernel version: (IS THIS CONFIDENTIAL INFORMATION?)
- I have installed a couple of root apps that I didn't know where root apps and so they don't work obviously.
- Ones I installed: Lucky Patcher, Titanium Backup
- It's not rooted yet I haven't modified it at all besides themes and settings
The reason why I'm posting:
- Can anyone please tell me EXACTLY which updated guides I need to follow for my specific device?
- How can I backup my device? I'd like to keep all the apps (and app data), contacts, everything if possible.
- I read as much as possible but I'm still not sure which guide to follow and which steps I need to take as some are dated and not recent. I'm scared I'll mess up my phone what are the chances of messing up my IMEI, bricking, bad stuff happening.
- Anything else I should know?
- What are some popular ROMS I can install on my phone that are supported (preferrably with JB)?
- Can I always go back to my original settings and apps like a restore but with a backup?
- Once I root what BLOATWARE can I UNINSTALL on my AT&T SIII? How do I do this as well?
Thank you for your patience, I am definitely going to stick with Android (stock iOS sucks balls and android is so much more aesthetically pleasing) I just want to make sure I'm doing everything right and that there is a proper way to do this.
Click to expand...
Click to collapse
www.galaxys3root.com <---- This is the website you need, just click on the Galaxy S3 FAQ and look under your model for all the information.
mathewrice said:
First things first...
Did you understand what you were really doing when you were jailbreaking your iPhone?
What was going on in the background, how the jailbreak was working, what was involved in the jailbreak process or even what the different types of jailbreaks were e.g. userland vs. bootloader (hardware level) exploits [are you familiar with the term "exploit"].
If you think what I am talking about is confusing and if you weren't aware of these things, you might want to avoid rooting and/or flashing custom ROMs.
Android as a platform is much more open than iOS, so lots of features and functions don't require rooting or flashing custom ROMs.
Before I purchased my GS3, I was a die hard iPhone owner, year after year since the first iPhone (with the exception of the recently released 6th gen iPhone and a few diviations here and there to blackberry and old Android phones).
Before I even considered messing with my Galaxy, I read, read some more, and then a little bit more. Regardless of all the reading I did, I had a moderate level of understanding of what I was doing and how my actions were affecting my phone.
All the advice in the world won't save you from bricking your phone if you don't have a general understanding of what these tools are doing to your phone.
In the iOS jailbreak community, the developers behind the tools leverage Apple's fall-back restore features to nearly eliminate the possibility of bricking your phone. But that is also inherent to the platform since there aren't custom ROMs available to install to an iPhone (for many reasons).
To summarize,
It sounds like you need to learn a little more about the world you've been playing in previously before you start playing in the Android world.
Click to expand...
Click to collapse
Hey man thanks for the advice!
I figured it out eventually. I just had to read and actually try Rooting. I now know most of the terminology of android. It's pretty straightforward. Of course there are some errors. But seriously Android is absolutely unbelievable (especially 4.1.1 and JB) have features I could only dream of getting supported on the iPhone.
If I do get errors there is usually a fix or something I can look up on how to avoid it. If a day comes when I do brick I should be alright if I do brick AT&T should be able to replace it for me. I've been a loyal customer to them and my family included.
I highly recommend this guide to rooting. I used it just a few days ago and it worked perfectly.
I tried AOKP and CM10 but have actually settled on this stock ROM for now. I like being able to maintain the 'motion' features which aren't standard on the others. Google Wallet works well too which is a big plus for me. There should be an update in the next 24 hours to "Milestone 5".
That'd the same one I'm using.
Sent from my SPH-L710 using xda premium
Titanium Backup
Spend those dollars on this App its worth every penny. Read all the FAQs under the links others already gave you.
OK, so bear with me, as I haven't rooted a phone is quite a while, and am having trouble locating just what I need. My goal is strictly to root the phone, I don't necessarily want to move off my os, as I am happy with it (Jellybean 4.1.2). If that is required, my apologies for being so uninformed on the process.
Here is my phone info:
Samsung Galaxy SII SCH-R760X (Carolina West Wireless is the carrier, but my recent rom stated that it was CDMA generic).
Android Ver = 4.1.2
Build = JZO54K.SCH-R760X.GB28
Kernel = 3.0.31-980103
Hardware version = H:R760.01 K.Q
I have tried to find an updated version of CF-ROOT, or something similar...but open to suggestions.
Thanks!
mjolly said:
OK, so bear with me, as I haven't rooted a phone is quite a while, and am having trouble locating just what I need. My goal is strictly to root the phone, I don't necessarily want to move off my os, as I am happy with it (Jellybean 4.1.2). If that is required, my apologies for being so uninformed on the process.
Here is my phone info:
Samsung Galaxy SII SCH-R760X (Carolina West Wireless is the carrier, but my recent rom stated that it was CDMA generic).
Android Ver = 4.1.2
Build = JZO54K.SCH-R760X.GB28
Kernel = 3.0.31-980103
Hardware version = H:R760.01 K.Q
I have tried to find an updated version of CF-ROOT, or something similar...but open to suggestions.
Thanks!
Click to expand...
Click to collapse
This might be worth looking at mate.
http://forum.xda-developers.com/showthread.php?t=1928566
will give it a try
imak3d3dp3pl said:
This might be worth looking at mate.
http://forum.xda-developers.com/showthread.php?t=1928566
Click to expand...
Click to collapse
I saw this one, but kind of assumed it would overwrite my updated rom. Since I still have the updater for jellybean (from Carolina West), I guess I can always go back to the way it is now if I don't care for it...so I will give it a shot. Thanks for the info! I appreciate it.
Nope
imak3d3dp3pl said:
This might be worth looking at mate.
http://forum.xda-developers.com/showthread.php?t=1928566
Click to expand...
Click to collapse
That didn't work out for me. Took a while to locate a good link for the kernel, but it seems to load fine with Odin, but I get the startup screen with a yellow triangle, and it doesn't move past that. I had my doubts as it seemed to be older than my current os/etc., but gave it a shot anyhow. I think the kernel is the only thing I need (as I only need root, not the custom rom, unless I have to)...so if I can get that working, all will be great. Thanks in advance for any additional direction.
Hi everyone. So I Just got a note 2 the other day after having been using a nexus 4 for the past six months. I never use stock Roms and haven't since I got my s3 a year or so ago (I seemingly change phones often...). That being said I was looking into how to root this device and which Roms were compatible etc.
It seems all Canadian note 2 devices are the same? Rogers, Bell, koodo/telus etc? Am I correct in assuming this, and if so that any of the Roms found in this forums sub forums for aosp as well as other Roms like PA etc are compatible? (if it's compatible with the att note 2 my koodo note 2 is good to go?)
Also, it seems this devices forums are outdated and dying sadly, so can anyone recommend a recently active Rom, be it aosp or not, that is highly themeable and configurable, and preferably has good s-pen support?
Much appreciated!
Oh, and a link to the correct post for rooting this device and flashing new recovery (twrp or cwm) in its latest compatible version would be awesome too.
Thanks everyone!
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Click to expand...
Click to collapse
Great Question and great response.
I recently got the Koodo note 2. I finally switched coming from my well aged HTC HD2. Anyway I have a quick question. If i'm using a TW or a AOSP rom I can't connect to my Mac adhoc network. The old roms I used on My HTC had something baked into them that allowed that. Note sure if there's a special file I have to change. Any help would be appreciated.
Thanks
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
Click to expand...
Click to collapse
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
DelphinusMinor said:
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Click to expand...
Click to collapse
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Catalyst2012 said:
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Click to expand...
Click to collapse
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Darkshado said:
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
Click to expand...
Click to collapse
Thanks.
1) No need to check the TWRP code as your response was clear and helpful.
2) A local unlocker business told me: they have a new way that no longer requires downgrading to 4.1.1. With his codes, I could unlock the device without any additional software or PC for C$40. I explicitly asked about KNOX - he wasn't 100% clear but said he did not think it would affect it. He said they buy lists of unlock codes based on IMEI and resell them for a small profit. Koodo requires 90 days on Koodo + the same unlock $ fee. I wasn't planning on staying on Koodo that long. In perhaps the 8 hours by now I've spent reading about this on XDA, its still not certain a device with 4.3 can be customized without blowing the Knox efuse. Towelroot 'might' give me root without tripping it but the risk of losing a full 12 month warranty is not welcome. A used device might be OK if it was still on 4.1.x. If it had been downgraded from 4.3, though unlikely, I probably wouldn't know until after I got home. Otherwise I could root+custom right way and never mess with samsung roms.
Any suggestions are welcome!
DelphinusMinor said:
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Click to expand...
Click to collapse
You should be able to test it without using any of your minutes. Just call Koodo customer service from your handset (*611 I think) it should be a free call. When the voice menu begins, start recording. Ask a few questions like "Do you support custom ROMs?" or "Do you know the winning lottery numbers", or whatever, this is just a 2-way voice recording test. I use this trick all the time when testing. Enjoy.
I have a tmo note 10.1 2014. Are any of these lte roms compatible at all??
Why yes they are I'm running xKat 5.0, SE permissive stock kernel, and TWRP (and have been since the night I got that tablet a week or so ago). SO glad that T-Mobile is carrying this hardware, AND that they're generally cool with rooting / modding etc. I even told the guy at the Tmo store my "policy" that I WILL NOT buy (well, much more trade in this case :good: ) any device that has arbitrary restrictions preventing me from gaining root (i.e. the ability to administer my own device.) He was ridiculously cool... even told me he was pretty sure it was cool if I flashed custom firmware on my new completely gratis "cellspot" router if I restored it to stock before I returned it (or likely will end up buying). SO glad Tmo is making all of these pro-consumer moves... and also that it seems to be working out for them so well (not to mention, their customers)!
I've read some of your posts around here. You mention removing a few files before flashing. Did you? If so, can share with me what/how you did?
Sent from my SM-P607T using XDA Premium HD app
No, I didn't... as you've probably noticed, info re: the entire process of root, recovery, custom ROM is kind of spread out around the forum. I thought that might be necessary because I recalled reading something about having to do that to flash a p605 ROM on a p607t (might have pertained to a specific ROM or something), but I asked specifically in the xKat thread to make sure and found it (well, first by just trying it - then took a look at the thread mid flash and saw that someone had responded :good that the xKat zip can be flashed as-is. Select any options you'd like in the Aroma installer and you're good to go! (You do need to flash an additional file after at least one reboot - otherwise you'll need to enter your wifi pass after each reboot... it's the OP of the ROM thread).
I can only say for certain that xKat w/ SE permissive kernel works great on the 607t... I think any p605 ROM can actually just be flashed without modification (hopefully someone will chime in and correct me if that isn't true - I think the info about modifying zips was just speculation, but was found not to actually be the case). Just make sure to make a nandroid of the stock ROM before flashing
How are you liking the new tablet? Loving it here! I hope now the T-mobile is selling it (by far the best of their Android tablets), this device will gain back some popularity that it lost from the TabPro release a few months later. Perhaps the forum will liven up a bit
I absolutely love this tablet. Im coming from a Nexus 10 and although they share the same screen resolution, this one is much faster, sleeker, brighter, and I'm loving the S pen. I had it rooted ten minutes after i brought it home. I've also recovered from a soft brick after having flashed the wrong twrp. Woops! Ive been dying to try different rom on this bad boy, hence all the questions for you. I'm gonna give xkat a go here. I'll report back to you with my results!
Sent from my SM-P607T using XDA Premium HD app
Nice man! Feel free to PM me if you get stuck anywhere along the way
BTW: Something I just learned, even if you select the SE permissive kernel, your kernel will be enforcing unless you manually change it, either via terminal or that SElinux Changer app (forgot exactly what it's called). I had been confused re: why in "About device" it said that the kernel was SE enforcing even though I installed the permissive one. Just FYI
Does spen work on xkat anybody revert successfully and gain the function back?
Neozx25 said:
I absolutely love this tablet. Im coming from a Nexus 10 and although they share the same screen resolution, this one is much faster, sleeker, brighter, and I'm loving the S pen. I had it rooted ten minutes after i brought it home. I've also recovered from a soft brick after having flashed the wrong twrp. Woops! Ive been dying to try different rom on this bad boy, hence all the questions for you. I'm gonna give xkat a go here. I'll report back to you with my results!
Sent from my SM-P607T using XDA Premium HD app
Click to expand...
Click to collapse
Hi, I have this tablet as well I've been on this build ne2 since I got it, & rooted it with towelroot but can't for some reason update I trying to update to the latest version that cam yesterday ota but it keeps failing can u help me please pm me
Hey folks!
I'm trying to research rooting procedures & tutorials and am running into a problem regarding 4.4.2 builds and compatibility. (I'm relatively tech savvy but have never rooted a device)
I have a T520 with Kitkat 4.4.2 build no. KOT49H.T520UEUANI1. The issue is that it seems this build has been available since last year, and somehow it is apparently the latest update (when I check for updates, it tells me this is the latest).
Now, as I understand it when using software like Odin to assist rooting, build compatibility is very important. I cannot find a tutorial with my particular build, or any information on its compatibility with Odin et al. The latest tutorial I can find for a T520 Root is for build KOT49H.T520XXUANAE ( I intended to link the URL but cannot as I'm a new user with less than 10 posts - if you'd like it, I can try typing it out manually). This particular tutorial was last updated on March 23rd of this year, so I assume this build is a later build than the one I am currently running.
It is also very possible I'm simply not comprehending basic information properly, so if there is any clarification or advice you can offer, I'd be happy to take it! Off the top of my head, I see builds mentioned such as KOT49H.T520XXUANI1 and I wonder if the "XX" is just a placeholder for various letters - it seems to be present in many builds, so it makes me curious. Anyhow, I'm very interested in rooting my device but obviously don't want to brick it in the process.
Also, I apologize if this is not the appropriate thread or forum to post in - it seemed the most recently active and relevant at the time of my posting and I didn't seem to find any appropriate answers in the suggested threads mentioned before posting this.
Thanks for reading!
-T
The "XX" is a region code (stands for some regions in Europe). IMO, the only thing matters is the last 3 digits of the build which shows the build date.
Also, as long as you don't care about Knox and warranty, isn't rooting Samsung stuff as simple as flashing a recovery via Odin and flashing SuperSU from there?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
The "XX" is a region code (stands for some regions in Europe). IMO, the only thing matters is the last 3 digits of the build which shows the build date.
Also, as long as you don't care about Knox and warranty, isn't rooting Samsung stuff as simple as flashing a recovery via Odin and flashing SuperSU from there?
Click to expand...
Click to collapse
Region code or the like was my suspicion, thanks for clarifying
Regarding the simplicity of rooting a Samsung device, I've never rooted a device of any kind before but from what I can tell - if following a tutorial - it does seem pretty simple. Also, I'm pretty certain my warranty has expired, so that and KNOX is of no concern.
Otherwise, because I'm new to the process of rooting, I want to make sure I'm on the right page, so to speak. If I can gather as much basic information about it as I can, and understand the context of that information, then I hopefully won't make an otherwise avoidable mistake. The build number compatibility was a little fuzzy to me.
Basically, I just need to make certain that whatever I use to root it is compatible with my tablet's build. From what I've gathered, that is one thing I should be certain of before beginning. That said, if yourself or anyone else can point me to something compatible with build KOT49H.T520UEUANI1, that would be be super helpful.
Also, thank you for taking the time to reply!
-T
I don't think you need to care that much about build number. Grab a custom recovery (latest TWRP recommended) for your device, flash it with Odin, and flash latest SuperSU package from it (it has almost universal compatibility).
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]