- #FLASH AN IMG FILE ON ANDROID HOW TO#
- #FLASH AN IMG FILE ON ANDROID ANDROID#
- #FLASH AN IMG FILE ON ANDROID CODE#
#FLASH AN IMG FILE ON ANDROID ANDROID#
Regarding point #1, in my experience, I would not count on theīrittle Android build tools to complain if you ask them to do Instead, however, it seems you tried to force your 2 GB image into a size that (1) might not be possible for it to be stuffed into and (2) is not the size that your device's system partition is supposed to be. If you and I are right, and it's about size (your tablet does only have 1 GB of RAM, and supposedly most devices try to read the whole image into RAM before flashing), this is where I think the mere adjustment of adding the -S option to fastboot might have fixed your flash as it has for me: fastboot -S 512M flash system system.img So, anyway, it seems here, that for whatever reason, you are unable to flash. linux_box# fastboot flash system system.img
#FLASH AN IMG FILE ON ANDROID CODE#
The current fastboot code is made to work around a max-download-size that is too small, but I've experienced your same error even when the image is smaller than what the device says it can handle, so actually the point is kind of moot, I guess. (bootloader) partition-size:system: 0x0000000080000000Īmong these variables, did your tablet return a max-download-size variable? If so, that might have provided a warning, outright, that the flashing process might have some issues with such a large image. It seems you've already found some kind of solution to your problem (there's a lot of text to read on this page), but it seems this probably could have been resolved much more simply. That did it - the tablet booted from my external SD card.ĮDIT: The journey continued - I eventually patched and compiled my own kernel and became root. and back in my linux box, I dd-ed the pristine backup of the tablet's system partition to my external SD card's 2nd partition - which I created via gparted to be exactly 2GB. My edit /dev/block/mmcblk1p2 /system ext4 rw,barrier=1 wait
#FLASH AN IMG FILE ON ANDROID HOW TO#
Original line that told the tablet how to mount /system /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait I needed to boot the tablet so that it used my pristine copy of the /system partition, but at this point, even though I had shell access, I was not root - ( the changes I did in default.prop are apparently ignored by the Asus kernel - I'll have to recompile it soon.) so I could not mount the external sdcard and dd over my good copy.īut I did have my own boot image - which meant I could edit the /fstab.qcom inside it, and do this:
That explained why the tablet was not booting, and gave me the final idea that solved the issue. It was a wonder that the partition was mounted in the first place. reported that all was Ok - had failed spectacularly. I finally got access to the tablet - from "inside".Ĭhecking the mounted /system, it became clear that the flashing process - even though fastboot flash system. I re-packed, and to my intense satisfaction, saw. and tried an obvious change: service adbd /sbin/adbd Service adbd /sbin/adbd -root_seclabel=u:r:su:s0 So I checked how adbd was started from my boot image's init.rc: # adbd is controlled via property triggers in Which left only one explanation - SELinux "cages". adbd itself was responding, so it was started on the tablet side - but it could not execute the shell, even when I hack-patched it to invoke a file ( /sbin/sh) that I myself placed in the boot image - being 100% sure that it had the proper permissions and was accessible from the shell (id=2000) account that adbd uses. If I ever had any chance of solving this, I first had to figure out why the shell wasn't working.
0 kommentar(er)
