yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] psycopanther:
are you saying you tried everything in order on the OP?
[Verizon Samsung Galaxy S III] Lemmiwinx:
Yes.Odin doesn't even acknowledge the phone at all
[Verizon Samsung Galaxy S III] Lemmiwinx:
Plus my laptop doesn't recognize the phone either.....
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Nothing here will help you, your phone is officially hard bricked because you flashed an international rom which overrode your partitions for download mode. You need a jtag brick repair.
[Verizon Samsung Galaxy S III] KevinGee:
Next time don't drink and flash.
[Verizon Samsung Galaxy S III] Lemmiwinx:
Thanks for the suggestion. Gonna do it tomorrow. Good thing its not my primary phone or I'd be screwed!
[Verizon Samsung Galaxy S III] MisterBigs:
Feel free to increment the counter on the OP by one. I was able to get my phone back from a soft brick by following these steps.

Thanks!!!
[Verizon Samsung Galaxy S III] alt230:
rooting vzw gs3

I'm totally lost. Almost all the links to root warez have been hijacked to mediafire home/sales pages. The root without odin method, root fs debugger or something like that, requires file data most of us don't know how to find and the method I used once has volatilized. I have found rooting guides but the links were dead or mediafired. Is there a safe location to get the files to root with? I can't remember it being this hard. I'm currently in android 4.1.2.
[Verizon Samsung Galaxy S III] bxlogic:
how long it should take the stock.czw_root66 in odin?
[Verizon Samsung Galaxy S III] takota6:
None of this worked for me ..ifollowed to the t, odin stops at nand.write

Edit. The first 2 steps did but 3rd did not.i have 3 different tar files to try but all fail.. I'm lost

Also I was on the latest ota to start
[Verizon Samsung Galaxy S III] gdwy89:
Most apt screen name in the forums. Thank you.
[Verizon Samsung Galaxy S III] takota6:
Let me point you to this

http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/

This one is updated , and has the missing pieces
[Verizon Samsung Galaxy S III] moldyghosty:
My t999 gs3 is bootloader bricked after flashing a corrupt file. I really want to try this, but I can't find Odin usable boot chains for my device. Asked in my q and a section and got nothing. Never been so stumped.
[Verizon Samsung Galaxy S III] CZ Eddie:
n/m

n/m
[Verizon Samsung Galaxy S III] ssojyeti2:
Am I hard bricked? What the hell do I do?

Sup everyone, I recently tried restoring my verizon sgs 3 to stock using the samsung gs3 toolkit. I feel I may have done things in the wrong order, as I unrooted my phone before I flashed the stock rom, boot.img, and recovery. Now I am left with the issue described in the first post, but when trying to flash the vralec bootchain for the first time, I accidentaly left auto reboot checked. Now whenever I go back to Odin and try to redo the process correctly, It gets stuck and It says fail after like 10 minutes. I tried the method below and also the method in the following post and neither succeeded. The pc still recognizes my phone but I am unrooted with a phone that won't boot up successfully. However I can still get to recovery and odin. Do I still have hope or am I hard bricked? Some incite please. Thanks
[Verizon Samsung Galaxy S III] Azuma73:
Followed the OP, took a couple tries, however it worked like a champ!!!! I thought I was so screwed!?!!? Mooch-ass, Grassy-ass senor!!:p
[Verizon Samsung Galaxy S III] nicholi2789:
Is there any way that you could post another link for the root66 tar? The first link doesn't work and I tried downloading the Torrent and I think I got a bad one. Could you at least post the size of the file so I know whether or not I got a good download?

Thanks for posting this thread. Super helpful.
[Verizon Samsung Galaxy S III] DKYang:
Stupid me pulled the battery in the middle of restoring an image and I couldn't boot into the recovery, it will just freeze. This helped me fix it. Just remember to pull the plug, restart odin, and plug it back in while staying in download mode.
[Verizon Samsung Galaxy S III] nicholi2789:
What was the size of the root66 file you downloaded? I just want to make sure I got a legit download and there is no md5 listed.
[Verizon Samsung Galaxy S III] james:
thanks you very much for this thread i would be out getting a different phone and costing me a ton of money so thanks again
[Verizon Samsung Galaxy S III] cmegalodon:
really frustrated.......

