yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Tiawaz:
That's just it, I think that is exactly what *ucked up my phone. Because the instructions for "replacing the boot loader" advised me to copy the debrick.bin file from the 4.4.2 compressed folder I downloaded.

Catch is there is only a .img file in there. I documented this in my original post. If you could direct me to the proper file, and how to go about doing it now that I cannot do it from a terminal running on the phone that would be amazing.

Like I said I am a bit out of my element, but I can follow information. I had gotten a bit creative and figured since .img and .bin and .iso and .nrg are all images, I could just convert the .img to a .bin with poweriso and use that but I guess I was mistaken.
[Verizon Samsung Galaxy S III] BadUsername:
That's a bit out of my skill set, so the instructions aren't working for the file you have? I've never seen someone successfully do this from a terminal emulator.

I'm not quite sure you're able to, and I think this has to be done from a computer. If that file you downloaded booted your phone then it's the right file. Ignore that it's only a single image file, the rewrite process should rewrite your boot chain if done correctly.
[Verizon Samsung Galaxy S III] Tiawaz:
Ok it looks like we are on the same page.

I don't know enough about android to tell if the .img and .bin extensions are interchangeable otherwise I would have renamed the .img to unbrick.img and used that name in the DD command instead of unbrick.bin that it has me use to write it to the phone.

Now since we are on the same page, the .img when written to the SD card does boot the phone. From what I can tell it looks like when I used the DD command and rebooted the phone it wiped the mount points for /data /cache etc. Which is why it's telling me it's getting errors and the factory restore can't continue because it's trying to write to those? Does that sound accurate? I'm out of my element here too.

---------- Post added at 04:23 AM ---------- Previous post was at 04:18 AM ----------

Additionally, how would it be done from a computer to phone interface.

I know there is an ADB toolkit for doing this junk from a computer terminal window, but if I'm not mistaken I have to have developer tools and usb debugging toggled in a running android OS for that to work lol.
[Verizon Samsung Galaxy S III] BadUsername:
can you post a screenshot of the file and the folder from either your phone or the computer? I don't see how your phone is booting from an image file.
[Verizon Samsung Galaxy S III] Tiawaz:
the 4.2.2 .img file I extracted from the compressed archive. when written to the SD card using the image writer specified in the OP, does boot the phone.
[Verizon Samsung Galaxy S III] Adreneline420:
Edit: Disregard

Worked perfectly thanks!
[Verizon Samsung Galaxy S III] huzaifaaleem:
Dude if I weren'r broke I would definitely have given you some donation. Thanks a ton for this guide and collecting all the files here!
[Verizon Samsung Galaxy S III] Youdoofus:
This debrick method works on most galaxy phones too. Just need the specific boot.img file is all
[Verizon Samsung Galaxy S III] elfico:
Hello everyone. I tried unlocking my bootloader using Casual, after I root and unlock successfully, I installed recovery and the prompt says the phone will reboot into recovery. I accepted and the phone went blank. I tried turning it on but with no success. I am trying the method the here and I want to know if I can use a memory card of 8GB. Thats the best I can get right now given the circumstances. My device was on stock 4.1.2 I900XXMF1 . Please any help is deeply appreciated. I just bought this phone after losing about 3 other ones in within the last ten months and can afford to lose another one right now.
[Verizon Samsung Galaxy S III] elfico:
Hello everyone. I just hard-bricked my device and I am trying to follow this guide. Please can any one point me to where I can get a 4.1.2 Debrick file? I would really appreciate any help. Thanks
[Verizon Samsung Galaxy S III] LightC:
Tried flashing the NE1 and ML1 modem after downgrading to 4.1.2 and bricked my phone again somehow. This time it was a bit different for some reason and I can't debrick using the debrick.img method!

Here is what I did:

- Downgraded to 4.1.2 using this method (I was on 4.3 ML1 previously)

- Rooted, flashed insecure aboot, installed the latest version of TWRP

- Flashed the NE1 modem only using TWRP resulting in the triangle error

- Flashed the ML1 modem only using TWRP which still resulted in the triangle error

Both modem flashes resulted in the triangle at bootup where it says that Verizon detected unauthorized software.

I was still able to get into download mode at this point so I thought I would ODIN flash the original ML1 firmware and start the process all over again.

When I did this and ODIN rebooted the phone, I was hard bricked!

