yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] open1your1eyes0:
I would recommend to factory reset, then immediately power off the phone and flash the full factory stock image. Then again power it off and flash the OP rooted image. Then go ahead and set up your phone. I do very much apologize that your internal memory was erased. Please kindly test again if the same thing happens when you factory reset. If it does then I will update as needed, but just FYI this is why I have step #3 in the OP regardless of what happens always backup your data (you can't trust technology).
[Verizon Samsung Galaxy S III] s197:
A factory reset does erase /mnt/sdcard. It does not erase /mnt/extSdCard.
[Verizon Samsung Galaxy S III] skiddingus:
Just wanted to say thanks. Installed the rooted rom and cwm. Everything is working great! Never lost an app or anything. The new CWM installation is a piece of cake.
[Verizon Samsung Galaxy S III] Noxious Ninja:
Sounds right to me. Will probably take 8-10 minutes.

Download mode/Odin operates outside of the normal Android OS. You don't need USB debugging enabled or to have non-Market apps enabled. I don't think having apps enabled/disabled will matter here, but I don't know the ICS built-in disabling works. If you removed some system app with Titanium Backup, you don't have to worry about restoring it.
[Verizon Samsung Galaxy S III] Zoandroid:
Honestly, as I read this thread, I had no idea what you meant by "Old Request" in the OP. It just confused me.

Thanks for clarifying that as of your post there were no issues.
[Verizon Samsung Galaxy S III] bgs_piece:
It wasn't a huge deal that the sd card was erased; I haven't had the phone long so there wasn't much on there. I had backed up everything to my computer, so just transfered everything back. I am wondering if the settings closing issue could be caused by an app I have installed. It was working fine for the first couple of days and when I was going through and installing everything from the market it all of the sudden started doing it. Narrowing down which one is going to be a hassle though.
[Verizon Samsung Galaxy S III] jbass350z:
How long should the flash take? Ive been sitting here for 45 minutes.. the bar is at 50% in ODIN but still slowly moving.
[Verizon Samsung Galaxy S III] Elite49:
So this is now the official way to pretty much root when you first get the phone? Ok then looks like I'll be needing this soon!
[Verizon Samsung Galaxy S III] bgs_piece:
I've done this a total of 3 times now and the longest it took was 10~11 minutes.
[Verizon Samsung Galaxy S III] rfurman24:
To those that have tried the invisiblek root and are having issues which one did you use and did you flash CWM(which one)? I have the full stock invisiblek root and flashed CWM through Google Play and have absolutely no problems. I see no signs of this mentioned Sprint elements.
[Verizon Samsung Galaxy S III] rldev:
The only problem I have is Google Play does not list the apps I have purchased. If I individually seek them out, it knows I paid for them. Not a big deal but strange considering I haven't seen anyone else mention this.
[Verizon Samsung Galaxy S III] rigman:
Have you tried running Titanium Backup's Market Doctor to fix the links?
[Verizon Samsung Galaxy S III] Funkybooyea:
Does anyone know how to access the external sd card in CWM? I do not like to store all my roms and flashable files on my internal SD Card.
[Verizon Samsung Galaxy S III] Zoandroid:
This ^^^^^^ +1

Along that same thought, does anyone know of a utility I could install that would internally make automatic backups to the "real" SD Card of any folders I would select that are on the internal "SD Card"? I can do that manually, but would prefer an automated app.
[Verizon Samsung Galaxy S III] neemo6:
Not sure if mentioned yet, but does this method bypass the Root check that is supposedly built into the bootloader?
[Verizon Samsung Galaxy S III] bgs_piece:
I downloaded the original stock image and need to flash it but its a zip file that contains 2 files; one of them is a MD5 file type and the other is a .dll file. Do I unzip the the files and change the file extension on the MD5 to a .tar? The name of the file is "HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5" and the other file is "SS_DL.dll".

I am having issues with the rooted version so I need to go back to completely stock and try again.
[Verizon Samsung Galaxy S III] rldev:
Wouldn't that require that I have already downloaded everything?
[Verizon Samsung Galaxy S III] faehsemc:
Thank you for root... i dont caee about roms really... i was just SICK OF ADS! thank you root and adfree android.. plus that damn wifi notification sucked
[Verizon Samsung Galaxy S III] justinglock40:
Anyone have issues with they're power button after getting this flashed. My screen won't turn off if I press the button and the power menu randomly pop-up
[Verizon Samsung Galaxy S III] Stam2000:
Anyone having battery issues with this version? I think I may need to write and reinstall. Getting about 6 hours of battery
[Verizon Samsung Galaxy S III] bamfart:
thanks for the torrent file, much faster.
[Verizon Samsung Galaxy S III] m1llert1me:
I went from 18 hours all 4G to about 6. I am am back to stock for now. Back to 18+ hours.
[Verizon Samsung Galaxy S III] xformulax:
no issues here, not only do i get well over 6 hours, i actually get more than 6 hours of screen on time.... amazed by this phone.
[Verizon Samsung Galaxy S III] s197:
+1

