Hello guys
I completely formatted the phone including internal data and everything but then i accidentally restarted the device and now its stuck in fastboot mode with device state unlocked and whenever i try to flash twrp for oneplus 6 it gives me this error
PS C:\adb> fastboot boot twrp-3.2.3-1-enchilada.img
downloading 'boot.img'...
OKAY [ 0.638s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.682s
PS C:\adb>
Related
Hello, on March 10th I received a new update on my N5. After update, which finished with no problems as usual, my phone was normally working or about two more hours. In that time no new apps were installed. Then it just shut down, and can't be properly turned on.
It always stuck at Google logo and that is all that it does. I'm able to get to the fastboot mode by holding Power+Volume Up+Volume Down buttons, but I can't get into Recovery Mode option to hard reset it. Nothing show up after selecting that option and Power+Volume Up does nothing. Ok, bad luck, time to flash it nice and clean.
Haha, nice try.
I'm not sure if I had USB debugging on or off, but I think off. Obtained ROM from Google + newest platform tools from SDK and followed all possible manual I could get from Internets, results:
Code:
adb devices
List of devices attached
*nothing*
Code:
adb reboot bootloader
error: no devices found
Drivers are newest from Google, reinstalled several times, device is visible in Windows as Android Bootloader Interface and seem working fine. adb just do not see phone.
Code:
fastboot oem unlock
...
OKAY [ 46.402s]
finished. total time: 46.403s - WORKS!
But rest is just no go:
Code:
fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase cache
********Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.217s
Code:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.218s
I tried several more commands, like to install twrp, but all with same results.
Code:
fastboot flash recovery twrp.img
sending 'recovery' (14314 KB)...
OKAY [ 0.653s] writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.835s
I also tried "fastboot boot twrp.img" and it worked but didn't helped much. Internal storage is showing size 0 MB an when I try to do anything it ends with wall of red text about how it's unable to find partitions or mount images, first line:
Code:
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
Also when I reboot bootloader, it get stuck and when I get it back with buttons, it is back in its locked state. So my guess is that eMMC went to Silicon Heaven.
Do you guys have any advices? Or is my phone just fancy mirror now?
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
audit13 said:
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
Click to expand...
Click to collapse
Like i wrote, it get back to locked state.
The emmc chip is defective and cannot be fixed. This is clearly indicated when the bootloader relocks itself at reboot.
Thought so, but wanted confirmation . Thank you.
My Archos Helium 70b is totaly bricked:
Hi all,
I got a bricked phone with following symptoms:
Normal boot stays in an endless bootloop.
Starting up from recovery does the same.
3th option is fastboot: If I want to fastboot from a previously downloaded image with 'fastboot boot boot.img' command I got this:
Code:
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.688s
Any option to unbrick the phone left?
Thx
T
Hello,
My Phone (Honor 6X BLN-AL10) is brick
Here the link: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601
On Fastboot Mode show only PHONE Unlocked and on normaly Boot: func No 11 and 2
dload not working it show the message func no 11
recovery flash show me:
target max-download-size: 450MB
sending 'boot' (15840 KB)...
OKAY [ 0.542s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.579s
and recovery too.. what can i make now? oooh and with : fastboot -c "console=ttyHSL0,115200,n8" boot BOOT.img comes:
creating boot image...
creating boot image - 16222208 bytes
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.739s
thx for your answer
What have done? Hwota first flash the twrp recovery.
Hi,
Yes i wanna upgrade my phone from emui 5 (Android 7) to emui 8 (Android Oreo)
Okey i follow this how to: https://forum.xda-developers.com/hon...or-6x-t3792601
But on TWRP Section my phone print error on partition i dont know which....
next Boot Installing dload twice and now bricked phone
dload not working the only thats work is download mode and HiSuite say not compatible phone
I dont know frp lock is on or off
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Why not try installing TWRP via magisk?? Its easier that way
/\ agree /\
:angel:
lawrence_craig said:
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Click to expand...
Click to collapse
Make sure you are using the latest TWRP img.
Never flash recovery. Always boot recovery and then install TWRP zip. Have you not read the instructions?
As others mentioned, easier way to recover TWRP is to flash a magisk patch boot.img and flash TWRP zip in magisk.
Thanks for the tips guys, all sorted!
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
@Peterrrrr said:
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
Click to expand...
Click to collapse
I have never tried msmtool, but it sounds like a driver issue. Maybe take a closer look at their instructions
You can try these fastboot flashable stock roms.
You have few options to solve your issue. Now you are in slot B. You can change switch partition to A with fastboot. Try use: fastboot --set-active=a. It will switch to partition A and then try to boot/flash recovery. Also you have try to use fastboot roms with flashall.bat. There are few availaible in forum.
If you would like to use MSM you have to connect phone in proper mode to PC. Power off and hold Vol+ then connect. Also try to install latest Qualcomm drivers.
Msm tool
Download and use msm tool