yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] DaveyBB:
If you are going to root, then do what Creepy suggests. If not, the disable you mentioned will work and then it is just a matter of enabling from the same place when/if you want to use the app. Once you disable an app, it goes to the bottom of the list, so check there if you want to enable something. Not all of the boat will have the disable option, but most should.
[AT&T Samsung Galaxy S II SGH-I777] ferrocene:
Yeah today my wife got this text 30 min before I did and we're on the same plan! And my phone was purchased early on launch day, one of the first sold in California. And my number comes first numerically. Not sure what method they use. I think I was one tower away physically, maybe that's it.
[AT&T Samsung Galaxy S II SGH-I777] funtapaz:
Is there a way to bypass the tether/hotspot check when rooted? I want to switch to the stock ROM, but I can't justify giving up tethering.
[AT&T Samsung Galaxy S II SGH-I777] corruptsoul:
My entire family uses these phones. I am trying to update from 2.3.6 to this new 4.1.2. I plug the phone in for Kies and it tells me there's an update. I start the update, and all is going smooth until:

After this, the window closes and KIES freezes and nothing happens on the phone. The phone SHOULD be copying over the upgrade files, but does not. Rooting is not an option and neither is wiping. They'd rather stick to 2.3.6 until they get a new phone than wipe everything.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I am not aware of any way to upgrade without wiping other than Kies. You can of course flash the new JB stock firmware with Odin, but if you try that without a wipe, I'm very skeptical of the results.

Did you try Kies upgrade with only one phone, or more than one. If only one, you might at least try another to see if it will complete.
[AT&T Samsung Galaxy S II SGH-I777] corruptsoul:
I've tried with the same phone but two computers. Both the same results. No dice. Both computers were running Windows 8. I was going to try with Windows 7 but I doubt the results would be the same. USB debugging doesn't need to be enabled does it? I wouldn't think it would matter through KIES.
[AT&T Samsung Galaxy S II SGH-I777] soxfannh:
I had the same problem under Windows 7 and then ran Kies as admin and it worked.
[AT&T Samsung Galaxy S II SGH-I777] BGood2:
Computer made the difference

My powerful 64-bit Win 7 desktop running Kies kept failing on this update to 4.1.2. Finally, I installed Kies on my 32-bit Win 7 netbook. Installation of Kies and its updates took over 30 minutes. Then actually upgrading the phone was very slow (another 30 minutes or so), but it did upgrade on the first try. So changing computer *might* help.

Now if I can figure out what to do with my battery draining so much faster on 4.1.2, I'd be really, really happy. But even with poorer battery life, I'm much happier with 4.1.2 that I have been with any version since the original 2.3.4 that it came with. It's smooth, improved, and much more polished.
[AT&T Samsung Galaxy S II SGH-I777] sleeperg:
Rooting 4.1.2

I did the AT&T/Kies version of upgrade to 4.1.2 instead of doing it manually using ODIN and Samsung stock UCMD8. Now no longer rooted. Anyone know how to root a SGH-I777 running 4.1.2? :confused:
[AT&T Samsung Galaxy S II SGH-I777] Eternalty:
Gotta search dude. It's just a few pages back...

http://xdaforums.com/showthread.php?p=37508806

A little searching goes a long way.
[AT&T Samsung Galaxy S II SGH-I777] ou812bkewl:
Disable real-time protections in your antivirus program. I had the same issue in Windows 7 with Microsoft Security Essentials and have to disable it every time.
[AT&T Samsung Galaxy S II SGH-I777] sleeperg:
species Unesca

Many thanks brandonarev. Rooted it and updated the kernel using AJK 2.0.5.
[AT&T Samsung Galaxy S II SGH-I777] mfisch@mfisch.com:
heimdall syntax

I see a few messages looking for instructions to flash the JB ROM with Heimdall.

