yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] SPatMobile:
I'm a little embarrassed to post this but don't want to waste anyone's time. It is totally bricked but I know why.

I just noticed I downloaded a rom from the i777 forum, and my device is a i727.

Oooops! Guess I'm learning a valuable $50 (plus shipping) lesson.

Thanks for the help, my phone is off Mobile Tech.
[AT&T Samsung Galaxy S II SGH-I777] knightsh:
Still might not be hard bricked. Mine did this a few weeks ago for no reason. Had been running fine then wouldn't boot one day. Wouldn't boot at all. Could not get into recovery.Nothing. Only thing that worked was connecting through Odin. Had to then flash original Gingerbread. Phone then booted fine. I have since rooted again and I'm now dual-booting SHOstock and Rootbox. Try Odin first.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I don't really know much about the I727 architecture, but I seriously doubt if your device is hard bricked. You should still be able to get into download mode via the normal procedure (maybe, or if not with a usb jig) for your phone, and then flash a good I727 rom, I believe. There are no bootloaders or partition information, or param files in any of the I777 roms, as far as I know, so there's really not much of anything that can do serious damage.
[AT&T Samsung Galaxy S II SGH-I777] snipe2nite:
Try getting in to download mode by With your phone off and unplugged. Enter download mode by pressing and holding the power and volume down buttons and plugging in the USB cable before the lights blink. I don't know it will work on i727 but worth a try..GL

This is a good thread to help you read all you can....

http://xdaforums.com/showthread.php?t=1652398
[AT&T Samsung Galaxy S II SGH-I777] SPatMobile:
Interesting. Well I suppose it is possible I had a legitamite hardware failure completely unrelated to the software issues. I did some searching around for hardware failures instead and found some very similar cases to this.

Exactly what happened. I downloaded the wrong rom, rebooted in cwm, wiped, then flashed the rom. It went successfully and I rebooted from cwm then during boot right after the samsung logo all the lights went off and the screen went black. I left it like this for about 45 mins to an hour and had dinner just in case it was still doing something. The battery was fully charged at the time I started the procedure, and I have tried using the wife's battery to make sure mine wasn't dead. My battery also functions without issues in her phone. I had done this successfully multiple times on my phone before and tablet, and successfully flashed two or three different roms on my wifes phone last night.

I tried every suggestion mentioned, and followed the guide as well. There is no glimar of life. If this is hardware I might be wasting my money with Mobile Tech but I suppose we'll know for sure soon. Phone is shipping off today.
[AT&T Samsung Galaxy S II SGH-I777] patriot720:
Have you tried a jig?
[AT&T Samsung Galaxy S II SGH-I777] exenocap:
you're doing the right choice, mobile tech is your best bet
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
OP got his answer. And his device is an i727. Let's let this one die before we attract trolls :p
[AT&T Samsung Galaxy S II SGH-I777] moneyover:
Ya good idea :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] SPatMobile:
In case anyone was interested it looks like the device was a hardware failure.

"Unfortunately, I was not able to repair your device. The device's onboard EMMC controller was in a non-responsive state. It is advised to try out warranty replacement if possible or to search for a parts device and use it's mainboard for the swap."

*edit - I tried to use the thanks meter for everyone, but thanks for all the help!
[AT&T Samsung Galaxy S II SGH-I777] paulfrankie:
Never was really a samsung fan until I got my i777. Blackjack? wth was that? Browsing with opera was off the hook though so the phone grew on me. Now I tried simply flashing a different i777 kernal because ICS constantly freezes and the phone bricks? Sent it to Mobile Tech Videos.... EMMC is in non responsive state for me too wtf Samsung? Had my nexus one twice as long and flashed twice as many times and its still rockin. Now will definitely think twice before going Sammy.
[AT&T Samsung Galaxy S II SGH-I777] karate104:
Did you wipe in ICS's stock recovery before flashing that different kernel? Because there's a well known brickbug with the I777's stock ICS kernel, where if you use it to do anything before you flash custom kernels, it'll mess up your EMMC and brick your phone. If this is what happened to you, I would suggest you do more reading before flashing anything again; different phones operate differently, and even if you're a pro at flashing stuff on a galaxy nexus that doesn't mean squat when it comes to flashing an I777. I don't mean to be harsh or offend you, I just want you to know that reading more is always a good idea, and that there's a chance that it wasn't Samsung's fault you wound up with a bricked device.
[AT&T Samsung Galaxy S II SGH-I777] Chr0nicDreamz:
He could always try the jig to kick it into download mode. Read up about it. It may save you some money.