No battery or power button issues here.
[Verizon Samsung Galaxy S III] azradiohead:
Other oddities from the original non stock rom

Something I noticed today. One of our (non rooted) Galaxy S III's made the EAS (Emergency Alert) tone, I thought it was on the TV in the other room until we checked and realized there was a EAS Flash Flood warning on the phone. I clicked more info and it provided the National Weather Service details. I was curious where this came from and backed out of it to find the Messaging app caused it. I went into Messaging Settings and at the bottom there is a section titled 'Emergency message settings'. The other non rooted phone didn't give the warning but it turns out I we disabled the messaging app in App Manager, it's not re-enabled and shows the Emergency settings. I went into the Messaging on my (rooted with the original root rom) phone and all I had instead of the 'Emergency message settings' was a option for 'CB Messages'. I remember CB are Cell-Broadcast SMS Messages, similar to EAS but it was disabled. I already downloaded the root66 ROM and re-installed it through Odin and now my 'Emergency message settings' options are back in the Messaging app settings. The Alert options offer Presidential Alerts (can't be unchecked), Extreme Alerts, Severe Alerts, and AMBER Alerts. Just a little FYI that I hadn't seen listed anywhere else so there is something else to add to the differences between the Verizon and Sprint roms.

Cheers,

:cowboy:
[Verizon Samsung Galaxy S III] Zoandroid:
This procedure worked for me to root. Installed ROM Mgr from Play store, and it hung the first time I flashed CWM Recovery for the GS3 (not touch recovery). I Rebooted and ran ROM Mgr again, successfully flashing CWM Recovery. I made a nandroid. It seemed to work OK, but the date is screwy, showing 1970-01-05.03.45.02. Any way to get the date fixed for making nandroids? Past experience has shown me that changing the name on a nandroid file will cause an MD5 mismatch when you try to restore it in CWM Recovery.

Thanks!
[Verizon Samsung Galaxy S III] open1your1eyes0:
For now it seems to be a small (but not important) bug that is an issue in all version of CWM and even TWRP. You can correct the date yourself manually and to fix the MD5 mismatch issue take a look at this: Link. Hope it helps. :)
[Verizon Samsung Galaxy S III] Elite49:
So according to some of the recent posts this still isn't 100% non problematic? Just to be sure ill do this once I get my phone ill factory restore, and flash like OP. Don't understand why people are having issues with this. Do it when phones 100% and calibrate battery.
[Verizon Samsung Galaxy S III] mrRobinson:
I can virtually guarantee you there are no problems with this. Any issues are something specific to that user's phone. I injected root into 4 other images before this. If you see an issue with this then you'll see it on stock.
[Verizon Samsung Galaxy S III] open1your1eyes0:
I can attest to this as well. I have running this build since the day it was released with no issues whatsoever. :)

On a sidenote: Would be great to have an exact deodexed/zipaligned version of this build if possible. The CWM flashable one in the other thread seems to have issues as well.
[Verizon Samsung Galaxy S III] jlokos:
+1; no issues with this build; works great. Also a +1 for the deodexed/zipaligned version. thanks for all of your help and work mrRobinson.
[Verizon Samsung Galaxy S III] Zoandroid:
Thanks. I started into that thread and now I have to wonder if I possibly may have had spaces in the new name when I renamed the nandroid. I know sometimes that is not allowed, but I can't recall now because the incident happened months ago. I suppose I could do some experimenting and see if 'just the rename' matters or if it was an issue of spaces in the name.

Edit - Well, I'm guessing my original MD5 mismatch issue had to be that spaces were used in the folder name, because I am currently restoring a renamed copy of the nandroid I made right after rooting this afternoon, and it is working. The renamed file name is STOCK-ROOTED-12_0714_1742. It just finished restoring OK.
[Verizon Samsung Galaxy S III] s197:
That's correct, you can rename but using spaces or special characters can result in an MD5 mismatch. Otherwise, you'll be okay.
[Verizon Samsung Galaxy S III] Elite49:
Ok thanks. I thought it would be user errors, just didn't want to flash this to have to flash another one a day later. Yea one of those would be great rom.
[Verizon Samsung Galaxy S III] parcou:
CallRecord

