Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Fastboot Download Partition
261 views
Skip to first unread message
Janita Castricone
Jan 10, 2024, 2:41:10 AM1/10/24
to
TWRP recovery will get into a boot loop but fastboot works so I reflashed TWRP recovery and then recovery works fine. But I can't reset/wipe/mount/etc. anything from within recovery as I just get errors:
fastboot download partition
Download https://3noduquiji.blogspot.com/?rhwc=2x6QYI
I thought I could use my nandroid backup to flash system.img, etc. to overwrite what's there but it's one big .win file. So I looked up the fastboot commands anyways and stumbled on an xda thread about un-bricking TF300s where they used fastboot erase on every mount point then fastboot flashed the stock firmware blob file from Asus' support website. Ran perfectly and now I have my tablet back! So all you need is fastboot to go completely back to stock.
I recently started to play around with the db410c. I was able to build the AOSP master with few patches that I found around on Linaro repo. Anyways, I have some problems understanding the bootloaders components / partitions while debugging the problem.
From the documentation it seems you can recover partition table and bootloaders using qdl tool, from this link I got the packages ( ). I tried the AOSP package but it does not contain the prog_emmc_firehose_8916.mbn flasher and if I use the same flasher on AOSP package it does not work.
So, using the linux package I was able to recover the board and start it in fastboot. Now, even if I flash again the partition table with the aosp partition table I cannot flash the boot partition. When I use flastboot flash boot boot.img it keeps saying:
Sounds like a messed up partition table. Did you install AOSP using the flash-all-aosp.sh in the installer directory (which sets up the partition table also)? Or are you trying to just flash the partitions manually?
To start this out. I have unlocked bootloader through various methods on many diffent devices befor. I have followed the guide on the fairphone website to the letter including the fastboot commands that should be used if the regular ones do not work.
I have adb fastboot on my laptop is because I wanted to flash something on my lg v20 and I was to impatient to wait until I got home so it has been tested recently. And I also just reflashed twrp 3.7.0 on us996 to make sure no space radiation came down and switched a transistor or something.
Not to doubt you but i have never heard of fastboot behing picky with a cable provided that the cable is able to transfer data. I only installed the driver a month ago on my laptop. I am more inclined to think that an older version would work better at this point as this is the newest as far as i am aware.
It is highly unlikly but maybe I ripped something out of the laptop that i shouldnt have. Maybe windows microsoft edge, windows stock music player or god forbid cortana is needed to use fastboot properly for modern phones. I dont know at this point
Update: It worked even less there but only to the extend that i had to set the fairphone up as an adb/fastboot device in the device manager first. When that was done the outcome was the same as befor on my laptop.
Edit 1: Yep i read the section hardware buttons again. If i didnt explore the bootloader befor doing trying to unlock this this would not have happen is there a reason there are two fastboots (no idea if thats the right term.
Dont know the difference however both exist on the FP4 as well. I used adb reboot fastboot and landed in fatsbootd as well, what I think does not happen on the FP4 however thought it was a coincidence. How did you boot into it also with adb?
Exactly i did go there the first time using commands because i was curious if i could boot directly into fastboot on this phone because the v20 would always just restart leaving me to go there the manual way. After that i just went there manually.
The fastboot that is reached when using the command adb reboot fastboot has (to my current understanding) the functions to unlock the bootloader disabled on only rudimentary fastboot functionality which would explain why it understood fastboot reboot but not fastboot flashing unlock.
Edit 1: Now knowing that Fastbootd is not some weird typo or necessary evil and after a quick google search i know that fastbootd is its own thing it was intruduced with android 10 (so 2 depending on view 1) android version after what i used to. What it does, not clue and off topic.
had no issues this way as long as you wipe with the last command it should boot fine. headphone fix posted above did work but you do need to be rooted for that to work. you can manually adjust the size of the partition but this way works fine for me in this case. that guide is here on the forum as well for the 2e. i can write up a more detailed version tonight when i have the phone available again to me. also make sure you are using the proper lineage version for this phone and to extract the zip you download to only be the img file do not try to flash the zip file itself (some people do not know to do this) you can also use twrp if you wish also found here on the forum.
Ok lineage-18 seems to have installed fine too, but again, you need to get to that specific incarnation of fastboot by using adb reboot fastboot. Since I had lineage-17 installed, I enabled advanced reboot and used the bootloader option and that brought me to fastboot verified by fastboot devices and again flashing failed with:
i have installed windows 8.1 and ubuntu on my new computer, and get the following error when i try to mount the device. I already googled and turned all the hibernation / fastboot options off, but i still have this problem. The option secure boot is disabled in the UEFI-BIOS aswell. Does anyone have an idea, what might cause the problem? And is there a chance to overwrite the Ubuntu error and mount the device -w to do some testing?
The flash-all.bat disconnects the device and I had to reconnect and switch to fastbootmode again. Then the script goes further. When the script is done the OS should be flashed. But in my case it only shows the first splash screen again and again. I tried it so many times and with so many things but always the same result.
Now im at a point where im not be able to turn the Radxa Zero in Fastboot mode. The bootloader.bin and the factory-loader.bin are not working anymore for it.
When I unplug and replug it, it wants to boot the half flashed OS and it shows the first splashscreen again and again. To come in fastboot mode again I have to replug it with the USB button and execute the bootloader again.
Then I remembered that I had seen this before, and dug up the Download Platform Tools page, and downloaded version 29.0.5 for Linux. I extracted only the fastboot binary to the folder with flash.sh, chmod +x fastbooted it, and finally succeeded flashing my device with this command:
That is, temporarily prepend the current folder to the path, so that the older Fastboot gets found first, and it can successfully flash the boot partition, and all the remaining operations succeed as well.
But, a few minutes on the web brought me to an issue discussion with Phhusson and Android2468 about this issue, and Phhusson recommended that Android2468 delete the product partition so there would be room to flash the system partition. So, I followed suit:
1) Fastboot supports OEM (original equipment manufacturer) command extensions (such as fastboot oem lock/unlock) which should be implemented by vendor.
fastboot oem format - is a command for creating new GPT table on eMMC for further flashing appropriate partitions. It should be done if partition table was modified or was not created before.
I have created an image for olimex lime2 for SD-Card which is working good, same I build for emmc,Now I have one problem how can I copy my image to emmc as per BBB I need to run a script during booting with sd-card which will copy the content of sd-card to emmc.At the same time, I came to know that olime lime2 support FEL booting so I have created image with -w option which will segregate the image by its partition,I had copied the part0.img(which is uboot) to the uboot of SOC, it will take me in FASTBOOT.Now I tried to copy the system-boot and writeable part to emmc of SOC via FASTBOOT,but it will expect writeable and system-boot in sparse format.My Query is -1- How I convert part1.img(system-boot) and part2.img(writeable) in sparse format, do i use simg2img tool to covert the raw image in sparse(FASTBOOT) format ?2- As ondra suggested that I need to divide the large writeable image into chunks, pls suggest how can I achieve this.
Yes we need two separate images, first image(u-boot-sunxi-with-spl.bin) which is used to make the device in fastboot boot mode.
Once we are in fastboot mode we flash rest of the image into the emmc i.e u-boot binary and writable image.
dragonboard builder will give you file per partition, as long as gadget has those files
so if you need 1st stage bootloader and u-boot as separate files and gadget has those, as separate files. Then you should be good, just make sure gadget.yaml represent correctly your part table
The fastboot protocol is a mechanism for communicating with bootloaders over USB or ethernet. It is designed to be very straightforward to implement, to allow it to be used across a wide range of devices and from hosts running Linux, macOS, or Windows.
Fastboot binary will follow directions listed out fastboot-info.txt build artifact for fastboot flashall && fastboot update comamnds. This build artifact will live inside of ANDROID_PRODUCT_OUT && target_files_package && updatepackage.
Where data_size is an unsigned 8-byte big-endian binary value, and data is the fastboot packet. The 8-byte length is intended to provide future-proofing even though currently fastboot packets have a 4-byte maximum length.
Firstly, boot from a UEFI Windows 8 recovery disk (CD/DVD/USB) - I found that the automated recovery process didn't find the correct Windows partition, nor when I managed to add it to BCD settings would it make it reliably bootable e.g. using BCDEDIT I got it to find and launch the Windows partition but it refused to cold boot or would not "keep" the settings after a 2nd reboot or power off.
35fe9a5643
fastboot download partition
Download https://3noduquiji.blogspot.com/?rhwc=2x6QYI
I thought I could use my nandroid backup to flash system.img, etc. to overwrite what's there but it's one big .win file. So I looked up the fastboot commands anyways and stumbled on an xda thread about un-bricking TF300s where they used fastboot erase on every mount point then fastboot flashed the stock firmware blob file from Asus' support website. Ran perfectly and now I have my tablet back! So all you need is fastboot to go completely back to stock.
I recently started to play around with the db410c. I was able to build the AOSP master with few patches that I found around on Linaro repo. Anyways, I have some problems understanding the bootloaders components / partitions while debugging the problem.
From the documentation it seems you can recover partition table and bootloaders using qdl tool, from this link I got the packages ( ). I tried the AOSP package but it does not contain the prog_emmc_firehose_8916.mbn flasher and if I use the same flasher on AOSP package it does not work.
So, using the linux package I was able to recover the board and start it in fastboot. Now, even if I flash again the partition table with the aosp partition table I cannot flash the boot partition. When I use flastboot flash boot boot.img it keeps saying:
Sounds like a messed up partition table. Did you install AOSP using the flash-all-aosp.sh in the installer directory (which sets up the partition table also)? Or are you trying to just flash the partitions manually?
To start this out. I have unlocked bootloader through various methods on many diffent devices befor. I have followed the guide on the fairphone website to the letter including the fastboot commands that should be used if the regular ones do not work.
I have adb fastboot on my laptop is because I wanted to flash something on my lg v20 and I was to impatient to wait until I got home so it has been tested recently. And I also just reflashed twrp 3.7.0 on us996 to make sure no space radiation came down and switched a transistor or something.
Not to doubt you but i have never heard of fastboot behing picky with a cable provided that the cable is able to transfer data. I only installed the driver a month ago on my laptop. I am more inclined to think that an older version would work better at this point as this is the newest as far as i am aware.
It is highly unlikly but maybe I ripped something out of the laptop that i shouldnt have. Maybe windows microsoft edge, windows stock music player or god forbid cortana is needed to use fastboot properly for modern phones. I dont know at this point
Update: It worked even less there but only to the extend that i had to set the fairphone up as an adb/fastboot device in the device manager first. When that was done the outcome was the same as befor on my laptop.
Edit 1: Yep i read the section hardware buttons again. If i didnt explore the bootloader befor doing trying to unlock this this would not have happen is there a reason there are two fastboots (no idea if thats the right term.
Dont know the difference however both exist on the FP4 as well. I used adb reboot fastboot and landed in fatsbootd as well, what I think does not happen on the FP4 however thought it was a coincidence. How did you boot into it also with adb?
Exactly i did go there the first time using commands because i was curious if i could boot directly into fastboot on this phone because the v20 would always just restart leaving me to go there the manual way. After that i just went there manually.
The fastboot that is reached when using the command adb reboot fastboot has (to my current understanding) the functions to unlock the bootloader disabled on only rudimentary fastboot functionality which would explain why it understood fastboot reboot but not fastboot flashing unlock.
Edit 1: Now knowing that Fastbootd is not some weird typo or necessary evil and after a quick google search i know that fastbootd is its own thing it was intruduced with android 10 (so 2 depending on view 1) android version after what i used to. What it does, not clue and off topic.
had no issues this way as long as you wipe with the last command it should boot fine. headphone fix posted above did work but you do need to be rooted for that to work. you can manually adjust the size of the partition but this way works fine for me in this case. that guide is here on the forum as well for the 2e. i can write up a more detailed version tonight when i have the phone available again to me. also make sure you are using the proper lineage version for this phone and to extract the zip you download to only be the img file do not try to flash the zip file itself (some people do not know to do this) you can also use twrp if you wish also found here on the forum.
Ok lineage-18 seems to have installed fine too, but again, you need to get to that specific incarnation of fastboot by using adb reboot fastboot. Since I had lineage-17 installed, I enabled advanced reboot and used the bootloader option and that brought me to fastboot verified by fastboot devices and again flashing failed with:
i have installed windows 8.1 and ubuntu on my new computer, and get the following error when i try to mount the device. I already googled and turned all the hibernation / fastboot options off, but i still have this problem. The option secure boot is disabled in the UEFI-BIOS aswell. Does anyone have an idea, what might cause the problem? And is there a chance to overwrite the Ubuntu error and mount the device -w to do some testing?
The flash-all.bat disconnects the device and I had to reconnect and switch to fastbootmode again. Then the script goes further. When the script is done the OS should be flashed. But in my case it only shows the first splash screen again and again. I tried it so many times and with so many things but always the same result.
Now im at a point where im not be able to turn the Radxa Zero in Fastboot mode. The bootloader.bin and the factory-loader.bin are not working anymore for it.
When I unplug and replug it, it wants to boot the half flashed OS and it shows the first splashscreen again and again. To come in fastboot mode again I have to replug it with the USB button and execute the bootloader again.
Then I remembered that I had seen this before, and dug up the Download Platform Tools page, and downloaded version 29.0.5 for Linux. I extracted only the fastboot binary to the folder with flash.sh, chmod +x fastbooted it, and finally succeeded flashing my device with this command:
That is, temporarily prepend the current folder to the path, so that the older Fastboot gets found first, and it can successfully flash the boot partition, and all the remaining operations succeed as well.
But, a few minutes on the web brought me to an issue discussion with Phhusson and Android2468 about this issue, and Phhusson recommended that Android2468 delete the product partition so there would be room to flash the system partition. So, I followed suit:
1) Fastboot supports OEM (original equipment manufacturer) command extensions (such as fastboot oem lock/unlock) which should be implemented by vendor.
fastboot oem format - is a command for creating new GPT table on eMMC for further flashing appropriate partitions. It should be done if partition table was modified or was not created before.
I have created an image for olimex lime2 for SD-Card which is working good, same I build for emmc,Now I have one problem how can I copy my image to emmc as per BBB I need to run a script during booting with sd-card which will copy the content of sd-card to emmc.At the same time, I came to know that olime lime2 support FEL booting so I have created image with -w option which will segregate the image by its partition,I had copied the part0.img(which is uboot) to the uboot of SOC, it will take me in FASTBOOT.Now I tried to copy the system-boot and writeable part to emmc of SOC via FASTBOOT,but it will expect writeable and system-boot in sparse format.My Query is -1- How I convert part1.img(system-boot) and part2.img(writeable) in sparse format, do i use simg2img tool to covert the raw image in sparse(FASTBOOT) format ?2- As ondra suggested that I need to divide the large writeable image into chunks, pls suggest how can I achieve this.
Yes we need two separate images, first image(u-boot-sunxi-with-spl.bin) which is used to make the device in fastboot boot mode.
Once we are in fastboot mode we flash rest of the image into the emmc i.e u-boot binary and writable image.
dragonboard builder will give you file per partition, as long as gadget has those files
so if you need 1st stage bootloader and u-boot as separate files and gadget has those, as separate files. Then you should be good, just make sure gadget.yaml represent correctly your part table
The fastboot protocol is a mechanism for communicating with bootloaders over USB or ethernet. It is designed to be very straightforward to implement, to allow it to be used across a wide range of devices and from hosts running Linux, macOS, or Windows.
Fastboot binary will follow directions listed out fastboot-info.txt build artifact for fastboot flashall && fastboot update comamnds. This build artifact will live inside of ANDROID_PRODUCT_OUT && target_files_package && updatepackage.
Where data_size is an unsigned 8-byte big-endian binary value, and data is the fastboot packet. The 8-byte length is intended to provide future-proofing even though currently fastboot packets have a 4-byte maximum length.
Firstly, boot from a UEFI Windows 8 recovery disk (CD/DVD/USB) - I found that the automated recovery process didn't find the correct Windows partition, nor when I managed to add it to BCD settings would it make it reliably bootable e.g. using BCDEDIT I got it to find and launch the Windows partition but it refused to cold boot or would not "keep" the settings after a 2nd reboot or power off.
35fe9a5643
0 new messages