Database Users

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.

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks

I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?

same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J

Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.

It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje

Can't boot to recovery.

Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.

First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.

I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.

I'm stumped on this (Rebooting into TWRP)

I've had this happen before on other phones, usually fixed by just installing a different rom or restoring a backup. Not here.
I finally unlocked my bootloader on the XT1607 (the Motorola site just randomly worked one day), installed TWRP & the 7.1.1 Soak Test (from here). I forgot to backup 6.0.1, so I backed up the soak test which was booting and working flawlessly. I was using it for a while, but I did a factory reset inside TWRP and it randomly said "cannot mount storage" and when I rebooted, it was into TWRP. It wasn't working at all, so I got LineageOS 15.1 and flashed that. Same error, "cannot mount storage" and back to TWRP. I went into Wipe>Format Data and then reinstalled Lineage. The "cannot mount storage" error was gone, but still booting into TWRP. I tried AOSP Extended, CyanogenMod, Paranoid Android. roms with gapps, roms without, with & without supersu or magisk. Nothing worked. So then I thought that restoring my backup (of all partitions) would fix the issue. It didn't, still booting back into TWRP. I'd also like to mention that plugging the phone in still worked, I can view the files in file manager, sd card works, etc.
So, no clue what to do here. What's wrong? It all started with that simple factory reset from twrp.
edit: I found that if I boot into bootloader and press start it will go into android, but hardly a permanent solution.

Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine

sumit1327 said:
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
Click to expand...
Click to collapse
Heyyy, thanks man. Worked like a charm.

Why can't i use any rome except OmniROM? The Phone does not boot at all.

Hi there folks!
Sorry if i open a thread, probably you've discussed somewhere before about this problem that i'm experiencing.
My OnePlus 5 basically works only with omniROM, it doesn't boot at all when i try to install another one.
I tried with this:
https://forum.xda-developers.com/oneplus-6/development/rom-aospextended-rom-v5-7-t3825642
and this one:
https://forum.xda-developers.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886
I followed every step (About CRAndroid), radio firmware 5.1.5 + TWRP 3.2.3 + Gapps + Magisk 17.1 and No Verity v3 (First try without noverity, second using it)
and i followed also every step neeeded in AOSPExtended rom.
When i try to boot the phone, after the OnePlus logo, nothing happens. The phone reboots in recovery mode, that's it.
If i repeat the same steps with OmniROM it works all fine, except Magisk. If i flash Magisk on the Omni it doesn't boot, if i flash SU it works.
Could it be something related to the encryption/Decription of the device?
When i go into TWRP it doesn't ask me for a pattern or a code. It should be decrypted, right? (i'm a bit confused about that).
I purchased the phone on Gearbest, could it be a particular version of the phone that doesn't allow me to work properly with roms?
Help

did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others

Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.

azretier said:
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Click to expand...
Click to collapse
Actually when the phone arrived i've just unlocked the bootloader and installed a custom rom....what's the purpose of this?

moffa~ said:
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
Click to expand...
Click to collapse
You....you're a good guy.
I did the command you said, then i booted into TWRP, flashed AospExtended, Gapps Pico and Magisk 17.1 - after reboot it has been stuck @ 1+ logo, then it rebooted again (as always when it doesn't work) and i said "ok here we go again in the TWRP-loop" and INSTEAD it booted rom! Yes!