Hey all...and to answer the number one question, yes I did do A TON of searches already to find a solution...PLEASE HELP if you have the knowledge
Phone Model: Galaxy S III (SPH-L710) Sprint 16gb
Firmware/ROM: All stock and never tried ANY customization
Problem: I think the problem happened when the phone auto updated to 4.3. Now when the phone tries to boot it just boots to the second Samsung "Samsung Galaxy S III" screen, reboots and then will get to the same screen and just sits there. One time I even let it sit there for 30 minutes just to see if it needed the ridiculous amount of time. When I try to get the phone into recovery mode (Volume UP/Home key/then the Power key) it will boot and on the first Samsung "Samsung" screen, in the top left corner in small print, it shows "booting recovery...". Then it will just go strait to the second Samsung screen then keeps rebooting twice before it will just stop on the second Samsung screen again. When I try to get the phone into ODIN mode (Volume DOWN/Home key/then the Power key) it will boot asking me if I'm sure and to press Volume UP to continue. Once I press Volume UP, to continue, I get to ODIN mode. In the top left corner it shows...
ODIN MODE
Product Name: SPH-710
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
(all grayed out) Qualcomm Secureboot: ENABLE
Then in the middle of the screen is the little Android guy. Below that it shows, "Downloading..." "Do not turn off target!!". And it just sits there doing nothing else.
I'm pretty sure I have done everything I could possible do to get it working again. From what I understand there may be other things I can do. Worse case scenario, if I must, I would be willing to loose everything on the phone and start over from scratch, if that's even possible.
There has to be some VERY smart people on here that can help me. This is my wife's phone and we don't have an upgrade until May...PLEASE HELP. Thanks all!!!
ONE MORE THING...almost forgot: We've never had the need to ever change anything on the phone so UBS debug was never turned on. Please tell me this isn't going to be a problem.
Sounds to me like the zip your phone downloaded to update to 4.3 was bad and now your system and recovery images are broke.
There isn't a MK3 tar you can flash via ODIN right now, you're probably best served taking it to a Sprint store to have them flash it.
You'd only be taking a risk trying to ODIN 4.1.2 (MD4) to your phone at this point. If the 4.3 bootloader made it on, then trying that will totally brick your phone to the point that they have to replace it.
Safest bet is Sprint store because you can get into Download mode, they should be able to get it working for you. I hope, good luck!
EDIT: there is a tar file for ODIN now
@romeoh posted this in the [STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP) thread
Finally a .tar file is available to download on sammobile website.
http://www.sammobile.com/firmwares/
Related
It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
dileepan said:
It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
Click to expand...
Click to collapse
Hm. if you boot up your phone are you stuck at the cm bootup? If you are im sorry bro you cant fix it for free by sending it to samsung. JTAG for 60 bucks or samsung for 60 bucks. Reason being that it shows that you have rooted and modded your device. If you were hardbricked and nothing would turn on at all you would be able to send it to samsung and get it fixed for free!
Well if it shows Download mode then it might be working, just not showing, if you see a blue ID:COM number in Odin its working. Try to flash a stock ROM in Odin while in Download mode and make sure its in PDA or you will brick. Check only Auto-Reboot and F. Reset time.
If it works congrats if not search this forum for a service called JTAG which repairs bricks.
\(._.\) To the window, to the wall.
(/._.)/
A little update ...
I was able to get to download mode after many trys and got back to stock -- unrooted. I should have stopped when I was ahead, but I was feeling invincible after this feat of reviving the phone and that was really stupid.
I wanted to root and flash CM10 nightly. I followed the instructions from http://rootzwiki.com/topic/32486-gu...m10-nightlies-without-k-exec-updated-8-18-12/. After unlocking the bootloader step, I wanted to backup the stock ROM I had on the phone -- I don't know why I wanted to do that as I had just flashed the stock and didn't have anything customized. Anyway, when I clicked backup from CWM everything died, kaput, nothing. I have been desperately holding the power button, reovery combination of buttons, download mode combination, anything I can think of, the phone is giving me the total silent treatment, which BTW I am used from a more human source.
Let me know if there is anything I can do, perhaps stand on one leg and try switching it on perhaps. http://forum.xda-developers.com/images/smilies/redface.gif
Sorry for the dumb jokes, I am a little frustrated, but I am sure I will get over it.
Thanks for those who took interest to read my question and those who cared to respond, I appreciate it....
Cheers!
are you getting any signs of life with the phone plugged in with or without the battery in?
jeeper11 said:
are you getting any signs of life with the phone plugged in with or without the battery in?
Click to expand...
Click to collapse
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
dileepan said:
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
Click to expand...
Click to collapse
Best advice...take out the battery, leave for 1-2 hours, insert battery, try to access download, flash stock in odin, reboot, don't flash any more Jelly Bean roms. lol
My Sprint Galaxy Nexus recently got submerged in saltwater (it was in a drybag that failed). After lots of rinsing and drying, I finally got it to turn on with the Google logo and go into a boot loop. I held vol up/down/power to get to recovery mode once and decided to do some Googling to make sure how to proceed. Ever since then, the vol up/down/power mode doesn't even work. Trying that, the phone will start up and just go to a black screen (if I'm in a dark room, I can see that the display is on, just black). As opposed to just hitting power which still shows the Google logo and boot loops.
I also can't seem to connect to adb, although I've done that many times in the past. I suspect it's because I can't get to bootloader mode. If I could get to that, I think I'd be golden. It seems, the only thing I can get to is odin mode, so I tried returning to stock using that. I was unfamiliar with that process, so I walked through the guide here and used the FH05 tar, however, it always seemed to error on the radio-cdma.img. If I remove that from the tar, it'll write fine, but nothing really changed in terms of what I could do. I was unable to find any other working tar links.
Any ideas on what to try with ODIN or help getting my adb connected or getting to recovery mode?
Hey guys, I could REALLY use some help with this. So i had my tablet Rooted. Then after a while my google play store wouldn't respond and I couldn't update any apps. So I decided to revert back to stock firmware. This was the file I had used.
(T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar.md5)
I have the Tab S 10.5 bronze.
So I installed it with Odin and I noticed on Odin it said (Succeeded 0/ Failed 0) and the tablet didn't reboot itself. so I thought okay... it must not have worked. Let me reboot the tablet myself. Mind you the screen on the tablet was still in Odin (Download) Mode. After I reboot it, it went into the same bootloop with the TEAMWIN icon popping up over and over again. So I reboot it again to try and put back into download mode. Well it wouldn't. It just popped up with the Samsung Galaxy Tab S Icon and kept repeating that spot. So once again I turned it off to try and get it into Odin mode, and now it wont turn on at all.
Okay. As i was typing this, i have the tablet connected to the computer and it just randomly turned itself on and now its in the TEAMWIN bootloop again. I don't wanna touch it until I get someones opinion on what to do next...
AWESOME it bootlooped itself again but this time when the samsung logo popped up I held the volume button and got it into Odin Mode! now.... what to do next? I dont want to try the same Stock FIrmware. Idk if it was the problem or not.
alright so here is what I just did..
The tablet rebooted itself while I was typing that message while it was plugged into the PC. It turned itself on but when it was at the Samsung Logo I quickly pressed the Volume button and had gotten it into Odin Mode. I disconnected it from the PC, loaded up the Stock firmware from the first post. Plugged in the Tablet while it was in the Downloading Odin Mode. Hit start on Odin and it did the rest. Now the issue is it reboot, samsung logos popped up and went away. the Samsung logo with the little blips of light/stars around it came up. then it said Installing Applications with a loading bar. That lasted about 2 seconds then went back to the samsung logo with the stars. Then the tablet shut off and now i cant get it back on again.....
Hold POWER + VOL DOWN
Yeah. I know that. That's how I got it into Odin mode.. Thanks for four word incredibly helpful post...
Are you sure you downloaded the correct software for your device? You could try another region's firnware or re-download the one you used.
Since you still see the Teamwin icon I guess it didn't install the firmware correctly or all of it since your recovery should be the stock one again after flashing. Or did you remove items from the .tar file you try to flash?
M1LLER_LITE said:
Yeah. I know that. That's how I got it into Odin mode.. Thanks for four word incredibly helpful post...
Click to expand...
Click to collapse
I'm telling you how to reset your device not boot into download mode smart mouth!
Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilà - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?
Hello All,
I recently found a Sprint Samsung Galaxy S3 (SPH-710T) that cannot boot to its custom ROM, CyanogenMod. The only thing I vaguely remember is a few years back when a coworker of mine had pulled out the battery when the phone was either rebooting or installing an update. The phone still boots to download mode, but when I do the combonation for recovery mode (Volume Up, Power, and Home), it shows the startup logo and blue text at the upper right corner, but then immediately shuts off. I have tries using download mode to install TWRP, but every time I do it, the program on my computer says that the process was successful, but the phone shows no sign of the program being installed. I have also been successful when downloading CF-Root to the phone, but the attempts at installing TWRP after that yeild the same result. I saw a video detailing a de-bricking SD card, but got scared after I learned that the card were not interchangeable between models. I am here for any questions you might ask and I will happily try any of the solutions provided by people.
Thanks so much for all of your help,
Max