yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] nosympathy:
Only thing I can think of, is beans roms are currently based on a deodexed verison of this rom. This rom for whatever reason is all kinds of jacked up that way. it doesn't deodex correctly among other things. If you compare the file structure too, it isn't even remotely the same. I don't know what the heck this rom is haha. I wonder since my rom is based off the stock samsung image, if that is why it works correctly.

Edit: Point of that was that messing with this rom, maybe broke some of those settings, or the apps in general? have no idea and since I have already decided this is great for getting initial root and recovery, and that is about it, I don't have a need to look into it.
[Verizon Samsung Galaxy S III] open1your1eyes0:
nosympathy, please note that many users have confirmed that this ROM acts exactly as stock and has resolved all issues of the original root room from the first thread. Not sure why you are having issues with it but a factory reset should clear things up as has been the case for many users so far.
[Verizon Samsung Galaxy S III] pjamv5:
Right, but like I said, that only changes the background of an open email, not the whole inbox list...at least for me.

Understand what you're saying. It's kind of minor for me in the grand scheme of things, and I sure don't feel like odin'ing back to stock to double-check. :) I'm liking your rom just fine.
[Verizon Samsung Galaxy S III] mb27:
Maybe you could extract the email app from the factory ROM (I think it's SecEmail.apk?) and replace the one you currently have in /system/app/ ?
[Verizon Samsung Galaxy S III] nosympathy:
I understand what you want to think.

This rom flashed by itself, untouched, may act as stock. Once you try and modify the rom, you find it is not the stock image from verizon/samsung. I have a PM from beanstown where he noticed the samething.

I am not trying to slam this rom, I am just pointing out that my rom is 100% stock verizon/samsung image. This however is not that. It is something different.

This rom does not deodexe correctly. I was attempting theming this rom and found all kinds of issues. My stock deodexed rom does not have these issues.

Therefor, something with this rom is not right.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Maybe it has something to do with the way it was repacked? I think mrRobinson used a different process to recreate it. Link here for details

So it's possible the way you are unpacking it is just not compatible for deodexing purposes. I have been running this rom since the day it was posted and do not notice a single difference from stock. No issues, nothing even to remotely tell that it is different from stock (other than obviously including Superuser and su). If there is something hidden in the changes I can definitely say it has no effect as you can obviously tell by all the people that mentioned it. Are you sure you tested that on mrRobinson's rom and not the one from this thread? That is the one that has been confirmed to be different from stock by multiple users already. Please make sure you are not confusing the two since most people see that thread before this one.
[Verizon Samsung Galaxy S III] nosympathy:
Possibly. It is just weird how so very different it is from the stock image.

Like I said, I don't see this being a problem for someone wanting a completely stock image on their rom. It will just be someone who wants to customize their rom, etc. that will possibly have issues.

Plus I think some people like having a completely stock image that they can flash through CWM/TWRP and not odin.
[Verizon Samsung Galaxy S III] open1your1eyes0:
I agree. This thread was never originally intended to be a separate rom actually. If you look at the original request you'll see the main reason for it was basically to just be a proper remake of the stock rom with just superuser/su added, since so many people were complaining about the original root rom.
[Verizon Samsung Galaxy S III] lowg:
I posted in nosympathy's thread but wanted to ask you guys also. Earlier in this thread I asked mrrobinson what he used as base image, and he also used the same base image as invisiblek did (stock image in sticky, from samsung-updates), with the same methodology (take stock image, add the su binaries and repackage).

If this is the case, the system images should be identical. Has anyone done a diff of the different "stock root" images? I think this would explain things. It could even be that the base image from Samsung-Updates is not the same as what is actually on device which is why differnt uses are seeing strange behavoir/differences from the software that originally came on the device.

Ideal situation would be if someone finds an exploit on the current version of stock OS so we can obtain root without flashing an entire image via ODIN then do a proper comparison/system image...
[Verizon Samsung Galaxy S III] s197:
Seems like wasted effort to me. The root66 image seems to be working fine for just about everyone, myself included. I never flashed Invis' image but according to many this one fixes the main issues (swype, messaging, predictive text, etc.). With new ROMs, including AOSP, starting to roll out, I see no need to have a perfect identical match to a stock ROM. I'd rather see development steer towards kernels and JB, as it appears to be.
[Verizon Samsung Galaxy S III] mad96:
I don't want to be a complete moron but the root 66 image that downloads won't allow me to extract anything. It wants to install vuse on my computer then won't allow anything else, is it a simple matter of renaming the extension or how? Any help would be great as Odin is new to me but android is not, thanks.

M.yA.nD.droidS3
[Verizon Samsung Galaxy S III] lowg:
If you care only about custom ROMs that others are creating for you then any of these rooted roms will do to get you started. You get root, can flash your custom recovery and then go to town. No need to worry about any of the supposed issues or differences with stock image.

If you just care about root on a stock rom and/or want the best base for creating custom roms based off the original kernel and system it is ideal. What is the cleanest method of achieving this, essentially overwriting everything on the device with hopefully the same files/versions, or simply copying two files with the proper permissions?
[Verizon Samsung Galaxy S III] GTvert90:
stupid question but is this suppose to be flashed under phone or pda like the previous method?
[Verizon Samsung Galaxy S III] pjamv5:
You'll need to flash this with custom recovery, either CWM or TWRP.
[Verizon Samsung Galaxy S III] GTvert90:
its suppose to be flashed in odin.. Just don't know what under as the original root method flash was under pda for what ever reason.
[Verizon Samsung Galaxy S III] pjamv5:
My mistake, I'm getting my threads mixed up here. For the root66 tar, just flash it in Odin with the defaults checked and PDA selected. Quoting another Odin-related thread, "PDA, PDA, always PDA!!!"
[Verizon Samsung Galaxy S III] GTvert90:
Beautiful.. thanks.
[Verizon Samsung Galaxy S III] odmejia:
Has anyone had any luck getting there wireless thethering to work? When I start it up it starts with log errors, its failing to create the ad-hoc mode. Anyone successfully tethering? Thanks in advance.
[Verizon Samsung Galaxy S III] pjamv5:
Try FoxFi. I have no issues with it at all.
[Verizon Samsung Galaxy S III] s197:
If you just care about root, I think root66 is fine. I've been running it for 2 weeks now and have not encountered a single error.

If you want to theme and all of that, nosympathy's ROM would be a good base because it's deodexed. His ROM would also be fine if you only want root, it is very close to stock with only the Bravia engine added. I haven't personally tried his ROM since I'm basically waiting for stable AOSP JB, however, it looks like a good base. From there you can debloat and theme to your preference/experience.
[Verizon Samsung Galaxy S III] mrRobinson:
I'm on tapatalk and not going to quote his entire post but to the guy with the batt drain issue put the boot ani back and retest. Sounds weird but trust me.
[Verizon Samsung Galaxy S III] themusicmonkey:
Change device type to CDMA Nexus, and it will work. It will then do WiFi tethering in both ad-hoc and infrastructure mode.
[Verizon Samsung Galaxy S III] mb27:
Hmm. I'll give that a try after my first hour is up from uninstalling the previously mentioned apps.

Ok, I lost 9% in one hour on idle. Boot animation has been restored. If it doesn't drain now.. that's a major WTF for me.
[Verizon Samsung Galaxy S III] Noxious Ninja:
Has anybody tried the debugfs root method yet? I don't really understand the exploit behind it, so I'm not sure if it's likely to have been fixed or not.

Looks like the system partition on the GS3 is mmcblk0p14.

If nobody beats me to it, I'll try tomorrow when I'm back home at my PC.
[Verizon Samsung Galaxy S III] aigochamaloh:
I'm using it just fine. You need to change the setup mode to generic ICS.
[Verizon Samsung Galaxy S III] primetime34:
My only issue has been with LTE. I have had to put my phone in airplane mode and then out of airplane mode at least once a day to get LTE connected again. Otherwise, it only connected at 3g. I have seen that a couple of others have had this issue. Is it widespread with root66? Or is it a device flaw and I should get my warrantied? Thanks.
[Verizon Samsung Galaxy S III] mrRobinson:
i'd just wait for the lg1 update.
[Verizon Samsung Galaxy S III] DROID3R:
im comfused. i dont see nay tar file in the rom thsi rom. i download a rar file then inside is another rar file and inside the second rar file are a bin file an img file and a few others. which file is it i put in odin to flash?

edit: never mind my computer sees the tar file as a rar file for some reason.
[Verizon Samsung Galaxy S III] sfin54:
I received a replacement S3 with the new baseband, and it did not fix the 4G, or reception issues.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Am i supposed to activate the phone first before rooting? or can i root and then activate?
[Verizon Samsung Galaxy S III] pjamv5:
I would definitely recommend activating prior to rooting. There seemed to be some people that had issues when they rooted first.
[Verizon Samsung Galaxy S III] mb27:
Ok. Major WTF after all.

I restored the boot animation and I've lost 7% in 3 hours, compared to 9% in one hour without the boot animation.

For anyone that has been following along, 7% in 3 hours sounds worse than what I was getting (1% every 2 hours on idle) BUT this time I did use my phone a bit so it wasn't completely at idle like before. But still, if I was having the problem I would be at 70% or lower battery after 3 hours no matter what I was doing.

So.... what makes the boot animation so important?! :confused:
[Verizon Samsung Galaxy S III] pjamv5:
Out of curiosity how did you restore the original boot animation? System restore or something more basic?
[Verizon Samsung Galaxy S III] mb27:
I had saved a copy of it on my PC before so I just moved a copy of it back to system/media
[Verizon Samsung Galaxy S III] mad96:
Have you tried using cpu spy in the playstore. Helped me track a few apps. Also I noticed after diabling Verizon bloat using the os not TB and I had crazy things like CPU locked at 1gig. And after I reenabled the Verizon bloat all was normal.

M.yA.nD.droidS3
[Verizon Samsung Galaxy S III] mrRobinson:
apparently the stock boot.img makes it important. you can change it just don't remove it.

Source: http://xdaforums.com/showpost.php?p=28484760&postcount=445
[Verizon Samsung Galaxy S III] guyd:
I've never removed or changed the boot animation, but I have had random high battery drains!

I still believe that it's either a rouge buggy app, or a Sumsung rouge bug.
[Verizon Samsung Galaxy S III] slvfox:
I'm having some weird issues. I was running this ROM for about three days with no issues. Yesterday I tried flashing the new CM10 after changing recoveries per the OP. I wiped data then flashed but always got stuck on the splash screen.

Pulled battery but same results. Wiped data then odined back to stock then odin this ROM with no issues. But now when I reboot, I still get stuck in the splash screen. I let it set for over five min's but it will not get any further. Any suggestions?
[Verizon Samsung Galaxy S III] mb27:
That's really interesting. I wonder what would happen if I replaced the boot animation file with a blank file called bootsamsung.qmg that way it looks like the file is there, but it's just not the animation.

I wish I could help you out but everything has been working great for me again now that I restored the factory boot animation.

Yes I tried but it never found anything abnormal.
[Verizon Samsung Galaxy S III] sage3:
I am about to root with root66 and was just wondering which recovery is working the best. I have read that some are not restoring backups. I am planning on staying stock w/ root for a while so all I want is backups and restores to work. Any suggestions would be appreciated!
[Verizon Samsung Galaxy S III] DROID3R:
All this rom needs is the power button mod

Sent from my VERIZON GALAXY S 3 LTE
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Try TWRP!
[Verizon Samsung Galaxy S III] chetqwerty:
+1 HELP!!!

---------- Post added at 01:36 AM ---------- Previous post was at 01:11 AM ----------

fixed, just boot into recovery again and wipe data and cache again and boots right up
[Verizon Samsung Galaxy S III] jlokos:
You can flash the standard recovery from rom manager. It works and dates the backup correctly. Or you can DL VZW GS3 EZ-Recovery ~ multi-recovery flashing app which has CWM touch and TWRP. The CWM Touch doesn't date correctly, but it backs up and restores correctly.
[Verizon Samsung Galaxy S III] DROID3R:
Does the ez recovery include the standard one?

Sent from my VERIZON GALAXY S 3 LTE
[Verizon Samsung Galaxy S III] jlokos:
I don't think so. See thread http://rootzwiki.com/topic/29698-vzw-gs3-ez-recovery-multi-recovery-flashing-app/. It works great if you don't want to ADB or TE a custom recovery such as that needed to boot CM9 or CM10.
[Verizon Samsung Galaxy S III] sage3:
I flashed the standard recovery from rom manager but it did not date the backups correctly. Its not a big deal to me because it did restore. I also tried TWRP and liked it as well.
[Verizon Samsung Galaxy S III] jlokos:
That is strange. Reading through the threads, it appears that some have been getting the correct dates and others the incorrect ones. I don't know why this is occurring.
[Verizon Samsung Galaxy S III] parcou:
How do you see CPU usage? I disabled in the Application as well and not TB
[Verizon Samsung Galaxy S III] mad96:
I noticed it from running quadrant, and checked it with all apps enabled then the Verizon apps disabled and my CPU speed was at 1g instead of 1.5

M.yA.nD.droidS3
[Verizon Samsung Galaxy S III] EvilMonkey2:
I don't suppose anyone figured out how to get the Verizon email app (with the white background) onto a non-Verizon flash? It's been driving me nuts (even extracted the SecEmail.apk and odex files from my wife's stock Verizon phone and my background is still black.

Must be something else in Verizon's version doing this besides the apk. Just don't know what it is.
[Verizon Samsung Galaxy S III] fatalfuryy:
Just curious because i have installed CM10 on my phone. When you did the flash did you do use the EZ recovery and flash the d2vzw_recovery.img image on the phone first before you did the recovery reboot? If you did not you didnt flash it correctly

I could recommend using odin and reimaging the phone with stock, reroot the phone and try again

I followed droidstyles directions and it worked for me

http://xdaforums.com/showthread.php?t=1762709
[Verizon Samsung Galaxy S III] wmaudio:
I rooted, used ROM Manager to install CWM Touch, then rebooted to recovery. When I try to perform a backup, I get an error, "Error performing backup" and then brought back to the backup menu. Anyone know why this might be happening? TB and SU are both working properly. Thanks.

---Update---

I installed EZ-Recovery from Google Play and flashed CWM Touch Recovery, rebooted to Recovery and I'm now backing up without issue. Now to flash some ROMs!! :)
[Verizon Samsung Galaxy S III] ercDROID:
Is this link still active? I can't download. I want to ODIN back to stock and back up IMEI with QPST.
[Verizon Samsung Galaxy S III] pedroflovera:
You save me

Thank this save my phone!... :laugh:

I flash cm10 and i star getting (software unauthorized for verizon wireless detected) , and the phone not even boot on recovery.
[Verizon Samsung Galaxy S III] Cyber Warrior:
Anyone have a mirror for the rooted stock image? Megashare download link was taken down. Thanks.
[Verizon Samsung Galaxy S III] Zoandroid:
Touch Recovery 6.0.1.2 now works well on Galaxy S3

I flashed this rooted stock root66 ROM when it became available, and have been using it ever since. I recently discovered that the Clockworkmod Touch Recovery version 6.0.1.2 was reported as having now been approved for use on the S III. So I flashed that recovery about 2 weeks ago, and it seems to work fine. I've made 3 nandroid backups (still has the screwed up 1970 date in the name, unfortunately) and restored 2 of them at a later date, with no problems.

You may like to consider revising the current statement warning users away from Touch Recovery on the S III.
[Verizon Samsung Galaxy S III] h311sdr0id:
Would just like to confirm that the MegaShare link has been "Removed".
[Verizon Samsung Galaxy S III] imneveral0ne:
Uploaded one to my DB if anyone want's it

http://dl.dropbox.com/u/17392812/stock.vzw_root66.tar
[Verizon Samsung Galaxy S III] Cyber Warrior:
Getting a 404 error on that drop box link.
[Verizon Samsung Galaxy S III] zcar.300:
Anyone have a good download link?
[Verizon Samsung Galaxy S III] open1your1eyes0:
I will try to reupload when I get home tonight, not sure why megashare removed the link.
[Verizon Samsung Galaxy S III] Cyber Warrior:
Wow.. this is insane.. it is impossible to find a download link for the root66 tar file ... can someone please upload a working link for the community.(not a torrent)

TIA
[Verizon Samsung Galaxy S III] open1your1eyes0:
I have just updated the OP with a new link. I will ask if you guys can please create mirrors and I will post the links in the OP as well. There is too much traffic at one link and they get taken down very often.
[Verizon Samsung Galaxy S III] Nnyan:
http://dropcanvas.com/tacvd

http://www.filedropper.com/stockvzwroot667z

http://justbeamit.com/23901
[Verizon Samsung Galaxy S III] Srambo217:
Seems like once a day between 12pm and 4pm my device locks up, crashes, redraws, than doesn't get a 3G signal for about 30 seconds. Has happened while doing a variety of tasks (downloading an MMS, surfing Chrome, browsing TweakDeck). It's becoming rather annoying. Anyone else running route66 stock rooted experiencing anything like this?
[Verizon Samsung Galaxy S III] BugginOuT:
I thought this ROM disables the Verizon OTA updates?
[Verizon Samsung Galaxy S III] jmorton10:
it blocked it in mine.
[Verizon Samsung Galaxy S III] Cmotion:
If I previously had my bootloader unlocked, and then used Odin to flash the root66.tar, it doesn't re-lock the bootloader, does it? I should be able to flash the TeamWin Recovery, and proceed as normal, yes?
[Verizon Samsung Galaxy S III] BugginOuT:
Strange, I got a notification for a software update earlier this week. I let it install, knowing that it was going to fail anyways. No one else experienced this?
[Verizon Samsung Galaxy S III] guruffl:
Do you have to unlock your bootloader before this root process? Or is this simply a permanent root process and once applied I can flash ROMs all day?
[Verizon Samsung Galaxy S III] nojak:
No, this is just an image that was modified from stock to allow root access, and has SuperUser installed. Everything else about it is stock.

The bootloader is still locked on this. You do not need to unlock it before flashing.
[Verizon Samsung Galaxy S III] noingwhat:
What baseband version is this from?
[Verizon Samsung Galaxy S III] e_droid:
How do I make this stop? It is the most annoying notification. Phone is constantly rebooting into recovery trying to install itself.
[Verizon Samsung Galaxy S III] mrRobinson:
You'll want to freeze, remove, rename, pm disable, etc. (pick whatever method you want) the

FWUpgrade.apk and .odex and I think the SDM.apk and .odex.
[Verizon Samsung Galaxy S III] rigman:
OP - Can you put a link for a rooted ROM with the Verizon update already applied?
[Verizon Samsung Galaxy S III] BugginOuT:
I've tried to rename the SDM.apk to SDM.bak and the system couldn't locate that file, even though it's listed. Can't find the FWupgrade.apk under System\Apps.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Thanks so much for this image. Saved my butt the other day. Kudos!
[Verizon Samsung Galaxy S III] e_droid:
I can find them under system/app but can't rename the extensions (with root explorer)

Edit: found my error
[Verizon Samsung Galaxy S III] BugginOuT:
Please share....
[Verizon Samsung Galaxy S III] Wisiwyg:
root66 dl link

http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar
[Verizon Samsung Galaxy S III] e_droid:
At the top of Root Explorer you want it to show 'Mounted as r/w' with the button next to it showing Mount R/O
[Verizon Samsung Galaxy S III] JamesPumaEnjoi:
After flashing root method via Odin and installing a custom rom. The option for carrier billing via play store( Verizon) is not available... Is the due to root method or something else(verizon galaxy s3)
[Verizon Samsung Galaxy S III] OchoNueve:
root66.tar will not boot. HELP!!!

Long story short, I installed the CM 10.1 and lost data. So i'm falling the direction to restore my data and it led me to this thread. Everything pass with using ODIN and restoring this root66.tar but my problem is that I'm stuck on the boot screen. It will not fully boot up. I've tried this twice. What to do next?

Thanks.
[Verizon Samsung Galaxy S III] jackdubl:
Probably have an old Play Store version now. If that's it, just update Play Store.
[Verizon Samsung Galaxy S III] mrRobinson:
when coming from a different rom base you need to do a full wipe. boot into recovery and factory reset.
[Verizon Samsung Galaxy S III] jackdubl:
Make sure you got a good copy of root66. If you do and it still won't work, try flashing the actual stock Samsung image from the samsung site first.
[Verizon Samsung Galaxy S III] ricecake2000:
I am also stuck at the boot screen, and I cannot locate any stock images on the Samsung Site?? Please Help
[Verizon Samsung Galaxy S III] faehsemc:
I've noticed this doesn't work anymore. I got stuck at the boot screen.. so then I booted back into download mode and flashed cwm again. After that I rebooted into recovery and flashed the boot loader unlock and just restored an old nandroid...
[Verizon Samsung Galaxy S III] jackdubl:
Stickied thread for all S3 downloads.

You guys do know there are now stock and stock rooted unlocked images of Jelly Bean available, right?
[Verizon Samsung Galaxy S III] mrRobinson:
Anyone stuck at boot screen a full wipe should get you past that. Just boot to recovery.
[Verizon Samsung Galaxy S III] micahansel:
I have done all the above methods and still have no data connection. Roaming has went away but the mobile state just says connecting but never actually connects
[Verizon Samsung Galaxy S III] BigErnM:
Did you try the reprovision dialer code?: *2767*3855#

This has fixed a lot of people's issues with data after odin flash back to stock.This will wipe everything, so backup first if you need to.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
He just made a thread in the Q/A section too, reiterating the same thing. No mention of using the dialer code there either.
[Verizon Samsung Galaxy S III] micahansel:
I did try the dialer code. It ended up being multiple issues. The main being the line had been suspended. I truly believe this had to do with rooting. It happened to be the same time i was doing this. I wonder what could have flagged the system.