i posted this in the post for rooting from 4.1.2:

this was yesterday:

let me sum up my day:

i followed this thread to a t (or so i thought). i tried to install a rom abd got a message about invalid verizon software blha blah blah. After some searching, i realized that i soft-bricked my phone. i followed hero's guide to unbrick it and set it back to stock. perfect. i attempt to follow the instructions again. i got into recovery. but before i was able to select flash the Both Root and Unlocked Bootloader i accidentaly rebooted the phone (i hit the power button - i just got this phone the other day, hence new button placement). the phone works. i can get into odin. i can get into recovery. here's where it gets screwey - i try to install the cwm touch recovery from my sd card, i get a E:signature verification failed message in red. so now i try to start over. odin says fail. i tried going back to stock, but those .tar files fail too. i want to do a factory reset in recovery. before i do anything i regret, what are my options?

p.s. i started on 4.1.2

this morning, after a suggestion to re-d/l the su/bootloader i flashed that from cwm recovery and i got the the same e:signature verification failed error. what do i do? i just want to either root or return to stock and start over. i can't do either. should i reformat my sd card and start over? try a new sd card? please help.
[Verizon Samsung Galaxy S III] nicholi2789:
It seems alot of people are having trouble with the SuperSU file. I don't know why because it worked fine for me. I would say to just keep redownloading it the md5 sums match.
[Verizon Samsung Galaxy S III] MrHeyWilly:
OMG, you have saved my life!! I had never experience this kind of problems with the incredible 2 and nexus. Those were so easy. The problem I was having was with TWRP. It wouldn't boot up unless i used goo.im to go into recovery, or maybe it was because i was on 4.1.2 root. All i know, my baby is back and that is all i care about. Thank you very much for this thread. Btw, i use the "click 2 sponsors" link, clicked multiple ones but never was able to download it lol.
[Verizon Samsung Galaxy S III] meandg5:
Worked for me!

You can change this "Number of devices tested on and confirmed working: 40" to 41!:D

THANK YOU!

Just 1 thing, could only use the first boot LEC boot chain image. Couldn't get the second one to load in ODIN?
[Verizon Samsung Galaxy S III] DBCar83:
any suggestions...my sgs3 is stuck in bootloop

it wont go into recovery as it well jus bootloops

and when tried odin flashes it always fails....the VRALEC.bootchain.tar.md5/BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 way and the official vzw it clears everything tar and odin still says it fails wtf

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> VRALEC.bootchain.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

it allows me to flash recoveries in odin but not roms although the recovers dont load just bootloop and if try to load my past beans 15 rom it says encryption failed :/

any suggestions

ThanX
[Verizon Samsung Galaxy S III] zlancerman:
Soft bricked my phone (Verizon Galaxy S3, sch-i535) and used these instructions to restore it. Worked great! Thank you so much!
[Verizon Samsung Galaxy S III] itm:
Would this procedure be a sensible thing to try in my current predicament:

1. Water damage to phone, but phone booted up OK at first

2. Ran Triangle Away to reset flash counter but it didn't reboot as it should have

3. When I rebooted manually it hung at the glowing Samsung logo screen

4. Tried flashing a stock ROM using ODIN but it still doesn't get past the Samsung logo screen when it tries to boot.

Would the procedure described in the post potentially help?

Edit: 2 other things:

- The Home button isn't working any more (need a USB jig to get into download mode)

- I can't get the phone into Recovery mode - only Download mode
[Verizon Samsung Galaxy S III] elliott35:
I folowed all the steps but when i try to flash root66 i get --

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Erase...

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> boot.img

<ID:0/005> NAND Write Start!!

<ID:0/005> recovery.img

<ID:0/005> system.img.ext4

<ID:0/005> __XmitData_Read ..

<ID:0/005> XmitData Fail..

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

It fails and im stuck
[Verizon Samsung Galaxy S III] wwonka69:
I would suggest you try downloading the file again.

Peace
[Verizon Samsung Galaxy S III] djngal:
Hi guys,

I tried this guide, followed it to the letter, the bootchains flashed ok but when trying to flash the stock root66 file odin fails immediately after starting the NAND write.

Any help on what should I do next?

