Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
Important Notice: This ROM can be flashed with either TWRP 2.8.1.0 or Philz Touch Recovery v6.55.0, however restoring backups is not straight forward. The only reliable way to restore a KitKat backup is to use this method.
.: Identity Crisis ROM (Single-SIM) :.(Android 5.0.2)Lollipop Bootloader not requiredThis ROM has been built from the latest firmware for XT1063 - Stock Android 5.0.2 (v22.21.28).
Yes, you read correctly; this is a Moto G (2nd Generation) ROM running on XT1032.
XT1032 Lollipop Radio Firmware available here.First boot can take a few minutes.Screen flicker is due to Kernel. Turn screen off once to fix. Custom stock kernels in the future might solve this.
Features:
Stock XT1032 5.0.2 Kernel
Debloated (Motorola apps still available in Play Store)
Zipaligned
Rooted
Busybox
'Cast Screen' Enabled
OTA Updates | Motorola Notifications Disabled
MultiROM compatible - TBC
init.d Script Support
Post-install zipaligning (Darky / Fly-On Mod™)
How to flash:
1) Sideload or download ROM to internal storage.
2) Boot into Custom Recovery.
3) Factory Reset (System, Data, Cache, Dalvik)
4) Flash zip, reboot.
This ROM requires a F2FS 'userdata' partition.
If you are GPE, or have ever been; you may need to convert to Stock. More info in FAQ here.
Working:
Almost everything
Not Working:
Compass
CDMA or Dual-SIM support
Tips:
Stock Boot Animation (Flash in Recovery)
Problems restoring TWRP backup? Read this and this
Speed up animations in Developer options - Instructions
"OK Google" / Google Search not working? Available in Play Store
Want Face Unlock? Flash this
Battery Percent Enabler
Adblock Plus issue
Faster GPS locking: Try this app
Enable Automatic Battery Saving Mode: Settings > Battery > Menu Button > Battery saver > Turn on automatically @ 5% or 15%
Download v006 (355MB)
v005
Download v005 (334MB) [Mirror]
Screenshots:
http://forum.xda-developers.com/devdb/project/?id=7715#screenshots
Changelog:
30/01/15 - v005 - Now using XT1032 Kernel / Modules. Fixed Camera issue. Updated SuperSU. Re-added Stock Equalizer (Sound > Audio effects)
22/01/15 - v004 - New build to fix audio issues
20/01/15 - v003 - Fixed APK issue (Thanks mounkg, VitaTaf); added ROM name to 'About phone' screen
17/01/15 - v002 - Fixed Speaker audio and Auto-rotate
16/01/15 - Initial release
XDA:DevDB Information
Identity Crisis ROM, ROM for the Moto G
Contributors
lost101, mounkg, VitaTaf
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: XT1063 (Titan) Stock Android 5.0.2 | Build: LXB22.46-28
Version Information
Status: Stable
Current Beta Version: v006
Created 2015-01-16
Last Updated 2015-02-22
Woe dude,awesome work! I will try this as soon as i get home!
Interesting ROM
Regarding Recoveries... What about the newer TWRP builds? Do they work properly with lollipop?
k-kuchen said:
Interesting ROM
Regarding Recoveries... What about the newer TWRP builds? Do they work properly with lollipop?
Click to expand...
Click to collapse
Work on Lollipop support has yet to begin.
Where is it? ?
Link up now. Sorry for the delay.
Twrp failed to flash, even after wiping internal storage, latest philz flashed fine. Working great on my xt1032
jikobutsu said:
Twrp failed to flash, even after wiping internal storage, latest philz flashed fine. Working great on my xt1032
Click to expand...
Click to collapse
TWRP needs a reboot if you wipe internal storage.
The ROM has no sound, and I mean everywhere ?
I made a test call and that had sound.
lost101 said:
I made a test call and that had sound.
Click to expand...
Click to collapse
can you test music playback? Or games sounds?
on mto g 1032 converted to gpe stuck at boot ... booting over 20 minutes now ... may i do migration maybe to f2fs ??
DeHuMaNiZeD said:
can you test music playback? Or games sounds?
Click to expand...
Click to collapse
I can't check until morning. A sound driver fix may be needed, should be only a small zip.
wts1 said:
on mto g 1032 converted to gpe stuck at boot ... booting over 20 minutes now ... may i do migration maybe to f2fs ??
Click to expand...
Click to collapse
Yes, f2fs required.
not working : audio , auto rotate
Made it with Phils recovery. Boot it in 3-4 min.. Rom is fast and smooth. Audio and rotate don't work, but if u fix that it would be great. Thanks @lost101
wts1 said:
not working : audio , auto rotate
Click to expand...
Click to collapse
bobrda said:
Made it with Phils recovery. Boot it in 3-4 min.. Rom is fast and smooth. Audio and rotate don't work, but if u fix that it would be great. Thanks @lost101
Click to expand...
Click to collapse
was about to flash it when i read this... too bad
will wait a little bit, in the meantime updating cm12
Can't wait for the audio fix.
Great ROM waiting for audio fix
Sent from my XT1032 using XDA Free mobile app
I actually contacted Shawn5162 a few hours before posting this. I asked him if he would consider a release of his ROM for Moto G (1st Gen) because I could see it might be possible, and told him how.
I made the decision to release a very basic ROM based on a pure stock system dump, for others to use as a launchpad for their own work. This ROM doesn't have most the features of the 'Titan Prime' ROM, because it's not a port of that ROM.
I don't mind changing the name if Shawn wants, and I am happy to credit anyone.
FYI: The codename of XT1063 is Titan.
EDIT: Now called 'Identity Crisis ROM' - the original working title...should have stuck with that.
With XT1063, the main speaker is front-facing.
A temporary solution is to re-route all audio to the earpiece speaker using SoundAbout.
Related
Resurrection Remix by quanganh2627
What is NOT working:GPS, FM radio, Autorotation
What is working:Other like Wi-Fi, OTG, baseband and etc.
How to install it:Step 0:
Bootloader unlock is required for every custom rom. You can use this tool for unlock:
https://drive.google.com/file/d/0B-Fin8UxrD6PWTZtR2VXX0dxcU0/view?usp=sharing
Step 1:
You should download files for flashing:
File with RR rom (Resurrection-Remix-LP-v5.5.8-20151024-a500cg.zip):
beta7.1
NOTE: RR builds for Zenfone 5 are compatible with Zenfone 6!
IMPORTANT: Do not forget to flash Xposed with RR Beta7.1. This way many issues (lags, memory bugs) will be solved.
OpenGapps: Download from Google Drive
XPOSED v78 : Download from Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new Decmber build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal two packages: Resurrection-Remix-LP-v5.5.7-20151012-a500cg.zip and gapps-L-x86-20150816-signed.zip.
NOTE: FlashResurrection-Remix-LP-v5.5.7-20151012-a500cg.zip file first.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:Attach logcat and detailed describe the issue. Send this to quanganh2627:
http://forum.xda-developers.com/member.php?u=5392204
Credits:to @quanganh2627 @knoneNull @shakalaca and Hazouh
XDA:DevDB Information
Resurrection Remix V5.5.9 for Asus Zenfone 6 by quanganh2627 , ROM for all devices (see above for details)
Contributors
tank0412, dimdimdim
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: unlocked bootloader
Based On: CM 12.1
Version Information
Status: Beta
Current Beta Version: 7.1
Beta Release Date: 2015-12-06
Created 2015-10-18
Last Updated 2015-12-06
To fix camera, you should open build.a600cg.prop and copy all stuff from this file to build.prop file.
And what's wrong with camera? Mine works fine on 5.5.7 kernel 6.6
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
Need help with Xposed. I've got boot loop with x86 sdk22 v74. Xposed for lollipop doesn't flash framework itself.
Okay, seems, the problem with Xposed is solved by flashing XPOSED X86 SDK22 v75 to 6.6 RT BETA http://forum.xda-developers.com/showthread.php?p=63396458#post63396458
some observations on beta with 6.5-6.6 kernels:
- touch freeze after call (system is still up, you can use your hard buttons to practice bringing volume panel and power menu up. by6the way, when I discussed xposed workability on zenfone 6 in my pms, one man mentioned he had same behavior within twrp recovery if flash zenfone 5 twrp on zenfone 6. IDK if this is in any way connected (anyway, we are flashing native zenfone 5 rom and recovery, so, everything is possible), but posting it here for devs, maybe it will bring them some ideas
- 6.6 kernel: burst mode on zenfone camera doesn't work. it starts working normally, but never stops and nothing saves. 6.5 seems works fine.
- Xanwars kernel v2(fixed lags) doesn't start second sim... Taking into account there is no raise in performance for me on this kernel (have no chance to test touch freezes after call due to a not working sim2) even though it allows overclock up to 2.2 and all the governors and schedulers are here.. Staying with beta 6.7 and 6.5 kernel
will update this. it's not a bug report with logcat yet as far as there is nobody here who develops for zenfone 6. yet, I hope.
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Hajile caz said:
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Click to expand...
Click to collapse
You don't have touch freezes after call on 6.6?
What about burst mode on asus camera? Does it work on your phone?
Which AnTuTu score do you get on 6.6?
Max what I saw on any kernel was 28900
Btw, dpi change on 6.2 kernel gives me boot loop. 6.7&6.5 both work fine.
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
My antutu score on beta6.6 without flashing any kernel
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
aymanz said:
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
Click to expand...
Click to collapse
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
Hajile caz said:
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
Click to expand...
Click to collapse
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
dimdimdim said:
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
Click to expand...
Click to collapse
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Hajile caz said:
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Click to expand...
Click to collapse
Do you think it will help for those, who have their bootloader unlocked unofficially, to lock it again and unlock with asus unlock?
I think it might be helpful for those devices that suffered from lags and freezes. Although it's a long process, but why not gave it a shot then, we all came this far.
beta 6.8 boots well http://forum.xda-developers.com/showpost.php?p=63457490&postcount=1918 on zenfone 6
first observations:
- no vibro (but this is common) -fixed the build from 24.10
- dpi change goes in some strange way: it works, but at starting apps point gets boot loop. anyway, you can break the loop forcing power off with hardware button at this point and bring it back to boot, which goes normally this way and never gets into the loop again after.
..still testing, got it in the night..
kloroform said:
thank you, downloading the ROM now, but my question is how stable is the ROM is now? Can I use all the ASUS apps with this ROM, the asus camera app mainly. Is it possible?
And can I come back to asus stock rom if I wish? I already made a backup, but a youtube channel guy on youtube told me few weeks back that it depends on the rom, he was talking about some odex-deodex thing. And if my ROM is odexed it wont boot even if I restore my stock rom backup on the same phone?
Click to expand...
Click to collapse
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
dimdimdim said:
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
Click to expand...
Click to collapse
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
kloroform said:
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
Click to expand...
Click to collapse
I'd like to help you, man, but I know nothing about bootloader unlock nuances on zenfone. Everything I know, I said: my burst mode on asus camera doesn't work and I have screen freezes with kernels older, than 6.2, and a man in this thread, you can check previous posts, has no these issues and he (and many others) believes it has connection to the bootloader unlock method.
Just be careful and make your decision, as playing with a bootloader lock/unlock with different tools could be dangerous. Remember, I know nothing about this.
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Hajile caz said:
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Click to expand...
Click to collapse
Hello, I'm using default one. Everything is ok with it for me, besides known bugs which are still here: screen freezes, gps, no screen rotation.
Hi!
My shieldtablet is running CM 12.1 (latest 20160807 build)... That works fine. It has latest TWRP 3.0.2-2 installed. And latest open GAPPS 5.1 (mini arm).
I am trying to get it to run CM 13 I've tried the first builds... didn't work... I tried today with the very latest nightly build 20160909... I do this by booting to recovery (TWRP 3.0.2-2) then going to install, and installing cm-13-20160909-NIGHTLY-shieldtablet.zip, and also open_gapps-arm-6.0-mini-20160912.zip (using the install multiple ZIPs feature of TWRP). Then I wipe DAVIK and cache and reboot.
Device stays forever at the nvidia logo.
I turn it off. Boot to recovery, reinstall CM 12.1 and opengapps 5.1 with same process... and that works fine. Machine reboots like a charm.
Any idea if I am missing a step? And what step that would be?
Thanks in advance,
Gilles.
Have you done the firmware update?
http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
Firmware Update:
If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.
3.1.1 (L)
4.2.0 (M)
Ah... No. I'm confused, though. What's the difference between L and M files? Do I need to flash both? Or just one?
I'm running CM 12.1 (Android 5.1.1 Lollipop)... So I could imagine having to flash L? But since I'm updating to 6.0.1... Would that mean M?
I imagine I download the ZIP, boot into TWRP, flash the right version. Then flash CM 13. Then flash Open GAPPS?
Or in a different order?
Thanks,
Gilles
I'm on stock, so it's just a shot in the dark - but i think this sounds logical:
L - Lollipop - 5.x, flash this when you are on 13.0 and want back to 12.1
M - Marshmallow - 6.x, flash this when you are on 12.1 and want flash 13.0
and then cm + gapps of course
regards,
wakko
All in one shot? Boot to TRWP, flash M, CM, GAPPS then reboot?
Hopefully - you'll only find out, when you try
So... that's exactly what I did, and it worked.
So steps : log into the SHIELD (CM 12.1 / Android 5.5.1)
Reboot to recovery (configured advanced reboot in developer options)
From recovery, selected the M drivers, then added the CM 13 zip, then added the Open GAPPS (6.0 ARM MINI) ZIP.
Then clicked FLASH
Then rebooted (I was impatient, didn't think to clear DALVIK and cache).
Machine rebooted and all seems well (SD card was detected and I said use as portable storage, Avast asked for a few more permissions, only Viber got confused and requires relinking to mobile account).
All nice.
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
ggravier said:
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
Click to expand...
Click to collapse
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Steel01 said:
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Click to expand...
Click to collapse
Thanks! Solved! So far, I love it!
ggravier said:
Thanks! Solved! So far, I love it!
Click to expand...
Click to collapse
I am having the exact same issues as OP. Not tried this fix yet, but seems promising. Question is, does any of those L or M files wotk with Nougat? or is there one for that too?
Disclaimer:
/* **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. * */
Resurrection Remix N
This rom is for D838 variant, maybe works on others, but I have not tested.
Working:
-Wifi
-Ril
-Camera (rear, front, video)
-Sound
-SDCard
-DT2W (Double tap to wake)
-Bluetooth
-NFC
Bugs:
-Tell me
LineageOS 14.1
Working:
-same as RR N
Bugs:
-same as RR N
Installation:
-same as RR N
Downloads:
Latest builds:
Mokee June Update:
-June security patch level
-Kernel and device tree updates
link : https://drive.google.com/open?id=1etfqN8e1C5VxvBdtyJmuSuDkIxRTg2vh
Mokee May Update:
-May security patch level
-Kernel and device tree updates
-Enabled zRam
link : https://drive.google.com/open?id=1El4BRvm0ehAMm7TzA1EiiHfRPYGDNGKr
February updates: (MOKEE N, LINEAGEOS 14.1, RR N
Download
Changelog:
-Kernel and device tree updates
-New governors and IO schedulers
-February security patch and ROM updates
(I'm gonna update RR and LineageOS soon)
December update:
https://drive.google.com/open?id=1jHwwNxaMJ91-iTOuSqm0jYRjzSuJO3jK[/SIZE][/B]
Only LineageOS is rooted, for other roms flash magisk.
Changelog:
-Kernel, device tree, rom updates
-December security patch level
Resurrection Remix N
RR-N-v5.8.5 20171010
link: https://1drv.ms/u/s!Ai3bT6KNVyQEiD62G-CtstEulJu0
news: RR updates, kernel updates, October security patch, etc
This is final build of RR based on Nougat
Lineage
lineage-14.1-20171013
link: https://1drv.ms/u/s!Ai3bT6KNVyQEiEArgg1WboOrj7B_
news: LineageOS updates, kernel updates, October security patch
This is final build of LineageOS based on Nougat[/B]
Installation:
You need twrp recovery by @xenius9 : https://forum.xda-developers.com/lg-g-pro-2/development/twrp-recovery-lg-g-pro-2-t3318686
1. MAKE BACKUP!!!
2. Push baseband , ROM and gapps to sdcard (copy cm13 zip and LP Baseband to sd card)
3. Make WIPE dalvik, data,cache(from recovery)(advanced wipe in twrp)
4. Install lollipop baseband
5. Install ROM
6. Install gapps
Additional links:
KK Baseband and kernel - https://yadi.sk/d/nVx3rb7MpheN9
LP Baseband and kernel(bumped)+KK bootloader - https://yadi.sk/d/_hz4jdQhpheNn
How to Restore previous ROM:
1. if you have KK based Rom - flash KK Baseband and restore ROM from Recovery
2. if you have LP based Rom - flash LP Baseband and restore ROM from Recovery
How to install twrp on kitkat:
1. You need ROOT
2. Download and install this apk: https://drive.google.com/file/d/0B4kfGU1z_PCla2pxMW9ZZWgzX3M/view?usp=sharing
3. Download updated TWRP zip and put to internal storage or sdcard: https://drive.google.com/file/d/0B0LH2ajSZjDpalVsQmpoTDBfTUE/view
4. Open installed app, grant root access, flash recovery
5. Reboot into recovery (via apk or power off phone, press power and volume down button until lg logo come up, release buttons for one second than press volume up and volume down, select yes and again yes. This will not erase your memory if you have TWRP flashed)
6. Flash updated TWRP
7. Reboot into recovery again
How to install TWRP on lollipop:
1. Need ROOT
2. Download and install LG drivers from here : https://drive.google.com/file/d/0B4kfGU1z_PClSWVlY0FGWWJoVFE/view?usp=sharing
3. Download and extract this files: https://drive.google.com/file/d/0B4kfGU1z_PClQ3AyM2lKOGR1S3M/view?usp=sharing
4. Enable usb debugging under developer options
5. Connect phone to pc via MTP
6. Run d838recovery.bat (You will see chinese language, just press any button to flash recovery)
7. Allow usb debugging and grant root access
8. DO NOT REMOVE USB CABLE
9. After finishing process press any key to reboot into TWRP recovery
TWRP 3.2.1-0
link: https://drive.google.com/file/d/1ADfHyz8ii6w_QErKkzhrKexTQ4a6cAXp/view?usp=sharing
to update from older twrp just flash zip
Recommended GAPPS (google apps) : http://opengapps.org/
Older builds
RR
link: https://drive.google.com/file/d/0B4kfGU1z_PClbmJUTkdGUnpYYlU/view?usp=sharing
Lineage
link: https://drive.google.com/open?id=0B4kfGU1z_PClbURaNm5ST1FMeVE
lineage-14.1-20170624
link: https://drive.google.com/file/d/0B4kfGU1z_PClRk5XV0pSS0hfMk0/view?usp=sharing
lineage-14.1-20170613
link: https://drive.google.com/open?id=0B4kfGU1z_PClSlBJd0djcWFHcDQ
Resurrection Remix M
Resurrection Remix M
-Based on @xenius9 Cyanogenmod 13
-Everything works
-Tested on D838 (I don't have F350 to test)
link: https://drive.google.com/file/d/0B4kfGU1z_PClaU02WVZMNHB0OVk/view?usp=sharing
LineageOS 13.0 (rebranded and updated CyanogenMod 13 )
Bugs: Same as CM13 and RR
Installation: Same as CM13 and RR
Link: https://drive.google.com/file/d/0B4kfGU1z_PClWDlobDhlSmZCbzA/view?usp=sharing
kernel and device tree sources: https://github.com/coavasic
thanks to:
@xenius9
RESURRECTION REMIX team
CyanogedMod
G2/G3 developers
Good, I am waiting for nuogat.
If I am already using Lollipop, do I need to flash lillipop baseband?
Does it have superSU, is it root?
yplim2300 said:
If I am already using Lollipop, do I need to flash lillipop baseband?
Does it have superSU, is it root?
Click to expand...
Click to collapse
No need, it has root
So nice?
I will flash it later.
Finished test on d838.
Done, its work very well! Vietnamese 99%, but isn't problem.
Best rom for me. But it play not good with stock rom. I play Mobius Final Fantasy with medium graphic and frame, some time it freeze 0,01s ^.^. Stock rom no problem. Can you fix it?
Hi, I am running this Rom now. So far so good no issue yet.
I found G Pro2 little slow though perhaps the storage or ram management.
which gapp should i should for this rom?i always get "unfortunately, google play has stopped"
g2mantap said:
which gapp should i should for this rom?i always get "unfortunately, google play has stopped"
Click to expand...
Click to collapse
i'm using this without any problem
https://www.androidfilehost.com/?fid=24591000424961929
coavasic said:
i'm using this without any problem
https://www.androidfilehost.com/?fid=24591000424961929
Click to expand...
Click to collapse
You flash this with Recovery?
We should choose ARM or ARM64 to download?
Yes, arm
Sent from my LG-D838 using Tapatalk
UPDATE: Let it go for a couple of hours and it seems fine OMG.
UPDATE 2: The second boot up takes a really long time too. I'm still waiting for it to boot up.
UPDATE 3: IT BOOTED UP! But it took seriously long. Tested Soft Reboot seems quick, now testing full reboot.
UPDATE 4: Seems like I should never do a full reboot or shut down on this. Holy **** it's long.
Not having a great time flashing this... Using TWRP 3.0.2-0 to flash the ROM somehow it doesn't go past starting apps. Doesn't seem to boot on CM13 as well.
I've tried:
- Full wipe (system, cache, dalvik, data) and normal wipe (cache, dalvik, data)
- Installing the ROM with and without GAPPS
- Installing LP Baseband & Kernel (found in CM13 thread) with ROM with and without GAPPS
ROM would refer to either RR and CM13.
No SD card inserted, tried having SIM card in or out, the only thing I have not tried is to put the camera back in (stock ROM works without camera).
how to install.. just flash baseband and rom and gapps? thats it? ty
pato2015 said:
how to install.. just flash baseband and rom and gapps? thats it? ty
Click to expand...
Click to collapse
Installation is same as CM13, if you are on lollipop/cm rom you don't need to flash baseband, just rom and gapps, if you are on kitkat flash lollipop baseband in cm13 thread.
@coavasic how long does it take for your phone to do a full reboot? Seems like it takes 45 minutes for mine to boot.
DJCrapsody said:
@coavasic how long does it take for your phone to do a full reboot? Seems like it takes 45 minutes for mine to boot.
Click to expand...
Click to collapse
about 1 min. It's just on this rom or same with cm13?
coavasic said:
about 1 min. It's just on this rom or same with cm13?
Click to expand...
Click to collapse
It's the same with CM13. Doesn't happen on stock or modded stock ROM though.
It's a LG D838 32GB Variant.
Update: Seems like the camera does not work after hooking it back up (it works when I'm on Stock ROM), could it be because the system has already registered it as a non-camera device as I did flash it without the camera hooked up. But I did also flash the Stock ROM without the camera and hooking the camera back on still allowed it to work... Hmm....
Update 2: Device feels sluggish compared to when on the stock ROM, when lucky, app just lags for a second, when unlucky, it hangs for a few minutes then crashes.
@coavasic it's definitely a CM thing, I just reflashed a modified stock ROM (Sphinx Pro v5a) and it booted up in seconds.
coavasic said:
-Based on @xenius9 Cyanogenmod 13
-Everything works
-Tested on D838 (I don't have F350 to test)
link: https://drive.google.com/file/d/0B4kfGU1z_PClaU02WVZMNHB0OVk/view?usp=sharing
kernel and device tree sources: https://github.com/coavasic
I will create this rom based on CM14.1 (nougat) when we have all basic functions working on Cm14.1
thanks to:
@xenius9
RESURRECTION REMIX M team
CyanogedMod
G2/G3 developers
Click to expand...
Click to collapse
just as suggestion....stock camera for this rom is not really good perfomance becoz the image not so bright......i already try installing lenovo super camera version 3.6.7 and it give much better result...hope u can replace the stock camera app
Working Perfectly On LG G Pro 2 F350S, Thanks For Beautiful ROM
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1:
!NEW AND THE ONLY RECOMMENDED METHOD!
You must be on Oreo. Before flashing delete all your saved fingerprints and screen locks.
1. Reboot to bootloader (Bootloader must be unlocked)
2. fastboot boot recovery-xx.img (in ADB)
-> Grab official recovery from here: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
3. Wipe System/Data/Cache/Dalvik
4. Flash Lineage & TWRP Installer zip
-> Grab TWRP installer from the link above
5. Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)
6. Flash Gapps/MicroG (opengapps.org -> platform ARM64 -> Android 8.1 + Variant [IMO pico is your best pick])
7. Flash Magisk [latest] if you want ROOT (I bet you want!)
-> Grab Magisk from here: http://tiny.cc/latestmagisk
8. Reboot to System
How to update from previous build:
If you don't have permament TWRP, just follow the method above.
If you have permament TWRP:
Delete all your previous fingerprints (just for safety)
Boot to TWRP
Wipe Data/Cache/Dalvik (wiping is optional - but clean flash is always encouraged)
Flash Lineage ROM zip file
Flash Magisk
Flash Gapps/MicroG
Reboot
KNOWN BUGS:* No bugs right now! Enjoy bug-free rom!
If you have signal stability issues, try this:
Dial *#*#4636#*#*
Go to Phone information
Set Preferred Network Type from Unknown to LTE or WCDMA only
WHAT IS WORKING:* Everything else
LINEAGE BUILD CHANGELOG:
Code:
[FONT="Arial"]
[B]Most recent build (24.03.2018):[/B]
Fixed portrait mode
Enabled hal3 camera by default
Added doze
Lineage upstream
[B](22.03.2018): [/B]
Fixed double tap to wake (should only work for focaltech panel)
Rebased kernel to latest oreo source drop
Enabled cpusets
Lineage upstreams
[B](13.03.2018): [/B]
Fixed verity issue (builds now can be flashed without magisk)
Fixed Live Display
Fixed Substratum
Fixed ril issues
Lineage Upstream changes
[B](08.03.2018): [/B]
Fixed notification light (should work in call cases now)
Fixed slow charging
Fixed deep sleep issue
Added navbar toggle
Fixed goodix fingerprint issue (should work for all and all 5 fingerprint should be registered now)
Lineage Upstream changes
[B](06.03.2018): [/B]
Fixed led light
Added fingerprint gestures
Fixed Bluetooth name
Fixed battery capacity
Lineage upstream changes[/FONT]
Have fun with LOS!
Q&A
What does NIGHTLY mean?
Nightlies are automatical builds (every few days), so it mean you will have frequent updates, recent Lineage changes will be present in a rom. Also fixes and new stuff will come faster!
How I can go back to stock?
Grab Mi A1 tool from here: https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857.
Install it in your PC, enable USB Debugging on your phone, plug phone to PC
Click Flash Stock ROM button
Click Download ROM and wait
Click FlashAll. Your phone will reboot to fastboot and it will start to flash stock
[You will loose all your data, so backup is encouraged]
Do I need to downgrade to Nougat before flashing?
Not anymore It's advised to flash from Oreo
After update my FP don't work, wat to do?!
Make a clean flash using method from OP. If clean flash won't help, try: https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
Is Dolby working on Lineage 15.1? How to install it?
Just download Magisk module and enjoy!
My mobile signal is unstable. Is there a way to fix it?
Yes, see a workaround from OP
Why Selinux is permissive, not enforcing?
In unofficial builds Selinux is permissive. If the build goes official, it will have Selinux set to enforcing. Don't worry, just wait for official version!
Is this rom stable enough to be a daily driver?
Depends what you need. Check buglist - if these bugs don't bother you - it can surely be a daily driver
When new build will be avaible?
Don't ask for ETAs. Developers are working hard (in their free time!) to fix a bugs - we just need to wait patiently.
Some users are experiencing wifi issues (myself included). How can i fetch the log?
Steps to reproduce: Turn off bluetooth. wait a moment... wifi will start dropping connection a lot. To fix, just turn on BT again.
Headphones do not work.
Headphones are working!
By the way. I found a bug. The equalizer don't work correct. Everytime when you skip a song you must tap the bass regulator again in the equalizer app. When you don't do it, it plays without bass.
konradit said:
Headphones do not work.
Click to expand...
Click to collapse
Everything fine here, try to reflash
Installed and used for 24 hrs with no apparent problems. No fingerprint bug.
All the other bugs reported in OP exists.
Returned to Stock since I found it a bit smoother.
I will wait for a more stable official build
Good work so far
still
rasputine said:
still
Click to expand...
Click to collapse
Are you using the deadman twrp? I got that using other TWRP versions.
goofball2k said:
Are you using the deadman twrp? I got that using other TWRP versions.
Click to expand...
Click to collapse
Yes I'm using deadman's twrp
rasputine said:
Yes I'm using deadman's twrp
Click to expand...
Click to collapse
Did you reboot after doing the data wipe?
Can I install LOS 15.1 without flashing magisk? I have tried this and had bootloop before any lineageos bootlogo
radogost said:
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1: There's a few working methods. First, most popular one:
....
Third, last one:
Boot to the recovery (same recovery as method above)
Wipe system and cache ( data is optional if your are on Oreo)
Check which partition you are on (A or on partiton B)
Flash the rom on one of the partitions
Flash the twrp installer zip
link: http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
Reboot back to the recovery
Switch to the second partition
Flash GAPPS/MicroG and Magisk
Reboot
Click to expand...
Click to collapse
Sorry to pick this up again but the last method implies that TWRP will be installed permanently as default recovery, right? I was successfull only with the first method however I always end up in LOS recovery when try to enter recovery with Vol-up+Power after everything is installed.
I'm sure we all agree that this whole recovery mess needs to be sorted out quickly. Even experienced users are hitting snags and flood the board with questions .
goofball2k said:
Did you reboot after doing the data wipe?
Click to expand...
Click to collapse
Yes sir
i face the same issue with any methond i am using.
in some cases i am unable to install all the zips and in another case i am unable to install only magisk(error 1)
i followed exactly the steps.
any suggestions?
I'm not sure why the issues. I followed the steps in the OP, except I didn't flash TWRP, I just boot to it temporarily.
I did the following:
Flashed 7.11.18 ROM using MiFlash.
Booted into the ROM, set it up minimally.
Rebooted to fastboot, unlocked bootloader
booted temporarily to deadman TWRP, wiped system/cache/dalvik/data (just to be sure it is completely clean)
rebooted and then booted back into deadman TWRP
flashed LOS.
rebooted and then booted back into deadman TWRP
Flashed gapps and magisk.
rebooted to OS.
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Flashed from 8.1.10 without any problems...
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
t0per666 said:
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Click to expand...
Click to collapse
Tornado95 said:
Flashed from 8.1.10 without any problems...
Click to expand...
Click to collapse
Hmm so which one is telling the truth? ??
Sent from my Xiaomi Mi A1 using XDA Labs
Lineage 17.1
Custom ROM for the LG G7 ThinQ
WARNING: Discontinued
No more Updates from me
This is Lineage 17.1 (Android 10) ROM designed for the LG G7 ThinQ. It was designed with the help of @thenotonly and @SGCMarkus and without them this would not have been possible. Thank you guys for all your help!
Supported models:
Anything that can go into Fastboot
(exept T-Mobile model G710TM and Korean users will have a hard time following the guide)
Warning: You need to have Android 9.0 Stock pre-installed.
Warranty Void:
I am not responsible if you are late for work, missed an important call, got yourself stuck under a rock or break your TV with a wii remote. That also includes turtles. Make sure everything important is working for you before you decide to use this ROM as a daily driver.
Click to expand...
Click to collapse
What is working:
Auto-brightness
Camera
Calls
DAC Controls
FM Radio
NFC
Bluetooth
WiFi
SDCard
Always on Display
Vibration
Most stuff i haven't mentioned
What are the Bugs:
Hotspot Fixed
Bluetooth Audio (Workaround)
USB Hotspot
The ones that are still hidden
Click to expand...
Click to collapse
Download link:
There are 2 Versions. One with Google apps (Gapps) pre-installed and one without Google apps (Gapp-less) witch is for people who dont like Gapps and want an alternative like Nanodroid (Not included).
Google Drive Folder for the LIneage 17.1
Click to expand...
Click to collapse
Installation:
Step 1: TWRP
Backup any data you have (including music, photos, etc)!
- You cannot do that in TWRP!
FIrst you need to boot TWRP. You can refer to the Guide right here
TWRP Guide for the LG G7 ThinQ < -- Link
Once you meet all the requirements boot into TWRP and proceed to step 2
Step 2: Installing
In TWRP go to Wipe -> Format Data. ( This will wipe absolutely everything on the phone.)
Connect your phone to your PC.
Download Lineage 17.1 Installation zip file from Google Drive and copy it to your phone
In TWRP go to Install -> Find your zip file -> Install it
Once done reboot the phone
Done
Step 3. Install Magisk (Optional)
Make soure you have successfully booted into LineageOS
Reboot to bootloader
Boot into TWRP using "fastboot boot"
Download Magisk zip file from the official Magisk XDA thread (Google it) to your phone
Install Magisk zip
Reboot to system
Done.
Click to expand...
Click to collapse
Congratulations! Now You have LineageOS installed on your device! WooHoo! :victory:
Sources:
https://github.com/LameMonster82/android_device_lge_judyln
https://github.com/LameMonster82/android_device_lge_sdm845-common
https://github.com/LameMonster82/proprietary_vendor_lge
https://github.com/TheNotOnly/android_kernel_lge_sdm845 (Kernel by @NotTheOnly)
XDA:DevDB Information
LineageOS 17.1, ROM for the LG G7 ThinQ
Contributors
LameMonster82, @thenotonly,@SGCMarkus
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9.0 pre-installed + TWRP guide
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 202200218
Stable Release Date: 2020-02-18
Created 2020-02-19
Last Updated 2020-04-17
Reserved
Changelog 2020-04-18
- Updated Gapps
- Fixed Bluetooth bug
- Updated Security patch
- Switch Kernel
- Added OTA Updates support (20200401 and up versions)
- Some other changes I forgot about
Changelog: 2020-03-02
- Updated Gapps
- Fixed Hotspot
- Fixed some issues with the LED
Changelog: 2020-02-18
- Initial commit
Is there a working AOD?
FluffyDiscord said:
Is there a working AOD?
Click to expand...
Click to collapse
Yes there is
Does GCam works? 6.2 version
This being unofficial, how do we get updates and how are they installed?
does vibration works?
It does not start, it starts defront the rom stock, as if nothing had been installed.
Modelo LG G7 Thinq G710EM
HimikoMw said:
It does not start, it starts defront the rom stock, as if nothing had been installed.
Modelo LG G7 Thinq G710EM
Click to expand...
Click to collapse
I answer myself, it is necessary to have android 9, but of the European version
Stvn77 said:
does vibration works?
Click to expand...
Click to collapse
It's not in the "not working" list so it works.
Does the aod work the same as the official system?Use a second backlight?
Hi guys i got the G710N korean version. how can i root and install this rom? do i've to convert to another firmware?
First Thank You for such great ROM!
I think for now there is no way to root this ROM on korean version. I tried to Install this Rom, next I changed with LGUP only boot_a using partition.dl for flash boot from ULM 11g ROM to unlock fastboot, flashed twrp (after this step I was able to boot stock ROM from slot a) and installed magisk from TWRP to boot_b which is used by LineageOS (select slot b in TWRP) after magisk install bootloop. Tried also flash only boot_b with ULM 11g boot same result.
I think there is problem with booting this with any other boot installed.
Aseiel said:
First Thank You for such great ROM!
I think for now there is no way to root this ROM on korean version. I tried to Install this Rom, next I changed with LGUP only boot_a using partition.dl for flash boot from ULM 11g ROM to unlock fastboot, flashed twrp (after this step I was able to boot stock ROM from slot a) and installed magisk from TWRP to boot_b which is used by LineageOS (select slot b in TWRP) after magisk install bootloop. Tried also flash only boot_b with ULM 11g boot same result.
I think there is problem with booting this with any other boot installed.
Click to expand...
Click to collapse
You can't keep twrp with lineage you have to Fastboot boot Twrp image and flash magisk zip
SELinux permissive? enforcing?
mr3p said:
SELinux permissive? enforcing?
Click to expand...
Click to collapse
Permissive
they know which version of Gcam works in this rom (lineage os 17.1)??
Thank you very much. It's great to see some progress on this phone. Works on G710EAW.
HimikoMw said:
they know which version of Gcam works in this rom (lineage os 17.1)??
Click to expand...
Click to collapse
These are the ones that are working for me...
LGN2_MGC_6.1.021_MI8_V1d
LGW2_MGC_6.1.021_MI8_V1d
theParanoid04 said:
These are the ones that are working for me...
LGN2_MGC_6.1.021_MI8_V1d
LGW2_MGC_6.1.021_MI8_V1d
Click to expand...
Click to collapse
Thank you, you know why the photo is not saved when the HDR is activated, it stays in processing HDR +, in the LGW2_MGC_6.1.021_MI8_V1d.