Develop Bugs

[Q] Samsung galaxy SIII hard bricked will not boot but ODIN can recognize it

Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod

If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app

i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it

You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.

chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.

Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help

Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!

serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.

Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case

serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..

Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!

DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.

Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already

[UPDATE 12/24/13 ] SOLVED! Hard-bricked? Un-hard brick using sd card SM-N900T/N9005

UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaЖ)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY

Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2

NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?

msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app

chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...

msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app

Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!

Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium

d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.

msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.

Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app

chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?

i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.

Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol

In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app

chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?

msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk

msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4

Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...

M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.

[Q] (AT&T SGH-I747) Firmware Upgrade Encountered an Issue....After Wipe

Hello! I was planning to sell my S3 because I got an S4. So after wiping the memory of the S3, it rebooted but it froze while starting up. So I held down the power button for a few seconds to restart it hoping it would work fine. But when it turned on, it immediately went to a screen that said "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can't go into Recovery mode on the phone, all I can go into is download mode. I tried to do a Emergency Firmware Recovery using Kies, but it didn't work. It either stayed at zero percent after downloading what was needed to update or it worked fine for a while until it showed up some error (I hate Kies with a passion). So I have no idea on what else to do. If I can't figure it out, I was just gonna sell it at a kiosk at the mall and just get whatever money I could get. **OH and my S3 is not or has ever been rooted.**
Please help! Thanks!
EDIT: My android version is stock TouchWiz 4.3 by the way!

Hello! I was planning to sell my S3 because I got an S4. So after wiping the memory of the S3, it rebooted but it froze while starting up. So I held down the power button for a few seconds to restart it hoping it would work fine. But when it turned on, it immediately went to a screen that said "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can't go into Recovery mode on the phone, all I can go into is download mode. I tried to do a Emergency Firmware Recovery using Kies, but it didn't work. It either stayed at zero percent after downloading what was needed to update or it worked fine for a while until it showed up some error (I hate Kies with a passion). So I have no idea on what else to do. If I can't figure it out, I was just gonna sell it at a kiosk at the mall and just get whatever money I could get. **OH and my S3 is not or has ever been rooted.**
Please help! Thanks!
EDIT: My android version is stock TouchWiz 4.3 by the way!
Click to expand...
Click to collapse
I could be off base a bit but I think you have a few options, standard disclaimer applies here if you Bork your phone worse than it is now by any thing typed below it is your fault not mine, I give fair warning of risks involved.
A) go to best buy have them flash whatever they can (this is the latest tech support info from samsung) perhaps they can fix it and you will still be official with warranty bit 0 in Grey letters,
there is very little risk involved with this option you might get into a car accident on the way to and from best buy.
B) intentionally hard brick your phone, use the SD card Debrick method, flash custom recovery such as twrp or cwm, flash a rom, bootloaders, modem and kernel. This method is not very safe, not 100% guaranteed to work nor recommended for an average user. There are significant risk involved and it will show warranty bit 1 in red letters when in download mode and it will also display flash count and custom instead of official this will also disable knox, root the phone and maybe other things I forgot about.
There is alot of risk involved here proceed with caution.
C) send/take the phone to a jtag service spend about $50 and the phone will still be official with warranty bit 0 with knox intact. There is a possibility that the phone cannot be recovered using this method so there is a low risk involved.
I recommend you use option A) go to best buy and let them try to work their smoke and mirrors. Then if that doesn't work try option B) because why not try to recover it yourself for free at home to save some money over option C) and if you are considering option C) they should be able to recover the phone so that removes most of the risk of option B) .
GOOD LUCK
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:26 PM ---------- Previous post was at 02:20 PM ----------
Btw you should try to sell it on www.swappa.com it is a great place to sell phones and it is endorsed by xda as our official market place to buy and sell, you can get between $200 and $350 on there depending on condition and buyers.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
I could be off base a bit but I think you have a few options, standard disclaimer applies here if you Bork your phone worse than it is now by any thing typed below it is your fault not mine, I give fair warning of risks involved.
A) go to best buy have them flash whatever they can (this is the latest tech support info from samsung) perhaps they can fix it and you will still be official with warranty bit 0 in Grey letters,
there is very little risk involved with this option you might get into a car accident on the way to and from best buy.
B) intentionally hard brick your phone, use the SD card Debrick method, flash custom recovery such as twrp or cwm, flash a rom, bootloaders, modem and kernel. This method is not very safe, not 100% guaranteed to work nor recommended for an average user. There are significant risk involved and it will show warranty bit 1 in red letters when in download mode and it will also display flash count and custom instead of official this will also disable knox, root the phone and maybe other things I forgot about.
There is alot of risk involved here proceed with caution.
C) send/take the phone to a jtag service spend about $50 and the phone will still be official with warranty bit 0 with knox intact. There is a possibility that the phone cannot be recovered using this method so there is a low risk involved.
I recommend you use option A) go to best buy and let them try to work their smoke and mirrors. Then if that doesn't work try option B) because why not try to recover it yourself for free at home to save some money over option C) and if you are considering option C) they should be able to recover the phone so that removes most of the risk of option B) .
GOOD LUCK
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:26 PM ---------- Previous post was at 02:20 PM ----------
Btw you should try to sell it on swappa it is a great place to sell phones and it is endorsed by xda as our official market place to buy and sell, you can get between $200 and $350 on there depending on condition and buyers.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply! I'm going to Best Buy either later or tomorrow to see what they can do. I called and they said they may be able to help. Oh and thanks for the website too! It sells for way more than I was offered! :good:

