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!
Related
Hi, this is my first root/custom ROM attempt and I can't for the life of me figure out what's wrong.
I started by installing the Android SDK and following these instructions. I got into the ClockworkMod Recovery, made a backup and installed the zip in this thread. This is the start of my troubles. When I tried to reboot, it would attempt to boot, then reboot into the Samsung recovery. I could get back into the CWM Recovery fine holding the 3 buttons.
From here I've tried everything to get back into the OS. I've wiped it several, restored my backup, tried installing a custom ROM, tried installing the stock rom, and installed the stock ROM from Odin.
Now all that happens is I see the Samsung logo for about 4 seconds before CWM Recovery shows up. Every time I reboot and any time I turn on the power from taking the battery out, it's the only thing I see.
What can I do to get back on the path and get my device working again?
ODIN your device back to stock (EC05 is the latest, use the pre-rooted one)
Then continue about your life.
063_XOBX said:
ODIN your device back to stock (EC05 is the latest, use the pre-rooted one)
Then continue about your life.
Click to expand...
Click to collapse
I think that I have done this. Is the .tar in this thread the right one? Because I have flashed that with Odin twice to no avail.
I had this same exact issue. Even after I Odin'd back to EC05. I ended up Odin'ing back to EB13...allowing it to boot up completely....then Odin'd to EC05. Then all worked just fine. Trust me...I was flipping **** when this happened to me so I just because trying anything and everything.
Quis89 said:
I had this same exact issue. Even after I Odin'd back to EC05. I ended up Odin'ing back to EB13...allowing it to boot up completely....then Odin'd to EC05. Then all worked just fine. Trust me...I was flipping **** when this happened to me so I just because trying anything and everything.
Click to expand...
Click to collapse
Wow! This did the trick! Thanks a mil!
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...
Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.
Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.
UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.
BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.
@Mardenator
your screenshot a looke liek from my adwluncher from my tab...
Lol I'm using ADW Ex.
ok i dont untersant waht you with them post, sorry.
Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
evolution2012 said:
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
Click to expand...
Click to collapse
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
hamzer11 said:
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
Click to expand...
Click to collapse
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
evolution2012 said:
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
Click to expand...
Click to collapse
Initial boots can be long but I don't know about more than 3 minutes? Not really sure about what happens if you ODiN back after TWRP? I'll let more technical folks take a stab at it. It can't hurt to wait though.
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
evolution2012 said:
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
Click to expand...
Click to collapse
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
hamzer11 said:
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
Click to expand...
Click to collapse
This was my first time ever using KIES recovery. As far as I could tell everything is wiped. I did a factory reset afterwards just to be safe so I can't say with 100% certainty. I had the custom logo after reboot for 10 seconds, then after a manual reboot it boots regularly without the custom logo.
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
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4