EDIT: I finaly figured it out and recovered the phone! I just saved another dead phone! :)
[Verizon Samsung Galaxy S III] DreadCode:
Hey , Every time I try and flash the Root66 , it always stops t the NAND flash and says failed to write. Any suggestions???

<ID:0/005> Initialzation

<ID:0/005> Erase

<ID:0/005> Get PIT for mapping

<ID:0/005> Firmware update start..

<ID:0/005> 7z(1/4) < There's a 1/4 symbol and an horizontal backwards L thing

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL!

<OSM> All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy S III] DreadCode:
Hey! I just figured it out . I was in the same boat as you. But how I fixed mine was by downloading the original jelly bean that comes on the phone , and flashing with Odin . I couldn't get this to work for me unfortunately .
[Verizon Samsung Galaxy S III] philseven:
And once that is done please please so in the future backup imei will save you a lot of headaches.
[Verizon Samsung Galaxy S III] MiamiDolFAN77:
I don't know if this is the right forum for this, but hopefully someone can help me here anyway. IHere's my problem from the beginning. I rooted my phone about 3-4 months ago on the stock OS.. It was working good, then Verizon forced that godawful update over my phone and i lost my root and got a really bad battey drain in return. About a week ago I dropped my Verizon Galaxy SIII in a parking lot onto its face. Screen scratched up a little bit and the edges got dinged up, but everything seemed to be working fine that day. Two days later my phone would start to go black randomly and I'd have to do a battery pull to get it to turn back on. This occurred randomly every few hours. Should have relaized then it was a problem and come here sooner. Fast forward to Thursday.the phone started doing it more frequently every few minutes. On the way home when I was listening to music it did it again. Upon getting home I did a battery pull and when I tried turning it back on it started up saying Samsung Custom then it would go to the Samsung Galaxy SIII logo screen, but it wouldnt get past there. At first I was able to bring up the phone into both download mode and recovery mode. Strange thing in recovery it would just have a bumch of red lines with the android guy on his back. I tried following some guides, but to no avail. Now my phone is giving me the Verizon triangle error once it gets past the Samsung custom screen. I took it to Verizon, but they were no help of course. They said its been messed with and wont be able to honor the warranty. I tried doing what was suggested at the beginnning of this guide, but when I go into Odin to flash the phone with anything ti's giving me a FAIL with no PIT etc. I even tried the PIT file with the boot 66. Still fails. I can still get into download mode, but when I try to go into recovery, It gives me a bunch of red lines of failure and then the boot sequence restarts. I dont want to think of my SIII as a blue paperweight. Can one of you knowledgeable folks be able to help me get my phone back to stock and working? :crying:
[Verizon Samsung Galaxy S III] Hero:
You don't need to flash the PIT files. Just use the bootchains and the root66 file. If they fail, keep trying or redownload the files until you get them to work.
[Verizon Samsung Galaxy S III] joedajoester:
You saved my precious device! Thank you so much :D
[Verizon Samsung Galaxy S III] my95z34:
//edit// Disregard.

Thank you for the tutorial though!! Saved my butt!
[Verizon Samsung Galaxy S III] aj8600:
Get bootloop after full odin wipe and root66, booted into recovery and it gave me a error i couldnt read in time and then rebooted and bootlooped

edit: booted into recovery, wiped and we'll see

edit 2: phone wont boot to samsung splashscreen anymore. Im pretty sure my phone is fried, I aready got a new one just trying to get this one to boot
[Verizon Samsung Galaxy S III] hexcorev2:
If it vibrates while having a blank screen as it turns on, then its hard bricked. No point in wasting your time if you have a new phone.
[Verizon Samsung Galaxy S III] tamkhanh:
I am not sure what happen with my device. It has a black screen. Didnt root nor flashed custom rom. Now it has black screen. When I plug it in a pc, pc shows it as a mtp and I can access the folders. When open odin it recognizes Com5. When I followed the steps odin stuck at setup connection.