OK, so I got the chance to go to Best Buy yesterday and they wiped and put the software back on my phone. Works great! Thanks for the help!

RDup98 said:
OK, so I got the chance to go to Best Buy yesterday and they wiped and put the software back on my phone. Works great! Thanks for the help!
Click to expand...
Click to collapse
Does Bestbuy charge for that service? I'm on ATT GS3 4.3 but for some reason cannot get rid of the Super Su app and I want to be unrooted. It keeps telling me that uninstall failed. I don't care about warranty because mine no longer has one. I tried to go to a lower stock rom or even just installing the upgrade but it won't work. Thanks
In odin mode it tells me the following:
Custom Binary Download= No
Current firmware = Official
Warranty Bit =0
SW Rev Check Fail: Fuse 2 > Binary 0

Kimo49 said:
Does Bestbuy charge for that service? I'm on ATT GS3 4.3 but for some reason cannot get rid of the Super Su app and I want to be unrooted. It keeps telling me that uninstall failed. I don't care about warranty because mine no longer has one. I tried to go to a lower stock rom or even just installing the upgrade but it won't work. Thanks
In odin mode it tells me the following:
Custom Binary Download= No
Current firmware = Official
Warranty Bit =0
SW Rev Check Fail: Fuse 2 > Binary 0
Click to expand...
Click to collapse
Nope, it was free and it only took about 15 minutes. :good:

You say in the OP that you can get into download mode. When KIES says to do a recovery all it requires is download mode and not recovery mode.
If you can get to download mode, you should be able to do what kies calls an emergency recovery. It would take you to 4.1.1 then you could OTA up to 4.3. And no, this won't downgrade the bootloader. Kies will only downgrade the rom firmware. Find the emergecy recovery options in one of the menus in KIES.
edit. opps sorry, just saw that this didn't work for you.
What version of KIES are you using? there's KIES and then there's KIES 3. try whichever one you're not using, i suppose.

jack man said:
You say in the OP that you can get into download mode. When KIES says to do a recovery all it requires is download mode and not recovery mode.
If you can get to download mode, you should be able to do what kies calls an emergency recovery. It would take you to 4.1.1 then you could OTA up to 4.3. And no, this won't downgrade the bootloader. Kies will only downgrade the rom firmware. Find the emergecy recovery options in one of the menus in KIES.
edit. opps sorry, just saw that this didn't work for you.
What version of KIES are you using? there's KIES and then there's KIES 3. try whichever one you're not using, i suppose.
Click to expand...
Click to collapse
I tried the newest versions of both Kies and Kies 3 but it still didn't work. But I like I said earlier, I took it to Best Buy and they fixed it so it's all good.

