Database Users

[HELP THREAD] I9505 S4 + Omega ROM + KT-SGS4 TW

Hi, as XDA doesn't allow me to ask this neither on the Omega Thread and on Ktoonsez Thread of the S4 development, I'l have to ask it here untill I have 10 posts.
I have a i9505 Galaxy S4, (I had an S3, a Note II with Omega, and an S2) and installed Omega 5.0 through the way ::indie:: indicates on Omega's thread which is as follows:
Installation Instructions:
1. Backup all your app and data so you can restore them to Omega v5.0 (I use Titanium Backup)
2. Make a full wipe (Data, System, cache, dalvik Cache) from recovery then boot to download mode immediately and flash Stock I9505XXUBMEA with odin
Get the firmware from here.
Flashing stock XXUBMEA is needed to make wifi work. Many users reported that it took them many flashes with odin to make wifi work on stock firmware.
3. Make sure all are working ok with stock XXUBMEA firmware, check if wifi + LTE (if your provider supports LTE) are working ok
4. Flash TWRP Recovery with odin, get it from here
5. Boot to TWRP Recovery and flash Omega Rom.
Wipe data from recovery is not needed, wipe your data only if you want to.
6. If LTE is not working flash this zip: I9505_Enable_LTE.zip
Ok.
Everything working great!
But then I installed Katoonsez GREAT WONDERFULL Kernel, but the device got so hot, and I could observe throught KTweaks that my cores were allways ever online and the clocks weren't adjusting well.
This happened with every governor and scheduler.
Then I could install every Kernel including reinstalling the rom with the original kernel afterwards that this happened. The only way to make it stop was going to recovery (TWM didn't helped, but CWM allowed me to format every folder like system folder) and only after formating everything, and installing XUAME2 stock ROM through Odin would make my phone not boot so warm again.
It happened several times and got me lots of flashings to dyscover the above procedure to make the phone not get warm.
Once, it worked I don't know why, with Omega 3.1 and KT-SGS4-TW-JB-INTL-05-30-2013. Actually it had the same issues, but specifically with intelidemand governor it suddenly started to work fine for the first time. That was when I realized why Ktoonsez Kernel was so great! it allows you to set so many parameters I had never seen in another Kernel! I succefully updated to T-SGS4-TW-JB-INTL-06-05-2013 and was the best week I had with a phone ever!!!
The battery was almost as good as with my undervolted Note2!
Then yesterday I tried to update to Omega 5.0 and KT-SGS4-TW-JB-INTL-06-06-2013 and all the madness started again :crying::crying:
I'm stuck in the loop and I simply don't know what in the process is making this happens. I tryed to flash in sevral different ways, but in every single way this happens.
I tried flashing the kernel in the same CWM session as I instal the ROM, I tryed doing separately, I tryed wiping wvwrything, I tried wiping only some things and not others, I tried fixing permissions and not fixing permissions after Kernel install (they recomend to fix permissions)...
Well, it is a nightmare!!! All I wish is to get my phone working as lovely as it was with Omega 3.1 again, but even installing the same files in the same way I did, I'm not geting it!
Please help!!!

i9505 Boot freeze/loop

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

Cant figure out how to install custom rom, without loosing root acces

Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati

Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).

antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?

Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.

SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!

Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.

antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.

No rom is booting up properly

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.

[Q] Factory reset every time ROM update?

Hi!
I use Google edition s4 ROM, and i really like it. But when it receives an update do i have to factory reset everytime? Im on 20150614, with CWM 6,0,4,7.
Id really really appreciate a fast answer
Also, if i wish to switch Kernel from Alucard to Googy-Max, is it ok to Wipe dalvik cache, and then flash kernel?
EDIT: the rom: http://forum.xda-developers.com/showthread.php?t=2557353

bump?

Dirty flashes should be OK, however the ROM thread you linked to should have provided the answer. Regardless, you really should change that recovery to TWRP. Clockworkmod is no longer being supported and people are having difficulty installing some custom ROMs with it.
Wiping cache is fine when changing kernels.

Thanks for the help
Btw. I dont know how to change recoveries? XD. Is it Just using Odin like with cwm? And do i have to remove cwm first / wipe device?

No, u can just flash ur new recovery through cwm

Okay. What is the preferred TWRP? Do you possibly have a link ?
Asking because i cannot find the S4 i9505 on their site?
EDIT: I managed to install it via the App they've made. It is much nicer than CWM. Thanks for the help both of you

Ok ive tried to flash 2 different kernels multiple times now.
Tried Googy-Max, and the phone wont boot android ?
Tried Hulk, and it took forever to boot, then rebooted immediately etc.
Am i flashing kernels wrong?, i did dalvik/cache wipe after the flash