Develop Bugs

[RECOVERY] TWRP-2.7.0.0-moto_msm8960-hdpi.img YOUR, pre Nov 8, TWRP IS BAD!

Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7

I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?

aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.

Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!

aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL

Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?

Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.

Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.

twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.

Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!

Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.

aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.

Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware

New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907

aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones

Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.

Would anyone know if Dhacker's TWRP works on the XT905 model as well?

Yes. But that is just good advice. I do not have one.

[Reward] [Request] [CM 11 ROM] Samsung Galaxy Tab Pro 12.2 (SM-T900)

I just bought one! and love CM since the release of my first android phone, the Samsung Galaxy S2
There are only custom roms for the 8.4 and the 10.1 version.
There are no custom ROMs available for this device now, and i hate the slurpy/fancy samsung interface.
I am willing to pay for it, for the first nice and clean nightly CM 11 rom + CWM/TWRP recovery and working Gapps for this device.
This device is out for a while now and there are still no custom roms for.
So i hope there is somebody who can help, to get the custom roms madness for this device getting started.

I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.

I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?

ExoRRSmits said:
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
Click to expand...
Click to collapse
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.

ik4evr2 said:
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
Click to expand...
Click to collapse
I am very much interested in this thanks!

nickster1 said:
I am very much interested in this thanks!
Click to expand...
Click to collapse
No problem at all. It will take me a day or two.

ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Can you make deodex please? I already have the stock debloate, but would be nice to have deodexed rom.

ik4evr2 said:
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
Click to expand...
Click to collapse
Well for now it sounds ok to me.
Is it rooted as well?
How debloated is it? Is samsung touchwiz removed?
That's what i'm hating the most. The settings app with tabs, i like the whole settings menu in cm.
And how fast can it see the light?
If its very nice, i can donate something for your good and hard work.

There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206

Ludespeed said:
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Click to expand...
Click to collapse
No, I tried it, and unfortunately it doesn't work for the 12.2 version. The internal, as well as the external sd card both are locked, meaning you can't even update any apps, or saving any data... you get an error message 110, from Play Store.

ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Any luck ?

ExoRRSmits said:
Any luck ?
Click to expand...
Click to collapse
+1!

What about an overclock kernel? I debloated my Galaxy tab 12.2 already but have yet to successfully overclock it. I've been looking everywhere for an improved kernel or something to improve the performance, debloating didn't help it that much so a kernel or custom rom would be the next bet. Anyone point me in the right direction?

In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go

Shaheer said:
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Click to expand...
Click to collapse
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.

arcadia2uk said:
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
Click to expand...
Click to collapse
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing

Shaheer said:
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Click to expand...
Click to collapse
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.

arcadia2uk said:
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
Click to expand...
Click to collapse
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.

Shaheer said:
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Click to expand...
Click to collapse
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.

