Develop Bugs

Working pdroid patches [currently AOKP(toro+maguro), stock AOSP, cm9]

I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.

Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions

Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.

Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.

I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.

deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.

Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.

IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.

I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!

i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?

SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.

xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium

JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.

robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.

Can you make a patch for stock root.
Thx

Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.

soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.

Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!

[4.4] CyanogenMod 11 nightlies

They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.

Flash with stock recovery?
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx

dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
You will not be able to flash this with the stock recovery. I imagine once it goes stable CM will push out an official update that will work on the stock recovery setup.
Until then, TWRP works great: http://forum.xda-developers.com/showthread.php?t=2537080

dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.

Harfainx said:
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Click to expand...
Click to collapse
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.

mcteague said:
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
Click to expand...
Click to collapse
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk

Harfainx said:
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.

Entropy512 said:
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Click to expand...
Click to collapse
Correct. Currently since they're coming direct from CM as nightlies, they aren't final stable versions. Those will be released like the other two were, and I'm sure will be built to flash in the N1 Stock Recovery.

Location not working
location still not working on latest nightly (130214).
anyone has any idea on how to fix it? the 240114 nightly is not longer on the getCM servers.

Anyone on M6? Thoughts?
I went straight from CM10.2 (CM edition N1) to 11 M6, so I don't know how battery life compares with Omni or other ROMs... would love to hear from those of you that have tried other ROMs and can compare with M6.
With M6, I am getting ~4% battery drain over 7 hours overnight (2G network on only).

All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Hi,
I am trying to install Cyanogend mod. N1 a OPPO
The steps are simple, but not working,
I've tried: (http://download.cyanogenmod.com/?device=n1&type=snapshot)
** Cm-11-20140804-SNAPSHOT-M9-n1
cm-11-20140805-NIGHTLY-N1
cm-11-20140124-EXPERIMENTAL-n1.zip
They all show the same error.
"Installation failed"
I downloaded the. zip for wifi, ethernet MAC, WINDOWS ........ and still shows the same error.
:crying:

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Sorry to bump a 3 year old thread for such an unrelated reason, but you have PMs disabled, and, well, CM11 is not that appealing anymore so I'm confident not many people are gonna read this anyway [any mods reading this, please spare my soul :silly: ]
That said, I just wanted to ask you why you rated my porting of LAOS 15 Trebuchet so poorly, since you didn't leave any comment; if it's some bug, crash or other error i can look into it.
BTW you can answer me on the app's thread if you wish (https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436)

ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Thank you for leaving your feedback, here are some answers to your points:
- (update mechanism) i actually caught a nasty bug in XDA Labs web console which prevents me from uploading new builds there (and I also deleted all previous reviews in the attempt to reupload the app ??); (i already filed a bug report and managed to get the dev's attention so I hope it gets fixed soon)
- (open source) being a porting, the app mostly shares the original staging/trebuchet15.1 source code, with only a handful edits for fixing crashes due to compatibility errors (and is built with gradle plugin 2.3.3 instead of 3.0.1)
- (very buggy) it inherits all current staging/trebuchet15.1 bugs, not that much from my tests, but yes, there are some

[Q&A] [ROM] [Alpha] Unoffcial CM12 for d2tmo

Q&A for [ROM] [Alpha] Unoffcial CM12 for d2tmo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Alpha] Unoffcial CM12 for d2tmo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

CM12 for D2tmo
i installed CM12 but it does not detect my simcard PLZ help

Cant wait for new Lollipop roms!!!

Do you know if any time soon there will be a fix for mobile data?
thanks for effort

menace211 said:
Cant wait for new Lollipop roms!!!
Click to expand...
Click to collapse
Yeah, if they turn out like KitKat Roms I'm heading back to touchwiz jellybean, stock.

Liquidsmooth lollipop for S3
Hi,
Here are some builds for the S3, including the d2tmo. I've loaded the but had to go back to backup , there is a bug (black screen) with lollipop that i could not stay with it.
Sorry .. they did not allow me to put in the message an outside link to the downloads
Adam

