[Info] mmcblk* partitons reference of the P6 B107

S34Qu4K3 · Aug 12, 2013

Located in /dev/block, may be useful

Code:

mmcblk0p1     -> /xloader
mmcblk0p2     -> /round              (-empty-)
mmcblk0p3     -> /nvme
mmcblk0p4     -> /misc
mmcblk0p5     -> /splash             (-empty-)
mmcblk0p6     -> /oeminfo
mmcblk0p7     -> /reserved1          (-empty-)
mmcblk0p8     -> /reserved2          (-empty-)
mmcblk0p9     -> /splash2
mmcblk0p10    -> /recovery2          (-empty-)
mmcblk0p11    -> /recovery
mmcblk0p12    -> /boot
mmcblk0p13    -> /modemimage
mmcblk0p14    -> /modemnvm
mmcblk0p15    -> /modemnvm2
mmcblk0p16    -> /system
mmcblk0p17    -> /cache
mmcblk0p18    -> /cust
mmcblk0p19    -> /userdata

I took this info opening the direct accesses in /dev/block/platform/hi_mci.1/by-name

TheProd · Aug 9, 2013 at 4:28 PM

To extract the boot or recovery img with dd:

Code:

adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p12 of=/sdcard/boot.img

S34Qu4K3 · Aug 9, 2013 at 4:51 PM

TheProd said:
To extract the boot or recovery img with dd:

Code:

adb shell su dd if=/dev/block/mmcblk0p11 of=/sdcard/recovery.img dd if=/dev/block/mmcblk0p12 of=/sdcard/boot.img

I already extracted recovery.img

But i can't unpack it, i use unyaffs.exe but i get "broken image file" D:
Same with the other *.img files

Stickman89 · Aug 10, 2013

Code:

BOARD_KERNEL_CMDLINE vmalloc=512M k3v2_pmem=1 mmcparts=mmcblk0:p1(xloader),p3(n
me),p4(misc),p5(splash),p6(oeminfo),p7(reserved1),p8(reserved2),p9(splash2),p10
recovery2),p11(recovery),p12(boot),p13(modemimage),p14(modemnvm1),p15(modemnvm2
,p16(system),p17(cache),p18(cust),p19(userdata);mmcblk1:p1(ext_sdcard)
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_RAMDISK_ADDR 01400000

Unpacking ramdisk to "/ramdisk/" . . .

Compression used: gzip
2085 blocks

Done!

Boot.img unpacked, K3V2 uses ARMv7 Instruction Set. Let's see if we can't get something cooking already

S34Qu4K3 · Aug 10, 2013 at 9:58 PM

I unpacked recovery and boot too

Sent from my HUAWEI P6-U06 using xda app-developers app

Stickman89 · Aug 10, 2013 at 10:15 PM

Good show, unless your planning on beginning work on a Custom Recovery what are you going to gain by unpacking the recovery.img?

I see your working on a CM port, so wish you all the best on that. I'll be porting MIUIv5 for the Ascend P6 as I did for a few other devices, also going to have another crack at porting Flyme OS since I already ported 90% to my previous device.

Best Regards,

s89

S34Qu4K3 · Jun 27, 2012 262 95 0

I unpacked boot and recovery to get info for BoardConfig.mk

Ty

Sent from my HUAWEI P6-U06 using xda app-developers app

Stickman89 · Aug 11, 2013 at 3:11 AM

If you've already got a build environment setup you may aswel build CWM from CM sources, we have more then enough information here to proceed. Even more convenient considering you have the recovery.img unpacked. Google "Build CWM Cyanogenmod" for more info. Failing that i'll setup a build environment and do so myself tomorrow evening.

Best Regards,

s89

S34Qu4K3 · Aug 11, 2013 at 8:24 PM

I'm setting up the enviroment to build CWM, i hope to get it done in a few hours, anyways, i got bad news. My laptop screen broke today, and i send it to repair tomorrow and i don't know how much time will take :/

Stickman89 · Aug 11, 2013 at 9:13 PM

S34Qu4K3 said:
I'm setting up the enviroment to build CWM, i hope to get it done in a few hours, anyways, i got bad news. My laptop screen broke today, and i send it to repair tomorrow and i don't know how much time will take :/

Aww man that's unfortunate, wishing a speedy recovery for said laptop aha. Are you continuing the build on another machine or using an external monitor for the meantime?

Best Regards,

s89

S34Qu4K3 · Aug 11, 2013 at 9:31 PM

Stickman89 said:
Aww man that's unfortunate, wishing a speedy recovery for said laptop aha. Are you continuing the build on another machine or using an external monitor for the meantime?

Best Regards,

s89

I got an small laptop and a pc, i have to install linux and will continue working (i think) i expect to be at least 1 week without my laptop (maybe i got it with screen broken ultil i wait the new screen)

Dam git sync, so ****ing long

S34Qu4K3 · Aug 11, 2013 at 9:58 PM

Just a question, if i have in my .fstabfile the partition routes this way:

Code:

/dev/block/platform/hi_mci.1/by-name/sdcard

I have to change it to

Code:

/dev/block/mcblk....

In BoardConfig.mk or can i let it original? Looks the same for me, /dev/block/platform/hi_mci.1/by-name/ points the mcblk, i want to be sure

Stickman89 · Aug 12, 2013

S34Qu4K3 said:
Just a question, if i have in my .fstabfile the partition routes this way:

Code:

/dev/block/platform/hi_mci.1/by-name/sdcard

I have to change it to

Code:

/dev/block/mcblk....

In BoardConfig.mk or can i let it original? Looks the same for me, /dev/block/platform/hi_mci.1/by-name/ points the mcblk, i want to be sure

EXT SDCard Mounts at:

Code:

/dev/block/mmcblk1p1

so your recovery.fstab should be setup like...

Code:

/sdcard vfat /dev/block/mmcblk1p1

So yup it needs to be changed to the second option.

I'm still syncing too... -.- ...zZzZzZzZz tired

Best Regards,

s89

S34Qu4K3 · Jun 27, 2012 262 95 0

Stickman89 said:
EXT SDCard Mounts at:

Code:

/dev/block/mmcblk1p1

so your recovery.fstab should be setup like...

Code:

/sdcard vfat /dev/block/mmcblk1p1

So yup it needs to be changed to the second option.

I'm still syncing too... -.- ...zZzZzZzZz tired

Best Regards,

s89

But /dev/block/platform/hi_mci.1/by-name/sdcard points to /dev/block/mmcblk1p1, so it shouldn't be necessary

(i'll use /dev/block/mmcblk1p1 style, to be sure anyway)

In 4 hours, i leave my lapton in the shop, in another hour, i got it repaired

(115€ D

Stickman89 · Aug 12, 2013

I've built CWM from CM sources. Haven't tried it as of yet though.

Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding on YOUR device.

Removed for the time being! Do not use...

Best Regards,

s89

S34Qu4K3 · Aug 12, 2013 at 3:29 PM

Stickman89 said:
I've built CWM from CM sources. Haven't tried it as of yet though.

Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding of your device.

Best Regards,

s89

My repo still 93% ;___;
Why you don't make a thread posting it??

Good job bro
We can try recoverys without flash using fastboot? Like the kernel?

Stickman89 · Aug 12, 2013

S34Qu4K3 said:
My repo still 93% ;___;
Why you don't make a thread posting it??
Good job bro
We can try recoverys without flash using fastboot? Like the kernel?

I've tried "fastboot boot recovery.img" to no avail. The output is as follows...

Output:

Code:

downloading 'boot.img'...
OKAY [  0.193s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.194s

As you can see... It's expecting a boot.img so this command is only available for booting ramdisk & kernel.

S34Qu4K3 · Aug 12, 2013 at 3:45 PM

Stickman89 said:
I've tried "fastboot boot recovery.img" to no avail. The output is as follows...

Output:

Code:

downloading 'boot.img'... OKAY [ 0.193s] booting... FAILED (remote: invalid command) finished. total time: 0.194s

As you can see... It's expecting a boot.img so this command is only available for booting ramdisk & kernel.

So, we have to flash it... Bad bad...D:

S34Qu4K3 · Aug 12, 2013 at 4:07 PM

I tried fastboot boot recovery recovery.img but i get:

Code:

fastboot boot recovery recovery.img
cannot load 'recovery'

Stickman89 · Aug 12, 2013 at 4:32 PM

I don't think that command is applicable until post flash as according to cyanogenmod documentation:

Code:

Installing recovery using fastboot

You can use fastboot to install your recovery image to the device.
Installing ClockworkMod Recovery on the device
Connect the device to the computer via USB.
Make sure the fastboot binary is in your PATH or that you place the downloaded image in the same directory as fastboot.

Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination.
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
Flash ClockworkMod Recovery onto your device by entering the following command: fastboot flash recovery your_recovery_image.img where the latter part is the name of the file you downloaded.
Once the flash completes successfully, reboot the device into recovery to verify the installation. This can be done by typing fastboot boot your_recovery_image.img.

Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.

[Info] mmcblk* partitons reference of the P6 B107

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer