CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=clark&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM64 platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/clark/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_clark
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Moto X Pure 2015 (clark), ROM for the Moto X Style (Pure)
Contributors
invisiblek, Hashbang173, gmillz, neph81
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2016-06-03
Last Updated 2016-06-03
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
tanpro260196 said:
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
Click to expand...
Click to collapse
Log? Check dmesg and /tmp/recovery.log
invisiblek said:
Log? Check dmesg and /tmp/recovery.log
Click to expand...
Click to collapse
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
tanpro260196 said:
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
Click to expand...
Click to collapse
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
You could wipe /system (use the advanced format option under wipe) as well as /data (but it looks like that fails, so a full format of internal storage would probably be recommended) and try again.
invisiblek said:
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
Click to expand...
Click to collapse
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
tanpro260196 said:
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
Click to expand...
Click to collapse
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
invisiblek said:
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
Click to expand...
Click to collapse
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
tanpro260196 said:
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
Click to expand...
Click to collapse
That's normal.
No, pretty unlikely.
invisiblek said:
That's normal.
No, pretty unlikely.
Click to expand...
Click to collapse
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
tanpro260196 said:
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
Click to expand...
Click to collapse
No, that's a TWRP thing and its purely cosmetic.
invisiblek said:
No, that's a TWRP thing and its purely cosmetic.
Click to expand...
Click to collapse
Tried your suggestion and failed again.
dmesg is the same.
Log attached. I see some errors in there but I don't understand any of them.
I just installed CM13, booting now... Never unlocked the device, so full stock unmodiffied system 'till now. I flashed CM Recovery but fails to install the .zip it says its for clarck and my device is . (none) so I flashed TWR Recovery and it flashed w/o error at all. First full wipe, including system, then cm.zip and then gapps stock, all fine. Now starting Android for first time optimizations... I'll let you know if something goes wrong.
At last...
Sent from my XT1572 using XDA-Developers mobile app
Clark booted fine no issues accept having issues updating binaries in SuperSU
---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------
ARUN B said:
At last...
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
+1
Haven't flashed anything in weeks, guess I'll finally give cm a shot.
Just noticed cm recovery. Any benefit to flashing this? I'll find out soon enough I suppose.
Weird, I can't flash this rom but I can flash everything else normally (unoffcial cm13, RR, Dirty Unicorn)....
Wow cm recovery is pretty lacking feature wise... Now i have to flash twrp again.
---------- Post added at 09:40 PM ---------- Previous post was at 09:11 PM ----------
Flashed fine here. Loading apps now.
Been running well for me most of the day. Thanks to everyone who has been a part of the ROM.
Hi, can you share battery life?
Related
LIke the title says, this rom is built from the 4.4.2_r1 image and binaries from the Google repository (no changes or mods). This is pure AOSP KitKat.
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ or PhotoSphere.
To install:
-TWRP or CWM recovery
-Factory reset, wipe cache and dalvik...if coming from a rom other than stock, wipe data too.
-Flash Rom
-Optional....flash "Photosphere Camera Addon Module" or other "Gapps packages"...only necessary for HDR+ and Photosphere
-Reboot and let install
-For HDR+ and Photosphere, flash "Photosphere Camera Addon Module" right after flashing rom (make sure its for 4.4.2) *see below for link
Rom Download.
aosp_hammerhead-kot49h MD5=34d9d60a4062d590f92746c977af9167
https://mega.co.nz/#!DJkD2QLB!OvMrzzp023VJYJSu-Y0wplRuL6Qlt3oDKNr6DtshoEw
Photosphere Camera Addon Module and all other Gapps-PA-Google apps
http://forum.xda-developers.com/showthread.php?t=2397942
To root-SuperSU 1.86
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
-Flash rom, let it install, place SuperSu into internal storage, reboot to recovery flash and reboot.
Thanks to Google for images and binaries
Thanks to TKruzze for PA-Google apps
Thanks to Chainfire for SuperSU
first... first time
will give it a shot.. lets go
Nice to have solid stock to fall back on. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Gene Poole said:
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Click to expand...
Click to collapse
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Loving all this new development. Thanks for this
sent from my Hammerhead Nexus
rsa 329 said:
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Click to expand...
Click to collapse
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Gene Poole said:
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Click to expand...
Click to collapse
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Gene Poole said:
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Click to expand...
Click to collapse
Interesting. I've been using a debloated version of my aosp for a while now with no problems. I ran this build for a couple weeks before switching and had no issues. Did you do a full wipe? How about ART, are you using art or dalvik? Have you tried your build after doing a system format? What service provider do you use?
Sorry for all the questions, just trying to get an idea of your situation.
I'm with AT&T. I decided to put this back on and wait for it to act up, then get a logcat and go from there. We'll see how it goes.
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Gene Poole said:
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Click to expand...
Click to collapse
Very cool! Glad to hear you got it working.
One issue I've just discovered is that the camera, when in video mode, records video files with a green line at the bottom (only visible on playback). I've researched this and found that AOSP source is missing an update in one of the files that makes up the libmmcamera_interface.so shared object. Copying the same filename from the factory image into the /system/lib directory, overwriting the existing file from AOSP build fixes the problem.
Again, no problem with your build; the problem seems to be that Android hasn't committed all their code the the AOSP tree.
rsa 329 said:
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Click to expand...
Click to collapse
Hi RSA,
can you please share the instructions with me as well ? much appreciate your work..
Unofficial build of SlimKat
Dont post in official threads please. I may have messed something up and i dont want to bother other people because of my mistakes.
After leeching for years on XDA (didnt even had an account) i finaly decided to give something back to the community.
Features:
Im using the build scripts from Slimsaber
Features of Slimsaber but not all are working!
Used newest Linaro 4.8.3 (2014.04) optimized for cortex-a15 from here for kernel and rom.
Did some patches so it compiles with strict-aliasing :victory:. But i hate those freaking pointers. So maybe i messed something up.
all the nice placebo compile flags: -O3 -mcpu=cortex-a15 -mfpu=neon-vfpv4 -mfloat-abi=softfp -funroll-loops -fomit-frame-pointer
Other flags:BOARD_USES_HGL := true, BOARD_USES_OVERLAY := true, USE_OPENGL_RENDERER := true, TARGET_USES_ION := true, TARGET_USES_C2D_COMPOSITION := true
all the nice placebo build.prop tweaks: debug.sf.hw=1, debug.composition.type=c2d, debug.performance.tuning=1, persist.sys.composition.type=c2d, persist.sys.ui.hw=1, hw3d.force=1, hw2d.force=1, video.accelerate.hw=1, force_hw_ui=true, debug.egl.hw=1, debug.overlayui.enable=1 (actualy i dont know which ones are working and which ones arent even in the code )
f2fs for data and cache partition. (I think the first released z ultra rom with f2fs. Correct me if im wrong please)
DPI set to 280 (tablet layout).
Install instructions:
Be running at least Android 4.3 or 4.4.2 with an unlocked BL (14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681 or 14.3.B.0.757 etc)
Make a backup of everything on your phone. Im not responsible for any loss of data!
Boot into recovery
Factory reset/wipe data
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom
Install Gapps (I use this one)
Optional: for even more placebo install this soundmod.
Not Working:
Nothing known
Not Tested (would be nice if someone could test it):
ART
Miracast
Other models then C6833
Bugs:
WARNING: ADB/USB Debbuging is always enabled on reboot! So if you have sensitive data on your phone this ROM is NOT for you! (maybe someone can help. tried to disable it via build.prop and settings.db but didnt work . I think it has something todo with the build scripts from Slimsaber but hadnt had time to check it.)
[*]After installing the ROM for the first time you have to go to developer settings and disable root and reenable it in order for it to work!
Its already set to apps only after installing but it wont work! You only have to do this once. If you reflash you dont have to do it again.
Some graphics glitches because of "USE_OPENGL_RENDERER := TRUE" in some system apps (like Browser).
Actualy i read somewhere that its not needed but it wouldnt be placebo without it
If you use MHL some of the screen will not be displayed (It displays only like 1900*1000)
Downloads:
FormatPartitions-userdata_cache.zip. Credits goto legolas83
PlaceboRom-togari-4.4.2-20140515.zip
RestorePartitions_ext4_userdata_cache. If you want to go back to another rom. Credits goto legolas83
I will try to build every two weeks.
I had only one freeze on my device (C6833) in over 1,5 months (with older builds) but consider these build as NOT STABLE. I dont want that you lose your job because of me.
Special thanks to team slimroms.
Visit official website at http://www.slimroms.net
Slimsaber is the inspiration for this rom. High five @fusionjack.
If I have time i will setup a github account so contributions will be clear.
At the moment im using repos from Slimkat, Slimsaber, CyanogenMod, VanirAOSP, AOKP, Linaro
If i missed something or didnt gave proper credits i can assure that this is a mistake.
Contact me please so i can correct it.
XDA:DevDB Information
PlaceboRom, ROM for the Sony Xperia Z Ultra
Contributors
MusterMaxMueller, fusionjack, [vertigo], dboliver, blueether, Christopher83, legolas83, prbassplayer, SlimRoms, CyanogenMod, VanirAOSP, AOKP, Linaro, FreeXperia, CodeAurora, Google
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681, 14.3.B.0.757 or newer
Based On: SlimKat, CynanogenMod, VanirAOSP, AOKP
Version Information
Status: Testing
Created 2014-05-15
Last Updated 2014-05-15
Reserved
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Reserved
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
Looks promising, yah the first F2FS! :highfive:
MusterMaxMueller said:
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Click to expand...
Click to collapse
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
keep it up mate...looking forward for this rom. :good:
@blueether
I think i dont get you. AOSP/Slim is released under ASL. So changes made to rom dont need to be published? Altough i will when i have time. And is defconfig considered part of the kernel? Because of "make menuconfig"? Does anyone know for sure? If i interpret this and this correctly changes to Makefile have to be published but defconfig not. They even mention build flags!I know its pedantic just want to know. It seems there is no defenite time frame when sources have to be published?
blueether said:
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
Click to expand...
Click to collapse
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
mac231us said:
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
Click to expand...
Click to collapse
That did it thank you.
reread it. i think youre right
blueether said:
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
i have no problems using minimal gapps from op.
try using the one from op.
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
F2FS mount and sysfs options
For those interested in tweaking F2FS, check my post here.
wrong install instructions
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
download not working
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Premananda_laishram said:
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Click to expand...
Click to collapse
I'm uploading to mega atm, should be up in about 20 - 30 min
Google Drive mirror: https://drive.google.com/a/fryett.net/file/d/0B2qGRw4S7bAuUkxWVzVXQzNJOXc/edit?usp=sharing
Mega mirror: https://mega.co.nz/#!9pt1xSQL!ozJyip-yzATId0_Po7sG1_sisWH8UfnNVOhHmxh-4fA
Premananda_laishram said:
Please upload to mega or somewhere else
Click to expand...
Click to collapse
you could also use the download tab ?
not working
Flashing instructions not working. Hangs at boot logo
Premananda_laishram said:
Flashing instructions not working. Hangs at boot logo
Click to expand...
Click to collapse
which install instructions doesnt work?
the first or the second one?
try first without flashing gapps.
Temasek's UNOFFICIAL CM13.0 BUILDS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
FAQ: "Q: Have problems connecting to your Wi-Fi router? -> A: Make sure you have selected the correct region/country code in the advanced wi-fi settings!"
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
@temasek
@arter97
@Chainfire
@benand - for highlighting a dam error that i had missed for over a month, thanks
CM Team]
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
Temasek
Rom Source
Changelogs
Temasek Github Changelog
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65559375&postcount=2252
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
joshndroid said:
more maybe
Click to expand...
Click to collapse
Any plans to support P601 variant, only Phone calls & 3G to be activated or added.
Much appreciated if you got the time to add this to your rom building,
Unfortunately not. Firstly because I don't have the device. Secondly I don't have the skill set to create a working device tree from relative scratch. Lastly Samsung suck for exynos based devices, sorry.
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Unfortunately not. Firstly because I don't have the device. Secondly I don't have the skill set to create a working device tree from relative scratch. Lastly Samsung suck for exynos based devices, sorry.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thought as long as they have the same Hardware , same tree would be applied and just adding a modem to it.
lsherif said:
Thought as long as they have the same Hardware , same tree would be applied and just adding a modem to it.
Click to expand...
Click to collapse
Lol
Not so simple.
temasek said:
Lol
Not so simple.
Click to expand...
Click to collapse
I know that for sure it is not that simple, but if you got the time to support this , would be my pleasure to test
need p601
p601 support please all devs i beg for this
thank,merci
hello thanks you for this new rom
Nice job!
P605/P607 please someone. A realible working one!
I'm using temaseks build for my note 3 and love it. Is there anyway to get it ported for the 605 lte model? I'd try but I have no idea how to build/port roms
davitox87 said:
I'm using temaseks build for my note 3 and love it. Is there anyway to get it ported for the 605 lte model? I'd try but I have no idea how to build/port roms
Click to expand...
Click to collapse
Running it on my S5 and I love it. P605 or P607 for me would be lovely.
after I tested...
I have this rom installed on my P601...
Not workings:
Camera
Flash light
Mobile Data and Sim Card
SuperSU
And some more...
But there is some thing that i love this rom... And it's because VPN connections works well
And it doesn't become so hot.. And will not die anymore... Nice work..:good::good:
Well at least you know it is not for your device? lol...
I always flash latest version of supersu and never rely on inbuilt su... I believe it may be addressed in temasek source though
New build tomorrow being a shift worker sucks sometimes.
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Well at least you know it is not for your device? lol...
I always flash latest version of supersu and never rely on inbuilt su... I believe it may be addressed in temasek source though
New build tomorrow being a shift worker sucks sometimes.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
SuperSU built-in from next build.
I might even totally remove Superuser.
BTW I'm a shift worker too and I spin builds like nobody business.
How is battery life with this one? And stylus functionalities? Not that I use it... ever. Just wondering how close it is getting.
Since it's tema's name in the name of the rom, I'm considering tearing my warranty into pieces
Any additional encouragements (or discouragements)?
temasek said:
SuperSU built-in from next build.
I might even totally remove Superuser.
BTW I'm a shift worker too and I spin builds like nobody business.
Click to expand...
Click to collapse
Yeah I have been reading github for additions
It's just the lack of time, a fresh cleaned out folder takes about an hour to build with lollipop no matter device. Takes 4 minutes with a dirty out folder. Comparison kitkat took 36 minutes with a fresh out folder and about 16 for a dirty. I want to be able to eventually build for about 4 or 5 devices so Just grabbed a new charger for my older i7 qosmio laptop... Gonna throw a big ssd in it coupled with a 1tb hdd and use it as a dedicated build box, rather burn that out churning builds than my clevo beast..
perozu said:
How is battery life with this one? And stylus functionalities? Not that I use it... ever. Just wondering how close it is getting.
Since it's tema's name in the name of the rom, I'm considering tearing my warranty into pieces
Any additional encouragements (or discouragements)?
Click to expand...
Click to collapse
I'm getting good battery life as for stylus I'll try my note 3 stylus and report back
Sent from my SM-N9005 using Tapatalk
Stylus works as it should the little mouse arrow shows and can even move the pointer around without actually touching the screen
Sent from my SM-N9005 using Tapatalk
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
Androidfilehost:
Download: https://www.androidfilehost.com/?fid=24391638059057759
Google Apps Minimal Edition:
Download: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Installation
1.) You must have twrp installed follow this guide here
2.) Download the ROM and Gapps and place them on internal or external storage (depending on your model you may only have internal storage)
3.) In TWRP navigate to "Wipe" and wipe cache, data, and dalvik
4.) In TWRP navigate to "Install" find the location of the downloaded zips and proceed with installation
5.) Once both ROM and Gapps have been successfully flashed reboot system and wait for the device to boot
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5, ROM for the Alcatel Onetouch Idol 3
Contributors
Unjustified Dev
Source Code: http://github.com/TeamRegular
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-10-14
Last Updated 2016-01-28
Status
Working:
Radio (Includes Dual Sim, Data and SMS)
Sound
Camera
BT
Sensors
Wifi
Known Issues:
Please share your bug reports (include a log if possible)
Tap to wake (Works, but disables itself randomly)
Horrendous battery drain
Changelog
20160218
remove unneeded qcom usb script
disable boot freq limit for cluster
20160216
Updated prima driver to LA.BR.1.1.3_rb1.45
Updated kernel to LA.BR.1.1.3_rb1.45
add back various alcatel kernel changes
set usb properties on boot (Fix the usb product model defaulting to Android)
set variant from init and add support for I806 (pivoq)
selinux enforcing (wcnss fixes by pivoq)
add peripheral manager
wcnss: restore stock config
20160128
update storage configuration (fix internal storage access)
don't set tct properties
set taptowake control state to 2
remove window cover support (revisit later)
remove unused zram script
remove tct cmdline garbage
remove unused hdcpService
remove power engine
remove powerup reason
remove unused Tct Daemon
disable secure discard
remove camera wrapper
use half res bootanimation
update WCNSS cfg from firmware bin
Stop the QC-QMI message spam
switch to init.qcom.power and update devfreqs
add script to identify device variants
switch to new cm-12.1 kernel
update adreno blobs
FAQs
Q: Is the device fully reversible on CyanogenMod as well?
A: Unfortunately no, it does allow all rotations but the dialer app currently will not allow you to place calls upside down.
Q: Does Dual Sim work with this ROM?
A: Dual Sim devices are now supported
Q: Why is my device 6045X?
A: The script failed to identify your device the supported model are 6045I, 6045B, 6045K, and 6045Y
Q: How can I get my device supported?
A: Post the model number and stock build.prop
Q: Is the Aero flipcase supported on CyanogenMod?
A:At the current moment it is not supported
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
salzy said:
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
Click to expand...
Click to collapse
No plans at the moment. There's is already someone handling 4.7 variants. Check out the CM port thread for details.
w00t!!!!!
Sent from my 6045I using Tapatalk
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
So close but yet so far.. I was so hyped when saw the thread but got down to earth quickly.. Stay focused my man, you're about to make something that's good into the great..
Just wondering if cm have some incompatibles with root apps like greenify, Viper 4 Android? Thank you
Sent from hell
Did you get the kernel to boot building from source or are you still repacking with stock?
Sent from my 6045I using XDA Premium HD app
brian117 said:
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
Click to expand...
Click to collapse
It's close. Just seeing how fast @Unjustified Dev has progressed to this point has been impressive.
Great Great Great my idol trembles park in the pits ready to receive new engine.
make sure everyone to get the minimal gapps as 5.1 before download
Whoohoo! so excited haha.
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:deleted
masterdex said:
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Unjustified Dev said:
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Click to expand...
Click to collapse
Then I immediately delete the link to avoid problems.
My ADB is ready.
will it be regular flash or aroma installer?
masterdex said:
Then I immediately delete the link to avoid problems.
My ADB is ready.
Click to expand...
Click to collapse
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Unjustified Dev said:
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Click to expand...
Click to collapse
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
masterdex said:
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
Click to expand...
Click to collapse
You can flash gapps before and the boot.img isn't needed flash cm and gapps. Once they are done mount system and use the file manager to remove wlan module and that's it reboot and everything should be fine.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Note 1/19/18: I fixed OTG in 3.2.1-0. Since the LineageOS kernel for the VS995 is known to have broken OTG, I went back to my good old reliable 10b source. I stripped down the options as much as I could to reduce the file size. It seems to be working well. Unfortunatly the only way to tell them apart is the file size or md5.
Old: 24,637,440 bytes / MD5 - ca8bb67c07a81fe17f463eeaacd7c096
New: 24,653,824 bytes / MD5 - d2b25849241b9524b838a11bb0a39093
Here's the build info from the old builds for those looking for breadcrumbs, etc.
OK, this is the first time I've built TWRP so I'm sure there are some issues. Please use this at your own risk. I've done some very basic testing and it seems to work OK for my purposes. I do not plan to build for anything other than the VS995. For other devices I'll lay out my basic workflow in hopes that those still working on other devices can do the same.
Basically I followed the guide here: https://forum.xda-developers.com/showthread.php?t=1943625
Since I already have the LineageOS repositories (with proprietary files from here) installed on my machine, I started with the code from here: https://github.com/omnirom/android_bootable_recovery
I found out LineageOS doesn't have busybox so I added that to my LineageOS system/external folder from here: https://github.com/omnirom/android_external_busybox
Since it failed to build with encryption, I cherry-picked this commit: https://gerrit.omnirom.org/#/c/22096/
I added the recover.fstab from here to the device folder for the vs995: https://github.com/jcadduono/android_device_lge_vs995/tree/android-6.0/recovery/root
Here are the extra lines and flags I added to my default LineageOS BoardConfig.mk
Code:
RECOVERY_VARIANT := twrp
PRODUCT_COPY_FILES += device/lge/vs995/twrp.fstab:recovery/root/etc/twrp.fstab
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TW_INCLUDE_CRYPTO := true
That's pretty much everything I've done.
Note to developers: This recovery is a true VS995 build. Please add vs995 to your zips asserts.
Know issues:
- ROMs, kernels, mods, etc. whose zips are built with 'elsa' and/or 'vs996' only asserts will not flash. This is not a bug. If your zip tells you it's for another device and not a vs995, please ask the developer to add this to their asserts.
Download: VS995 TWRP 3.2.1-0
Device tree/kernel source
Old Builds:
VS995 TWRP 3.2.0-0
TWRP 3.2.1-0 Changelog
Code:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Thank you very much, even though I don't own a VS995 it's always good to see new development. Thanks again OP.
Link gives me "Access Denied"
wally86 said:
Link gives me "Access Denied"
Click to expand...
Click to collapse
I (think I) fixed it. Please try again.
BackCheck said:
I (think I) fixed it. Please try again.
Click to expand...
Click to collapse
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
wally86 said:
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
Click to expand...
Click to collapse
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
BackCheck said:
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
Click to expand...
Click to collapse
Alright sounds good. I'm gonna try resurrection remix & weta with this version and I'll report back in a few days with how it's working.
Awesome, thanks for keeping the development alive!
Awesome thanks so much. Downloading now. You're great!
Any idea if this is available on the H918 (T-mobile)?
jaysonic88 said:
Any idea if this is available on the H918 (T-mobile)?
Click to expand...
Click to collapse
To the best of my knowledge, there is no 3.2.0 TWRP for the H918, 3.1.1 is the most recent build for it.
This works perfectly with VS995. Thank you!
Any idea how to make this for H990DS ?
Zenns said:
Any idea how to make this for H990DS ?
Click to expand...
Click to collapse
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
BackCheck said:
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
Click to expand...
Click to collapse
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
toastyp said:
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
Click to expand...
Click to collapse
Good job. And no, my first build had completely different errors. If you want to PM me your fstab and board config I might be able to look over it sometime and see if I can see anything. Those 2 files look like good places to start.
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Phoenix591 said:
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Click to expand...
Click to collapse
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
BackCheck said:
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
Click to expand...
Click to collapse
No it isn't in jc's fstab, looks like USA-RedDragon has it in his, https://github.com/DesolationRom-Devices/device_lge_h910twrp?files=1 . Going to take a closer look in a day or so.
Well, I got USB otg working, just not the way I hoped. I grabbed the prebuilt kernel image from the repo in my last post and that did the trick when using his fstab as well. So it's probably a kernel problem, since it didn't work with his fstab alone. I tried enabling the more obviously named USB otg kernel config options without success.