The Samsung firmware package on offer here can't be consumed directly by the Heimdall GUI which expects meta-information, however the below syntax will work to get you back to JB stock. Heimdall should be in your run path on Mac OS X after you install the heimdall suite, although you'll need to extract the component images from the tar.md5.7z file using something like Keka (Mac OS X GUI compression tool). You may need to manually remove md5 from the decompressed file name to get Keka to recognize it as a tar file.

When connected in download-mode:

heimdall flash --BOOT boot.bin --CACHE cache.img --MODEM modem.bin --KERNEL zImage --FACTORYFS factoryfs.img --HIDDEN hidden.img --PARAM param.lfs --SBL1 Sbl.bin

* A note here, if you've re-partitioned your internal flash these images may not "fit". Getting back to a stock filesystem layout is beyond the scope of this post. A repartitioned "internal sdcard" is not a problem, nor is it a problem if you've formatted any of your partitions previously. If you don't know what re-partitioning is or how to do it, it's unlikely you need to worry about this.

** Usual note about how this tool can softbrick your phone if you don't really know what you're doing.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
You dont need Keka. Just remove the MD5 at the end and double click. Voila extracted.

Sent from my crack smoking SGH-i777
[AT&T Samsung Galaxy S II SGH-I777] sciguy125:
I didn't see anyone else post about it, so I decided to check on the super brick bug. I downloaded the source from Samsung (http://opensource.samsung.com/). I believe* that the stock JB kernel has been patched, so factory resets should be safe. I diffed it against the same file from the AJK kernel and there's only superficial differences.

stock kernel, drivers/mmc/host/sdhci.c line 2639

mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE;

That's the relevant line of code and is correct.

*I'm new to poking around in Android code, so I may be wrong. If you do a factory reset and it bricks your phone, don't blame me.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
The brick bug was only in the ICS roms. Its been fixed for quite awhile on the i9100 side.

Sent from my crack smoking SGH-i777
[AT&T Samsung Galaxy S II SGH-I777] NBA Brawler:
Just to be sure, there's no multi window in the update right?
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Nope. No ripple effect either but it can probably be enabled like it can on the i9100. Ill have to try it this afternoon..

Sent from my crack smoking SGH-i777
[AT&T Samsung Galaxy S II SGH-I777] laut8:
Thank you, Just to add to this, Framaroot version1.4.3 did not work. I used a previous version (1.4) and was able to root. Cheers
[AT&T Samsung Galaxy S II SGH-I777] Whizzpopper:
Could someone please help me out and upload your stock kernel sec_touchkey.kl ? If you don't know where it is, it's here: /system/usr/keylayout/

I switched back to stock kernel but my home key isn't working! Thanks!

Should anyone encounter this issue, the fix is easy: there is no sec_touchkey.kl! You just delete the sec_touchkey.kl, reboot and you're good to go on the stock kernel.
[AT&T Samsung Galaxy S II SGH-I777] rickychew87:
Working CWM?