All three debrick images do not get my phone to boot this time. I'm unable to get back to ODIN or to get any response from the phone. Previously, I was able to use the debrick.img for 4.3 when I had flashed a NE1 modem with MF1 firmware on the device. I've tried a number of burns of the SD card with the same debrick.img but have had no luck.

I guess I have to say goodbye to this S3 unless anyone has any ideas!
[Verizon Samsung Galaxy S III] Youdoofus:
Get the boot.img from the tar.md5 with the correct bootloader, format a SD card, mount the image to that card, put it in your phone and reboot

---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------

Keep trying different boot images. It'll eventually work when you have the right one
[Verizon Samsung Galaxy S III] LightC:
Can you elaborate on this? I have the original tar.md5 and the boot.img file that was working on my phone. Do I just need to write this img file to the SD card using win32discimager? That didn't seem to work to get my phone to boot.

Before my brick, I tried to flash d2vzw_NE1_modem.zip, where I started getting the triangle with the verizon unauthorized software error. I then flashed I535VRUCML1.modem which I believe was my original modem. This didn't fix the triangle unauthorized software error upon boot to my surprise.

I then flashed ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5 which should have brought me back to stock ML1. After this is when I experienced my unresponsive hard brick. Perhaps the hard brick has something to do with flashing the NE1 modem which locked up the boot loader?

I have tried all three debrick images but have had no luck.

Any other ideas? This SD card worked previously on this phone with the debrick.img. I'm surprised it no longer works.
[Verizon Samsung Galaxy S III] Youdoofus:
I use iso to USB. Format the SD to fat 32, mount the image, put the card in your phone and boot
[Verizon Samsung Galaxy S III] LightC:
ISO to USB cannot read the boot.img that is in the tar.md5 for some reason.
[Verizon Samsung Galaxy S III] Youdoofus:
There are a myriad of free .exe's that accomplish the same task
[Verizon Samsung Galaxy S III] elfico:
Thanks for the response. I have tried it with some of the files that the OP posted. I was on 4.1.2 before the hard-brick. I tried with all the files the OP uploaded but none worked. So I tried with the Debrick for 4.4.2 and I booted up but showed me that the firmware is unauthorized and I should contact Verizon. I tried to boot into ODIN mode and I was successful.

I am trying to get the firmware so that I can follow the method you posted. However, I dont know which baseband I should get. Before the brick, my phone info (*#1234#) showed that my AP, CSC and PDA is I9300XXMBF1. My baseband also showed I9300XXMBF1 and model number as I9300. But I am sure it is a verizon made because my laptop recognizes it as SCH-I535. I checked the page for I9300 and could find no matching file. I Checked the page for I535 and found a file with baseband I535VRBMF1. Should I use this file?

Thank you.

N.B: Though the phone is a verizon phone, I am using it in Nigeria.
[Verizon Samsung Galaxy S III] Youdoofus:
That's weird man. The i9300 and i535 are two completely different models. Well, I can tell you that any boot.img file you use won't hurt your phone as it'll only boot from the SD card until you move the IMG to your device via terminal emulator. So, the MF1 tar.md5 should be fine. You're good to go ahead and use that file
[Verizon Samsung Galaxy S III] elfico:
[MENTION=3695297]youdoofus[/MENTION] thanks. The phone baseband is actually I9300XXBMF1. Thats why I think the SCH-I535 of I535VRBMF1 should work. I checked the back of the phone and the model number says I9300 but the specifications do not match that of I9300 but that of SCH-I535. E.g It has a 2GB RAM and a qualcomm snapdragon s4 chip set running a 1.5GHz dual core. I still dont understand why it shows as I9300.
[Verizon Samsung Galaxy S III] vzw:
Ok pulled the old gs3 i535 out to install pokemon for my kid but ALAS you need to be on 5.0 or higher to run it. My gs3 is running 4.4.4 after search and searching I was able to get root but the boot loader was locked Odin was seeing it but failing to flash recovery. Found an apk that stated unlocked bootloader for gs3 so like an idiot i figured I'd give it a try worse case I would just find the images and reflash using odin... Well it hard bricked won't power on. I found the debrick.zip file but it is for 4.4.3 and nothing above that. MY QUESTION IS: Is there anything that can be done?
[Verizon Samsung Galaxy S III] ShapesBlue:
Your stuck on 4.4.2 there wasn't anything above that with any OTAs on the locked bootloader

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] vzw:
Thanks for your reply

