[DEV] Lineage OS for Oppo F1 (f1f)

[DEV] Lineage OS for Oppo F1 (f1f) - Oppo F1

Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC « magic » registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this…

kdd998 said:
Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC � magic � registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this�
Click to expand...
Click to collapse
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).

Try this op2 also has backlight issue in custom rom.
Group Butler [beta]:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git?
Click to expand...
Click to collapse
Yes, the msm8939 kernel common to Oppo devices.
MiniBlu said:
Did you have to make any changes to the kernel source?
Click to expand...
Click to collapse
Yes, changes are necessary. I didn't have a look at audio yet, but the touchscreen driver needs changes, dtsi files to clear warnings and the lm3630 driver needs a lot of changes to make the probe work.
MiniBlu said:
CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb).
Click to expand...
Click to collapse
Yes, but with cm-14.1, there's a big gap in the kernel source. It seems to be nearer the CAF source and all the ugly Oppo ifdefs are out (seriously, Oppo's coding style is awful ).
MiniBlu said:
Also, does rotation work, I have been having problems using their sources with accelerometer.
Click to expand...
Click to collapse
I'll try to see if rotation is OK but I have doubts. I didn't have a look at it yet. Which device is it?
Ucihaflash said:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
Click to expand...
Click to collapse
Thanks for the tip, I'll have a look, but I find it strange that this device is in the leds class, I thaught it was in the backlight class. It needs to be tried anyway

So, rotation doesn't work. But button-backlight is there, but I cannot control backlight. I'll continue digging…

Wow u actually been able to put cm14 on oppo f1. C
When you finish this will you make it public? Many people would love this

Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.

Thanks so much. Good luck with cm14. Hope u succeed! ?

verry happy to see that, good luck thank's:good::good::good::good::good::good:

kddoran said:
verry happy to see that, good luck thank's:good::good::good::good::good::good:
Click to expand...
Click to collapse
- 6months latter
........... . .when you guys realize that Oppo has the worst vendor ive ever seen on the planet, bad,slowest(never)get update at all..

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).
Click to expand...
Click to collapse
Which sources did you use to build? Last time I tried compiling from the official sources I got some errors building the kernel so I gave up but that was a while ago.

As an Oppo f1 user, good luck to your project since oppo never update its thing

kdd998 said:
Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.
Click to expand...
Click to collapse
Is there a hope for getting officially build on CM

i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?

Jamie_oppo said:
i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?
Click to expand...
Click to collapse
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.

Thanks so much. I will try this as soon as I can. If something goes wrong after fastboot boot the twrp image will I still have fastboot just in case??

MiniBlu said:
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.
Click to expand...
Click to collapse
i extacted all the files and put twrp and the magictricks thing in the fastboot folder
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin These all worked fine
but when i got to reserve4 i got C:\Users\ponyd\Desktop\back to colour os>fastboot flash reserve4 reserve4.img
target reported max download size of 268435456 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.200s]
writing 'reserve4'...
FAILED (remote: size too large)
finished. total time: 0.216s
i shat my self when that happened? i then flashed the boot.img logo and modem of project spectrum and went back to spectrum. DId i do something wrong?

Backlight fix
Try coloros setting app. Search and u will get it.

I'm actually under spectrum project hope you could port this cm14.1 for OPPO f1...
Thanks

I know this may be abit reluctance but you may want to open source the project on what you have now and list what is working and what's isn't, and I'm sure people will contribute to the project given that is qcom there should not be much of an issue to get it working.

Related

[Q] Bricked my device

It's fair to say I'm an idiot. I couldn't update my OPO to XNPH30O, so I thought it was a good idea to reboot the recovery (TWRP) and reset my device. I clicked on advance and checked all the boxes, including system... So as dumb as I was I didn't know what it meant, so accidentally I erased my operating system. Now I don't know what to do. Could somebody please help me. I already tried this, but I received an error: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

pronkjuweel said:
It's fair to say I'm an idiot. I couldn't update my OPO to XNPH30O, so I thought it was a good idea to reboot the recovery (TWRP) and reset my device. I clicked on advance and checked all the boxes, including system... So as dumb as I was I didn't know what it meant, so accidentally I erased my operating system. Now I don't know what to do. Could somebody please help me. I already tried this, but I received an error: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
Goto android development and download any rom mahdi or calkulins and perform full wipe from twrp and flash it...if that didnt bootnurbdevice foral a reason or other u have to flash stock using fastboot,
Try and lets see

Nickthegr8 said:
Goto android development and download any rom mahdi or calkulins and perform full wipe from twrp and flash it...if that didnt bootnurbdevice foral a reason or other u have to flash stock using fastboot,
Try and lets see
Click to expand...
Click to collapse
That's exactly what I did: [GUIDE] Return your OPO to 100% Stock (Current Build - XNPH30O) , but it failed as I showed above.

