I was wondering if anyone had a file for the Amaze to go in the edify_defs folder in the kitchen. Or if someone could help me finishing filling it out.
Thanks!
Code:
#
# The values below should be set in each file in this folder.
#
# Each file represents a device name (set in ro.product.device of
# build.prop)
#
# If yes, then this device requires changing the mount point
# names in the new updater-script or update-script
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL
change_mnt=yes
# If yes, the device is by Dell and requires changing the mount
# point names in the new updater-script or update-script
change_mnt_dell=no
#
# NOTE: The update-script will be converted to updater-script if the
# definition file for the device exists. If 'change_mnt' or
# 'change_mnt_dell' are set to 'yes' then the mount names will
# also be changed.
#
# Mention the mount point names if change_mnt=yes
# Use '\/' instead of '/'
# e.g. sys_mnt=\/dev\/block\/mcblk0p25
#
# If unknown, set to: ???
sys_mnt=\/dev\/block\/mmcblk0p29
cache_mnt=\/dev\/block\/mmcblk0p30
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=???
sdcard_mnt=???
# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2
modem_mnt=
# Set this mount point if you know what it is (e.g. on Motorola Atrix)
webtop_mnt=
# Filesystem info for SYSTEM/DATA/CACHE/etc.
# e.g. param1=ext3, param2=EMMC
param1=
param2=
# If SDCARD filesystem is different from above, then mention it
# e.g. param1_sdcard=vfat, param2_sdcard=MTD
param1_sdcard=
param2_sdcard=
# If CACHE filesystem is different from above, then mention it
param1_cache=
param2_cache=
# If yes, the device does not require using a 'tmp' folder when
# flashing the boot.img in the updater-script
#
# e.g. package_extract_file("boot.img", "/dev/block/blah1");
fix_boot=no
# If yes, the device requires a 'tmp' folder when flashing the
# boot.img in the updater-script, PLUS the boot partition name
# needs to be used, rather than just 'boot'
#
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
# with: write_raw_image("/tmp/boot.img", "/dev/block/blah1")
fix_boot2=no
# If yes, the device requires a 'dd' command to write the boot.img
#
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
# with: run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/blah")
fix_boot3=no
# Device uses /cache instead of /tmp, e.g. when writing boot.img
use_cache_not_tmp=no
This should help.
Cayniarb said:
These are the partition mounts on the Amaze 4G:
Code:
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 00040000 00000200 "pdata"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p21: 02000000 00000200 "adsp"
mmcblk0p19: 007ffc00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
mmcblk0p18: 02800000 00000200 "mdm9k"
mmcblk0p20: 007ffa00 00000200 "mdm9k_config"
mmcblk0p27: 00400000 00000200 "mdm_efs1"
mmcblk0p28: 00400000 00000200 "mdm_efs2"
Click to expand...
Click to collapse
Thanks, I got that far. I need everything after the mount points lol
Draciel882 said:
Thanks, I got that far. I need everything after the mount points lol
Click to expand...
Click to collapse
Try taking a file specifically for a similar device (one with two storage mounts) and simply edit it to match the specifications for the Amaze. That's what I did. Sorry but I don't have it anymore.
Binary100100 said:
Try taking a file specifically for a similar device (one with two storage mounts) and simply edit it to match the specifications for the Amaze. That's what I did. Sorry but I don't have it anymore.
Click to expand...
Click to collapse
Thanks anyways haha I was hoping someone would provide me with the file they used.
Sent from my Bulletproof Amaze 4G from xda premium
I've filled in everything I can from what you posted and what I cross referenced from the HTC Flyer file and this is the result of unpacking the rom:
Code:
Creating working folder WORKING_AMAZE_TEST1 ...
Extracting ROM ...
Renaming ...
boot_signed.img -> boot.img
Found system.img
Found boot.img
adsp.img
dzdata_16g.hdr
dzdata_16g.img
dzdata_4g.hdr
dzdata_4g.img
hboot_8x60-lte_1.90.0008_20111101_signedbyaa.nb0
mdm9k.img
mdmrcdata.img
nfc_106.img
pg2fs_spcustom.img
ramdisk.img
rpm.img
sbl1.img
sbl2.img
sbl3.img
tz.img
Adding an update-script ...
od: illegal option -- -
usage: od [-aBbcDdeFfHhIiLlOosvXx] [-A base] [-j skip] [-N length] [-t type]
[[+]offset[.][Bb]] [file ...]
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Fuse installed
Trying to mount the filesystem
dyld: Library not loaded: /usr/local/lib/libfuse.2.dylib
Referenced from: /usr/local/bin/fuse-ext2
Reason: image not found
Filesystem mounted
File system listed, analyzing
Failed to mount the filesystem: mount point empty
Error: No /system/framework folder found!
Press Enter to continue
Anyone?
mount points
Did you figure this out, if so could you send me the template of yours
Umm out of curiosity, what are working on here?
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk
DEFINITIONOFREAL said:
Did you figure this out, if so could you send me the template of yours
Click to expand...
Click to collapse
My problem was because I was in OSX. But I moved to Ubuntu and everything worked like a charm.
Sent from my Bulletproof HTC Amaze 4G
Did anyone create the template? If so, can I have it lol? I tried changing it using what Binary gave but i can't find it for data and sdcard
Please keep all question based threads in the Q&A section.
Thread Moved.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
Related
How to pull boot.img from neo v ROM..?
Use 7zip and flash it with flashboot
Sent from my MT15i using xda premium
But I cannot find Boot.img in any part of the rom in Neo v please help
dendenny01 said:
How to pull boot.img from neo v ROM..?
Click to expand...
Click to collapse
May I ask why you need .img of stock kernel?
I want edit edit ramdisk and kernel
dendenny01 said:
I want edit edit ramdisk and kernel
Click to expand...
Click to collapse
I didn't find way to get .img from .sin, but I packed zImage(compiled from source) and kernel.elf.ramdisk.gz(which I got from flashtool->elf extract) into .img so please test it(before you edit it), as I'm not on stock rom, but I did seen boot logo, so it does boot.
I think if you've unlocked the bootloader you can boot `recoveryNeo.img` (the CWM image) and just create a backup?
alvinwong_1234 said:
and just create a backup?
Click to expand...
Click to collapse
of what? kernel? erm, no can do
You can try opening a shell to your phone via adb shell, then type 'su' to get root permissions then type:
Code:
#cat /proc/mtd
And you should get something like this:
Code:
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
To get the boot.img use this command:
Code:
# cat /dev/mtd/mtd2 > /sdcard/boot.img
Hi, I'm working on creating a custom CWM Flashable ROM (zopo zp900).
I'm making a updater script, but I'm having trouble finding all the partitions for my phone, especially the /boot partition.
See the quote down there, that's what I'm trying to achieve except for my device.
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 22dffe00 00000200 "system"
mmcblk0p29: 09800000 00000200 "lib"
mmcblk0p27: 090efc00 00000200 "cache"
mmcblk0p26: 496ffe00 00000200 "userdata"
mmcblk0p30: 014bfe00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p28: 00010000 00000200 "extra"
Click to expand...
Click to collapse
Many THANKS!
tehPanda said:
Hi, I'm working on creating a custom CWM Flashable ROM (zopo zp900).
I'm making a updater script, but I'm having trouble finding all the partitions for my phone, especially the /boot partition.
See the quote down there, that's what I'm trying to achieve except for my device.
Many THANKS!
Click to expand...
Click to collapse
The boot partition may not be visible to the Linux kernel.
$ cat /proc/mtd
$ ls -l /dev/block
$ mount
Also, have a look in /init.*rc for mount points and run "dmesg" on your newly booted device. The device may be of type mtd or mmc and they are treated quite differently.
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
xorkrus said:
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
Click to expand...
Click to collapse
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Sent from my SCH-I535 using xda premium
shimp208 said:
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Click to expand...
Click to collapse
View attachment mounts.txt
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
xorkrus said:
View attachment 1395857
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
Click to expand...
Click to collapse
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
Code:
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
From here you should be able to tell which ones is boot, recovery, etc.
shimp208 said:
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
From here you should be able to tell which ones is boot, recovery, etc.
Click to expand...
Click to collapse
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
xorkrus said:
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
Click to expand...
Click to collapse
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
kuisma said:
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
Click to expand...
Click to collapse
View attachment fdisk.txt
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
xorkrus said:
View attachment 1409237
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
Click to expand...
Click to collapse
You already know system, cache and data. Also, root and boot lives in the same partition.
So the past few days i have been working on porting clockworkmod to my tablet Vexia Navlet 2 White (cpu telechip tcc892x, board m805_892x_evm), i have setup a build environment and managed to make a bootable CWM but have reached a bit of a wall, my recovery dont mount anything ><
And so i have a few doubts:
1 -
In boardconfig.mk
i have these lines
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00a00000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00a00000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x19000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x39800000
BOARD_FLASH_BLOCK_SIZE := 131072
the size must be set based on the cat /proc/mtd result (or so it says on the different guides i found)
Code:
dev: size erasesize name
mtd0: 00a00000 00200000 "boot"
mtd1: 00600000 00200000 "kpanic"
mtd2: 19000000 00200000 "system"
mtd3: 00400000 00200000 "splash"
mtd4: 09600000 00200000 "cache"
mtd5: 39800000 00200000 "userdata"
mtd6: 00a00000 00200000 "recovery"
mtd7: 00200000 00200000 "misc"
mtd8: 00200000 00200000 "tcc"
after searching on the forums and googling i saw that some people use the hexadecimal value of the column size but other people convert it to decimal, what is the right way? are both okay? is the code from my boardconfig.mk up there ok?
2 -
Code:
BOARD_FLASH_BLOCK_SIZE := 131072
This value, after researching it seems that this must be the decimal converted value of the erase column
Code:
mtd8: 00200000 00200000 "tcc"
in this case 00200000 (hex) -> 2097152 (dec), but if i set this value i get and boot.img too big error, i dont know if this is the reason of the mounting not working, but leaving the default value i can make it and the recovery boot
And the at last (i couldnt post everything together for some reason :S)
3 -
The main problem i have with all guides is
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.
Click to expand...
Click to collapse
how the hell im supossed to add the lines on the boardconfig.mk?, if i do it like this it fail
Code:
(...)
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/unknown/m805_892x/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
/sdcard vfat /dev/block/mmcblk0
i have been looking at boardconfig.mk others devices and the use something like this, which i tried and didnt work
Example:
Code:
BOARD_DATA_DEVICE := /dev/block/mmcblk0p5
BOARD_DATA_FILESYSTEM := auto
BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/ndda1
BOARD_SDEXT_DEVICE := /dev/block/mmcblk0
How im supossed to make the mounting work? >< pls help me, explain this to my because i just dont get it at all sorry and thx
Here attached what i have already done, and what i used V
I've run into quite a bit of trouble with my Evo 4GLTE today. Seems I can no longer mount /data. I can boot into recovery and have twrp 2.5 installed. I've gone as far back as 2.4.1 but no further as earlier editions don't support the v2.5 touch driver. I'm HTC Dev Unlocked & S-ON.
Anyhow, I have no nand backup. Lucky me. RUU is useless as the 3.15 doesn't want to install when a 3.16 base is present. Beyond trying to fix up stuff with JET and superCID- it seems if I only knew to which partition /data is supposed to mount, then I could take action on that and do something useful. TWRP is working and I can get an ADB terminal session running, but that's about it.
My one and only goal is to just install a ROM. Any ROM, I don't care which at this point. TWRP gives me a unable to mount '/data' error.
Here's what the device looks like (conspicuously missing /data)
cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p35: 4dfffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 89fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p38: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p34: 060e9c00 00000200 "reserve"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 00040000 00000200 "skylink"
mmcblk0p33: 00040000 00000200 "cdma_record"
mmcblk0p34: 060e9c00 00000200 "reserve"
Any ideas?
ttmcmurry said:
cat /proc/emmc
dev: size erasesize name
mmcblk0p37: 89fffe00 00000200 "userdata"
Click to expand...
Click to collapse
Sometimes all I need to do Is complain about something and the answer strikes shortly thereafter....
So I made a gross assumption that "userdata" = /data.
When I attempted to e2fsck the device (/dev/block/mmcblk0p37), it couldn't read the block at all, just errored out.
I figured since the partition type was showing up as unknown (parted /dev/block/mmcblk0, print), that I might as well format it. I know the device is on 4K blocks, so it wasn't a stretch of the imagination to make an educated guess what to do next:
mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p37
e2fsck -y /dev/block/mmcblk037
Reboot, install a ROM, and voila. I have a useable phone again.
Let it be known that if you have 3.16 installed, using an earlier RUU again is useless. There isn't a 3.16 RUU. Lesson learned.
ttmcmurry said:
Sometimes all I need to do Is complain about something and the answer strikes shortly thereafter....
So I made a gross assumption that "userdata" = /data.
When I attempted to e2fsck the device (/dev/block/mmcblk0p37), it couldn't read the block at all, just errored out.
I figured since the partition type was showing up as unknown (parted /dev/block/mmcblk0, print), that I might as well format it. I know the device is on 4K blocks, so it wasn't a stretch of the imagination to make an educated guess what to do next:
mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p37
e2fsck -y /dev/block/mmcblk037
Reboot, install a ROM, and voila. I have a useable phone again.
Let it be known that if you have 3.16 installed, using an earlier RUU again is useless. There isn't a 3.16 RUU. Lesson learned.
Click to expand...
Click to collapse
Go get s-off using facepalm or dirty racun, and for 3.16, viperboy made VipeRuu, to use it you need to be s-off, glad you got it solved!
Sent from my EVO using xda app-developers app
jocarog said:
Go get s-off using facepalm or dirty racun, and for 3.16, viperboy made VipeRuu, to use it you need to be s-off, glad you got it solved!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thanks. I had actually tried using viperuu as a potential fix, however, it couldn't handle a damaged data partition. That's where my scant Linux skills came into play. I really don't feel the need to be root anymore FWIW. S-Off seems like an invitation to BadThings these days. I like the idea of those special partitions being protected during operation; the convenience isn't worth the added risk of compromise. That said, I'm cool with a reboot to fastboot for the few occasions I actually need to alter something on that level.
I appreciate the suggestions!
That said, I'm cool with a reboot to fastboot for the few occasions I actually need to alter something on that level.
Click to expand...
Click to collapse
Good luck with that... HTC is making it harder to do anything with our devices with each update. They are locking the bootloader down tighter and tighter.