yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] chocolate8175:
I think you guys might be making this more complicated than it really needs to be, here's my advice... Go to the stickies section of the android development section, find the thread by the same op of this thread (it's titled jellybean factory image I think), download the factory image. Flash the jellybean factory image in odin, then flash the VRALEC bootchain from the OP of this thread in odin. After that flash the recovery of your choice from the OP of this thread in odin, be sure to uncheck the auto-reboot box in odin before flashing your recovery. VERY IMPORTANT!!! Wait for odin to show pass on the recovery flash then pull the battery, replace battery and hold volume down and home. Press and hold power in addition to the other keys and wait for the first vibration, as soon you feel it release the power button but keep holding the volume up and home buttons until you see the recovery you selected. Flash the root and bootloader zip from the OP of this thread in recovery, flash the VRLBLK3 bootchain from the OP of this thread in odin. That should do it, worked for me. Enjoy, hope that helps somebody if not you guys

---------- Post added at 05:59 AM ---------- Previous post was at 05:33 AM ----------

Here's the rooted jellybean image that was referenced a couple posts back if anyone was looking for it, looks like it might be a good method too. I can't vouch for it however

http://xdaforums.com/showthread.php?p=33948598
[Verizon Samsung Galaxy S III] SteveGrandRapids:
. . the problems people are having getting custom recovery to stick reminded me of a similar problem with the Sprint Samsung Moment with Android 2.* . . . the stock ROM ALWAYS overwrote the custom recovery file by default . . . did some research and found that the same thing is happening again with the Galaxy S3 LTE JB and wondering if this is what is happening with Galaxy S3 JB Verizon . . . Team Epic developed a root.zip file to flash after installing CWM prior to booting up system for the first time . . . from Team Epic's site:

"WARNING: Do not boot into Samsung's ROM without first applying our Root .zip. Samsung's OTA updates install /system/etc/install-recovery.sh and /system/recovery-from-boot.p, which cause Samsung's ROM to replace the recovery image you had just flashed with the stock recovery. Our Root .zip removes these files, thus preserving your custom recovery. "

maybe this is what is needed for Verizon's OTA JB?

Team Epic's CWM Recovery Install

. . . here is their root.zip file that can be analyzed:

View attachment 1578527
[Verizon Samsung Galaxy S III] GrainOsand:
Sorry, I didn't have the time to try the rooted odin file yet. I will try again after work today. Ill keep you guys updated.

I have tried every other method I can think of. Including trying to flash back to an older stock odin and starting all over.

This is probably my last option.

---------- Post added at 10:23 AM ---------- Previous post was at 10:19 AM ----------

Team Epic developed a root.zip file to flash after installing CWM prior to booting up system for the first time . . . from Team Epic's

The locked boatloader prevents us from flashing CWM. We need to root 1st and then unlock the bootloader. To get a custom recovery. ....
[Verizon Samsung Galaxy S III] TokedUp:
I see what I was doing wrong. I was letting the flash of the recovery go until it said pass. I was pulling the plug during the Rest phase. All is well. Thanks u guys.
[Verizon Samsung Galaxy S III] peeyourownpants:
Any idea on how to wipe the Odin flash counter? Or if it's important to do before sending back to Verizon for warranty replacements?
[Verizon Samsung Galaxy S III] SteveGrandRapids:
. . . only need to reset Flash Counter if returning to Verizon . . there is an app "Triangle Away" (requires root and is not free) available from Play Store that resets counter . . . :good:
[Verizon Samsung Galaxy S III] GrainOsand:
I was doing same. I will try again tonight. .
[Verizon Samsung Galaxy S III] peeyourownpants:
Yeah. I did this a few times. Good thing it's robust.
[Verizon Samsung Galaxy S III] TokedUp:
It will work for u Grain. I had to let it sit there for a couple mins before it finished flashing CWM.
[Verizon Samsung Galaxy S III] GrainOsand:
I am very impatient! After about 10sec I would pull USB thinking it was done. Thanks for the heads up.
[Verizon Samsung Galaxy S III] Gervin:
Tried and worked.

Awesomeness.... tried it, and worked flawlessly.

THANKS!!!!!!!!