What is the step that you want to achieve? Stock ROM? Custom ROM?
If you're able to get into fastboot and recovery mode, your device is not bricked

If you have fastboot or can access your recovery your fine. You have wiped your complete phone so you will need to sideload an appropriate ROM or put it onto a USB stick and use USB to loaf ROM from twrp

zephiK said:
What is the step that you want to achieve? Stock ROM? Custom ROM?
If you're able to get into fastboot and recovery mode, your device is not bricked
Click to expand...
Click to collapse
I want stock ROM.
nathlynn22 said:
If you have fastboot or can access your recovery your fine. You have wiped your complete phone so you will need to sideload an appropriate ROM or put it onto a USB stick and use USB to loaf ROM from twrp
Click to expand...
Click to collapse
I can access my fastboot and my recovery (TWRP). How do you sideload an appropriate ROM or put it onto a USB stick and use USB to load ROM from twrp?
Thank you both for your help

pronkjuweel said:
I want stock ROM.
I can access my fastboot and my recovery (TWRP). How do you sideload an appropriate ROM or put it onto a USB stick and use USB to load ROM from twrp?
Thank you both for your help
Click to expand...
Click to collapse
Just browsing the forums don't have a OPO but its all the same with twrp if you have a USB otg cable put the stock ROM you want which you will find in development put that onto the USB stick then connect USB stick to otg cable then install through twrp. Or of you can't do that search on google how to sideload an app using twrp and you will find your answer and flash it that way

nathlynn22 said:
Just browsing the forums don't have a OPO but its all the same with twrp if you have a USB otg cable put the stock ROM you want which you will find in development put that onto the USB stick then connect USB stick to otg cable then install through twrp. Or of you can't do that search on google how to sideload an app using twrp and you will find your answer and flash it that way
Click to expand...
Click to collapse
Do you know which one of these two version I need to download?
cm-11.0-XNPH30O-bacon-signed-fastboot.zip
or
cm-11.0-XNPH30O-bacon-boot-debuggable.img

pronkjuweel said:
Do you know which one of these two version I need to download?
cm-11.0-XNPH30O-bacon-signed-fastboot.zip
or
cm-11.0-XNPH30O-bacon-boot-debuggable.img
Click to expand...
Click to collapse
Your best bet is asking @zephiK that as I'm pretty sure he has the phone so he could help better there.

pronkjuweel said:
Do you know which one of these two version I need to download?
cm-11.0-XNPH30O-bacon-signed-fastboot.zip
or
cm-11.0-XNPH30O-bacon-boot-debuggable.img
Click to expand...
Click to collapse
fastboot.zip

zephiK said:
fastboot.zip
Click to expand...
Click to collapse
I downloaded the file, how do I put in on my phone?

pronkjuweel said:
I downloaded the file, how do I put in on my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Follow the instructions under "Instructions." You'll need fastboot environment set up.. http://forum.xda-developers.com/showthread.php?t=2788632

zephiK said:
http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Follow the instructions under "Instructions." You'll need fastboot environment set up.. http://forum.xda-developers.com/showthread.php?t=2788632
Click to expand...
Click to collapse
I downloaded the file from the site and followed the instructions, all the steps worked, expect the last one:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH30O-bacon-signed-fastboot.zip
There isn't such an file when I unpack the zip.And if you checked out the attachment on my original post you see that I got an error with this method? Any idea how to fix that? thanks alot.

Had the same weird boot.sig error when following the CM11s guide too. It seems the last command didn't want to work for me either. Here's how to fix it:
Get the CM11s zip and extract the contents. Stick the OPO into fast boot mode and open your command line.
Then do each command manually (copy/paste):
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
Source: http://forum.xda-developers.com/showthread.php?t=2770535
That should get you back up and running.

kinghu said:
Had the same weird boot.sig error when following the CM11s guide too. It seems the last command didn't want to work for me either. Here's how to fix it:
Get the CM11s zip and extract the contents. Stick the OPO into fast boot mode and open your command line.
Then do each command manually (copy/paste):
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
Source: http://forum.xda-developers.com/showthread.php?t=2770535
That should get you back up and running.
Click to expand...
Click to collapse
Thank you man! It worked. The rest of you who helped my out also thanks.

Now that's what I like seeing. People helping others. Great job guys

Flickering Stripes on Dispaly - OnePlus supplies patch