arcadia2uk said:
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
Click to expand...
Click to collapse
Hey!,
So I was really busy yesterday evening writing a 3 page essay and doing other homework so I didn't get anytime to work on the rom. My thoughts too were to start a new thread in the dev section for this.
I haven't gotten too far with the T520 port either as i'm still learning CM development. (I'm more used to touchwiz ) I have some time right now so give me a bit and i'll try to get a thread started and update the rom to get SD Card working.
EDIT: Actually, I can't proceed till someone can make sure that Google Play downloads app properly. If it doesn't then I need to work on that before anything or it's going to cause major issues.

[Q] OS does not start on MOTO G.... Says android is Locked...!!!

Hi Everyone..... Hope you are all doing Great....
Today I wanted to get my hands on Paranoid Android on my MOTO G (XT1032). I flashed the build - - 5.1-- (File a_falcon-5.1-20150704.zip), everything went fine but my phone couldn't start and after 'Android is upgrading' screen it displayed a message 'Android is Locked enter password to unlock your Phone', and initial setup couldn't begun. I tried fofmatting everything (which I already had done) and re-flashed PA but in vain. Please if someone can provide help.
I also tried flashing without GApps but it still didn't work
I was previously using FLEX OS Android 5.1.1. After this experience with PA I flashed EUPHORIA OS (5.1.1) and Resurrection Remix(5.1.1), both worked like charm.
I really wanna try Paranoid Android, so please help me out as I am just a simple user not an Android geek..... ?
Regards.

hamzaalijoiyah said:
I tried fofmatting everything (which I already had done) and re-flashed PA but in vain.
Click to expand...
Click to collapse
Try to format your data partition with Ext4 and flash PA again. It should work without getting stucked. However, you probably will not be able to encrypt your data partition using the built in PA encryption this way.
In my case I am waiting for an update hopefully solving this issue as Encryption is a mandatory feature to me.

hamzaalijoiyah said:
Hi Everyone..... Hope you are all doing Great....
Today I wanted to get my hands on Paranoid Android on my MOTO G (XT1032). I flashed the build - - 5.1-- (File a_falcon-5.1-20150704.zip), everything went fine but my phone couldn't start and after 'Android is upgrading' screen it displayed a message 'Android is Locked enter password to unlock your Phone', and initial setup couldn't begun. I tried fofmatting everything (which I already had done) and re-flashed PA but in vain. Please if someone can provide help.
I also tried flashing without GApps but it still didn't work
I was previously using FLEX OS Android 5.1.1. After this experience with PA I flashed EUPHORIA OS (5.1.1) and Resurrection Remix(5.1.1), both worked like charm.
I really wanna try Paranoid Android, so please help me out as I am just a simple user not an Android geek.....
Regards.
Click to expand...
Click to collapse
Same problem here, I've tried to find any light on this issue but so far your post is the only thing that matches my situation.
Edit: I tried with the previous version of Paranoid (pa_falcon-5.1-20150619) and it is working now.

LuisPachon said:
Edit: I tried with the previous version of Paranoid (pa_falcon-5.1-20150619) and it is working now.
Click to expand...
Click to collapse
Good to know. I might try this version as well, hoping the encryption will work here. :fingers-crossed:

THANK YOU!!!
LuisPachon said:
Same problem here, I've tried to find any light on this issue but so far your post is the only thing that matches my situation.
Edit: I tried with the previous version of Paranoid (pa_falcon-5.1-20150619) and it is working now.
Click to expand...
Click to collapse
Whoa!! u have saved my day !! well I did that update lost all my data and bricked my phone , well after seeing your post now will take the new update and try it
thanks a ton mate !!

timeo78 said:
Good to know. I might try this version as well, hoping the encryption will work here. :fingers-crossed:
Click to expand...
Click to collapse
Encryption working fine with pa_falcon-5.1-20150822. However OTA updates are not working here. I might try with an OTG cable later and let you know the result.

timeo78 said:
Encryption working fine with pa_falcon-5.1-20150822. However OTA updates are not working here. I might try with an OTG cable later and let you know the result.
Click to expand...
Click to collapse
Update via OTG cable working fine. It seems there is no update issue by encrypted data partitions this way.

Porting LineageOS 14 to the d710

Disclaimer: I am not a ROM developer. I am a developer and Linux user, but I know next to nothing about creating Android ROMs. Whole other world to me.
I'm wondering if all three of us Epic 4G Touch users left might be able to get a working port of LineageOS 14 on our aging handsets.
The good news:
I just loaded the Official LineageOS 14 for i9100 20170419 nightly on my d710, and IT WORKS
...almost.
The bad news:
The ROM boots up, everything works and looks normal except for:
Wi-Fi - Settings app spins with message "Turning Wi-Fi on..."
Menu Button
Home Button
Now, I'm wondering if there is a way to fix these problems. I prefer on-screen navigation anyway, so that's probably an easy "fix." But Wi-Fi will probably be trickier. I assume it's kernel related, but I can't find any Nougat kernels for this device, so that will likely be the most difficult part.
Thoughts? Anyone else out there have any input or want to give this a crack?
Links:
https://wiki.lineageos.org/devices/i9100/build
https://wiki.lineageos.org/devices/i9100/install
https://web-beta.archive.org/web/20161224202958/https://wiki.cyanogenmod.org/w/Build_for_d710
https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0
https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig
https://github.com/Lanchon/TWRP-Patcher-SGS2
https://github.com/Lanchon/REPIT
https://forum.xda-developers.com/ep.../rom-cyanogenmod-11-official-nightly-t2852074

Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one

svaethier said:
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
Click to expand...
Click to collapse
Link is in the OP. Here it is again: https://forum.xda-developers.com/galaxy-s2/general/rom-t3555834
Direct link to the download page: https://download.lineageos.org/i9100

How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly

svaethier said:
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
Click to expand...
Click to collapse
I don't know what you're talking about. I don't get an error.
The ROM flashes without modification. Make sure you have an up-to-date TWRP with the i9100 crossflash patch: https://github.com/Lanchon/TWRP-Patcher-SGS2

Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation

svaethier said:
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
Click to expand...
Click to collapse
I followed lots of advice from this thread: https://forum.xda-developers.com/epic-4g-touch/help/help-getting-stock-rooted-4-1-2-to-cm11-t3384832
I believe the method that finally worked for me was: Odin to EL29 rooted, Philz recovery, TWRP, CM11.
That's where I was before I tried the i9100 LOS 14.1 ROM.

I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it

svaethier said:
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
Click to expand...
Click to collapse
If you have root in CM11, you can use Flashify to flash the new TWRP .img file.

My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.

flamadiddle said:
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
Click to expand...
Click to collapse
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.

flamadiddle said:
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
Click to expand...
Click to collapse
I'll reach out to some developer associates and see what I can find out about the WiFi.
Sent from my SM-S903VL using Tapatalk

I'm not a developer, but I have a D710 lying around and I am willing to do testing if you need me

I also have an Epic 4g touch that im willing to test stuff

So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.

chrismin13 said:
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
Click to expand...
Click to collapse
Never had any real interest, and I don't know enough to do it myself.

flamadiddle said:
Never had any real interest, and I don't know enough to do it myself.
Click to expand...
Click to collapse
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make it work for our device, because why not!
Thanks for still responding after so many months!

chrismin13 said:
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make a for for our device, because why not!
Thanks for still responding after so many months!
Click to expand...
Click to collapse
Those were the only two things I noticed. Bluetooth worked. I didn't see any apps crash (but I couldn't load new ones because no wifi). I didn't try cell service because I don't even have Sprint anymore, but I suspect that probably didn't work for the same reason wifi was killed.
Thanks for looking into this! I'm still interested if we can find a way to make it work. I just don't know much about creating ROMs. I'm not an Android dev.

