Related
Search function is down but I did go through a few pages of threads looking for what was going on and no luck but I apologize if this has been solved somewhere else.
First off I would rate my rooting know-how as beginner to intermediate. I've jailbroken/unlocked multiple iPhones awhile back and have rooted/flashed roms on a cliq, mts, my3g, and this mt4g before.
I recently returned my current mt4g back to stock rom and unrooted. I do not think I turned s back on but I should have double checked before.
I currently have root and flashed clockwork and am trying to flash CM7 (I had ran it before on this phone as well). I have an issue right now where I cannot get into clockwork recovery as it will just sit at the mytouch logo forever and if I try and volume up and power into recovery all I get is 3 vibrations and a flashing amber light.
I can boot into the stock (but rooted) rom.
Any ideas? I feel like my recovery is broken or something but this goes beyond what I know. Any help would be great and any information you need I'll be happy to provide.
myTouch 4G, rooted, s (probably) off, stock rom, clockwork says i'm on 3.0.2.4
After reading that, I'm not fully convinced you actually have root and S-OFF. If you're sure you do, download ROM Manager from the Market and use that to install a fresh copy of CWM recovery. Also make sure the "fast boot" option is turned off somewhere under Settings. At that point, there should be nothing preventing you from getting into recovery if you have perm root.
I've got ROM Manager and it has SU permissions and I have the latest recovery flashed but I am still stuck on mytouch logo or the 3 vibrations/amber light when I try to get to recovery. If I reboot there is still no problem getting SU in terminal emulator or ROM manager or anything.
Fast boot is off as well. Thanks for the help so far.
Any ideas?
I don't often boot into recovery manually since most custom ROMs have an enhanced reboot menu with a recovery option, but if memory serves, I believe the key press combination is actually Power + Volume Down, not up like you mentioned in your OP. Give that a try.
Man I am really crazy. Here I am a tmo rep and also a novice modder and I'm hitting power + volume up.
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Thanks for the fresh set of eyes!
breakaway87 said:
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Click to expand...
Click to collapse
After flashing CM7, the phone hangs at the myTouch screen when attempting the first boot?
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
breakaway87 said:
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
Click to expand...
Click to collapse
What if you select the "boot into recovery" option in ROM Manager? Does the phone reboot into CWM recovery? (you should see the main CWM menu in orange text)
Boot into recovery takes me to MT4G logo and hangs.
breakaway87 said:
Boot into recovery takes me to MT4G logo and hangs.
Click to expand...
Click to collapse
So you don't have a good installation of CWM. Open ROM Manager again and re-flash a fresh recovery. I think there's an option to wipe your existing recovery beforehand, so if you see that, select it. You need to get a working recovery image before you can do much else.
Deleted current recovery and I confirm my model again and it takes a total of 5 seconds. Trying to reboot into recovery again after and I still hang at MT4G.
I hate it when you know something you need to do but you've been working on it so long you can't come up with new ideas.
Thanks again for the help.
Sorry multipost since it didn't register on my computer the first time for some reason
Yeah sorry man, I've never heard of a situation where CWM stubbornly refuses to install. If you have the engineering bootloader, you could manually flash it that way, but that's my only other idea.
Alright well thanks for all the help man, I'll dig around and pick up tomorrow.
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
breakaway87 said:
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
Click to expand...
Click to collapse
Sure, glad you figured it out.
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.
ryuz4ki said:
Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.
Click to expand...
Click to collapse
Well, for one thing, never format boot.
After trying cm7, you still get cyanoboot? It should have changed to the green cyanogenmod logo. If not then your flashes are not working.
Sent from my Nook Color running ICS and Tapatalk
After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.
ryuz4ki said:
After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.
Click to expand...
Click to collapse
Ok, that means that CWM is putting the boot files on the boot partition since they change CM7 vs CM9.
Which version is your CWM on the SD?
You can't boot to anything, not even emmc recovery? Or you just can't boot to 'normal'? Do you even have emmc recovery installed? If you don't, get the first file on this post and flash it with your CWM card. You may be in a recovery bootloop, without a recovery.
http://forum.xda-developers.com/showthread.php?p=21932561
Sent from my Nook Color running ICS and Tapatalk
Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.
ryuz4ki said:
Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.
Click to expand...
Click to collapse
It's possible your recovery somehow got corrupted during the flash. If that happens, it does not clear the recovery boot flag and it keeps trying to boot to recovery and it can't because it is corrupted. And it just bootloops forever.
Also, make sure your CWM bootable card is a recent version. If you have a newer nook and an old CWM and you try to clear data, it fails and you have a mess.
Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks
huyroy said:
Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks
Click to expand...
Click to collapse
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.
DizzyDen said:
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.
Click to expand...
Click to collapse
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.
huyroy said:
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.
Click to expand...
Click to collapse
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?
leapinlar said:
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?
Click to expand...
Click to collapse
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.
huyroy said:
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.
Click to expand...
Click to collapse
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.
leapinlar said:
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.
Click to expand...
Click to collapse
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks
huyroy said:
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks
Click to expand...
Click to collapse
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.
leapinlar said:
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.
Click to expand...
Click to collapse
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol
huyroy said:
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol
Click to expand...
Click to collapse
Thank YOU for testing my card and proving that gets you out of the recovery bootloop you were in.
You need to take one more step. You need to put a new CWM back on your internal memory so it is there ready for the next time you want to install a ROM. If you go back to my tips thread, there is a link to a new flashable CWM zip (version 5.5.0.4) that can be put on your internal memory. The link is in item B1. Just download that zip file, then boot one more time to my bootable CWM card and install that zip. You should not need my card anymore after that unless you get in a bootloop again.
I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.
NapalmDawn said:
I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.
Click to expand...
Click to collapse
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.
leapinlar said:
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.
Click to expand...
Click to collapse
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be
NapalmDawn said:
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be
Click to expand...
Click to collapse
First thing I would try is just to exit the new CWM via the menu to see if it gets you out of the bootloop. Retry booting without the SD in. If it will still only boot to recovery, I would again boot to my CWM and flash the new recovery to emmc. Next I would try to restore your old nandroid backup with the new CWM. If none of that works, flash a new CM to emmc with the new CWM.
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
hotshot545 said:
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
Click to expand...
Click to collapse
Unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of CM. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red M" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
If you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
dr. Orange said:
unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of cm. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red m" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
if you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
Click to expand...
Click to collapse
thank u sooo much
hotshot545 said:
thank u sooo much
Click to expand...
Click to collapse
ok i just wanted to know is there a way to charge phone b4 doing this
hotshot545 said:
ok so if i flash it using sbf lite... will it run stock android 2.2 or will it's still run 4.1.1 and also will it still be rooted or will i have to restore root. and btw b4 i do this can i charge my phone in this "boot loop mode"... srry i am not the best at this kind of stuff... so I would greatly appriciate if you assisted me step by step if you could... thx in advance again..
**don't wanna brick my bravo xD
Click to expand...
Click to collapse
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Dr. Orange said:
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Click to expand...
Click to collapse
ok thx sooooo much.. approximatly how long will this take
hotshot545 said:
ok thx sooooo much.. approximatly how long will this take
Click to expand...
Click to collapse
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Dr. Orange said:
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Click to expand...
Click to collapse
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
hotshot545 said:
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
Click to expand...
Click to collapse
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Dr. Orange said:
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Click to expand...
Click to collapse
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
skeevy420 said:
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
Click to expand...
Click to collapse
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
hotshot545 said:
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
Click to expand...
Click to collapse
My fault, its Volume Down, and yes, the green blink before the blue is when you push it.
I got it confused with Stock Recovery, which is Power Button+Volume Up while turning on the phone.
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?