search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.4k stars 660 forks source link

[Huawei P9 Plus] Can´t flash img #546

Closed Kazuma98 closed 5 years ago

Kazuma98 commented 5 years ago

Hi,

everytime i flash the image i get this error:

target reported max download size of 471859200 bytes sending sparse 'system' 1/4 (460796 KB)... OKAY [ 10.817s] writing 'system' 1/4... FAILED (remote: sparse flash write failure) finished. total time: 10.859

i tried it with -S 100m and sim2img.

PhieF commented 5 years ago

Hi, same problem here with huawei p9 ! :)

penn5 commented 5 years ago

System version? Output of adb shell cat /proc/cmdline (contains bootloader version)? /proc/balong/log/fastboot_log after forcibly booting to recovery using rescue_recovery (this is complex - see below) To get fastboot logs, make sure you have the stock images and TWRP. We will need to load them to RAM. Run

fastboot flash rescue_recovery_kernel STOCKKERNEL.img
fastboot flash rescue_recovery_ramdisk TWRPRAMDISK.img
fastboot flash rescue_recovery_vendor STOCK_RECOVERY_VENDOR.img

And the device will boot to twrp. From twrp you must take the file /proc/balong/log/fastboot_log and upload here

PhieF commented 5 years ago

Thanks !!

https://framabin.org/p/?1fc80610b1b7c063#kBZg/ai9lTVDSAUbQvSx3TmI5RUw4TK3Jw5+4JzpqXw=

I already had twrp as a recovery, so here is fastboot log fastboot_log.txt current android is 9 but stock is 8, it should be treble OK but even stock roms from google won't boot, but flashing them is ok

phhusson commented 5 years ago

Well I'm not a fan, but you could just flash using twrp until this is fixed

Le mer. 5 juin 2019 à 09:18, Han98 notifications@github.com a écrit :

Hi,

everytime i flash the image i get this error:

target reported max download size of 471859200 bytes sending sparse 'system' 1/4 (460796 KB)... OKAY [ 10.817s] writing 'system' 1/4... FAILED (remote: sparse flash write failure) finished. total time: 10.859

i tried it with -S 100m and sim2img.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/546?email_source=notifications&email_token=AAAA4OXJK22MP7IWFGGWEHDPY5SD3A5CNFSM4HTRPESKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXWJKDA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAA4OUINRMHZMSRNKFKJPDPY5SD3ANCNFSM4HTRPESA .

penn5 commented 5 years ago

Thanks !!

https://framabin.org/p/?1fc80610b1b7c063#kBZg/ai9lTVDSAUbQvSx3TmI5RUw4TK3Jw5+4JzpqXw=

I already had twrp as a recovery, so here is fastboot log fastboot_log.txt current android is 9 but stock is 8, it should be treble OK but even stock roms from google won't boot, but flashing them is ok

Please do the instructions to get a live fastboot log. The one you sent is useless; it is the boot after fastboot flashing

PhieF commented 5 years ago

Is this better ?

fastboot_log.txt Thanks !

@phhusson I tried through TWRP: flashing "System" didn't work at all Flashing "System Image" did something but I'm now unable to boot (twrp tells me I have no operating systems) Which one is supposed to work ?

Thanks

edit: well even flashing a working system img with twrp seems to lead to this issue

phhusson commented 5 years ago

System image is supposed to work.

You're on EMUI8? Using AOSP v114, arm64 aonly?

Le dim. 9 juin 2019 à 13:26, PhieF notifications@github.com a écrit :

Is this better ?

fastboot_log.txt https://github.com/phhusson/treble_experimentations/files/3269472/fastboot_log.txt Thanks !

@phhusson https://github.com/phhusson I tried through TWRP: flashing "System" didn't work at all Flashing "System Image" did something but I'm now unable to boot (twrp tells me I have no operating systems) Which one is supposed to work ?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/546?email_source=notifications&email_token=AAAA4OXJJAZH7JYQL2RDM3LPZTSHNA5CNFSM4HTRPESKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIIJ5Q#issuecomment-500204790, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAA4OV5OWLJX7UTS5HKSBDPZTSHNANCNFSM4HTRPESA .

barisdemirdelen commented 5 years ago

I can confirm with huawei p9 with emui 8 aosp v114 arm64 aonly su/nosu doesnt work via flashing to twrp as system image. Flashing completes succesfully but twrp says no os found. Mounting the /system via terminal gives invalid argument error.

With fastboot i also cant flash.

phhusson commented 5 years ago

Please give result of dmesg in TWRP after trying to mount /system

Le dim. 9 juin 2019 à 14:39, Barış Demirdelen notifications@github.com a écrit :

I can confirm with huawei p9 with emui 8 aosp v114 arm64 aonly su/nosu doesnt work via flashing to twrp as system image. Flashing completes succesfully but twrp says no os found. Mounting the /system via terminal gives invalid argument error.

With fastboot i also cant flash.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/546?email_source=notifications&email_token=AAAA4OR5PMEDR5XU54XAL4LPZT2WNA5CNFSM4HTRPESKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIJKIQ#issuecomment-500208930, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAA4OQ2R73ANHYYQ4NPGXDPZT2WNANCNFSM4HTRPESA .

barisdemirdelen commented 5 years ago

Sure, thanks for the fast response, here it is. This is me first flashing and then trying to mount it.

dmesg.log recovery.log

phhusson commented 5 years ago

`

<4>[ 76.588745s][pid:324,cpu5,recovery]EXT4-fs (mmcblk0p52): bad geometry: block count 524288 exceeds size of device (507904 blocks) ` What's your system partition size? Le dim. 9 juin 2019 à 14:48, Barış Demirdelen a écrit : > Sure, thanks for the fast response, here it is. This is me first flashing > and then trying to mount it. > > dmesg.log > > recovery.log > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . >
barisdemirdelen commented 5 years ago

Twrp says 1921MB with 1815MB used and 106MB free. Is there a better way to see?

barisdemirdelen commented 5 years ago

cat /proc/partitions says it has 2031616 blocks

phhusson commented 5 years ago

K so that's indeed too low for my images which are 2GB. I'll try to change to your partition's size

Le dim. 9 juin 2019 à 14:58, Barış Demirdelen notifications@github.com a écrit :

cat /proc/partitions says it has 2031616 blocks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/546?email_source=notifications&email_token=AAAA4OT63F6KOWNHJMOW7VDPZT47XA5CNFSM4HTRPESKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIJTGQ#issuecomment-500210074, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAA4OTACVUUXCWNXKEBFR3PZT47XANCNFSM4HTRPESA .

barisdemirdelen commented 5 years ago

I tried building with a 1.9gb partition size and everything went well with twrp and I was able to boot.

phhusson commented 5 years ago

Here is a test image: https://treble.phh.me/system-arm64-p9.img

PhieF commented 5 years ago

Huawei p9 is ok with it, thanks !