I tried to put it in download mode but wothout seeing anything on the screen I cannot see if it is in dl mode or not. Any suggestions?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
First I suggest copying all your internal storage data before you proceed. Its good that you can access the files. Now pull the battery, hold vol down, power, and home for about six seconds and you'll feel the phone vibrate, let it go a second or so after it vibrates.. It should boot into download mode a second or two after it vibrates. Wait another five seconds then press volume up, then wait a few more seconds and you'll be entirely in download mode. There are two screens in download mode, one that asks if you want to proceed and the second is the actual download mode scree. This is why when doing this blind, I suggest you wait several seconds. I think you're going to run into issues if the display does not light up after Odin flashing cuz the next few steps in this thread require you to see the options in recovery which is much more difficult in your case.

Good luck.
[Verizon Samsung Galaxy S III] tamkhanh:
I tried that as well but it kept going straight to mtp mode. Does the mhl to hdmi work?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You should be using the Samsung USB cable to plug into your computer.
[Verizon Samsung Galaxy S III] lazarus0000:
Oh dude - you have so got to post that story somewhere. It's not often you find a phone that'll "light your fire" like that...

"I've got a revolution behind my eyes..."

--Battle Flag
[Verizon Samsung Galaxy S III] wizayne:
Try another USB port, usually ports on the back work best. If that doesn't help...

Try uninstalling the drivers. Reboot. Then reinstall them. Reboot.

See if this allows you to actually get it going. That has helped me in similar situations with Odin.
[Verizon Samsung Galaxy S III] RoxRedEye:
Thanks!!! If this method ends up working for me tonight, I will gladly donate!! Barely got any sleep last night trying to fix my phone. I've already been at it with Odin for 3 hours now. I hope I'm not up all night again. I'll keep you posted.
[Verizon Samsung Galaxy S III] jager420:
So I used the first method. After booting into recovery and performing the wipe factory reset the phone booted up, as the method said it would. I am having problems getting the phone to flash a custom ROM. I used the casual root tool to root the phone. I flashed touch recovery via GOO.im app. Installed xyz ROM and upon reboot I got a "Message Saying Verizon doesnt approve this software take to nearest store". I thought maybe I forgot to unlock so I repeated this method again and rooted and unlocked but still to no avail. Anyone know I can flash a custom ROM again??
[Verizon Samsung Galaxy S III] blackrose1:
Hi

Will work on gs3 international?

GT-I9300

Which file i should use?

Exactly same Stephen and flash same files and bootloder and root66 file?

If not

Is there any link for my bricked international GT-I9300?

Big thanks

(( هرچه بگندد، نمکش میزنند((@)) وای ب روزی که بگندد نمک ))

---------- Post added at 09:11 PM ---------- Previous post was at 08:21 PM ----------

COLOR=Red]DO NOT USE ROOT66 OR THE LINKED BOOT CHAINS IF YOU ARE ON ANOTHER CARRIER! YOU MUST USE YOUR OWN DEVICE-SPECIFIC FILES![/COLOR]

How to find my root66 and bootchain s

GT-I9300 international

Can you give me link?.. Thanks

(( هرچه بگندد، نمکش میزنند((@)) وای ب روزی که بگندد نمک ))
[Verizon Samsung Galaxy S III] JustArchi:
Don't use it on GT-I9300 or you'll brick it.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
As of this very moment, only the Samsung-updates link works. Goo.im looks to have removed a lot of stuff so the links for Invisiblek are dead. The torrent files look fine but I don't use torrents so I can't verify those.

Here are updated root66 tar files but for newer firmware through VRBMB1 4.1.2 by mrRobinson.
[Verizon Samsung Galaxy S III] MrBrady:
What did you figure out to get it to work properly?
[Verizon Samsung Galaxy S III] djngal:
There are 2 things to keep in mind, provided that you follow this guide to the letter.