fully functional work around to get lollipop on s3 d2tmo t999l
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
important things that do work :
4g YES
bluetooth with android wear YES
gps YES
camera for android YES( stock camera NO google camera NO)
wifi YES
flash light YES
time needs to be adjusted(settings > date & time > check atumatic date & time (use network-provided time) uncheck automatic time zone, select time zone to finish time set)
sound YES
dsp YES
security YES unlocks only with power button (home button will not unlock your phone takes some getting use to)
keyboard YES
what was used to set up my phone: philz recovery, rescripted 12-20141125-UNOFFICIAL-d2att, superSU beta app,gapps 5.0, latest modem from xda for d2tmo t999L

leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Is it possible that you could upload d2att rom with changed script?

leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
Click to expand...
Click to collapse
Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
it looks like the file is too big to upload, here are the steps to edit the file manually, if you follow these you wont screw up
1. open the file in total comander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isnt
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU

Wiwee said:
Is it possible that you could upload d2att rom with changed script?
Click to expand...
Click to collapse
files not uploading still sorry

leonid002 said:
files not uploading still sorry
Click to expand...
Click to collapse
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.

PHP:
alarmdude9 said:
I have determined I am an idiot. I downloaded the rom and tried to change the stuff you have listed and no love. If you have a chance to get it uploaded ( mega.co.nz with a public link maybe.....) please share would love to give it a shot.
Click to expand...
Click to collapse
I'll get right on it thanks for the response,did it not let you flash it and say it's not compatible?

leonid002 said:
PHP:
I'll get right on it thanks for the response
Click to expand...
Click to collapse
No thank you for trying to help idiots like me. that is correct says not compatable

alarmdude9 said:
No thank you for trying to help idiots like me.
Click to expand...
Click to collapse
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference

leonid002 said:
I got it to work at 3 in the morning so if I forgot something I'm sorry in advanced it's halfway uploaded right now with the changes in the script. Hope this helps. I also flashed with Philz recovery if that makes any difference
Click to expand...
Click to collapse
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along

leonid002 said:
after doing a lot of research i have sucsesfully installed lollipop onto my s3 and got the camera to work with the camera for android app from the play store. the data also works the build i installed is the 12-20141125-unofficial-d2att after changing the script file to include d2tmo instead of the d2att. works great no real bugs except the time stamp on hangout mesages which is fixed by setting the time on the phone to network but turning of the reginal time set. thought this would be nice to share.
ps: stock camera and google camera still do not work but everything else does so this can be used as a daily driver links below to camera and build:
camera: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
build: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Added screen shots of apps used speed test and the edit that needs to be made to script file to make installable
lollipop for d2tmo install instructions
WHAT YOU NEED
the build location:
12-20141125-unofficial-d2att link: http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
in the same link is superSU
also will need gapps 5.0 lollipop
"camera for android" ( stock camera and google camera DOES NOT work)
link: https://play.google.com/store/apps/details?id=com.photo.android.camera&hl=en
total commander
instructions to exit the updater-script file to make the build installable on your d2tmo
1. open the file in total commander
2. META-INF> COM>GOOGLE>ANDROID
3. open and edit the updater-script by long pressing the file choosing unpack+edit
4. change d2att to d2tmo in the first line P.s. theres two words change both
5. go back and the editing is done now just wipe everything and flash just like any other rom the boot up takes about 8 to 9mins so dont worry about it being stuck in a loop, it isn't
do not forget to download superSU from the same link as the build and have gapps 5.0 when you flash
flash in this order: rom, gapps, superSU
Click to expand...
Click to collapse
alarmdude9 said:
No apologies needed at all. Don't know if one version of the recovery matters or not. I know it did way back in the days of the CLIQ but I'm hoping not this far along
Click to expand...
Click to collapse
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited

leonid002 said:
https://mega.co.nz/#!8wdyVICK!ORYZsTOTdnXvgpEYVA6mJr9JbQJ0MCz_wFh8sA_xPNk
Try this I checked the file to make sure it was edited
Click to expand...
Click to collapse
awesome bringing it down now.

alarmdude9 said:
awesome bringing it down now.
Click to expand...
Click to collapse
so when you flash there should be a small error but it will continue flashing. let me know it goes

leonid002 said:
so when you flash there should be a small error but it will continue flashing. let me know it goes
Click to expand...
Click to collapse
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.

