Kinda odd something I came across today in my S4, something I see others having mentioned before. Getting stuck on the att logo screen. I am stock rom, just rooted. Right now it seems to be back to normal on reboots and so, but a few mins ago, it would get stuck there on one boot, next boot might be fine. Now I did go into recovery to try that wipe cache, tho the android icon said error after it started and just rebooted, so not sure the deal there. Just was wondering, is this something that more people get commonly a random stuck on att logo? (Or is it just a odd thing where it could be a super long boot up and just wait?)
Now with reboot or shutdown, anyone know the deal why that seems to take so long to do?
Edit: Take that back, this reboot test, got stuck again on att logo... odd.
Anyone?
Something might have happened that caused a rebuild of the Delvic cache. When that happens, it can take as long as a few minutes to boot, but it should only happen the first boot after the cache wipe. If the problem persists, you could try to factory reset your phone in recovery or just use ODIN to re-flash MF3 to your phone. I suggest you make sure to read and learn about whatever option you try and understand, there is always risk associated with trying anything.
After I rooted, I was having similar issues. But the phone would reset or power up fine if I had the cable plugged in. Eventually figured out is was the battery that was bad. Rooting before the problems started was just a coincidence. Check to see if adding power to USB helps.
I had never tried to clear my cache or reset my phone through system recovery until after I had already rooted. Neither of them worked for me though, it would just say error and then try rebooting. I also got stuck on the AT&T boot logo, but it was every time I tried to boot. I was stuck with my phone like this for about two months. I finnaly fixed it but its still rooted. I haven't wanted to attempt to unroot it and brick it again, so I haven't been able to discover if it only fails with root or not. I will attempt to after I get my 4.3 update from AT&T, which should unroot my phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 07:20 PM ---------- Previous post was at 06:53 PM ----------
I think I recall the cache problem occurring on even unrooted phones though. The AT&T boot logo issue should be a direct problem from root though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
midge23 said:
I had never tried to clear my cache or reset my phone through system recovery until after I had already rooted. Neither of them worked for me though, it would just say error and then try rebooting. I also got stuck on the AT&T boot logo, but it was every time I tried to boot. I was stuck with my phone like this for about two months. I finnaly fixed it but its still rooted. I haven't wanted to attempt to unroot it and brick it again, so I haven't been able to discover if it only fails with root or not. I will attempt to after I get my 4.3 update from AT&T, which should unroot my phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You will attempt to what?
As of now, there is no Root method available for 4.3 on AT&T. Maybe there will be one, but who knows how long it will take. You would be better off to ODIN MF3 back to your phone (if you are currently on MF3), do a factory reset, re-root, and see if it solves the problem. If not, you can always ODIN back to MF3 again and take the OTA when it rolls out. Whatever you do, make sure you read and learn about it first because there is always risk. Good luck.
There is an odin mf3? I thought I was reading in some of the threads that there was no odin flash for mf3 and that if you rooted, you had to be super careful, cause there was no way to fix any damage done. Did I miss a thread? Cause if I did, I wanna get that flash file, so this way I could start titanium backup removing some of the att bloat.
Also even when 4.3 OTA rolls out, I dont think we can odin back to 4.2 could we, isnt there something that prevents it from going back?
As for battery, its a brand new phone, so dont think it could be that.
-Dupe post-
Related
Hey guys. I'm trying to fix my friends Defy for him. I've rooted my old Evo 4g, my wifes samsung transform, and her motorola Photon Q so I'm pretty familiar with rooting. But I'm having a problem with his Defy. Here's the skinny:
So his phone froze up on him. And after pulling the battery, it now won't boot. So I booted into recovery, and tried a factory reset. The factory reset won't complete. The little loading bars that go across the screen just keep going forever (I let them go for 3 hours straight one day). And I still can't get the phone to boot. So I figure, no big deal, i'll just root and install custom recovery. So I looked into rooting methods for the Defy, and they all seem to involve booting the phone. Does anyone have any ideas? Or know of a way to reflash the original recovery? I'm assuming the problem is the recovery. Thanks in advance for any help. And my buddy thanks you too.
You can use RSD to flash it with stock rom of your region. Do not flash any gingerbread rom if the phone never had gingerbread(you will have downgrade issues).
I don't want a Tapatalk sig!
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Any Luck M8
dhughes214 said:
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Click to expand...
Click to collapse
was just reading your post and was wondering if you have had any luck with your buddy's Defy ???
Flashing a fresh .sbf using RSDlite should fix the recovery problems, as it will overwrite it with a fresh one. The /system partition will be rewritten, also. After flashing, the phone might boot to the system already, but if not, just enter recovery and do a factory reset, now it should finish fine and boot fine, as well. (it doesn't matter if you do a factory reset before or after the flash)
Latest RSD Lite I've found is v6.1.4. You will also possibly need drivers, google for - "Motorola_End_User_Driver_Installation_5.9.0"
Keep us posted! Good luck
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
ccdsatt said:
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
Click to expand...
Click to collapse
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Its OK now
jco23 said:
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Click to expand...
Click to collapse
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
ccdsatt said:
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
Click to expand...
Click to collapse
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
jco23 said:
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
Click to expand...
Click to collapse
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
ccdsatt said:
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Most of the ROMs need a gsmfix zip flashed, but they'll work on GSM with that
Sent from my Nexus 7 using Tapatalk HD
While trying to do the hotspot mod on my Sprint Galaxy s4, something went wrong. Phone will not boot past Yellow Sprint screen. I have tried full system reset by flashing stock rom with odin, but still no go. It says pass, but when rebooting, still stuck at yellow screen. Any ideas?
How long are you letting it sit there. It takes a few minutes to boot sometimes after a reset.
Sent from my Sprint Galaxy S4 using Tapatalk 2
did you make sure you installed the right version??
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
strange odin always works for me...it takes mad long to boot but it works
Did you not take a Nandroid backup before trying this? If so restore.
This happened to me as well. Went ahead and restored. Then flashed stock with no root. Installed root and TWRP. Flashed through Odin Noobnl's bootloader upgrade file and then the latest stock kernel. Then I did a factory reset and the hotspot mod appeared finally and all is good.
I'm pretttyyyy sure the hotspot mod is for deodexed ROMs only. Make sure you are deodexed and not odexed. That will cause you to get stuck at the Sprint boot up screen.
Joe0113 said:
I'm pretttyyyy sure the hotspot mod is for deodexed ROMs only. Make sure you are deodexed and not odexed. That will cause you to get stuck at the Sprint boot up screen.
Click to expand...
Click to collapse
there is hotspot mod for odex and deodex
LIL_ROOKIE said:
there is hotspot mod for odex and deodex
Click to expand...
Click to collapse
Oh my fault, didn't know that! Maybe he flashed the opposite one that he was supposed to then?!
PS- To the OP... this thread is probably gonna be moved to Q&A.
I had this happen the other night while flashing both hotspot mod and 4 in 1 reboot mod. The only thing I could come up with (why it didn't work the first time but worked fine second time) is that I flashed from internal sd the first time but from my external the second time. Unfortunately I couldn't restore my nandroid because my phone wouldn't recognize my 64gb sd card while in recovery. (OUDHS)
To get out of it I just flashed crawj's stock rooted odexed ROM and then re-flashed both mods (from external sd) with no problems at all.
GiantJay said:
How long are you letting it sit there. It takes a few minutes to boot sometimes after a reset.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Over 3 hours
jeffvb9 said:
Did you not take a Nandroid backup before trying this? If so restore.
This happened to me as well. Went ahead and restored. Then flashed stock with no root. Installed root and TWRP. Flashed through Odin Noobnl's bootloader upgrade file and then the latest stock kernel. Then I did a factory reset and the hotspot mod appeared finally and all is good.
Click to expand...
Click to collapse
I did not make a nandroid backup. I tried flashing crawj's stock mdl kernel.
Esoteric68 said:
I had this happen the other night while flashing both hotspot mod and 4 in 1 reboot mod. The only thing I could come up with (why it didn't work the first time but worked fine second time) is that I flashed from internal sd the first time but from my external the second time. Unfortunately I couldn't restore my nandroid because my phone wouldn't recognize my 64gb sd card while in recovery. (OUDHS)
To get out of it I just flashed crawj's stock rooted odexed ROM and then re-flashed both mods (from external sd) with no problems at all.
Click to expand...
Click to collapse
I will try that ROM. I am downloading it now, but it says over an hour remaining. I'll try it as soon as it is finished.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Try just doing a factory reset and reboot.
Sent from my Sprint Galaxy S4 using Tapatalk 2
chjlfox said:
I will try that ROM. I am downloading it now, but it says over an hour remaining. I'll try it as soon as it is finished.
Click to expand...
Click to collapse
Ok. Downloaded Crawj's Stock root MDL data wipe zip file and flashed it from recovery mode. Still same problem. It was on Yellow sprint screen all night. I don't know what else to try.
chjlfox said:
Ok. Downloaded Crawj's Stock root MDL data wipe zip file and flashed it from recovery mode. Still same problem. It was on Yellow sprint screen all night. I don't know what else to try.
Click to expand...
Click to collapse
Try doing a factory reset and reboot.
Sent from my Sprint Galaxy S4 using Tapatalk 2
OK GOT IT! Flashed a stock MDC ROM. It reset but keeps asking for a software update. I am a little nervous about doing update because I don't want to lose root.
My friend has sort of the same problem..but his is not app related. His phone just rebooted itself out of nowhere yesterday...he is 100% stock..not even rooted...it also hangs on the horrid yellow Sprint boot screen....it will boot fine into safe mode. So I rooted it, installed a new stock rom/modem/kernel...and still he is having the same problem. it can not be the battery otherwise safe mode would reboot too...but I am at a loss here..some other random hardware failure from some app that isn't loaded while in safe mode??
Same issue, please help
chjlfox said:
OK GOT IT! Flashed a stock MDC ROM. It reset but keeps asking for a software update. I am a little nervous about doing update because I don't want to lose root.
Click to expand...
Click to collapse
Did you figure out a fix for the stuck at yellow sprint screen? I too, installed the odex file and am now stuck on the yellow sprint screen. my phone doesn't boot up. I went into the cwm boot up and selected restore but that didn't fix it. I went into the normal boot recovery mode and selected data wipe/factory reset and it said that this was completed; however, I'm still stuck at the Yellow Sprint Screen.
Does anyone have a fix? Any help is greatly appreciated.
lanekelley said:
Did you figure out a fix for the stuck at yellow sprint screen? I too, installed the odex file and am now stuck on the yellow sprint screen. my phone doesn't boot up. I went into the cwm boot up and selected restore but that didn't fix it. I went into the normal boot recovery mode and selected data wipe/factory reset and it said that this was completed; however, I'm still stuck at the Yellow Sprint Screen.
Does anyone have a fix? Any help is greatly appreciated.
Click to expand...
Click to collapse
Please help somebody! I am in the same boat. Call me an idiot (I deserve it) for not making a backup after rooting.
Can someone please do a step by step on how to get past the annoying ugly yellow Sprint logo screen?
So I'm stuck as well on the Yellow Sprint Screen on boot. All I did was qbking77 root and wifi mod. At the end following his video he said to reboot the phone. Well now I'm stuck. I'm ODEX MF9 with 4.2.2. I followed the instuctions step by step, not sure what happened. Any help please? Thanks
I recently reverted to a touchwiz ROM on my I337M (Bell) and a popup asking about updating my Samsung Account, and i meant to hit No, because i dont even use my samsung account, but i accidentally triggered yes, and figured oh well, no harm. Until i rebooted my device and now i permanently get stuck on the Galaxy S4 upon boot. When i go into TWRP and try to fix permission it fails at /Data/xxxxxx/xxxxx etc and says that it lacked permissions to chown or something. I tried restoring from my nandroids but im stuck on the boot loop and i get the same issue when i fix permissions now. I'm wondering if that samsung account thing has to do with OTA maybe? Did it just ruin the ability for me to use custom ROMS? It didnt even say anything about firmware update or anything.
I never had an issue switching between my ROMS, and havent changed my TWRP version or anything. I havent had a chance to try ODIN to Stock, but im going to as soon as i get home, just i find this very weird. It seems like when im restoring in twrp as well, that its not writing anything to my internal storage.
Samsung account has nothing to do with otas. But doesn't make much sense that recovery is broken now. Only thing I can think of is try flashing another rom via recovery. But most certainty odin should fix. Maybe it's a hardware issue?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Jnewell05 said:
Samsung account has nothing to do with otas. But doesn't make much sense that recovery is broken now. Only thing I can think of is try flashing another rom via recovery. But most certainty odin should fix. Maybe it's a hardware issue?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Before you go thru all that try flashing a different att loki kernel, it may have triggered something, go freeze that worthless samsung acct app. (of course when you get booted)
TheAxman said:
Before you go thru all that try flashing a different att loki kernel, it may have triggered something, go freeze that worthless samsung acct app. (of course when you get booted)
Click to expand...
Click to collapse
This is a Canadian I337M which has an unlocked bootloader, which loki isn't needed. The kernel i use on my device is the TMO KTSGS4. However i just tried odin flashing to stock last night, and it went successfully but wont boot past the Samsung Galaxy S4, and in the Stock recovery it gives the dead android and cannot mount /data. I tried flashing CWM, but upon flashing, when i try to boot into recovery, it just freezes on Recovery Booting and just hangs there and never lets me into recovery.
I created a new thread that properly explains the problem in the title, as this has turned out to be not related to the samsung account.
http://forum.xda-developers.com/showthread.php?t=2377230
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
NidexX said:
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
Click to expand...
Click to collapse
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Aww really, i totally missed that this was for sprint:/. I have the NEE version(unbranded GT-I905). Are you sure i can flash stock, what if it would reboot while flashing? It is already stock, just that I have this damn problem with the reboots;(
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
jejb said:
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
Click to expand...
Click to collapse
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
NidexX said:
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm now very stable on MF9, rooted, stock rom.
jejb said:
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm not very stable on MF9, rooted, stock rom.
Click to expand...
Click to collapse
nvm dude, seems like it's hardware failure. I tried flashing it with stock MGA firmware and the problem remains, as well as the screen ****ing up just before it is about to reboot. Well, thanks anyway!