HTC = Hate The Consumer
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Mobile tech will fix ya :p but in all seriousness, phones are way different from model to model. As previously stated. Read a lot before doing anything. may Atrix is way different than this phone,.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL

Let us know if it's a lockdown flash...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Did you remove Flipboard or install an update?

You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Here you go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
tried that still the same error message need some help please....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?

If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.

Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I"m a bi confused too, but from a different perspective.

I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
Odin back to pure stock working fine.. some of my apps fore close though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Anyone wanna pull just the baseband for cwm zip?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aridon:
Extracted and flash with mobile Odin without issue.

People that list their imei need to post their clockwork version and method in the thread dedicated to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vancraft:
How di you get it fixed? I have the same symptoms you were having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sentry07:
OP per your reply in the the other thread can you kindly make a mod for only thether?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Yeah, just added one with cell standby and tether. I can't see why you wouldn't want the cell standby fix, too. It's in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sentry07:
Thank you.

EDIT: BTW script still says that it includes autobrightness, you need to update the ui-print ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Oops. Yeah, forgot that. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznguy84:
So I'm currently rooted on stock rom. I used ODIN to load CWM Super User 3.0.7. Am currently running busy box pro and I reset my flash counter with Triangle Away from Chainfire.

I've attached a picture of my current device specs.

Would it be worth it for me to update right now? And if so, which download one would it be?

I'm comfortable with all the install methods, but still a n00b on a number of things. (Went from an iphone :( to an S3 :) )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Tough call. I'm running LG1 (of course) and haven't personally noticed any "oh wow" kind of improvement. One user reported that switching between two calls using the LEM modem would drop one of the calls, while that was fixed with the LG1 modem, but I couldn't reproduce it. So, really your call. Personally I like to be on the latest version, but I don't have a good reason for that.

If you do decide to upgrade, you have three ways available for doing it:

Install OTA Rootkeeper. Revert to stock recovery. Install the OTA through the phone, then reflash recovery.

Use Odin to flash the root-injected LG1 ROM.

Use the CWM zip in this thread.

If you choose one of the the first two, you'll lose Universal Search, but you can grab the old one here and replace it using Root Explorer or something.

I'm also not sure how to advise you regarding which package from this thread to flash. I personally flashed the whole thing, including the bootloader and the kernel. Some people feel that AT&T is evil and has included something nefarious in the bootloader and have therefore decided not to flash that. I personally haven't had any problems with the new bootloader.

When making your decision, you might want to think about the risks for losing your IMEI. There are threads here and here about it. The summary is that sometimes your phone will lose the IMEI and you'll have to send it back to the carrier or manufacturer for replacement. Nobody really knows why this happens or how to back up the IMEI and restore it if it does. Most of the people who have lost their IMEI have lost it after flashing something with CWM, but I'm not sure if that means flashing with Odin is safer or it's just an artifact in the data because most people flash with CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznguy84:
Hmmm...at this point it seems like it might not be worth the risk of losing my IMEI as I really can't be without my phone.

If I did decide to though, in your opinion, would the safest route likely be to:

1. Restore to stock (I killed a lot of the proprietary bloatware already I think)

2. Load the Root-injected Rom with OTA Update

3. Go about using my phone, business as usual

Also, couldn't I just update the modem as that seems to be the, if any, only beneficial piece of the OTA update?

Thanks so much for your help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Personally if I were you, I'd flash the root-injected LG1 ROM, replace the Google Search widget, then freeze (not remove) the bloatware. The reason to freeze is that it doesn't prevent a future OTA from succeeding. I found I could apply this OTA with the bloatware frozen and when I was done, it was still frozen.