:D
[Verizon Samsung Galaxy S III] AngryGibson:
So the issue might've just been us not giving it enough time to rest after flashing CWM? Lol. I will try this again later today. If I can't get it, ill just say roll back to ICS and reroot.
[Verizon Samsung Galaxy S III] billyr14:
I have done steps 1, 2 & 3 without issues, but when attempting to flash from SD Card in Step 4, I get an abort message. Have tried 3 times to no avail!

Reviewed video and it appears that I have followed the instructions. My recovery screen does not look like the video.

Also, I chose the recommended bootloader.

Has this happened to anyone and is there a solution?

Thanks
[Verizon Samsung Galaxy S III] AngryGibson:
Yeah, my issue was not waiting long enough to let the CWM finish. When it displayed "rest", I thought I could disconnect the USB and do the battery pull. One last question, the last step is not needed correct? What exactly is "return your original partitions"?

BTW, I'm now rooted. Thank you to all of those that helped figure my issue. I feel pretty dumb now..
[Verizon Samsung Galaxy S III] GrainOsand:
LOL, Don't feel dumb! I have used ODIN on my Fascinate, Droid charge and my gs2 when I had a t-mobile line and I still couldn't figure it out. Especially with Verizon's track record of sneaky behavior. It wouldn't surprise me if they pulled some ish like locking down the CLN devices before shipping them out. ...:what:
[Verizon Samsung Galaxy S III] Q0596:
Doing something wrong...

So I got to the part where I needed to flash the bootloader and rooting the device and I am getting an error message - I think I might be doing something wrong, hopefully someone can clarify for me.

Error message is:

"failed to verify whole-file signature"

"signature verification failed"

I tried the Root/Unlocked Bootloader combo. Any thoughts?

Thanks!
[Verizon Samsung Galaxy S III] bionik9:
I followed the instructions down to the part where I install a custom recovery. I tried CWM since I am most familiar with that, but the MD5 didn't check out after downloading 2 different instances of it. So I ventured out with TWRP. Flash was successful through Odin, but I can't get into recovery mode. It says on my screen that I am entering recovery mode, but then shows a Samsung splash screen with a lock on it and says "Custom". Can anyone help me out here?
[Verizon Samsung Galaxy S III] ct_tec313:
i had encountered the same problem as you tried all night to get recovery to stick, no dice so i had to change the game up, found the stock rooted odin version of the jelly bean ota flashed via odin, went into the play store and grabbed terminal emulator app and did this....

Optional, Recovery (may now trip counter):

Loading any custom recovery or custom kernel may now trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:

The instructions here are for TWRP but you can follow same procedure for CWM as well.

Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.

Connect your phone to your computer and use adb

type adb shell

once in the shell run su

then

dd if=/sdcard/openrecovery-twrp-2.3.1.0-d2vzw.img of=/dev/block/mmcblk0p18

Alternate if unfamiliar with adb commands

Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.

after i got recovery flashed i used the unlock bootloader zip then....boom profit...you can also go to cwm mod website and get the latest cwm touch and do the same thing just make sure put the image on the root of your sd card hope this helps.......heres the thread to find the factory rooted image

http://xdaforums.com/showthread.php?t=1762709
[Verizon Samsung Galaxy S III] edthesped:
I can vouch for this version, I used it for the last couple of leaks and it works like a charm in fact it's the only current method I'd use.
[Verizon Samsung Galaxy S III] BigErnM:
+1 I think it is the easiest and best method by far. I used it to flash the J1, K1 and K3 leaks with no problems at all. It fixed the problems I had when I originally used the other method to flash the J1 leak.
[Verizon Samsung Galaxy S III] Matthewbe:
Do I still get to keep everything on my device?
[Verizon Samsung Galaxy S III] ct_tec313:
yeah its the best method for those who can get it to work, i couldn't get recovery to stick so i had to try an alternate method to get the same results and that worked for me, and it might for some one else...you know there is more than one way to skin a cat:good:
[Verizon Samsung Galaxy S III] macdroid01:
rooting S iii with 4.0 was great it was one click, just open Noxius Ninja's app in Windows and it worked.

Will there be something like that, that is idiot-proof for nervous people like me?

If not... or people here do not think it will happen due to technical reasons, I guess I'll take the plunge and do this "recovery" stuff. It doesn't sound too bad, but I figured I'd wait a week or two and see if someone came up with a "one click" method first before I tried this method..

