Hello.
I've built a custom kernel for Dell Streak.
When I try to boot it I get a message:
Code:
$ ./fastboot-linux -i 0x413c -c 'root=/dev/mmcblk0p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' boot arch/arm/boot/zImage
creating boot image...
creating boot image - 2144256 bytes
downloading 'boot.img'... OKAY
booting... FAILED (remote: invalid command)
Does this mean that Streak fastboot does not support booting custom kernel?
- -
Anyway, I flashed it with:
Code:
$ ./fastboot-linux -i 0x413c -c 'root=/dev/mmcblk1p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' flash:raw boot arch/arm/boot/zImage
creating boot image...
creating boot image - 2144256 bytes
sending 'boot' (2094 KB)... OKAY
writing 'boot'... OKAY
After booting I have a "Dell logo reboot loop".
Is there a way of getting kernel messages somehow, to see why is it failing?
Sent from my Dell Streak using XDA App
I`d love to know more about this as well. Did some Dev`ing many years ago in a galaxy far far away.
I was talking to defet at #modaco, and apparently ARM kernel needs board specific files in arch/arm/mach-msm/ that describe the hardware board name/id, features and memory layout.
Without this, there is no way of running a kernel on Streak board, because kernel just is unaware of the board features. The kernel checks the board name on boot and if it is not compiled for this exact board it just stops booting.
So, without kernel sources from Dell, we are totally screwed.
You may want to support http://forum.xda-developers.com/showthread.php?t=761856 because without this you may as well dream of running Linux or Froyo on Streak.
Hi,
I'm fairly green when it comes to Android devices, but my understanding is that when using "fastboot," I ought to be able to select "hot boot" a kernel and ramdisk using the "boot kernel <ramdisk.gz> command. However, for my Xperia Z Ultra, I'm finding that when I attempt this, I am told:
"FAILED (remote: dtb not found)"
A bit of research indicates that this probably refers to a "device tree blob", something which I understand is used to inform the kernel as to how to access devices (http://xillybus.com/tutorials/device-tree-zynq-1). However, I can't find any information pertaining to the inclusion of a "dtb" when using fastboot.
In my probing of various "sin" files, I've managed to extract the kernel.sin for the HK 461 amd 471 ROM versions. They present me with an elf file. This elf file, in turn, can be extracted into three files. The kernel image, the ramdisk gzip and a ".3" file, which I can only assume is the dtb.
My question is whether it is possible to reassemble these files into an elf, and subsequently a sin file so that I can then put this back into the original ROM ftf. Failing this, I'd like to be able to simply hotboot the kernel and a modified ramdisk (that leaves / and /system mounted as rw and runs adb as "root" rather than "shell").
I'm not asking for a handout or a painstakingly written HOWTO, just a pointer in the right direction, if possible.
Interestingly, if I try to simply "hot boot" the extracted elf, it seems to upload perfectly to the phone, but then the phone hangs when trying to boot:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf
creating boot image...
creating boot image - 8663040 bytes
downloading 'boot.img'...
OKAY [ 0.283s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 413.509s
The "FAILED" is reported after I simply unplug the phone. At this point, the phone is very much locked up with the blue LED illuminated. After a few panicked moments, I realised that Vol-Up + Power is a force-reset key combination (it causes the vibration motor to pulse three times, then reboots).
For completeness, here's what happens when I try "hot booting" the extracted kernel and my custom ram disk:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf.Image D:\ramdisky.gz
creating boot image...
creating boot image - 8329216 bytes
downloading 'boot.img'...
OKAY [ 0.274s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.322s
Chinese, all i see here i chinese One thought though, wouldn't the guys over at the Xperia Z forum be at any assistance? They are working with Sony hardware after all, and maybe they can give you some tips and ideas? I'm just thinking here though
Anywho, keep it up. It's only a matter of time until you crack the code!
ShALLaX said:
Hi,
I'm fairly green when it comes to Android devices, but my understanding is that when using "fastboot," I ought to be able to select "hot boot" a kernel and ramdisk using the "boot kernel <ramdisk.gz> command. However, for my Xperia Z Ultra, I'm finding that when I attempt this, I am told:
"FAILED (remote: dtb not found)"
A bit of research indicates that this probably refers to a "device tree blob", something which I understand is used to inform the kernel as to how to access devices (http://xillybus.com/tutorials/device-tree-zynq-1). However, I can't find any information pertaining to the inclusion of a "dtb" when using fastboot.
In my probing of various "sin" files, I've managed to extract the kernel.sin for the HK 461 amd 471 ROM versions. They present me with an elf file. This elf file, in turn, can be extracted into three files. The kernel image, the ramdisk gzip and a ".3" file, which I can only assume is the dtb.
My question is whether it is possible to reassemble these files into an elf, and subsequently a sin file so that I can then put this back into the original ROM ftf. Failing this, I'd like to be able to simply hotboot the kernel and a modified ramdisk (that leaves / and /system mounted as rw and runs adb as "root" rather than "shell").
I'm not asking for a handout or a painstakingly written HOWTO, just a pointer in the right direction, if possible.
Interestingly, if I try to simply "hot boot" the extracted elf, it seems to upload perfectly to the phone, but then the phone hangs when trying to boot:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf
creating boot image...
creating boot image - 8663040 bytes
downloading 'boot.img'...
OKAY [ 0.283s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 413.509s
The "FAILED" is reported after I simply unplug the phone. At this point, the phone is very much locked up with the blue LED illuminated. After a few panicked moments, I realised that Vol-Up + Power is a force-reset key combination (it causes the vibration motor to pulse three times, then reboots).
For completeness, here's what happens when I try "hot booting" the extracted kernel and my custom ram disk:
Code:
C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot.exe -i 0x0fce boot D:\kernel-461.elf.Image D:\ramdisky.gz
creating boot image...
creating boot image - 8329216 bytes
downloading 'boot.img'...
OKAY [ 0.274s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.322s
Click to expand...
Click to collapse
yes, same thing in here (it seems newer kernel with dtb)
how to extract them correctly and re-pack to work?
http://forum.xda-developers.com/showthread.php?t=2428117
hkfriends said:
yes, same thing in here (it seems newer kernel with dtb)
how to extract them correctly and re-pack to work?
http://forum.xda-developers.com/showthread.php?t=2428117
Click to expand...
Click to collapse
Why extract it at all? Sony has released the kernelsourcecode and we can create a dtb from scratch. Btw dtb and kernel are corresponding, so better not always use 475 dtb for ever!
So you guys better grab the kernel opensource and compile it sourself instead breaking heads on howto extract.
See our repos custombootimg.mk for the mkbootimg parameters once you compiled dt.img
Regards
Gesendet von meinem C6833 mit Tapatalk 4
I wasn't looking at how to extract it, but how to include it in the ELF. I'll take a look at the mk file, got a link?
Sent from my GT-I9500 using xda app-developers app
As the title said, i'm having some errors while i try to flash something in fastboot, i'm folowing this steps:
First i open CMD (with administrator rights) or Terminal (root mode) and Type this:
Code:
adb devices
adb reboot-bootloader
My device reboot into bootloader, then i use:
Code:
Fastboot devices
Fastboot flash [partition] [path to file]
In this case: Fastboot flash recovery recovery.img
And here is where the problems begins
Code:
Fastboot flash recovery (path to the recovery.img file)
Sending 'recovery' (42834 KB) Failed (remote: 'not support "-u" option')
Fastboot: error: command failed
I do a little research about "-u" and got something about erasing a overwriting stuff so...
Code:
Fastboot erase recovery
(Everything is ok)
Fastboot flash recovery (path to the recovery file)
Sending 'recovery' (42834 KB) OKAY
Writing 'recovery' FAILED (remote: 'write partition:recovery')
Fastboot: error: Command Failed
I can't even do a Fastboot boot because of the '-U' option error...
I've tried with RKtools (because of my rk3368h chipset) and there i can flash everything succesfuly but when i try enter in recovery mode my device get stuck in the initial boot image (not the CR boot image)
So, i don't know if i'm using a wrong recovery.img or if my device is the problem. I hope someone can help me :laugh:
P.D: My device is a generic (unpopular) Android, so the only useful info that can i bring you is:
Android version is 8.1 (November 2018 security patch)
Device uses a rk3368h chipset
Bootloader is Unlocked
Obviously isn't rooted (that's why i'm trying to flash a CR)
Similar device: Teclast P10 (probably the m3f5)
And i'm trying to flash a ported TWRP (ported by ME )
That's all, thank you for reading my post and trying to help me.
Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
Adroid One 10
Unlock solved and installed the lineage OS a several times in twrp with success according to the given instruction here:
https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt
but the phone didnt boot the OS after restarting neither in slot A nor B. In twrp u could read that there was "no OS installed" (??).
In the last try i changed the slot before installing and now the phone hangs in a restart loop with download mode and i connot turn down the phone or get back to twrp. Trying to connect it by adb to restart twrp is not working....
=========================
My errors while trying to get out:
=========================
fastboot boot twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot B:\Various\Nokia\TWRP\twrp.img
downloading 'boot.img'...
OKAY [ 0.969s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.011s
fastboot flash recovery twrp.img
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery B:\Various\Nokia\TWRP\twrp.img
target reported max download size of 402653184 bytes
sending 'recovery' (42412 KB)...
OKAY [ 0.953s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.968s
So right now I'm at the end with my rudementary skills here.
Any idea how to get back to the point with twrp and installing an OS?
Thanks.
In case that no one else answers but someone else have the same problems , I write my solutions here.
.......
I got back to twrp by changing the slot in ADB
fastboot --set-active=a
unfortunately the restart loop doesn't end and no OS starts wether in slot a or b.