Due to my low post count I can not post in development section.
After I flash Omega v23 rom, my phone is now stuck on the "Samsung Galaxy Note II GT-N7100" screen, and when I go into recovery and reboot, it would say that I do not have a OS.
I installed Omega using TWRP recovery from Omega v19.
What did I do wrong? I
kuromusha38 said:
Due to my low post count I can not post in development section.
After I flash Omega v23 rom, my phone is now stuck on the "Samsung Galaxy Note II GT-N7100" screen, and when I go into recovery and reboot, it would say that I do not have a OS.
I installed Omega using TWRP recovery from Omega v19.
What did I do wrong? I
Click to expand...
Click to collapse
have you read the installation instructions?
try to reinstall as the dev written on the thread
kuromusha38 said:
Due to my low post count I can not post in development section.
After I flash Omega v23 rom, my phone is now stuck on the "Samsung Galaxy Note II GT-N7100" screen, and when I go into recovery and reboot, it would say that I do not have a OS.
I installed Omega using TWRP recovery from Omega v19.
What did I do wrong? I
Click to expand...
Click to collapse
try flash with Philzz v5
chobztopz said:
try flash with Philzz v5
Click to expand...
Click to collapse
I did, that what I had in the first place, but the Omega v23 installation would freeze, and people on the thread said they solved the issue using TWRP recovery.
ended up format the internal storage!
the installation guide clearly says no need to format internal storage when coming from 4.3 Omega rom.
kuromusha38 said:
I did, that what I had in the first place, but the Omega v23 installation would freeze, and people on the thread said they solved the issue using TWRP recovery.
Click to expand...
Click to collapse
philzz v6 has trouble with aroma, are you sure installed v5 not the new philzz v6? i had no trouble installed it with v5
Related
I've been trying many things to no avail. I am able to get recovery on my i9505G (which I have read is built into the CWM version now for the i9505) and it seems to work fine. I have the 01/08 nightly CM11 on the phone, but whenever I reboot and select "recovery" it gives me this error. Sometimes if I hit the restart the device, it will boot into recovery correctly. I've even started fresh by wiping the entire phone and the multiple partitions (from having started on 4.2) and flashed a fresh 4.4.2 stock (rooted) tar through odin. From there I flashed the recovery, installed CM as I always have, but it is still happening.
What am I doing wrong?
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Joku1981 said:
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Click to expand...
Click to collapse
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
mrmartin86 said:
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
Click to expand...
Click to collapse
Coz u are installing CWM for i9505 no for i9505G maybe?
Joku1981 said:
Coz u are installing CWM for i9505 no for i9505G maybe?
Click to expand...
Click to collapse
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
mrmartin86 said:
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
Click to expand...
Click to collapse
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Joku1981 said:
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Click to expand...
Click to collapse
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
mrmartin86 said:
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
Click to expand...
Click to collapse
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Joku1981 said:
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Click to expand...
Click to collapse
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
mrmartin86 said:
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
Click to expand...
Click to collapse
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Joku1981 said:
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Click to expand...
Click to collapse
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
mrmartin86 said:
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
Click to expand...
Click to collapse
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
mrmartin86 said:
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
Click to expand...
Click to collapse
CWM 6.0.4.4 work fine on the i9505G. I use it on mine and have since it came out.
hi sorry for my english. so i have samsung galaxy s4 i9500. so i just installed cyanogenmod 11 20140222 nightly version. everthing was fine.Now i downloaded update 20140225 nightly update. i installed it but phone is not booting. it close after samsung logo. so i wipe data and cache. wipe everything. i try install rom but it still not booting. i use CWM 6.0.4.7 Advanced Edition / PhilZ Touch 6.15.4
sniper845 said:
hi sorry for my english. so i have samsung galaxy s4 i9500. so i just installed cyanogenmod 11 20140222 nightly version. everthing was fine.Now i downloaded update 20140225 nightly update. i installed it but phone is not booting. it close after samsung logo. so i wipe data and cache. wipe everything. i try install rom but it still not booting. i use CWM 6.0.4.7 Advanced Edition / PhilZ Touch 6.15.4
Click to expand...
Click to collapse
Already Tried to flash Perseus kernel?
Androiders96 said:
Already Tried to flash Perseus kernel?
Click to expand...
Click to collapse
no i didnt install kernel. i dont know how i do that. i installed cm 11 20140224 nightly version again and it works fine. i wonder what the problem is about last update?
sniper845 said:
no i didnt install kernel. i dont know how i do that. i installed cm 11 20140224 nightly version again and it works fine. i wonder what the problem is about last update?
Click to expand...
Click to collapse
Just CM Commit 20140225
See www.cmxlog.com/11/i9500/
Hi,
Yesterday I went to flash CyanogenMod 11 on my Galaxy s4 (GT19505) and it wouldn't work. The first time, it started then went to a black screen. I turned my phone back on to find it wouldn't boot up at all (I waited over 10 minutes for it). I can access recovery mode, and when I did it again, it said md5 couldn't be found.
I used Odin to flash the most recent CT auto root and then moved over TWRP (with Odin) and I had no trouble with these.
I accidentally moved TWRP 2.5 over instead of 2.7. I was running 4.4 KitKat on my phone. Could it be 2.7 isn't compatible with CM 11?
Help!?
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
3593483
Lennyz1988 said:
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
Click to expand...
Click to collapse
I'm using a stable version. I haven't downloaded any latest ones. How would i do that if I can't access the phone? Boot it to download then go from there?
are you sure you (even) flashed a (compatible) kernel?
Sent from my GT-I9505 using XDA Premium 4 mobile app on OmegaRom v19
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Manganese said:
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Click to expand...
Click to collapse
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
dwarfer66 said:
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
Click to expand...
Click to collapse
So I redid TWRP, now what about CM 11? TWRP uses the jfltexx in its name...do I just use Odin to move CM?
So, I installed TWRP 2.7 and it worked. All is good, currently enjoying CM!!!
Now the battery is saying it's at 0%...how do I fix that?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Did you wipe before restoring?
Lennyz1988 said:
Did you wipe before restoring?
Click to expand...
Click to collapse
No. I just tried it and the same problem occurred. It's no biggie, I can reformat the settings myself. Thanks for the help.
dude, google it
Sent from my GT-I9505 using XDA Premium 4 mobile app
Ok guys ..hi there. I am running PAC ROM 4.4.4..ok guys am having an issue ..i originally got this phone (i9500) with 4.4.2 kitkat touchwiz i rooted it and installed twrp 2.6.0.0 and all was well..Then i decided to install the ozcan rom 6.3 ...after flashing the rom...the first boot was stuck on Samsung logo ( and yes i advance wipe my phone several times using the mke2fs format) and this rom is for my model! So i was disappointed... Then i wiped again and tried to restore my backup which also led to a bootloop..soo i had no choice but to flash a next ROM... The rom that worked was 4.2.2 wanam lite (jellybean) ..i got tired of it and went to pac ROM now.i wanted to try the ozcan rom again.. It didn't work! I tried arrow rom..it didn't work ..and these worked for other i9500 users..so am wondering is my recovery outdated and not doing it correctly ? So the main question is WHY CANT I INSTALL A TOUCHWIZ KITKAT ROM??
Sent from my GT-I9500 using XDA Free mobile app
BenDroid1 said:
Ok guys ..hi there. I am running PAC ROM 4.4.4..ok guys am having an issue ..i originally got this phone (i9500) with 4.4.2 kitkat touchwiz i rooted it and installed twrp 2.6.0.0 and all was well..Then i decided to install the ozcan rom 6.3 ...after flashing the rom...the first boot was stuck on Samsung logo ( and yes i advance wipe my phone several times using the mke2fs format) and this rom is for my model! So i was disappointed... Then i wiped again and tried to restore my backup which also led to a bootloop..soo i had no choice but to flash a next ROM... The rom that worked was 4.2.2 wanam lite (jellybean) ..i got tired of it and went to pac ROM now.i wanted to try the ozcan rom again.. It didn't work! I tried arrow rom..it didn't work ..and these worked for other i9500 users..so am wondering is my recovery outdated and not doing it correctly ? So the main question is WHY CANT I INSTALL A TOUCHWIZ KITKAT ROM??
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
You could try updating recovery. And maybe try to flash it via Odin (if that's possible)
Hi guys ..so it turns out that my recovery was outdated (twrp 2.6.0.0) its working great now..i love this ROM i don't think i'll be changing for a while. ..Until 6.4 gets out lollipop based ....So yea guys now i have 6.3 ozcan rom and the latest philz touch recovery ...i flashed it via twrp
Sent from my GT-I9500 using XDA Free mobile app
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
safi_k19 said:
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
Click to expand...
Click to collapse
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Interface23 said:
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Click to expand...
Click to collapse
Yes, I did everything as there said.
safi_k19 said:
Yes, I did everything as there said.
Click to expand...
Click to collapse
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Interface23 said:
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Click to expand...
Click to collapse
twrp. I dont know what you mean by stock rom because this is my first time I did. My device is running 4.4.2. and I chose for kernel 4.4 version of tw.
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
msmlz said:
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
Click to expand...
Click to collapse
I agree with msmlz, if you have nandroid restore it or download the firmware in sammobile and reflash it and before flashing the custom kernel again, read the thread, see if someone face bootloop like you. Hope someone with experience on it could help you, I never install custom kernel, just update the last stock kernel on my rooted stock rom.