Thanks everyone..!!
[Verizon Samsung Galaxy S III] The Apostle:
When you put the Unlock Bootloader on your SD card where does it needs to be? And does it go on SD Card or External SD?
[Verizon Samsung Galaxy S III] droidstyle:
finally some folks that understand...since its been confirmed that the K3 leak is the same as official, there is absolutely no reason to flash all these files. MrRobinson made it extremely easy for us to root.

-download the Root66_VRBLK3 image http://xdaforums.com/showthread.php?p=33948598(I recommend the full wipe version)

-connect device to pc via oem usb cord, open odin and place the image in the PDA slot of Odin and hit start

-should take around 8min...upon completion the device should reboot

-once fully booted into android, open up playstore, download ez recovery and flash recovery of choice thru app.

Congrats you are now rooted and have obtained a custom recovery on 4.1.1 jelly bean. I don't know how it can get much easier then that. Also this was the very first method we had to get root on the gs3 and gn2...I see much less issues posted using it. Not trying to troll this thread but seriously there are too many folks having issues.
[Verizon Samsung Galaxy S III] GrainOsand:
Never mind I misread.
[Verizon Samsung Galaxy S III] arockj:
Thank you. I just got my phone on Wednesday. Rooted it today. :)
[Verizon Samsung Galaxy S III] XNO:
Big thanks bud.
[Verizon Samsung Galaxy S III] ct_tec313:
basically followed the same steps as what droid style did but just used terminal emulator too obtain custom recovery then flashed the unlock bootloader zip,but now that i know that you can use ez recovery too flash cusom recovery no need for termainal emeulator but its still good too know how to use.....
[Verizon Samsung Galaxy S III] AngryGibson:
Yeah. This was my first time using the ODIN program. The last time I rooted my phone, it was pretty much a one click method so I wanted to be extra careful this time.

What does "return to original partitions" mean for the very last step?
[Verizon Samsung Galaxy S III] imtoomuch:
I just rooted using this method and suddenly my WiFi is insanely slow. It's unusable at this point. Any ideas?

I can't access the Verizon service menus via the keypad anymore. Does rooting get rid of those?

Lastly, what is the safe way to return to completely stock with the flash counter reset to 0?
[Verizon Samsung Galaxy S III] jaben2:
Just used this method. It worked perfectly.

I was previously rooted, and unlocked had to restore due to possible warranty and signal problems.

Ran it stock for a few days, and nothing changed other than updating my PRL.

So back to Executioner 2.5

Thanks again.
[Verizon Samsung Galaxy S III] BoLTroid:
This is a great method and I want to root mine, but anyone know how to do it NOT using a PC (I only have Mac computers) or without a computer device at all?
[Verizon Samsung Galaxy S III] Rword69:
Rooted! Thanks for the great write up! :D :good:
[Verizon Samsung Galaxy S III] 2fasteddie:
Took the OTA a week ago but didn't need/want root until today. This method took all of 5 minutes to complete, thanks!
[Verizon Samsung Galaxy S III] DrkGhst87:
hmm this didn't prompt for me:

•Upon exiting your custom recovery to reboot first time, you will be asked if you want to "Disable recovery flash", you MUST select Yes

the phone just rebooted... Chose TWRP as the recovery and after reboot turned off to flash the original bootchain in odin. Then after final reboot checked root and everything was okay along with being able to go back into TWRP recovery. Just wondering if I'm still okay?
[Verizon Samsung Galaxy S III] open1your1eyes0:
OP has been updated with new version of custom recoveries.

ClockworkMod Touch Recovery 6.0.2.3 and TWRP Recovery 2.3.3.0
[Verizon Samsung Galaxy S III] Mikestony:
If I just followed this guide before the updated recovery that was posted, and want to just update my recovery, I assume I can just follow step 3 correct?
[Verizon Samsung Galaxy S III] BigErnM:
You could do that, but since you are now rooted, it is probably much easier to flash the recovery of your choice either using the goomanager app for TWRP or ROM Manager for the latest CWM. Flashing in Odin may be the easiest way if you need the Clockwork Mod Touch Recovery though, since ROM manager tries to get you to pay for it and EZ-Recovery has outdated versions, although I think you can manually download the Touch Recovery to flash with EZ-Recovery. Every time you flash in Odin is a little more chance of something going wrong and keeps increasing your flash counter. Not that that matters or can't be easily reset.
[Verizon Samsung Galaxy S III] jdk2:
Thanks for the update and the hand holding through the process. It's much appreciated :)
[Verizon Samsung Galaxy S III] Mikestony:
Thanks! So currently I am on CWM. I want to update to the newest CWM--use Rom Manager.

