Related
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.
playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse
barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5
munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Hello all! I've been trying to fix my phone for a few days, and can't seem to do it, so I thought I'd make a post regarding it.
I believe the beginning of this originated after trying to go back to gingerbread from fc15 ICS. To learn from my mistakes, this is NOT good, right? lol. probably because fc15 wasn't made for gingerbread?
I was able to get into CWM, but I couldn't perform a recovery or install a new ROM. At this time (after trying a whole bunch of things to fix my device), I may or may not be rooted, but I'm almost certain I am not because I can't get into CWM. If I have to lose all of my data, I guess I will (I didn't have an SD card at the time - just got one), but if there's any way I would like to keep my data. Also, at this point, I'm at the "formware upgrade encountered an issue. please select revoery mode in kies and try again". I have been able to get rid of this screen in the past, but I'd like to know the best rout to go from here.
I have read about bricked devices for awhile now, but to attempt to link the hazy definition I have with experience, is my device bricked?
Please help me!
Thank you.
tf201
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
andddlay said:
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
Click to expand...
Click to collapse
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
CyberpodS2 said:
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
Click to expand...
Click to collapse
thanks for the reply! after flashing stockcwm-el26, i was able to get back into cwm. however, from there i'm still having trouble. it will not boo. i'm still going to try a whole bunch of stuff lol
tf201
Hopefully someone will comment on my suggestion... If you can get into cwm then I would use calc's format all zip then flash a ROM that has a great record of smooth install.I personally have never had a problem with Blazer so that's what I would flash. Like I said, hopefully someone will either agree or have a better solution before you go with my idea. Good luck and make sure if you get it going you share your leanings!
Swyped from my E4GT running Blazer 4.1 using xda premium
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
dante32278 said:
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yea what he said... Much easier than screwing around with flashing stuff like I suggested.
Swyped from my E4GT running Blazer 4.1 using xda premium
sorry for responding so late!
thank you both very much. i tried the program, and was still unable to recover the device - it always hung right at the end, unfortunately. a replacement device is in the mail, and i should get it very soon (thankfully for free).
another question i suppose i would like to ask...on cwm, it says i can mount internal storage as a mass-storage-device. when i try to do this, nothing pops up. is there a way to do this and, potentially, recovering my data?
tf201
hey guys,
( I know that there is another thread here asking that same question, but actually the questioner didn't get the perfect answer , that's why I ask this question again, I really need your help )
please I have a problem in my device,
I have Samsung Galaxy S 2 and the problem is when I switch it off after that
the phone will turn itself ON automatically, in another words, I can't switch it off.
please, can anyone tell me the reason or the solution of this problem ?
( knowing that there is no Samsung Center in my country to fix the phone for me)
thank you so much.
Do you have stock, or a custom rom? if stock, are you rooted?
Sent from my SGH-T989 using xda premium
J.Rawand said:
hey guys,
( I know that there is another thread here asking that same question, but actually the questioner didn't get the perfect answer , that's why I ask this question again, I really need your help )
please I have a problem in my device,
I have Samsung Galaxy S 2 and the problem is when I switch it off after that
the phone will turn itself ON automatically, in another words, I can't switch it off.
please, can anyone tell me the reason or the solution of this problem ?
( knowing that there is no Samsung Center in my country to fix the phone for me)
thank you so much.
Click to expand...
Click to collapse
What happens after you do a battery pull? Try that leave it out for a few seconds and see if it turns itself on again, essentially it shouldn't be able to unless your hardware button is stuck/sticky.
Is your phone insured ?
If you are on a custom rom it could be a bad download. Check the MD5 checksums and verify that your download was legitimate. Other than that. If you ARE NOT rooted, I suggest you read MULTIPLE tutorials and root your phone in addition to adding a custom ROM.
May I suggest Juggernaut V5.0. Or if you like ICS I suggest Blackedition or NexusMod
Best of luck
icepally said:
What happens after you do a battery pull? Try that leave it out for a few seconds and see if it turns itself on again, essentially it shouldn't be able to unless your hardware button is stuck/sticky.
Is your phone insured ?
Click to expand...
Click to collapse
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Illuminatiii_X said:
If you are on a custom rom it could be a bad download. Check the MD5 checksums and verify that your download was legitimate. Other than that. If you ARE NOT rooted, I suggest you read MULTIPLE tutorials and root your phone in addition to adding a custom ROM.
May I suggest Juggernaut V5.0. Or if you like ICS I suggest Blackedition or NexusMod
Best of luck
Click to expand...
Click to collapse
well I actually I installed a custom rom before, but for now I am on the original 2.3.4 version. I prefer ICS, I will try Both Blackedition or Nexus mod, I really appreciate your help thank you man.
J.Rawand said:
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Click to expand...
Click to collapse
he means that the power button might be stuck. try booting into recovery, and if your phone automatically selects reboot, you know your power button is stuck.
that's somewhere to start.
J.Rawand said:
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Click to expand...
Click to collapse
Take the Sim card and external SD card out, too. Have a drink. Put your phone back together
Sent from my SGH-T989 using xda premium
ive had this issue with darksides ROM went away I think after a bit
Sent from my SGH-T989D using XDA
This happened to my mytouch 4g.. Once u press power it turns on automativally right away.. I tried switching multiple roms and even tried unrooting it and putting it back to stock but it still happened... After many complaints tmobile insurance too it back and even gave me a brand new sensation free of charge
Sent from my SGH-T989 using xda premium
Give this a go... Back up your device beforehand.
Download Samsung Kies. Put you phone into download mode. Open Kies, and under "Tools" menu, select "Emergency firmware recovery". This will completely restore your device to stock. If you still have issues afterward, its a hardware problem.
Edit: You WILL lose root with this method. But you'll also get a definitive answer...
Unroot it and install stock
Sent from my SGH-T989 using xda premium
Is your phone plugged in when reboot? What are you charging it with? A usb cable or an actual charger?
Sent from my SGH-T989 using xda premium
I would try flashing a new ROM and especially a new kernel. Try to do it over ADB if you cant get it through recovery.
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2
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