Database Info

[RECOVERY][MOD][Desire][02-Nov-2011] Clockwork 5.0.2.7.111102

First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.

it works... thank you

suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.

bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?

sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.

zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days

sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.

well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?

sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk

yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!

sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.

Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.

teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?

Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.

Updated OP to version 4.0.0.0.

Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.

teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.

I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.

Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.

TWRP unable to flash CM10

Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app

the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.

thorrules said:
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!

tobdaryl said:
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
Click to expand...
Click to collapse
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
mike-y said:
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
Click to expand...
Click to collapse
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.

thorrules said:
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
Click to expand...
Click to collapse
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.

tobdaryl said:
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
Click to expand...
Click to collapse
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).

thorrules said:
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
Click to expand...
Click to collapse
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.

tobdaryl said:
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
Click to expand...
Click to collapse
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.

thorrules said:
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
Click to expand...
Click to collapse
OK, that is the reason I mentioned 4.2 and multi-user.
Good Luck!

[Q][HELP] convert EXT4 to F2FS

Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
lotherius said:
...on my 2012 Nexus 7 I was having a lot of lag issues using stock/Faux123. It was painfully slow at times, even just waking the screen. I converted to F2FS (data only, not system), and the problems evaporated. [...] It was slow before, then it was fast. I had tried multiple other solutions prior to F2FS that didn't work. Many other users on the N7 2012 have also reported the same experience.
Click to expand...
Click to collapse
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]

Narciso Neto said:
Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Click to expand...
Click to collapse
Have you find solution?

I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.

Will it delete all the files in internal storage?

shsagnik said:
Will it delete all the files in internal storage?
Click to expand...
Click to collapse
Yes, it'll as we'll format the partition as F2FS. Make a backup if you have important data on there.

willianalberto said:
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Click to expand...
Click to collapse
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.

jcooler said:
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
Click to expand...
Click to collapse
Have you tried converting AFTER CM boots the first time? Also, are you using the latest build? It can be TWRP's fault too (just read on a thread on ASUS) or maybe our device don't support F2FS yet.

I have managed 2 convert many ROMs for the tab 2. I've spent hours reading about it in the past. As far as I'm aware no lollipop ROMs can convert yet as u also need a custom kernel that supports f2fs. U should be able 2 convert most KitKat ROM s with the right tools. Its only about 4 lines of the updater script 2 edit then find a kernel that supports ur ROM and f2fs like agni,dhollmen or blackhawk. Youll also need custom recovery thats f2fs ready, theres a twrp and philz download around. pitty easy once you do it ab couple of times. Hope that helps u......

Are there performance improvements?

There was quite a bit improvement, first sign of any custom kernel for lollipop that support's f2fs I'll be trying 2 convert the ROM to see the comparison's. Think that might be a little time away yet tho........

I've opo and like to migrate on CM12 nightly with F2Fs but stopped on boot logo with AK kernel any suggestion??
-cm-12-20150312-NIGHTLY-bacon.zip
-AK.128.OPO.SKULL.CM12.zip
-formatted cache, data, system, sdcard as f2fs by philz_touch_6.59.1
what's wrong?

[Q&A] BigPart Repartition Upgrade and Resource Center

Q&A for BigPart Repartition Upgrade and Resource Center
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for BigPart Repartition Upgrade and Resource Center. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Exe files?
When I try to download the zips for BigPart Twrp and the wingray BigPart boot image, it downloads executable files? Why does it not just download the zip files as promised?

Exes
I tried downloading one and instead of downloading the zip file I wanted it downloaded EZ Downloader, and broke my Chrome browser. Why can we not just download the zip files required to change over to the BigPart repartition for xoom?

I made a huge mistake. I installed TWRP 2.6.3.0 fine. Unfortunately I got distracted and forgot to flash twrp bigpart. Instead I skipped to the step where you wipe everything but the sdcard, and when I rebooted to recovery, the screen hung on the teamwin splash screen. When I did a hard reset and tried to reboot manually into recovery I get the motorola dual core screen with a message saying "starting fastboot protocol support", and it just hangs there. Any help from you guys would be greatly appreciated.
Disregard, I finally got it to boot back into recovery manually and went on from there.

Guide
9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.
Click to expand...
Click to collapse
But I don't see the files on the memory card
from FAQ
Q: Followed the instructions for the re-partitioning. Everything worked except the Xoom cannot see the external sd card in recovery. I have re-formated it as fat32 and tried another card. When I view the files in the PC they are there. Any ideas?
A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...
Click to expand...
Click to collapse
it doesn't work
upd:
another card is working correctly!
upd2:
no need to flash BigPart boot image package!

