Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom
Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed:
Related
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
roelprincen said:
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
Click to expand...
Click to collapse
same with me ?
Try to relock and then unlock. I've had this problem too after downgrade to mm by official Huawei rollback package. Then phone and other tools shows than phone is unlocked and it was unable to flash recovery.
if it says wrong password it means you got the wrong password. it will say it's already unlocked if you try unlocking it while it's unlocked
My phone was unlocked with Potato v2.0.1, with working TWRP, rooted etc...
I solved this problem that arose after unsuccesfully install custom Rom, restore backup of stock rom, install update through dload and many many other attempts at improvement of my smartphone :-( No more time again!!!
Probably installing update through Dload will relock bootloader, but in the fastboot mode it says bootloader still unlocked.
Before I did all this, I had an original stock rom.
1: Relock bootloader with PotatoNV v2.0.1 (You need to open case and connect tespoint by wire - look on Youtube, i´ve find it there, also you need "Huawei testpoint drivers")
2: Factory reset
3: Install any update stock rom with Dload (Vol up + Vol down + power)
4: Factory reset
5: Developer options-turn on OEM unlock and USB debbuging
6:Unlock bootloader with PotatoNV v2.0.1 - keep password generated by Potato
7:Multitool 8 for Huawei - in the bootloader state unlock bootloader again - use password generated by Potato
8:Multitool 8 for huawei - install TWRP - it says "Succesfully installed" - TWRP works, root is possible. Yeah!!!
May be this is not right way to solve this, but for me it workś..
Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/
jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.
What about friends, it happens that I wanted to install TWRP to my OP6T, but it did not go well ... I followed the steps and when I gave "Reboot Recovery", I entered the fastboot mode, and it did not happen there, it did not allow me to flash the rom, the stock recovery, or the TWRP, tells me the following ...
This happens when wanting to boot the twrp.img:
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
PS C:\Users\vhr07\Desktop>
--------------------------------------------------------------------------------------------
This happens when you want to install the recovery stock:
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.518s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.536s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
I install the recovery by means of "boot" and it says OK, but when wanting to boot I get error:
PS C:\Users\vhr07\Desktop> fastboot flash boot recovery.img
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.518s]
writing 'boot'...
OKAY [ 0.271s]
finished. total time: 1.794s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.506s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.547s
PS C:\Users\vhr07\Desktop>
---------------------------------------------------------------------------------------------
These were my last attempts ...:
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (30948 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.734s
PS C:\Users\vhr07\Desktop> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.508s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.525s
PS C:\Users\vhr07\Desktop> fastboot flash recovery twrp.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16849 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.406s
PS C:\Users\vhr07\Desktop> fastboot flash recovery_b recovery.img
target reported max download size of 536870912 bytes
sending 'recovery_b' (65536 KB)...
OKAY [ 1.523s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 1.538s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b recovery.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.517s]
writing 'boot_b'...
OKAY [ 0.301s]
finished. total time: 1.824s
PS C:\Users\vhr07\Desktop> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.511s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.549s
PS C:\Users\vhr07\Desktop> fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (30948 KB)...
OKAY [ 0.714s]
writing 'boot'...
OKAY [ 0.154s]
finished. total time: 0.874s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30948 KB)...
OKAY [ 0.717s]
writing 'boot_b'...
OKAY [ 0.181s]
finished. total time: 0.904s
PS C:\Users\vhr07\Desktop> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.716s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.746s
----------------------------------------------------------------------------
Please, I need your help I promise not to ROOT again the hahaha team
I would pay if necessary
PD: already tried with bootloader unlocked and blocked
UPDATE: MSMTools, stuck on "PARAM PREPROCESSING"
https://imgur.com/qiaF8oh
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
foobar66 said:
First, flash the original boot.img again:
> fastboot flash boot_a boot.img
> fastboot flash boot_b boot.img
Then follow the instructions in https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482.
Click to expand...
Click to collapse
Same situation
PS C:\Users\vhr07\Desktop> fastboot devices
785694ef fastboot
PS C:\Users\vhr07\Desktop> fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.500s]
writing 'boot_a'...
OKAY [ 0.308s]
finished. total time: 1.814s
PS C:\Users\vhr07\Desktop> fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.498s]
writing 'boot_b'...
OKAY [ 0.345s]
finished. total time: 1.849s
PS C:\Users\vhr07\Desktop> fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.505s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.537s
PS C:\Users\vhr07\Desktop>
Seem look like usb debug not authorize pc
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
efebe said:
i had the same issue, and i was able to resurrect my phone, here's what i did:
Download both files from here
Once u are finished:
1.- Turn off ur phone
2.- Press volume up + volume down (at the same time, DONT PRESS POWER BUTTON) and plug ur phone into ur computer (the phone will go into QDL mode)
3.- Open msmdownloadtools mclaren
4.- Press START
5.- Wait for it to finish
You will have H2OS installed... now install OOS
This should work for you, since i was on the same boat as you. Good Luck!
Click to expand...
Click to collapse
MSMTools stuck on this
https://imgur.com/qiaF8oh
Vlodayax said:
MSMTools stuck on this
https://imgur.com/qiaF8oh
Click to expand...
Click to collapse
Click "stop" then "exit" and kill the program and start over. Keep trying. I was down a whole day and a half after trying to flash a Rom. I made it worst after wiping the system and the MSM tool saved my a$$.
Sent from my OnePlus6T using XDA Labs
My OP2 is bricked, just only use fastboot mode, when i use "fastboot oem unlock" command, it show ok & complete, and then offline suddenly.
So i try fastboot mode again, flash recovery, it show the phone is locked.
Can anyone help me ?
C:\WINDOWS\system32>fastboot oem unlock
...
OKAY [ 0.118s]
finished. total time: 0.118s
C:\WINDOWS\system32>fastboot flash recovery c:\twrp-3.2.1-0-oneplus2.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.653s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.673s
This phone have probably softbrick or hardbrick and bootloop and intro to recovery (no erecovery) gets a rescue mode screen
I have tried with the "potatonv" tool and trying to flash a stock rom and a custom recovery but none work and I have the bootloader unlocked but I get these following results:
>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 471859200 bytes
sending 'RECOVERY' (36118 KB)...
OKAY [ 0.986s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 1.012s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (36118 KB)...
OKAY [ 1.000s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.468s