Database Users

My backups are not working....

Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.

what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also

thesystem90 said:
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Follow full wipe procedures, have the same recovery you made the backup with, and try again.

rugmankc said:
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
Click to expand...
Click to collapse
I flashed the stock firm. Soft brick averted. Did the same goo manager recovery method, but now i'm thinking of flashing that cwm as ppl have reported the same nandroid backup issues with twrp. My version is 2.5.0.2. I will keep trying to get twrp for a while with others users till i get sick of it (semi twrp fan). Any further advice would be cool. Oh and I did a factory twrp wipe the first time this problem occurred.

I wipe data caches and system before flashing. No more advice. Had newest TWRP hang on Team Win screen. Several manual reboots into recovery till it worked. Maybe I better do restore to see if it works.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta

[H] Flashing issues

about a week ago when 4.4 roms surfaced for mako, i wanted to try one out. when i did it failed, so i read that you had to either update TWRP or use CWM. so i tried to update TWRP with goo, and goo is down i guess, so someone posted a flashable zip of the newest TWRP(2.6.3.2) and CWM(6.0.4.4) so i got them both, and flashed the TWRP, and it flashed the 4.4 roms. and i used my nandroid to go back to 4.3(Carbon ROM) and now it fails when i try to flash a new nightly (i facrtory resetted) and it failed on my backup too, so i flashed CWM, and rebooted and it fails on everything too. (new nightly, and a copuple of roms i had been meaning to try) and i just fastbooted the official image from teamw.in website (2.6.3.3) and its failing on nightlies, but restored my backup.
what can i do to make it flash again?
should i downgrade to TWRP 2.6.3.0, i think that is where i was and it would flash, I THINK. lol.
please help.

[Q] Unable to restore using Twrp or Cwm

Need some help guys. Havent been on here in some time. So I have the Telus variant s4. I updated to the ota kitkat when it launched but found that the battery life was terrible after the update. I thought I'd try out a couple custom r8ms and see if I found a better result in battery life. I rooted the phone and decided to try gummy 4.4.2. Prior to that I installed twrp recovery which I have used with other phones in the past, which I used to dona backup of the stock rom in case something went wrong. I then flashed the rom no issues and played with it for a couple hours. I didnt like it much and decided to restore using my backup. Twrp would not do the restore, when I selected the file and dragged the slider Twrp would just reboot. I tried a bunch of times with the same results. Ni downloaded and tried Cwm but that wouldn't even recognize the backup file. I read somewhere that I could use mobile Odin which would recognize the file if I renamed it to recovery.tar. Tried that and it didnt work. Now Twrp wont recognize the renamed file and dont remember the original name. The phone works with the gummy build but I want to get the stock or something close to it. I also noticed that when I poweres if off to charge it says kernel is not seandroid enforcing. Set warranty bit kernel. I need some help here. I havent a clue what I should try next. Ive been reading all night till 4am couldn't come with anything. Help!

It sounds like the twrp nandroid was corrupted. Fyi, it's a zip file so if you rename the tar to zip twrp should recognize it. Twrp and cwm nandroids are not compatible so a nandroid made in one will not work in the other.
At this point I would make a nandroid of your current rom in twrp and restore it just to confirm you have twrp working correctly. Then I'm afraid you're going to have to recreate your stock from scratch.
Sent from my Nexus 5

[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.

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.