yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Koala23:
and cannot find this files for this model
[Verizon Samsung Galaxy S III] Droidriven:
This thread is for the S3, not S3 mini.

Try looking in the S3 mini forum/threads.

I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] Farabomb:
I've been trying to flash the first 2 but only once did I get a PASS after the flash I went to flash the second one and I got reset. I've tried it for hours but I can't even get it to pass again.

I'm kinda stuck now. I can root and install TWRP for some reason but I can't get the bootloader unlocked so I'm stuck on 4.04 or the 4.1.1 I can get to install. Casual, ez unlock all can't get me unstuck.
[Verizon Samsung Galaxy S III] geepounds:
Samsung GT-P3100 Phone Restarting after every ten seconds

Hello everyone, Please I need help urgently with my GALAXY GT-P3100. It keeps restarting after every 10 seconds. I think my carrier (VOD) UK recently upgraded something on their server and my device was unable to successfully complete the installation as I am not in the UK. I have done all I can think of, which includes perfoming factory reset, flashing via odin with the same stock (VOD) firmware, flashing via odin with both Arabic and India repair firmwares by Rev04_user_low_ship, flashing the pit via odin, Installing via ADB and SD card and many more.

I'm guessing my device is on "Read-Only". Is there something I am missing? The stock (VOD) firmware gets stuck and fails at system.img while flashing with odin. Although, I get a pass while flashing with Rev04_user_low_ship Arabic and India repair firmwares, the phone returns to same problem after reboot. I get "E-Verification Signature Failed" while trying to Install via adb or SD Card and my recovery shows "MANUAL MODE Applied the CSC-Code : VGR did not match sized system/csc/common/system/csc/others.xml(No data available)". I have never used Custom ROMs or Recoveries on my device. Please what's the solution to this problem.
[Verizon Samsung Galaxy S III] tafkam4055:
My phone seems to get stuck on 'system.img.ext4' during flashing process in ODIN. Any help would be really appreciated.

UPDATE:

Figured it out.

The post on page 3 with the pics was really helpful.

I had to wait for the process to go from the Blue "RESET" state to the Green "PASS" state when I flashed the first 2 bootchains

Something else random.

I had to Re-Name my VRALF file to "BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar"

