These were/have been previously posted over in sprint apps section, but I keep seeing people posting questions about need this one or that...so here they are for T-Mo.
Thanks goes to the original developers for these, and for the sharing and caring..
Thanks for the thread. People always make these then never keep them up to date, so it's nice to have a current one. I guess they got different devices or stopped caring It's nice to have them all in one place.
One question, though. I notice you didn't tag the files with d2tmo. I know that d2spr recoveries work on this device, but wouldn't there be some assert problems on any zip that tries to verify the device before a flash?
Thanks for the thread. People always make these then never keep them up to date, so it's nice to have a current one. I guess they got different devices or stopped caring It's nice to have them all in one place.
One question, though. I notice you didn't tag the files with d2tmo. I know that d2spr recoveries work on this device, but wouldn't there be some assert problems on any zip that tries to verify the device before a flash?
Not that I am aware of. They are sprint branded, but identical versions.
The md5s don't match:
b6bf09d9afbbb5611a8173dd3bf453fb *recovery-clockwork-touch-6.0.2.3-d2spr.img
aff9411791f857c98c2538cb809348b8 *recovery-clockwork-touch-6.0.2.3-d2tmo.img
How can assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo"); possibly pass if using a d2spr recovery? Does that command only work if an OS is installed?
Understand, that I'm not necessarily saying that you are incorrect, but it just doesn't add up to me.
The md5s don't match:
b6bf09d9afbbb5611a8173dd3bf453fb *recovery-clockwork-touch-6.0.2.3-d2spr.img
aff9411791f857c98c2538cb809348b8 *recovery-clockwork-touch-6.0.2.3-d2tmo.img
How can assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo"); possibly pass if using a d2spr recovery? Does that command only work if an OS is installed?
Understand, that I'm not necessarily saying that you are incorrect, but it just doesn't add up to me.
then dont use it...use the flashable as a template to make your own...
I made my own months ago, I have tars in my sig and zips in my DropBox (which I've linked several times). You seem to have taken offense at my questions, when I clearly pointed out I didn't want you to interpret them that way. My questioning was merely a vain attempt to learn something new. Not to tear you down, but for me to become more knowledgeable about a subject from someone who clearly knows more about Android than I do.
I could of used you yesterday. I was literally scouring yesterday looking for a flashable recovery. Ended up using adb and Odin to flash something.. Thx for this post.
I tested both CWM Touch and TWRP myself this morning (latest versions for both). d2spr recoveries (the ones originally posted) absolutely fail the d2tmo assert check (for any zip that includes it).
As of 2012-02-17, 10:50AM EST:
The CWM Touch link is good (it was edited since my last post). Did not test CWM non-touch. Not sure why anyone would use it.
The TWRP 2.4.1.0 link is bad. This is still the d2spr version. Safe to assume the older versions are as well.
Stock recovery link is also bad.
Do not flash recoveries that are not for the T999.
So you’re playing with your shiny new Windows 8 tablet PC, when one of your like-minded geeky … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?