i've just done my first make of the android sources, and i don't got a boot.img? i have a ramdisk.img, system.img and userdata.img but no boot.img.
has the compilation failed? or am i missing something?
ps. should this be in the development forums as it's a kinda newbie dev question!
Well, that's strange. For me it always like all-or-nothing -- you get all image files or it will stop compiling when error occur and you get nothing.
Have you tried repo sync and re-compile again? I'm compiling AOSP myself and will let you know the result once it finished.
Related
wtf does this mean and how can i get around it? i've unlocked the bootloader, and am trying to flash a system.img using fastboot. fastboot sends the file ok, but write fails, and the phone states invalid magic code 0x0000003 (or maybe a few more/less 0's)
why?
It most likely means, that the system.img got corrupted somewhere along the way.
cgi said:
It most likely means, that the system.img got corrupted somewhere along the way.
Click to expand...
Click to collapse
but i've tried to flash two images, and same error for both. i can flash a radio.img, though haven't tried the recovery or boot
i'm on stock, i've only upgraded with ota's from google, but one thread somewhere seems to suggest that you only get it if your recovery image is not stock
so, this is a big wtf for me.
Hi everyone,
I pulled down images made from AOSP for the Nexus 7 device successfully. I am trying to flash the zImage onto the Nexus 7 device via fastboot. But in the terminal I get a "Invalid partition" error after doing "fastboot flash zimage zImage". I can flash the boot.img, userdata.img, and system.img just fine. But I get an error for zImage.
I also tried a different method. I did a "make otapackage" and flashed the zip through CWM to I get a "no file_context warning". Afterwards when rebooting, the device shows the google logo but is a blank black screen after a few seconds.
That is when I fastboot flash all the stock images back on and try again... but no success.
Has anyone encountered something similar? Or has some idea of what I steps I can take to remedy this?
Thanks!
mdrdroid said:
Hi everyone,
I pulled down images made from AOSP for the Nexus 7 device successfully. I am trying to flash the zImage onto the Nexus 7 device via fastboot. But in the terminal I get a "Invalid partition" error after doing "fastboot flash zimage zImage". I can flash the boot.img, userdata.img, and system.img just fine. But I get an error for zImage.
I also tried a different method. I did a "make otapackage" and flashed the zip through CWM to I get a "no file_context warning". Afterwards when rebooting, the device shows the google logo but is a blank black screen after a few seconds.
That is when I fastboot flash all the stock images back on and try again... but no success.
Has anyone encountered something similar? Or has some idea of what I steps I can take to remedy this?
Thanks!
Click to expand...
Click to collapse
Not sure if your question was answered in another post as I found this thread searching on google for my own issue.
You can't fastboot flash zImage at all. You may be able to fastboot boot zImage but trying to flash the zimage is an incomplete image. You'd have to add the zimage to a boot.img to flash it with fastboot. Then you'd fastboot flash boot boot.img.
You should be able to fastboot boot zImage to boot the kernel from your pc with the existing boot.img. Hope this helps. I may not even see a response to this thread but I check Nexus 7 Q&A so I hope I hear it helps.
tiny4579 said:
Not sure if your question was answered in another post as I found this thread searching on google for my own issue.
You can't fastboot flash zImage at all. You may be able to fastboot boot zImage but trying to flash the zimage is an incomplete image. You'd have to add the zimage to a boot.img to flash it with fastboot. Then you'd fastboot flash boot boot.img.
You should be able to fastboot boot zImage to boot the kernel from your pc with the existing boot.img. Hope this helps. I may not even see a response to this thread but I check Nexus 7 Q&A so I hope I hear it helps.
Click to expand...
Click to collapse
Thank you for the reply!!! I really appreciate it as I didn't really know what to do about this issue. I don't know how to add the zimage to the boot.img, but I will look into it... do you have any more advice on this?
Before, when after building, I did flash boot.img, zImage (which failed), system.img, and userdata... and I did get it to boot, and everything seems to be working okay in general but I have an inkling that the zImage generated will be needed for what I aim to accomplish.
Anyhow, thanks again for the information I'm new to android development and am glad for any help!
Google decompiling a boot.Img
You can't flash a zimage (ramdisk) because it is not a partition
The boot partition or boot.Img contains both the kernel and the ramdisk
So what you need to do is decompile the boot.Img of your rom
Then put your new ramdisk into the decompiled one
Then recompile the boot and flash that
Sent from my Nexus 7
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
"boot.sig и recovery.sig"
You must install the recovery.img and boot.img
Solution
Here's a solution for ya: http://shuiqingwang.blogspot.com/2013/03/solvedfastboot-wired-errors.html
Basically use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
I know this post is late, but this worked for me
vitaminan said:
I used the fastboot command and updated every time when I bought nexus 7 (wifi) from last year.
However, when I updated from jwr66v to jwr66y, I used wipe function in CWM. Then, I got the "archive does not contain boot.sig" and "archive does not contain recovery.sig" and "failed to allocate XXXXXXX.byte"...
Then I tried to get back version to 4.2.2, but I also got the same error message. I follow the guidehttp://forum.xda-developers.com/showthread.php?t=1907796 to manual flash each .img files, the same problem occur at flashing system.img
At now, I could not get into android system, just hang on the "Google" logo.
I have read the same problem in another threadhttp://forum.xda-developers.com/showthread.php?t=1992063, but I could not have any idea to solve it?
Anyone have idea?
Thank you very much.
PS: I used the platform-tools r22.0.5
Click to expand...
Click to collapse
I have compiled a kernel for the Ze550ml using ASUS released kernel sources and I got a kernel file. Usually when unpacking boot.img file, I usually see just two files.... the kernel and the ramdisk. With this original boot.img I found a third one which is "second bootloader" file. I included it in remaking the boot.img with my compiled kernel (but won't release it due to possible brick). Any ideas?
If anyone is very close to a ASUS repair shop and have no issues repairing or replacing their ze550ml... LMK if you want to try the boot.img to boot (not flash) and see how it goes.
Just got a hold of support and says that our bootloaders are LOCKED... so a modified boot.img will brick the device hopefully they release an unlock tool soon so we can start developing.
There are "Bootstub" strings in the 2nd bootloader. And from this link, the bootstub is "fixed content" in ZF5/6. Although ZF2's boot.img format is different from 5/6, the function of bootstub should be the same, so I think we can re-use the 2nd bl from official boot image to repack our homemade kernels. (That's only what I think, and thus no guarantee on this)
clemsyn said:
Just got a hold of support and says that our bootloaders are LOCKED... so a modified boot.img will brick the device hopefully they release an unlock tool soon so we can start developing.
Click to expand...
Click to collapse
Yep. Even just a simple ro.secure=0 ro.debuggable=1 in the ramdisk and reassembled to boot.img was diceless..
I should try bullying Asus into providing optional unlocked bootloaders. Unlocked everything dammit.. Last I checked, its my phone.
Hi clemsyn!
Blades said:
Yep. Even just a simple ro.secure=0 ro.debuggable=1 in the ramdisk and reassembled to boot.img was diceless..
I should try bullying Asus into providing optional unlocked bootloaders. Unlocked everything dammit.. Last I checked, its my phone.
Hi clemsyn!
Click to expand...
Click to collapse
BLADES!!!!!! Been awhile =)
http://forum.xda-developers.com/zenfone2/orig-development/tool-zenfone-2-boot-repack-t3146088
When you do get unlocked, recompile the boot.img with the second file added into it.
Just build it with the mkbootimg with
Code:
--kernel zImage --ramdisk initramfs.cpio.gz --second second.gz
And then whatever else you have after it, and of course the boot.img name you want.
That's what I had to do to make the insecure boot.img on the 551.
Hello.
I would like to use custom kernels with enabled modprobe supporting. But I am afraid to flash third party modules with magisk because of potential data lost or boot loops or something like that.
So I want to loading kernel without flashing with fastboot like a:
Code:
fastboot boot boot.img
However, I don't know why, all custom kernels ditribute with 'zImage' file. Therefore I need to repack boot.img manualy:
Code:
abootimg -x boot.img
(abootimg deb package)
or
Code:
unpack boot.img
(whiteboard[at]ping[at]se/Android/Unmkbootimg)
or
Code:
mkboot boot.img out/
(github[at]com/xiaolu/mkbootimg_tools)
In all cases I have the same result (files have identical md5sum).
But when I try to build boot.img I've obtain not bootable image.
Also I noticed that after rebuilds boot.img lose 100MB:
original boot.img - 128M
new_boot.img - 17M
Also notice, I didn't make anything changes!
Please tell me, what I do wrong?
Thank you.