Take a look at the list of changes in the OP of this thread. There are lots more than just the modem and it's hard to say if that's the only beneficial piece or not. Plus, there was at least one report of someone flashing the modem and losing their IMEI, so I don't think it's necessarily any safer than doing everything else.

I flashed the entire thing myself. I do use some of the "bloatware" and I want the updates to that. There are updates to other pieces, such as core libraries and some wifi binaries. I want the updates to those, too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznguy84:
I will do just this.

Can I flash the root-injected LG1 ROM directly using CWM after I restore the framework or do you think I should restore it to 100% stock first?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The root-injected ROM is flashed with Odin. It will replace your recovery and your entire ROM, so there's no need to restore to LEM stock, first. After you flash it, you'll need to follow the instructions to add CWM back (or flash it again with Odin or use ROM Manager).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznguy84:
Understood. Will probably do this later today. I will update how it goes! Thank you again in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznguy84:
Thank you again! Loaded with everything fine. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
Tried flashing the non boot loader version and in getting error abort 7 blah, blah, blah.

Im using the CMW version linked to in post, don't have any mods to framework.

Any ideas what I'm overlooking?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
This is likely one of a few things:

You have signature verification turned on in CWM.

You have removed or modified one of the files the OTA is trying to patch.

If it's the first issue, just turn off signature verification in CWM. Otherwise, please post the entire error message.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamanaco:
I'm about to install the Tether and Cell Phone Standby MODs in the OP and wanted to backup the files it modifies. Just to clarify, this MOD only modifies framework-res.apk and SecPhone_ATT.apk... right?

Another question a bit off-topic... In my old Captivate I used an app called Android MaketAccess version 1.0.6 to bypass some AT&T market restrictions... Is this app still useful and compatible with the S3 LG1 or is there something else I should be using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That mod only modifies framework-res.apk. The no increasing ring mod modifies SecPhone_ATT.apk and deletes SecPhone_ATT.odex.

I believe it still works with the S3. I personally never had to use it with my Cappy and haven't had to with my S3 either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamanaco:
After applying this Teher+Standby MOD I noticed that the Device Status went from Normal to Modified. I'm assuming that this was caused by the modification to the framework-res.apk and can be reversed by replacing the modify .apk to the original and by setting the correct permissions to the file.

Another quick question... In the modified ROM of my Captivate I have extended options in the pull-down taskbar which included a WiFi AP toggle. Is there an app or a way to create a Home Screen shortcut to enable tethering without having to go to settings?

Thanks again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I assume so. I haven't worried about the modified status since I have BusyBox installed and that is enough to trip it. Plus, I'll be flashing stock before doing a warranty return and that will reset the status.

I don't know how. I'm sure there's an app to do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
What's the benefits of having the updated bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Went a few pages back and didn't see this asked, sorry if it's been asked a thousand times before. Can I flash just the modem if I'm not on the stock rom. Thanks, sorry if I'm trolling yall ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
I flashed just the modem, I'm on kyanROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 21cdb:
I flashed it with TWRP while I was on JB AOKP. Worked fine. :) I'm on WanamLite now, everything still good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I don't know. Maybe they fixed some bugs? I haven't seen any reason not to flash the updated bootloader yet. I've flashed it and not had any problems, but I'm still on stock LG1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krips2003:
I purchased my phone on July 24th. I didn't root but I didn't want to update the newer firmware because of screwed up Google search. Then I found the below thread in development section. Followed the procedure. Got root, firmware and kernel updated. No apps, widgets or settings changed. copied the old Google search apk as mentioned in the thread. Everything working fine.

http://xdaforums.com/showpost.php?p=28019751&postcount=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Tried flashing the bootloader with twrp and it failed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Thanks for the report. I've fixed the zip file. It works now (tested with twrp).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Still no go. I downloaded the one for ucalg under the other pieces section its like 1.1 mb it fails.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
In what way did it fail? What did the log say?

