Database Users

[Q] I9505 do not boot

I have a big problem with my new I9505.
Today I flashed new CWM 6.0.3.6 and 4.3 GE Jamal Rom. After I flashed some mods for testing.
Then I wanted to install a clean rom, I formated in CWM every point (system, data, cache, sdcard, dalvik and dont know what else).
After I flashed again 4.3, now it do not boot. Stuck at Google boot animation.
I thought it will be fixed if I flash the stock rom via Odin (only PDA with I9505XXUBMGA_I9505OXABMGA_I9505XXUBMGA_HOME.tar.md5).
But now I stuck at Samsung Boot animation.
It is possible to boot into Recovery and Download mode.
Whats happening?
I hope somebody can help me.
Big thanks.

keynex said:
I have a big problem with my new I9505.
Today I flashed new CWM 6.0.3.6 and 4.3 GE Jamal Rom. After I flashed some mods for testing.
Then I wanted to install a clean rom, I formated in CWM every point (system, data, cache, sdcard, dalvik and dont know what else).
After I flashed again 4.3, now it do not boot. Stuck at Google boot animation.
I thought it will be fixed if I flash the stock rom via Odin (only PDA with I9505XXUBMGA_I9505OXABMGA_I9505XXUBMGA_HOME.tar.md5).
But now I stuck at Samsung Boot animation.
Whats happening?
I hope somebody can help me.
Big thanks.
Click to expand...
Click to collapse
Try to get into recovery and wipe both caches and reboot. If that doesn`t work also do a data factory reset. Don`t you have a nandroid backup to fall on back too?

My nand backup is corrupt :/

keynex said:
My nand backup is corrupt :/
Click to expand...
Click to collapse
Just reflash the rom again with a full wipe and after the flash wipe both caches and reboot.

Okay I figure out my nand backup is not corrupt..
If I select backup in cwm it restore system but it cant mount data.
I think the mistake is here.. /data do not exist?

gee2012 said:
Just reflash the rom again with a full wipe and after the flash wipe both caches and reboot.
Click to expand...
Click to collapse
Flashed again with wipe.. same problem..

keynex said:
Flashed again with wipe.. same problem..
Click to expand...
Click to collapse
I would return to stock to get the phone running again. so:
1. Go to recovery and wipe the caches and do a data factory reset and format system.
2. Pull the battery and go into downloadmode
3. Flash a stock rom with Odin 3.04
4. Reboot, setup the phone and reroot.

