Related
First of all, I would like to apologize if this question has been answered in another thread. I have searched the xda forums and others with no success.
My situation is the following:
Running on Windows 8.1
1. Rooted Nexus 4 on 4.4 (if I remember correctly)
2. OTA update to 4.4.2 (loosing root, but device remains unlocked) (I think I also tried flashing the factory image manually, but failed, I don't remember exactly)
I rooted my phone when Kitkat was fresh and found there were no custom roms on 4.4 yet so I went back to stock because it was the easiest way to get the update. Right now I can not flash a custom recovery.
fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
===================================================
fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
This is the same for both TWRP and CWM. I am very sure I did NOT misspell the name.
Does anyone have any idea why this is happening and how to fix it?
Thank you for taking the time to read this post!
You have to use this
fastboot flash recovery recovery.img
wrong syntax, must be: fastboot flash recovery recovery.img
Wow.... I am ashamed with myself. I cannot believing I missed that.
Thank you for the quick reply guys.
I was just doing the same here thanks!
command doesnt work for me
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
FastSl0th said:
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
In the xda forum, check carefully whether you are asking a question in the appropriate Q&A section for your device, because you are certainly not writing about Nexus 4.
.
FastSl0th said:
command doesnt work for me
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
Hopefully you may have already asked or solved this question. I am assuming you are issuing command from platform-tools folder. If you have a Windows 10 OS system then, I too could not found USB drivers for my system with windows 10. If 'fastboot devices' command returning some device id then maybe I have guessed wrong reason.
I entered "fastboot flash XXX.img" Too. hahaha
After i see this article, I entered "fastboot flash recovery flash XXX.img"
Thank you anyway.
unsolved
dan60 said:
unsolved
Click to expand...
Click to collapse
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How To Solve This Problem Brother..Please Tell me
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
d4_daman_ said:
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
Click to expand...
Click to collapse
Hi there!
It didn't work for me but you can try it >>>
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi guys, I found the same error when I've tried to install TWRP on mi Xiaomi Mi A3 by FASTBOOT on Linux Terminal.
After a lot of searching, I solved my problem using the syntax below:
"fastboot flash boot XXX.img"
"boot" is the partition about FASTBOOT are asking for.
Hope to be usefull.
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
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
bijilidk said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.
bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader
bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration
neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/
So everything is solved here right ? you can close this thread now i think !
Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Peskyleo said:
Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Click to expand...
Click to collapse
Flashing twrp has only ever worked for me if I immediately go into it I have never been able to get it to stick around after a restart
Peskyleo said:
Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Click to expand...
Click to collapse
Why u want to flash that recovery?
When usb cable is in phone with power+volup u will get emui recovery without usb u will boot costum (twrp) recovery. If u want to install oreo emui 8.0 use hwota.
Послато са WAS-LX1 уз помоћ Тапатока
nemanjsb said:
Why u want to flash that recovery?
When usb cable is in phone with power+volup u will get emui recovery without usb u will boot costum (twrp) recovery. If u want to install oreo emui 8.0 use hwota.
Послато са WAS-LX1 уз помоћ Тапатока
Click to expand...
Click to collapse
I already tried to do it without an usb cable plugged in but it will still get me to the EMUI erecovery one. What could be the problem? And if I install oreo 8.0 can I then root it anyways?
Peskyleo said:
I already tried to do it without an usb cable plugged in but it will still get me to the EMUI erecovery one. What could be the problem? And if I install oreo 8.0 can I then root it anyways?
Click to expand...
Click to collapse
Use HwOta method for emui 8.0 and u can root with magisk.
nemanjsb said:
Use HwOta method for emui 8.0 and u can root with magisk.
Click to expand...
Click to collapse
Thank you. I will keep you updated then!