So, I compiled my own android image and kernel and want to try it out, it spat out a system.img file.
I've tried both on Windows and Linux to get fastboot working, but I cannot. My device never gets detected.
(Really wondering if it's even possible)....fastboot mode is odin mode...right? I haven't a clue...anyways.
I tried Heimdall as well. Kernel flashing works great, but factoryfs flashing results in an error:
ERROR: Failed to confirm end of file transfer sequence!
So that's out as well.
I've been searching around, but I can't seem to find another option, any ideas?
EDIT:
Came across this: http://blog.coralic.nl/2010/01/25/how-to-create-update-zip-using-your-build-aka-system-img/
Basically system.img -> update.zip.
Guess that's one way to do it.
Related
I'm having trouble flashing a kernel. I've compiled the 2.3.4 kernel (faux's kernel, and i'm using ken's 2.3.4 ROM) and i am trying to fastboot the resulting zImage to my device with no luck. i keep getting either an error, or no action at all.
using the below command, the image is sent, bootloader mode, but just sits there forever.
Code:
fastboot boot zimage zImage
and below just gives an error such as FAILED: 0x30003000.
Code:
fastboot flash zimage zImage
i've searched the forum and see talk about needing the ramdisk, but i'm new to that. my nexus one i was able to just flash the zimage directly after compile with no ramdisk with it.
however i did give the ramdisk a shot. i took my nand backup, pulled the boot.img from it. then broke that up with an extract perl script i found from google, got the resulting ramdisk, which actually looked like the same size as the HKTW ramdisk, both at 152kb. but alas, i just get a boot loop when i use the ramdisk with the following command:
Code:
fastboot flash:raw boot zImage ramdisk.gz
so i'm kinda stuck here and hope someone could give me a pointer. thanks!
i had this while trying to flash xoom's kernel
Sent from my MB860 using XDA App
interesting so you think there is no solution and it has something to do with tegra devices? i can't imagine it's impossible else how are we making custom ROMs!
anyone else have hints? i doubt recovery matters, but i'm using CWM. i even tried wiping dalvik cache before the flash. since fastbooting a kernel doesnt use recovery but the bootloader, recovery prob does not matter either way.
anyone have the ramdisk they could send me? i'm using 2.3.4 ken's ROM. maybe i just goofed on extracting the ramdisk myself.
anyone have any additional advice or tips on the kernel zimage and flashing it to the atrix? i'm at my wits end here. i've tried for 5 days everything i could think of and just CANNOT flash the kernel that i compiled.
i also compiled it about 30 times thinking something screwed up. but seems like i just cant flash it to device. thanks.
use cwm? thats how I flashed the kernel. went perfectly.
also, are you unlocked?
Stephen Who said:
use cwm? thats how I flashed the kernel. went perfectly.
also, are you unlocked?
Click to expand...
Click to collapse
Well this is a zimage because I compiled the source and that's what's giving me trouble flashing to the phone.
I'd have to bundle into a flashable zip to use CWM and I need the ramdisk to do that.
Yes I'm unlocked.
Movd to proper section
Here is a (roundabout) way:
Not sure if you found an answer - but here is a roundabout way:
Start with an existing CWM kernel zip file and extract the boot image off it. Then follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=443994
to get the ramdisk from the image.
Now - since you compiled your own kernel, assuming you know your way around Linux - you might need to adapt the command to match your linux installation, paths, etc.
Also - You might want to use moto-fastboot instead of the stock android fastboot:
Code:
sudo moto-fastboot flash:raw boot zImage mynewimage.img-ramdisk.cpio.gz
where zImage is the zImage compiled by you, and the ramdisk.cpio.gz is the ramdisk you extracted. This is how I load my own kernels onto my Atrix - and has worked for me. I just use a standard ramdisk image - makes life easier
Cheers.
I keep getting the following error:
-i0x413c flash recovery recovery.img error: cannot load 'recovery.img'
After this the installation from the SD card aborts with a status 7 error.
Any help appreciated!!
morganphare said:
I keep getting the following error:
-i0x413c flash recovery recovery.img error: cannot load 'recovery.img'
After this the installation from the SD card aborts with a status 7 error.
Any help appreciated!!
Click to expand...
Click to collapse
This is supposed to be a full path where the recovery.img is located, for example C:\downloads\407\recovery.img.
I try to flash with the O2 version too, and have an error 7, when try the recovery from sd card. Do I need to change from O2 to another rom and then try to update the 407?
Where are you attempting to copy RECOVERY.IMG from? If from the Streak's MicroSD, then you're doing it wrong. RECOVERY.IMG needs to be on the hard drive and flashed using the fastboot command you gave above. Preferably both RECOVERY.IMG and FASTBOOT.EXE are in the same directory on the hard drive, one that is easy to find.
Do search the forums and the wiki. Read everything you can find, and then read it again. If you're experienced enough to have flashed phones in the past, don't rely on your experience. Read.
I can use RSD Lite to flash the 4547-fix-try2.sbf file to the phone.
I can get RSD, fastboot, and etc options.
I can't seem to get any roms installed. If I try to do it with RSD it says "Please check inpu file. Either XML format is wrong or image files associated with it are missing."
fastboot.exe gives me a similar error.
What should I do?
Well some how magically I got it back to stock.
Hi guys,
It's been the hole day now struggling trying to solve my bootloop. Could someone help me?
This morning I had 170B with root and I decided to put the new 330B.
So I flashed with ADB the files extracted from the original 121B package: BOOT.IMG, CUST.IMG, RECOVERY.IMG, CACHE.IMG AND SYSTEM.IMG.
Everything fine with the exception of SYSTEM.IMG: - error: cannot load 'system.img' -
So I tried with the version 100B but same problem.
I cannot more go inside the bootloader even if I flash the TWRP back. I tried running cmd as administrator and I also tried to add -S 512M when flashing.
I searched in the hole WWW but coulnt find anything that solves my problem...
Thanks for the attention
Fuserr
EDIT: solved
I'm trying to port TWRP to my Ulefone Armor x10 on the way to de-googling it.
I have extracted the boot.img from the official zip from the website, and then used https://github.com/twrpdtgen/twrpdtgen to generate a basic device tree.
I then downloaded the device tree for the Armor X5 from here, https://github.com/SPRATAY/android_device_ulefone_x5_armor
and compared the two,
i then built TWRP using the minimal manifest guide: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
I get the build to finish OK, but when I try to boot via
fastboot boot mytwrp.img
i get
FAILED (Status read failed (Too many links))
and if i flash with
fastboot flash boot mytwrp.img
the device just bootloops endlessly with nothing on the screen.
How can I debug TWRP builds to see why its failing?
My phone has bootloader unlocked and flashed null vbmeta
Am I on the right path here? there seems to be not many Mediatek 6762 devices running android 11+ with recovery in boot ramdisk.
Is there a great guide on porting TWRP?
Thanks!
OK, i will reply here incase anyone else picks this up online.
I followed lots of guides suggesting USB drivers, bad ports, old ADB versions, it seems its a generic error.
I tried fastboot boot with the stock image I dumped from the phone and that also failed, so I realised its just a generic problem.
It was also the problem given by the broken TWRP i ported when I flashed it onto the phone.
I knew flashing the stock boot image with fastboot flash boot stockboot.img worked, so I then unpacked stockboot with Carliv image kitechen, added a single text file as a text, rebuilt it, and flashed it to boot and the phone booted fine.
I then found a closer match of TWRP and followed the porting guide https://techsbyte.com/how-to-port-twrp-to-a-b-partitioned-devices-mediatek/ and got a version to boot.
The storage partition still doesn't work, I will reply if I get a working TWRP for this phone with a link.
Leaving this incase someone else is trying to port TWRP and gets a similar error.