Hi there!
EDIT2: WARNING! ONLY FOR 64GB INTERNATIONAL EDITION
Seems some people are having the same problem as me and are facing some screen issues. Mostly occuring as colorful or black flickering stripes along the display.
I contacted OnePlus support and they gave me a link to a patch.
I'm currently trying to figure out, what this patch is really doing and maybe just extract the patched part, as their batch files do (unlock oem locking, flashing, oem locking) wipe the phone.
If anyone is interested aswell,. here's the link they provided:
https://account.onepluscontent.com/downloads/tools/oneplus-one-reflash.zip
Edit: Content of the batch files:
ONEPLUS ONE - 0.bat
@echo off
fastboot devices
pause
Click to expand...
Click to collapse
ONEPLUS ONE - 1.bat
@echo off
fastboot oem unlock
fastboot reboot-bootloader
sleep 5
Click to expand...
Click to collapse
ONEPLUS ONE - 2.bat
@echo off
echo ######### This patch is Created by ONEPLUS Technical Support. #######
echo ###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ######
@echo off
fastboot oem unlock
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot oem lock
fastboot reboot
echo It is done Now
pause
Click to expand...
Click to collapse
Anyone care matching the md5 sums of the img files or something to identify the ones with changes?
Maybe we can flash this without wiping...

Hi there.
This looks just like a complete factory reset to me. Its probably the same zip OnePlus provided to "fix" a GPS problem.
I don't think that there are really any relevant changes in this images, it is probably just a hard factory reset. In addition it even erases the whole phone including sd-partition and unlocks the bootloader, for whatever reason, so be warned.
I had the problems with the black flickering "lines" as well, I solved it by disabling hardware overlays in the developer options.
Just realized, that they relock the bootloader again in the last batch. Ts.

microserf said:
Hi there.
This looks just like a complete factory reset to me. Its probably the same zip OnePlus provided to "fix" a GPS problem.
I don't think that there are really any relevant changes in this images, it is probably just a hard factory reset. In addition it even erases the whole phone including sd-partition and unlocks the bootloader, for whatever reason, so be warned.
I had the problems with the black flickering "lines" as well, I solved it by disabling hardware overlays in the developer options.
Click to expand...
Click to collapse
Yep, I was suspecting something like this.
Anyone having the time to verify that the images are just the current ones?
Have been playing around with different kernels and disabling the HW overlays. But I'm not really happy, with this workaround - although the phone seems more smooth (which is quite odd in my opinion)

aliander said:
Yep, I was suspecting something like this.
Anyone having the time to verify that the images are just the current ones?
Have been playing around with different kernels and disabling the HW overlays. But I'm not really happy, with this workaround - although the phone seems more smooth (which is quite odd in my opinion)
Click to expand...
Click to collapse
Yeah, it is more a workaround than a fix. But I was kinda relieved that its software related and not a broken digitizer or something. Problem started to occur on 38R with stock and different revisions of Franco Kernel. Before that it was all fine.
There is also a bugreport in the cyanogenmod jira about this issue, so for now I am living with the workaround and will probably wait for the Lollipop Update.

Yea this is just a factory recovery image they provided. Saw this was posted as a "FIX" for other issues on the OnePlus forums as well. Seems like a very generic solution from OnePlus tbh, and i dont know if it actually fixes anything., looks more like their playing for time...

S M G said:
Yea this is just a factory recovery image they provided. Saw this was posted as a "FIX" for other issues on the OnePlus forums as well. Seems like a very generic solution from OnePlus tbh, and i dont know if it actually fixes anything., looks more like their playing for time...
Click to expand...
Click to collapse
Yeah seems so.
Thanks

