[KERNEL][Unofficial CM11][F2FS Userdata][Overclock][TWRP 2.7.1.0][7/12] - 7" Kindle Fire HD Android Development

This will wipe EVERYTHING and i have not tested restoring any app data backups after restoring back to ext4->f2fs or f2fs->ext4.
Features
-Supports F2FS or EXT4 format on userdata partition - http://review.cyanogenmod.org/#/c/65480/
-CPU overclocking up to 1.728 GHz default 1.2 GHz
-GPU Overclock 512 MHz
-You have to flash the boot image after you flash any cm11 rom everytime
Source:https://github.com/Maromi-/kernel_omap_bowser-common
Changes
***Update 7/12***
-New boot.img allow usage of ext4 or f2fs on same partition
Bootimg_ext4orf2fs_CM11_Overclock_20140712.zip - 3.85 MB
MD5:ead39d8e659b3bc63518b0508a0e6ddb
****UPDATE 7/11 You can use current cm11 roms with this****
-You have to flash the boot image everytime after you flash a newer cm11 rom
-Previous TWRP F2FS users flash the zip below
zip-f2fs-kfhd7-twrp-2.7.1.0-recovery.zip - 6.36 MB
MD5:1700347b3c2890cbd63b265b07084920
-There should not be anyone using this with F2FS CWM and flash img below in fastboot
f2fs-kfhd7-twrp-2.7.1.0-recovery.img - 7.96 MB
MD5:c7a090f0aabcac06b34bda200b6bb89f
Instructions
clicking show content is consent of you alone taking a risk of app data not being able to be restored and/or brick
Prerequisites:
backup your needed app data and files on device and put on external backup device
NOTE:
Step 1: FILES
Download boot and recovery zips, place zips on device storage
EXT4 or F2FS Boot.img (supports both formats on same partition)
Bootimg_ext4orf2fs_CM11_Overclock_20140712.zip - 3.85 MB
MD5:ead39d8e659b3bc63518b0508a0e6ddb
TWRP 2.7.1.0. follow step 2 (DO NOT flash this unless you are going to use f2fs)
New_f2fs_user only-kfhd7-twrp-2.7.1.0-recovery.zip - 6.36 MB
MD5:145e935f919c45b4c4329b8d2d82e20a
Step 2: FLASHING
flash bootimg
flash recovery
reboot into recovery - The following steps will wipe backups,storage, app data
click wipe
click advanced wipe
select data and internal storage
click Repair or change file system
click change file system
click F2FS
reboot system
RESTORING USERDATA back to ext4 if needed also wipes storage again
reboot into recovery
click wipe
click advanced wipe
select data and internal storage
click Repair or change file system
click change file system
click EXT4
reboot system
Thanks
@Hashcode
http://teamw.in/about

