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
hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
hsl43 said:
hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
Click to expand...
Click to collapse
Google updated the Android SDK (fastboot) in November of last year to enable flashing the extremely large Lollipop system.img files.
Update your Android SDK to the latest and you should be good to go.
FWIW: flash_all does not work.
RESOLVED. for the benefit of anybody else that may run into this problem...
after much Google sleuthing and gnashing of teeth, it turns out the solution was... to simply switch which USB port on my laptop the cable was plugged into. for the life of me, i don't know why, but i'll take it.
thanks @cam30era for your reply! your recommendation may have been a part of the solution, but as a developer, i keep my SDK reasonably up-to-date, so that particular issue didn't come into play in this instance. nonetheless, thanks very much again for taking the time to provide that info!
Hello,
I ‘ve tried to flash ma XIAOMI REDMI 3 PRO with twrp_ido, and now my phone cannot start, it is blocked on MI logo.
My phone is unlocked.
Fastboot is available.
Flash is Ok, but the recovery fastboot boot command is on error :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15502 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.204s]
finished. total time: 0.744s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.626s
I’ve tried to flash manually all IMG from a stable fastboot ROM. Everythings rules but I’m staying blocked on the MI logo after rebooting
I’ve tried many cable, many computers, many MIFLASH, many TWRP sources many forums but still on same error after rebooting :
I’ve tried also to install several rom Stable /DEV fastboot with fastboot option, it doesn’t work, a readrobust js encountered
I’m blocked since several weeks and I don’t know what to do.
Could you help me your assistance will be very (very very) appreciated.
Thanks in advance
Philippe
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
MHuncho said:
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
Click to expand...
Click to collapse
Hi,
That might be a simple answer but try to add the full path of the file at the end of the command :
./fastboot boot [drag the file and drop it next to the word "boot" to have its full path written down without any typos]
Let me know what you get
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.