[Recovery][D2SPR] TWRP for Boost/Virgin Mobile Phones

[Lrs121]

MTP may or may not be enabled. i dont remember if i disabled it on build. ive made one more build but apparently the official twrp version is working. if you like the material layout you can use the official version with this theme http://forum.xda-developers.com/devdb/project/dl/?id=13238 and if you need help installing it read this http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584/post56224204#post56224204

 

[madbat99]

MTP may or may not be enabled. i dont remember if i disabled it on build. ive made one more build but apparently the official twrp version is working. if you like the material layout you can use the official version with this theme http://forum.xda-developers.com/devdb/project/dl/?id=13238 and if you need help installing it read this http://forum.xda-developers.com/and...light-play-t2915584/post56224204#post56224204

The theme worked beautifully. It says its for one m9, but worked fine. Do you think it would work on the note 4? I'm helping a friend.

 

[Lrs121]

The theme worked beautifully. It says its for one m9, but worked fine. Do you think it would work on the note 4? I'm helping a friend.

It's the same theme that's in testing that I cherry pick when I build twrp, just packaged as theme zip. With the way twrp does themes now it doesn't have specific sizes for screens. It's based on density and scales for screen sizes. The m9 theme is 1080p but scales down for 720p. It should work for the note 4, scaling up to its resolution from 1080p though it may not look quite as good.

 

[Lrs121]

working on an updated build using the android 6.0 twrp sources

 

[Lrs121]

working on an updated build using the android 6.0 twrp sources

New build is live. It Should work but be considered beta quality. Built with a new build system and had to reinitialize the project so there may be broken things.

 

[cwhatever]

What is better about this update then the last one that works great on my boost s3?

Sent from my SPH-L710 using Tapatalk 2

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------

What is better about this update compared to the last one that works great on my boost s3.

Sent from my SPH-L710 using Tapatalk 2

 

[Lrs121]

What is better about this update then the last one that works great on my boost s3?

Sent from my SPH-L710 using Tapatalk 2

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------

What is better about this update compared to the last one that works great on my boost s3.

Sent from my SPH-L710 using Tapatalk 2

Just bug fixes, though I cant test it myself since I dont own a boost/virgin device. Though I remember hearing a little while back that the official twrp images work now. I just find it slightly annoying that they dont update them very often even after there are some major bug fixes included in the sources since the last time they compiled the recovery. If you dont want to run it the last build should work just fine, its just an unknown factor if android 6.0 roms will install with the old one when the aosp community catches up.

 

[cwhatever]

I will give it a go tomorrow or the next day and post the results. Thx.

Sent from my SPH-L710 using Tapatalk 2

 

[Lrs121]

new build based on cm-12.1 source tree and twrp updates. version = 2.8.7.2

Oh and new graphics

 

[Lrs121]

Im trying out a new build method, the recovery should work as always but i modified some of the sources for building purposes. You can find them on my github here https://github.com/Lrs121/android_device_samsung_d2spr and here https://github.com/Lrs121/android_device_samsung_d2-common branches cm-*version*-vmb for the latter. there have been a boat load of fixes since the last build and I also believe the new graphics have been green lighted so they should be built in already.

This may or may not be my last build, the friend i was building for has upgraded to my old nexus 5. Ill try and keep an up to date guide for build guide at https://github.com/Lrs121/android_recovery_resources/wiki/Build-TWRP-for-D2SPR_Boost-or-D2SPR_Virgin as well as keep my sources up to date as best as possible for another year or so but after that its up to everyone else to submit issues and pull requests so long as the device can be built for on cyanogenmod. I may also include it in an automated build environment if resources allow for it.

 

[Lrs121]

Got bored at work and updated the build guide. https://github.com/Lrs121/android_recovery_resources/wiki/Build-TWRP-for-D2SPR_Boost-or-D2SPR_Virgin

 

[spirithandler]

Stupid Question alert!!!!
Will this work on a sprint s3?

 

[Lrs121]

Stupid Question alert!!!!
Will this work on a sprint s3?

Obvious answer is no. Specific answer is it depends.

I've noticed that some Sprint S3's have an odd partition table and don't usually work with the official twrp versions.

My question, now, is why do you ask? Do you fall in to that category where the official twrp versions dont work for your phone?

 

[Lrs121]

I don't know who still uses my builds, but since I've finally gotten a build server up again I thought I might throw the recovery on there.

 

[wilberfan]

I don't know who still uses my builds, but since I've finally gotten a build server up again I thought I might throw the recovery on there.

Good to know you're still building these. I recently flashed the 3.0.0 from the TWRP page on my d2spr and it seems to be fine. Is yours significantly different...? I've forgotten!

 

[Lrs121]

Good to know you're still building these. I recently flashed the 3.0.0 from the TWRP page on my d2spr and it seems to be fine. Is yours significantly different...? I've forgotten!

Not particularly, I've forked the original repo which I keep inline with the official repo. The only real difference is mine tend to be more bleeding edge then the official builds and sometimes include code or features that are only on omniroms gerrit that don't always get merged in.

My fork can be found at https://github.com/Lrs121/android_bootable_recovery -- forgive the lack of clickable link, I'm using the XDA labs app right now.

You can track any changes there.

 

[wilberfan]

Not particularly, I've forked the original repo which I keep inline with the official repo. The only real difference is mine tend to be more bleeding edge then the official builds and sometimes include code or features that are only on omniroms gerrit that don't always get merged in.

My fork can be found at https://github.com/Lrs121/android_bootable_recovery -- forgive the lack of clickable link, I'm using the XDA labs app right now.

You can track any changes there.

I downloaded the first .zip I came across and tried to flash it--no dice. I obviously missed what we need...?

 

[Lrs121]

I downloaded the first .zip I came across and tried to flash it--no dice. I obviously missed what we need...?

Thats just the source code. I'm still working on getting the build environment setup then cranking out a build. I'll post the link when its done working.

 

[madbat99]

@Lrs121 Hey bro, my wife broke her s3. I might have to get her the new virgin mobile J3. It looks to be an update to the s3. Similar specs, but with lollipop. Of course no twrp yet. Before I get it, curious about porting twrp. Just wondering if you've heard anyone has that phone, or may be building/porting twrp for it.
I know its a long shot, but ya never know till ya ask right? Lol.

 

[Lrs121]

@Lrs121 Hey bro, my wife broke her s3. I might have to get her the new virgin mobile J3. It looks to be an update to the s3. Similar specs, but with lollipop. Of course no twrp yet. Before I get it, curious about porting twrp. Just wondering if you've heard anyone has that phone, or may be building/porting twrp for it.
I know its a long shot, but ya never know till ya ask right? Lol.

I haven't seen anything related to it. I may be able to take a look at porting twrp if you'd like. The device isn't too expensive so I may be able to pick one up for testing when my tax return comes in.