My USB is broken, which is the whole reason I'm in this mess. I'm in Boston too. Any other ideas you have would be greatly apprecaited.
[GUIDE] Compile CWM Recovery
- Thread starter Shaaan
- Start date
My USB is broken, which is the whole reason I'm in this mess. I'm in Boston too. Any other ideas you have would be greatly apprecaited.
Hi guys
Is it possible to compile CWM with prebuilt kernel and dt.img
If yes, how I have to set device tree makefiles?
Is it possible to compile CWM with prebuilt kernel and dt.img
If yes, how I have to set device tree makefiles?
when i type make -j4 otatools
grep: build/target/board/generic/recovery.fstab: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
build/core/prebuilt.mk:123: *** recipe commences before first target. Stop.
grep: build/target/board/generic/recovery.fstab: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
find: ‘out/target/common/docs/gen’: No such file or directory
build/core/prebuilt.mk:123: *** recipe commences before first target. Stop.
sorry sir @hali_fax @Shaaan
i want to ask about find out BOARD_FLASH_BLOCK_SIZE := ??
my recovery.fstab & fstab.redhookbay doesn't show recovery and boot partitions soo i can't check recovery & boot partitions size, do u have any solutions?
this recovery.fstab :
this fstab.redhookbay :
this list my block partitions :
thanks before sir
i want to ask about find out BOARD_FLASH_BLOCK_SIZE := ??
my recovery.fstab & fstab.redhookbay doesn't show recovery and boot partitions soo i can't check recovery & boot partitions size, do u have any solutions?
this recovery.fstab :
Code:
/dev/block/mmcblk0p1 /reserved hidden None length=0
/dev/block/mmcblk0p2 /panic raw None length=0
/dev/block/mmcblk0p3 /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0
/dev/block/mmcblk0p4 /spare ext4 defaults length=0
/dev/block/mmcblk0p5 /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0
/dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered length=0
/dev/block/mmcblk0p7 /logs ext4 nosuid,nodev,barrier=1,journal_async_commit,data=ordered length=0
/dev/block/mmcblk0p8 /system ext4 ro,noatime length=0
/dev/block/mmcblk0p9 /data ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard length=-16384
/dev/block/mmcblk0p10 /sdcard vfat defaults length=-16384
/dev/block/mmcblk1p1 /mnt/sdcard vfat defaults length=0this fstab.redhookbay :
Code:
/dev/block/mmcblk0p3 /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait
/dev/block/mmcblk0p8 /system ext4 ro,noatime wait
/dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered wait,check
/dev/block/mmcblk0p5 /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait
/dev/block/mmcblk0p9 /data ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard wait,check,encryptable=/factory/userdata_footer
/dev/block/mmcblk0p7 /logs ext4 nosuid,nodev,barrier=1,journal_async_commit,data=ordered wait
*/block/sd /storage/usbcard vfat None wait,voldmanaged=usbcard:auto
*/block/mmcblk1 /storage/sdcard_ext vfat None wait,voldmanaged=sdcard_ext:autothis list my block partitions :
Code:
root@K900:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30523392 mmcblk0
179 1 167936 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 32768 mmcblk0p3
179 4 131072 mmcblk0p4
179 5 131072 mmcblk0p5
179 6 786432 mmcblk0p6
179 7 262144 mmcblk0p7
179 8 1310720 mmcblk0p8
179 9 2097152 mmcblk0p9
179 10 25587695 mmcblk0p10
179 80 8192 mmcblk0gp0
179 60 4 mmcblk0rpmb
179 40 2048 mmcblk0boot1
179 20 2048 mmcblk0boot0
root@K900:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.2 GB, 31255953408 bytes
256 heads, 63 sectors/track, 3785 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 3786 30523391+ ee EFI GPTthanks before sir
Last edited:
Cmw for Acer
Is there cmw for Kobo Arc 7 and come for Acer z520:crying::laugh::crying::good::good::good::silly::silly::cyclops:
Is there cmw for Kobo Arc 7 and come for Acer z520:crying:
:laugh::crying::good::good::good::silly::silly::cyclops:sir i have i ball silde briiliant tablet , it is dead please help me to flash stock rom or help me to install another rom
it has intel processor ..
i am tired with google for solution
it has intel processor ..
i am tired with google for solution
That's not what this thread is for. You better look at your device forum. Also CWM is a dead horse, never disturb dead horses
TBM 13
Senior Member
sorry sir @hali_fax @Shaaan
i want to ask about find out BOARD_FLASH_BLOCK_SIZE := ??
my recovery.fstab & fstab.redhookbay doesn't show recovery and boot partitions soo i can't check recovery & boot partitions size, do u have any solutions?
this recovery.fstab :
Code:/dev/block/mmcblk0p1 /reserved hidden None length=0 /dev/block/mmcblk0p2 /panic raw None length=0 /dev/block/mmcblk0p3 /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0 /dev/block/mmcblk0p4 /spare ext4 defaults length=0 /dev/block/mmcblk0p5 /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered length=0 /dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered length=0 /dev/block/mmcblk0p7 /logs ext4 nosuid,nodev,barrier=1,journal_async_commit,data=ordered length=0 /dev/block/mmcblk0p8 /system ext4 ro,noatime length=0 /dev/block/mmcblk0p9 /data ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard length=-16384 /dev/block/mmcblk0p10 /sdcard vfat defaults length=-16384 /dev/block/mmcblk1p1 /mnt/sdcard vfat defaults length=0
this fstab.redhookbay :
Code:/dev/block/mmcblk0p3 /factory ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait /dev/block/mmcblk0p8 /system ext4 ro,noatime wait /dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered wait,check /dev/block/mmcblk0p5 /config ext4 nosuid,nodev,noatime,barrier=1,data=ordered wait /dev/block/mmcblk0p9 /data ext4 nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard wait,check,encryptable=/factory/userdata_footer /dev/block/mmcblk0p7 /logs ext4 nosuid,nodev,barrier=1,journal_async_commit,data=ordered wait */block/sd /storage/usbcard vfat None wait,voldmanaged=usbcard:auto */block/mmcblk1 /storage/sdcard_ext vfat None wait,voldmanaged=sdcard_ext:auto
this list my block partitions :
Code:root@K900:/ # cat /proc/partitions cat /proc/partitions major minor #blocks name 179 0 30523392 mmcblk0 179 1 167936 mmcblk0p1 179 2 8192 mmcblk0p2 179 3 32768 mmcblk0p3 179 4 131072 mmcblk0p4 179 5 131072 mmcblk0p5 179 6 786432 mmcblk0p6 179 7 262144 mmcblk0p7 179 8 1310720 mmcblk0p8 179 9 2097152 mmcblk0p9 179 10 25587695 mmcblk0p10 179 80 8192 mmcblk0gp0 179 60 4 mmcblk0rpmb 179 40 2048 mmcblk0boot1 179 20 2048 mmcblk0boot0 root@K900:/ # fdisk -l /dev/block/mmcblk0 fdisk -l /dev/block/mmcblk0 Disk /dev/block/mmcblk0: 31.2 GB, 31255953408 bytes 256 heads, 63 sectors/track, 3785 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 1 3786 30523391+ ee EFI GPT
thanks before sir
Same problem here, did u find any solution?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
129Hi. I am creating this guide because i did not find any particular functional guide with details.
You must be running a 64 or 32 bit version of Ubuntu. Please note that i wont be going in the details on how to setup a build environment and sync sources as there are many guides for that.
Step 1 :
Install the required packages
Step 2 :
Setup the build environment and sync the sources for the required CWM. CWM source comes bundled with the CyanogenMod source.
Code:CWM 5 - Gingerbread CWM 6 - Jellybean
Step 3 :
Now we come to the actuall compiling part. Make sure you have synced the latest source using the "repo sync" command.
Change directory to your source.
Issue this command :
Code:make -j4 otatools
Step 3.5 :
Do this step if your device is not officially supported by CM10.
Using terminal emulator on your device, issue the command
This will dump the boot image to your sdcard. Transfer it to your home directory.Code:dump_image boot /sdcard/boot.img
To build Android from source for a new device, you need to set up a board config and its makefiles. This is generally a long and tedious process. Luckily, if you are only building recovery, it is a lot easier. From the root of your Android source directory (assuming you've run envsetup.sh), run the following (substituting names appropriately):
For example if you are having the Samsung Galaxy Ace device, the command will go as follows :Code:build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
Code:build/tools/device/mkvendor.sh Samsung cooper ~/boot.img Please note that Cooper is the device name. Only use "~/boot.img" if you have the boot image in your home directory. Or else please specify the correct path.
You will receive the confirmation "Done!" if everything worked. The mkvendor.sh script will also have created the following directory in your Android source tree:
manufacturer_name/device_name
Step 3.5 ends here.
Step 4 :
Now that you have the device config ready, proceed.
Type the following code in your terminal in the source directory.
This will setup the build environment for you to work.Code:. build/envsetup.sh
Now launch the command
Code:lunch full_device_name-eng
This will set the build system up to build for your new device. Open up the directory in a file explorer or IDE. You should have the following files: AndroidBoard.mk, AndroidProducts.mk, BoardConfig.mk, device_.mk, kernel, system.prop, recovery.fstab, and vendorsetup.sh.
The two files you are interested in are recovery.fstab and kernel. The kernel in that directory is the stock one that was extracted from the boot.img that was provided earlier. For the most part, recovery.fstab will work on most devices that have mtd, emmc, or otherwise named partitions. But if not, recovery.fstab will need to be tweaked to support mounts and their mount points. For example, if your /sdcard mount is /dev/block/mmcblk1p1, you would need the following lines in your BoardConfig.mk
/sdcard vfat /dev/block/mmcblk1p1
Once the recovery.fstab has been properly setup, you can proceed to the next step.
Step 5 :
Now we build the actual recovery.
This command builds the recovery imageCode:make -j4 recoveryimage
You can use the command
to make a fakeflash recovery i.e. a temporary recovery to test out on the actual device.Code:make -j4 recoveryzip
Your recovery can then be found at "your_source_directory/OUT/target/product/device/recovery.img" and the temporary fakeflash zip in the utilities folder at the same location.
If everything works out well, you will have a working recovery.
Once you have working builds, notify "koush", on Github and he can build official releases and add ROM Manager support!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Some tips :
- If you want to compile CWM 6, sync the jellybean branch using the command :
Code:repo init -u git://github.com/CyanogenMod/android.git -b jellybean repo sync
- If you want to compile CWM 6 on a 32 bit system, you need to sync THIS source too. Instructions are given in the readme.
- Run "make clobber" between builds if you change the BoardConfig.mk, or the change will not get picked up.
Credits :
Koush for this guide.8I would like to ask if someone could compile CMW Recovery for my device Samsung GT-S7710 running JB? I do not know much about linux :/
I can provide the necessary files, and of course 30 euros donation via PayPal for working recovery
This is orginal revocery: http://www.mediafire.com/?was97s3r2wo97wk
orginal boot: http://www.mediafire.com/view/?st3aj5854r4l1sg
if you need some other files, please write4
Umm.. Weird.
Grab the unpackbootimg binary from out/host/linux-x86/bin/unpackbootimg and paste it to /usr/bin. Reboot.
Then run the make command again.2
If make otatools executed successfully the files should be there. But since they are not there, it didn't succeed!
Recovery and rom are two separate things. You can run any version of recovery on any version of a ROM.
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________ - If you want to compile CWM 6, sync the jellybean branch using the command :
