I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!
mexusbg said:
I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!
Click to expand...
Click to collapse
Just to clarify you are trying to mount the recovery.img on your PC?
thewadegeek said:
Just to clarify you are trying to mount the recovery.img on your PC?
Click to expand...
Click to collapse
Yeah I'm trying to mount the recovery.img and replace iunin recovery files with cwm's files.
I tried:
gunzip -c ../your-ramdisk-file | cpio -i
gzip: recovery.img: not in gzip format
cpio: premature end of archive
./split_bootimg.pl recovery.img
Android Magic not found in recovery.img. Giving up.
Also I don't have /dev/mtd/ ....
I've attached the recovery.img file if someone want's to check it out.
EDIT: I tired dsixda-Android-Kitchen and still cannot mount/unpack recovery.img.
EDIT2: List of other files in the update.zip:
zImage-GB-v746-2703 - KERNEL
system-GB-1.3-2703.ext4 (EXT4 image) - System
ramdisk-uboot-GB-1.3-2703.img - ramdisk
ramdisk-recovery-uboot-GB-1.0.img - recovery
Link to the whole firmware: https://dl.dropbox.com/u/41124284/A8HD/Firmware/um2703-GB-1.3-sdUp-381.zip
Please help me.
Related
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
xboxexpert said:
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
Click to expand...
Click to collapse
I would think once you have 3.0.1.0 then you should be all set for 2.2 (ext3 FS) or CM7 (ext4 FS) as 3.0.1.0 supports both while 3.0.0.5 only supports ext3 thus why it won't work with CM7 as has ext4 FS...
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
jtbnet said:
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
Click to expand...
Click to collapse
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
faceman66 said:
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
Click to expand...
Click to collapse
Yes I believe you are correct. Place both files on the recovery SD and when you want to flash with 3.0.0.5 for like he said "FROYO" , just flash the 3.0.5.0.zip and it will replace the recovery kernel and ramdisk. And when you feel like flashing CM7, just flash the zip for 3.0.1.0 and "vice versa" as xboxexpert said.
xboxexpert said:
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
Click to expand...
Click to collapse
Okay... so you are putting standard CWR 3.0.1.0 on the sdcard that can then be used to flash updates to EMMC as defined by your recovery.fstab... I guess the point being for folks who don't want flash CWR directly on EMMC so as to retain stock recovery...
First off, mods, if this is in the wrong place sorry, secondly, thanks for the help in advance.
I have dsixda's kitchen set up via cygwin, but do not have the proper files in the edify_defs folder so that the kitchen knows the proper mount points. What I am talking about is in the following bit quoted from the original kitchen thread.
WARNING: If your device is not listed in post #1 of this thread, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually only low-end devices use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
NOTE: This method does not guarantee your device will work with your custom ROM, however. Some devices may require more steps than just the edify_defs file, but the procedure is outside the scope of this FAQ. Ask around in the XDA sub-forum for your device if you need further help.
Click to expand...
Click to collapse
The devices I would like to add are both the first gen Nexus 7 (nakasi/grouper) and second gen Nexus 7 (flo). When I follow the instructions from that quoted section I am unable to make sense of the listed mount points and how to create the proper files. Any help is appreciated, thanks!
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
dark2099 said:
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
Click to expand...
Click to collapse
would like to add support for LG-E510, I've tried many times, help
---------- Post added at 07:59 PM ---------- Previous post was at 07:38 PM ----------
here is my fstab file:
# Mount point fstype device [device2]
/ boot mtd boot
/ cache yaffs2 cache
/ data yaffs2 userdata
/ misc mtd misc
/ recovery mtd recovery
/ sdcard vfat / dev/block/mmcblk0p1 / dev/block/mmcblk0
/ system yaffs2 system
help me
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
No one can help:good:
giltros1 said:
No one can help:good:
Click to expand...
Click to collapse
Mobile name?? version >> android
danger_beast said:
Mobile name?? version >> android
Click to expand...
Click to collapse
Mobile name: LG-E510, LG optimus Hub
Version android 2.3.6
Thanks
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
So if u got the ro.product.device ID (can be found in build.prop its easy then follow the steps above.....)
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Could u upload and pm me the files??
Could someone please help me with this recovery.fstab file for the hisense sero 7 lt tablet? It looks like the partitioning is messed up but im not completely sure. Im trying to make a partition file for android kitchen and thats why i need help with this recovery.fstab.
i cant attach the recovery.fstab so i'll copy and paste whats in it
recovery.fstab
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thank you for helping me!!
Well, I'm also in the progress of trying to figure this out, but try this:
get an ADB shell, or use a terminal app from the Play Store,
and execute:
Code:
cat /proc/mtd
That should give a list of partitions and their dev codes.
Tip: when posting files or code, try to make use of the code tags,
text inside them will be displayed with a monospaced font, so things will be more readable.
See more info here.
Thanks for the tip and I figured it out by using
cat /proc/partitions and cat /proc/mtd
Click to expand...
Click to collapse
those commands gave me the names of the partitions and what block number they are. Credit goes to Abdul_pt for giving me the partitions command credit goes to you hamc0re for helping me with the mtd command
Sent from my Amazon Otter2 using Tapatalk
Hey guys, I was recently given a Galaxy Tab 3 Lite (SM-T110) and have found very little roms considering its an old tablet and none are with my latest stock firmware. That said, I'm trying to implement this tablet into dsixda's kitchen but am having a little bit of trouble.
I have set up the kitchen successfully on Windows 10 using cygwin and have even complied a rom successfully but the problem is when I flash it it gives me errors about boot.img mounting points. I pretty much have 3 questions:
1. Cant find my boot mnt point and was wondering if someone can help me find it? (ill attach my recovery.fstab file in the bottom for you to see)
2. Dont really know if I need that "fix_boot2=yes" line? "fix_boot=yes" line? Or none? How can I tell if i need it?
3. Since boot mount point is not inside recovery.fstab file, does that mean it is not need to be mentioned?
I made a file called "goyawifi" inside the edify_defs folder with the following info inside it:
# Samsung Galaxy Tab 3 Lite SM-T110
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p15
cache_mnt=\/dev\/block\/mmcblk0p14
boot_mnt=\/dev\/block\/mmcblk0p15
data_mnt=\/dev\/block\/mmcblk0p16
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
And this is my recovery.fstab info:
#mount point fstype device [device2]
/mrd emmc /dev/block/mmcblk0p1
/mrd1 emmc /dev/block/mmcblk0p2
/mep2 emmc /dev/block/mmcblk0p3
/efs ext4 /dev/block/mmcblk0p4
/dtim emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p9
/kernel emmc /dev/block/mmcblk0p10
/radio emmc /dev/block/mmcblk0p11
/custom ext4 /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p16 length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/mnt/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Can anyone please help me to start customizing/flashing my rom? Thanks in advance...
FWI: When I say "successfully compiled a rom" I mean that the kitchen makes a rom, but upon flashing it, it gives me an error. Something about boot.img not mounted right
Bump! 45 views and no replies? So many developers here, surely someone knows the answer to my problems
Tried again to build a rom using dsixda's Android Kitchen, would like to find boot mount points... can anybody help?
Sorry, I don't have this device to test, but I think you should check "/kernel emmc /dev/block/mmcblk0p10"
Here should be the kernel image and maybe not the whole boot.img !
As you already know , boot.img have a kernel image and a ramdisk .... but on your device , ramdisk may be under /system ... I'm not 100% sure ... but from what you've posted so it seems !
So, there is no partition on your device for boot.img ... anyway you can make a custom rom also in this case, but you should know how to flash the new kernel image and also the ramdisk !
Unfortunately Samsung has made this device quite difficult for development, but not impossible .
Good luck !
I want to move /system /vendor /cache /data to microSD card by editing /vendor/etc/fstab.mt6765 and other files on /vendor.
modified /vendor/etc/fstab.mt6765
Code:
/dev/block/mmcblk1p2 / ext4 ro wait,recoveryonly
/dev/block/mmcblk1p3 /vendor ext4 ro wait,recoveryonly
/dev/block/mmcblk1p4 /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable
/dev/block/mmcblk1p5 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,reservedsize=128M,formattable
I have extracted vendor.img from OTA.zip and searched and replaced strings like
/dev/**/**/**/system with /dev/block/mmcblk1p2
and
/dev/**/**/**/data with /dev/block/mmcblk1p5.
I have unlocked the bootloader using
Code:
fastboot flashing unlock
.
I am not modifing /system. I will copy system.img from OTA.zip to sdcard using dd.
since I am not modifing /system I think it is safe. Is there possibility of issues with dm-verity?
Have I disabled dm-verity by unlocking the bootloader?
On an android-6 device with no /vendor partition I have moved /system /data /cache and /nvdata to sdcard by modifing boot.img.
But this android-9 device uses System-as-root ( /system is mounted at / ) and boot.img doesn't have fstab.** and .rc files. Some .rc files are in /system (mounted at / ) and other .rc files and fstab are in /vendor/etc/
Is it safe to flash modified vendor.img using
Code:
fastboot flash vendor vendor.img