older F2FS roms
4.4.3 rom
f2fs-cm-11-20140615-Overclock-tate.zip - 196.80 MB
MD5:61bfb395a9a30b7821e71030d32f5900
4.4.4 rom
f2fs-cm-11-20140621-Overclock-tate.zip - 196.85 MB
MD5:436a89b5061bcab5a5b93afaf9767df2
F2FS only Boot.img
f2fs_CM11_Bootimg.zip - 3.85 MB
MD5:df1cee328c7809af1d5d24c361b73a63
DO NOT USE, FOR REFERENCE ONLY CWM instructions(can't switch formats on the fly when switching roms)
F2FS cwm recovery
f2fs-tate-cwm-6.0.4.9.zip - 6.13 MB
MD5:8559ccebb17a113cefd62c01f98648bf
Step 2:
Power OFF the device
Boot into recovery
flash the ROM first
reboot into recovery
flash the recovery
reboot into recovery
NOTE: Until any formatting is done you can still go back and flash other roms and recoveries that do not use F2FS
Step 3:
Use volume rockers to scroll and power button to open menu
scroll to Mounts and Storage Menu press power button
use format /data and /data/media <--------------------------------------------when used this is the point of no return
reboot into recovery again
do a wipe data/factory reset
reboot device
Restoring back to EXT4 roms if using F2FS CWM Recovery(aka official rom builds)
This will wipe all data again so have your app data and restores backed up
***If you are running the FSF2 ClockworkMod recovery you need to flash twrp
flash recovery in fastboot
fastboot -i 0x1949 flash recovery f2fs-kfhd7-twrp-2.7.1.0-recovery.img
reboot into recovery
***
flash the rom
DO NOT REBOOT
go back to the main menu
click wipe
click advanced wipe
select data and internal storage
click Repair or change file system
click change file system
click EXT4
reboot system

*awaiting* (and, oh yeah, FIRST!)
Sent from my Amazon Tate using Tapatalk

Maromi said:
This will wipe EVERYTHING and i have not tested restoring any app data backups on this rom or after restoring back to non-F2FS Rom.
clicking show content is consent of you alone taking a risk of app data not being able to be restored and/or brick
Prerequisites:
Fully Charged Device
VERFIY
you can get into Fastboot (if something goes wrong or you want to go back and use non F2FS roms)
see:http://forum.xda-developers.com/showpost.php?p=37472472&postcount=1
BACKUP imgs and apps(many ways to backup) to externel media
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/current-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/current-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/current-system.img"
adb pull /sdcard/boot0block.img
adb pull /sdcard/current-boot.img
adb pull /sdcard/current-recovery.img
adb pull /sdcard/current-system.img
NOTE: Until any formatting is done you can still go back and flash other roms and recoveries that do not use F2FS
Step 1:
Download Files and place on device storage
F2FS rom
f2fs-cm-11-20140615-Overclock-tate.zip - 196.80 MB
MD5:61bfb395a9a30b7821e71030d32f5900
F2FS recovery
f2fs-tate-cwm-6.0.4.9.zip - 6.13 MB
MD5:8559ccebb17a113cefd62c01f98648bf
Step 2:
Power OFF the device
Boot into recovery
flash the ROM first
reboot into recovery
flash the recovery
reboot into recovery
NOTE: Until any formatting is done you can still go back and flash other roms and recoveries that do not use F2FS
Step 3:
Use volume rockers to scroll and power button to open menu
scroll to Mounts and Storage Menu press power button
use format /data and /data/media <--------------------------------------------when used this is the point of no return
reboot into recovery again
do a wipe data/factory reset
reboot device
Features
F2FS format on userdata partition rom and recovery
Linaro 4.9.1 -O2 optimized
CPU overclocking up to 1.728 GHz
GPU Overclock 512 MHz
Going back...
instructions wip
Source:https://github.com/Maromi-/kernel_omap_bowser-common haven't pushed commits yet
THANKS @Hashcode
Click to expand...
Click to collapse
Why not O3 optimized?
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
See this installing guide http://forum.xda-developers.com/showthread.php?p=53024798
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
Can you add some features of the galaxy nexus kernel I shared (for example SuperRam or Bestmem)?
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:35 PM ---------- Previous post was at 08:28 PM ----------
Your installation method is way better
Sent from my Amazon Tate using XDA Premium 4 mobile app

Looks like I am the first to download as well. Going down for a reboot now. Will report back!
Sent from my Amazon Tate using Tapatalk
EDIT: WOW! I noticed the speed increase immediately and when pulling a file via adb, the speed was reported to be 5870666 bytes/sec (roughly 5.6 Gigabytes/Sec, but I highly doubt it's THAT fast)

r3pwn said:
Looks like I am the first to download as well. Going down for a reboot now. Will report back!
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
And? Can you fell the change? I m going to wait until xposed support ART
Sent from my Amazon Tate using XDA Premium 4 mobile app

persano said:
And? Can you fell the change? I m going to wait until xposed support ART
Sent from my Amazon Tate using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I edited that post right after you quoted me. I just don't like xposed, so I went and enabled ART.
EDIT: WOOT WOOT! Over 13000 in Antutu X. That's only at 1.5Ghz, though.
Sent from my Amazon Tate using Tapatalk

persano said:
Why not O3 optimized?
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
See this installing guide http://forum.xda-developers.com/showthread.php?p=53024798
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
Can you add some features of the galaxy nexus kernel I shared (for example SuperRam or Bestmem)?
Sent from my Amazon Tate using XDA Premium 4 mobile app
---------- Post added at 08:35 PM ---------- Previous post was at 08:28 PM ----------
Your installation method is way better
Sent from my Amazon Tate using XDA Premium 4 mobile app
Click to expand...
Click to collapse
-O3 doesn't benefit as much as -O2 and the flashable zip for the ROM is 206 MBs

Maromi said:
-O3 doesn't benefit as much as -O2 and the flashable zip for the ROM is 206 MBs
Click to expand...
Click to collapse
I don't plan on going back because it's so amazing, but if someone wanted to, how would they go about doing so?
Sent from my Nexus 7 using Tapatalk

Is this good for M7 or just the nightlies?

Braves1995 said:
Is this good for M7 or just the nightlies?
Click to expand...
Click to collapse
It's not a kernel. It's a specially formatted ROM.
Sent from my Amazon Tate using Tapatalk

r3pwn said:
I don't plan on going back because it's so amazing, but if someone wanted to, how would they go about doing so?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
the easiest method(doesn't exist yet for our device)
flash a recovery(TWRP 2.7.10) that can mount F2FS and EXT4 for a particular partition and convert between formats
adb push <EXT4 rom> /data/media/0/
flash the rom
power off device
power on
done
FYI also you need to back-up app data again to external media before switching formats

Only Userdata & Media format in f2fs?
system still in ext4?
----------------------------------------------------------------------------
All working well exelent.!!!

Quimicax said:
Only Userdata & Media format in f2fs?
system still in ext4?
----------------------------------------------------------------------------
All working well exelent.!!!
Click to expand...
Click to collapse
Only userdata is F2FS

Maromi said:
Only userdata is F2FS
Click to expand...
Click to collapse
after flashing this, is it safe to update or switch ROMs?
Sent from my Amazon Tate using Tapatalk

xWolf13 said:
after flashing this, is it safe to update or switch ROMs?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
No.You can only use F2FS ROMs. I'll post a way to go back

Maromi said:
No.You can only use F2FS ROMs. I'll post a way to go back
Click to expand...
Click to collapse
Would it be okay to download a recovery for ext4, flash the recovery, flash an ext4 rom, then wipe data+sdcard before rebooting?
Sent from my Amazon Tate using Tapatalk

I'm still questioning to try this out. It will wipe my entire SD card or everything on device?
Sent from my Amazon Tate using Tapatalk

r3pwn said:
Would it be okay to download a recovery for ext4, flash the recovery, flash an ext4 rom, then wipe data+sdcard before rebooting?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
No. The ext4 recoveries won't recognize F2FS partitions

Maromi said:
No. The ext4 recoveries won't recognize F2FS partitions
Click to expand...
Click to collapse
Okay. Awaiting your conversion method. I miss nightlies.
Sent from my Amazon Tate using Tapatalk

Related

[RECOVERY] CWM based recovery v5.5.0.4 + repacked Touch CWM v5.8.1.8

ClockworkMod Recovery for the Transformer TF101​
NEW: Repack of Koush's touch clockworkmod recovery v5.8.1.8 to address the reboot to recovery issue.
This recovery is not mine and I take no credit for it. I only made a small change to the official recovery found here
and repacked it into a flashable zip.
Here is a diff of the hacky but working fix.
Code:
diff -Naur org/init.rc new/init.rc
--- org/init.rc 2012-04-02 21:18:24.875745175 +0100
+++ new/init.rc 2012-04-02 20:58:55.855745201 +0100
@@ -31,6 +31,8 @@
service ueventd /sbin/ueventd
critical
[COLOR="Green"]+service clearmisc /sbin/clear-misc.sh
+[/COLOR]
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
diff -Naur org/sbin/clear-misc.sh new/sbin/clear-misc.sh
--- org/sbin/clear-misc.sh 1970-01-01 01:00:00.000000000 +0100
+++ new/sbin/clear-misc.sh 2012-04-02 20:58:55.855745201 +0100
@@ -0,0 +1,4 @@
[COLOR="Green"]+#!/sbin/sh
+# This clears the boot flag from misc which forces
+# this device to continuously boot into recovery
+/sbin/dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13[/COLOR]
Even though these recoveries have been tested by me, I won't be responsible for any loss of data or any damages done by using it.
IF YOU ARE NEW HERE PLEASE READ THE NEXT LINE VERY CAREFULLY!
See here if you are having trouble with a recovery loop from another version of recovery...
Did you get that? Just in case please read it again before posting about not seeing recovery being updated!
Download
Touch Recovery v5.8.1.8 (repacked from official with the fix above)
MD5: 0b7f3c5986847e37c1dffcb53a9b79af
ClockworkMod Recovery v5.5.0.4 roach-tf101-r2
MD5: a352abf783746eb29a0f98159ca3c439
Changelog
v5.5.0.4 roach-tf101-r2
-Standard 5.5.0.4 recovery
-Installs from the Internal sdcard
-Tar backups (Not compatible with backups from version 3.2.0.1 and below)
-Power off option re-added as I find this useful
v3.2.0.1 roach-tf101-r1
- Fixed Dock keys (Left shift and Caps Lock were reversed)
- Added advanced backup from solarnz
- Tweaked mounts to improve performance
v3.1.0.1 (R3-240511-1908)
- Initial release for Asus Transformer
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method
Mod Edit:
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credit: http://forum.xda-developers.com/showthread.php?t=1093818
Older versions
v3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
gnufabio said:
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
Click to expand...
Click to collapse
I'm already on the case, the first post was just a taster of things to come.
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Working towards rom manager support too?
Sent from my Transformer TF101 using XDA Premium App
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
brookfield said:
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
Click to expand...
Click to collapse
It's not currently backed up by CWM because the transformer has no /boot partition. There is however another way to back this data up so you will see this in a future update.
006fazer said:
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Click to expand...
Click to collapse
I had the wrong link. fixed now.
Warboy said:
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
Click to expand...
Click to collapse
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
The ability to Install updated from the internal sdcard will be in the next version.
i download the good file, but upate don't work !
Roach, how did you compile it?
try this http://www.mediafire.com/?o4e36tmkd2xqb11
Roach made a small mistake making the update.zip. You simply have to rename /kernel folder to /recovery
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
love you roach!
Sent from my Transformer TF101 using XDA Premium App
david279 said:
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I uploaded the wrong file lol, fixed now and MD5 updated. Apologies for the inconvenience
gnufabio said:
Roach, how did you compile it?
Click to expand...
Click to collapse
I used ubuntu.
Awesome nice to see Clockwork Recovery being updated. Maybe after you're done working on this one, you could port TeamWin Recovery Project over too for fun or something I used to use Clockwork on my phone but then made the switch to TWRP for a new feel.
Source for TWRP: https://github.com/TeamWin/Team-Win-Recovery-Project/
TWRP Image: http://forum.xda-developers.com/showpost.php?p=16130864&postcount=263
Overall, feels cleaner.
Aside from that suggestion rant, this version looks nice and looking forward to your additional updates for Clockwork Recovery. Hoping for ROM Manager support in the future.
Roach2010 said:
I used ubuntu.
Click to expand...
Click to collapse
I meant: did you used make or android's mm?
gnufabio said:
I meant: did you used make or android's mm?
Click to expand...
Click to collapse
Oh, Sorry. I used make. You will need to setup a full build environment if you want to compile recovery.

[UNOFFICAL] CWM RECOVERY 6.0.2.7 Tested

Newest CWM build from CM10.1 source.
Tested on GB and JB
Not work on Froyo - tested
Not support RFS
Future work:
Need fix graphic
*DO IT AT YOUR OWN RISK*
INSTALL GUIDE:
-Download tar file
-Go to Download Mode
-Open Odin Multi Downloader
-Choose BENI.ops
-Tick One Package option
-Click One Package button and browse to tar file
-Start
-Done​CREDIT
CyanogenMod
CWM
Me - just compile​NOTICE
Small chance mess up boot flags.
Mount /system before install anything..
HOWTO fix: flash stock rom zzz or will find other way in future
​
Will test on GB...Thanks for this...:thumbup::thumbup:
Sent from my GT-S5670 using xda premium
Bro great
great job...:good::good:
Where`s the download link
Update info about recovery loop
-I don't know what reason make CWM ruin boot flags so Device will boot to recovery instead of normal boot.
to minimal the chance you should manually mount /system
-Will test on new update script. The old script marks as error in cwm error log...
Tried using custom graphics source for recovery ?
Nice waiting for it for so long....btw shudnt this be in original development section
So,I can start to install roms and other things with this recovery but just mount /system before do it?
Happy New Year!
Sent from my GT-S5670 using xda app-developers app
CWM-based Recovery v6.0.2.7 i flashed the image using recovery flash utility it flashed successfully ... i wiped my device then installed cm10 rom,,,,but when i " reboot system now " the recovery itself reboots ....it moves no further it reboots into recovery again and again as i click reboot system.... Somebody help on this....
mni ANKIT said:
CWM-based Recovery v6.0.2.7 i flashed the image using recovery flash utility it flashed successfully ... i wiped my device then installed cm10 rom,,,,but when i " reboot system now " the recovery itself reboots ....it moves no further it reboots into recovery again and again as i click reboot system.... Somebody help on this....
Click to expand...
Click to collapse
U should have read first post. ...!!
Sent from my GT-S5670 using xda premium
droider007 said:
U should have read first post. ...!!
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
My bad ,,, can provide me previous versions of CWM.zip flashable file...
mni ANKIT said:
My bad ,,, can provide me previous versions of CWM.zip flashable file...
Click to expand...
Click to collapse
Go to fit original development section.....there you will find it......it's by tj_style....
Sent from my GT-S5670 using xda premium
droider007 said:
Go to fit original development section.....there you will find it......it's by tj_style....
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
whereever i searched i got only .tar files with an image file in it ....i cannot use odin hence i need a .zip file flashable by current recovery......
zcop dude any updates as in are you still with this project or have you abandoned it.
no rush just asking.:good:

Tutorial [noob] How to Install CM11 ApexQTMO Clockworkmod .IMG file on Relay4G

I was looking for this for a long time and finally found it embedded in a thread here at XDA and thought it would be helpful to have a clean thread for installing the
1) Download latest supported recovery.img from http://forum.xda-developers.com/showthread.php?t=2528752
Currently: http://cmw.cmfs.me/apexqtmo/apexq_recovery-10.2.img
2) Place it at the root of your sdcard and rename it recovery.IMG
3) Download and install terminal emulator from the play store.
4) Run the terminal and
type: su (press enter)
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
Don't mess up the command or you WILL brick your phone.
5) Enjoy your Clockworkmod.
Note: I don't take any credit for this
Freaky way for flashing a recovery, just use clockworkmod recovery app from play store or use another tool (heimdall is pretty easy).
I prefer odin, then a flashable zip afterwards, I updated mine with Rom Manager before I found the right flash able. To each his own!
The reason I put this up is that the post for apexqtmo is a .img file, not a zip so i couldn't flash with existing.
I just assume that if they update CWM in the future it will also be in .img format, so for quick reference I made this how-to.
Feel free to post other methods
yohan4ws said:
The reason I put this up is that the post for apexqtmo is a .img file, not a zip so i couldn't flash with existing.
I just assume that if they update CWM in the future it will also be in .img format, so for quick reference I made this how-to.
Feel free to post other methods
Click to expand...
Click to collapse
You can just take any flashable CWM zip and replace the .img within with the one you want to flash. Using dd on the recovery partition sounds scary to me.
Other metod.
So is there any simple metod of doing that when I have img file on SD card?
I mean other than DD.
I have some old recovery CWM 6. something.
Is possible to do it without connecting to PC?
Try this
Download terminal emulator from play store (use the one by jack p)
su
flash_image recovery /sdcard/nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Download terminal emulator from play store (use the one by jack p)
su
flash_image recovery /sdcard/nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Isn't there an easy way to convert img to zip? Thanks
PS using cwm from the play store did the trick without terminal or imag to zip etc...
yes, its not hard to create your own .zip that is flashable in recovery
you just need to write your own updater-script and then grab the update-binary for you device
doesnt take but a few minuets, but if you dont want to do this using a terminal emulator is quick and painless too
how about adb?
yohan4ws said:
I
type: su (press enter)
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
Note: I don't take any credit for this
Click to expand...
Click to collapse
I can do this from adb can't I?
Yes
Sent from my Nexus 7 using XDA Premium 4 mobile app
If you screw up that dd command, you'll likely have some pretty big issues, depending upon where the recovery gets written to.
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexq_recovery-10.2-347.zip
Is a slightly updated version of CWM fully supported by TeamApexQ that works with CM 10.2, CM 11, and HypnoToad in an update.zip form, to flash from recovery.
This recovery is better (cmw based) and more up to date (also zip):
http://forum.xda-developers.com/showthread.php?t=2588646
Be wary of 'more up to date' recoveries. The one we support is able to flash images of Android 4.3.x and 4.4.x If you upgrade to a 4.4 based recovery, it will error on Android 4.3 Images.
Magamo said:
https://googledrive.com/host/0B-v962...y-10.2-347.zip
Is a slightly updated version of CWM fully supported by TeamApexQ that works with CM 10.2, CM 11, and HypnoToad in an update.zip form, to flash from recovery.
Click to expand...
Click to collapse
I am on Android 4.1.2 (from T-mobile) and from recovery CWM did nothing to me.
Or maybe change something - splash screen to Apex..
It is now v 6.0.4.4 and I believe it was that before update.
---------- Post added at 09:30 AM ---------- Previous post was at 09:14 AM ----------
robuser007 said:
This recovery is better (cmw based) and more up to date (also zip):
http://forum.xda-developers.com/showthread.php?t=2588646
Click to expand...
Click to collapse
This is what i would avoid as hell... touch version of recovery! OMG, any misstouch might make a lot of trouble I believe..
mazak23 said:
I am on Android 4.1.2 (from T-mobile) and from recovery CWM did nothing to me.
Or maybe change something - splash screen to Apex..
It is now v 6.0.4.4 and I believe it was that before update.
Click to expand...
Click to collapse
That is the updated version.
In general folks, you only need to update your recovery when a new image feature requires you to (Such as with Android 4.2's multi user/profile stuff, or Android 4.3/4.4's increased use of SELinux)

[GUIDE][SCRIPT] Install/Restore 4.1/4.2 ROMs without Odin

If you want to install or restore a CM10.1-based or stock-based ROM while you are on CM10.2/11 based ROM without using Odin you are into right place.
Automatic process with Recovery-flashable zip:
Download Format-Preload-RecoveryModeV2.zip and put it into sdcard
Reboot device in recovery and install the zip, no need to reboot after flashing
Now you can install or restore any CM10.1-based ROM!!
Semi-automatic process with Linux/Windows script - needs ADB
To use only if Automatic process doesn't work for you
Reboot device in recovery and connect to USB
Download Format zip depending on your OS. Then:
On Windows: Extract zip, copy extracted file to the same directory where is ADB executable and double click .bat
On Linux: Extract zip where you want, for example your home directory, and run it in Terminal with . PreloadFormat.sh
Click to expand...
Click to collapse
Manual process with ADB
To use only if either Automatic and Semi-automatic don't work for you
Boot device into recovery mode, connect it to USB
Open ADB and type in order:
Code:
[B]adb devices[/B] (to be sure that device is recognized, you see some numbers followed by "recovery" word)
[B]adb shell
su
parted /dev/block/mmcblk0
mkfs
(now wait 2 sec and confirm with Y)
9
ext2[/B]
Little explanation: Preload partition is used as swap partition from CM10.2 and up in our device, without formatting it (format /preload when is a swap partition doesn't work in CWM, at least for me. Parted can't format in ext4, so we need to format in ext2) you get bootloop when you install/restore a 10.1 ROM.
There is one more way too without using pc and adb..
Boot into recovery and format /system.(optional)
Now install any CM10.1 ROM on top of CM10.2.
Then go to advance option in CWM recovery and choose "reboot recovery".
Now when phone reboots into recovery, go to mount and storage and format /preload and /data.
Now reboot.
The rom will boot up normally.
I was on carbon ROM and successfully booted the MIUI using the following method..
Thanks to @Toni5830 for letting me know this method..
dagger said:
There is one more way too without using pc and adb..
Boot into recovery and format /system.(optional)
Now install any CM10.1 ROM on top of CM10.2.
Then go to advance option in CWM recovery and choose "reboot recovery".
Now when phone reboots into recovery, go to mount and storage and format /preload and /data.
Now reboot.
The rom will boot up normally.
I was on carbon ROM and successfully booted the MIUI using the following method..
Thanks to @Toni5830 for letting me know this method..
Click to expand...
Click to collapse
...but I have to use my method all the times because format /preload never works for me with Toni's guide
Inviato dal mio GT-I9070
Tesla-MADAL93 said:
...but I have to use my method all the times because format /preload never works for me with Toni's guide
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
Format /preload won't work if formatting it with the recovery in cm10.2.
That's why i said to reboot recovery so as to enter into cm10.1 recovery..
Sent from my GT-I9070 using Tapatalk
dagger said:
Format /preload won't work if formatting it with the recovery in cm10.2.
That's why i said to reboot recovery so as to enter into cm10.1 recovery..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Yes, it doesn't work on CM10.1 too! Maybe because my device is repartitioned and /preload space is around 128 KB.
Inviato dal mio GT-I9070
Tesla-MADAL93 said:
Yes, it doesn't work on CM10.1 too! Maybe because my device is repartitioned and /preload space is around 128 KB.
Inviato dal mio GT-I9070
Click to expand...
Click to collapse
Ah..
Maybe that's why..
Sent from my GT-I9070 using Tapatalk
Added script for Windows to automate this operation! Soon for Linux and CWM Recovery too
EDIT: Added for Linux too
Modified OP, flashable zip for recovery is ready
Inviato dal mio GT-I9070
Works like a charm thanks a lot
Tesla-MADAL93 said:
Download Format-Preload-RecoveryMode.zip from attachments and put it into sdcard[/B]
Reboot device in recovery, make sure that /system partition is mounted under mounts and storage and flash zip file, no need to reboot after flashing
Now you can install or restore any CM10.1-based ROM!!
Click to expand...
Click to collapse
It worked for CM10.2.
Last night I returned to the CM10.1 from CM10.2, and all I had to do isto have already downloaded all the zip on the card, follow the procedure from OP and everything was impeccable with your script.
Thanks @Tesla-MADAL93
it works..thanks.. :good::laugh:
dagger said:
There is one more way too without using pc and adb..
Boot into recovery and format /system.(optional)
Now install any CM10.1 ROM on top of CM10.2.
Then go to advance option in CWM recovery and choose "reboot recovery".
Now when phone reboots into recovery, go to mount and storage and format /preload and /data.
Now reboot.
The rom will boot up normally.
I was on carbon ROM and successfully booted the MIUI using the following method..
Thanks to @Toni5830 for letting me know this method..
Click to expand...
Click to collapse
@dagger does this method work if i want to downgrade from CM11 to cm10.1
shadytarek_97 said:
@dagger does this method work if i want to downgrade from CM11 to cm10.1
Click to expand...
Click to collapse
I don't think that it works on cm11..
This method only works for installing cm10.1 from cm10.2.
You can't flash a 4.3 or 4.2 ROM from the cm11 recovery as it gives an error in the flashing process..
Sent from my GT-I9070 using Tapatalk
dagger said:
I don't think that it works on cm11..
This method only works for installing cm10.1 from cm10.2.
You can't flash a 4.3 or 4.2 ROM from the cm11 recovery as it gives an error in the flashing process..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
but tesla's automatic process mentioned in op works with cm11 right ??
shadytarek_97 said:
but tesla's automatic process mentioned in op works with cm11 right ??
Click to expand...
Click to collapse
CM10.2 and CM11 uses preload partition as swap, so you can install CM11/10.2 based ROM over CM11/10.2 based ROM without using this. You can't downgrade to previous versions without this or flashing stock firmware.
shut_down said:
CM10.2 and CM11 uses preload partition as swap, so you can install CM11/10.2 based ROM over CM11/10.2 based ROM without using this. You can't downgrade to previous versions without this or flashing stock firmware.
Click to expand...
Click to collapse
But if you try to install a cm10.2 based ROM on cm11 based ROM, don't you get an error??
Sent from my GT-I9070 using Tapatalk
dagger said:
But if you try to install a cm10.2 based ROM on cm11 based ROM, don't you get an error??
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I think I installed CM11 before, over CM10.2 - with system wipe. but now I am not 100% sure that I remember it right.
shut_down said:
I think I installed CM11 before, over CM10.2 - with system wipe. but now I am not 100% sure that I remember it right.
Click to expand...
Click to collapse
Cm11 over cm 10.2 will install fine..
But cm10.2 over cm11 will give error.
Sent from my GT-I9070 using Tapatalk
Sorry for noob question but as OP says; Make sure that /system partition is mounted under mounts and storage
What do I need to do in CWM
unmount /system ?
coffeecore said:
Sorry for noob question but as OP says; Make sure that /system partition is mounted under mounts and storage
What do I need to do in CWM
unmount /system ?
Click to expand...
Click to collapse
No, leave it mounted if it is.

[CWM][DEV] ClockWorkMod 6.0.1.2 - BroadcomCM [TOTORO]

CLOCKWORKMOD RECOVERY 6.0.1.2
Click to expand...
Click to collapse
This is the CWM recovery found on the latest CM9 sources.
INSTALLATION
Click to expand...
Click to collapse
Download the update.zip found here
Place it on your SD card
Flash it on your actual recovery (doesn't matter if it's stock one)
USAGE
Click to expand...
Click to collapse
Press home + volume up + home button to enter
Our sources can be found on BroadcomCM Github
reserved
@op why does it says v6.0.0.7 in screenshot instead of 6.0.1.2 ?
Sent from my GT-P3110 using Tapatalk
did not work for me..status 7 on cm11 and is not resize for galaxy y
Hello sir ..
i flashed this cwm.. it worked but is there any bug in it ??? when select install zip from sdcard or make a backup or restore , it shows can't mount sdcard for every option ..
Showing error as "Error while mounting /data"
On stock Rom, stock kernel..
---------- Post added at 06:37 AM ---------- Previous post was at 06:37 AM ----------
shankarsj said:
i flashed this cwm.. it worked but is there any bug in it ??? when select install zip from sdcard or make a backup or restore , it shows can't mount sdcard for every option ..
Click to expand...
Click to collapse
Its mounting sdcard but not data..
---------- Post added at 06:41 AM ---------- Previous post was at 06:37 AM ----------
Fallen_Knight said:
did not work for me..status 7 on cm11 and is not resize for galaxy y
Click to expand...
Click to collapse
This cwm is resized for SGY... Im not sure, bt it should work on Cm11 as its Temp.CWM
---------- Post added at 06:42 AM ---------- Previous post was at 06:41 AM ----------
kundancool said:
@op why does it says v6.0.0.7 in screenshot instead of 6.0.1.2 ?
Sent from my GT-P3110 using Tapatalk
Click to expand...
Click to collapse
Because its not the screenshot from SGY!
Check the line above SS...
---------- Post added at 07:09 AM ---------- Previous post was at 06:42 AM ----------
@bieltv.3 , I cant mount Data
For people who get error mounting data
Simply flash this cwm
Flash the rom zip (this will install the kernel)
Reboot to recovery
Format system data cache
Mount system data cache
Flash the rom zip again
Restart
For me it shows..
Can't mount sdcard when i try install zip from sdcard really... actually i flashed for galaxy pocket it worked dont say now how it worked i will send ss also wait ..
shankarsj said:
Can't mount sdcard when i try install zip from sdcard really... actually i flashed for galaxy pocket it worked dont say now how it worked i will send ss also wait ..
Click to expand...
Click to collapse
Hmm its more likely than Galaxy pocket uses another location for Sdcard. Compare the recovery.fstab files of this CWN zip and the one you yave on cori
I like ur works alott sir ...
so sir i need to replace that file with my pocket cwm file right
i will ..
Thanks sir
---------- Post added at 08:17 AM ---------- Previous post was at 07:52 AM ----------
bieltv.3 said:
Hmm its more likely than Galaxy pocket uses another location for Sdcard. Compare the recovery.fstab files of this CWN zip and the one you yave on cori
Click to expand...
Click to collapse
Sir you are awesomee.. it worked can mount sdcard and extsdcard to .. i think now i can flash roms from sdcards right ???
But last bug for pocket is when click reboot system now
it just shows rebooting only not able to go to homescreen Help pleasee
shankarsj said:
so sir i need to replace that file with my pocket cwm file right
i will ..
Thanks sir
---------- Post added at 08:17 AM ---------- Previous post was at 07:52 AM ----------
Sir you are awesomee.. it worked can mount sdcard and extsdcard to .. i think now i can flash roms from sdcards right ???
But last bug for pocket is when click reboot system now
it just shows rebooting only not able to go to homescreen Help pleasee
Click to expand...
Click to collapse
This was happening too. Kernel modifications are needed. Try to use mackief kernel
sir .. im using galaxy pocket
Should i flash mackief kernel on galaxy pocket ??? Really should i ??
And sir can i make a thread for galaxy pocket of cwm 6.0 in miscelns development section please not able to pm you ??
@bieltv.3 bug reports:
1. system & cache is mounted when i enter into the recovery but when i unmount & mount again,they don't mount.
2. data & sd-ext can't be mounted.recovery.log attached.
3. when clicking to backup,recovery background image turns into huge big & some portion is blacked.screenshot attached.
i didn't test further such as wiping battery stats,dalvik cache,formatting,flashing etc. i tested only above mentioned on my galaxy y duos,running stock 2.3.6 rom.
killoid said:
@bieltv.3 bug reports:
1. system & cache is mounted when i enter into the recovery but when i unmount & mount again,they don't mount.
2. data & sd-ext can't be mounted.recovery.log attached.
3. when clicking to backup,recovery background image turns into huge big & some portion is blacked.screenshot attached.
i didn't test further such as wiping battery stats,dalvik cache,formatting,flashing etc. i tested only above mentioned on my galaxy y duos,running stock 2.3.6 rom.
Click to expand...
Click to collapse
This CWM is only compatible with EXT4 filedystem. I should add that info to the firdt post
Works.......
Works perfectly fine on galaxy pocket with some modifications.....Needs to be resized though....But, my question is, can it flash CM11? (not on pocket but on totoro)....
akhbh said:
Works perfectly fine on galaxy pocket with some modifications.....Needs to be resized though....But, my question is, can it flash CM11? (not on pocket but on totoro)....
Click to expand...
Click to collapse
yes it can flash cm11
of course you need to be on ext first or flash the cm11 rom (this will install the kernel) reboot to recovery format system data cache mount system data cache and flash the rom zip again
would be easier just flashing the kernel with cwm built in if you are using totoro
if you get status 7 errors it means your phone doesnt currently have the correct build prop - you can either
remove the lines that check for the prop in the updater script of the rom
flash cm7 first
try flashing my buildprop first that I posted in the cm11 general section
So sir ..
marcussmith2626 said:
yes it can flash cm11
of course you need to be on ext first or flash the cm11 rom (this will install the kernel) reboot to recovery format system data cache mount system data cache and flash the rom zip again
would be easier just flashing the kernel with cwm built in if you are using totoro
if you get status 7 errors it means your phone doesnt currently have the correct build prop - you can either
remove the lines that check for the prop in the updater script of the rom
flash cm7 first
try flashing my buildprop first that I posted in the cm11 general section
Click to expand...
Click to collapse
i and akhbh are getting status7 error we tried what steps you have said now but in vain . .
shankarsj said:
i and akhbh are getting status7 error we tried what steps you have said now but in vain . .
Click to expand...
Click to collapse
you cant have done all the steps
if you have flashed and got a working cm7 it would be impossible to get status 7 errors
also if you mounted system and flashed my build prop (note if you use this recovery you must already be on ext - if not use cmw 5 to flash my build prop file) and rebooted to recovery you would also have the correct build prop (your current rom will no longer boot) then you can flash cwm 6 and not have status 7 errors
@marcuss smith sorry but u are wrong
Flashing cm11 needs kernel modification
Just but boot.img from cm11 to a Kernel zip (Kernel cm7 totoro for example) then flash it
And now flash cm11
Sent from my Nexus 5 using XDA Premium 4 mobile app
myaservip said:
@marcuss smith sorry but u are wrong
Flashing cm11 needs kernel modification
Just but boot.img from cm11 to a Kernel zip (Kernel cm7 totoro for example) then flash it
And now flash cm11
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
in what part am I wrong -
The cm 11 rom zip contains the kernel therefore you can flash this temp cwm and them flash the rom zip - in the process you are flashing the kernel - you can then reboot to recovery format system data cache to convert to ext mount everything again and then flash the rom zip -
Of course it would be much easier to just flash the kernel with the cwm6 built in and reboot to recovery and format system data cache and then mount everything and flash the rom zip - but if you are on ext anyway then you can just use this and flash the rom zip - will still work
Job done except if you have status 7 error
the reason I said its easier if you on cm7 is because of the following
stock rom build.prop is - GT-S5360
cm7 build.prop is - totoro
in order to flash the cm11 rom zip without status 7 error you need your build prop to say your device is totoro
Thats why I said you can either remove this requirement from the updater script - be on cm7 first - or flash my build.prop in order for it to say your device id is totoro

Categories

Resources