Related
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
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
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.
I have been a Samsung Galaxy Y user for more than a year. I have to say that this device is awesome. But.... I have later noticed 2 problems.
1) One day I tried to install Elegance ROM. I followed all steps very carefully and when the installation was done, I rebooted my phone. Unfortunately, my phone booted up again at Samsung stock firmware. I tried to enter recovery mode because I wanted to see what went wrong, but I was automatically redirected to CWM recovery. I tried once again to install Elegance ROM, and the result was the same. From that day, CWM is my default recovery. Why? How to fix this??? I can't access stock recovery and I also cannot install any custom ROMs. How to fix this?
2) Even my SD card is full with songs, photos and videos, the "Gallery" and "Music" apps don't read any file. Why? How to fix this?
P.S. I'm running stock 2.3.6 rooted.
Thanks for help.
Sent from my GT-S5360 using xda app-developers app
You have a permanent cwm because you are using a custom kernel with a permanent cwm - probably was included in the rom zip
If you want stock recovery flash stock kernel (can be found in general section or flash hells fusion #50 from dev section and select option to flash stock kernel)
you would of remained on stock rom after flashing another rom because you didn't mount system in cwm before you flashed the zip
As for your other problem flash stock rom via odin as you have probably mucked something up from flashing zips incorrectly
So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium
dimsar2013 said:
So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Dude ur 2nd problem may be caused by Ur sd card!!
Try another sd card may it help you!!
dimsar2013 said:
So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Yes stock kernel = stock recovery and you can flash a temporary cwm
there is no problems with a permanent cwm in custom kernels as you need cwm to flash roms
If you goto phone settings about phone it will show you your current baseband - for example mine is xxlf3
You can either download that stock rom firmware from dokys thread if there or any other from your country
Thanks everybody. You are all really helpful. I appreciate your help. But tell me, do I need to mount system before installing Elegance? And while I'm having a custom kernel installed, can I flash roms or I need the stock kernel?
Thanks again.
Sent from my GT-P3110 using xda premium
dimsar2013 said:
Thanks everybody. You re awesome. I appreciate your help. But tell me, do I need to mount system before installing Elegance? And while I'm having a custom kernel installed, can I flash roms or I need the stock kernel?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Follow instructions on the op of the rom you want to flash
you must always mount system before flashing a zip else nothing will happen - you can flash zips all day and no changes would happen as it can't write to system as it's not mount!
As a general rule
wipe system
wipe data
wipe cache
mount system
mount data
mount cache
flash zip
format data (not always required just for some roms)
restart
you do not need to go back to stock to change rom
There are guides in general section - please read them first then you would understand the process
My current ROM. Stock 2.3.6 rooted
Sent from my GT-S5360 using xda app-developers app
A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help
dimsar2013 said:
A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help
Click to expand...
Click to collapse
Yes you can flash it over any kernel and yeah mount all the partitions after formatting them.
dimsar2013 said:
A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help
Click to expand...
Click to collapse
I refer you to my previous post in this thread
wipe data system cache
mount everything
flash rom
you can use any compatible kernel
The problem with the files is caused by the sdcard
Sent from my GT-P3110 using XDA Premium 4 mobile app
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
JaguarBeast said:
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
Click to expand...
Click to collapse
You can easily test that theory by not flashing Gapps. Just only flash the rom and try to boot it.
Also are you running a Lollipop bootloader and modem?
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
JaguarBeast said:
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
Click to expand...
Click to collapse
Ok do this:
Backup everything that you want to save stored on your internal storage.
1. Make sure you are running the latest TWRP. This is important because using an outdated version will not let you boot the rom.
2. Start TWRP and do a advanced wipe. Format /data (this will wipe your internal storage), format /system, format /cache and /dalvik.
3. Flash the rom.
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
JaguarBeast said:
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
Click to expand...
Click to collapse
What version of TWRP are you using? And did you try booting it without simcard and sd card?
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
JaguarBeast said:
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
Click to expand...
Click to collapse
No idea. I'm just guessing because that rom should just boot.
Are you sure the file you downloaded is not damaged? Check the MD5 signature. For example, the latest version of the JDC CM rom has MD5:
3a1af890b87c11256c943759459ec3e4
So transfer the file to your phone. Then download a MD5 checker from the market and compare it.
Md5 matches. Looks like the insides of my phone are screwed up
Reparation your device
As those are caused by a screwed partition
As a reparation fixes this
You are going to need :-
0.a PC
1.a PIT file for your Galaxy s4 (depending on your variant)
2.Odin
3.Samsung USB drivers installed in the PC
Sent from my GT-I9505 using Tapatalk
Start with flashing the stock rom using odin. Then go for root,then recovery and then try flashing. I had the same problem but it never bothered me after flaahing the stock.