So if I was on 4.4.4 and hard bricked will the 4.4.3 or the 4.4.2 debrick work?
[Verizon Samsung Galaxy S III] ShapesBlue:
4.4.2 there was never an OTA to 4.4.4. You should be able to recover from the debrick image but I'm not 100% on that

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Silver hawk 555:
Will this work on mine ?

will this method work on my s3 ? the thing is.......i'm having a

GT-i9300

so will this debrick file work for me ?

i was trying to flash twrp recovery. :( and to my luck i bricked(hard) my phone.

and if this debrick file does't work would please tell me where i can get debrick file my GT-i9300?

thanks..............:o:o:o:o
[Verizon Samsung Galaxy S III] SeriousSet2:
Would the same principle work on a lg k8 (350n)? if so do u have a source for a debrick file?
[Verizon Samsung Galaxy S III] ilmentor:
Would this work for a galaxy s3 i9300 4g.i think I hard bricked it. I used an app to unlock the bootloader but it seems that app is for another s3 modal. Now my phone don't wanna turn on at all.
[Verizon Samsung Galaxy S III] PaulPizz:
You need to find the debrick.img for your phone and baseband the phone is on and it should work.
[Verizon Samsung Galaxy S III] ilmentor:
How may I know my phone baseband plz. And it doesn't seem to be a debrick. Img for this phone around.

---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------

Wouldn't the debrick. Img in the first post work.
[Verizon Samsung Galaxy S III] ShapesBlue:
[MENTION=5884944]One2lv[/MENTION] was all that nonsense really necessary???
[Verizon Samsung Galaxy S III] One2lv:
http://192.168.43.40:2121

Fri Nov 18 14:12:34 PST 2016
[Verizon Samsung Galaxy S III] RedNak71:
[MENTION=4725496]ThePagel[/MENTION] Hey thanks for the guide. Friend asked me to root his s3. I did it and then tried to unlock the bootloader but didnt know about the OTA that locks it. It was dead in the water. This guide helped me get it back up and running. It would at least power on after this so I could use Odin to flash the stock recovery. Thanks again.
[Verizon Samsung Galaxy S III] Forsonkwesi:
hi, ive tried my best but its still not working..

i have burned the files on my sd many times.

am so frustrated.

please contact me on my email : forson.kwesi@gmail.com , since i might not be able to come here regularly.

thanks a zillion.
[Verizon Samsung Galaxy S III] Forsonkwesi:
Hey guys thanks a zillion .....it worked oooo how happy I am....and guess what I jux needed to boot it and use a pit file and reflash custom twrp recovery.....I got my ROM and all files intact and safe:D
[Verizon Samsung Galaxy S III] akiraO1:
wow!! so i tryed to unlock the bootloader with that unlock apk and got bricked but this fix worked like a charm. gunna reflash firmware and see if it will boot without sd card.
[Verizon Samsung Galaxy S III] AndroidJulio89:
I hope someone can help me. None of the original post files worked for me, I tried 5 times each, I noticed that when win32diskimager writes in my sd it leaves a "image" folder and all the files INSIDE it, shouldn't be the files in the root of the SD instead of a folder? thanks in advance.
[Verizon Samsung Galaxy S III] akiraO1:
Make sure to format thw SD card first and follow the instructions to the letter and it should workit. It's worked 3 times for me so far and once it does work, reflash the firmware so u can take the SD card out :)
[Verizon Samsung Galaxy S III] AndroidJulio89:
Well, it finally worked for me, I used a class 10 32gb SD card and it worked with the 3rd file, I transfered the file using console emulator, when rebooted my device became stuck on the boot logo but I finally was able to access download mode so I reflashed the stock firmware. Its too bad I'll never be able to taste marshmallow in my S3, a bootloader workaround was never founded right?
[Verizon Samsung Galaxy S III] akiraO1:
Look up stafestrap recovery for the Verizon GS3, it's the only way right now to flash roms on the Verizon GS3.
[Verizon Samsung Galaxy S III] AndroidJulio89:
Wait, it its really working for the I535 how come that I never found anything?
[Verizon Samsung Galaxy S III] swagkiller420:
well i tried to mount 4.3 on to an sdcard but didnt work tried 4.4.2 with another sdcard and it didnt work either and now both sdcards are completly corrupted since it will crash any program that tries to use the sdcard so now i cant even recover them.

any help?
[Verizon Samsung Galaxy S III] JeRiCkY_pOpS:
can i use 8gb class 6 micro sd??

---------- Post added at 05:29 AM ---------- Previous post was at 05:11 AM ----------

will this guide work to fix "system software not authorized by Verizon"??
[Verizon Samsung Galaxy S III] Etheralrealm:
hey, i have an old i535 that has been bricked for a while now, last time this happened it worked but now i just get a buzz and thats it. I was trying to port a version of lineageos for it and ****ed some **** up. any ideas?
[Verizon Samsung Galaxy S III] akiraO1:
when you flash the stock firmware via odin, use a pit file click repartition, also click nand erase all and flash, that should fix the problem.
[Verizon Samsung Galaxy S III] kingwaqar:
i unlocked bootloader with ez unlock will this method works for me because this sdcard and jtag has same prices
[Verizon Samsung Galaxy S III] 3mad7ajeb:
32G sdcard calss 10

hey can i use 32G sdcard class 10

for my s3 !

my phone Internal storage is 16 G

can i use it ??
[Verizon Samsung Galaxy S III] noidodroid:
Apparently you will need a Samsung Class 10 16GB card in order for it to work. I do not understand why a Samsung card is needed. I never had any luck myself with other brand SDCards and never got to the point to buy a Samsung. I found 2 donor S3's one a Tracfone and the other a Verizon for $6 a piece. Both worked ! Going to sell all i have if i can find another 1-2 donors with mint bodies then just swap out the motherboards. This might be a better route for you to take. (Was for me)...

Bit off topic but.. One thing I will have to admit.. Replacing the digitizer on these S3's is near impossible.. The glass adheres to the LCD. I got maybe a quarter of a screen removed and still there was too much film left on the LCD. It is better offer to buy a whole assembly or better yet a donor phone and just build up something. Super easy.
[Verizon Samsung Galaxy S III] YodaDude2011:
Im using ES File Explorer and i can't find the debrick.bin anywhere. I see these directories: Android, images, LOST.DIR, and System Information in the sdcard. help!
[Verizon Samsung Galaxy S III] darkherman:
I work with my SD 64gb A2, previously I tested with 8gb class 4 and it did not work

it is recommended to use a fast memory with high gb capacity

---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------

@SpyroDazee

update it post and add this as a minimum requirement
[Verizon Samsung Galaxy S III] noidodroid:
Make sure you have enable all files to be shown. Hidden files. Also make sure you have switch to the correct drive that you have put it in and that you are using a file system that is readable under the operating system you're trying to view through which I'm assuming would be Android.

---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------

Enable hidden files. Make sure you actually have the file on your card or on your phone that you are trying to view. Sometimes it's easy to forget.
[Verizon Samsung Galaxy S III] sinnersays:
Sorry for bringing this topic up again, please feel free to delete or move this post, in case I should habe opened a new thread.

It seems like an old Galaxy S4 mini of mine is bricked. I had it charge over night and it was dead in the morning. Doesn‘t turn on or give any sign of life. Only when I connect it to a PC it says „qhsusb_dload“ in the device manager.

Now I wonder wouldn‘t it say the same though if there was a hardware fault like a short circuit around the charging or power management or anything?

How to be sure wether it is hard bricked or „just“ a short circuit or something else?

And ultimately how to fix this on an s4 mini?
[Verizon Samsung Galaxy S III] studiorat:
I took the update and fort Knox took away root and Locked up my Bootloader ....... So i rooted and then stupidly used EZ-Unlock on my bootloader that gave me the pop up Bootloader unlocked that was easy!!!!. So I installed TWRP and rebooted and BOOOOOM ..... Down I went!!!!!

I found this on XDA and I used it and it worked for me on 2 devices without the Class 10 SD Card, I used a stock 16GB card from best buy that I had laying around. but all other steps were the same, Just Saying!!
[Verizon Samsung Galaxy S III] pyx4:
Please Help!!!

When I do the above commands in Android Terminal Emulator, it says:

Cannot open for write: Permission denied

I do not have root access and cannot boot into download mode, nor can I boot into recovery. I can only boot off of the sdcard. Is there any way that I can get this phone to boot without the sd card? Please help!
[Verizon Samsung Galaxy S III] Pikeypete:
You have to have your S3 rooted. Hence the "SU" (SuperUser) command in the terminal emulator.

I don't post very often as I don't believe in commenting on posts unless it's justified but I have to say, a HUGE thank you for this post and contribution, you saved an S3 that I was working on. The EZ-Unlock ,APK file had screwed the up phone resulting in not being able to power on at all.

Thank you greatly, an awesome contribution. :good::good:

Pikeypete
[Verizon Samsung Galaxy S III] pyx4:
I tried rooting, but whenever it reboots it stays off. When I turn it back on again using the sdcard, I don't have root access, hence I can't do the above command.
[Verizon Samsung Galaxy S III] ThePagel:
Did you use safe root? If not its the only way to root s3 on 4.3.
[Verizon Samsung Galaxy S III] droidshadow:
You have to boot into your phone with the sdcard. Your bootloader on your phones internal drive has been corrupted so that is why you can only boot off of your sdcard. When you boot up your phone it looks for a bootloader, since the one on your internal drive is messed up your phone looks for it on the external drive aka your sdcard. this is why when you remove your sdcard you can't boot your phone. in order to fix your internal drive bootloader you first need super user access in a terminal aka root access.

Here is what you do...

Make sure you have the Samsung USB drives for your windows based os such as Win7. Then download saferoot.zip which you can find here on xda or with a quick Google search. Next connect your phone to your computer with your USB charging cable that came with the phone. When you see that your computer has recognized your phone then run the saferoot exploit with the .bat file I believe.

Now saferoot will say for your S4 but you have an S3...don't worry it will still work. You may have to run the program a few times to get it to work correctly I did.

once you are rooted make sure you have supersu installed reboot your phone so the su binary takes.

After that download the app root checker from play store to make sure your phone ia properly rooted. If all goes well and you are rooted then proceed to run the commands that were given in this tutorial. You need to run the commands in Android Terminal Emulator and before you enter the commands you need to run 'su' in order to evalate your privlages so that you have the correct permission to execute the commands in the tutorial.

I hope this has helped clarify things for you and helped you out, if it has show some love and hit the thank you button!

droidshadow
[Verizon Samsung Galaxy S III] BeansTown106:
thanks for putting this toghether spyro! i succcesfully unbricked my bricked s3 :D i actually used a 32gb class10 uhs1 sdcard so the 16gb limit isnt neccasarily true. again thanks and im gonna reccomend to [MENTION=3125148]kennyglass123[/MENTION] to pin this
[Verizon Samsung Galaxy S III] pyx4:
Thanks a lot!

Thanks so much for this post! You were right, I had to attempt the root a few times before it worked. It seemed that while it was trying to root my phone, my phone switched from "Installer" to "Media" which interrupted the root. At first I didn't think anything of it because I thought it was telling it to do that, so I waited for my phone to go into "Media" mode and then ran saferoot. It worked immediately.

Now the only thing that is still not right is when I boot the phone up, when it says Samsung there is a picture of a padlock under it, and under that it says custom. I can't figure out how to remove that. Before 4.3, I would just boot into recovery and install a fixedbootloader.zip file (can't remember what it was), and that would take care of the "custom" screen.

