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...
Related
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
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)
Hey, I seem to have gotten myself into a pickle. Here's what happened: I wanted to do an update to Cyanogenmod 10.2, so I downloaded the ROM and gapps. I wiped dalvik, cache, and system and flashed the ROM. When I tried to flash the gapps Clockwork Mod said it was corrupt. No problem, turned the phone off, pulled micro usb card and put the gapps on that. The only problem is now I can't boot into recovery at all, with the Power+down option and ROM Manager crashes when I try to open it. So the problem is that I can't boot into recovery and I can't reinstall ROM Manager because I don't have gapps. Titanium Backup is also having problems and can't get root access. Does anyone have any ideas on what the problem is or how to fix it? Thanks in advance.
I'd Odin back to stock and start over.
jd1639 said:
I'd Odin back to stock and start over.
Click to expand...
Click to collapse
How do I do that? Will I be able to since I had CyanogenMod 10.1 on before I tried to update?
Also, It would be better if I could just reflash a custom recovery, is there any way to do that?
AwesomeDerek said:
Also, It would be better if I could just reflash a custom recovery, is there any way to do that?
Click to expand...
Click to collapse
See if you can find an odin flashable recovery. There's probably one in the development forum. Flash that.
jd1639 said:
See if you can find an odin flashable recovery. There's probably one in the development forum. Flash that.
Click to expand...
Click to collapse
Do you think this tool would work? http://forum.xda-developers.com/showthread.php?t=2297033&highlight=odin+recovery
AwesomeDerek said:
Do you think this tool would work? http://forum.xda-developers.com/showthread.php?t=2297033&highlight=odin+recovery
Click to expand...
Click to collapse
It's worth a try. If it doesn't work you could go the Odin to stock method.
hungape special
Ding! Got into recovery, now I'm gonna wipe everything. Thanks for your help
AwesomeDerek said:
Ding! Got into recovery, now I'm gonna wipe everything. Thanks for your help
Click to expand...
Click to collapse
Np
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
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
Which twrp recovery you using?
Sent from my SPH-L720 using xda app-developers app
openrecovery-twrp-2.6.0.0-jfltespr
excessive81 said:
openrecovery-twrp-2.6.0.0-jfltespr
Click to expand...
Click to collapse
Twrp version 2.6.0.0 seems to be buggy either try 2.5.0.2 or 2.6.0.3 they seem to be working for people the most
Sent from my SPH-L720 using xda app-developers app
excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.
smizak said:
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.
Click to expand...
Click to collapse
the 2.6.3 worked thanks
excessive81 said:
the 2.6.3 worked thanks
Click to expand...
Click to collapse
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app
ParkerParker said:
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.
excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.
Click to expand...
Click to collapse
stock recovery, factory reset. trust me.
excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore
Just give it some time you will have curtain hangs... If you flash a lot.. But onto the zip, just flash in recovery, done
Heres the twrp thread if you feel like a read, http://forum.xda-developers.com/showthread.php?t=2262999
Click to expand...
Click to collapse