I am a newbie to Android and I would like to get help about how to root my P10 Plus. I would need to find a detailed guide with download links. My device is huawei P10 Plus 128 GB Android 7.0 EMUI version 5.1 VKY-L29C185B124, I have enabled the developer mode and enabled the "USB Debugging" and "OEM Unblocking". I have found a few topics about how to root it, and tried to follow what it says, after I get my phone in fastboot and try to install the ".img", I get the following error:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.692s
Thanks in advance and sorry for my bad English, my newbieness, and if this was posted in the wrong forums section.
Related
It has taken a long since I tried to root my ZTE kis Q with no success. FramaRoot didn't work, so I tried adb and fastboot. However I think the recovery image from Clockworkmod is no working with my ZTE version, because it refuses to install it when I make
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img I get
> sending 'recovery' (3768 KB)... OKAY [ 0.142s]
writing 'recovery'...
FAILED (remote: partition 'recovery' not support flash )
finished. total time: 0.155s
Since I'm using linux I don't have drivers issues
Does anyone have an opinion about it.
Thanks
Hello,
i have a big problem yesterday i made the update to 560.
After this i want to root it i tried it with Kingroot *windows*.
After 50% the phone rebootet and show Fastboot screen and *Phone Unlocked*
So i thinked why not, so i tried to root with this
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
but CMD shows me only
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp_3.0
.2_mate7_6.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (11924 KB)...
OKAY [ 1.219s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.234s
Then i tried to relock bootloader but i have no Key. And i had not unlocked my Phone with a key....... whats wrong
you should take unlock code
Sent from my HUAWEI MT7-L09 using Tapatalk
If you need an unlock code this solved it for me,
Use king root, followed by Honor Tuner app
This is how I did it, couldn't figure out how to use Huawei site either
Follow this guide
http://forum.xda-developers.com/mate-7/general/unlock-code-via-honortuner-t3217651
All credits to that thread
Good Luck
KingRoot doesn't work for me on marshmallow. Oh well.
Have you tried using the android apk, not the windows application
funboomer2005 said:
Hello,
i have a big problem yesterday i made the update to 560.
After this i want to root it i tried it with Kingroot *windows*.
After 50% the phone rebootet and show Fastboot screen and *Phone Unlocked*
So i thinked why not, so i tried to root with this
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
but CMD shows me only
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp_3.0
.2_mate7_6.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (11924 KB)...
OKAY [ 1.219s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.234s
Then i tried to relock bootloader but i have no Key. And i had not unlocked my Phone with a key....... whats wrong
Click to expand...
Click to collapse
your system partition is corrupted,
Extract system.img from B560 firmware,
Flash system.img
hopefully it will be ok
Sorry for that late Post it helped. THX
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!
Hi.
I've been trying to flash twrp my Huawai Mate 8 for a couple of weeks. I keep getting the error I mentioned in the title. The bootloader is unlooked, frp is looked. USB debugging is enabled. OEM is grey.
Android version 7.0, emui version 5.0.1. I've been using the official twrp and used adb files and fastboot from other sources as well as official files. The phone is NOT rooted.
Here is the full message:
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22142 KB)...
OKAY [ 0.470s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.477s
I would appreciate any help as this problem has bugged me for so long by now. Thanks!!
So it's my first time ever trying to root a phone and i can't install TWRP on my phone (Mate 10 Lite). My phone has both OEM unlocked and USB debugging on. I'm using ADB to install it.
That's what i get when i type in "fastboot flash recovery twrp.img" to the command window:
target reported max download size of 471859200 bytes
sending 'recovery' (25170 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.636s
twrp file I'm using: https://forum.xda-developers.com/ma...s-recoveries--other-development/twrp-t3737747
and the tutorial I followed: https://www.xda-developers.com/how-to-install-twrp/
It's my first time ever doing something like this so please be understanding.