I also can't boot into recovery now, even though I did the above instructions and restored stock recovery. Anyone have any suggestions?

Thanks a lot for all the help guys. XDA is the best.
[Verizon Samsung Galaxy S III] buhohitr:
Once you updated to 4.3 you only can boot into download mode, are you able to boot to download mode(holding the 3 buttons method)? Also you can safely ignore the custom lock, it's a bug with Samsung, even a facotry phone does this.
[Verizon Samsung Galaxy S III] pyx4:
Yes, I can boot into download mode. Now the question is can we still get rid of the custom binary download count?
[Verizon Samsung Galaxy S III] SpyroDazee:
Thanks beans!

Good info to know, after several people said it isn't necessary, I might as well change it :cool:

That you cannot do. Bootloader locked = no modifying at all (except for xposed framework)

What I did instead of using the terminal is boot from sd into recovery, then remove sd, use sd formatter to bring the sd card to its original state, then move the 4.3 update.zip to the sd card and proceed to flash from there. Also, if you can get into download mode and want to go to full on stock unrooted again, you can use ODIN and the 4.3 .tar file, still won't reset your counter.
[Verizon Samsung Galaxy S III] WNThinks:
Hey there, I am on Linux and it keeps on saying 'Permission denied' when I input the second line of code. Also will the Linux version work on Mac?
[Verizon Samsung Galaxy S III] ThePagel:
Did you log in as root? Type su then login and try or type sudo before the line stated above.
[Verizon Samsung Galaxy S III] WNThinks:
Thanks but I found what happened. Does my SD card need to be bootable?