Database Users

[Q] How to restore downloaded apps from back on different ROM

Hi Guys,
Just a quick question from a rookie.
I like changing custom rom since I rooted my LG G2 about a month ago and experimenting some custom roms on my LG G2 D802.
I have managed to successfully flashed few custom rom such, Paranoid Android, ClaudyFlex 2.4, Liquid Smooth and CyanogenMod. I always do backup on TWRP everytime I have fully restore all my app on each ROM i'm using. My question is, is it possible to restore only the apps that I have previously downloaded via TWRP? as I hate re-downloading again all the apps via wifi that sometimes take a very long time to fully restore from PlayStore.
Let say I'm now using CyanogenMod 11 with TWRP 2.7 recovery installed. I want to change my ROM to Pardus Classic HD ROM. Should I just simply restore from my back up (Pardus Classic HD ROM+Gapps+all downloded apps on .zip file) that I have done previously using TWRP recovery or should I clean wipe and install the Pardus ROM first, then do a restore of backup from TWRP backup folder after the Pardus HD ROM has been fully installed on my device.
Sorry for a rookie question... just enjoy the beauty of rooting devices and so keen to experimenting here and there...
Regards,
ePWT
LG G2 D802
CyanogenMod ROM
11-20140617- NIGHTLY
KitKat 4.4.3
Kernel 3.4.0-CM+

[Q] Custom ROMs not booting (boot loop)

I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.

VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant

v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.

VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.

Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.

[Q] lost IMEI after flashing Temasek's CM12.1 v. 14.9

Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
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.
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. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!

django e said:
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
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.
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. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
Click to expand...
Click to collapse
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.

kenny1991 said:
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
Click to expand...
Click to collapse
Thanks! I managed to restore the imei flashing stock lollipop. I initially downgraded because it seemed to me that all instructions were based on kitkat and not much information was available on lollipop. Just wanted to make sure I followed the instructions to the letter. Stupid me...
I tried to restore efs the way you describe it, but it didn't work out for me. Thankfully, things are back to normal now and I will flash cm12.1 directly from stock lollipop now.
Thanks for taking the time to help!

GT-I9505 not allowing any custom ROM after CM13??

Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...

1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.

Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.

Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...

Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...

mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.

It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...

I don't know. It's worth a try.

If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.

Updating from CM12.1 Nightly

Hay,
I already read the thread for CM13 on the LG G2 (d802). But actually I am kinda confused and I just want to go sure that I don't do anything wrong again. Currently I am using CM 12.1-20151114-NIGHTLY-d802 with Gapps. Today I wanted to update to the CM13 Release. I did what on the cyanogen site was written and flashed the CM13.zip and the gapps.zip, then wiped Dalvik and rebooted. Unfortunately i got a blackscreen and nothing happened. I rebooted into recovery and restored the CM12.1 backup I did before.
So if I understood the CM13 thread correctly, I do have to go back to LG G2 Stock ROM and update to Lollipop and then root and flash CM13. Or I do have to install another Bootstack(?), which is not recommended.
So what is this Bootstack and why isn't it recommended?
Thanks for your help!