People...

I am not looking to make this question a fight as to why I am doing it, is it legal, etc. etc. as people tend to get into with this question. Does the kernel of this rom allow for call recording from kernel??

I have a rooted HTC Thunderbolt running BAMF Soab rom w/IMOS kernel and waiting for the Samsung phone to deliver. I am North America tech support and clock over 3500 minutes per month on global conference calls. Being able to listen back to my calls, collect minutes, and re-capture things I missed is hung for me when you support half the globe.

So pls no flaming on this question. I just want to know will the stock kernel work with my paid CallRecord app or will I have to see another kernel for the SIII phone.

Thx
[Verizon Samsung Galaxy S III] skiddingus:
I am also on this rom and it is perfect. Absolutely no issues. I can also say that the recovery method from the OP works perfectly. I loved this rom but I wanted the 50gb from dropbox. I made a backup of this rom, then flashed the beans rom and signed into dropbox to get the 50 gb upgrade. It worked perfectly. Then I did another wipe and flashed back to this rom. I am hoping the 50gb upgrade stays because dropbox should just assume I have another device. Everything worked perfectly. Thanks to everyone for all the work involved with creating these roms. I only hope that when "official" updates are released that we can get another rom like this that is simple rooted stock.
[Verizon Samsung Galaxy S III] xliderider:
Need a little help here lol. I flashed the root66 file in Odin and when my SG3 rebooted I see this overlay with system settings and info on my homescreen:

There was a brief pop-up window that said the device was in Factory Mode I think. How do I get out of this mode? A reboot and a battery pull didn't have any effect. Thanks.

Edit: Found solution searching xda. If anyone else gets stuck in Factory Mode after flashing, do this:

Open a terminal emulator

Type su

Then enter the following after the #

echo -n ON > /efs/FactoryApp/factorymode

(yes ON is the correct setting to turn it off)

Then I had to reboot for the change to take effect. FYI, I had to go through initial setup after the reboot.
[Verizon Samsung Galaxy S III] wardo5757:
thats some real stupid ****... he talking about and trying to get a problem resolved... and how the hell do you know if there is a problem until you DO flASH..
[Verizon Samsung Galaxy S III] Neverendingxsin:
+1 for the sidenote :)