So I downloaded a fastboot factory image version R38
MD5 Results:
Code:
$ md5sum.exe ONEPLUS\ ONE-Patch/*.img
46276588ab8cb0e2b68a813012c5c332 *ONEPLUS ONE-Patch/boot.img
eb6bf677953fd446d16336f627e28f24 *ONEPLUS ONE-Patch/cache.img
7800fb3768c5a5f310c3b6bc443e4f72 *ONEPLUS ONE-Patch/persist.img
3b0dba90ea6ecdf27a201cb16af940b8 *ONEPLUS ONE-Patch/recovery.img
2c72217c90be4175c9e9092929839bfd *ONEPLUS ONE-Patch/reserve4.img
732ef3ce979960be5eb225bad14d4e80 *ONEPLUS ONE-Patch/system.img
9cd750b19b7c30c640647b6f0df8f6b4 *ONEPLUS ONE-Patch/userdata.img
07b9774134f26f72ea7e73e580b19c17 *ONEPLUS ONE-Patch/userdata_64G.img
Code:
$ md5sum.exe cm-11.0-XNPH38R-bacon-signed-fastboot/*.img
46276588ab8cb0e2b68a813012c5c332 *cm-11.0-XNPH38R-bacon-signed-fastboot/boot.img
eb6bf677953fd446d16336f627e28f24 *cm-11.0-XNPH38R-bacon-signed-fastboot/cache.img
3b0dba90ea6ecdf27a201cb16af940b8 *cm-11.0-XNPH38R-bacon-signed-fastboot/recovery.img
732ef3ce979960be5eb225bad14d4e80 *cm-11.0-XNPH38R-bacon-signed-fastboot/system.img
9cd750b19b7c30c640647b6f0df8f6b4 *cm-11.0-XNPH38R-bacon-signed-fastboot/userdata.img
07b9774134f26f72ea7e73e580b19c17 *cm-11.0-XNPH38R-bacon-signed-fastboot/userdata_64G.img
Seems everything is identical, but reserve4.img and persist.img missing in factory image.

[Mega Thread] Smartfren Andromax Q

Introduction:
Smartfren Andromax Q is the fourth device with official Cyanogen OS support.
http://www.xda-developers.com/xda-external-link/andromax-q-is-a-new-cyanogen-device-in-indonesia/
https://cyngn.com/blog/cyanogen-comes-to-indonesia-with-smartfren
http://www.smartfren.com/id/andromax-q/
Specification:
http://bestmobs.com/smartfren-andromax-q/
Device Codename:
"rendang": https://en.wikipedia.org/wiki/Rendang
Stock ROM:
Take a look in @Spannaa's thread in OnePlus One section to get a clear idea about signed fastboot zips, signed zips, boot-debuggable images and OTA incremental update zips. Cyanogen does provide stock factory package for this device (from 2015/09/04), but I'm able to scrap the all of the links using my tool.
Build 2015-11-11 (cm-12.1-YOG4PAS42M):
http://builds.cyngn.com/cyanogen-os...PAS42M-rendang-signed-fastboot-ae9f129c55.zip
http://builds.cyngn.com/cyanogen-os...rendang-signed-fastboot-ae9f129c55.zip.md5sum
http://builds.cyngn.com/cyanogen-os...12.1-YOG4PAS42M-rendang-signed-258d4e132b.zip
http://builds.cyngn.com/cyanogen-os...G4PAS42M-rendang-signed-258d4e132b.zip.md5sum
http://builds.cyngn.com/cyanogen-os...PAS42M-rendang-boot-debuggable-407a3c9ad7.img
http://builds.cyngn.com/cyanogen-os...rendang-boot-debuggable-407a3c9ad7.img.md5sum
Click to expand...
Click to collapse
YOG4PAS2H2 to YOG4PAS42M: http://builds.cyngn.com/incremental/rendang/cm-rendang-86917f8d9b-to-c4e9f095bc-signed.zip
Build 2015-09-15 (cm-12.1-YOG4PAS2H2):
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS2H2-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YOG4PAS2H2-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...17f8d9b/cm-12.1-YOG4PAS2H2-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS2H2-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS2H2-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YOG4PAS2H2-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
YNG1TBS1ZM to YOG4PAS2H2: http://builds.cyngn.com/incremental/rendang/cm-rendang-41daeb34c5-to-86917f8d9b-signed.zip
Build 2015-08-17 (cm-12.1-YOG4PAS1P4):
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS1P4-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YOG4PAS1P4-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...726a317/cm-12.1-YOG4PAS1P4-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS1P4-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS1P4-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YOG4PAS1P4-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-06-19 (cm-12.0-YNG1TBS2XI):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS2XI-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS2XI-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...82ddb7d/cm-12.0-YNG1TBS2XI-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS2XI-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS2XI-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS2XI-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-05-16 (cm-12.0-YNG1TBS1ZM):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1ZM-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS1ZM-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...aeb34c5/cm-12.0-YNG1TBS1ZM-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS1ZM-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1ZM-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS1ZM-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-04-24 (cm-12.0-YNG1TBS1DM):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1DM-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS1DM-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...80facfc/cm-12.0-YNG1TBS1DM-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS1DM-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1DM-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS1DM-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Flash Stock Firmware:
Code:
fastboot -i 0x201E oem unlock #Unlocks the bootloader; skip if already unlocked
fastboot -i 0x201E flash aboot emmc_appsboot.mbn
fastboot -i 0x201E flash modem NON-HLOS.bin
fastboot -i 0x201E flash rpm rpm.mbn
fastboot -i 0x201E flash sbl1 sbl1.mbn
fastboot -i 0x201E flash tz tz.mbn
fastboot -i 0x201E flash hyp hyp.mbn
fastboot -i 0x201E flash boot boot.img
fastboot -i 0x201E flash cache cache.img
fastboot -i 0x201E flash system system.img
fastboot -i 0x201E flash recovery recovery.img
fastboot -i 0x201E flash userdata userdata.img
fastboot -i 0x201E oem lock #Locks the bootloader (optional)
Track OTA:
https://play.google.com/store/apps/details?id=com.arjanvlek.cyngnotainfo
Unbricking the device (flash using Qualcomm QLOADER mode):
http://www.needrom.com/download/smartfren-andromax-g36c1h-cyanogenmod/
Root:
1. Unlock the bootloader (fastboot -i 0x201E oem unlock).
2. Flash (fastboot -i 0x201E flash recovery XXX.img) or tethered-boot (fastboot -i 0x201E boot XXX.img) the latest Cyanogen recovery (replace XXX with the name of the Cyanogen recovery).
3. Flash or adb sideload the latest SuperSU zip.
CyanogenMod:
Being an official Cyanogen supported device, CyanogenMod is already available for it.
Link to latest nightly: https://download.cyanogenmod.org/get/rendang-latest.zip
Link to latest snapshot: https://download.cyanogenmod.org/get/rendang-snapshot.zip

[Reserved for future]
I don't have the device myself, so it would be better if some friends from Indonesia will help me out
1. Please post the device's hardware IDs of adb & fastboot interfaces. We may need them to whitelist the device for detection.
Got the device IDs:
ro.usb.vid=201E
ro.usb.id.charge=F006
ro.usb.id.mtp=2282
ro.usb.id.mtp_adb=2281
ro.usb.id.ptp=2284
ro.usb.id.ptp_adb=2283
ro.usb.id.ums=2286
ro.usb.id.ums_adb=2285
Click to expand...
Click to collapse
2. Post raw backup of 'aboot' partition before & after unlocking bootloader; we need them to add this device in this project.

Kernel Source: https://github.com/CyanogenMod/android_kernel_smartfren_msm8916
Device Tree: https://github.com/CyanogenMod/android_device_smartfren_rendang

I would like to post a screenshot but every time I press the picture button it said "xdamobile has stopped responding" and there are 2 buttons report and OK. The same problem with bbm app. Also happen on FB Lite app, when trying to post a pic in a reply, didn't complained if I tried to post a pic as an actual post. :banghead:
Wondering what's wrong. I already did 5 factory resets and 1 complete os reinstall.
https://www.dropbox.com/sh/1xp5ltlnek0t0je/AACTgldjQsCkKozAoXhGrcmOa?dl=0 pictures/screenshots of antutu benchmark results
http://www.needrom.com/download/smartfren-andromax-g36c1h-cyanogenmod/ link to download full 1.3gb rom
Sent from my Andromax G36C1H using XDA Free mobile app

try to install another gallery source

COS 12.1 is available! Updated first post.

hd.herlambang said:
try to install another gallery source
Click to expand...
Click to collapse
so I have to uninstall the gallery app in the phone and replace it with another gallery app? I don't understand.
question:
I've rooted my device using KingRoot. I was able to download the whole 429.4mb worth of "incremental update" yesterday BUT was not able to install the update. after I pressed the "install update" button, the phone rebooted, went into the picture of the green android robot having a spinning stuff in the stomach while wiggling the antennae (which sent my kids to burst laughing), then it kicked me into recovery mode. unfortunately I picked the highlighted option, which would be the most logical for me after applying an update, which is "reboot system now" instead of "apply update" or "power off". but when I got back in, the build number didn't change. and also I can't find the update again while doing "check system update". after 2 restarts, then phone will notify me that there's an update available. so I thought that I will just redo the update, but alas I can't find it anywhere in the phone/physical sdcard. there's nothing dated 10/2/2015 (october 2nd, 2015). then I started opening every single available viewable folder, and found that the folder /dev and most of its contents were dated 10/2/2015. and well, it seemed like that I have to waste another 500mb to redownload the whole updates again. although I'm not sure what went wrong.
should I unroot first? or should I reflash the whole phone first? can anyone give me any advice? thanks!

@bulukaki
It would be better to get the latest fastboot flashable package & do a clean flash.

@Titokhan
Build 2015-09-15 (cm-12.1-YOG4PAS2H2)
Build 2015-08-17 (cm-12.1-YOG4PAS1P4)
what was the differences between of them ? in addition to the built date.
why there were YNG1TBS1ZM to YOG4PAS2H2: http://builds.cyngn.com/incremental
whereas the latest CM12.0 is cm-12.0-YNG1TBS2XI ?
and there is no YNG1TBS2XI to YOG4PAS2H2.

@hd.herlambang
As Cyanogen doesn't publish any official changelogs, we've to depend of CyanogenMod changelogs: http://www.cmxlog.com/12.1/rendang/
Again, the incremental OTAs are tracked via Cyanogen's own API so it entirely depends on them.

Just bought this phone. Thanks for the thread.

I am trying to build cyanogenmod using the build guide for rendang. (can't include url)
There is some problem but i've past that. Now i meet another problem that i'm stuck.
Error after brunch rendang.
target thumb C++: libinputservice <= frameworks/base/libs/input/PointerController.cpp
target thumb C++: libinputservice <= frameworks/base/libs/input/SpriteController.cpp
target thumb C: libsuspend <= system/core/libsuspend/autosuspend.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_autosleep.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_earlysuspend.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_wakeup_count.c
make: *** No rule to make target `/media/im/ext4/andromaxQ/cyanogen/out/target/product/rendang/obj/lib/libtime_genoff.so', needed by `/media/im/ext4/andromaxQ/cyanogen/out/target/product/rendang/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so'. Stop.
make: *** Waiting for unfinished jobs....
make: Leaving directory `/media/im/ext4/andromaxQ/cyanogen'
Click to expand...
Click to collapse
Someone can give any hint about it?

Titokhan said:
[Reserved for future]
I don't have the device myself, so it would be better if some friends from Indonesia will help me out
1. Please post the device's hardware IDs of adb & fastboot interfaces. We may need them to whitelist the device for detection.
Got the device IDs:
2. Post raw backup of 'aboot' partition before & after unlocking bootloader; we need them to add this device in this project.
Click to expand...
Click to collapse
How can I help/participate for this project? I have a non-rooted bootloader-locked Andromax Q with CM12.1 installed

@zlebors
Thanks for your interest. You need to unlock the bootloader, temp-boot CyanogenMod recovery, sideload SuperSU zip to be rooted. Then backup the 'aboot' partition. Now relock the bootloader & again backup the 'aboot' partition - please post those two backups.
:good::highfive:

Updated first post - cm-12.1-YOG4PAS42M-rendang.

Ask
Gan... Andromax Qi bisa di root ga ?
Soalnya pake kingroot gagal terus

need my SF Max Q to be rooted, was failed with kingroot and iroot. anyone could help?
when later i have rooted-phone, i wanna move pre-installed apps like chrome or google other fam apps, is it affecting on next update of cyanogen os installation?

@rahendz
1. To root, please read the first post carefully. You just need to flash SuperSU zip package via CyanogenMod recovery.
2. Yes, removing system applications leads to inability to install subsequent OTA. But you can grab the full signed zip from the first post & flash to bypass this problem.

Titokhan said:
@rahendz
1. To root, please read the first post carefully. You just need to flash SuperSU zip package via CyanogenMod recovery.
2. Yes, removing system applications leads to inability to install subsequent OTA. But you can grab the full signed zip from the first post & flash to bypass this problem.
Click to expand...
Click to collapse
which full signed zip exactly?
YOG4PAS2H2 to YOG4PAS42M: http: //builds.cyngn.com/incremental/...5bc-signed.zip
Click to expand...
Click to collapse
i downloaded it and try to flash, bu i have "signature verification failed" in return. is there something wrong?

Titokhan said:
Root:
1. Unlock the bootloader (fastboot -i 0x201E oem unlock).
2. Flash (fastboot -i 0x201E flash recovery XXX.img) or tethered-boot (fastboot -i 0x201E boot XXX.img) the latest Cyanogen recovery (replace XXX with the name of the Cyanogen recovery).
3. Flash or adb sideload the latest SuperSU zip.
Click to expand...
Click to collapse
Thanks for step guide rooting this device, it works 100%. Even i know this quite late though but it's great to know what works. Sorry for my bad english. May i ask once again tito? just before i know this step, i try many ways to root and makes my HH little uncomfortable to use and i wanna flash with CM12.1 stock, in many post i barely understand the step.
Could you just give me easy step to understand how to flash CM12.1 using adb fastboot? because what i read, i've download the stock with size almost 1.5gb but in next step we only need the boot, recovery and system image. But in another post, those three taken from platform-tool compressed file. that's what makes me confused. thanks before.

Moto G4 play harpia stock firmware.

I figured that since the Motorola web site doesn't have the firmware for this yet I would post a link to my Dropbox so others have access to the firmware. This is for us cellular Moto g4 play xt1607 not sure if it will work for devices on a different carrier. If someone could make a backup of their current rom and test it out to let us all know if it does that would be great. Please hit the thanks button if this helps anyone. https://www.dropbox.com/s/i6jsafelq...y-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?dl=0
This must be flashed with fastboot. If you do not know how to flash with fastboot there are tons of how to videos if you google it.
BACKUP YOUR DEVICE TO SD CARD OR PC BEFORE DOING ANYTHING!!!!!
DISCLAIMER: FLASHING ANYTHING TO YOUR PHONE HAS RISKS. IF YOU DO NOT KNOW WHAT YOU ARE DOING AND YOU HAVE JUST PURCHASED YOUR PHONE AND HAVE NOT UNLOCKED THE BOOTLOADER STOP!!!!! DO NOT CONTINUE. IM NOT SURE WHAT THE EFFECTS WILL BE IF YOU TRY FLASHING WITH A LOCKED BOOTLOADER, IT COULD BRICK YOUR DEVICE!!!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING THIS FIRMWARE. IF YOU DID SOMETHING WRONG AND DONT FOLLOW INSTRUCTIONS THAN THATS YOUR OWN T.S.

Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then download firmware, unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.

I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
DanHutchins said:
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
Click to expand...
Click to collapse

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is the bootloader unlocked?

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What command gives the error?

I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
DanHutchins said:
Is the bootloader unlocked?
Click to expand...
Click to collapse

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Not sure. Did you make sure USB debugging is active for file transfer?

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.

II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
Click to expand...
Click to collapse
That's because if you unplug the phone from the PC then plug it back in it defaults the USB debugging to charge only. If you get into twrp you can still put a custom ROM in root of phone to flash in twrp. I would try that then try to install the stock again. Be sure to have debugging set to file transfer.

I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Please do as of now that's the best I can do. Everything worked fine for me. I have flashed the same file many times on my g4 play

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Were you able to get back to stock?

DanHutchins said:
Were you able to get back to stock?
Click to expand...
Click to collapse
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.

jestyr8 said:
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
Click to expand...
Click to collapse
I like cm13 there just aren't any real good themes for free. I don't mind donating to a dev. but if I can't test it out to see if I like it or not I don't want to pay.

I'm using the material glass theme along with stealth icons, i like it a lot

jestyr8 said:
I'm using the material glass theme along with stealth icons, i like it a lot
Click to expand...
Click to collapse
Looks cool.

DanHutchins said:
Looks cool.
Click to expand...
Click to collapse
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.

jestyr8 said:
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
Click to expand...
Click to collapse
No problem, ask around for anyone able to make it flash able with twrp I'm sure someone can or at least give you instructions on how to do it.

USB debugging to file transfer
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
Where/how to "change debugging to file transfer" on Win-7?
Thanks!
Until now, my only experience was flashing a recovery image to Moto E2 with command:
Code:
fastboot flash recovery twrp.img
Neither I have to change "USB debugging to file transfer", nor I needed to use command
Code:
fastboot oem fb_mode_set
Is that something new and specific to Moto G Play 4th Gen?
Edit:
I have just unlocked the bootloader of my new Moto G4 Play and flashed a new logo file with command:
Code:
fastboot flash logo logo.bin
Still puzzled by "change debugging to file transfer"

Lineage OS 16/17/GSI Install Guide for LG G7 ULM

UPDATE: I kept finding bugs in josh1x's rom, so i installed the LOS17 GSI instead. Guide for that outline in reply #11
Figured this out and thought i'd write a simple tutorial that covers stock (i was at 20e) to lineage. You'll need the LG USB Drivers and adb/fastboot. There are a couple other things to download through out the tutorial and the unlock tutorial in step 1.
LG USB Drivers 4.2.0
ADB/Fastboot
LGUP with partition DL
Note: I was able to reach download mode and fastboot at any point in this process and even when it went wrong (kernel crashes, boot loops etc) while figuring out this tutorial. I found that i could just hold vol down or up in a bootloop with the usb connected to get to the mode i wanted.
Typical combos:
-Download mode: power off phone with usb disconnected. hold vol up and plug in cable
--NOTE: after wiping laf_a and boot_b, you must switch to slot b to access download mode (run command: fastboot -ab)
-fastboot: power off phone with usb disconnected, hold vol down and plug in cable. or adb reboot bootloader
--NOTE: after wiping laf_a and boot_b, you can only access fastboot from slot a by holding vol up on boot (for 20e/21d, on 11g vol down still works).
-Recovery: power off. hold power and vol down, when you see the white LG G7 logo temporarily release just the power button. Continue to hold power and vol down till you get to the option menu. Select Yes three times.
Guide:
1. Follow the universal unlock method here.
1.5. You need to zero out laf_a and boot_b before flashing 21d/20e to maintain fastboot access. Use adb to run the following commands
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
1.75. Enable usb debugging (should already be done). Open LGUP and connect to your phone. dont close it. If you open it after booting to DL mode it wont recognize it
2. 21d ULM firmware (here) must be flashed to use the latest twrp (20e works as well). The 11g twrp cannot install lineageos. I would imagine the EU firmware could be flashed as well, but I used ULM.
Code:
Boot into fastboot
fastboot -ab
Boot into download mode
Use the lg up linked in this post to flash 20e/21d without laf_a and boot_b with partition dl mode
3. Format userdata to decrpyt your file system so TWRP can access it. Then flash TWRP; boot_twrp-june.img can be found here. It's from Josh1x's post here. Note: this TWRP is non persistant.
Code:
Boot to bootloader
fastboot format userdata
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Select restart in fastboot
Boot to recovery
4. Obtain the latest lineage build here. This is from Josh1x's post here. I attempted to flash gapps at this point and it failed, see the next steps.
Code:
Wipe everything
Transfer lineageos to your phone and install it
Restart normally
5. Gapps
Code:
Reboot to bootloader
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Reboot to recovery
Transfer opengapps 9.0 to your phone and install.
Reboot to bootloader
6. We need to flash the stock lineage boot image (here) again now that we are done. The file was obtained with this method
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Restart normally
if you have magisk, it would be magisk_patched_boot.img (here). this one was made from the above image with magisk on my phone.
Code:
fastboot flash boot_a magisk_patched_boot.img
fastboot flash boot_b magisk_patched_boot.img
Restart normally
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
I am so glad to be off of stock, enjoy guys and girls!
Bugs (from my ULM phone)
-flash doesnt work in the camera. also probably why gcam crashes (gcam works on an EM phone somehow)
-brightness slider is calibrated incorrectly compared to stock. way too bright when set to 0%
NOTE: using ULM vendor fixed the flash and brightness, but gcam still doesnt work. This would make it the most functional rom for this phone at this point (vibrate does work).

Being that since day1 of g710pm/ulm could be boot unlocked, all ypu had to do is flash the eu firmware and go to lineage frlm there due to twrp incompatibility.
I have not tested it, but does being on lineage based off EU blobs, do you still get full LTE and/or volte.
If sprint users have switched to eu/lineage do you have full lte/ril compatibility.

Ah crap I didn't know that. I tried unlocking through LG when I got it a couple months ago and that didn't work of course. At that time the phone was working well (not going on a background apps killing spree), so I didn't bother. I couldn't find anything on here at the time for unlocking, but I obviously missed that.
LTE and wifi are working fine. Maybe that has something to do with me never flashing the EU rom to install lineage? Anyways, I couldn't find a volte toggle, but I'd assume it is working. I'm on Verizon and I believe they are killing their cdma network, so I'll find out.
Would this work on sprint phones? There is a warning at the end of the unlocking guide about sprint phones loosing fastboot when upgrading to ulm pie.

does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too

Emanel000000 said:
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Click to expand...
Click to collapse
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.

Have you tried the other twrps?

sirbow2 said:
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Click to expand...
Click to collapse
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?

Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk)
Click to expand...
Click to collapse
oh yea. i see, yes, they might as they are from the lineage rom.
Emanel000000 said:
... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.

sirbow2 said:
oh yea. i see, yes, they might as they are from the lineage rom.
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
Click to expand...
Click to collapse
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide

Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
Emanel000000 said:
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Click to expand...
Click to collapse
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.

Edit: Update 2: dont use the vendor in this post. I patched the ULM vendor, but vibrate and gcam are still an issue with a GSI. links here: https://forum.xda-developers.com/showpost.php?p=81563763&postcount=41 Also, using the ulm vendor on Josh1x's rom fixed everything but gcam.
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.

sirbow2 said:
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Click to expand...
Click to collapse
i just had 20c for em it doesnt matter the version

sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Thanks. You're process got my audio working on GSI. Not sure what incorrect image I was installing or what the issue was.
Just need to disable the LED notification and get vibration working.

EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.

loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
thats what i was kind of thinking the issue was. thats over my head though.

sirbow2 said:
thats what i was kind of thinking the issue was. thats over my head though.
Click to expand...
Click to collapse
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet

loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
loonycgb2 said:
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
Click to expand...
Click to collapse
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?

sirbow2 said:
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
Click to expand...
Click to collapse
Once you got twrp running with stock then do the normal thing of format userdat to decrypt it then flash the no dmverity zip mentioned in the thread or magisk then backup vendor via twrp or dd...
That will give you a usable vendor for lineage and such.
All josh1x or whoever did to the EM vendor was modify fstab to remove the force encrypt so that way decrypted roms would work.

I tried using the vendor from ULM 20e and it doesnt work, i even tried flashing dm verity right after. How would one modify the vendor partition anyways?

Database Info

welcome