If I want to switch to TWRP, use Goo Manager--correct?
[Verizon Samsung Galaxy S III] BigErnM:
Correct. Here is the post that tells how to use EZ-Recovery to flash CWM Touch: http://xdaforums.com/showthread.php?t=1955582. I prefer the non-touch version myself, but everybody has different preferences. ROM Manager will flash the non-touch CWM 6.0.2.3. It will try to get you to buy the app to flash CWM touch, but don't waste your money when you can do it for free.
[Verizon Samsung Galaxy S III] Droid2drummer:
Yes it does. And did for me several times. Ota rootkeeper. If you are on ics and still havent updated save yourself some time and get this app.
[Verizon Samsung Galaxy S III] putney1477:
Do I have to extract the.tar files for twrp recovery and the bootchain before flashing with ODIN?
[Verizon Samsung Galaxy S III] jaguarpaw:
followed the directions.. had some prob w/ the sum of the md5 on the first file to flash but after a few downloads got it to load.... rooted unlocked and cwm is good to go... Thank you so much for this helpful post...

i have one question. regarding cwm the nandroids back up and the file name is a date that doesnt make sense ... is that normal. how can i know which is the latest backup.. is there a way to rename them.? i like cwm but this has always been an issue... thanks again!!!
[Verizon Samsung Galaxy S III] BigErnM:
You don't need to extract them, just flash them as they are.
[Verizon Samsung Galaxy S III] imtoomuch:
Bump. Any ideas?
[Verizon Samsung Galaxy S III] peeyourownpants:
Yeah. This happened to me too. If you're worried, try going through goo manager to install twrp once you've booted back up, but I haven't had any issues and I didn't get that option before the reboot either.

---------- Post added at 02:07 AM ---------- Previous post was at 01:51 AM ----------

Just about restoring to send it back to Verizon. Haven't heard about the other issues.

http://xdaforums.com/showthread.php?t=1867253

[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)

The flash count wiper from chainfire works well.
[Verizon Samsung Galaxy S III] badge 214:
Using TWRP I could not get this to come up..

Upon exiting your custom recovery to reboot first time, you will be asked if you want to "Disable recovery flash", you MUST select Yes

It just let me exit every time. Should I use the other recovery??

Also is there a rooted rom out there that has everything original like the stock rom? Alarms and all? I want to root again, But I like the stock rom and would like to stay with it..

---------- Post added at 07:05 PM ---------- Previous post was at 06:40 PM ----------

just read the last page of posts sorry about the first question, but I still have that second question...
[Verizon Samsung Galaxy S III] joebob2000:
Did you already have a recovery from rooting an earlier stock rom? I noticed that CW recovery didnt ask me this as well, but it didn't matter as everything went fine anyway. I was rooted under ICS and unrooted to let the OTA update run, and followed these steps to re-root. Everything went great. There are a bunch of stock roms if you are interested in a near-stock experience but want it pre-rooted, just look around for one you are comfortable with. The only downside is you have to wipe everything when you do the switch.
[Verizon Samsung Galaxy S III] ndtinker:
This may not be news to some but it made all the difference to me: Odin doesn't like 64-bit os'. It will get stuck on the "Get PIT for mapping" part. It ran fine on my Win8 32-bit but not Win7x64.

Otherwise though the guide worked great!

BTW I used the CWM recovery and had to do the "hold up and home on reboot" dealio to get it to get into CWM after it rebooted. And KEEP holding up and home till it gets in there. If you let go, it'll reboot like normal.
[Verizon Samsung Galaxy S III] ratledge:
This method works with VRBLK3 (Jelly Bean) firmware on CLN phones!

Interesting: I've never had a single problem with Odin 3.07 under Windows7 64-bit with any of my 5 VZW GS3s - works just fine for me. YMMV, obviously...

I *can* confirm that this method also works perfectly with a refurb ("CLN") phone from Asurion (or I have to assume VZW) with VRBLK3 Jelly Bean already on it when it arrives! :good:

