So I managed to get the phone bootloader unlocked by following one of the guides, cross-flashed a ULM firmware, then followed the EDL method guide and this time it worked. It wouldn't work before cross-flashing the ULM firmware for some reason.
However, i cannot flash the rooted magisk boot image, i get this error in command prompt when i run the command "fastboot flash boot_a magisk_patched.img": fastboot: error: cannot get boot partition size. I also tried "fastboot flash boot magisk_patched.img", but i get the same error.
I'm stuck here, basically one step away from root. What is going wrong? How do i fix the error "cannot get boot partition size" to flash the pre-rooted image?
Load the boot patched via Qfil
Related
Good day friends
d855t have just hurts my hand in fastboot,
does not enter the installation mode,
I tried to write the boot gave the cmd error
I tried to patch gave error recovery,
please help ...
cd c:\ sdk-tools
From there flash aboot:
fastboot flash aboot aboot.img
Next boot laf:
fastboot boot laf.img
error:commad...
failed writing block
The right command to write the boot partition
fastboot flash boot boot.img
aboot is the bootloader
I tried giving the error can not be my friend
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
I really Need help. I tried everything from xfstk(It reboots in fastboot but no 4 colors) to Aft (failed to flash GPT ERROR). When I try to flash recovery with Adb it's works but when I reboot in recovery appears "error!" Blinking. I found GpT failed Also when fastboot OEM partition tbl. Any solution?
mediih said:
I really Need help. I tried everything from xfstk(It reboots in fastboot but no 4 colors) to Aft (failed to flash GPT ERROR). When I try to flash recovery with Adb it's works but when I reboot in recovery appears "error!" Blinking. I found GpT failed Also when fastboot OEM partition tbl. Any solution?
Click to expand...
Click to collapse
go to the following link. and see section flash firmware without AFT. now run each and every command in same sequence as suggested. run all command even if some of them fails. (probably partitioning commands will fail). first boot will take long time don't interrupt. if still fails flash xFSTK files again. never ever use AFT after that.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following link. and see section flash firmware without AFT. now run each and every command in same sequence as suggested. run all command even if some of them fails. (probably partitioning commands will fail). first boot will take long time don't interrupt. if still fails flash xFSTK files again. never ever use AFT after that.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much for support, I've already tried your guide. Now, I've retried but only fastboot oem partition /tmp/partition.tbl Fail.
When I reboot with the last CMD command the phone returns in "Error!" blinking. I've no Idea what to do.
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
please , i want to know , how can i give fastboot on my redmi7 device
H R Habib said:
please , i want to know , how can i give fastboot on my redmi7 device
Click to expand...
Click to collapse
This is a forum dedicated to the Poco F3 so I think you should ask it on the Redmi 7's forum
Use MiFlash to flash the fastboot Version of stock.
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Phoost said:
Use MiFlash to flash the fastboot Version of stock.
Click to expand...
Click to collapse
I didn't find an official MiFlash tool and I don't trust closed-source tools for this kind of things.
avidduo said:
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Click to expand...
Click to collapse
I tried that but it didn't work.
EDIT: After re-trying several times, I was finally able to make it work by booting with ArrowOS' recovery. TWRP was not accepted, but ArrowOS' one was
So I've been able to flash the Xiaomi.EU rom, I'll stick with it for now.
I was trying to root my moto g8 play, as there is no TWRP for my device (at least I didn't find one), I tried a diffrent method:
I got the exact same firmware and extracted the boot.img, patched it using magisk, then installed it on fastboot mode with the commands:
fastboot flash boot_a patched.img
fastboot flash boot_b patched.img
fastboot reboot
After this my device went into a bootloop, I tried fixing it with the commands in the flashfile.xml, but now it just says "Your device is corrupt. It can't be trusted and may not work properly" and doesn't turn on.
Note: Bootloader is unlocked
Is there anything I can do?