i heard with the deodexed it messes up mms :(
[Verizon Samsung Galaxy S III] Zoandroid:
WiFi instabilities?

I hate to rain on this parade, but I MIGHT have a problem to report. I could use some help in testing this if you can provide perhaps a more reliable way to do it.

I use Cheetah Sync to back up files by WiFi from my Iconia A500 tablet running ICS, and it works fine. So I decided to try it on the S3 once I had the ROM which this thread supports up and running. Cheetah Sync allows one to specify a target folder on your PC, and then specify a source folder on the Android device, and will synchronize the files between them over wifi. I use a one-way sync from Android to PC. It had been working well as I began syncing essentially small folder content like Memento database, MobisleNotes, and NoteEverthing. But when I tried to sync my clockworkmod folder with a nandroid in it (which works fairly fast and flawlessly when done from the tablet) the S3 keeps disconnecting from my D-Link DIR655 router's wifi connection, and in so doing it loses the wifi icon in the notification bar.

I tried deleting the wifi connection (I use DHCP WPA/PSK) and making a new connection, and then tested the tablet again while it sits here on my desk right next to the S3 (the router is about 15 feet away). Both devices are on their charge cables. The S3 has about 75% charge. The tablet quickly and flawlessly completed its sync. The S3 keeps throwing a rather wordy error message as it loses its connection. I used a pair of screen shots to capture the entire message because it scrolls and is about 2 screens tall. Please see attached.

Because I can repeat the error on the S3, but not on the tablet, I believe that vindicates the router as being the problem. Unfortunately that leaves only the S3, its hardware, and software where the problem has to lie. Any help would be appreciated.
[Verizon Samsung Galaxy S III] Zoandroid:
Well, after a reboot of the S3, I was getting 3-4 'rays' of signal here at my desk, but the S3 still seems to suddenly drop out of wifi and switch to 3G while trying to copy the 1.57GB nandroid to my PC. However, when I put the S3 directly in front of my router, it copies the whole file OK.

I decided to try Kies Air, and am having the exact same problem. The files start to copy, with the wifi icon showing 3-4 rays, and then suddenly it drops wifi and switches to 3G, just as if the router had been switched off or something. I finally decided to try cycling the power to my router. Once I did that, both Kies Air and Cheetah Sync were successful in their file copying operations. If things stay good now, I guess it won't be any sort of problem with the S3 itself.
[Verizon Samsung Galaxy S III] zcar.300:
It didn't give me any options while flashing. It did flash but it doesn't any option to apply an update.zip from internal memory.

To Install Official CWM Recovery

***Do not flash the touch version just yet, only use regular v5.8.4.9***

1. After following above process, download "Rom Manager" from the Play Store

2. Open Rom Manager

3. Select "Flash ClockworkMod Recovery"

4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash

5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
[Verizon Samsung Galaxy S III] pkd600:
Has anybody else had problems doing this? I downloaded ROM Manager, have given it Root permissions, but when I try to install the Samsung Galaxy S3 (Verizon) CWM, ROM Manager seems to freeze up and eventually tells me it isn't responding
[Verizon Samsung Galaxy S III] zcar.300:
Fixed

OK, you can't just use the "flash Clockworkmod Recovery" at the top of the in Rom Manager. You have to scroll down and use the one at the bottom of the app. My bad...
[Verizon Samsung Galaxy S III] jlokos:
I didn't have that problem when I flashed recovery from Rom manager. It flashed from the top item. I was also able to flash the touch version. The only problem was I could not get that version to make a back up. if you are having problems with recovery see this thread: http://xdaforums.com/showthread.php?t=1760376
[Verizon Samsung Galaxy S III] BungeBash:
I think the WiFi issue is a known problem with the phone. Before I rooted I was having a similar issue when trying to transfer large amounts of music.
[Verizon Samsung Galaxy S III] skiddingus:
It worked for me a few days ago.
[Verizon Samsung Galaxy S III] Zoandroid:
That's exactly what happened to me. I rebooted the S3 and tried a second time, and it worked.

---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------

Thanks. I hoped not, because I had read a lot of concerned posts wondering about the quality of the radios in the S3, compared to the Nexus. I guess the thing to do is run the same operation again tonight and see if I have the same problem again.

Edit - I just made another nandroid tonight, and successfully used Cheetah Sync to send it by wifi to my PC, no problems at all. So hopefully this issue is behind me now. :)
[Verizon Samsung Galaxy S III] Bassdj427:
Hey guys, I'm running root66 and cannot send mms...any fix for this atm?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Mine is working fine, don't think any one else reported as well. Highly recommend factory reset and then reflash root66.

EDIT: FYI little tip, I was having major messaging issues when I was restoring my 5000+ SMS/MMS from my old phone using Titanium Backup. It was freezing and using up a lot of CPU usage. After a while I finally realized what was happening is that the messaging app had a set limit of 200 messages in the options and because of that it kept stalling and freezing. Soon as I unchecked that and tried restoring again, no issues. Just a little reminder in case anyone forgets.
[Verizon Samsung Galaxy S III] BungeBash:
Something is causing my stock music player to act weird. It randomly pauses songs or fast forwards. I cant get through full songs now.
[Verizon Samsung Galaxy S III] pjamv5:
I'm having issues with copy/paste. It's either not working, or it's force closing any apps I attempt it in. I tried clearing my cache and that didn't help. Anyone else experiencing this?

Edit: Well after a quick Google search it looks like it may be a more global issue with the S3...

