Help! Phone not bricked, but won't boot. - Sprint Samsung Galaxy S III

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

Related

Bootlooping

I need some serious help I have tried everything which means wiping cache, davlik, perform system reset and then tried to install this rom with the latest radio pack and tiamat 4.1 and my phone still keeps bootlooping right when I go to sign into the gmail, no matter what I try it will not work. I can't even get a logcat in adb, has anyone ever had this problem or knows what I can do to fix it
EDIT: I did have some help with putting on this stock RUU rom or whatever but I mean it still did it a couple times today, last night it was doing it every ten mins... but I would still like some help to get it to stop and so I can get back on CM 7.1
Try this
http://www.multiupload.com/RS_7QL6SAXKOD
Download the pc36img.zip and make sure that's what it says then put it on root of sdcard then go into bootloader then let it scan it will ask you if you want to update then hit yes and let it do its thing
Sent From way down Bikini Bottom
ok ill post back after I try it
EDIT: Ok it updated and everything now I believe it is a stock RUU again can I wipe everything and go to CM 7.1 now? or should I give this a day and see if it bootloops anymore and then post back
EDIT: It has already boot looped 4 times now
paperc07 said:
ok ill post back after I try it
EDIT: Ok it updated and everything now I believe it is a stock RUU again can I wipe everything and go to CM 7.1 now? or should I give this a day and see if it bootloops anymore and then post back
EDIT: It has already boot looped 4 times now
Click to expand...
Click to collapse
Wow ok so after you did what I said what did you do? Download any apps, run scripts, changed kernals anything???
Sent From way down Bikini Bottom
sharkboy0901 said:
Wow ok so after you did what I said what did you do? Download any apps, run scripts, changed kernals anything???
Sent From way down Bikini Bottom
Click to expand...
Click to collapse
nope I did not touch it I was waiting to here from you and see if it was safe to go to CM 7.1 obviously not
I even have tried to go do this RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed
and I just get a error 155 (saying its the wrong RUU) which it's clearly not
Sorry I'm stumped guess you have to unroot it and send it to sprint cuz its probably defective don't know what else to tell you
Sent From way down Bikini Bottom
That's a hardware issue. Had the same problem with mine, last year. Means an insurance replacement, since Sprint can't fix this instore. Bummer man. :-( Unles you're still under warranty, that is. In that case you could send it to HTC. Means being without for a week, but you get Your phone back. Instead of a refurbished one.
Sent from my PC36100 using xda premium

[Q] Boot hang after flashing using Odin back to stock rooted

Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.

[Q] Soft Brick,TWRPvsClockwork-Avoiding same mistakes

Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
I had a similar problem to yours last night to. Except I didn't really do anything to it. It was just sitting there charging and I took it off the charger and it was doing some kind of boot loop, But every so often it would just stop on a black screen. I lgnpst about six times back but after running root and freegee I would try to get into bootloader and it would do it again. Eventually I tried doing freegee with clockwork instead and it did it again, Than I forced the phone off and pluged it in to my computer to get ready to lgnpst again so I could at least use the phone. All of a sudden I look at the screen and there was a battery charging animation. And then unpluged it and for kicks turned it on and it booted up no problem. Then I tried booting into bootloader and all works now. It was really strange, I did put twrp back though. I like it better then clockwork. I think I sore you asking questions in irc while I was in there asking question to ha.
-Frank
MikeDroid said:
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
Click to expand...
Click to collapse
I had the same thing happen and couldn't figure it out so I took it back to sprint told them I did the update and it messed up so they gave me a new phone for 35 bucks and from now on im staying STOCK.........................
DId you try to lgnpst back yet? That may help you.
-Frank
Frank...yup that's how mine worked. Just not sure how to do this. I don't think my failed lgpnst attempts did anything, b/c mine took the update eventually. I'll keep trying. This phone is so temperamental. Does Shellnut have some input on this problem? I can't figure out why some phones take and others don't when doing the same thing.
Talk to Shelnut2 over pm or find him in irc. I just found out there is a special version of freegee that may fix the problem. I seem to have fixed mine but I sent him a pm asking some questions about the problem. I think you are going to need to lgnpst back. Then root and run the special version of freegee. You have to get it from him because it does some things different that may brick the phone permanently. Thats why you have to ask for it. From what I understand it fixes that kind of problem.
-Frank
I will. I'm going to see if this thing will self correct. Otherwise I will check with him on that. The LGPNST is something I'm not looking fwd to doing.
LGPNST is not detecting phone in dl mode but does detect when in recovery. This SUCKS. Frustrated and out of ideas.
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
frankt2012 said:
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
Click to expand...
Click to collapse
Not sure if I ran as administrator. Assumed that I did. As a casual hack, I'm in over my head.
Sent from my LG-LS970 using xda app-developers app
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Bricked OG
MikeDroid said:
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Click to expand...
Click to collapse
I've been working on mine for a day and a half. I can't figure out the thing with renaming the ".tot" file to ".bin" because I don't even see a .tot file. After I unzipped the big ZV7 there was only one file without an extension so I can't figure out if thats the one I'm supposed to rename. Can you point me in the right direction?:crying:
[ I figured it out, I had to go into Preferences on my file explorer and set it to show all file types...DUHHH ]
In Windows, go to control panel, file settings, show file extensions. Something like that.
Sent from my LG-LS970 using xda premium
Finally got bit working. No more issues. Non of this stuff is very intuitive when your in panic mode. All is good now though.
Sent from my LG-LS970 using xda app-developers app
Apps
MikeDroid said:
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Click to expand...
Click to collapse
Always backup your phone before tinkering with system files, and experimenting with launchers, kernals etc.
Titanium backup in WORTH the investment to upgrade to PRO.
Rom manager is a good one to boot directly into recovery without fiddling in the fastboot menu. And for backing up settings and roms.
Always KNOW what your doing. lol. sometimes even the big guys forget this. RESEARCH!

[Q] Weird bootloop problem...

Last month, my gnex suddenly rebooted itself when texting, then it just stuck in bootloop forever.
I got it work again only after several times of factory reset and even pushing factory image.
I was using xenon + franco at that time.
However, 3 days ago it rebooted itself again when playing a music app, then the bootloop problem happened again. Somehow it could boot, but within a minute, it reboots and bootloops again.
i was using xylon + ak kernel this time.
I started to think if this is due to hardware problem.. and i took it to store yesterday after pushing the factory image to it. they said this is due to some incompatibility of some apps... (i dun understand why factory image could have this issue...) and did a recovery for me. My phone is reset back to 4.0.4 and it seemed working fine..
Then i pushed back the 4.2.1 factory image to it and still nothing happened. i started flashing back xylon and ak kernel to see if it works. It did run perfect for the whole night until this morning. When i was installing some ordinary apps, eg. air, skout, it rebooted itself again...
Flashing factory image of 4.2.1, 4.1.2, and even 4.0.4 all do not work.
it got past the google screen, and then to the bootanimation for a few seconds and it freezes and color seems weird, and then reboot again.
i have tried flashing through the toolkit and also through fastboot command..
does anyone know what is the problem causing this...
thanks in advance.
Anyone help please..
thyau said:
Anyone help please..
Click to expand...
Click to collapse
ok lets see if my craziness can help lol
ok this will seem crazy but it is a last resort which i did the other day .
if you have nothing to lose do this its a 50-50 shot
but first
what recovery and what toolkit do you have before i tell you this
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
thyau said:
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
Click to expand...
Click to collapse
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Alpha_wolf said:
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Click to expand...
Click to collapse
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
thyau said:
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
Click to expand...
Click to collapse
nothing to lose right? might as well try anything lol
sounds like your device might have a problem with its internal storage
Alpha_wolf said:
nothing to lose right? might as well try anything lol
Click to expand...
Click to collapse
All user data has been lost due to the crash already, really nth to lose.. lol
simms22 said:
sounds like your device might have a problem with its internal storage
Click to expand...
Click to collapse
You mean physically right??
thyau said:
All user data has been lost due to the crash already, really nth to lose.. lol
You mean physically right??
Click to expand...
Click to collapse
yea, physically. when/if it finally goes, you wont be able to recover from the bootloop.
simms22 said:
yea, physically. when it finally goes, you wont be able to recover from the bootloop.
Click to expand...
Click to collapse
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
thyau said:
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
Click to expand...
Click to collapse
well, it is a common issue with the nexus devices without a sd slot(nexus s and the galaxy nexus).
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
thyau said:
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
Click to expand...
Click to collapse
Op the same thing is happening to me, i also was on xylon and it was running fine and it just started bootlooping. i tried everything toolkit, flashing factory image lie you did and nothing, the only one that works now is ics stock 4.0.4 .if i try any other rom stock or custom the bootloops starts again and it wont boot, it only boots on 4.0.4 .so pretty much the same thing happened to me .

[Q] rebooting in recovery

phone keeps rebooting while navigating in recovery mode.
tried stockcwm el26
any repack on ics
always randomly rebooting when navigating through the menus.
any clues on what might be wrong? thanks
Esk1L said:
phone keeps rebooting while navigating in recovery mode.
tried stockcwm el26
any repack on ics
always randomly rebooting when navigating through the menus.
any clues on what might be wrong? thanks
Click to expand...
Click to collapse
Rebooting during recovery mode menus?
Odd...I've never had this happen, but it sounds like you have a bad download...try to download again & reflash...could be your cable...believe it or not, the 13th Amendment to the US Constitution does not apply, all data cables WERE NOT created equal....try a different one. For that matter, a different USB port too.
Download ODIN again...whatever you did, do it all again, but with different stuff. You can never be too cautious playing with this stuff.
I have that stock rooted el26 & use it prior to flashing ROMS on my E4GT's when I buy them...I've probably put it on 50+ at this point & have never encountered this, and based off the fact your phone is still alive - logic dictates either it's a bad phone (Im guessing you would have noticed erratic behavior prior to this) or it was just a SNAFU during the update which is the horse I'm betting on. :good:
Hit "Thanks" if any of this helped (or at least entertained you)
Your power button may be going out as well.
When in doubt, I agree on re-download, maybe different cable, etc. Never had issues with recovery.
.: :: Sent from USC-GS2~PACman via Tapatalk 2 :: :.
Yep came to the conclusion that it is my power button that is going out sadly I'm too scared to open up the phone to fix. So I might go to sprint and see what they can do about it. Thanks for the help though guys !
Sent from my SPH-D710 using xda premium
Esk1L said:
Yep came to the conclusion that it is my power button that is going out sadly I'm too scared to open up the phone to fix. So I might go to sprint and see what they can do about it. Thanks for the help though guys !
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
They wont do anything if the device has a custom recovery. It is not hard to take the device apart for a fix, but you can always go to http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-power-button-repair/ and they will do it. They do amazing work and the turn around time is incredible.
graydiggy said:
They wont do anything if the device has a custom recovery. It is not hard to take the device apart for a fix, but you can always go to http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-power-button-repair/ and they will do it. They do amazing work and the turn around time is incredible.
Click to expand...
Click to collapse
well ill try flashing stock el29 with stock recovery and see what they can do, hopefully that will work
Esk1L said:
well ill try flashing stock el29 with stock recovery and see what they can do, hopefully that will work
Click to expand...
Click to collapse
Make sure that your flash counter is cleared before you take it to sprint. You don't have to do anything if you are sending it to mobiletechvideos, though

Categories

Resources