Lineage 15.1 build?

Is anyone trying to build lineage 15.1 for this device? I have been trying unsuccessfully for two months. I have gotten as far as like 30%. I changed a few lines here and there and got it to build a kernel but, after it builds the kernel it runs into sepolicy errors. I'm making progress but I was wondering if anyone else was trying and had knowledge we might could swap? I'm not a full fledged developer but I have made progress.

You could ask for help from previous mainteiners of this device.

https://forum.xda-developers.com/ga.../rom-octos-t3532529/post75186090#post75186090 the reply on this post said he will maintain the device he was on octos team .you can ask him for help, hope he can
https://forum.xda-developers.com/member.php?u=6264948 his page

I don't think we will ever get 15.1. Last time I checked the kernel change, it's huge. Almost you need to rewrite everything... Can't use the old stuff. To be honest, it's not hard to port a rom. You can learn it to do it yourself in probably a day. But to build a kernel, it will take a team plus many months. It's not a one man's job. Most of the kernel developers here are taking a similar device as a base and port new functions or changes. Unless we can get a similar base, I don't think we will get a kernel works for 15.1.

It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of

I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.

Joker1716 said:
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
Click to expand...
Click to collapse
you can do it bro :good::victory:

Still encountering errors but I've gotten it to 75% or better. Still trying

Joker1716 said:
Still encountering errors but I've gotten it to 75% or better. Still trying
Click to expand...
Click to collapse
Awesome, bro
Sent from my Samsung SM-A520W using XDA Labs

Joker1716 said:
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
Click to expand...
Click to collapse
Good luck to you. What's your base?

I've gotten all the way through the build basically. But I keep getting a recovery partition size too large error. I am trying to work it out. Not very successfully but I am still trying. I have devoted all of my free time into trying to get this done. Hopefully it's worth it. Even if it builds the Ota zip, it may still not even boot. But I am dedicated to attempting to make this happen.

I finished still gotta try to flash it. About to pass out no sleep in a while.

Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.

Joker1716 said:
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
Click to expand...
Click to collapse
Awesome! Glad someone is doing this for us!

Don't give up bro! And try to ask for some help.

I managed to compile the recovery it's still a little iffy but it does flash and factory reset. dirty flashing works but if you factory reset first it deletes everything and does not mount to the usb to the computer. It also does not match the assert right. what i did was unzip the d2att rom.zip , delete the assert line on the META-INF/com/google/updater-script, and re-zip to get it to flash. It did flash. haven't tried with a SD card yet. So it's not where it needs to be just yet. If you plan on messing with this recovery it will flash in TWRP under install/install image the lineage recovery will not flash an image so make sure you know how to flash one in odin, and have everything ready if you plan on going back to a different recovery. The rom i built with it flashes tries to boot up led light pulses like 7 times and then goes into download mode . Making progress but I'm going to be taking a break for a few days. AYOR I assume no responsibilty for whatever you may do to your device with this file. if you dont know what you are doing dont mess with it if you do its At Your Own Risk . Enjoy.
if anyone wants to check it out here is the download link
#Recovery
https://www.androidfilehost.com/?fid=11410932744536990805

Truly appreciate the amount of time, effort, and sleeplessness you have put into and endured for this development! :angel:

Can you not use twrp?

ibuddler said:
Good luck to you. What's your base?
Click to expand...
Click to collapse
Not really sure if I understand the question. I'm using the d2att device tree. Msm8960 board, krait architecture. I built for the klte (krait, Msm8974) which is very similar so I could see how everything goes down then compare, make changes, and wait an extremely long time for the build to compile. My computer is old. I run into .jackserver problems like there's no tomorrow. I am a landscaper I cut grass. build walls, lay sod, plans flowers,trees, dig up flowers,trees, etc. That being said I am a tad out of my element but I started doing android developmental things on my s2 and have not stopped sometimes I think smoking crack would be easier but I kinda enjoy this type of stuff. Just basically saying I have no clue what I'm doing in technical terms but I can read compare and research and maybe get something accomplished

iloveoreos said:
Can you not use twrp?
Click to expand...
Click to collapse
Yeah I can use TWRP.?? I can use what I have build a new one etc. But I'm trying to build 15.1 for the d2att and lineage recovery is included in the build