I really like the UI of 2.8.6.2. Thank you very much lrs121. This is truly awesome. Most devices don't even have this version yet. My nexus 7(2013) flo doesn't have it, my coworker's sprint note 4 doesn't have it either.
Last edited:
[Recovery][D2SPR] TWRP for Boost/Virgin Mobile Phones
- Thread starter Lrs121
- Start date
-
- Tags
- development
That's cause I increment the version numbers when I make a change. Most devices with official twrp are version 2.8.6.0. I've made 2 changes from basic twrp hence 2.8.6.2. The changes can be found in the change log.
Oh, I see. I like the look, and new features. The way you choose internal and external storage is more intuitive. Its working very well. Thanks again for making this, philz was starting to feel a little antiquated. And philz is soooo slow. This is just as exciting to me as a new ROM.
Yah ive been itching to make a new recovery for my old nexus 7 and nexus 5 with the new look. also credit for the new look goes to the respective creators i just cherry-picked it cause i like the look of it better.
version 2.8.6.3 is out, change log is in op. Make certain to read the second post to understand the limitations and features of the recovery http://forum.xda-developers.com/showpost.php?p=60495767&postcount=2
I've been running PhilZ on my d2spr (VirginMobile) forever (and flawlessly). I keep reading disclaimers on various ROMs that they're not responsible, blah, blah, if we don't flash using TWRP. I tried the TWRP install via the Play app--nothing mounted. Which led me here.
I've just spent an hour trying to flash the tar.md5 via Odin--which crashes every time. I've tried different versions of Odin, I've run with and without administrator priviledges. I tried using Odin to reflash the latest PhilZ (which was still on my sdcard) and it worked beautifully.
What do you think is going on with Odin/TWRP/my phone??
Is TWRP significantly better than PhilZ? (I know development has stopped on the PhilZ.)
I've just spent an hour trying to flash the tar.md5 via Odin--which crashes every time. I've tried different versions of Odin, I've run with and without administrator priviledges. I tried using Odin to reflash the latest PhilZ (which was still on my sdcard) and it worked beautifully.
What do you think is going on with Odin/TWRP/my phone??
Is TWRP significantly better than PhilZ? (I know development has stopped on the PhilZ.)
Last edited:
I just came here to post the exact same thing. Odin keeps crashing when I try to flash the tar. I can't flash .img files with philz. I can't do the old flash_image through adb method because i get an error saying that only position independent executables are allowed.
What if I told you you could have twrp for $0.99? I got it working using flash image gui from the play store. Just download the latest twrp.img and point the flash image gui at it. Reboot to recovery and enjoy.
Interesting. Thanks! I happened to have gotten it loaded using Flashify (for root users) from the Play store (FREE!) to load the latest .img from this thread. I just used TWRP to flash the latest AICP 5.1.1. So far, so good...
I would still find it useful to know why the Odin .tar.md5 route doesn't work on my (our) phone. And is there, in fact, an advantage to running TWRP at this point? Just curious.
Last edited:
Just get flashify from the play store. Its free and flashes image files. Great app.
---------- Post added at 03:54 PM ---------- Previous post was at 03:51 PM ----------
Twrp is much more advanced at this point. It also supports f2fs formatting. Most Roms that have ota updaters will not work with philz. They need twrp. Philz was never updated to properly support lollipop. And the list goes on and on.
That's a'zackly what I was curious about. I'll stick with the TWRP, then. Any thoughts on why it won't "Odin"??
To add to this, If you already have root you can use the DD method in the op
Haven't a clue since it doesn't spit out logs, though I've never had any issues with 1.85 version of odin or something along those numbers.
I tried several different versions I had of Odin. The absolute newest, and a couple of really old ones. And, remember, at least in my case, the PhilZ Odin'd instantly and cleanly...
Hum strange. though the s3 i have is a generic cdma one, not a sprint variant like is used for Boost or virgin. for the sake of posterity heres the setup i used to flash with odin.
- Windows 8.1
- Windows completely updated
- Samsung Kies 2 & 3 installed
- The latest odin available
- Google ADB & fastboot installed
If oding keeps having trouble try flashing the img.tar with jodin built with the casual language and it can be used on linux.
I also used all the ODINs with the same setup, adding that I also have the correct smasung drivers. It kept crashing while analyzing the .img. At least it crashes before doing any flashing. I have ODINed the ndc stock rom and philz fine. Could it possibly be the same reason that flash_image via adb fails (The PIE thing)?
Possibly it may just be I have a bad tar image up
So... i was right i put a bad tar image up.
when you make the tar.md5 files the recovery has to be named recovery.img
new files are up
Guide using cm11 is up plus a surprise later
@Lrs121 By the way, I just tried twrp 2.8.7.0 for d2spr. It mounted everything properly. (I'm on virgin Mobile). No previous builds, except for yours of course, have done that. I prefer yours much more. The ui, the color, the whole setup.
I wonder if TWRP 2.8.7.0 can format the /data partition as f2fs?
EDIT: Yes it can.
EDIT: Yes it can.
Last edited:
I just cherry pick the ui from omniroms gerrit. its the planned next look for twrp
And thats what the surprise was gonna be. i had it almost figured out. ive got a test build out but if you or madbat can sent a full recovery log so i can tear through it and find out why mine doesnt work.I wonder if TWRP 2.8.7.0 can format the /data partition as f2fs?
EDIT: Yes it can.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone