So I run my Galaxy S4+ GT-I9506 on Cyanogen 13.0 and I downloaded the latest update cm13.0 20160113 Nightly today and everything went smooth until after the optimization of apps. And when it said cm settings storage it just frooze and rebooted. And now Im stuck...
I've tried to wipe data/factory reset it just blinked very quickly and nothing happends
wipe cache partition nothing
tried to install the update again nothing
So... Im stuck in Cyanogenmod Recovery and I dont know what to do
anyone?
Tried that with odin fails all the time. What recovery should I use?
TWRP. Bu you need Odin to flash it. Unless you can flash it with CM recovery.
Cant do that, cuz Cyanogenmod do not support sdcars :crying:
What about internal memory? You might also be able to push it through adb.
Can you flash this version of TWRP using Odin: https://twrp.me/devices/samsunggalaxys4ltea.html
Related
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
so decided to update my N4 from 4.3.1 to 4.4? from 10.2.1 stable to 11 nightly.. booted into TWRP, and tried installing CM11, but FAILED. wiped Cache, Dalvik Cache, and Factory Reset. Still FAILED. Wiped System too. Still Failing. Any ideas?
The CM 10.2.1 zip doesnt work either. Originally i had updated to 10.2.1 and noticed it was still android 4.3.1 XD just.. updated? so decided to go CM 11 then this happened T_T
any ideas?
-----------------------
so i found out CM11 doesnt work with TWRP. had to use ADB to flash recovery to CWM then flash CM11....
Sounds like you need to update your recovery
Sent from my Nexus 4 using Tapatalk
Happened to me also, you need to update to the latest version. I have CWM but for TWRP is probably the same.
yeah o well. i flashed to CWM recovery (newest one prob) and it worked. running CM11 now.
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.
EDIT: the problem is solved, see my last post
Hey guys,
I'm not new to installing roms, as I did with my SGS 2 before. But I haven't done it for a long time and it's the first time I do it on my SGS 5... with no success at all.
The problem is that, out of all the roms I've tried, none of them boot up entirely without crashes. I've followed the instructions to the letter and I'm not sure what I'm doing wrong.
Here's what I had before starting to fiddle:
SGS 5 G900F, no specific carrier, bought in Europe
stock android/touchwiz 5.0, never rooted or anything
Here are the roms I have tried:
cynaogen 5.1.1 12.1 20150508 for klte + these gapps http://teambliss.x10host.com/BlissStalk/Gapps/ --> stays blocked on the samsung logo forever
BlissPop 5.1.1 v3.3 20150515 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> google newstand and another google app are crashing in a loop during the setup, I can't tap any button
PAC 5.1.1 20150503 for klte + pa_gapps-stock-5.1-20150418-signed or pa_gapps-modular-full-5.1-20150418-signed --> the install wizard application itself is crashing in a loop
THe kernels I've tried:
KT-SGS5-LP5.1-AOSP-G900-05.02.2015
boeffla-kernel-2.0-beta8-CM12.1-g900f.recovery
My recovery:
twrp-2.8.6.0-klte (flashed with Odin, it works fine, and I could boot the stock rom without problems with it)
Any idea about the cause of the problem?
Thanks
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
*Detection* said:
I guess if you are not new to stuff like this, you have 100% wiped everything before flashing in TWRP recovery, and factory reset / wiped caches after flashing the ROM and Gapps?
Click to expand...
Click to collapse
Yes, before and between installing different roms, I wiped everything: system, cache, dalvik, internal storage
I've also flashed twrp previous version 2.8.5.0, and philz touch recovery. They all work fine, but still can't boot any rom
Strangely, I now works using this version of CM 12.1: http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-12-1-android-5-1-t3066252
I have no idea why I had all these crashes and boot problems with the other 3 roms.
Cheers
Odd.
I downloaded Imperium ROM from a thread on xda and installed it. I wiped data, wiped cache and dalvik and installed zip. Then I rebooted and it showed a downloading screen, after a little bit of research it's called download mode or ODIN mode. Now what's happening is whenever I try to reboot, it shows the S4 i9505 screen (i think it's called a splash screen, thats what someone called it) and freezes. After about 10-15 seconds, reboots into recovery. I've got CWM installed and I've ran out of ideas. The volume buttons are not being touched and for some reason recovery and download mode are always being booted into, never the OS.
I'm also new so anything I've done wrong, I'd love to know.
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Lennyz1988 said:
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Click to expand...
Click to collapse
Update I tried to install albe95's s6 port. I've noticed something and it's that both ended up with Statuc 7 or some word that started with "S" and had the number 7. Googled that and turns out it's bad. I formatted /System and installed the ROM, it worked!
I guess there was just no OS to boot into. Going to try installing Imperium now.
Status 7 errors can occur if the recovery is outdated. What recovery is on the phone?