alarmdude9 said:
Will do. Besides the camera everything else is working? Can't test it a lot tonight, just got called into work, but want to get it set up and a nandroid then play with it after work tomorrow.
Click to expand...
Click to collapse
when I first flashed the time for some reason was off but its pretty easy to fix, as for the camera install camera for android in the play store so you have some kind of working camera if that matters to you . everything else works perfectly a lot faster than the carbon ROM I had

[ROM][LineageOS 13][Marshmallow][6.0.1][MOB31K][Mar.18.2017][XT907][JBBL][Share]

Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here

Updated to 03.25.2016 build

Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?

Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues

Updated to April 02, 2016 build!

I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?

Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?

bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!

KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?

crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL

rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.

One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...

Would you mind adding dates to post #1?

Any updatefor this rom?

crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!

Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?

crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.

Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.

I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app

Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?

E980 Modem / Baseband Saga, Consolidated. (Paging MadMack/devs?)

I've spent a bunch of time trying to understand why the modem in a particular E980 doesn't work in Cyanogenmod 12. Others should benefit from my efforts.
Searching reveals several posts about the modem issue, but quite a few of the responses are either links or references that require significant background to understand.
The community consensus is that one must flash "madmack's modem" when using CM with the E980 & variants. Without it, many phones can't enter deep sleep and thus drain the battery. Others can't use the modem at all.
(Madmack's modem post: https://forum.xda-developers.com/showthread.php?t=2430456)
(Current source of CyanogenMod 12.1: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html)
"Madmack's modem" is the image for the BM9615A-CEFWMAZM-3.0.113012. Some users had a driver for a CM9615A[...] variant instead. For those users, flashing the BM9615A driver allowed the phone to go into deep sleep. Hooray!
---
Unfortunately, other E980 owners have a completely different modem: the APQ8064/MDM 9x15M. In this case, flashing the BM9615A file doesn't help.
If your modem appeared as an APQ8064/MDM9x15M on stock, it appears as the BM9615A upon flashing CM12. Unfortunately, its still an APQ8064 on the inside. This makes it seem like CM 12.1 is hard-coded to the BM9615A modem. When CM tries to speak BM9615A-ese to an APQ8064, the result is "No Sim" (or rather intermittently detecting and dropping the SIM).
Flashing the BM9615A image on an APQ8064 doesn't help -- the modem can't understand itself. CM and the modem firmware may speak the same language, but the image that runs the modem isn't right for the hardware.
At least, thats what I think is happening. I would appreciate it if someone with experience could please let me know if my understanding is incorrect.
Until someone finds a way around this, those people whose modem is APQ8064/MDM9x15M on stock may want to hold off on trying the available roms. Most are based on CyanogenMod and thus can be expected to have the same problem.
I wrote this post both to consolidate information and to ask for help. Does anyone have a way of getting an E980 with a APQ8064/MDM9x15M to work with CM 12.1?
(Note: Tried Emmanuel's wild kernel. Didn't help.)

No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.

ShadySquirrel said:
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
Click to expand...
Click to collapse
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?

facepalm5 said:
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
Click to expand...
Click to collapse
Which CM build are you trying to use?

ShadySquirrel said:
Which CM build are you trying to use?
Click to expand...
Click to collapse
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html

facepalm5 said:
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
Click to expand...
Click to collapse
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.

ShadySquirrel said:
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
Click to expand...
Click to collapse
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.

facepalm5 said:
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
Click to expand...
Click to collapse
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.

Intended a direct reply. See below.

ShadySquirrel said:
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Click to expand...
Click to collapse
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.

facepalm5 said:
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
Click to expand...
Click to collapse
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.

ShadySquirrel said:
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
Click to expand...
Click to collapse
Thanks. I'll give it a try, but let me make sure that I understand which one. There are two mirrors on the EOL thread: basketbuild & androidfilehost.
The newest build on basketbuild is 02072016. Androidfilehost has a 021816, however there is a note in the EOL thread that 021916 shouls be deleted because it doesn't work. Is that the same as 021816 or is 021616 really the same as 021616?

Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.

ShadySquirrel said:
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
Click to expand...
Click to collapse
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?

facepalm5 said:
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
Click to expand...
Click to collapse
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.

ShadySquirrel said:
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
Click to expand...
Click to collapse
I can confirm the builds he has uploaded work for me, including the kernel fix for LMK which he posted this past year. ROM runs great