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
How can i RooT my 2.3.4 "SonyEricsson XPERIA Play (R800i)" with build number xxx.69?
Ok so....i have been looking for some tutorials (semi NooB here) and i cant seems to find some new one or one that is consistend or just about root.
Also many are outdated, poorly written, and there arent many tutorials as i saw about RooT-ing XPERIA Play, at least not the one with build number .69.
Also if i DO find some good (as i saw from comments) like this one for example: https://forum.xda-developers.com/showthread.php?t=2204321 (i mean i only really trust XDA forum for stuff i do to my phone) the links for necessary files are long gone.
So...if anyone can please help me or rederect me to some updated, good and thread or website with tutorial that HAS working links, please do!
Anyway...
So i got "SonyEricsson XPERIA Play" (R800i) with build number 4.0.2.A.0.69, With Android version 2.3.4. Its never been RooT-ed as i know.
So i just want to RooT it so i can remove ANNOYING bloatware and free up some space and make it clean teh way I want tbh! I see no other reason to RooT it... I mean there is one but im still thinking about it (for now) and that is, as i heard, since X-Play doesnt have any OFFICIAL updaes, its stuck on Android 2 (gingerbread) i heard that i can flash a ROM to Android 4, and that improves gaming, which is what i want TBH, i mainly, if not always, use this phone for gaming and emulators, and if Android 4 custom ROM can improve already great (for X-Play ofc) performance, id be happy to do so!!!
But first thing first, i like to get informed first of all... But as for now, im just looking help for first step, and that is: How to RooT my XPERIA Play, please?
Thanks guys! ^^
Anyone..i tried numerous stuff, but im constantly stuck..cant seems to rood. idk what am i doing wrong
[HOW-TO][zergRush Root] Root w/ v2.2.x-2.3.x (NOT ICS 4.x or GB after 11/2011)
This thread is a collaboration by myself, paxChristos, DooMLorD, & amishxda. Please give credit where credit is due. Thanks. This method has been confirmed to work on all models of the Xperia PLAY - R800x / R800i / R800a / R800at. Also works...
forum.xda-developers.com