Related
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.
I'm having the darndest time trying to figure out a certain issue I'm having. For some reason I cannot edit or delete or even write to certain folders of my internal storage. I have searched the forums for fixes, and the common sense fix keeps coming up, permissions.
In Terminal Emulator I am looking at the permissions for all the folders on my internal /sdcard and they disply as:
Code:
drwxrwxr-x
as expected. Yet when I try to delete say for example /sdcard/Download it tells me the folder is Read Only.
I even chmod to change the permissions and they just dont change. The reason I use the Download folder as an example is because I cannot download any files, like an updated ROM from any browser, it just fails. It is extremely annoying. My Prime is rooted, unlocked, and running Virtuous S .28
To make matters worse, I am deployed to Afghanistan and my laptop recently died, so all I have are my Prime and Desire HD phone to work with.
If anyone has any ideas on how to resolve this I'm all ears.
Many thanks in advance.
TrailorParkKid said:
I'm having the darndest time trying to figure out a certain issue I'm having. For some reason I cannot edit or delete or even write to certain folders of my internal storage. I have searched the forums for fixes, and the common sense fix keeps coming up, permissions.
In Terminal Emulator I am looking at the permissions for all the folders on my internal /sdcard and they disply as:
Code:
drwxrwxr-x
as expected. Yet when I try to delete say for example /sdcard/Download it tells me the folder is Read Only.
I even chmod to change the permissions and they just dont change. The reason I use the Download folder as an example is because I cannot download any files, like an updated ROM from any browser, it just fails. It is extremely annoying. My Prime is rooted, unlocked, and running Virtuous S .28
To make matters worse, I am deployed to Afghanistan and my laptop recently died, so all I have are my Prime and Desire HD phone to work with.
If anyone has any ideas on how to resolve this I'm all ears.
Many thanks in advance.
Click to expand...
Click to collapse
What's the output of the "ls -l /sdcard/Download"??
craigacgomez said:
What's the output of the "ls -l /sdcard/Download"??
Click to expand...
Click to collapse
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # ls -l /sdcard/Download
-rw-rw-r-- root sdcard_rw 63816 2012-03-07 14:40 -1
-rw-rw-r-- root sdcard_rw 63733 2012-03-07 14:40 -2
-rw-rw-r-- root sdcard_rw 334117 2012-03-07 13:03 12th CAB Packing List FINAL.docx
-rw-rw-r-- root sdcard_rw 62524 2012-03-07 02:35 ALERT ROSTER.pptx
drwxrwxr-x root sdcard_rw 2012-07-02 10:29 Adobe Reader
-rw-rw-r-- root sdcard_rw 346301 2012-03-07 14:40 CJTF computer user agreement.pdf
-rw-rw-r-- root sdcard_rw 10041835 2012-06-18 07:44 DebugfsRoot_v1.8.zip
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 FAQ
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 MANUAL
-rw-rw-r-- root sdcard_rw 4045147 2012-06-22 23:21 Phonesky.apk
-rw-rw-r-- root sdcard_rw 162197 2012-03-07 14:40 SFC CRIST-DA FORM 2875_BLANK FORM.pdf
-rw-rw-r-- root sdcard_rw 4036382 2012-06-23 19:18 Signed_Vending-mod.apk
-rw-rw-r-- root sdcard_rw 622047 2012-06-23 11:27 UnLock_Device_App_V6.apk
-rw-rw-r-- root sdcard_rw 4031699 2012-06-23 18:14 Vending-3.5.16-mod.apk
-rw-rw-r-- root sdcard_rw 16903 2012-03-07 14:40 _CJTF USER AGREEMENT INSTRUCTIONS.docx
[email protected]:/ #
File permissions of /data/media issues
TrailorParkKid said:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # ls -l /sdcard/Download
-rw-rw-r-- root sdcard_rw 63816 2012-03-07 14:40 -1
-rw-rw-r-- root sdcard_rw 63733 2012-03-07 14:40 -2
-rw-rw-r-- root sdcard_rw 334117 2012-03-07 13:03 12th CAB Packing List FINAL.docx
-rw-rw-r-- root sdcard_rw 62524 2012-03-07 02:35 ALERT ROSTER.pptx
drwxrwxr-x root sdcard_rw 2012-07-02 10:29 Adobe Reader
-rw-rw-r-- root sdcard_rw 346301 2012-03-07 14:40 CJTF computer user agreement.pdf
-rw-rw-r-- root sdcard_rw 10041835 2012-06-18 07:44 DebugfsRoot_v1.8.zip
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 FAQ
drwxrwxr-x root sdcard_rw 2012-06-23 16:10 MANUAL
-rw-rw-r-- root sdcard_rw 4045147 2012-06-22 23:21 Phonesky.apk
-rw-rw-r-- root sdcard_rw 162197 2012-03-07 14:40 SFC CRIST-DA FORM 2875_BLANK FORM.pdf
-rw-rw-r-- root sdcard_rw 4036382 2012-06-23 19:18 Signed_Vending-mod.apk
-rw-rw-r-- root sdcard_rw 622047 2012-06-23 11:27 UnLock_Device_App_V6.apk
-rw-rw-r-- root sdcard_rw 4031699 2012-06-23 18:14 Vending-3.5.16-mod.apk
-rw-rw-r-- root sdcard_rw 16903 2012-03-07 14:40 _CJTF USER AGREEMENT INSTRUCTIONS.docx
[email protected]:/ #
Click to expand...
Click to collapse
TrailerParkKid,
I'm having similar issues. The /sdcard folder is a sym-linked to /storage/sdcard0. /storage/sdcard0 is virtualized from /data/media. I noticed that in this folder the user\group is root\root with permissions -rwx------.
I think we have permissions issues in this directory. If I change the permissions to -rwxrwxrwx then things start working, however I don't like that answer.
I was unable to fix it by changing any permissions through TE. I was finally able to use another device to download the Stock JB ROM modded with the new bootloader and the current version of TWRP. The new version of TWRP allowed me to use my external SD card to flash, so I used the Full Wipe flash to completely wipe the internal SD card. It was a last resort, but I didn't really have a choice. Since then I have been able to download files without issue.
My solution to repair /data/media/
TrailorParkKid said:
I was unable to fix it by changing any permissions through TE. I was finally able to use another device to download the Stock JB ROM modded with the new bootloader and the current version of TWRP. The new version of TWRP allowed me to use my external SD card to flash, so I used the Full Wipe flash to completely wipe the internal SD card. It was a last resort, but I didn't really have a choice. Since then I have been able to download files without issue.
Click to expand...
Click to collapse
TrailorParkKid,
Good to see you got it working. There's always more than one way to fix things. I suspect the Full Wipe of internal SD card probably set the permissions up correctly so that subsequent downloaded files would inherit the correct settings. I did that as well, but then I also restored my backed up files. Those files and directories then got the wrong permissions.
My solution was the following 3 lines executed from /data/media/. Hope this also assists someone else googling...
find . -type d -exec chmod 775 {} ";"
find . -type f -exec chmod 664 {} ";"
find . -exec chown media_rw:media_rw {} ";"
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.
hello,
my HTC amaze has been rooted for years, but somehow it recently got unrooted. busybox installer still shows it as rooted, but every other application i have that requires root tells me i need root access/superuser privileges. when i try to re-root with the zerg rush exploit, this is what happens:
bash-3.2# adb devices
List of devices attached
HT19VVP12772 device
bash-3.2# adb push zergRush /data/local/
1667 KB/s (21215 bytes in 0.012s)
bash-3.2# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
bash-3.2#
***EDIT***
i am pretty sure it got unrooted after i installed busybox, which installed at /system/xbin.
responses from adb terminal commands:
bash-3.2# adb ls /system
000041ed 00001000 515f14ed .
000041ed 00000000 53343bad ..
000041ed 00001000 00000000 lost+found
000041ed 00002000 53343976 app
000041ed 00001000 53343976 bin
000081a4 00001fd0 515f14ed build.prop
000041ed 00001000 4f7f6e47 customize
000041ed 00001000 4f7f6e49 etc
000041ed 00001000 4f7f6e4a fonts
000041ed 00001000 4f7f6e53 framework
000041ed 00002000 4f7f6e64 lib
000041ed 00001000 4f7f6e65 media
000041ed 00001000 4f7f6e72 usr
000041ed 00002000 52d9d612 xbin
adb ls /system/xbin includes this:
0000a1ff 00000014 4f7f6e73 sh
whereas adb ls/system/bin does not have "sh" listed.
so /system/bin/sh doesn't exist but /system/xbin/sh does.
how do i fix this and get my device rooted again? this is driving me nuts! thanks
FIXED (i think - i hope)
installed su binary from recovery, did cleanup in superuser app, root seems to be working again now
eudemonics said:
installed su binary from recovery, did cleanup in superuser app, root seems to be working again now
Click to expand...
Click to collapse
That's what I was going to suggest, but glad you figured it out.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
UPDATE on 09/23:
Thanks Modding.MyMind for all the hard work!
Finally our beloved MT2-L03 have TWRP recovery...Mission Accomplished!!
Please go here for the recovery thread:
http://forum.xda-developers.com/showthread.php?t=2885144
======================
Now we have the phone rooted, before I dare to try anything dangerous, I really hope we can have a recovery first.
Following is the partition of our phone
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ ls -l |sort -k 7
lrwxrwxrwx root root 1970-01-01 07:14 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 07:14 modemst2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 07:14 modem -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 07:14 fsg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 07:14 fsc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 07:14 ssd -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 07:14 log -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 07:14 bkbootup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 07:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 07:14 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 07:14 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 07:14 sdi -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 07:14 cust -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 07:14 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 07:14 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 07:14 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 07:14 userdata -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 07:14 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 07:14 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 07:14 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 07:14 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 07:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 07:14 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 07:14 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 07:14 modemst1 -> /dev/block/mmcblk0p9
And I already dd them out as backup, following is their dd out file size:
Code:
09/05/2014 01:01 PM 524,288 mmcblk0p1.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p10.img
09/05/2014 01:02 PM 100,663,296 mmcblk0p11.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p12.img
09/05/2014 01:03 PM 1,024 mmcblk0p13.img
09/05/2014 01:03 PM 8,192 mmcblk0p14.img
09/05/2014 01:03 PM 33,554,432 mmcblk0p15.img
09/05/2014 01:03 PM 67,108,864 mmcblk0p16.img
09/05/2014 01:03 PM 8,388,608 mmcblk0p17.img
09/05/2014 01:03 PM 12,582,912 mmcblk0p18.img
09/05/2014 01:03 PM 16,777,216 mmcblk0p19.img
09/05/2014 01:01 PM 32,768 mmcblk0p2.img
09/05/2014 01:04 PM 268,435,456 mmcblk0p20.img
09/05/2014 01:04 PM 201,326,592 mmcblk0p21.img
09/05/2014 01:05 PM 4,194,304 mmcblk0p22.img
09/05/2014 01:06 PM 1,073,741,824 mmcblk0p23.img
09/05/2014 02:34 PM 0 mmcblk0p24_toolarge.txt
09/05/2014 02:34 PM 0 mmcblk0p25_toolarge.txt
09/05/2014 01:01 PM 32,768 mmcblk0p3.img
09/05/2014 01:01 PM 512,000 mmcblk0p4.img
09/05/2014 01:01 PM 512,000 mmcblk0p5.img
09/05/2014 01:02 PM 5,726,208 mmcblk0p6.img
09/05/2014 01:02 PM 1,048,576 mmcblk0p7.img
09/05/2014 01:02 PM 67,108,864 mmcblk0p8.img
09/05/2014 01:02 PM 4,194,304 mmcblk0p9.img
09/05/2014 02:17 PM 4,194,304 mmcblk0rpmb.img
09/05/2014 02:34 PM 0 mmcblk1p1_toolarge_4GB.txt
So, maybe someone can help us build a recovery image? I like to learn, but really don't have much experience on these.
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
That might help you out if you haven't already looked into it.
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Man, I wish I could help but I don't know anything about this.
If there's a CWM forum, try asking there. Hopefully we can find someone to help us.
xordos said:
Thanks, I will take a look that.
Right now, I am using their online builder:
http://builder.clockworkmod.com/
Still I am wondering, how that online builder (or the manual compile steps in your link) decide which partition is system/data/cache etc? Is that device-by-name is universal?
Also, is that safe to flash the recovery? if recovery image is bad, am I be able to boot normally to phone, and use adb to restore stock recovery?
Thanks.
Click to expand...
Click to collapse
I will answer my own question..
That online builder looks like is not working.
The build process will extract recovery.fstab from the the ramdisk image inside the recovery image.
The local build of the recovery did went through, but the whole process is so complex, and I have never done this before. I am pretty sure I will miss here and there. So my confident of the generated recovery.img is very low.
-rwxr--r-- 1 16777216 Sep 6 18:36 recovery_mmcblk0p19.img
-rw-r--r-- 1 8456192 Sep 6 21:53 recovery_new.img
Anyway, following command can flash the recovery easily.
Code:
fastboot.exe devices
fastboot.exe flash recovery recovery.img
The things is, with my recovery image flashed, it can't enter the recovery mode, following is detail:
1. "fastboot flash" to flash recovery.
2. hold 10 seconds to reboot ( or use fastboot reboot)
3. The phone will boot normally into android OS.
4. Then I shutdown the phone.
5. Before it completely shutdown, it showed Huawei logo once as usually, then it show the BootLoader screen. means the phone won't shut off completly.
(or In step 4. I use usb adb cmd "adb reboot recovery" it will same result in step 5)
If I flash back the original recovery in step 1, then in step 4, "adb reboot recovery" will easily reboot into recovery without hold any key. So keys holding is not a issue here.
So, I am not sure "always go into bootloader" means what, the recovery image is bad? or the phone has some checksum/sig check before it load recovery.
Anyway, I didn't try fastboot flash system, but looks like fastboot is one way to flash some partitions, following is the help:
Code:
...
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
.
I also searched some other Chinese varies Mate2 ROM, they are very differnt, the CPU is different, and the kernel command line (which is configured in the recovery partition) is quite different, so I doubt MT2_L03 can use recovery image from others like MT2_C00.
For ROM Developers, please see attachment for the device files.
I only updated BoardConfig.mk on those partition size. ( I double checked the size from /proc/partitions as well as the dd file size, they matching)
The recovery.fstab is original that extract from stock recovery image by the build tool automatically.
I am build on CM souce code branch 10.2.
Please let me know if you have any idea.
Without a working recovery to backup/restore, Having root on the phone is pretty dangerous. That's also the reason I am still not try xposed on my phone yet.
Hope we can have a working recovery soon.
Thanks.
I wouldn't bother with CWM.. Personal preference I guess. I would aim to build TWRP. Also, sync OmniRom. TWRP is officially located within the OmniRom source now.
http://docs.omnirom.org/Setting_Up_A_Compile_Environment
Can someone pull me their boot.img, recovery.img, build.prop and collect all of their "getprop" information. Zip it all up and throw it up on dev host or another cloud service. Would like to review.
hey, i am outside right now,will upload tonight
EDIT: @Modding.MyMind
uploaded....Here is the list of files in the zip:
09/05/2014 01:03 PM 12,582,912 boot_mmcblk0p18.img
09/07/2014 04:19 PM 13,109 build.prop
09/06/2014 02:17 AM 2,966 device_mount.txt
09/06/2014 02:18 AM 9,104 device_names.txt
09/07/2014 04:19 PM 20,936 getprop.txt
09/07/2014 04:14 PM 1,168 md5sum.txt
09/07/2014 04:18 PM 1,194 proc_partition.txt
09/06/2014 06:36 PM 16,777,216 recovery_mmcblk0p19.img
File location:
https://drive.google.com/file/d/0B-nJFDpWA4MdaWFEckVfUERSRk0/edit?usp=sharing
md5: c73da57ebc630a244ec86f15937251ea mt2_l03_upload.zip
Please let me know if you need anything else.
Thanks a lot.
You guys are simply amazing! :good:
Thanks, will be syncing OmniRom to my computer tomorrow after work. Meanwhile, will be looking over the contents inside the zip. Don't remove them on the cloud just yet lol. Won't be able to download it until tomorrow. I will let you know when that happens so if you wish to remove them later on you may.
@xordos and @ScoobSTi, can either of you confirm that you can currently install a recovery to your device now that ya'll are unlocked. Pull your stock recovery and in turn try to install that same recovery to see if the screen reports back successful.
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
xordos said:
yes, I already did that when i test my cwm recovery. The phone will boot normally into OS, so I dd out new partition image, and verified using bvi or other binary editor. Then i can restore stock recovery back. pls see post #6 for details.
Click to expand...
Click to collapse
Awesome, great news. Just wanted to verify so I had reassurance that if my first TWRP build is buggy you or another tester could get back to your stock recovery .
@xordos, Syncing OmniROm now. Downloaded your zip that you provided. Will begin my work.
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Modding.MyMind said:
Quick question, is the storage sdcard path located at /data/media, or no? Need to know. Reviewing the zip I got and it was giving me mixed feelings on that issue.
Almost done building the device configuration folder.
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
Also, what is ya'lls device resolution? Need that as well lol.
Click to expand...
Click to collapse
/storage/sdcard0 - I think
720x1280
aragon257 said:
/storage/sdcard0 - I think
720x1280
Click to expand...
Click to collapse
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Modding.MyMind said:
Thanks. Makes it easier for me.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Is this device CDMA or GSM? Looking at it tells me it is GSM but wanted to verify with you guys.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I'm also not seeing a partition for the internal sdcard. I have to assume it's fused with /data/media. Will hit up the build.prop to verify. It will tell me there. And I see there is an external sdcard as well (up to 64 gigs). Useful info for building.
---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------
And I see it is CDMA with no SIM card according to the build.prop. Also, just so you guys know, the internal sdcard is in fact fused with /data/media.
Click to expand...
Click to collapse
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
USHAM2 said:
It is GSM ..Also, very few 64GB microSD cards are compatible with this device. 32GB is preferred.
Click to expand...
Click to collapse
Thanks, knowing if it were GSM or CDMA was very important to me. I looked back at the build.prop and saw that is in fact GSM. Read the info wrong lol. It happens . Working to complete the device configuration before the syncing is complete so I can jump straight in to building TWRP for you guys.