[Q] Soft brick & Odin flash always fails, what next? - Galaxy S III Q&A, Help & Troubleshooting

Hi all,
I followed the guide in this forum to the letter, however the firmware flash fails after a few seconds. Now when it powers up, I no longer see the Samsung boot screen, I have this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies". And I can no longer access the recovery menu by pressing up volume, power & home.
I contacted the previous owner to get some more info, and found out that the phone was originally from another country (UK) and I had attempted to flash it with Australian firmware. Not sure whether this is the cause of the current issue...?
So now I've got the UK firmware, however each time I attempt to flash it, after a few seconds it fails.
In the "Downloading" dialogue on the phone, I can see information against every field: Product name (GT-I9300), Custom Binary (1), Current Binary (Samsung official), and System Status (Official).
Based on this and what I've read here, this is a good sign (ie: software recoverable, and not hardware failure). However I'm stumped on the flashing situation. I've tried Odin 3.07 and 3.04.
Appreciate any advice.

Try the rescue firmware from a sticky in general forum, follow the instructions exactly.
Sent from my GT-I9300 using Tapatalk

Related

Odin tips for better success......

folks,
With the recent number of AT$T note users having Odin troubles, I decided to post up a few of the "known" problems that jam up the device. They are Brick level issues, and I decided to share them with you in a new thread.
The information is likely already out there, but spread far, and over many threads, so this will offer you a one stop fix you "NEED" to have, in the event you are restoring the SGH-I717 device to a factory state, and you find yourself seeing the download mode "limp mode" screen.
( this screen makes you think that download mode is gone, and no longer functions, but it does)...
Many users have the desire to return to stock, and in doing so, have encountered Severe Odin issues. This particular one, has caught several users in the last month, myself as well, and can catch even the seasoned Odin user by surprise.
Follow the steps below, and you will be okay....(I hope.)
(First) : When flashing a stock Odin .tar back to the SGH-I717, you "MUST" first go into your recovery...(CWM/TWRP) and factory reset the device. This will remove the data remnants that are often staying on the device.
(this can cause an immediate force close when the device boots from a good flash restore, and can corrupt your new shiney restored rom on pre-boot)
(Second): When pushing the stock rom .tar through Odin, "DO NOT" uncheck the "reset" toggle in ODIN !!!
this bypasses a critical write step in the restore process, and forces the device into download "limp" mode. Basically asking you to emergency restore using kies.
This is because the recovery is still being written to the device, even though Odin confirms the write step as a "PASSED". and the boot must occur to finish the process.
(Third): and possibly the most important step:
"DO NOT" attempt to multi-push Odin files back to back, by turning off the reset toggle in Odin.
You "MUST" ALLOW THE DEVICE TO BOOT, between .tar flashes. Again, the reset is a feature that finalizes the writing of the files to the device, and must remain "ON"...
Now, I realize that many PC environments are different, and each device also. Not to mention user skill levels, and what is being accomplished. But with the number of folks having flash issues using Odin lately, I simply wanted you to be aware of a few things that "WILL" jam you up.
And I'm certain that a few of these "bricks", needing a JTAG repair, were not true bricks. Instead, the download mode was still there, but was asking for a Kies emergency restore in the "limp mode" screen instead.
The screen is much different, showing a picture of a device, with an "X" between it, and a computer icon. Basically telling you that your flash failed, even though Odin shows a "PASSED" in the dialogue box.
Edit:
In the event of the download mode "limp", you will see an error screen asking you to go into kies for an emergency restore.
The kies restore is not needed. As you can start Odin again, and push the rom.tar to the device from this screen. (but you "MUST" remove the cable, then open Odin and load the .tar, then plug in the device and wait for the "COM" connection to show.
If Odin fails to push the .tar, "Then" go to Kies, and emergency restore the device using the super secret code.
Standard disclaimers apply, and mileage may vary...so do your homework.
hope this helps a few of you out......g
Nicely done, good sir.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thanks G!
Bam....and another add to the GNote Super Page
[Road & Ref Map]: Galaxy Note Super Everything Thread (I717)
Thank you Joe ....
I hope this helps a few folks ...and slows down some of these problems we've been having .....g
What to do if we cannot get into recovery just download mode.
prettedda said:
What to do if we cannot get into recovery just download mode.
Click to expand...
Click to collapse
Flash.. then boot to recovery and factory rs... then reflash
Sent from my GT-N7000 using Tapatalk 2
Agreed.....g
I'm trying to use Odin to root a stock AT&T Galaxy Note i717 with Gingerbread. I can't get Odin to work. It keeps failing. Any ideas?

[Q] GT-i9300 crashed on update and now can not enter recovery

Hi there
Although this is my first post on XDA, I have been using samsung phones for about two years now and never come across this problem before. I purchased a brand new GT-i9300 four days ago and Kies notified me of a firmware update. No problem, my phone went from ICS to Jelly Bean just fine. Then today it prompted me for another update, while it went into download mode the phone stuck with the blue progress bar making no progress at all for over an hour. Now the phone keeps telling me that "firmware upgrade encountered an issue. please select recovery mode in Kies and try again.", so I connect it to Kies which recognises there has been a firmware upgrade error and takes me through the emergency firmware recovery. However, to recover it wants me to put the device in recovery mode, I know how to do this but each time I hold the power/home/volume up buttons, I get no tiny blue wording to prompt me to release the buttons and I end up and the same screen telling me to use Kies again. I've tried using Odin to manually install a stock ROM but as I can't switch on USB debugging, this has not worked. I've tried using the S3 toolkit but in it's current state, the phone is not recognised by the software although it is seen by Odin.
Apologies if the explanation is long but I wanted to be clear about exactly what has occurred here and would be very grateful for any help/tips/advice that anyone may have as I feel I have looked everywhere.
Regards
P.s. thanks for reading
One its a Samsung problem covered under warranty .
Two Odin does not require USB Debugging mode to flash stock firmware .
Three I get no tiny blue wording to prompt me to release the buttons
What tiny blue wording are you sure you are following instructions and releasing buttons at Samsung splash screen .
With your lack of knowledge i would return to Samsung if you still have warranty .
Root or SGS3 |Toolkit will void warranty .
You can of course flash a stock rom .
Basics Faqs and Guides all here .
http://forum.xda-developers.com/showthread.php?t=1927113
jje

[Q] Firmware upgrade encountered an issue.

I'm am getting the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." on bootup.
I had been working on trying to change my Bell i717 (hardware) with Rogers firmware, as I signed up with Koodo to the Telus firmware. I had been flashing the Telus ICS firmware to un-root my phone. I had just finished flashing with the copy from: sammobile.com
using this thread for help: http://forum.xda-developers.com/showthread.php?t=1483113&highlight=firmware
I tried to connect from with Kies on two different computers with different cables and neither will Connect. The computers try but I get: "Device not responding. To resolve, the issue, reboot the device." popup box - OK is the only choice. I reboot, and still get the same message.
When I go to Tools - Emergency Firmware Recovery on both laptops, I get the same result: the device does not show up the the box: List of devices requiring emergency recovery.
Next I try Troubleshoot connection error. I get: Connection error troubleshooting process is complete with a check mark. The only option is Complete button.
So the cable checks out. Windows installs the Note's device drivers when connected.
How do I get my device back?
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Thanks Kenny.
I found a solution! I bought a jig, but it didn't work.
I figured I would try one more time flashing with Odin. Odin showed that it still communicated with the phone, so I flashed the phone one more time with the Telus ICS i717D firmware from Sammobile.com. I needed to have the RESTART checkbox checked and as soon as the Note restarted I pressed the Volume Up & Down and got the Recovery mode. I wiped my caches and rebooted.
I have a working i717D phone! :laugh:
One last question, when in Download mode OR when the phone first boots up, I see on either screen i717R (Rogers). On bootup, after stating: Samsung Galaxy Note i717R another screen shows with 4G LTE Telus. In the phone properties, it shows i717D and when connected to my windows PC as well.
How or what file, do I flash my phone to change the ODIN and first screen on bootup to say i717D?
How did you get it to work? I am having a simmilar problem.. ATT i717...
Changing the boot animation:
http://forum.xda-developers.com/showthread.php?p=29240104
You will need to root your stock ROM and install a file manager to make a switch.

[Q] s5830i loops since update from Samsung

Hi,
I'm a total novice with phones.
My daughter was downloading a update from 'Whatsapp', it went to playstore and since then it loops.
It loops from turn on, through the S5830i logo then Samsungs logo. Then it loops all over again and can only turn it off by removing battery (which gets hot).
Tried the recovery mode, clearing the cache, reset to factory, my SIM nothing just the loop.
Tried the Download mode, which says ODIN MODE, PRODUCT NAME: GT-S5830i, CUSTOM BIN DOWN: NO(0 counts), CURRENT BIN: SAMSUNG OFFICAL. Beneath that it says: Downloading..... Do not turn off target !! stays like that for ever...
Tried connecting via Kies, no joy saying to insert SIM when one is already there.
Unsure if this is as you call Bricked or what to do next.
thanks
Anyone know which Firmware should be used for UK also a Rom download.
thanks
@onegalaxy, For official stock firmware the only reliable source is sammobile.com database. Just go there and choose firmware from top side and you will be directed to another page with couple of choices. If you know your original PDA/CSC/MODEM choose check firmware,, not so sure ,, choose firmware database , which requires fewer queries such as your preference country/region , model and OS type. (Android 2.3.6) model GT-s5830i
Following post are very helpful for your future troubleshooting and implantation of your Stock firmware over Odin,, some useful hints here for driver related issues ( Kies is useless, you have to do it all by yourself to get your Ideal Final result )
Thank you for the links and info.
All sorted..
thanks
Just hold vol up home and power until the screen goes on and there is a menu (recovery menu) and just go wipe data/xxx something and go yes, you navigate eith volume buttons and confirm with home button
Sent from my GT-S5830i using XDA Free mobile app
Thanks,
Did that, no joy.
Had to re-install Firmware for the phone.
All working fine now.

Booting in System issues

Hello,
I've recently acquire an used Samsung Galasy S3 (I9300) and since Android 4.3 is quite old I've decided to update the phone. So I've started by rooting the device which have gone well. Then I decided to unlock the bootloader of my phone, and for this i've used the app "EZ Unlock", I clicked on the "unlock" button and then I've reboot my phone. And this is where the problems begins. When I'm booting there is a screen stuck on the device saying : "Downloading... /n Do not turn off target!" without the little white text in the upper left corner. I eventually did managed to install a recovery, the TWRP 3.1.0. But I can't do anything, when I'm trying to flash a ROM from the recovery mode I have an error 7. I also tried to flash the stock firmware via Odin, but it get stuck. Thank you for any help.
Ps : My engliski is bad, i know.
Pss : I'm not stressed by this whole situation as the phone was already quite at the end of his life.
You've probably killed it with that ez-unlock crap..
1. Do you know exactly which variant of the i9300 you have?.
2. Does the stock firmware you're trying to flash match that device/region.
The stock firmware you're trying to flash must be android 4.3. You cannot downgrade once it has been updated to 4.3, the lowest you can go is 4.3.
3. Have you rebooted the device since? What is displayed on the screen right now?.
If you have the international (btu) version I have a stock firmware to flash via odin.
Beamed in by telepathy.
The bootloader on the phone was never locked so, as @shivadow said, the app probably did something to the phone.
What error are you getting in Odin? Post the Odin log and maybe someone can help interpret the results.
You tried using Odin with different USB cables, and USB ports?
Hello and thanks for the replies,
I did finally managed to flash android 7, I just choosed the wrong image. Sorry for my noobness.
Thanks y'all !

Categories

Resources