http://androidforums.com/samsung-ga...-s3-crashing-when-copying-text-clipboard.html
[Verizon Samsung Galaxy S III] pkd600:
Yup, I tried it again last night after rebooting and it flashed fine!
[Verizon Samsung Galaxy S III] BungeBash:
Seems an unmount/remount of the SD card fixed it...mostly. Still randomly pauses...
[Verizon Samsung Galaxy S III] Assassin74:
Hi I flashed this and have no issues other than I can`t use any terminal emulators or root explorer. They will launch then freeze up for about 5 minutes and crash my phone. Any one have any ideas what the problem could be or how to fix it? all other root apps work fine.
[Verizon Samsung Galaxy S III] vudugan:
I just checked that Messaging setting and I too have the CB setting. If I read your post right, (cause I can't exactly remember where i got the rooted stock file..) I have the image that this Thread is warning against? Since getting root, I noticed battery draining faster and wifi issues but didn't think it could be caused by rooting. I have the stock.vzw_root66 downloaded now and waiting. Can someone confirm this please?
[Verizon Samsung Galaxy S III] Elite49:
Did you factory default or no? I don't have phone yet but am following this thread and others noticing rooted users are saying they have less battery then normal.
[Verizon Samsung Galaxy S III] vudugan:
Not yet, was waiting to see what others thought before I got back home and charge up. Will more than likely reset and re root before night is over. Been browsing Web and noticing phone getting warmer. It's got to be the case though.
[Verizon Samsung Galaxy S III] Glasairmell:
Hi,

Coming from a bone stock VWZ G3 I applied the OPs method and have zero issues with the root or CWM. Battery is great and every app works including root explorer and terminal.

Phone behaves exactly as it did before the root after many hours of use.

Thank you!
[Verizon Samsung Galaxy S III] Morrisme:
going to try tonight, thanks for the good work.
[Verizon Samsung Galaxy S III] bucsfann20:
Once I click PDA and start, Odin gets stuck on "Get Pit for mapping..." then fails.

any ideas?
[Verizon Samsung Galaxy S III] aigochamaloh:
I had been debating flashing this or not for awhile, even before I received my phone. Got my phone today, set it up the way I wanted, then finally just took the plunge. All my stuff was saved no problem, as expected. Didn't flash custom recovery cause I don't care about custom roms yet. Just wanted Ti Backup and wifi tether, which work perfectly. MMS works, nothing is broken as far as I can tell. ODIN Mode still says official binary, so that's good. Thanks for the hard work!
[Verizon Samsung Galaxy S III] radiohead14:
^this please! :good:
[Verizon Samsung Galaxy S III] vudugan:
Went ahead and factory reset, rooted according to this thread and file, reflashed wifi icon. Settings under messaging for Emergency message settings have been corrected. Thx for that lil info azradiohead!

Off to work I go.
[Verizon Samsung Galaxy S III] faehsemc:
Redownload the file check md5. Also try a different cable or pc if that doesnt work.
[Verizon Samsung Galaxy S III] mb27:
I rooted last night and I've gotten pretty nasty battery drain. It's gone from 100% to 59% in 4h 43m. Cell standby accounts for 82% of that (I was sleeping). Device idle was 8%, screen 5%*, android system 4%, maps 1%.

Normally when I get 8 hours of sleep it goes down 1-3%. What happened??? :crying:

I'm reading about a cell standby bug, but that seems just like a bug in the reporting (ie, getting 14hrs of battery still but cell standby makes up a high percentage).

On mine, the actually battery life drastically decreased.

*I used it a little after I unplugged it and before my head hit the pillow

EDIT: I flashed the cell standby fix, and it changed it from 82% to 31%. Still doesn't help the fact that the battery decreased 41% in 4 hours when it had been 1-3% in 8 hours.
[Verizon Samsung Galaxy S III] griffis:
Can we get a zip of the stock rooted rom that can be flashed in CWR?

Thanks for your work!
[Verizon Samsung Galaxy S III] Elite49:
Did you factory reset like in OP?
[Verizon Samsung Galaxy S III] johnh123:
Where are you seeing this?
[Verizon Samsung Galaxy S III] BungeBash:
I'm actually in the middle of doing a compile for the image. I have just added the binary and app into the stock Verizon image and I'm trying to check all loose ends.
[Verizon Samsung Galaxy S III] open1your1eyes0:
I was trying this method myself using adb shell on my Xoom but I'm having trouble with makeuserimg.sh command. When I enter "./mkuserimg.sh -s temp system.img ext4 tempdir 1536M", it keeps saying "sh: ./mkuserimg.sh: No such file or directory". In fact before that, it was saying "cannot execute - permission denied", I added execute permissions to mkuserimg.sh and then it was giving me the file/directory not found error. Not sure what's happening when I have the "temp" directory mounted. I think I'm very close though. Any ideas? It's quite a poor quality guide if you ask me...
[Verizon Samsung Galaxy S III] eckzow:
./mkuserimg.sh is from the ext4_utils. Copy it into whatever directory you have temp/ in, and grab ext4_utils/make_ext4fs while you're at it or you'll get another missing file error when it runs. (Or update the paths in the script and call it from wherever it lives.)
[Verizon Samsung Galaxy S III] BungeBash:
I'm trying to work off of my windows machine and using a whole lot of work arounds right now to get through the steps. If you are able, try:

sudo ./make_ext4fs -s -l 512M -a system new.img sys/