yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Addiso:
Lol I just love how I'm on all this even if I don't have the gs3 yet waiting for my update on dec.15 haha just want to be prepared and everything set up thanks bro ;)

Sent from my Goonified Paranoid Jelly Droid Incredible 2
[Verizon Samsung Galaxy S III] FAUguy:
Got J1 up and running, rooted, unlocked, cwm.

Two browser issues still remain: When typing in a forum (such as this text box) the Paste long-press doesn't always show, and when using the cursor arrow pointer it jumps around alot. This is in Chrome, Dolphin, and Stock. Neither of these browser issues were in ICS F2/G7/HE.
[Verizon Samsung Galaxy S III] aigochamaloh:
Sweet update, especially if this does end up being the OTA build like it was mentioned in the other thread.

When you say no data wipe, will my texts still be there? That's pretty much the only thing I care about, I can reinstall everything else if it needs be.
[Verizon Samsung Galaxy S III] xluryan:
I followed the instructions, however I seem to be hitting a wall. I am coming from CM10.

After flashing the PDA in step 1, my GS3 never finishes booting. It turns on, shows the SAMSUNG logo, then Samsung Galaxy S III, then the SAMSUNG boot animation, then the Verizon 4G LTE boot loop repeats forever. I've let it sit for 10+ minutes, battery pull, then power on. Same thing every time.

Any ideas?
[Verizon Samsung Galaxy S III] andydesai:
Thanks....

Hey thanks for the new update on K1 i dont know how many of you had this problem of the media process eating up the battery... my phone would not last even 6 hours....yesterday i flashed the new release K3 and charged the phone to 100% now i am 71% after 4 and half hour... wifi is continuously on, made some calls,been using whats app and listening to music... And in the battery usage if i check this what is been using.

screen 28%

voice calls 23%

android os 14%

android system 11%

MAP service samsung 11%

media server 6%

cell satndby 3%

wifi 3%

Device idle 3%

music player 2%

Now looking at this anyone here can tell me whether the battery usage is ok or u feel any process is eating up the battery...or how to optimize battery life....

Once again i am thankfull to open1your1eyes0 providing the Jb K3...
[Verizon Samsung Galaxy S III] rtop2:
I flashed this over my stock ICS and I dont have super user, its supposed to right?
[Verizon Samsung Galaxy S III] andydesai:
Hi their it does not write on itself ....you have to flash Clockworkmod touch recovery and after that boot into the recovery and then flash super user and bootunlocker file which you should place on your sd card before flashing it...you did not follow steps 2 and 3 in the first post. Please have look at them.

After you follow the above you will be rooted.
[Verizon Samsung Galaxy S III] Gareee:
Looks like both links to download #8 are currently down. ---> 8.Stock VRBLK3 Factory Image with No Data Wipe - Links (1, 2)

Alternatives?
[Verizon Samsung Galaxy S III] suXor:
Not down, just sssslllllooooowwwww
[Verizon Samsung Galaxy S III] Gareee:
I'll try again then. Thanks!

EDIT:

This is listed at the top of both download links:

"SYSTEM NOTICE: CA Server M5 having some issues. Taken offline until its fixed"
[Verizon Samsung Galaxy S III] buschbarber:
I have already rooted my Verizon S3 and have flashed CM Recovery. I am familiar with flashing Roms on my HTC Thunderbolt. I boot into Recovery and flash a ZIP file from the SD card. This Rom file name has an extension of .tar.md5. How do I flash that with CM Recovery?
[Verizon Samsung Galaxy S III] droidstyle:
you dont...read the other guide stickied, section 2.
[Verizon Samsung Galaxy S III] AJ26T:
You dont flash a .tar file via cm recovery a .tar file is meant to flash via odin

You want to flash jb stock scott has a stock rooted rom
[Verizon Samsung Galaxy S III] droidstyle:
you need to wipe data factory reset!
[Verizon Samsung Galaxy S III] buschbarber:
I am new to this forum so I do not know who Scott is. I was anxious to upgrade to Jellybean. Do you have a link to his Stock Rooted Rom?

I am not familiar with Odin or why I would want that instead of ClockworkMod Recovery.
[Verizon Samsung Galaxy S III] AJ26T:
If you back out of this thread and scroll down you will find alot of jelly bean roms custom and stock

