Related
[Patch] Adlxmod.F4D.2.03-patch
This patch includes previous Adlxmod.F4D.2.02 patch, plus:
- Semi-transparent pulldown bar
- Updated: Google Maps 5.2
- Updated: Market 2.3.4
- Latest Cyanogen APN list (February 06, 2011)
- Fixed notification texts not always white in the DarkBar version (only applies to Adlxmod.F4D.2.03-DarkBarOnly patch)
- Note 1: This patch will restore the white notification bar. Download the new DarkBar patch to switch again to a Black bar.
- Note 2: This patch will automatically wipe the Dalvik cache, so the first reboot will take some more time (can take >5 min depending if you have many apps installed) - Don't freak out.
New Notification bar patches:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
[Patch] Adlxmod.F4D.2.02-patch
This patch includes previous Adlxmod.F4D.2.01 patch, plus:
- BlurHome selectable: You can switch to BlurHome if you like it
- Added: Adobe Flash 10.1.106.16
- Updated: Market 2.3.2
- Updated TitaniumBackup 3.7.1
- Added: Copy to Clipboard
- Added: Shrinkpipe
- Removed BlurUpdater.apk
Base rom Adlxmod "Froyo for Defy" v2.0:
- Based off UK 3.4.2-117 Froyo leak
- Fully Deodexed by me -> Theme ready
- Optionally a dark notification bar patch can be installed, see below. White patch also provide to get back at it.
- Rooted, Recovery installed
- Phone can be used with no SIM
- Includes Motoblur, but it can be skipped
- Many language supported: Spanish, English, French, Portuguese,...
- Camera flash IS working and synced
Added:
- LG Optimus 2X ringtones (some literal in chinese)
- Adlxmod splash (installed on 1rst boot, will appear on 2nd boot)
- HTC_IME Keyboard para Froyo!
- Gingerbread Keyboard
- Android Terminal Emulator
- Wireless (Wifi & Bluetooth) Tethering
- Busybox fully installed
- AOSP Email App
- Titanium 3.6.7.1
- LauncherPro 0.8.3
- Tenfar Recovery
- 3D Gallery (my mod)
- Overclock support (phone won't be OCed by default)
- SetCPU (free from XDA, please donate on the Market)
- Milestone Overclock
- Added in /system/xbin: rwsystem/rosystem, wpa_cli, zipalign, strace, ssh, sqlite3, dexopt-wrapper, tcpdump, fix_permissions, iptables,...
- Extensive APNs list (Cyanogenmod)
- Ad-Blocking
- AOSP Eclair icons & lock screen sliders
Updated:
- Market 2.2.11 + Market Fix (Paypal shows up for example)
- Google Maps 5.1.0
- Adobe FlashPlayer 10.1
Download these files:
Chinese sbf : Defy_2_2_CN.zip
Rom's Nandroid: Adlxmod.F4D.2.00.zip
Boot+Devtree : Tmo_2.2.1-3.4.2-107-boot-devtree-ONLY.sbf
SuperOneClick : SuperOneClickFor2.1.zip
(this link included Tenfar Recovery with an installer) -> use this one.
Latest Adlxmod Froyo for Defy patch: Adlxmod.F4D.2.03-patch-signed.zip
Optional files you may need:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
- Patches for fixing signal/baseband, 2g/3g
- Alternative languages (like PortugueseBR,...) for Swype: see here
Instructions: Please READ-RELAX-READ-FOLLOW
First of all, check CAREFULLY in which case you are:
Case 1:
If you come from a US T-Mobile Defy with the 3.6.90 update
If you have already flashed a non-downgrabable sbf (2.51 or 3.4.2).
Case 2: If you are not in case 1.
Due to Motorola Defy having a locked bootloader at the time of doing this rom, the flashing process is quite complex, so READ AND FOLLOW it VERY CAREFULLY, or you will end with a non booting phone. If it is the case, you should restart again the whole procedure from the beginning.
I recommend you print the whole procedure, and check every step as you do them.
PLEASE READ EVERY SINGLE STEP BEFORE STARTING IT AND FOLLOW THE ORDER CAREFULLY.
If you don't respect the steps and order, the result can be unpredictable.
Only run the steps that apply for your case!
This Rom is a Nandroid backup of system to be restored over the phone:
Unzip the rom file, and place the 2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar folder into the SD:/goapkrev/backup/ folder. If SD:/goapkrev/backup/ doesn't exist you have to create it. It should look as follow:
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/system.img
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/nandroid.md5
Start with FULL battery! (cases 1 & 2)
Be sure your phone's battery is charged 100% before starting.
Wipe all (case 2 ONLY)
Boot your Defy into Stock Recovery (Power + Volume Down button)
Tap in the bottom right corner of the screen to get into the menu
Select Wipe Data, then press OK
Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
Flash Chinese sbf, root, install recovery (case 2 ONLY)
!! WARNING !! Be sure you are in case 2 before you follow! If you are in case 1, read instructions again!
Connect the phone via USB to your computer
Flash Chinese Froyo sbf using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
After flashing the phone will reboot. As we have wiped, it should boot correctly into the Chinese rom.
At the Chinese Motoblur login screen:
Select English language
Press Menu -> Skip Motoblur setup
Root, Install recovery (case 2. also case 1 if you have never rooted & installed recovery)
Go to Settings, Applications, Development -> Enable USB Debugging Mode
Root the phone using the provided SuperOneClick
Don't reboot yet. Run the "Install Recovery.bat" in the same SuperOneClick folder.
This will copy Tenfar Custom bootstrap recovery to the phone and reboot it.
Power up the phone again & wait until it boots.
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Install Recovery System", when Asked for Superuser permissions, give them and wait until it says "Install Success!"
Reboot into Custom Recovery & Flash Rom (case 1 & 2)
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Recovery Boot"
In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
Here you can also flash the patches you want to install (Apply zip from sdcard)
Get back to the recovery main menu, and WIPE ALL
(case 1 ONLY) Reboot. End.
Flash boot&devtree (fixes cam flash) (case 1 & 2)
Reboot. /!\ While the phone powers off and on again, maintain the "Volume UP" button pressed!!
Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Connect the phone via USB to your computer (if it was unplugged)
Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
End. Enjoy your Adlxmod Froyo for Defy!
Once you have correctly done the process, you may want to flash some option patches. Just go into Recovery mode and flash the zip you need from the optional patches.
Phew what a detailed protocol. Thank you so much will try it tomorroow
Sent from my MB525 using XDA App
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Update0: You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
I'm trying to start over, but I can't get anywhere except Stock recovery (which doesn't respond to any commands on the OK Button - wierd) and the USB Bootloader, which doesn't help because if I go through the whole process without doing the factory reset, I can't get to Tenfar's recovery boot after flashing the devtree only sbf - I just get a blank screen.
So I'm pretty much effed.
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Update3: I am going to try a different ROM entirely and maybe I can get a working phone before work tomorrow...
Update4: Yeah, your instructions were backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.)
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
will try it rite now, coming from chinese sbf, never flashed 2.51. will post feedback tomorrow.
Darkcaptain said:
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
Click to expand...
Click to collapse
hmm good question dude dark bar would look awesome going to try it as im board let you know if it works
edit tried it, it works but imo doesn't suite stock rom
rob-t said:
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Click to expand...
Click to collapse
If you haven't flashed any UNdowngrabable rom, you should be able to flash this one. After flashing this rom using my procedure, you will NOT loose downgradability. In other words, yes, my rom is downgradable.
rob-t said:
You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
Click to expand...
Click to collapse
If you land in Tenfar recovery you haven't followed my instructions that say:
- Press "Recovery Boot". /!\ Phone should now reboot. While the phone powers off and on again, maintain the "Volume UP" button pressed!!
- Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Click to expand...
Click to collapse
That means that, anyway you land in Tenfar recovery, just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf.
If you get a non-booting device at some step, try to just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf at this step.
rob-t said:
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Click to expand...
Click to collapse
Well, Stock Recovery is a bit tricky to use... In my particular case I use the vol up/down to select menu entry, and I tap on [ok] (I usually have to tap several time to have the [ok] actually do something. Once it starts, yes, the Wipe is very slow! Like 1-2 minutes.
rob-t said:
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Click to expand...
Click to collapse
That is weird... Anyway I'll double check later, but it's what I have written on my notes, and I've followed my notes a lot of times, so I guess this order worked for me at least.
rob-t said:
Update4: Yeah, your instructions are backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.) PM me when you fix your instructions and I'll remove this.
Click to expand...
Click to collapse
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
adlxdum said:
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
Click to expand...
Click to collapse
ill give that ago running uk 2.2
Nice rom, will feedback you...
can confirm that if you already running 2.2 all you need to do is run the nadroid back up and all should be good btw dude nice rom
First of all thanks for this rom! I am expecting my Defy over the mail by monday or tuesday and up till now this rom is the most appealing.
I have one question. How do you prevent motoblur installation? Is that simply a matter of skipping at first boot? Do you have plans to make a deblurred version of your rom?
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
that happened to me pulling the battery sorted it and it booted fine after that
i think native boot+devtree would be better, so here it is.
racca said:
i think native boot+devtree would be better, so here it is.
Click to expand...
Click to collapse
I also had this one, but as the US one was working correctly I sticked with it. I have posted what I have tested.
Boot loop in Motoblur Animation?
fabianowerner said:
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
Click to expand...
Click to collapse
If you have Boot loop in Motoblur Animation, please try this:
- Boot your Defy into Stock Recovery (Power + Volume Down button)
- Tap in the bottom right corner of the screen to get into the menu
- Select Wipe Data, then press OK
- Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
- Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
Then reboot. How does it go?
adlxdum said:
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Click to expand...
Click to collapse
Thanks, yeah I was coming from Eclair 2.34, so I should be downgradable. Can confirm that the camera works fine on this ROM.
Sadly, I have the dreaded "Unable to open connection to server" problem with Android 2.2 so no more exchange email.
Update: Ran a quadrant benchmark on my phone with this ROM, got 1299, so pretty good! I haven't removed any apps, and also added SetVsel and DroidWall. Overclocking in SetVsel was set to: 1000mhz/52 600mhz/36 300mhz/26. About the same speed as I had going in Eclair.
Missing WIpe!
There was a missing step (to Wipe all) in my instructions, sorry. It's fixed on the first post.
- In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
- Get back to the Recovery Menu, and WIPE ALL once more.
Click to expand...
Click to collapse
Hmmm, I'm not sure having both email apps installed is a good idea. Once you get past setup in either app (took about 20 tries but finally it connected to the server and completed setup), either app will both force-close as soon as they are launched. Were you actually set up an exchange account during testing of this rom?
Will give this a try, Is market working?
also can i flash the data.img from my backup to restore my apps and data?
Introduction:
---------------------
TeamWin Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features that we deemed missing from current recoveries. After a lot of hard work for weeks, we are happy to announce the release of twrp.
Key Features:
---------------------
- Clean, simple, intuitive Menu System
- Ability to save custom recovery settings
º Default partitions to back up
º Default zip folder location
º Default color theme (lots to choose from) (Thanks to ffolkes!)
º Default Time Zone (for more accurate time stamps; US time zones only for now)
º Zip Verification
- Ability to select which individual partitions to backup, and restore.
- Ability to choose compression or no compression backups.
º Compression takes longer of course, but you save roughly half the space. You choose.
- Ability to auto restore GAPPS on zip flash (for CM based ROMS)
- Ability to auto reboot after successful flashes (for the lazy)
- Capacitate Button functions
º Home - Main Menu
º Menu - Advanced Menu
º Back - Up a Menu Level
º Search - Select Current Selection
- Battery Level and Timestamp (Better safe than sorry)
Known Issues:
---------------------
- Capacitative Buttons sometimes bug out after a while, but this does not hinder twrp in any way. (happens in aosp recoveries)
- While working on twrp, TeamWin's top race horse ran off, if you find him please let us know. (Emo Horse was found!)
Disclaimer:
---------------------
As usual, use at your own risk. TeamWin is not responsible for anything bad that may occur from using twrp. We do however take responsible for the awesomeness that comes with it. Don't be a d3rp and use twrp for bad. With great power, comes great responsibility.
Special Shout Outs:
---------------------
- TeamWin
º toastcfh - for his under appreciated dedication to the community.
º agrabren - for his leading the way to freedom for numerous devices with fre3vo.
º Dees_Troy, joeykrim, shift, vividboarder, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, eyeballer, OtisFeelgood.
- Amon_RA - for his great Recovery for which we gained a lot of inspiration from.
- Koush - for his dedication to the community and ClockworkMod.
- unrEVOked for their great work and dedication to the community.
- AlphaRev for their great work and dedication to the community.
Source Code:
GitHub
Download:
---------------------
TeamWin twrp Page
(All future updates will be updated on TeamWin's site.)
---------------------
Donate to TeamWin Recovery
ChangeLog:
2011-08-05 - v1.0.3
- Added timezones that should cover everyone
- Added twrp spam feature (twrp settings)
- Added fix permissions (advanced menu)
- Added wipe cache and dalvik into Flash Zip menu
- Added copy recovery.log to /sdcard (advanced menu)
- Added output spam/no spam to restores
- Added mke2s prebuilt to /sbin
- Fixed SD-EXT issues, (no partition SD-EXT features yet)
- Fixed EFS partition issues
- Changed the way we do backups on mtd devices, which should fix any boot partition issues
(we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G,etc)
2011-07-31 - v1.0.2
- Fixed SD-EXT issues
- Added Format SD-EXT into format menu
- Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
- Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
- Rearranged the format menu
2011-07-30 - v1.0.1
- initial release on EVO 4G
FAQ
FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PC36IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PC36IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-supersonic-1.X.X.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
Why should I use this over ClockworkMod or Amon Ra?
Feature comparison matrix!
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Post all twrp supersonic questions in here, thanks!
Moar winning...
Excellent job guys
This is just a recovery right? Not anything to do with 2.3.3 root right?
Sent from my PC36100 using Tapatalk
I personally approve this message.... I use this on my 3D, and i guarantee if you like Amon Ra, you will truly love this team win recovery.
Koo
Sent from my PC36100 using XDA App
Edit: we use PC36IMG to flash correct? FAQ says pg86img...or no?
very nice....
Oh so sexy
Showing it off to the world
mfknboss said:
Koo
Sent from my PC36100 using XDA App
Edit: we use PC36IMG to flash correct? FAQ says pg86img...or no?
Click to expand...
Click to collapse
PC36IMG.zip, sorry, copy and pasting from 3D forums.
mfknboss said:
Koo
Sent from my PC36100 using XDA App
Edit: we use PC36IMG to flash correct? FAQ says pg86img...or no?
Click to expand...
Click to collapse
36. That's probably the 3D's file name haha
Sorry about the .zip name, my bad. It's fixed now. A little too much copy pasta.
Many thanks to TeamWin for this, it is the perfect match for Cyanogen.
Quick question, are Amon RA nandroid backups compatible w/ this recovery? Thanks in advance, thanks for this awesome recovery and keep up the good work!!!
frenchy714 said:
Quick question, are Amon RA nandroid backups compatible w/ this recovery? Thanks in advance, thanks for this awesome recovery and keep up the good work!!!
Click to expand...
Click to collapse
No, they are not. Sorry.
Does this support both scripts like amon RA or just one like clockwork?
Sent from my Xoom using XDA Premium App
Zac95 said:
Does this support both scripts like amon RA or just one like clockwork?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Just one. We want everyone to adopt the new edify standard.
Will this work with Sense (based) ROMs, or only AOSP?
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
I have ported touch recovery to Clockworkmod 6. I will be making updates to this just like my other touch recovery. I have added a few menu items and tweaks to make it like my CWM5 recovery.
Looking through the cwm code more in depth i have noticed MANY flaws with the code for new(er) phones that use /emmc instead of /sdcard as the main storage. i have now fixed those flaws in v9+.
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.6_skyrocket.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
[/CODE]
Current Version:
v14.4.6
- added exFAT support
- some under the hood optimizations
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking)
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
its fixed now
BaconStep said:
I used the odin install and now I cant boot into recovery at all. just goes to a black screen.
Click to expand...
Click to collapse
let me take a look.
sk8erwitskil said:
let me take a look.
Click to expand...
Click to collapse
almost fixed. uploading now
watching this
Hope to check this out soon! Gotta wait for a more stable release though.
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
lnfound said:
Slightly off topic but what are the benefits in upgrading CWM? I'm on 5.5.0.4 touch and have always disregarded upgrading with each phone I root as they all seem to function the same.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mostly bug fixes and compatibility issues.
This should be ready soon! Gweedo and utkanos are working on it as well so something good is coming
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
augh yes! i fixed it and its running smooth as buttah!!! ill add recovery.img and recovery.tar.md5 later but there is a flashable zip in the OP. just flash in recovery.
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Dismal Shadow said:
When wiping davlk, it throws like it was on CWM 5
E:unknown volume for path [/sd-ext]
Click to expand...
Click to collapse
yes thats expected. i dont know how many times this has been talked about. /sd-ext is a legacy option in cwm that was used for apps2sd. if you can find a cwm that doesnt show that error i would be shocked. the only reason it doesnt do it on my 5.5.0.4 touch recovery is because i took out the part where it prints it to the screen so people would stop asking about it. lol.
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Will this work for the t989?
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
Yea it should i flashed the first one put up and it wrked on my t989
Sent from my SAMSUNG-SGH-T989 using xda premium
Gotroot said:
Will this work for the t989?
Click to expand...
Click to collapse
yes it will work. but the fix permissions might not work. i have to make one specifically for the hercules. thats my project tomorrow.
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
garydv2002 said:
So just to clarify. Download zip. Flash in current cwm touch and that's it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yessir
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
RiNo808 said:
You are awesome, we need you over on the gsiii side...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
no poaching our devs!
deezhemi said:
no poaching our devs!
Click to expand...
Click to collapse
Heh.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hello everybody!
Yesterday, I collected my previous recoveries, updated them and built a new one (TWRP) too. I made CWM-flashable and Odin-flashable packages too.
CWM v4.0.0.2: (Thanks to The-Droidster for the recovery! )
- This is the first ever custom recovery for the Galaxy R.
- It has all the nice CWM features.
- You can restore ICS with this.
- It has no known bugs. Everybody used it as a starting point.
- What I changed:
- Removed the /lib/modules directory. --> 0,1MB size decrease.
- Enabled button backlight.
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?71ynk9btw7euocr
ODIN: http://www.mediafire.com/download.php?iczq8xed26ohakw
CWM v5.5.0.4:
- Built from the latest CM9 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Very stable!
- It has no known bugs yet (Lot of users have been using it and no bugs have been reported).
- Toggle feature is disabled! (I find it really annoying and it doesn't make real sense for a recovery to lock the screen.)
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?98c1smq7nk4485d
ODIN: http://www.mediafire.com/download.php?c7qbjaqwgpnbr9w
CWM v6.0.3.2:
- Built from the latest CM10.1 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/7xyevjf32fixf3a/CWMv6.0.3.2_CWM.zip
ODIN: http://www.mediafire.com/download/oksv1o2hu63gohi/CWMv6.0.3.2_ODIN.tar
CWM v6.0.1.5 Touch:
- Built using the online builder at http://builder.clockworkmod.com
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling up: Volume up or home button, Scrolling down: Volume down or menu button, Selecting: Power button, Going back: Back button. (This is the default layout and cannot be changed.)
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10 kernel (based on stock ICS one), but it's still lazy.)
CWM: http://www.mediafire.com/download.php?jz24eugrrr988f2
ODIN: http://www.mediafire.com/download.php?6vju9tlf9byeufe
TWRP v2.5.0.0: (Thanks to 'cooleagle' for the tip! )
- Built from the latest TWRP and CM10.1 sources.
- It has a lot of nice features, more than CWM does.
(For example:
- on-screen keyboard -> custom backup names
- built-in file manager
- built-in terminal)
- It has a fully touch-driven and very intuitive interface.
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10.1 kernel (based on stock ICS one), but it's still lazy.)
Note: Backups of TWRP are said not to be compatible with those of CWM. For everything to work well, I recommend that you create a TWRP backup too before modding.
CWM: http://www.mediafire.com/download/8ibammwrtwrwo3d/TWRPv2.5.0.0_CWM.zip
ODIN: http://www.mediafire.com/download/pjxp5xhi96gtbvb/TWRPv2.5.0.0_ODIN.tar
PhilZ v5.06.6: (Thanks to Tha TechnoCrat for the tip! )
- Built from the latest PhilZ and CM10.1 sources.
- It has a lot of nice features, more than CWM does. Check here: http://forum.xda-developers.com/showthread.php?t=2201860
- Based on CWMv6.0.3.2
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/4qz1g86oncn4foq/PhilZv5.06.6_CWM.zip
ODIN: http://www.mediafire.com/download/ixlxkh87s2lxbp9/PhilZv5.06.6_ODIN.tar
Stock GB recovery (XWLA4): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?di4e3ms3qrxuapy
ODIN: http://www.mediafire.com/download.php?i4a1t7ntavvguu7
Stock ICS recovery (XXLQ7): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?kg58rxmlnxkpkqv
ODIN: http://www.mediafire.com/download.php?pjn87j4fyjs34vt
If you want to install a custom recovery for the first time, you always have to start with an Odin-flashable package first. Flashing a recovery with Odin doesn't increase the download counter!
Tutorial (Flashing with Odin):
Please refer to the following thread (This is very detailed and good in my opinion): http://forum.xda-developers.com/showthread.php?t=1406664
Choose a downloaded TAR file (ODIN-flashable) for PDA option.
Tutorial (Flashing with CWM):
Note: This only works if you have already flashed CWM with Odin.
1: Reboot into recovery mode. Do this with a custom rom or by powering on your phone and pushing Volume UP+Home button simultaneously while the Samsung boot logo appears (you have to be fast).
2: Select 'Install zip from sdcard' menu.
3: Select 'Choose zip from sdcard' menu (or if you want to flash something from your internal sdcard, select 'Choose zip from internal sdcard' menu.) Note: On CWM v4.0.0.2, there isn't any separate menu for internal sdcard. It shows internal sdcard by default. External sdcard is mounted under the external_sd folder on the internal sdcard.
4: Navigate to the file you want and choose it.
5: Choose 'yes'.
6: Wait for it to finish and you're done.
Changelog:
08 July 2012: Initial release of v5.5.0.4 in old thread
09 July 2012: Added CWMv6.0.0.0 Touch (alpha)
17 July 2012: Added CWMv6.0.0.3
18 August 2012: New thread (this) created. CWMv5.5.0.4, CWMv6.0.1.1, CWMv6.0.1.1 Touch and TWRPv2.2.1.4 added.
30 August 2012: Modified CWMv4.0.0.2 (touchkey backlight, some init tweaks and smaller image) added.
2 September 2012: Stock GB (XWLA4) and ICS (XXLQ7) recoveries added.
10 November 2012: CWMv4.0.0.2 and CWMv5.5.0.4 reuploaded. CWMv6.0.1.5, CWMv6.0.1.5 Touch and TWRPv2.3.1.1 with new CM10 kernel added.
14 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 added
16 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 with USB Mass Storage fix updated, PhilZv5.06.6 added
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
Dude, you're awesome
Sent from my Galaxy Nexus using xda app-developers app
Man thanks. you are the one who making Galaxy R known to the world. thanks again:angel:
wow you are rocking buddy :good:, thank's a lot just now flashed TWRP and its rocking........
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Adam77Root said:
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Click to expand...
Click to collapse
Thats means u r world famous buddy.. Bt we are waiting.. If someone need that one then we will ask in PM.
Sent from my GT-I9103 using Tapatalk 2
I think this should be stickied!:good:
The-Droidster said:
I think this should be stickied!:good:
Click to expand...
Click to collapse
Me too :good:
Update the OP!
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
The-Droidster said:
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
Click to expand...
Click to collapse
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Adam77Root said:
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Click to expand...
Click to collapse
Along with the stock recoveries of ICS & GB CWM flashable zips kindly try to add a Unroot CWM zip (ICS / GB separate if needed) so that everyone can just flash that zip & get unrooted if in any circumstances they can't flash the stock ROM via a USB if the port is damaged. This will serve as a way for people who have damaged their USB port to get unrooted, flash stock recovery & claim warranty for the damaged USB port.
pankaj88 has already made one but it doesn't remove the busybox so if possible try to make a zip which removes all the traces of the a rooted stock ROM.
You could start a new thread for it if you think it's needed as it is pretty useful & important.
Cheers !
Adam Now we are having ICS, so is it possible to rectify the touch Recovery bug (little lazy for few seconds) please.....
oops sorry i haven't read the OP fully, Ok now i understood because of kernel size you are not able to do it.....
UPDATE:
I updated the links, added CWM v4.0.0.2 and a short tutorial.
I'll get stock GB and ICS recoveries and add them in the following days (It depends on when I get them.)
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
It'd be really great! I think a GB and an ICS one is enough. Thanks in advance!
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
This is great since I need to repack the stock firmware with CWM now just to get rid of the emmc bug.
xlm13x said:
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
Click to expand...
Click to collapse
Added them to the OP.
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
kartiknnn said:
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You cannot flash through stock recovery right now. Flash a one with Odin first, it'll not increase the binary counter.
Sent from my GT-I9103
CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
12.03.2014 - CM code synced. This is most likely the final CM10.2 build.
18.12.2013 - CM code synced
21.11.2013 - CM code synced
07.11.2013 - reverted wpa supplicant(fixes wifi tethering, wifi network list do not refresh again); torch tile added to quick settings; CM code synced
31.10.2013 - wpa supplicant updated(fixes wifi list updates); more kernel tweaks; TWRP updated; keyboard file names aligned(sholes-qwerty.kcm->sholes->keypad.kcm); CM code synced; new gapps available
23.10.2013 - Fixed baseband switching; no other changes, so don't update if you do not have problems with carrier signal
21.10.2013 - Interactive and ondemand CPU governors tweaked(Blachd0se) - this should fix battery drain in the latest build; polish keychars updated(thanks to Rabinhood; see NOTES); CM code synced
17.10.2013 - 720p recording enabled; CM code synced(Long Term Orbits(LTO) added)
10.10.2013 - Fixed(hope that this time for good) camera orientation when using custom camera apps(e.g. igcamera).
09.10.2013 - Reverted camera orientation changes(colors should be ok right now, but igcamera orientation is again incorrect-need some more time to figure this out); data transfer statistics(download/upload arrows on the wifi icon) fixed(Quarx/Blachd0se); CM code synced(resolved Settings->Buttons crash and black camera preview after taking a picture).
02.10.2013 - Fixed multitouch points number setting; Igcamera should behave ok right now; CM code synced
30.09.2013 - Added switching to horizontal mode when hardware keyboard is open; CM code synced; NOTE: you may need to add google account again after update from previous version(s), so sync/backup your google stuff.
26.09.2013 - Call recording fixed(tried with AutoCallRecorder 1.0.9 - present in some tezet's ROM's); Some more work on internal storage; CM code synced
25.09.2013 - Internal storage size fixed
24.09.2013 - Keyboard layout fixed
23.09.2013 - Camera should work ok at 848x480(720p not supported yet); CM code synced
20.09.2013 - Initial version
NOTES:
Keyboard - to access polish letters, choose Qwerty polish in Settings->Language & Input->Sholes keypad->Set up keyboard layout. Use ALT LOCK or ALT LOCK + SHIFT to get polish letters. ALT LOCK + '?' is mapped to pipe symbol('|').
If you wish to see national symbols for some other language, please download and update the following file (similarly as Rabinhood has done for polish symbols(look at letter A and ralt/shift+ralt modifiers)), test it by replacing file /system/usr/keychars/sholes-keypad.kcm with your version(reboot required), and once you are satisfied with the outcome, send it to me.
Known issues:
If bluetooth is on, and autocallrecording is installed, no sound during calls(reported by Fedroid)
Sound quality when using BT headset is not very high
Wifi list does not refresh.. workaround: turn wifi off and on
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Installation
If coming from stock ROM or CM7:
install tezet's CM10 first(http://forum.xda-developers.com/showthread.php?t=1827801) and look at next point
If using tezet's CM10 ROM or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->custome recovery;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to ext4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If coming from engle mars's CM10.2 ROM(haven't tried it, but should work):
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->TWRP;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to EXT4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If want to get back to tezet's CM10 or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose tools->file tools->format data + cache to EXT3(not that you will loose your data(the ones on the sdcard are safe))
choose recovery->TWRP recovery
when in recovery, choose install zip from sdcard and instlall ROM you want.
in the same way install gapps(if not included in the ROM)
reboot
if something goes wrong... post here describing what's going on... there is a slight chance that someone will help you
Credits:
Credits for this rom goes to: Quarx2k, Tezet, Blachd0se, CM team... and many, many more.
czechop said:
CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
20.09.2013 - Initial version
Known issues:
Camera is far from good
Call recording not working
Hardware keyboard might produce incorrect characters when ALT used in some languages(polish version works quite well)
Notes:
For installation instructions look at other threads
Full wipe recommended!!!
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Click to expand...
Click to collapse
1. Fix camera, and it will be perfekt rom.
2. Just copy keyboard layout from CM10.2 of EngleMars.
3. Its very fast, and really nice ROM.
Bye
Faster than engle mars rom?
Can someone post photos how the rom looks like?
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
tezet is still alive! cm10.2 seems to become a really great and stable rom
you will find the qwertz keyfile attached. download and decompress it and change it, by replacing this file in system/usr/keychars and set permission to rw r r
cheers
Hey guys. I believe at least some of you have already tried this fresh ROM. Could you please share your comments? How does this ROM look like in comparison to Engle_Mars CM 10.2 in terms of performance and features? Do you think the differences make this ROM worth trying?
Thanks.
tezet said:
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
Click to expand...
Click to collapse
Hi Tezet... good to see you too You haven't posted anything for so long, that I started thinking you sold your phone and switched to some other brand. But after all, motorola is the best
Keyboard layout should be fine right now.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
Haven't noticed it earlier... thanks, will have a look.
downloading the rom to test.
After I have installed'll post a print for the curious :cyclops:
To those who have installed this:
- How is battery life compared to EngleMars's 10.2?
- Can this be backed up via recovery, ie does the restore function actually work?
These are the only two areas in which EngleMars's, otherwise perfect in my opinion, ROM is lacking.
first impression: very, very similar to the ROM CM10.2 Engle_Mars.
In visual and performance ... Very stable.
Surely in the next updates will be even better.:good:
{ Internal memory showing wrong size. (~ 254mb only) }
gigabruno said:
{ Internal memory showing wrong size. (~ 254mb only) }
Click to expand...
Click to collapse
Should be fixed in the newest version
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Installation guide for stock roms users
1) Root your phone (you may use SuperOneClick root method)
2) Install Droid2 Bootstrap Recovery
3) Open Droid2 Bootstrap Recovery and tap "Bootstrap Recovery", then "Reboot Recovery" granting root privileges. The phone should reboot into recovery. Use volume buttons to navigate, camera button to accept, power button to go back. You will install files by selecting "Install zip from sdcard".
4) Optionally: create a backup of your data
5) Install latest CM ROM image file.
6) Optionally: install Google Apps
7) Select "Wipe data/factory reset"
8) Reboot and enjoy
9) Optionally: select baseband version corresponding to your country and BPSW version
Click to expand...
Click to collapse
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
As it is not mentioned anywhere, am I correctly assuming that Bluetooth is working flawlessly?
I'm excited to try this but BT is crucial!
Have you tried the "TWRP Recovery"?
xyphur said:
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
Click to expand...
Click to collapse
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Here are the files you will need: http://www.mediafire.com/folder/1p23cv7r38491aq,nteg1stu575rjde/shared
gigabruno said:
Have you tried the "TWRP Recovery"?
Click to expand...
Click to collapse
I haven't yet, no. Of course, that may be because I was completely unaware of its existence, probably because most of these ROM release threads expect everyone reading them to know the ins and outs already... quite frustrating.
Is "TWRP 2.1.1" the latest available? Should I attempt to use that?
Appreciate the help btw...
---------- Post added at 08:43 AM ---------- Previous post was at 08:37 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
That seems.... exceptionally convoluted, lol... I'll give it a try though. Thanks for the link.
---------- Post added at 09:12 AM ---------- Previous post was at 08:43 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
xyphur said:
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
Click to expand...
Click to collapse
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
henediac said:
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
Click to expand...
Click to collapse
Got into CWM5 finally via the bootmenu... the CWM5 .zip file that was linked to earlier by lulli1 is "CyanogenDefy Recovery v5.0.3.4-jordan" if that matters.
It's still not accepting the latest release of this ROM though (25.09.2013), keeps claiming the following:
...
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Obviously there's something wrong somewhere... has anyone else successfully installed latest version?
This is really starting to frustrate me...
Maybe I should attempt TWRP method?
Thanks for the pointer abut vol down during blue LED... that's what I had forgotten and why I kept seeing the stock recovery menu. :S
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
Just verified the MD5 hash for the heck of it. File checks out OK.
Any ideas?