Related
Hey, i tried to install the android 6.0 beta from this forum, but i was rooted, now its stuck in a loop where it turns off, turns on and tries to install it and fails at 0%, and again. I can enter Fastboot/rescue mode and thats it. I tried to flash recovery boot and system.img in adb and fastboot, but it shows this:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 1.265s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.265s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.858s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.874s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system.img
unknown partition 'SYSTEM.img'
error: cannot determine image filename for 'SYSTEM.im
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
Help pls. I tried everything...
System.img flash failed after 2 mins now too. Still no idea.
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.
daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Click to expand...
Click to collapse
Ive got all the informations for getting the bootloader unlock code, but when i type it in the thing by huawei to get the unlock code it tells me that its wrong... I could get it here if you could help me with it?
Hello,
I'd like to request a bootloader unlock code for my Huawei device
Information:
Product: HUAWEI ALE-L21
SN:
IMEI:Nvm
Product IDups.
Thank you!
So, this is the e-mail i sent to Huawei, they couldnt help me. Everything here is directly from the phone itself, so i dont think its wrong.
With the Product ID, you can get the code, but the details above are wrong, more precisely one of them, which is the Phone Name
Try it without the HUAWEI, it should look like this: "ALE-L21" (without the " of course).
If it somehow would not work for you, I sent you a PM with your unlock code in it.
Note: I recommend not to publish your information like this. The phone is blockable with the IMEI remotely by the service providers or the police. Please remove them for your own safety.
Tried the update again, now flashing doesnt even work.
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
Hey all,
I recently bricked my Huawei p9 lite VNS L31 by wiping ALL partitions , I manged to restore all factory images via an adb shell , but whenever I try flashing the vendor.img I am met with the following error:
target reported max download size of 471859200 bytes
sending 'vendor' (424761 KB)...
OKAY [ 10.666s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.701s
I have already locked and re-locked my bootloader several tiles (so don't ask me to , erecovery is useless as always as is the dload method)- I have a feeling my drivers are the problem but I an not sure.
Without the stock vendor.img my phone will not boot
Could a kind soul plleeaasee help me?:angel:
Do you have TWRP installed ?
yes
What's your model exactly ? VNS-L31Cxxx ?
FunnkyHD said:
What's your model exactly ? VNS-L31Cxxx ?
Click to expand...
Click to collapse
VNS-L31 c432b171 (nougat version)
VNS-L31 c432b161 (marshmallow version)
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
UselessIdiot said:
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
Click to expand...
Click to collapse
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
It says "Getting package info failed"
My internet connection should be ok.
But I didn't try factory reset yet.
Shall I try?
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Download b560 fullota-MF-PV !!!
Flash it using twrp open Kirin edition the one here on the forums
First flash the update zip and then the second file with it
U will be back to stock & receive updates
If anything happens & the system ask for reset simply erase data and redo the process and that's it {I did this many times since I always brick my phone with testing & always worked}
ceriqdesign said:
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
Click to expand...
Click to collapse
The Bootloader is unlocked but TWRP isn't installed.
UselessIdiot said:
The Bootloader is unlocked but TWRP isn't installed.
Click to expand...
Click to collapse
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
>fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.626s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.637s
OEM-Unlock is not Enabled
And I cant relock the bootloader.
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
UselessIdiot said:
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
Click to expand...
Click to collapse
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
ceriqdesign said:
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
Click to expand...
Click to collapse
I can't transfer Gboard from another phone, bacause my phone is stuck in the establishment phase.
I can't give my PC access to my files.
So i cant fill in my google account and because the FRP is still active i cant bypass the google protection. xD
Done! My mobile phone works again XD
But I would like to get away from the test keys.
UselessIdiot said:
Done! My mobile phone works again XD
But I would like to get away from the test keys.
Click to expand...
Click to collapse
did you already tried HuRUpdater method?
ceriqdesign said:
did you already tried HuRUpdater method?
Click to expand...
Click to collapse
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
UselessIdiot said:
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
Click to expand...
Click to collapse
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
ceriqdesign said:
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
Click to expand...
Click to collapse
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
UselessIdiot said:
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
ceriqdesign said:
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
Click to expand...
Click to collapse
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
UselessIdiot said:
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
Click to expand...
Click to collapse
sorry..but have you renamed twrp to recovery.img?
if it showed FRP Lock in bootloader with green font it's mean that the bypassed is not successful..did you try both method in the video?
Hello, I'm new here so if I miss any Forum rules please let me know.
TL;DR: I unlocked the bootloader of my VNS-L31 with PotatoNV and now I get the Message FAILED (remote: 'image verification error')
So, i want to install a Custom ROM in order to get OTG Support for my Smartphone. I'm new to this but as I figured out I need to do the following Steps.
1. Unlock Bootloader using PotatoNV
2. Install TWRP
3. Root via SU
3. Install CustomRom via TWRP
I think I managed to unlock my bootloader as I get the "your device cant be trusted" message every time I boot. I can enter fastboot mode with ADB and my device is recognized when it's in fastboot mode. when I try now to install TWRP (i tried different versions) I get the following message:
J:\Smartphone\TWRP\platform-tools_r31.0.2-windows\platform-tools>fastboot flash recovery twrp-3.1.1-0-venus.img
Sending 'recovery' (24464 KB) OKAY [ 0.648s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed
Reading the Forums suggested to relock the Bootloader and then unlock it again in good old " did you turn it off and on again" manner. but when I googled how to relock and unlock I got the warning that a lot of devices cant be unlocked a second time. So should I try to relock it via fastboot ? if I do so, can I unlock it again with the new unlockcode i set in PotatoNV, or do I need to open my phone for Testpoint mode and unlock it with PotatoNV again?
so hopefully i didn't miss any necessary information and someone here can help me or point me in the right direction
greetings
Elfenfreund
PS: Pardon my Writing. It's late and my English is not very trained.
No need to relock. Just unlock it again using the code given by the Potato. Then try flashing again the image.