Is there any working CWM recovery for this device on I777UCMD8 firmware?
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Look in mr-cook's thread for Cooked rom. Post #1 has the rom, post #2 has stock plus root plus AJK kernel, and post three has just the AJK kernel. The easiest would be to flash the rom. The AJK 2.0.5 no swap kernel is the only way to get CWM recovery on UCMD8 as far as I know.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
I'm sorry to essentially ask the question you just answered but are you saying that I could download the AJK kernel in that link. Then go into 3e recovery and flash it and I will have root?
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Yes and No. You can download just the kernel from that thread, but you cannot flash it from 3e recovery. I was thinking that he provided Odin flashable .tar files but as I go back and look at the thread, it appears that they are all CWM flashable zip files (although he doesn't specifically say.)

To install the kernel, you will have to root first, using framaroot. Then install Mobile Odin Lite or Mobile Odin Pro and use it to install the kernel. You will download the CWM flashable zip from the thread and extract the zImage from it, and use that in Mobile Odin. (Mobile Odin will not recognize the zip file.)
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
I have multiple times. Framaroot DID NOT work for me. :confused:
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Sorry to hear that.

I don't believe there is any other way to root UCMD8. So your alternative would be to flash one of the other stock plus root packages, maybe UCLL6, then install Mobile Odin and a custom kernel. You could then go back to the Cooked thread and flash one of his files using CWM recovery.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
Please pardon my ignorance, but how would I go about doing that without first having CWM recovery? I'm trying to NOT trip the "flash" counter.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Go to the OP of this thread. Follow the guide in the OP.

Flashing a custom (non stock) kernel using Odin or Heimdall is the only thing that will trip the flash counter. You can flash a stock kernel with Odin or Heimdall and it will not trip the flash counter. So, when you flash the stock plus root package with Odin or Heimdall, it does not trip the flash counter, since root is injected into the factory file system, and the kernel is bone stock.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
It would appear I've forgotten as much as I've learned, it turns out I already have that .zip I just forgot what I used it for. I've been collecting various files for my phone in case I might need them and again and the dev no longer has it available. I honestly thought it might be a whole new ball game with 4.1.2. In any case, thanks for reminding me, I'm squared away now.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
BTW, are there similar tools to be found for the Note and S3? There's a possibility I'll be putting CM on my parents phones.
[AT&T Samsung Galaxy S II SGH-I777] galaxy-s2-quest:
I'm also frantically looking for an answer to this question, does anybody know if there's a solution?

I didn't realize that rooting won't enable hotspot on 4.1.2 and am up the creek without a paddle now that I've updated, but I don't want to have to bend over for AT$T if there might be a fix on the horizon...
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
I can't say I know one way our the other regarding a "fix" for what you're asking about, but I've successfully tethered using CM 10.1, Task650's AOKP and SHOstock3. I don't know about Mr. Cooks debloated stock ROM but I would guess yes.

If tethering is of utmost importance to you, it might be time to jump past simply being rooted and try installing a custom ROM.
[AT&T Samsung Galaxy S II SGH-I777] galaxy-s2-quest:
Not tethering, but enabling the wireless hotspot on a stock rooted rom. Before 4.1.2, all you had to do was root a stock rom to enable the wireless hotspot. Now, it seems to check with AT&T to see if you've paid for it. I've been running various custom ROMs on it for almost 2 years but just loaded the new 4.1.2 on it because I loaded it on my wife's GS2 and it's excellent.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Well, AT&T doesn't want people using that feature, obviously, since they eliminated it's use in the 4.1.2 stock rom. I doubt if anyone has even tried to get around it in the stock rom, since anyone with any interest would be using or building a custom rom, and they pretty much all have that feature built in.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
SHOstock3 my friend. I know it's not exactly like AT&T stock, but it's pretty darn close and you can use the phone as a "hot spot". Just realize that it's called "tethering" in that ROM.
[AT&T Samsung Galaxy S II SGH-I777] galaxy-s2-quest:
Thanks for the responses, okay I'll check out that shostock but I really want it to sync with Kies if/when I get an s4.
[AT&T Samsung Galaxy S II SGH-I777] SteveO390:
I'm pretty sure SHOstock actually does sync with Kies. It's a TW based ROM after all. Flash it, try to sync it with Kies and see if it works, I think it will.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Is it just mine or is the lock screen security broken?? No matter what I set it to, its always got the swipe enabled and whether its set to PIN/pattern/whatever it only works like 1/3 of the time. Usually right after I swipe theres my home screen wide open...

Edit: nvm.. Guess they changed the default option to lock like 10 minutes after the screen goes off. Scrolled up and theres the old 'after 10 or with the power button' option!

Sent from my crack smoking SGH-i777
[AT&T Samsung Galaxy S II SGH-I777] lizhida30:
kkkkkkkkkkkkkkkkkkk

oloooooooooooooooo
[AT&T Samsung Galaxy S II SGH-I777] jball:
possible

I was on AOKP 4.2.2 rom with my i777 s2 b4 buying my i337 s4 .after doing the regular with my s4 we all do.I started playing with my s2 again and felt like doimg the official update 4.1.2 jelly.I didn't use kies or even desktop odin, I used mobile odin pro so I can keep root using the everroot option.I lost cwm and didn't want to try using a gingerbread kernel I case I borked my phone.I tried out rom manager and flashed the latest cwm touch and well It worked for me .
[AT&T Samsung Galaxy S II SGH-I777] dphuff:
Official 4.1.2 --> CM10RC ?

Looks like there's a Release Candidate for CM10 for my i777. I'd like to move back to CM from the official 4.1.2 I installed with Kies awhile back (the AT&T / Samsung 4.1.2 has some battery life, and occasional lock-up, issues for me).

I used Creepy's excellent "How to Flash Custom Binaries Without Ever Incrementing the Flash counter!!" instructions to go from the phone's orig Gingerbread to CM9 earlier, and it worked w/o a hitch. Can I just try that with the current ROM ? or do I need to use the "return to stock GB method" before that ? (i.e. are there any issues I should be aware of with getting my i777 with this ROM to state where I can do a CWM flash of CM10 :confused: )

Thanks!
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Are you still rooted, or did you lose root when you upgraded to 4.1.2?

If you have root, then you can install Mobile Odin Lite or Mobile Odin Pro and use it to install the AJK kernel that works with stock 4.1.2.

If you don't currently have root, you should be able to root using Framaroot.

After you have the custom kernel with custom recovery, you can then flash your desired firmware.
[AT&T Samsung Galaxy S II SGH-I777] dphuff:
Not rooted, but tried Framaroot and the "Aragorn" method worked just dandy. Read the thread here on the AJK kernel and the install doc leaves me with a few concerns:

"After recovery has been restarted, go into kernel specific options and Reset ExTweaks profiles" Is that a menu option or a "manual" thing where I have to know what I'm doing ?

"Fix permissions in recovery" Again, is that a menu option or a "do it yourself, because you should know what this means" sort of thing ?

Just need to know if I need to go off and research some more, or if these actions will be fairly obvious once I get to them. Your orig guide to installing customized ROMS w/o incrementing the flash counter was so straight-forward I didn't have such questions. Just followed the appropriate steps and voila! (basically, all one has to do with that guide is just be able to read carefully and follow instructions) So I guess I was trying to see if what I want to do now could be handled with a similar lack of "WTF ?!?" from me :D
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Both of those are accomplished in the custom recovery with menu options. I'm not using that kernel, but I would assume that the first one would be under a menu item that is called "kernel specific options" and "Fix Permissions" would be found in the "Advanced" menu. But just look around in recovery after you have rebooted to it, and you will find them.
[AT&T Samsung Galaxy S II SGH-I777] junwuu:
The update sucks my battery, it only last between 4-5 hours.
[AT&T Samsung Galaxy S II SGH-I777] nathan_42594:
can anyone help me please? .. after downloading the firmware upgrade a prompt will pop up and says " failed to run firmware upgrade. unknown error occured. i realy want to upgrade my device . please anyone help me :(
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
You can flash the stock firmware using Odin, but it isn't exactly the same process as upgrading via Kies, in that you will need to perform a wipe data/factory reset which will mean you will lose all installed applications and user settings.

Loot at this thread from earlier today for the basics, and if you have questions feel free to ask.
[AT&T Samsung Galaxy S II SGH-I777] vinek14:
thanks men :laugh:
[Defy Q&A, Help & Troubleshooting] lucasfpaixao:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).