Putting a 100$ bounty for someone to fix my phone (SGH-i317M)

I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.

have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you

Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.

eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck

Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.

eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?

Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app

ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps

Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.

Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.

[Q] Today's update soft-bricked my phone

Hello. Last week I got impatient with the fact that I could not write to my sd card under the newest versions of Android (thanks, Google!), so I rooted my phone with a (supposedly) unobstrusive ROM as described here: http://forum.xda-developers.com/showthread.php?t=2143479.
And today, after installing the baseband update, my phone will no longer boot. The screen just goes dark after saying Samsung Galaxy Note II.
I tried reinstalling the root, I tried installing a custom ROM, I tried resetting to factory and clearing the cache. Nothing has worked.
I really would like to have my phone back Does anyone have any suggetions?

OTA update
pstuart82 said:
Hello. Last week I got impatient with the fact that I could not write to my sd card under the newest versions of Android (thanks, Google!), so I rooted my phone with a (supposedly) unobstrusive ROM as described here: http://forum.xda-developers.com/showthread.php?t=2143479.
And today, after installing the baseband update, my phone will no longer boot. The screen just goes dark after saying Samsung Galaxy Note II.
I tried reinstalling the root, I tried installing a custom ROM, I tried resetting to factory and clearing the cache. Nothing has worked.
I really would like to have my phone back Does anyone have any suggetions?
Click to expand...
Click to collapse
Try Kies software (samsung), let me know if this works for you.

azRisky said:
Try Kies software (samsung), let me know if this works for you.
Click to expand...
Click to collapse
I only backed up some of my applications. I am not sure this will work but I will try when I get home.
If anyone else has any ideas, I would still appreciate to hear them. I need the phone for business reasons, so I need to purchase another tonight if I am not able to fix this one.
FWIW, at one point I noticed that the phone still made my speakers crackle when I put it near them, so it was transmitting *something*. The screen is blank though.

azRisky said:
Try Kies software (samsung), let me know if this works for you.
Click to expand...
Click to collapse
I'm in his exact same boat. Rooted about a month ago, the update soft bricked my phone. I've tried everything from flashing rom after rom to trying to recover in Kies.
No dice, when you try to recover in Kies, it won't recognize your device, it just saying Connecting until it asks you to reboot your device.
Any help is greatly appreciated. Been triyng to fix this for 18 hours so far
If you need any info to help just tell me I'll provide everything.
Some info:
In download mode, this is displayed;
ODIN MODE
PRODUCT NAME: SGH-I317
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3

tplaistow said:
I'm in his exact same boat. Rooted about a month ago, the update soft bricked my phone. I've tried everything from flashing rom after rom to trying to recover in Kies.
No dice, when you try to recover in Kies, it won't recognize your device, it just saying Connecting until it asks you to reboot your device.
Any help is greatly appreciated. Been triyng to fix this for 18 hours so far
If you need any info to help just tell me I'll provide everything.
Some info:
In download mode, this is displayed;
ODIN MODE
PRODUCT NAME: SGH-I317
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
Click to expand...
Click to collapse
Your specs are EXACTLY the same as mine. I am getting the dreaded SW Rev. Invalid Magic string when I try to flash from Kies. I am currently downloading a 4.4.2 ROM from d-h.st to try to fix it; I will keep you updated.
Side rant: If you're a tiny website like d-h.st, probably not a good idea to force the user to type in their credit card by hand. Seriously, I was all ready to throw money at the screen and get this stupid thing over with, but like heck if I'm going to type my credentials into that kind of site.

Just curious guys but have you all tried flashing stock rom back to the phone using odin?