1. Use the ORIGINAL Samsung USB that came with the phone. (In my case this is what saved me in my case. Although was using my nexus 4 usb cable, not a cheap chinese one, but still didnt't work.)

2. During the first flash sequence, make sure you see the PASS message. This is very important and I missed it a couple of times at the beginning because, when you start flashing after a few seconds you will see an O.K. message and it will appear that its done, but its not... you have to leave it go get a cup of coffee or something and give it a couple of MINUTES.

I must have done the procedure of this guide more than 20 times that day... After reading through the whole thread I must say that if the phone boots to download mode then you can save it using this guide. Relax, take a deep breath and follow the guide carefully. You have probably missed something if it didn't work for you. It really easy to happen because of the stress, having a non working device in your hands...

Good luck :fingers-crossed:
[Verizon Samsung Galaxy S III] psycopanther:
lol, i think i did somewhere on here before. its been a while. i still got all the pictures though lol. and Samsung will not to this day, reply to me OR send me back my broken phone like they stated they would. it was the best and worst phone i ever had lol. floor is still burnt where battery fell. oh well
[Verizon Samsung Galaxy S III] auggie43:
Can i use vlarec bootchain and use the latest odin kernel I535VRBMF1
[Verizon Samsung Galaxy S III] whoopingchow:
Sorry if I missed something, but the links to the bootchains in the OP seem to be dead. Is there another link to them I can use?
[Verizon Samsung Galaxy S III] skyss07:
This thread must be updated, I guess cause the link for downloading files are dead.

VRALF bootchain should be here.
[Verizon Samsung Galaxy S III] SignalX:
can i use this method for bricked International Galaxy S3?
[Verizon Samsung Galaxy S III] buddhafool:
This is failing for me. I can make it all the way through Odin with PASS on every step. On the recovery reboot it looks like the factory rest and cache clear fail. On reboot it eventually hangs on "Samsung Galaxy S III" splash screen. I left it there for 6 hours.

Once it makes it the the recovery section it gets a huge amount of write errors include during the factory reset, clear cache and even during the reboot. See attached. I know some errors are expected but it cannot do the wipes described:

"e:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15" (this the user partition)

"e:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17" (this the cache partition)

(It is using the stock recovery.)

I have tried all the troubleshooting steps I could find ion this thread (redownloading from many other sources, when to pull the cable during the process, flashing the correct pit file as well, different cables, samsung oem cable, three different versions of the samsung drivers.) I even made my own flashable odin image of my other phone with no luck.

This happened after I had the stock image successfully rooted and insecured then simply tried to install CM 10.2. I had just done the same on my other S3 with no problem.

I suspect if I can do the pit file correctly I can lick this but I need a little more guidance.
[Verizon Samsung Galaxy S III] oakdale_cricket:
First I was rooted with Clean ROM and encrypted per Exchange security policy at work.

I couldn't decrypt even after removing work Exchange account but I wanted to switch ROMs, so I finally figured a way to use TWRP to install CM 10.2 and then CM 11 without ever decrypting. However, I completely wiped internal storage and reformatted external SD after installing CM 11. I tried to go back to Clean ROM and when I tried, CWM said it installed the ROm, but prompted for an encryption password after restart. Neither encryption password I've ever used works. So I thought I could Odin back to stock. No such luck so far. I'm guessing it's because a portion is still encrypted, but I don't know for sure. I can get to Odin mode, but I think I've relocked the bootloader because doing a regular boot brings up the message "System software not authorized by Verizon has been found on your phone..."

Any help is most appreciated!

EDIT: I'm back, baby! Thanks to http://xdaforums.com/showthread.php?t=1984436
[Verizon Samsung Galaxy S III] Wesam-syria:
i have problem with flashing

i hope u can help me man

i cant open recovary for my s3 and each time i try to flash it by odin it fails....

i try to do the way u have explanend but it fails again

i did flash the sotck cwm and it pass but not yet open the recovory...

i can open download mode just like that and i try to flsh 4.1.1 and 4.1.2 but same thing fails

is there any way to flash to booloader?:confused:
[Verizon Samsung Galaxy S III] KevinGee:
When flashing twrp through Odin try with another USB cable.
[Verizon Samsung Galaxy S III] MWTTRON:
Go here this is page 1 Post #2 and try HERO's suggestions...

http://xdaforums.com/showthread.php?t=1840030
[Verizon Samsung Galaxy S III] udg21:
do you think this would work on a verizon galaxy tab 7 i have a similar problem in recovery get errors cant mount E: yada yada.
[Verizon Samsung Galaxy S III] Andrew.80:
i have a really weird issue i got this is vzw s3 and its in a bootloop it will only go to the galaxy s3 logo and then black screen and keep vibrating.

it will not go into recovery at all . it will go into download mode but only for a couple seconds then black screen. bought a jig and same thing it will read in odin for a couple seconds after the black screen but not long enough for it to flash anything any ideas i have been looking for days for another way to fix it but i cant find anything