Here is a stock one. http://xdaforums.com/showthread.php?p=35129131
[Verizon Samsung Galaxy S III] droidstyle:
sir I will say one more time then your on your own...click the gs3 link in my sig and proceed to section 2...nobody hear will offer more clear and concise instructions. When you get to section 2, chose beans stock rooted deodexed K3 rom and proceed.
[Verizon Samsung Galaxy S III] GalaxySII5191:
You can't. You have to use odin
[Verizon Samsung Galaxy S III] shafty023:
For those of us that have been using the no-wipes, would simply flashing the latest leak w/ a wipe fix these issues? Especially if we don't care if we lose our data.

EDIT

Never mind, the CRC check fails trying to flash the new update w/ wipe so we're kind of stuck until the fix is released.
[Verizon Samsung Galaxy S III] BigErnM:
Download links for 5-7 are down for me.

Working again.
[Verizon Samsung Galaxy S III] xluryan:
Well, I would love to do that, however, Odin no longer recognizes my phone when it's in download mode. Any ideas?
[Verizon Samsung Galaxy S III] US Marine:
Not to insult your intelligence, but have you rebooted your computer, tried different USB ports, or reinstalled the Samsung drivers? Odin can be quite finicky.
[Verizon Samsung Galaxy S III] buggerritt:
Do these unlocked bootchains with CWM recovery not work on the stock unrooted data wipe leak? I just Odined to the latest build and wanted to unlock/root it but both TWRP and CWM files fail in Odin for me. I've tried several times redownloading and retrying. I reflashed the leak too. I'm guessing that these only work on the no data wipe versions?

Edit: Yep. That's what's up. I flashed the no data wipe version and then was able to flash the bootchain successfully.
[Verizon Samsung Galaxy S III] cnlson:
The XDA effect :)

New mirror for K3
[Verizon Samsung Galaxy S III] Ryno77:
I'm assuming this fix does more than a factory reset would...obviously the "fix" saves your data but if doing a factory reset fixes the problems I would give it a shot. I'm trying to download the with wipe version but it stops downloading literally every minute.
[Verizon Samsung Galaxy S III] shafty023:
If you can tell me what the issue is I'm pretty sure I could do it myself without having to wait for a flashable zip. Or if you're not 100% sure at least openly discuss what you think the issue is and those of us with years of experience can help out.
[Verizon Samsung Galaxy S III] xluryan:
I have rebooted, tried different versions of Odin, different ports, etc...

Still nothing. I have an old GS2 and Odin sees that just fine. Thanks for the quick reply, anything else you can suggest?
[Verizon Samsung Galaxy S III] wooddale:
I have 2 computers a new desk top with all the whistles and bells and an older HP laptop. My new shiunny desktop cant see squat no matter where I plug in my old HP lights up like a Christmas tree when I plug into it figure it out lol.
[Verizon Samsung Galaxy S III] xluryan:
EDIT:

Ok I've got Odin to recognize the phone. Driver issue...

But new question. I did a nandroid backup before my first flash. How can I access that file now if my phone won't boot?
[Verizon Samsung Galaxy S III] cnlson:
I think you may need to check this thread

http://xdaforums.com/showthread.php?t=1840030
[Verizon Samsung Galaxy S III] xluryan:
Will I lose my data/apps/etc with that method?
[Verizon Samsung Galaxy S III] pvcdroid:
Try checking boot settings on your machines "USB Wake settings". Mine was disabled for some reason. Drove me nuts till I found it.
[Verizon Samsung Galaxy S III] cnlson:
I don't know for sure, but rather that than the phone. At least if you know adb commands you should be able to move your nandroid backup before trying.
[Verizon Samsung Galaxy S III] xluryan:
Can I use adb from download mode??
[Verizon Samsung Galaxy S III] KevTN:
Finally got Odin to work for me...stupid question how do I tell if my counter was tripped?
[Verizon Samsung Galaxy S III] AJ26T:
Go into download mode and up top it says Custom Binary mode if it says no after it your fine or it may say yes then it was tripped
[Verizon Samsung Galaxy S III] Snakehn:
any mirror for the DATA WIPE version? thanks
[Verizon Samsung Galaxy S III] x714x:
http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html
[Verizon Samsung Galaxy S III] suXor:
I did a full wipe on this (LK1 and LK3), and noticed that it seems much changed from the original ROM from Samsung. Number of languages at startup increased many times over, Find My Mobile (under security settings) appeared, many default shortcuts on the home screens were missing. What exactly was changed to cause all of this? I am not complaining, just curious.

Find my mobile doesn't seem to actually connect to the service like my Wi-Fi Tablet does.
[Verizon Samsung Galaxy S III] shafty023:
For those that followed the no-wipe installation path and are still having battery drain from the Media service like I was I have a solution. Reboot into CWM recovery, do a full data wipe, then wipe cache, then go into advanced and wipe dalvik-cache, then reinstall the latest no-wipe. I also removed all of the Verizon bloatware