I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://xdaforums.com/wiki..._Bootloader_v7

I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).

It results in a Bootloader error (Err:A5,70,00,00,23)

UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).

I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz

But I still want to install the CM 7.2.

OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar

Andoird version 2.3.6

Kernel version

2.6.32.9-ge281b6e

hudsoncm@il93lnxdroid51 #1

Build number

4.5.1-134-DFP-231

I already checked the MD5 of the downloaded zip files.

I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.

Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.

What is missing?

Thanks in advance!
[Defy Q&A, Help & Troubleshooting] bufa:
I have the same problem! but with a Defy (green lense)
[Defy Q&A, Help & Troubleshooting] hotdog125:
I just got the same problem yesterday. The bootloader screen came with with an error. I FLASHED AN SBF, AND THEN AFTER INSTALLING SNDINIT, I FORMATTED SYSTEM AND DATA TO EXT3 USING BOOTMENU. NOW CM7.2 RUNS FINE.
[Defy Q&A, Help & Troubleshooting] mmrakk:
/tmp softlink

it sounds to me that it can be a problem with /tmp softlink - you need to remove the softlink and create /tmp as a new directory ( I can't post links yet, but if you search for "defy+ /tmp softlink" you get a nice guide as a first result) Hope that help!
[Defy Q&A, Help & Troubleshooting] lucasfpaixao:
workaround with partitions

Thanks for the tip. Maybe the problem was the file system. Yesterday I tried a lot of times with other CM7.X resulting in the same problems. I get bored and needed to solve as soon as possible this phone (that is my mom's). So I tried CM10. It worked without problems as worked in the very same phone (mine).

So I think hotdog125 is right but I haven't tested formatting the partition to ext3 yet. I searched on the web about CM7 partition support but I cannot find any secure information about it.

I will remain my mom's phone in CM10 by now. It's working well.

Does anyone know how a documentation about CyanogemMod versions and partition support?
[Defy Q&A, Help & Troubleshooting] ionix2727:
To install CM7 u need SndInitDefy 1.4.2

Your problem is that you ar using the SndInitDefy_2.3.apk that is for ICS and JB i had the same problem when i flashed my MB525 whit CM 7.2 By jordan i was lucky that i backed up my phone and was able to restore the stock rom whitout RSDLite. After i recoverd to stock rom i uninstalled SndInitDefy_2.3 and installed SndInitDefy 1.4.2 and i was able to flash CM 7.2 whit no problem hope this information help's you :):good:
[Defy Q&A, Help & Troubleshooting] lucasfpaixao:
Thanks a lot for the answer. I think you are absolutely right.

As far as I know there is no information about bootloaders and CM 7/9/10 compatibility. Does anyone know some place about it? It should have a documentation to prevent problems like this.
[Defy Q&A, Help & Troubleshooting] thekguy:
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.

Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom

The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.

The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.

And lastly, formatting to ext3 is required only when downgrading from jb builds:)
[Defy Q&A, Help & Troubleshooting] lucasfpaixao:
thekguy, thank you for the explanations.

I've read something about kernel and ROM compatibility. But, as I remember, this is a problem for old Defy phones with green lens and not for Defy+ phones. So I never care about the kernel version and also the guides for installing custom ROMs never report compatibility of the kernel version for Defy+ users.

Where we can find trustable documentation about ROM and kernel compatibility?
[Defy Q&A, Help & Troubleshooting] droid_<3er:
Being on BL7 does not mean that one cannot use CM7, but it may mean that CM9/10 compatibility is hampered and does not guarantee that it will work. Is his mother's Defy+ also on DFP231? If not, then that may explain it...

And do not use MB525 CM7 builds on a Defy+, there's a different kernel. CM10 works because it uses 2ndboot, but CM7 relies on 2ndinit, therefore the GB kernel is of importance. You cannot downgrade from a GB kernel from a BL7 stock ROM to a froyo MB525 kernel.
[Defy Q&A, Help & Troubleshooting] thekguy:
Since defy and defy+ do not share a stock kernel by default(a defy+sbf can be installed on defy) this issue arises. You have to use the defy+ builds for gb roms and for newer roms there's no such problem