jaybeerange said:
Just curious guys but have you all tried flashing stock rom back to the phone using odin?
Click to expand...
Click to collapse
jaybeerange- this will not work because Samsung Kies tries to restore to version 4.1.2, but the boot loader disallows it because it's too old.
If you have a 4.4.2 sitting around, by all means, let us know. I've been trying to download from d-h.st, but rumor has it that it will fail.
I am literally out of options.

Yeah the one from dhst is the one im talking about. I dont know why it wouldnt work. If I remember right it doesn't contain the bootloader so that shouldnt be a problem. The bootloader just wont allow itself to revert to an older version but its a 4.4.2 rom so it should work
---------- Post added at 03:23 AM ---------- Previous post was at 03:13 AM ----------
Just to be clear you know that when I say odin I mean the odin application and not kies right?

This OTA update bricked mine as well. Don't install this if your rooted!!!

I was able to take the update and im rooted and running custom recovery. Only thing I can think of that might be different is that I never took the official ota update. I flashed a stock 4.4.2 rom in recovery so im still on the 4.3 bootloader

Sweet mother of Zeus, I downloaded the 4.4.2 ROM off d-h.st, flashed it in Odin, and unbricked my phone.
Instructions for everyone else:
* Download Android 4.4.2 stock here: http://d-h.st/8HG. FYI, don't bother buying a subscription to the site to speed up the download unless you're doing it to thank the owners. Membership WON'T DO ANYTHING to help your speed. You'll just have to wait ~4 hours.
* Flash with Odin 3.0.7.
If anyone who has rights wants to post in this thread, it might be helpful.
I plan to set up a torrent tonight for anyone who wants to download it without the long wait.

Here is the magnet link: magnet:?xt=urn:btih:03336f24f4d6b9e86ca608d7766287edc7cd5d73&dn=I317-ODIN-UCUCNE5-Stock-No-Recovery.zip&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80
By all means download, but PLEASE seed if you do. I am allocating a lot of bandwidth but I can only upload so much!
PS. If you're worried about the reliability of the torrent, d-h.st provides an md5 sum that you can use to check the file after you've downloaded it.

Exactly what the guy said about flashing the stock rom is right. However, since my phone didn't have enough space, it didn't reset my phone. Maybe it works if you go into download mode (power, volume up and home) and then reboot it works. Have rebooted it twice since then and it still works. Everything is just how i had it before the update, but with the update.

no seeds for the torrent?

xCAVEMANx said:
no seeds for the torrent?
Click to expand...
Click to collapse
I don't know what to tell you. Three people have already downloaded it from me (unfortunately, none is seeding).

pstuart82 said:
I don't know what to tell you. Three people have already downloaded it from me (unfortunately, none is seeding).
Click to expand...
Click to collapse
I think the technical term in torrent speak is leeches. So your torrent has zero seeders, zero peers, and 3 leeches.

ATT update
Rule #1 of OTA. No root and stock completely.
This link here shows you every file that the OTA checks for and many other things before it does anything.
https://www.androidfilehost.com/?fid=95784891001611244
If something does not match, it craps out.
I'm downloading the Zen's ODIN NE5 from dev-host now. They must have fixed issues because it's flying.
I should have it in 10-15 minutes. I have uploaded a version that I had to androidhost, but I'm waiting to hear from Zen if he's ok with me posting a mirror.
And I need to make sure that what I'm downloading and what I have uploaded in the same. But like I said looks like Dev-Host is working better, or at least better than it has been the past couple of days.

xCAVEMANx said:
I think the technical term in torrent speak is leeches. So your torrent has zero seeders, zero peers, and 3 leeches.
Click to expand...
Click to collapse
It wouldn't be so bad if I hadn't explicitly asked people to seed. Anyway, there's pne seeder: me. Interestingly, I tried to attach to it with uTorrent, and I can't connect to the host. So maybe there's something wrong with my torrent server. If you want, PM me and I will sign in to Windows and seed from there.

Had exact same issue and flashed the boot loader and now my phone works great!
here is the link: http://d-h.st/qDY
Have a good one guys

Had a lot of hope for this, but I'm now getting one step further in my loop (I see the ATT logo spinning then it just hangs).
Any ideas?