I believe it had dashes when I downloaded it
[Verizon Samsung Galaxy S III] dgm_mixtoon:
this work for d2can variant?
[Verizon Samsung Galaxy S III] Droidriven:
With the correct files for your specific model number......yes.
[Verizon Samsung Galaxy S III] noidodroid:
Great guide. Bookmarked it incase I run into this after unbricking my now hard bricked S3 d2vzw. Second Samsung in my time I have ever managed to sink to Qualcomm 9008. Never have this kind of luck.
[Verizon Samsung Galaxy S III] xXCharlyGhostXx:
we have the same problem in s3 mini "movi_write card_status" Odin download mode, any solution.
[Verizon Samsung Galaxy S III] Smil3yWulf:
can u help me out to unbrick my verizon samsung galaxy S4..its hard brick, the computer recognized it as Qloader port
[Verizon Samsung Galaxy S III] Sleepy-T:
Well, I was 'bit' as well. I was so careful in checking MD5 sums earlier I got careless in the most recent Synergy update and forgot to check. It was a bad download (I checked afterwards and the md5 didn't match.. I deserve this pain). The phone is stuck at the 'Samsung' screen you mentioned. Tried this odin procedure in this thread but can't get a success when flashing the bootchains via PDA. I get 0 successful / 0 fail. The rest of the turorial/instruction leaves me behind as I no longer have the next step options.

I just want to get this phone to boot up again. Lesson learned. Please help me.

anyone who helps me get back on my feet has a beer on me. honestly. :fingers-crossed:
[Verizon Samsung Galaxy S III] h311sdr0id:
Did you try BOTH of these?:

-

METHOD 1 (OP)

METHOD 2

-

This also happened to me a few times. Try installing both bootchains and if that doesnt work, then just try installing the second one before you flash "root66".

-

Download ODIN here.

-

Download Drivers here.

-

Download VRALEC here.

-

Download VRALF2 here.

-

Or, download

both

VRALEC and VRALF2 zipped together here.

-

-

INSTRUCTIONS:

Re-install the drivers.

Then open up ODIN.

Plug in your device (make sure it recognizes your device, it should say "Added" or something like that).

Wait for the drivers to load all the way (Windows 7).

Make sure ONLY "F. Reset Time" is checked".

Click on the checkbox next to "PDA".

Then load your first bootchain(VRALEC) (depending on which method you are using [you can try both VRALEC[1st] and VRALF2[2nd] or just try flashing the VRALF2] ).

Press "Start".

Let it run through until you get the green "Pass".

Unplug your phone.

Exit out of ODIN.

Start up ODIN again.

Plug-in your phone (make sure it recognizes your device, it should say "Added" or something like that).

Make sure ONLY "F. Reset Time" is checked".

Click on the checkbox next to "PDA".

Pick your second bootchain(VRALF2) (depending on what what method your using).

Press "Start".

Wait for the green "Pass".

Unplug your phone.

Exit out of ODIN.

Start ODIN back up.

Plug your phone back in (make sure it recognizes your device, it should say "Added" or something like that).

Make sure ALL 3 checkboxes are checked (Auto-Reboot, F. Reset Time, Nand Erase All)

Click on the checkbox next to "PDA"

Click on the "PDA" button

Find/Load "root66" (that you have already downloaded)

Press "Start".

Wait for the green "Pass".

Unplug your phone.

Your phone will try to boot, but will not get passed the cheezy Verizon boot-animation.

Take your battery out.

Put your battery back in.

Start your phone in Stock Recovery (hold-down volume-up+home button+power button).

On the Recovery Menu, it will show a few errors in RED. This is normal.

Do a "Wipe data/factory reset".

Then do a "Wipe cache partition".

Now "Reboot" your phone and wait.

That SHOULD do it.:cowboy:
[Verizon Samsung Galaxy S III] Sleepy-T:
I appreciate the info. I am up and running and will save what you posted in case something happens. I learned my lesson though. Thanks.
[Verizon Samsung Galaxy S III] Immolate:
Worked for me. Had to unplug and restart Odin between flashes to get it to work, but went smoothly at that point.
[Verizon Samsung Galaxy S III] h311sdr0id:
Wait, so did you figure it out already? What did you do?

---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------

I am glad you were able to get it working. Did you do anything differently? I am really interested in any other methods people are trying.
[Verizon Samsung Galaxy S III] espnaholik:
Help

I made a mistake and flashed a cm10 rom on a locked bootloader. I cannot find the stock.vzw_root66.tar file anywhere for download. Currently my phone is stuck at the verizon system software not authorized screen. If anyone knows where to get this please assist. Megashare is not working.
[Verizon Samsung Galaxy S III] Hero:
Use the torrent. Download a bit torrent client like utorrent first.
[Verizon Samsung Galaxy S III] GarethD:
<ID:0/006> Initialzation..

<ID:0/006> Erase...

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

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

<ID:0/006> 7z¼¯'

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

<ID:0/006> FAIL!

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

Does anyone have any idea why my format failed. I followed the instructions to the letter but it seems that it will not install the root66 file!
[Verizon Samsung Galaxy S III] chamkilla:
how long does it take to flash

its keep showing me msg from 20 mins do i need to wait more or just unplug ?

<ID:0/006> 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/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

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

<ID:0/006> aboot.mbn

<ID:0/006> NAND Write Start!!
[Verizon Samsung Galaxy S III] h311sdr0id:
Did you try unplugging between flashes?
[Verizon Samsung Galaxy S III] elreydenj:
Ok, I am in need of some input. Here is my phone info before problem.

I was stock rom, with cwm touch recovery. I had added some inverted gapps, flashed google now, frozen bloat, and added the stock samsung boot animation. My custom binary was no and phone was samsung official. Everything was working fine for a few weeks with no changes.

My phone turned off two days ago while using gps and navigation. It would not boot into recovery or download mode unless on the charger even with a new battery that had a charge from Verizon. So, the battery is not the issue. I have tried everything. After leaving it on the charger for a day I can get it to boot, but for only a few minutes and it does not connect to wifi or mobile data. After it shuts off and I plug it back in it shows an empty battery with a circle in it and then the green battery comes up and shows about an 80% charge and always appears this way. Once again, as soon as I disconnect the charger it shuts off. Here are my problems with the suggested soft-brick fix posted above. After flashing the bootchain and reset, odin always gets stuck at setup connection when I try to flash the stock rom. If I unplug the phone and restart odin like specified above, then the phone shuts down and is out of download mode. I believe it says to not reboot your phone when restarting odin and plugging it back in but I have no choice as it shuts off as soon as I take it off the charger. Also, does it have to be root66 stock rom or can we use the stock rom from samsung updates for the i535? My phone appears to be stock and is not modified after flashing the stock rom in odin and looking at the status for the few minutes that it will stay booted so Verizon is sending me a phone and I will return this one. However, I would prefer to fix my own and gain some valuable knowledge at the same time and send their refurb right back to them. Sorry for the long post and thank you.

---------- Post added at 04:37 PM ---------- Previous post was at 04:17 PM ----------

I don't want this question to get lost in my long post. Does it have to be root66 stock rom , or can it be the official stock rom from samsung?
[Verizon Samsung Galaxy S III] h311sdr0id:
Hey brother

-

Make sure it is root66. I have tried flashing stocks and other ROMS and it never works. Now when you go to flash root66 after flashing the two bootchains, every once in awhile, it will get stuck. What I then do is (while still in Download Mode) I unplug the phone and pull the battery, turn off ODIN, re-install the USB drivers, startup the phone in Download Mode again, and start the process over again. I actually just ran into this problem today.

-

I USE THIS METHOD FOR LAST RESORTS:

Install the USB Drivers (or re-install them again)

Plugin your phone so that the computer completely finishes updating the drivers (Windows 7)

Start ODIN with the phone already plugged in

CHECK ONLY "F. Reset Time"

Flash the first bootchain

WAIT until you get a green "PASS"

Exit out of ODIN using the "X" in the right-hand corner of the window (don't press "Exit")

Now unplug your phone

Startup ODIN, plugin your phone

CHECK ONLY "F. Reset Time"

Flash the second bootchain

Wait until you get the green "PASS"

Exit out of ODIN using the "X" (not the "Exit" button)

Now unplug your phone

Startup ODIN again

Plugin your phone

CHECK ONLY "F. Reset Time, Auto Reboot and Nand Erase All"

Flash root66

Wait for the green "PASS" (if it gets stuck and doesn't start installing then redo it like I explained above)

Your phone should be stuck in the stock VZW boot animation

Pull the battery

Boot into stock recovery (volume up+menu+power)

You will get errors but that is normal

Do a full wipe/reset and then do a cache wipe

Reboot

-

Let me know what happens
[Verizon Samsung Galaxy S III] elreydenj:
Ok I may try again with root66 however there is one problem. If you reference lines 14, 15, 16 in your steps it says to go into odin mode and then plug in your phone. My phone will not do anything unless plugged into a usb port or charger. It is a brick on its own. Do you think it will work if when I have to unplug the phone as stated it shuts off and I must reboot into download mode to go to the next step? I must completely reboot into download mode while connected to usb if I unplug the phone. Also, does root66 trip the flash counter? I do not want a custom binary because if I do not get it to work I am sending the phone back tomorrow. a refurb has been mailed and I will get it tomorrow. Thank you for your time.
[Verizon Samsung Galaxy S III] h311sdr0id:
Try leaving it plugged in and skip those steps. At least that is what I would try. I am not sure if it will make it worse...
[Verizon Samsung Galaxy S III] elreydenj:
Do you know if root66 trips the flash counter? I don't believe it does but I was searching on xda and did not find confirmation.
[Verizon Samsung Galaxy S III] Hero:
No, root66 doesn't trip the flash counter.
[Verizon Samsung Galaxy S III] droidstyle:
no only custom firmware flashed in odin trips the counter...since the root file is injected into a stock package, aboot does not detect it.

---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------

^ninja'd lol
[Verizon Samsung Galaxy S III] mjmixer:
Just want to say, Thank You!

Oh and you could add me as a statistic, and that this method works great!
[Verizon Samsung Galaxy S III] robpet2:
This thread is a lifesaver !!!!

finally got odin to flash stock root tar.. was going crazy over here for a few minutes..

now i remember why i dont like flashing themes over roms, the last time i soft bricked a device was due to the same reason.... but this method is bringing it back to life..

----------------------

edit -

i didnt do the boot to recovery and wipe data etc, and i let it boot up, all my apps and data were just like it wasnt lost.. Stock Rooted, login and apps all working fine..
[Verizon Samsung Galaxy S III] Chrisace89:
I keep getting error

Please help I keep getting this error in odin when i try to install the second bootchain.
[Verizon Samsung Galaxy S III] NetApex:
Big Thanks!

I just acquired my S3, and like any good flash-a-holic, I had gotten everything setup, and done a nandroid before tinkering. Next step was to get Google Wallet running on it so I could redo my app that Google pulled (again). So I changed the build.prop and suddenly I am searching frantically for this page. I followed the steps up to flashing 666. As soon as that was done the phone rebooted and I let it go all the way up. It appears everything is now working correctly, no data loss, and it is a happy little S3. Thanks a ton!
[Verizon Samsung Galaxy S III] Hero:
Glad this worked for you and so many others :)

Sent from my Supercharged S3 w/ unlimited RAM
[Verizon Samsung Galaxy S III] Chrisace89:
Could you please help me, I keep getting an error message saying "MD5 has value is invalid" I get this error as soon as i click on the second bootchain. This happens whether the phone is plugged in or not. see attached picture
[Verizon Samsung Galaxy S III] Hero:
Looks like you had a bad download. Re-download the bootchain and try the process again. Do an md5 check on the file and make sure it's correct.
[Verizon Samsung Galaxy S III] sinman02:
Root 66

Does anyone have a copy of this? All the links I can find are dead and the torrents don't have any seeders... I'm stuck in a soft brick and the other rooted roms I've tried doesn't work. Please help! Thanks.
[Verizon Samsung Galaxy S III] fluxvalve:
Don't know about the dead links, but the torrent does have seeders. I've uploaded 79112.8 MB on this one, and noticed at least two downloaders earlier today who were downloading at a very fast rate.

Maybe you need to check your firewall settings to see why the torrent won't work?
[Verizon Samsung Galaxy S III] sinman02:
Yeah it seems my utorrent was outdated...Thanks for the tip!
[Verizon Samsung Galaxy S III] MaverickCoast:
Problem downloading

Trying to download Route66.tar file but freaking Just Cloud website keeps popping up. Tried three different PCs. Tried copy and pasting.

Any suggestions? Is there another link?

Signed MAD AS HELL!!!! :mad::mad::mad::mad::mad::mad::mad:
[Verizon Samsung Galaxy S III] h311sdr0id:
-

Use Google. There are other links to it.

-

If you find that they are also down, use

this

one. BUT ONLY if you do not have any other choice. This is a personal backup of root66.

-

Download ROOT66 (h311sdr0id's Backup Link):---------->

HERE

-

Or copy/paste this: https://docs.google.com/open?id=0B5XTHyH8X0KdUzMxMlZsVFJ5YTA

-

MD5: BE4350A56E739EAF7A4184352D653A7B

-

Make sure to check it using an MD5 app (MD5 Checker http://getmd5checker.com/)

-

-

I take NO responsibility for anyone downloading this from my storage.

-
[Verizon Samsung Galaxy S III] droidstyle:
try the link in section 6 of my guide under rooted stock vralf2.
[Verizon Samsung Galaxy S III] vladimirtm:
i was flashing the chain and i get a message system software not authorize,how i fix this please help!

---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------

i was trying to flash the chain and after i flash the first one and erro message show up saying unauthorized software in your phone go to the nearest verizon store, i cant put it in downloading mode or anything please help
[Verizon Samsung Galaxy S III] droidstyle:
pull and reinsert battery then try putting it in download mode.
[Verizon Samsung Galaxy S III] fantasyrulz:
my problem is it will be stuck at NAND write start forever...

for both ralec and ralF
[Verizon Samsung Galaxy S III] fantasyrulz:
i tried both the RALEC and RALF2

both seems to push the data...

my phone displayed it full bar.

but in odin it did not show anything rather then nand write forever

pushing in asia singapore STARHUB rom seems to be fine with PASS

but still stuck at booting screen meaning both my RALF2 and RALEC did not went through.

can u point to me how come i did not push in the data ?

---------- Post added at 01:09 PM ---------- Previous post was at 12:58 PM ----------

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

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

<ID:0/006> sbl1.mbn

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

this is my error
[Verizon Samsung Galaxy S III] fantasyrulz:
spend whole day doing and no luck

wakeup today load a new official rom from UK and went into the last proccess.

i now understand WHY it did not work...

because im not using the correct rom. because ur method is designed for the euro side uk etc

and im using a asia singapore rom. that is not valid ?

my first 2 bootloader did not get PASS notification but i use the method u said to plus and put the second loader.. apparantly thats the cure....
[Verizon Samsung Galaxy S III] Hymizzle:
Trying to restore back to stock coming from synergy ROM.

Didn't lock the boot loader was I supposed to?

I'm stuck in Odin forever, see attachment. I had to unplug and try again.

I have the stock file and bootchain tar files. Still stuck.
[Verizon Samsung Galaxy S III] Hero:
You shouldn't have to do this to get your phone back to stock if it was already working in the first place. If you want to go back to rooted barebones stock from Synergy (not softbricked) just flash the root66 in Odin and boot into recovery after to factory reset. No need to use the bootchains. Also, no, you dont need to lock the bootloader and by your picture it looks like the system partition was writing correctly and wasn't stuck. How long were you stuck at the /system write?
[Verizon Samsung Galaxy S III] Hymizzle:
Was stuck 30 minutes. Bootchain was just another option to attempt to get Odin to restore by following the guide if phone is soft bricked.

Another attempt with stock tar file but it's been taking over 45 minutes and restoring is only 15% complete.

Been flashing/restoring phone for years, don't know why this isn't a simple restore as I've done it before.

Restoring phone to sell it. Already have another S3.
[Verizon Samsung Galaxy S III] ccogan:
I just wanted to say thanks for this guide it was a lifesaver yesterday as I thought I was going to have a $700 paperweight. Followed the guide and it work great.
[Verizon Samsung Galaxy S III] rpxz:
I tried the method that the OP posted. I'm at the point where the phone reboots and looks like its loading but it doesn't.

I pulled the battery out. Booted to recovery mode. Blue texts comes up saying booting recovery and it restarts and never boots into recovery.

I tried to go back into download mode as well to start this entire process over. I press the power up button to confirm download mode and it just restarts.

So am I stuck with no phone now? All this stuff started last night flashing the cm10 nightly.

Someone please help me, Id really appreciate it.

EDIT: Nvm I got it. Disregard.
[Verizon Samsung Galaxy S III] krazie805:
Ive been stuck for 30-1hr also have had no luck so far any help would be appreciated
[Verizon Samsung Galaxy S III] erikclaw:
I was running jbbuild2 then accidentally flashed a kernel that didn't go good. Got the soft brick gone, reloaded this rom, gapps and kt747 kernel. Last three times I get stuck at bootanamation and never gets out of it. Tried with another kernel too but same result. Any ideas? Getting this thing out of soft brick is getting old
[Verizon Samsung Galaxy S III] Hero:
What error are you running into?

Hmm? I think you might have posted this in the wrong section. This isn't a ROM. It's just a method of getting out of soft brick.
[Verizon Samsung Galaxy S III] mark-in-dallas:
I am also getting an MD5 hash value is invalid message when tryng to load the second Bootloader. I reset and exited Oden, unplugged the phone, started Oden back up and plugged the phone back in between the first Bootloader and the second.

I also tried running the route66 tar after the first Bootloader since the second did not wotk, but the route66 tar fails.

Any help would be gretly appreciated.
[Verizon Samsung Galaxy S III] erikclaw:
I know that, just thought someone might have an idea what it could be.
[Verizon Samsung Galaxy S III] Hero:
Re-download the bootchain that's giving you the md5 error.
[Verizon Samsung Galaxy S III] mad96:
Thanks man your guide saved my butt cause Odin reflashing w/o your 2 files wasn't working, tho now when I plug my phone Into my laptop it says device ID unknown even tho the drivers installed. Not a big thing but still thought I'd mention.

M.yA.nD.droidS3
[Verizon Samsung Galaxy S III] mark-in-dallas:
I actually found the problem, from somebody else experiencing the same issue who posted in another thread. It's the filename itself causing the MD5 mismatch. After I changed the filname I was able to run everything and get my phone back. :)

The file downloads as:

BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5

But for the MD5 check to pass it needs to be changed to:

BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar.md5

Thanks for posting the unbricking method though, as you saved me time, hassle and probably $600! Donation made!