I have a D801 running an old CM12 (Lollipop 5.0.2 16 June 2015 nightly build), with TWRP v2.8.2.1
Can I install the latest August 20 snapshot CM13 over top of the CM12, assuming I first update TWRP? No problems with old KK-based bootstacks? Don't want to brick this phone or lose the IEMI.
Or should I first take the phone back to its original LG stock KitKat? TIA
Never mind. It worked. I installed the latest TWRP 3.0.2-1 and rebooted back into TWRP. Then I flashed CAF Bootstack for the D801, followed by the August 20th snapshot and the Nano GApps from Open GApps. All good.
aquatarkus said:
Never mind. It worked. I installed the latest TWRP 3.0.2-1 and rebooted back into TWRP. Then I flashed CAF Bootstack for the D801, followed by the August 20th snapshot and the Nano GApps from Open GApps. All good.
Click to expand...
Click to collapse
I LOST MY IMEI can you help
Make sure to flash the correct CAF boot stack for your phone model (which I assume is the D801).
Sent from my LG-D801 using Tapatalk
aquatarkus said:
Make sure to flash the correct CAF boot stack for your phone model (which I assume is the D801).
Click to expand...
Click to collapse
Please am new here can you link me some correct CAF for d801
There are links in this video https://youtu.be/_7JunuDssy8
**make sure to change the filename in the URL when you download, so you get the correct files for D801 *** If you install the wrong files, you will brick your phone.
Sent from my LG-D801 using Tapatalk
download it and flash but still the same please any ideas
Related
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temasek's version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
sanjsrik said:
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temaseks version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
Click to expand...
Click to collapse
I tried to flash latest nightly with MultiROM, result is bootloop for CM12.
You can make CM12 as primary ROM and keep KitKat based ROMs as secondary
(Clean flash is needed for above statement)
sanjsrik said:
Are there any CM12 builds (or variants) for OnePlus that are compatible with MultiROM? I got so confused reading how to flash Temasek's version that I gave up. There was one that was compatible and it worked until the latest firmware was released. Just wondering if MultiROM is worth it for CM12 builds?
Thanks in advance.
Click to expand...
Click to collapse
I was able to do this.
I used the following workaround:
1) Install MultiROM
2) Backup your primary ROM
3) Flash the Lollipop ROM as primary ROM
4) Backup the Lollipop ROM
5) Restore the backup of your CM11S? ROM
6) In the TWRP recovery go to MultiROM -> add ROM -> from backup
7) Enjoy!
I'd like to include a link where i found this but unfortunately I can't (I need 10 posts). I do know that it is the first/second link if you google this: [WORKAROUND - MULTIROM] How to avoid "error executing updater binary in zip"
But if you're interested PM me.
No need to do any of those swapping ROM things anymore
Search keyword multirom in the temasek thread and you will find multirom edited ROMs that you can add and they will work. Just make sure you install the multirom app from play store and update to the latest on your primary ROM if there are any updates.
Only requirement is that your primary ROM needs to have a custom kernel. You can flash ak kernel on your primary. Make sure you get the right version for whatever ROM is your primary. Or your can simply install the kernel from within multirom app if you don't care about custom features with custom kernels and that will work also
Sent From Lollipopified Bacon Goodness!
Hello,
I have a perfectly working moto G 4g with cyanogenmod, and did the install very easily the first time. I am stoked with it so when my mother asked me for a new phone I got another MotoG 4G, and went directly to install TWRP and cyanogenmod... BUT :
- when I want to flash Cyanogenmod build zip, TWRP tells me the version is not supported by this cyanogen build.... apparently it wants version 0x411A and nothing else. The only version available on TWRP website is the newest 0.3.2.0 ....
- I have tryed another twrp version found online (a 2.7.8 not official) and it fails again to install Cyanogenmod, saying the TWRP version is not correct.
Where can I get the correct 0x411A version of TWRP ? Or is the message actualy is about something else ?
Best regards and thanks in advance for your help.
I was confusing Bootloader version and TWRP version. I used a tool found on XDA that has updated my bootloader.
Then i was able to install cyanogenmod but was stuck on the logo for the first boot.
Updated TWRP to the latest one and trying again, flashed darvin cache, and i am flashing nightly cyanogen+gapps.
I hope it'll work this time
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:
I am not responsible for anything that may happen to your phone as a result of installing this rom. You do so at your own risk and take responsibility upon yourself.
About:
The Stock ROMs posted here are extracted from official LG KDZ files for the T-Mobile LG G Pad X 8.0 | v521 | b3.
Only change made on ROM was to prevent stock recovery from restoring itself
ROM includes modem/radio, however you can also manually flash the modem/radio from here
root is NOT included. However feel free to flash your choice of root with Magisk, SuperSU, or any others at anytime to get root.
Info:
Android version: 7.0
Kernel version: 3.10.84
Build number: NRD90U
init.d support
forceencrypt disabled
Requirements:
Your device must be or have been on 20f or newer at one point or another. If your device has always been on Marshmallow and has never been updated to Nougat by kdz or OTA, you'll need to upgrade to Nougat and re-root first. (Thank to monkeyass408 for verifying)
You can follow this guide to do so: Guide to Update V521 LG GPAD X 8.0 to 7.0 and Root
You must have TWRP or another custom recovery already installed in order to flash this rom.
Instructions:
Download the version of your choice from below.
Boot into TWRP and make a backup. You may want to remove any lock screen security before doing this as restoring with lock screen may cause unexpected issues.
Optional: Wipe data and/or system. As of TWRP 3.1.1.0, you will want to reboot recovery after wiping data/system before flashing as TWRP may get stuck on a black screen during the flashing process without a reboot.
Flash ROM.
Optional: Flash the disable OTA zip to prevent and disable official LG OTA updates & notifications
Reboot and you should be all set.
Downloads: (Listed by Sofware version / Android security patch level)
Note: As of 2017-02-21, TWRP 3.0.2-0, will sometimes give the error "Failed to map file" when attempting to flash this rom. Rebooting TWRP will resolve it and allow you to flash the zip.
v52120n >> Apr 1, 2018
v52120m >> Feb 1, 2018
v52120l >> Dec 1, 2017
v52120k >> Oct 1, 2017
v52120j >> Aug 1, 2017
v52120i >> Jun 1, 2017
v52120h >> Apr 1, 2017
v52120g >> Feb 1, 2017
v52120f >> Dec 1, 2016
All Stock ROMs Folder
Disable Stock OTA
Note: This should prevent you from verifying and updating via OTA. The OTA notification may still pop up but it should go away when you attempt to update after flashing this. I haven't fully tested this so backup first and don't be surprised if it returns you to full stock.
Credits/Thanks:
tungkick for the initial root method
shabbypenguin for TWRP on the LG G Pad X
All other devs who make rom building possible
Reserved - Unlikely I'll need it but who knows?
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
channeledbymodem said:
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
Click to expand...
Click to collapse
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
supaet said:
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
Click to expand...
Click to collapse
Hmmm I haven't had any issues with my 5ghz on my tablet. The roms are ripped straight out of the kdz files so any changes between 20g and 20f are strictly from LG/T-Mobile. Although I do recommend keeping the modem version and the rom version the same, I am curious, would you be able to test and see if it still happens if you downgrade the modem version to 20f while you're on the 20g rom?
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
.fenrir said:
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
Click to expand...
Click to collapse
Appreciate the update Thanks!!!
A bit quicker this time around. 20k has been added.
Amd4life said:
Appreciate the update Thanks!!!
Click to expand...
Click to collapse
No problem.
.fenrir said:
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
Click to expand...
Click to collapse
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
monkeyass408 said:
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
Click to expand...
Click to collapse
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
.fenrir said:
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
Click to expand...
Click to collapse
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
monkeyass408 said:
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
Click to expand...
Click to collapse
Glad to hear it worked out for you. I stand corrected on it being flashed over Marshmallow so I've updated the first post to reflect that. Thanks for trying and verifying it.
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Char_Liu said:
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
Click to expand...
Click to collapse
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
channeledbymodem said:
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
Click to expand...
Click to collapse
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
Thank you for the update.!
Appreciate the update
Thx a lot
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
I have always had excellent battery life but after a dirty flash of v.l it is terrible. I am losing 30% overnight. Can I roll back to v.k? I am reluctant to clean flash v.l; it's a lot of work getting back to normal.
Since it appears to be quite some trouble to obtain the last release of Lineage 15.1 for the A9 I share a copy of it
Flashable ZIP
484,78 MB
hiae
LINK (expires 01-12-2019)
(direct download from dropbox)
https://ea1.eu/LOS-hiae-20180625
ALTERNATIVE LINK
(Tresorit)
https://ea1.eu/LOS15-1_signed
Make sure you're on the last firmware and TWRP versions
Obtain GApps from www.opengapps.org (Android 8.1 arm64+)
Good luck and I salute our dead device
This is for hiaeuhl, right?
15.1 should be universal, u can use it on both versions
Is rom stable?
depends on what u mean by "stable" yeah it works and runs fine, but the main issue with Los 16 is u don't have any audio while call
Do I need to be on nougat firmware before I can flash this rom?
Sent from my 2PQ93 using XDA-Developers Legacy app
you should have the latest stock firmware + bootloader etc. installed before u flash it ( i think )
solved said:
you should have the latest stock firmware + bootloader etc. installed before u flash it ( i think )
Click to expand...
Click to collapse
True. Flash the latest stock firmware and boot all the way to setup. This way all partitions will be correctly mounted. Then flash TWRP followed by the ROM and GApps
Installation Package Error
I have an hiaeul phone, and i found an error in the update-script file. It attempts to mount a directory that does not exist. To correct, open the file and replace all occurrences of "/dev/block/platform/soc.0/7824900.sdhci/by-name/system" with "/dev/block/platform/7824900.sdhci/by-name/system".
NOTE: I am not sure if this holds true for other variations of HTC One A9, only edit if you get an error.
I found the problem
After installing Google framework service , have problems
All the links is dead, can you update the links
Cicada_3301 said:
All the links is dead, can you update the links
Click to expand...
Click to collapse
I would like to download because I flashed twrp and wiped data but did not backup and am on version 2
I don't know if it works but I found a download link for Lineage 15.1 "lineage-15.1-20190724-UNOFFICIAL-hiae.zip" https://androidfilehost.com/?fid=6006931924117923121