Motorola Xoom bigpart repartition touch recovery
Hello, never rooted xoom but want to so I can have KitKat. When I try to download original TWRP 2.6.3.0 touch recovery it takes me to a smut video. Do you have a link to the real file. Also since I have never rooted this device, do I have to do something else before I follow the big part repartition upgrade. Sorry very green about this.
Thanks!

Trouble with flashing BigPart to WingRay unable to wipe or mount data
I have tried a lot of ways of flashing the BigPart partition (TWRP 2.8.6.0 for BigPart) but it seems that every way I do it is wrong. I think I followed the directions correctly but every time I do it I either get a password request to login to TWRP or it starts up but says that the data partitions is not able to be wiped or mounted. Most times I can not select the data check box. Please help me figure out what I am doing wrong or tell me were to go. I really want to flash the 5.1.1 but I am getting no where.

Assistance is required to flash JB to Samsung Galaxy SII

Hi All,
I decided to flash JB firmware to my old device and give it to my son. Now device has GB version.
I found topic: http://forum.xda-developers.com/galaxy-s2/general/rom-cyanogenmod-10-official-nightly-t1794758 which presumable should help me with that by encountered few problems:
1. The first advice is: Make sure you're running a proper working ClockworkMod-Recovery.
I went to appropriate topic (DANGER!!!): http://forum.xda-developers.com/showthread.php?t=1118693, which refers to http://d-h.st/pQK but downloaded ace-archive contains virus. I killed the virus eventually, but wondering how is that possible that XDA references something with virus inside?
Question #1: should I still try to download ClockworkMod-Recovery from the referenced topic? Today I tried that again, but ace archive still contains a very suspicious exe... and I'm afraid, that is still virus.
2. Further advice is: Copy GApps and CM10 ZIPs to your internal SDCard
Where can I get CM10? In the original topic there is only reference to the nightly guild of CM10. Should I try it? Is there more reliable build?
Another topic: http://forum.xda-developers.com/xperia-j-e/orig-development/miro-tipo-j-edevelopment-cm10-t1997251 doesn't have any reference to download.
Question #2: Where can I download CM10 and other gapps?
Question #3: Where can I get firmware itself? I could not see any WORKING reference in the original topic. Please advise.
Thanks a lot!

SeredaOM said:
Hi All,
I decided to flash JB firmware to my old device and give it to my son. Now device has GB version.
I found topic: http://forum.xda-developers.com/galaxy-s2/general/rom-cyanogenmod-10-official-nightly-t1794758 which presumable should help me with that by encountered few problems:
1. The first advice is: Make sure you're running a proper working ClockworkMod-Recovery.
I went to appropriate topic (DANGER!!!): http://forum.xda-developers.com/showthread.php?t=1118693, which refers to http://d-h.st/pQK but downloaded ace-archive contains virus. I killed the virus eventually, but wondering how is that possible that XDA references something with virus inside?
Question #1: should I still try to download ClockworkMod-Recovery from the referenced topic? Today I tried that again, but ace archive still contains a very suspicious exe... and I'm afraid, that is still virus.
2. Further advice is: Copy GApps and CM10 ZIPs to your internal SDCard
Where can I get CM10? In the original topic there is only reference to the nightly guild of CM10. Should I try it? Is there more reliable build?
Another topic: http://forum.xda-developers.com/xperia-j-e/orig-development/miro-tipo-j-edevelopment-cm10-t1997251 doesn't have any reference to download.
Question #2: Where can I download CM10 and other gapps?
Question #3: Where can I get firmware itself? I could not see any WORKING reference in the original topic. Please advise.
Thanks a lot!
Click to expand...
Click to collapse
You can find your CM10 and recovery on cyanogenmod.org

Tyaginator said:
You can find your CM10 and recovery on cyanogenmod.org
Click to expand...
Click to collapse
Was not able to find CM10 on cyanogenmod site, only ROMs.
I want also to update community that I was able to update the firmware on my device.
The most important things which helped me to do are below. Hopefully they will help somebody else.
1. The very basic part of device (at least of Galaxy SII) is "Download mode" accessible via "VolumeDown+Home+Power". This mode literally unbreakable and your safety net if anything goes wrong. Via this mode you are able to upload "Recovery software". To do this you need Odin and recovery SW itself. I used Odin 3.04 and CWM-KitKatCompatible-i9100.tar
2. Recovery mode is SW which allows to upload ROM. To use it one should upload zip with FW (firmware) to SD card and using recovery mode SW install it. Usually, people upload ROM when their device is fully functional. In my case (I broke it before I uploaded FW) I pushed fw via ADB (which is working in recovery mode). Command line: adb push "file_with_FW" /sdcard/storage0 - worked for me
3. Also makes sense to install google apps (set of apps from google which will make other programs work better). Trivial thing after you manage items 1 and 2.
Good luck!