• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SPH-M930GLS build

U

unixpunk83

Lurker
I received a refurbished Transform Ultra from Ting. Everyone said their devices were supposed to be Sprint branded but the phone I received has a build.prop that indicates model SPH-M930GLS but also mentions SPH-M930BST in the ro.build.fingerprint of build.prop so I'm not sure what I have here exactly since I was under the impression that Sprint phones were just "SPH-M930" with no extra letters.

There are issues with the ROM and Google Play and other apps (still shows market, won't update itself, pushing newer apk via adb side loading gets null download errors). Build is based on 2.3.4 EG29.

I can su and remount /system rw and wrote an extra comment line to build.prop via adb.

Is there any way to tell what flash I can use on this device to either replace this with a good build or fix the installed apps package? And if so whether it really needs a Boost or a Sprint flash?
 
unixpunk83 said:
I received a refurbished Transform Ultra from Ting. Everyone said their devices were supposed to be Sprint branded but the phone I received has a build.prop that indicates model SPH-M930GLS but also mentions SPH-M930BST in the ro.build.fingerprint of build.prop so I'm not sure what I have here exactly since I was under the impression that Sprint phones were just "SPH-M930" with no extra letters.

There are issues with the ROM and Google Play and other apps (still shows market, won't update itself, pushing newer apk via adb side loading gets null download errors). Build is based on 2.3.4 EG29.

I can su and remount /system rw and wrote an extra comment line to build.prop via adb.

Is there any way to tell what flash I can use on this device to either replace this with a good build or fix the installed apps package? And if so whether it really needs a Boost or a Sprint flash?
Click to expand...

Being a Sprint user for the SPH-M930 I do know that all Rom's for this phone does work no matter if the build was for Boost as most Rom's are except for Megatron. Still had access to everything.

As far as your phone, I can not speak intelligently on that subject being as I know nothing about Ting. Sorry. But flashing Megatron should help.
 
Probably the best course of action is install CWM via Odin and then I believe I saw a zip that would pack a tar file for odin restore so I can have whatever this build is exactly backed up and then install megatron from CWM then I guess. Depending on what Ting says about the devices shipping out in this state.
 
Ting has confirmed that the phone is a former Boost phone. Thanks for all the info, I'll update if flashing a ROM built for Boost works out.
 
I downloaded the stock Boost recovery odin flash and extracted it, dumped partition 13 from the phone, same length and cmp shows no bytes different so the recovery image is definitely stock Boost recovery but still not sure what the system flash on here is exactly since it has no Boost branding and doesn't seem to have all the Gapps installed correctly.

Fairly confident that should be able to overwrite partition 13 with CWM image while booted to full system since it has root and then boot to CWM to backup whatever this system image is.
 
unixpunk83 said:
Fairly confident that should be able to overwrite partition 13 with CWM image while booted to full system since it has root and then boot to CWM to backup whatever this system image is.
Click to expand...

CWM image written to partition 13 followed by a reboot recovery booted to cwm fine, but backup of the existing system gives me an error while making a backup.

Going to reboot and see if this system image overwrites recovery like the stock images do.

Edit: The reboot to the installed ROM did NOT replace CWM recovery. Can still access the modified recovery just fine. Waiting for Ting to determine how they want to handle these issues before I attempt to flash MegaTron.
 
Just documenting more I find about this software build.

backup from CWM fails because of a vfat file size limit. Not sure how it is getting 4GB+ tar created from a ~2GB internal mmc flash....


/sdcard/clockworkmod/backup/2012-10-26.18.45.49 # ls -l
-rwxrwxrwx 1 root root 5242880 Oct 26 18:45 boot.img
-rwxrwxrwx 1 root root 7864320 Oct 26 18:45 recovery.img
-rwxrwxrwx 1 root root 4294967295 Oct 26 18:57 system.ext4.tar


/sdcard/clockworkmod/backup/2012-10-26.18.45.49 # fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
 
So far so good, went ahead and captured the partitions using the Odin tar creator scripts and then flashed the Boost image for Megatron and it booted just fine and seems to be running well and am able to use Play and other google apps without the issues of that "bad" testing rom or whatever it was. Thanks to all the devs here who put together such great information.
 
You must log in or register to reply here.
Back
Top Bottom