gee2012 said:
I would return to stock to get the phone running again. so:
1. Go to recovery and wipe the caches and do a data factory reset and format system.
2. Pull the battery and go into downloadmode
3. Flash a stock rom with Odin 3.04
4. Reboot, setup the phone and reroot.
Click to expand...
Click to collapse
Have done again exactly like you said, still same problem (

keynex said:
Have done again exactly like you said, still same problem (
Click to expand...
Click to collapse
Did you factory reset after the flash of the stock rom and also wipe the cache in stock recovery?

gee2012 said:
Did you factory reset after the flash of the stock rom and wipe the cache in stock recovery?
Click to expand...
Click to collapse
Thank god, thats it. My S4 is alive.
You are my hero, thanks :laugh:

keynex said:
Thank god, thats it. My S4 is alive.
You are my hero, thanks :laugh:
Click to expand...
Click to collapse
Glad it worked out after all You don`t have to say thanks, just press thanks bro

I had exactly the same issue,except whilst i was reflashing my nandroid the phone shut down, formatted everything as one normally would using philz recovery, tried again and it failed.
Now i cannot even gain access to recovery it stays on "loading recovery" only option i suppose is to reflash stock via odin.

me too
Davies_90 said:
I had exactly the same issue,except whilst i was reflashing my nandroid the phone shut down, formatted everything as one normally would using philz recovery, tried again and it failed.
Now i cannot even gain access to recovery it stays on "loading recovery" only option i suppose is to reflash stock via odin.
Click to expand...
Click to collapse
I've also experienced this on my gpe and it seems going back to stock is the best solution for doing the factory reset. I've tried doing the factory reset with both team win recovery and cwm.

Please help! I'm freaking out, thank you in advance!
gee2012 said:
I would return to stock to get the phone running again. so:
1. Go to recovery and wipe the caches and do a data factory reset and format system.
2. Pull the battery and go into downloadmode
3. Flash a stock rom with Odin 3.04
4. Reboot, setup the phone and reroot.
Click to expand...
Click to collapse
Hi, I ran into the exact same problem doing exactly the same thing, but I cannot get into recovery to factory reset and wide cache. Do you know how to fix this problem? I get stuck at samsung boot animation screen as well while trying to flash back to stock.:crying:
Please Help!
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
THC122 said:
Hi, I ran into the exact same problem doing exactly the same thing, but I cannot get into recovery to factory reset and wide cache. Do you know how to fix this problem? I get stuck at samsung boot animation screen as well while trying to flash back to stock.:crying:
Please Help!
Click to expand...
Click to collapse
UPDATE
I actually was able to get into the recovery at like the 10th attempt. Thank you so much for your directions! Imma hit thanks!

[Q] Stuck Boot with any custom Kernel

Hi!
I have a EU i9505, rooted with Jamal GE ROM, September update.
I tried installing KTOONsez, both version, but the phone just stays tuck at the Galaxy boot logo
si I have to clear both cache and reinstall the ROM
I tried with Chronic Kernel, same issue...phone stuck at Google 4 circles boot logo.... so I cleaned cache and reinstalled rom... BUT now the phone is not booting anymore
As soon as the boot finishes I see for a while the desktop (with the STD wallpaper and wrong time/date) andthan it reboots....
HELLLP!!!!!

Sounds like something has gone wrong with the installation process and now nothing works. I personally would now install a stock Rom via Odin and get the phone working again. Then start again installing your rom of choice. Ensure that you use an old stock firmware as newer versions have the fuse security feature. What recovery did you use. I had similar issues with Philz so now I use official CMW.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HANDSY said:
Sounds like something has gone wrong [...]
Click to expand...
Click to collapse
Thank you, I give it a try! I did a full wipe and reinstalled Jamal AOSP GE. Now it is working again.
I will remove PhilZ, put CWM, than flash OMEGA + new kernel

theluke79 said:
Thank you, I give it a try! I did a full wipe and reinstalled Jamal AOSP GE. Now it is working again.
I will remove PhilZ, put CWM, than flash OMEGA + new kernel
Click to expand...
Click to collapse
New ROM, same issue...if I install a new kernel, the device just reboots... I will try Cwm vs philz

problem after installing cm10.2

hello everybody
im kinda new her so be cool with me
i'v just installed cm10.2 latest version on my nexus 4 4.3 ver, and i'v restarted the phone, and after he worked properly and smoothly before that restart, he writes me "Unforrtunetly, System UI has stopped." after i click OK another one comes and over and over..
iv installed the latest cm nightly version, i realy need ur help!

noamp0 said:
hello everybody
im kinda new her so be cool with me
i'v just installed cm10.2 latest version on my nexus 4 4.3 ver, and i'v restarted the phone, and after he worked properly and smoothly before that restart, he writes me "Unforrtunetly, System UI has stopped." after i click OK another one comes and over and over..
iv installed the latest cm nightly version, i realy need ur help!
Click to expand...
Click to collapse
Did you wipe data/factory reset in recovery before you flashed the rom?

22sl22 said:
Did you wipe data/factory reset in recovery before you flashed the rom?
Click to expand...
Click to collapse
yea of course!
perhaps i should meantion that in the guide it says that this part of wipeing data should take time but at my case id didnt pass the 30 sec..

noamp0 said:
yea of course!
perhaps i should meantion that in the guide it says that this part of wipeing data should take time but at my case id didnt pass the 30 sec..
Click to expand...
Click to collapse
Wiping data shouldn't take long at all. When people say wipe data/factory reset when changing roms it doesn't mean wipe the whole sd card. Do you have the latest recovery version? For CWM it is 6.0.3.6 or 6.0.3.7. For TWRP it is 2.6.3.0
The correct procedure is:
Wipe data/factory reset (NOT sd card)
Wipe cache/dalvik cache
Install Rom
Install Gapps
Install SU (optional)
Reboot

22sl22 said:
Wiping data shouldn't take long at all. When people say wipe data/factory reset when changing roms it doesn't mean wipe the whole sd card. Do you have the latest recovery version? For CWM it is 6.0.3.6 or 6.0.3.7. For TWRP it is 2.6.3.0
The correct procedure is:
Wipe data/factory reset (NOT sd card)
Wipe cache/dalvik cache
Install Rom
Install Gapps
Install SU (optional)
Reboot
Click to expand...
Click to collapse
yeah i have the CWN 6.0.3.6 version, and i did it all according to this procedure except the dalvik cache wipeing and that SU? (what is it exacly)?
u think i should do this all over again? maybe it will fix somthing... also ive notice that a new cm version (20130922) is out and mine is 20130921..
what are u saying? i would prefer not to do it cuz iv already manged all my apps and settings on the phone

noamp0 said:
yeah i have the CWN 6.0.3.6 version, and i did it all according to this procedure except the dalvik cache wipeing and that SU? (what is it exacly)?
u think i should do this all over again? maybe it will fix somthing... also ive notice that a new cm version (20130922) is out and mine is 20130921..
what are u saying? i would prefer not to do it cuz iv already manged all my apps and settings on the phone
Click to expand...
Click to collapse
Redownload the ROM. Once you've downloaded just install it and wipe cache and dalvik and it should be fine.
Su, in full, Super SU is root made by Chainfire. The normal one in cm is made by Koush but you don't need to flash the Chainfire one, only do that if you have root problems
Sent from my Nexus 4

22sl22 said:
Redownload the ROM. Once you've downloaded just install it and wipe cache and dalvik and it should be fine.
Su, in full, Super SU is root made by Chainfire. The normal one in cm is made by Koush but you don't need to flash the Chainfire one, only do that if you have root problems
Sent from my Nexus 4
Click to expand...
Click to collapse
i dont have any root problems so that fine, and ill try this and edit!
EDIT: it didnt work.. iv installed the new CM ver and after deleted cache and dalvik as u sayd and still not working properly..

U should flash stock rom, after that flash your cm rom again,your issue will be solve. Good luck.
Sent from phone's neighbor wife at dreaming place

bbanana said:
U should flash stock rom, after that flash your cm rom again,your issue will be solve. Good luck.
Sent from phone's neighbor wife at dreaming place
Click to expand...
Click to collapse
r u sure it will solve it? or can i try another thing as last resort before i wipe all/?
EDIT: and another thing, if u can give a link to the stock rom ill be glad!

i realy need ur help, im realy stuck here..
i tryed wipe all and istall the new CM ver and still not working..
how do i flash that stock rom??

[Q] AT&T Galaxy S4 - Freezes on Samsung Screen after Reboot

Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...

a.stalker22 said:
Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...
Click to expand...
Click to collapse
Use twrp 2.5.0.2. I'm guessing you're using 2.6

jd1639 said:
Use twrp 2.5.0.2. I'm guessing you're using 2.6
Click to expand...
Click to collapse
No, I am using 2.5.0.2 just verified.

a.stalker22 said:
No, I am using 2.5.0.2 just verified.
Click to expand...
Click to collapse
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.

jd1639 said:
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.
Click to expand...
Click to collapse
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:

a.stalker22 said:
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:
Click to expand...
Click to collapse
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.

emckai said:
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.
Click to expand...
Click to collapse
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?

a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Get a cwm zip file and flash it like you would a rom but don't do any wipes. It'll flash on top of twrp and replace it. Do the same thing to go back to twrp.

a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?

Try to clear the delvik cache and the cache. I believe it will boot normal then
Sent from my SAMSUNG-SM-N900A using Tapatalk 5

emckai said:
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?
Click to expand...
Click to collapse
No, they're not all based off of CWM.
The last few I tried were BeanStalk and Task650 AOKP. The Task650AOKP booted up fine the first time, I did a reboot and then it was permanently stuck at the Samsung Galaxy S4 screen, even after I cleared cache's and factory reset with a re-flash. I tried that several times and still couldn'y get back in, so luckily I had a backup of my original rooted config and that booted up.
I did install rom manger just now and flashed cwm recovery...just afraid to reboot..haha. I wish I knew what the problem could be here...

S4 won't boot 4.4 rom

is stuck at cyanogenmod logo or android kitkat logo, what can i do?
i always used s4 with 4.2 roms

djsolidsnake86 said:
is stuck at cyanogenmod logo or android kitkat logo, what can i do?
i always used s4 with 4.2 roms
Click to expand...
Click to collapse
Maybe you have to flash a different pit-file first. Some updates from Samsung repartioned the system and other ROMs are not compatible with it. Please check for the size of you system. If it is any bigger that 8.9GB, you have to flash the according pit file first.

body150165 said:
Maybe you have to flash a different pit-file first. Some updates from Samsung repartioned the system and other ROMs are not compatible with it. Please check for the size of you system. If it is any bigger that 8.9GB, you have to flash the according pit file first.
Click to expand...
Click to collapse
what is this pit file? how flash it?

Just clear cache partition and delvik cache by using custom recovery then reboot
Sent from dish washer

smep said:
Just clear cache partition and delvik cache by using custom recovery then reboot
Sent from dish washer
Click to expand...
Click to collapse
done but isn't working!

djsolidsnake86 said:
is stuck at cyanogenmod logo or android kitkat logo, what can i do?
i always used s4 with 4.2 roms
Click to expand...
Click to collapse
Did you do wipe before installing the ROM?

Hyuna-A said:
Did you do wipe before installing the ROM?
Click to expand...
Click to collapse
of course!
i saw that cm based on 4.2.2 work, based on 4.3 or 4.4 go stuck at cm logo (bootloop)
how solve?

djsolidsnake86 said:
of course!
i saw that cm based on 4.2.2 work, based on 4.3 or 4.4 go stuck at cm logo (bootloop)
how solve?
Click to expand...
Click to collapse
The best thing you could do right now is to reflash the rom again , and make sure your doing a full wipe , cache/dalvik/factory reset or if your using a philz recovery go ahead and choose Factory reset/Wipe to install a new rom" option or something like that.or either you can use tamirda's Superwipe from here http://forum.xda-developers.com/showthread.php?t=2379104. then install the rom and i hope this fix your problem. Have a nice day.

Repulsa said:
The best thing you could do right now is to reflash the rom again , and make sure your doing a full wipe , cache/dalvik/factory reset or if your using a philz recovery go ahead and choose Factory reset/Wipe to install a new rom" option or something like that.or either you can use tamirda's Superwipe from here http://forum.xda-developers.com/showthread.php?t=2379104. then install the rom and i hope this fix your problem. Have a nice day.
Click to expand...
Click to collapse
i already do wipe to install a new rom!

djsolidsnake86 said:
i already do wipe to install a new rom!
Click to expand...
Click to collapse
Well if im havibg this problem i will just install the stock rom or either wait for someone knows any other option to fix this problem.(Im not sure which Stock rom do you need either 4.2.2 or 4.3) Have a nice day.

very strange!