except

for My Verizon Mobile and Mobile Hotspot. So far 24 hours later and no battery drain. And like the poster above says, things definitely look different when you actually wipe (good thing).
[Verizon Samsung Galaxy S III] fanto3k4:
Per the link in OP...

Stock VRBLK3 Factory Image with Data Wipe (Original Untouched) - Link

***The above image is FOR REFERENCE ONLY - DO NOT USE IN MY GUIDE***

MD5: F751236B4CA13FA272DC4D6A78D3250B

I am getting MD5 2b6566c30e2a2cd94d624fe3149c908b

I am downloading from the mirror to see if I can get the correct MD5 value but wanted to make sure the value is correct.

<<<<<Update>>>>>

Second download and I got the correct MD5
[Verizon Samsung Galaxy S III] cnlson:
I'll be honest and tell you that I do not know, but my thoughts are that you can. I really think your posts are in the wrong thread here. I would check the other thread out and try what they suggest and report issues in that thread since that is the focus of it. You aren't getting many replies here because that isn't the focus of this thread, and the "experts" in bricked phones are in the other thread. When you get it sorted (Samsung phones are mostly recoverable) let us know what you did and it can be added to the faq on the first page of this thread.
[Verizon Samsung Galaxy S III] Snakehn:
Outstanding, will try in when I get off from work thanks.
[Verizon Samsung Galaxy S III] open1your1eyes0:
For those of you guys who would like to try a temporary workaround to fix those small bugs while I'm working on making new No-Wipe images this is what worked on my device:

Note

: For

knowledgeable/advanced members only

that have full experience with ODIN and CWM

Copy all contents of your internal (built-in) SD card storage on your device to your computer

- May have to use "adb pull /storage/sdcard0" if regular drag-and-drop doesn't work

Make a full CWM nandroid backup to an

EXTERNAL

SD Card card on your device

Take the external SD Card out of your device and set it aside

Use ODIN to flash the original Full Wipe image (Link)

Verify the MD5 of that file is

F751236B4CA13FA272DC4D6A78D3250B

before flashing!!

After the device reboots twice, just run through the quick setup and setup up basic settings

- No need to add your Google account or anything, just skip that and make sure everything is working on the device and you don't see any of the previous bugs anymore

Once you have tested all is good, connect the device to your computer and restore all contents of your saved internal SD card storage back to the device as before

Flash VRALEC bootchain in ODIN to allow you to flash custom recoveries again (Link)

Flash VRBLK3 bootchain (with CWM included) in ODIN (Link)

Insert your external SD Card back into your device

Boot to CWM Recovery and "Advance Restore" only your "Data" partition from the nandroid backup you made earlier

If all is well, upon reboot you should have your device back to the same condition it was before but this time all the listed bugs should be resolved

Disclaimer

: No guarantees for this method, it worked fine for my device doing the process exactly in that order but I cannot guarantee anything for other devices. Proceed at your own risk and as I have stated before this is for

advanced users only

!
[Verizon Samsung Galaxy S III] aaroncal:
Followed all the step to the tee as I always do and the phone will not boot or do any thin after flash system image
[Verizon Samsung Galaxy S III] open1your1eyes0:
I assume you're talking about the 4th bullet? Did you use this link? Confirm your MD5 of that file is F751236B4CA13FA272DC4D6A78D3250B. Try again if it is.

I just flashed that image last night so I know it works as long as the file you got was not corrupt. Very important that you verify the MD5 before doing anything.
[Verizon Samsung Galaxy S III] buhohitr:
I flashed the no data wipe K3 from K1 and I lost root?? anyone has this issue?
[Verizon Samsung Galaxy S III] open1your1eyes0:
This is absolutely normal. That's why you have to follow all three steps again to get Root and Recovery back.
[Verizon Samsung Galaxy S III] buhohitr:
What 3 steps you refered to??
[Verizon Samsung Galaxy S III] open1your1eyes0:
The same three steps you used to get each build rooted using the OP in this thread. You have to do them each time you upgrade to a new build.
[Verizon Samsung Galaxy S III] aaroncal:
Cannot get into download mode and does not boot and PC does not recognize it even through adb

i747 GS3 Gem Dandy ROM 4.1.2
[Verizon Samsung Galaxy S III] buschbarber:
I am happy to say that I was able to install Odin, flash the rom, reinstall Recovery, and Root/Unlock the phone, again. I found that when booting into Recovery, I had to release the Power button immediately after I felt the vibration, or it booted normally. Timing was critical.
[Verizon Samsung Galaxy S III] junksecret:
Ummmmmmmm, your sig says i747, you do realize this is a Verizon SIII leak??
[Verizon Samsung Galaxy S III] open1your1eyes0:
Thank you for pointing that out junksecret. I didn't even notice before.

Unfortunately he is correct. If you did just flash this image over your i747 and not i535 it is very likely your device is now permanently bricked as you overwrote an incompatible bootloader. Unfortunately we can't help you now since the only way to fix it through software means is to flash your i747 bootloader or full factory image in Download Mode through ODIN. But if you can't get to Download Mode in the first place then you are officially stuck and have to get your device replaced either with your carrier or via Samsung RMA under warranty.
[Verizon Samsung Galaxy S III] dunderball:
Are there any negative experiences from going from stock to J1 leak to K1 leak to K3 leak? I've used both no-wipe versions so far and am wondering if it's even worth going to the K3 leak. I'm thinking of just staying on K1 until open1your1eyes come out with a solid no-wipe version of the official Verizon OTA (whenever that comes out).
[Verizon Samsung Galaxy S III] open1your1eyes0:
I may have a new No-Wipe image with the fix ready shortly. If anyone is willing to test please PM me and I will send you details.
[Verizon Samsung Galaxy S III] fanto3k4:
I have not had much time to play with it but over the weekend I went from No Wipe K3 to Wipe K3. Right off the back I noticed my corporate email background is no longer black like it was in K1 and I think K3 No Wipe versions.
[Verizon Samsung Galaxy S III] Sting32:
Dumb question #1

Here's where I am at. I have had older phones, that I've flashed. I kind of get the process, I did things just like it before, with my old Touch pro 2's and stuff. Dont get me wrong, I know I have to read and reread everything, I just want to be sure. Most of that was long ago with windows phone, and dual booting, but still I just need to ask a couple questions:

My VZW GS3 is stock, no "mods". I am reading the 3 steps involved, do I really need to continue after step 1? As I read it, after step 1 Im on JB. But, not sure why to go on to steps 2 & 3?

I guess I would've been highly recommended to, do steps 2 & 3, only so if I have a problem I can reflash to where I was after I did step 1, right? or am I misreading everything?

All I want to DO, is to see if I like this phone on JB? Then I can go on from there.

if I don't for any reason like JB, (which you may doubt) I would like to go back easily. Is that in itself a problem? Back in the old days we had a copy of the stock rom we'd load if we had to send for warranty, I see this is not true today with the SG3, but I admit I have some more reading to do... I have to do my homework in spurts, so if anyone can see what I am asking, it would help to clarify how much further I want to go.

Thanks to all of you in advance.
[Verizon Samsung Galaxy S III] open1your1eyes0:
The black background you saw is actually a small bug in my No-Wipe images, it should always be white like in ICS. I mentioned a few posts back. I am preparing a fix shortly after I have a few testers.
[Verizon Samsung Galaxy S III] aaroncal:
I have have both carriers and the problems I have explained are on my Verizon gs3. Sorry my SIG might of made it confusing

i747 GS3 Gem Dandy ROM 4.1.2
[Verizon Samsung Galaxy S III] open1your1eyes0:
Thank you for clarifying. In all likely cases however if you are not able to boot into any mode on the phone and you have verified that your battery is good then you are likely permanently bricked on the device. Right now what I'd like to figure out is what happened. Many users have used this file already so I know it's not the file itself. Most likely case is that you got a corrupt download and flashed that. If you still have the original file you used to flash the image can you please run an MD5 check and post the MD5 of that file?
[Verizon Samsung Galaxy S III] xluryan:
Well, I can tell you what happened to me was that I flashed the NO WIPE and then my device would not boot. I left it plugged in during one of the boot attempts and Windows started installing drivers. Foolishly, I unplugged my device in the middle of Windows installing drivers and as a result my Windows drivers were corrupted (which I didn't figure out until later).

I could still get to download mode and recovery. As an FYI to anyone else in that boat: adb does NOT work in download mode (not how you'd expect, anyway), but it DOES work in recovery mode (including stock recovery).

How I ended up fixing everything was as follows:

- uninstall Windows Samsung drivers / reinstall (just reinstalling does not work; you must uninstall first)

- backup all data from phone through adb and stock recovery

- flash FULL WIPE via Odin 3.07

- restore backup if you want

- flash NO WIPE

- good to go

Hope that helps.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Looking for more testers of the new fixed No-Wipe image.

Please verify if you have any of the top 3 bugs listed here: Link

If you do, please PM me and I will give you the link and details.
[Verizon Samsung Galaxy S III] cam1pbell:
I'm running k3 what I've noticed is when I'm downloading a video, watching a video -not off the web. Anything that has to do with media or downloading my phone gets hot. It got up to 108 so far. And my phone never gets hot. Plus battery doesn't last as long. My signal is better. So far j1 is the best. But I had a lot of dropped calls using j1
[Verizon Samsung Galaxy S III] open1your1eyes0:
Just received quite a bit of positive feedback from this new fixed No-Wipe image. A few more confirmations and I shall have it posted for you guys. :good:
[Verizon Samsung Galaxy S III] FAUguy:
I have those bugs #2-4. The Help app I disabled for it to stop popping up.

Also the Calendar app not syncing with Facebook calendar events.
[Verizon Samsung Galaxy S III] open1your1eyes0:
PM sent
[Verizon Samsung Galaxy S III] open1your1eyes0:
Okay guys, after much feedback I have determined that the new No-Wipe image is now fully working as intended and you should be able to apply it the same way you flashed all leaks before with the same three steps but this time using the new FIXED link I have posted. If any of you have the "Help" app disabled please re-enable it before flashing as all previous bugs have been fixed and you should be able to use it properly. Refer to OP FIXED link for K3.

This will fix all of the following bugs below and maybe a few more that gone unnoticed before:

Lock Screen help text not going away even after swiping the action multiple times (Example)

T9 Trace feature (basically Swype) on the official Samsung keyboard does not work at all

E-Mail app (not G-Mail) is always black background even with power savings off
[Verizon Samsung Galaxy S III] Conagher:
What happened to the voice (microphone) to text button on the keyboard that was in ICS? I started liking that feature a lot after using it.

I noticed it's not there after installing your earlier image a couple weeks ago.

Thanks for all your hard work :cool:
[Verizon Samsung Galaxy S III] fanto3k4:
Awesome. Can I Odin this over K3 Wipe version?
[Verizon Samsung Galaxy S III] FAUguy:
Been downloading the Fixed K3, but is going really slow, I guess from heavy load.
[Verizon Samsung Galaxy S III] Ryno77:
Flashed over k3 with no issues. Thank you for all of your work on this! Will report back after running the fixed version for a while.
[Verizon Samsung Galaxy S III] aigochamaloh:
Flashed over the old K3 no problem as well. I, for one, liked the dark email background a lot. Was going to keep using the old version but noticed that the media process was draining the battery on my phone. I never had any of the other bugs listed though.
[Verizon Samsung Galaxy S III] Ryno77:
No swiping okay for a missed call or text with help enabled. This is not bad but the bubble when you miss a call or text no longer shows up on the lock screen..... I could care less about this, just something I noticed.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Should be possible but not much point as you shouldn't have the bugs if you flashed the Wipe version. This is basically a fix for the old No-Wipe as well as properly being able to use No-Wipe the first time.

The dark background is actually a bug carried over from ICS power-saving mode as Samsung intends it to be white. Just FYI.

For one reason or another Samsung/Verizon intended to remove the lockscreen missed notifications with Jelly Bean. I missed them as well but it makes sense now why that lockscreen text didn't go away before because that notification is not supposed to be there so it doesn't know how to clear it. Basically it's running as it should now. At least that bug is gone.
[Verizon Samsung Galaxy S III] BigErnM:
If you use root explorer to look in system/csc you should see a file named customer.xml. You can rename it to something else or just delete it. Some people don't have this folder, but this is what fixes the notification bubbles for me and on several of the TW JB roms.
[Verizon Samsung Galaxy S III] open1your1eyes0:
The CSC folder was actually missing because of my original No-Wipe images. The one I posted today should fix it.
[Verizon Samsung Galaxy S III] kazarp:
Same here. Everything seems to be working well in the newest build. Thanks!
[Verizon Samsung Galaxy S III] Snakehn:
I thought it was a bug, takes time to get used to.
[Verizon Samsung Galaxy S III] fanto3k4:
I currently have the stock K3 WIPE version. Not the NO WIPE. Can I ODIN the NO WIPE FIXED over the K3 WIPE?
[Verizon Samsung Galaxy S III] skrypj:
is it just me or are people getting mismatched MD5's on the k3 no wipe download? Ive tried twice and both times its giving me a different MD5 and ODIN wont load it.