EDIT: Make sure you turn off signature validation, too. I haven't figured out how to sign it in a way that TWRP (or CWM) things is valid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Thats off, maybe because I'm on kyanROM. It's giving me an error 7 when going into build prop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Yeah, that may be it. The update script has a check to ensure the phone is AT&T and I think kyanROM is based on a Canadian ROM. You can modify the updater-script to remove or comment out the assert lines at the beginning of the file. If you're not comfortable with that, I can do it tomorrow. I'm not near my computer right now.

EDIT: Please try flashing the attached file. It prints out the build.prop values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Yeah his is based off the Canadian so I'm giving aokp jellybean a go, I should be able to do the update with this ROM?

Edit: It failed on jellybean as well then I edited the file you suggested and it looked like this when I got done.

mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");

show_progress(0.100000, 0);

ui_print("Update sbl2 ota");

assert(write_backup_sbl2("/dev/block/mmcblk0p3", "/dev/block/mmcblk0p19"));

assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p3"));

assert(erase_backup_fota("/dev/block/mmcblk0p19"));

ui_print("Package sbl2 Done.");

ui_print("Update sbl3 ota");

assert(write_backup_sbl3("/dev/block/mmcblk0p4", "/dev/block/mmcblk0p19"));

assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p4"));

assert(erase_backup_fota("/dev/block/mmcblk0p19"));

ui_print("Package sbl3 Done.");

ui_print("Update aboot ota");

assert(write_backup_aboot("/dev/block/mmcblk0p5", "/dev/block/mmcblk0p19"));

assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p5"));

assert(erase_backup_fota("/dev/block/mmcblk0p19"));

ui_print("Package aboot Done.");

ui_print("Update rpmfw ota");

assert(write_backup_rpm("/dev/block/mmcblk0p6", "/dev/block/mmcblk0p19"));

assert(package_extract_file("rpm.mbn", "/dev/block/mmcblk0p6"));

assert(erase_backup_fota("/dev/block/mmcblk0p19"));

ui_print("Package rpmfw Done.");

ui_print("Update tz ota");

assert(write_backup_tz("/dev/block/mmcblk0p8", "/dev/block/mmcblk0p19"));

assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));

assert(erase_backup_fota("/dev/block/mmcblk0p19"));

ui_print("Package tz Done.");

show_progress(1.000000, 0);

unmount("/system");

The flash was successful used root checker from market to check my boot loader version and it reads the ucalg boot loader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Perfect!

I just made those changes myself and uploaded packages without the checks, with links in the OP, but you beat me to it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Your on top of it, keep up the good work!:cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Finally had a need for the wifi hotspot, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmirrow:
problem

Getting the following error message: Currently at stock rooted I747UCLEM. Flash counter is set to 0, and I havent frozen anything. Tried loading the one without bootloader, and the full, get the same message both times. Any ideas?

assert failed: apply_patch_check("EMMC:/dev/block/mmcblk0p7:5710080:f7cab8e921c9fa9e03332678ca8e415325f176a29:5712128:fb95a5d43d651be3972f96e8d6d2eb181a9fc66b", "fb95a5d43d651be3972f96e8d6d2eb181a9fc66b", "f7cab8e921c9fa9e0332678ca8e415325f176a29")

Error in /sdcard/I747UCALG1_OTA.zip

(status 7)

Installation Aborted.

Thanks guys. Also, this was answered im sure but i couldnt find a clear enough answer. Can i do the AT&T software update? What would I have to do after I applied it that way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
/dev/block/mmcblk0p7 is the kernel, so you must have a non-stock kernel installed. You can flash the "no bootloader no kernel" zip. Then flash the bootloader zip if you want the LG1 bootloader.

You would have to flash the stock recovery to apply the OTA from AT&T. And easier alternative is to flash the root-injected LG1 ROM from here:

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

You will lose Universal Search, but you can install the Google search widget from the same thread to restore it. You will not lose your apps or settings and that will install the full ROM including kernel and bootloader regardless of whether you're already on unmodified LEM.