Database Users

[Q] doing something wrong?

Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading

sometimes mine gets stuck on that screen as well after flashing something... i just hold the power button to restart the phone and then generally it boots up fine...
also I'm assuming you have an i9505?
Sent from my GT-I9505 using Tapatalk 4 Beta

Yes i9505, I have tried long holding power button but just goes back to that screen. Just finding it quite frustrating now it must be something simple I'm missing.

igrieve said:
Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading
Click to expand...
Click to collapse
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work

123hiten said:
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work
Click to expand...
Click to collapse
just tried for omega and foxhound and no difference just going to try the last one now.

just download a pre-rooted stock, flash via odin, then flash a recovery via odin, wipe everything, format /system and then install a custon first boot takes around 3 minutes...

Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.

igrieve said:
Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.
Click to expand...
Click to collapse
It should work my friend give it a try again and which recovery are you using? Name
Sent from my GT-I9500 using xda premium

Maybe your base rom wasen't the same as the rom you tried to flash?
Sent from my GT-I9505 using xda premium

My friend has the exact same issue on his i9505 using twrp, he tried to flash various ROMs but not getting past boot screen, fortunately his back up worked but still no luck in getting a ROM to flash...very odd
Edit: he is running a 3 network supplied phone if that make any difference
Sent from my Nexus 4 using xda premium

I have exactly the same!
Formatted, factory reset, wipe cache/dalvik, stock firmware using Odin, Nothing is working so far..
$%^$%
Now trying to instal FoxHound 0.5.

Well still having problems lol no idea why but I can only install two ROMS but I am happy with the one I'm currently using but your always curious to see what the others are like.

If you guys are using twrp as your recovery and you format internal sd this will happen. It is a know issue with that recovery. It messes with the partition and you need to flash a different recovery. You may need to Odin back to stock to get the partition right and go from there. Hope this helps.
Sent from my GT-I9505 using xda app-developers app

Im currentl;y using philz_touch recovery, I have been having to go back to odin and flash stock rom just to get the phone running again after trying these roms. I havent tried any roms from the original android development forum so might see if I get any joy with them, I know it must be something silly I'm missing

It happens if the base ROM you are currently on isn't the same or similar to the ROM you're trying to flash. Maybe changelog of the ROM you're trying to flash is a lot higher tan your current ROM and things get mixed up. I have always had success by performing a factory reset after flashing the ROM.
I had the exact same problem going from MDE firmware to Omega V7. After flashing Omega again I did a factory reset and it was sweet
Sent from my GT-I9505 using XDA Premium HD app

TWRP restore

I restored my phone using TWRP. Everything works ok except if I try to restart the phone it hangs at the Samsung logo. Please someone help me to get my phone back working :crying:

I'm asking you restored a stock backup. Did you wipe before restoring? Have you wiped since?

Yes and yes. My phone works perfect but won't boot up if I restart it. Then I need to wipe, format, restore just to boot up again. Has happened three times in a row so now I cannot restart or turn off my phone without taking 15 minutes to restore again
Sent from my stock rooted i337m

WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.

TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7

trueking7 said:
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7
Click to expand...
Click to collapse
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Right now I am trying to find out if flashing the stock kernel will enable me to reboot normally? I will copy the kernel to the card just in case my phone powers off. Then I will try flashing it to see if phone will boot. If not then I will restore from nandroid yet again and be unable to reboot.
I will use Odin as a last resort.
Ps. This would be a lot easier if install instructions were carrier specific.
jd1639 said:
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
Sent from my stock rooted i337m

here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome

TheAxman said:
here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome
Click to expand...
Click to collapse
I got my phone booting properly again. I re-rooted. I installed TMO KTweaker. I can still reboot. I took another nandroid. I will try flashing omega + ktweaker again this time without formating via TWRP which apparently casused my problem.

Usually when you have restore problems, its either a MD5 mismatch, or corrupt micro SD card. You don't have to wipe when restoring, TWRP does it automatically when you restore.

I got Omega v7 working with the TMO KTweaker on my rogers i337m. Thank you all!

everything works perfect now thanks!!

good deal

Can't get passed boot logo..

This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.

Try flashing a different compatible kernel.

ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.

Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app

Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr

ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app

I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!

Glad it's working out for you.

If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?

Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.

[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...

[Q] After rooting and installing CWM Recovery Note 3 freezes on all ROM installs

Hey Everyone
My note 3 roots fine using auto-root and I have tried twrp, cwm, and also philz recovery. They all install fine to my knowledge. However, Once I boot into recovery to flash the custom ROM. I delete cache, user data and delvik and reboot back into recovery I install the rom from sd card it fails. No matter what Rom I used. I have tried Sacs, X-Note, C-Rom, Anthem, no matter what it always freezes and I have to restore stock. Any ideas?
Thanks

Joining to the question
After the custom rom (X-Note,BobCat), my Note3 sm-n9005 freezes randomly, and a boot is required.
The problem doesn't occur when using cyanogenmod 11.
BR,

I have the same problem. Can only install asop ROMs but touchwiz ROM won't boot after install. Phil recovery doesn't work for me. Any assistance would be great
Sent from my SM-N9005 using XDA Premium HD app

phonz said:
I have the same problem. Can only install asop ROMs but touchwiz ROM won't boot after install. Phil recovery doesn't work for me. Any assistance would be great
Click to expand...
Click to collapse
you need KK BL and take philz 6.48. flash stock KK rom

Legend, thank you Rayman. Will give it a go
Sent from my SM-N9005 using XDA Premium HD app