Rocking with my 5th VZW GS3 at this point, one hard bricked device out of 4, 2 of 4 with power or volume rockers that fell off - not bad. Fortunately with the Otterbox "Commuter" series case on it, all those buttons are captive and can't escape even if they do come off, and apparently something about the way it keeps them covered seems to ameliorate the problem with the buttons tending to jump off in your hand (actually, my 3rd CLN phone arrived with the power button in the bottom of the box and the volume rocker popped loose before I could even get it activated! We'd have to say "poor quality control" especially since Sammy is known for good build quality. This 5th one looks like the buttons protrude just a little less than the previous ones I've fondled... :silly:
[Verizon Samsung Galaxy S III] badge 214:
When I rooted I checked out a few roms on Goomanager, But did not like them much.

I have not found a rom that will give me the stock samsung experience. I unrooted and am back at factory jellybean. I root and unroot my nexus 7 all day, but the new phones make me kind of leery :(

After I Unrooted I was reading about people loosing stuff and getting stuck in roam. I guess that's why I have not jumped back in again yet.:rolleyes:
[Verizon Samsung Galaxy S III] thejron:
I did not get the Disable recovery flash message. Ive sinced rebooted into recovery twice and its currently making a backup just fine.

Should I just let it go? Or will this haunt me down the road?

---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------

Beantown rom man.
[Verizon Samsung Galaxy S III] badge 214:
I tried Beantown...It was So So...I quess I'm going to jump back in today and see how it goes. I'm going to try clean rom..:eek:
[Verizon Samsung Galaxy S III] dems86:
Jelly beans 7 and galaxy mod rls12 are both solid. Those are the touchwiz roms I run when I'm not on aosp/aokp. I definitely recommend either of them fast reliable, hassle free daily drivers with stock++ look and feel.
[Verizon Samsung Galaxy S III] AngryGibson:
Although I am rooted with the previous custom recovery, do I need to reflash it just to be current or does it not matter?

***This is an open question to anyone. Thank you.
[Verizon Samsung Galaxy S III] SteveGrandRapids:
. . . the latest version fixes a charging issue . . . :good:
[HTC One X] lummujaj:
greetings guys. sorry for disturbing you all with my post ! ive a screen problem , sometimes it goes black but my phone is still working and the touch is working too maybe !

ive searched a lot and i know someother had the same problem but i never was able to find is there exist a solution

so can anyone around help me
[HTC One X] ShyamSasi:
We may need some more information.

Custom ROM or Stock ROM?

Rooted & Unlocked?

Is it ICS or JB?
[Asus Transformer TF700] Hazmatyre:
I accidentally formatted data under TWRP and now the internal memory won't accept files larger than 4gb.

How do I format the internal memory to another filesystem?
[Asus Transformer TF700] _that:
I would not expect that Android works at all with /data on a FAT32 partition - are you sure that it's not ext4? The problem could also be somewhere else. Please post the output of "mount|grep /data" (e.g invoked using adb shell).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LAKsupply:
Having issues with a 32g SD card. The 8 and 16g cards work fine but certain files won't move to the 32g and the camera won't recognize it. Running Task's AOKP ROM and KT 747 kernel, but had this same problem on different ROMs. Any thoughts? I really need a 32g card in this thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JWC59382:
You have formatted the card in settings right? Under Storage?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LAKsupply:
I formatted and mounted in recovery. Nothing. I went back and got a new card and reformatted/mounted, and it works for the camera storage and I can move individual files over there. Folders are still a no go though... for some reason I can't create new folders on the sd card or move existing folders. I can move the individual files, but then can't create a folder for them even after the fact.
[General Questions and Answers] SXUsr:
You need to sort that out then, connect your Phone normally and uninstall it in Device Manager on the PC. When you've cleaned your PC Reconnect your Phone in flashmode and let the drivers install before moving on to the next step.
[General Questions and Answers] gilang1kb:
Problem solved. Tried flashing my phone using Windows 7 and everything ran well (as long as I followed the instructions provided). The problem was with my Windows XP, I don't know why (my Windows XP OS is a (highly) customized one and I can't figure out why it wouldn't work for flashing my Xperia Tipo Dual). The Flashboot's language interface also displayed well when I installed it on Windows 7. Thanks a lot anyway for the response. :good: