yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
The 1.5.14 version of USB Driver for Samsung Phones is fine. Any earlier version is probably fine also, but you will need to reboot the computer after uninstalling, then reinstall and reboot your computer again. Win7 x64 is fine also, and Odin3 v1.85 is preferred.

You didn't say if you got the BSOD on the pc or on the phone. It is usually a term that is associated with windows on the pc. You also didn't say if the Odin flash completed and if you got a pass or fail.

At this point you need to pull the battery to turn the phone off, and start over.

Make sure you have a good install of the usb driver, with reboots as above.

First try to enter recovery mode by holding down all three buttons, vol- vol+ & pwr. If that is successful, do a wipe data/factory reset and then reboot. If the phone boots up normally, then you're back in business.

If you can't get into recovery, or if you get recovery but the phone does not boot up normally, you need to flash again. Enter download mode and do the flash again.

____________________

The following is for reference. How to use stand-alone Odin3 to flash firmware:

Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.

1.) Open Odin on the Windows Desktop.

2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.

3.) Shut the phone off.

4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.

5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.

6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.

7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.

8.) Make sure the check box next to the PDA button is checked.

9.) Click the Start button.

10.) You should see the green progress bar advancing.

Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Thanks for the quick reply.

In my haste during the initial flash, I forgot to capture the logs, but I'm pretty sure it just started getting to "Nand Write Start". It was pretty early in the process. Then my PC had the Blue Screen of Death, (some PFN error). After realizing that I should still have the bootloader intact, I eventually unplugged the phone and then tried to resume it. I got the same error. Then I tried other versions of the USB driver 1.5.5 (uninstalling then installing with reboots), and I believe it gave me the same error. I then also tried it on another Win XP computer, and one instance I got as far as NAND write start, and then ODIN terminated it this time. Again, I didn't capture the log.

However, I did go back to my Win 7 x64 PC and then installed the latest driver 1.5.25, and I did manage to collect the log for that (I'll be sure to do that from now on):

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> cache.img

<ID:0/004> NAND Write Start!!

<ID:0/004> factoryfs.img

<ID:0/004> Complete(Write) operation failed.

Anywyay, I can get download mode again, but I can't seem to get recovery. I instead get a dreaded yellow triangle error message that says Firmware upgrade encoutered an issue, please select recovery mode in Kies & try again. I'm not sure if I'm pressing the correct buttons, but before this process started I was able to get into 3e recover, but it's a tricky sequence to get right sometimes.

Is my problem the image I'm trying to flash? Should I just try to use the one click to UCKH7 since the aborted ODIN flash corrupted my UCKK6?

I was thinking of using Heimdall, but just my luck that their hosting service is doing some maintenance!

Anyway, I'll go through your sequences for ODIN again, but my problem seems to be mostly centered around the driver (especially on the WinXP machine where it won't recognize the device), and on the Win7 x64 I get the Blue screen when any transfer is occurring.

I'll try with your steps outlined above, although I was kind of doing that already sometimes since I seem to recall you posting that somewhere else.

Thanks so much for your help.
[AT&T Samsung Galaxy S II SGH-I777] Teknodad1974:
Make sure you run Odin in administrator mode..!
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
If I am understanding you correctly, your computer interrupted the flash during the first time you tried to flash the stock plus root package. This likely happened early in the flash cycle. (By the way, there is no bootloader in that package.)

One possible result is that you now have a partial flash in one partition of the nand, which is essentially nand read/write corruption. I would start with the following to see if it will clear the problem.

1)Assuming your phone operating system is Gingerbread, go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.

2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.

3) If that is successful you are done. If it is not, then:

4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.

5) Flash the Kernel, as in step 1.

6) Flash the full stock Gingerbread distribution, as in step 2.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Thanks for the detailed instructions. I'll give it a shot. I hope your theory regarding NAND partitions is explaining the weird behavior regarding both my PCs with the USB drivers (x64 Win 7 & XP SP3). If I can't seem to resolve the USB Driver issues and Odin, is it possible to flash the Siyah Kernels with Heimdall? I think their hosting site is back...

Also, as I understand it, if I'm able to successfully flash the kernel it will trip the counter, right? Anyway, it's a moot point since I'm past warranty anyway. I'd be thrilled if I don't have.

Thanks again for all your help!
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Yay! I was able to flash the Siyah kernel after lots of experimentation (long story short, I gave up on the Win7 x64 machine, and tried the XP SP3 again, and after cleaning out my registry for Samsung that improved things as well as trying a new USB port on the PC).

Now I have the i9100 screen with the yellow triangle which I assume is because of the Siyah kernel.

Before I move on to the next step, I wanted to make sure I understood things correctly. you want me to next flash the complete UCKH7 binaries linked in your Download Repository from sammobile.com? It also contains the bootloaders, right? I guess for sure I will stay away from the x64 machine since I have that Blue screen problem. I'm assuming the one click and .tar.md5 are the same, right? Since I still am not that confident about my USB drivers, what would be the Heimdall commands in case this doesn't work. I'm also wary of flashing bootloaders.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I doubt that the phone has anything to do with the pc freezing. It could have something to do with bad flashes if the USB port on the phone is dirty or beginning to fail. Flashing a bootloader is minimally risky. The risk is the flash being interrupted while the bootloader code is actually being transferred, and since the sbl is so small, that transfer happens in a matter of seconds.

If it is nand read/write corruption, you most likely will need to flash the full firmware including sbl and param.lfs. You might first try flashing the package that has the sbl and param.lfs removed, just to see if it will work. But for nand read/write corruption, the sequence I posted is what is needed, afaik. There should be no difference between using the one-click downloader and stand alone Odin. The method is a little different is all.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Thanks for the info as I'll try that. I don't see a ODIN package with UCKH7 stock binaries that have the sbl & params removed. There is one for Heimdall though. I guess I was hoping to test my ODIN setup on the successful PC (running XP) before I run the whole package. Alternatively, I have played around with Heimdall on the original offending Blue Screen PC, but gave up on Win 7 x64 and successfully downloaded the PIT file on the exact same PC booting up in Ubuntu, so I feel good that the connection there is safe. As a general thing with Heimdall, does it matter the order I'm flashing the partitions, or can I even break them up into pieces, taking the UCKH7_noBL image and flashing the factoryfs, and zImage with separate commands?
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Entropy512's Original I777 UCKH7 Kernel plus Non-Rooted System Package, which is the second block below the UCKH7 stock binaries is the one that has no sbl or param.

With Ubuntu, you want to use Heimdall command line tool. The code for Heimdall is in the little code boxes in the Download Repository. I don't think the order matters, but there is information in the readme file with the command line tool which suggests an order.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
I'm starting to run out of ideas regarding this phone. I went back to ODIN on the Win XP PC that successfully flashed the Siyah Kernel, but after running into problems, cleaning registry entries of Samsung, I can't seem to flash anything past the "SetupConnection" phase of ODIN. It pretty much just hangs there, and I never see any indication that anything is being written to the device (ie no green bar on the phone). I was trying to just flash the Entropy's UCKH7 system files and modem as I'm afraid to just yet flash the bootloaders yet. I guess my question is, are the write problems caused by my hosed NAND partition or am I still having problems with my USB drivers on the Win XP machine. I've installed/deinstalled them many times and spent most of my time rebooting and having ODIN just hang there after SetupConnection.

In parallel, I also tried my Win7 x64 machine (the one that original caused this problem with ODIN), but I only booted up in Ubuntu with Heimdall. I found Ubuntu/Heimdall to be the most reliable as I can reliably get the PIT file at least (I don't always get that far with ODIN on XP). BTW, I think with 1.40 version of Heimdall, he did away with the hard coded names that CreepynCrawly has in the instructions of his download repository, but most of them are just simply in CAPS as opposed to the partition names in the download repository (ie --KERNEL instead of --kernel). You can find out for sure by issuing a print-pit command. With Heimdall, I'm consistently getting the OS to recognize the device in boot mode, but then when it starts writing, I get a libusb error, and I never see the green bar move on the phone.

I still haven't flashed the full stock with bootloaders yet, as I'm hoping that will do the trick. BTW, for the tar.md5 file, what slot do I insert it in since it contains bootloaders and modems? Do I just put it in the PDA slot? With Heimdall, would I issue the commands for the bootloaders first, then the non system images? Or do I just do one Heimdall command for all of them?

Anyway, I'm still not sure if I have a reliable PC that flashes correctly, or my NAND corruption is causing the write errors. If it's the latter, then I'm thinking my phone could really be bricked despite being able to get at the bootloader.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Oh, and 1 more thing. What was the point of flashing the Siyah kernel, and then stock image? I was pretty happy when I got that successfully flashed, but now I'm not sure what purpose it's serving.....
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
The purpose is to clear nand read/write corruption. If nand read/write corruption is the problem, then following the sequence I posted exactly should clear it and get your phone back. I don't understand the inner workings of the phone well enough to know why that sequence works. But you havn't tried this sequence yet, since you havn't flashed the full stock image.

The cause of the failed flashes is most likely in the phone. There is some possibility it is because of the connection between the phone and the computer. It is almost certainly not just because of the computer.
[AT&T Samsung Galaxy S II SGH-I777] 4-2ndtwin:
zebra72,

With a quick read of this thread i didn't see it mentioned...but have u tried a different micro usb/usb cable yet ??

Sometimes that cable that u thought was reliable can all of the sudden become not so. Using a different cable has solved heimdall flashes that weren't workin for me in the past...and even odin flashes that were not completing successfully.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Ok, Thanks again for the explanation. Right now, I'm just gun shy given what has happened since the full stock image contains bootloaders. I just don't want it to fail at any of the critical steps, however small that may be. Would I be able to try to flash the Siyah kernel again as a test of my setup, and then if it succeeds flash the full stock?

I had thought about it, but now hearing creepyncrawly's explanation and your previous experience, it's something I'll have to check. Any recommendations on cables? Should I go with stock Samsung cables? Thanks for the suggestion!
[AT&T Samsung Galaxy S II SGH-I777] Teknodad1974:
Samsung Oem USB

http://pages.ebay.com/link/?nav=item.view&id=400467800450 :)
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
Wow, what a difference a USB cable makes! So after more failures today, I decided to pull out the old data cable from my Nexus One and give that a shot. I used both ODIN and Heimdall, and I was able to flash the Siyah kernel again as well as the UCKH7 modem file in Heimdall. With Heimdall, it was telling since I had turned on verbose mode, and with my original OEM cable, I would occasionally get time outs even when retrieving the pit file, but it would recover. However, with flashing, it must not have been able to overcome the errors. In retrospect, the OEM cable has been through a lot (ie chairs rolling over it, pulled and dragged) since it is the same cable as the charger. Props to 4-2ndtwin for pointing this out! And creepyncrawly, it looks like you were right. I kept on thinking it was my computer with the USB ports or drivers!

I also noticed now that I have CWM recovery on it, when I flashed the Siyah kernel a second time. After noticing how fast the ODIN flash was, I'm starting to think the first flash probably didn't fully flash correctly, but I got success after a much longer time than with the good cable. Now I'm wondering if I should risk flashing the bootloaders and instead just try to flash the the UCKH7 with root and go from there. Of course, now that my counter is tripped, can I just flash a ROM that I'm interested in?

Thanks so much for all the help!
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
You may be able to flash custom firmware now. It won't do any harm to try. Then if it doesn't flash, you can do the steps I gave for clearing nand r/w corruption.
[AT&T Samsung Galaxy S II SGH-I777] zebra72:
That was my thinking exactly, and I tried to flash UCKK6 root (trying to get back my old data), and it failed on the factoryfs partition through Heimdall. Then I just followed your instructions with the stock UCKH7 through Odin and crossed my fingers when it flashed all the important stuff (bootloader, etc), and I let out a huge sigh of relief when it all worked! I'm so excited to have my phone back as I started exploring buying other phones when it looked bleak! Now I'm ready to explore the world of custom ROMs.

Moral of the story is you really have to look at everything even if you think it couldn't be something simple like a cable!

And finally, I want to give a huge thanks to creepyncrawly for helping me out! I'd be SOL without all the prompt help you have provided for me!
[Sony Xperia P, U, Sola, Go] TeamMex:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* or you getting fired because the alarm app failed.
*/

​

Screenshots:

​

Features:

* Latest CM9.1

* Optimized Ramdisk

* Odexed

* Full support stock kernel

* gobernors pegasusQ ondemandX

* io schedulers SIO

* More optimized

* PAtched some parts and services for more stability

NOTE:

Can You use on custom kernel only need delete :

on System/etc/init.d/00wifiifx
System/xbin/sh
system/bin/ chargemon
system/bin/chrger
system/bin/recovery.tar
system/bin/ramdisk.tar

and copy file from attachament into rom.
upload later
[/HIDE]

Requeriments:

* Latest kernel ICS (Maybe U need flash ICS Firware oficial 6.1.1.B.1.54)
* CWM (can you download my proper CWM in Downloads Section) or find [URL="http://d-h.st/RK"]here[/URL] [URL=http://d-h.st/RKo]cwm-2.0-lotus-XPE.zip - 2.32 MB[/URL]
* And download this file.

How to install:

* Copy zip file in to internal storage-->
* Enter in to CWM and make wipe data,dalvick-cache and battery stats.
* Flash zip file
* and optional Flash Gaaps
* Reboot and Enjoy!.

Downloads:

XPerience-9.1-V3_Rc1.zip - 131.85 MB

GAAPS:

http://goo.im/gapps/gapps-ics-20120429-signed.zip

cwm-2.0-lotus-XPE.zip - 2.32 MB
​

Older downloads

XPerience_CM9.1_lotus_signed_070713_150634.zip - 131.53 MB

XPerience-9.1-20130725-UNOFFICIAL-lotus.zip - 138.79 MB

Sources:

https://github.com/XPerience-montblanc/

Special Thnks:

* Cyanogenmod Team

* FreeXperia Project (FXP AKA Jerpelea)

* My mom :D

* My girlfriend

* Unkown
[Sony Xperia P, U, Sola, Go] TeamMex:
More changes from:

http://review.cyanogenmod.org/#/q/branch:ics,n,z

FIX SU PROBLEMS

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

* Fix derp translation spanish.

*

Changelog

V3

* CM11 Bootanimation.
* Backported Circle battery from CM10,CM10.1,CM10.2,CM11,XPerience 5.0.2 CN10 Shakira
http://review.cyanogenmod.org/#/c/24736/
* When use Circle battery , if charge are 95 or more circle change to green color if u unplugg this returns to white.
* Deleted Support for HDPI AND XHDPI themes for now add later :)
* Some kitkat icons :)
* more performance and fixed some problems with ThemeManager
* Backported Apolo from Jelly bean
* Backported CMfilemanager from Jellybean
* Audioblob updated
* Builded with linaro 4.8.2
* Builded with -O4 flag maximun optimization for ICS
* Common: Things and Stuff (I swear we will fill this out much better later on)
* Common: Android 4.0.4 (Google)
* XPErience sauce for maximun performance of Processor
* alsa-lib, alsa utils, blktrace emma,dnsmasq,bluetooth,bison,iptables from 6.1.1.B.1.54 source

V2

* Lates CM9.1 sources
* Support to P, U ,Sola
* New Mali400 drivers
* Optimized system
* some sound optimizations
* battery performance
* Updated vendor blobs
* Odexed
* Themes supprt HDPI AND XHDPI (thnks to [MENTION=4421347]Dzol Cp[/MENTION] )

and more...

*First release on Lotus
* Based on latest CM9.1 and FXP 216 sources codes
* Fixed MTP and EMC mounts (some bugs on stock kernel)
* Optimized Ramdisk (extracted from sources)
* Add CWM (my CWM from xperience jb rom)
* Patched some parts of system
* smooth and more performance
* some minimun changes on lib-alsa sound
* Zipaligned for best use on ram
[Sony Xperia P, U, Sola, Go] TeamMex:
Addons

Walkma ICS

Features: Walkman XPERIA S ported for DoomLORD

Color extractor , album art extractor, Music tag editor -Thnks to me for fixed this.

Download:

WALKMAN_ICS-XPE.zip - 4.56 MB
[Sony Xperia P, U, Sola, Go] 42me:
Bro what about unlockbootloader?i want to try this thanks
[Sony Xperia P, U, Sola, Go] TeamMex:
only need ICS kernel ;)
[Sony Xperia P, U, Sola, Go] TeamMex:
For now rom are for lockedbootloadr

maybe tomorrow add file to work proper on custom kernel ;)
[Sony Xperia P, U, Sola, Go] 42me:
ok thankss bro keep it up:cool:
[Sony Xperia P, U, Sola, Go] arenaboy007:
Oh shoot I have unlocked bootloader...

I shall relock it and try this rom, but if you will update it for unlock bootloader tomorrow then should I wait?

Edit: lol just out of bat, whew.
[Sony Xperia P, U, Sola, Go] TeamMex:
work on all CM9 roms :) locked and unlocked BL
[Sony Xperia P, U, Sola, Go] arenaboy007:
Looks good, and is pretty smooth. I wish it was jellybean.

Can I install this kernel on this rom?

http://xdaforums.com/showthread.php?t=2322227
[Sony Xperia P, U, Sola, Go] 42me:
thankss bro download now report later
[Sony Xperia P, U, Sola, Go] TeamMex:
yep only read first porst
[Sony Xperia P, U, Sola, Go] arenaboy007:
A

Thanks! One thing I noticed. Ram seems to be very unstable. Fluctuates from 100 to 150 in seconds without launching anything.

Edit: Will this tweak, work with your rom? Just want to be safe.

http://xdaforums.com/showthread.php?t=1926776
[Sony Xperia P, U, Sola, Go] arenaboy007:
Will Adrenaline Engine, Geeky Engine, LoopySmoothness tweak still make an improvement on this ROM?
[Sony Xperia P, U, Sola, Go] TeamMex:
Im not test these tweaks

can u test and report

cheers.
[Sony Xperia P, U, Sola, Go] arenaboy007:
Doesn't work. The phone does not boot after installing the script.
[Sony Xperia P, U, Sola, Go] TeamMex:
Updated read 2nd post
[Sony Xperia P, U, Sola, Go] TeamMex:
try force reboot with power and vol up (vibrate one time)
[Sony Xperia P, U, Sola, Go] afpereira:
the new rom, force closes on superuser and themes, please fix this.
[Sony Xperia P, U, Sola, Go] TeamMex:
I tested Super user, themes and work good

maybe u don't make wipes.

Edit:

IM USING POPSTYLE theme

cheers.
[Sony Xperia P, U, Sola, Go] afpereira:
yes i make all the wipes, i make wipes before, after but didn't work
[Sony Xperia P, U, Sola, Go] 42me:
yap... i have this problem too...
[Sony Xperia P, U, Sola, Go] afpereira:
ok, to solve the su problem i delete su apk and copy the new one, the theme problem remains, and when i reboot they make a new android system actualisation everytime.

I think this was a bad compiling, but i don't understend nothing about compiling or make roms...
[Sony Xperia P, U, Sola, Go] eswawan:
Can anyone give me stock ics kernel please.:thumbup::thumbup:
[Sony Xperia P, U, Sola, Go] uruguayo21:
very good rom my friend :)
[Sony Xperia P, U, Sola, Go] Davidmarshall:
please

only ICS .54 version is required for this rom ? or ICS .10 is enough???
[Sony Xperia P, U, Sola, Go] TeamMex:
you need .10 ics kernel
[Sony Xperia P, U, Sola, Go] Davidmarshall:
thanks

thank you so much for your reply, now ill flash stock ICS.10 version of X go...then your rom....

Actually i love your rom cuz its based on CM...love it will try it ASAP....
[Sony Xperia P, U, Sola, Go] Davidmarshall:
sir, please

As per the previous post reported, Themes and Su FC....and Apollo music doesnt show album art...just goes blank and sometimes FC too..

and in power menu i selected reboot to recovery... it got struck up and after holding power and volume + it booted...

and volume has been dramatically reduced in song playback....

tried flashing it twice with all wipes but no improvement....

why i reporting all these ? cuz i love this rom badly ..i need it and i love it...so i want it as a bug free one....pls try to fix this issues...

and waiting for this quote to be replied..

plz

Tried installling with both ICS .10 and .54 kernel...

and when i reboot they make a new android system actualisation everytime. kindly focus on this issues..
[Sony Xperia P, U, Sola, Go] TeamMex:
Hello

Sorry, but have to wait a little longer.

Since I had an accident with my xperia and touch panel stay fact , I am gathering the money needed to buy the new touch and to continue development.

Greetings.