So I tried the flash-all to update to new version, and it failed with the system.img error everyone talks about.
I saw that that was common, so I went ahead with flashing each image separately. However, when I try to flash the bootloader, I get the following error:
E:\adb\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot flash bootloader boot.img
target reported max download size of 518205818 bytes
sending 'bootloader' (8278 KB)...
OKAY [ 0.555s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: header error)
finished. total time: 1.143s
Any idea how to fix this? Googling it didn't come up with anything. I just downloaded the newest version of fastboot by updating the android SDK today, so I don't think it's that.
I got the exact same error when I tried flashing my Nexus 5, before attempt my Nexus 9. I actually uninstalled the SDK and dowloaded and installed a whole fresh version and the Flash All script worked fine after that for both the N5 and N9. Both have been running great! The animations, volume slider for exampt, are so much smoother in M. Lots of little tweaks.
If it's working properly on the N9, fastboot will sparse the System image and send it to the device in multiple uploads and flashes.
Of course you would have failed. You have done it the wrong way. The bootloader command should be like:
fastboot flash bootloader bootloader.img
but you flashed bootloader with kernel boot.img
Related
Hi guys
So the problem I faced, I accidentally formatted my personal data off my phone, which included a rom I had just put onto my phone to install.
Obviously the rom had been deleted too, so I decided to ADB sideload a rom. As I did this I ran into an error reading 'Error: closed'. I couldn't find a way around it so I decided to use hasoon2000's tool to flash RUU zip. It mentioned that I'd need to relock the Bootloader in order to do so, so I simply relocked it using the tool. However, when trying to flash RUU from zip I get error:
sending 'zip' (711168 KB)...
OKAY [ 88.290s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) time: 4283
(bootloader) rom parsing finish ...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 124.368s
Click to expand...
Click to collapse
I also get Customer ID error when trying to use RUU exe
I made an attempt to unlock the bootloader again, after failed 4 times, I decided to do one last try and it suceeded.
How would I go about using the RUU now? Should I risk relocking my bootloader? Should I leave bootloader unlocked and use RUU?
Or how would I get a rom onto SD card via fastboot?
Many thanks!
I have read. But I don't know much about your phone version. I don't know much about your OS. If you want help fill in your profile or at least gave the basics infos.
I am not a developer, but would like to consider myself an advanced user.
After unlocking the bootloader, I have installed custom ROMs on three different devices at different times. I have also installed the stock ROM. But have never locked the bootloader back.
However, on the current device (that was looping through the bootloader), I installed the stock ROM (RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC.xml) and locked the bootloader. Successfully updated it to the official OTA Lollipop 5.1.
After that, I just tried my luck to install Ubuntu Touch (ported actually for Moto G [falcon] by h2o64, based on this thread). I unlocked the bootloader again for this. The install was 'successful' (there were no errors surprisingly), but the device obviously did not boot.
Now, I wanted to reinstall the stock firmware on the device. This time however, it fails at this command:
sudo fastboot flash partition gpt.bin
Here's the result >
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.087s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.667s
I have used fastboot in Linux all the other times I said I installed custom and stock ROMs.
However, I tested with mfastboot on Windows 10 as well, with no luck.
I am also able to successfully install TWRP recovery on the device and erase "system", "cache" and "userdata" using fastboot. However, cache and dalvik cache removal fails on TWRP.
Finally, although the partition flash command (which I personally understand as creating the partition table - correct me here please) and the motoboot.img flash command failed, I ran the rest of the commands and successfully installed the stock ROM mentioned above. However, this time, the "fastboot oem lock" command fails.
Any suggestions would be of great help... (it's not my phone)
hii.
i am new on this site and android too but about 3 days gone after i was tring to flash android but with noluck.
1.i have bootloader unlocked and s-on
2.i have 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip downloaded from this site
3.i also tried to flash androd i create new folder and fill this files:adb, AdbWinApi, AdbWinUsbApi, fastboot, rom(witch is 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
4.i launch htc one m8 bootloader mode and use this commands :
fastboot devices
fastboot oem rebootRUU
fastboot flash rom.zip
and here is error:
sending 'zip' (1687272 KB)... OKAY
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
need to fix this issue please help me on this
HTC_E11 version
Before:
I just unlocked the bootloader and installed a custom ROM (LineageOS 15.1: https://forum.xda-developers.com/huawei-y6/development/lineageos-15-1-huawei-y6-2018-t3832278) on my Huawei but it won't let me flash the TWRP from adb. I tried before flashing the custom ROM and also after but no progress. I tried with 'fastboot flash recovery recovery.img' as well as 'fastboot flash boot recovery.img' because I knew some smartphones include the recovery in the boot.img but I am always getting the same error:
Code:
fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16544 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.553s
I am not an expert but I understood that 'recovery' partition doesn't exist. I found some possible solutions online such as writing 'fastboot flash RECOVERY recovery.img' or 'fastboot flash erecovery recovery.img' (because Huawei calls the stock one 'erecovery') but they both gave me another error:
Code:
fastboot flash RECOVERY recovery.img
target reported max download size of 535822336 bytes
sending 'RECOVERY' (16544 KB)...
OKAY [ 0.522s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.528s
UPDATE: I found, maybe, the correct name of the recovery partition and it seems to work:
Code:
fastboot flash recovery_ramdisk twrp.img
< waiting for device >
target reported max download size of 535822336 bytes
sending 'recovery_ramdisk' (14026 KB)...
OKAY [ 0.443s]
writing 'recovery_ramdisk'...
OKAY [ 0.323s]
finished. total time: 0.767s
BUT it actually doesn't work properly because when I boot into recovery it boots the stock one. I tried other solutions found on the net like instantly unplug the phone after the flash and reboot it into recovery immediately but again it boots into stock one...
OTHER UPDATE: I managed to find and flash a TWRP that can boot up but it shows the internal storage 0MB not allowing me to install any .zip file. Because of that, I cannot install SuperSU to get root access.
I tried installing TWRP also with stock ROM but still showing 0MB because the phone is encrypted. To disable encryption I need to install the bluspark TWRP (As I found online), the problem is that bluspark won't boot and gets immediately overwritten by the stock ROM as it happened with the one I mentioned in the first update of the post.
Now I will try buying a microSD card and see if it shows right so that I can still flash .zip from the microSD card.
Now:
LATEST UPDATE: The SD card is working properly and I see it as around 60 GB instead of 64 but that's not the problem. I can see the .zip files I'd want to flash but when I try to do it it says me that it failed to mount every single partition and after some research I discovered that my Huawei has all the data encrypted. After other research I found that there are some TWRPs like blu_spark that could decrypt the data but every version I tried doesn't work and gets immediately overwritten by the stock recovery.
Does anyone know other methods to decrypt all the data on Huawei? Otherwise it's impossible to flash any .zip. Actually it flashes it but it fails to update the partitions state so the system doesn't recognize the changes.
Rooting Huawei is so difficult.. I will buy an OP5t as soon as I have the money XD.
Y6 2018 twrp
Any progress? I'm also looking for a version of TWRP that works with the Y6 2018.
I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.