Hello,
I can not flash a recovery on my P9 (EVA L09C432B399) to be able to root my P9. It is under 5.0.1 and android 7.
I tried a lot of TWRP.
Thank you for your help
Did you unlock bootloader, before trying to install twrp recovery ?
Yes it's unlock
chuppito said:
Hello,
I can not flash a recovery on my P9 (EVA L09C432B399) to be able to root my P9. It is under 5.0.1 and android 7.
I tried a lot of TWRP.
Thank you for your help
Click to expand...
Click to collapse
It must be TWRP for EMUI 5.01
https://forum.xda-developers.com/p9/development/twrp-t3565703
There is an enhanced version here
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Btw, Fastboot reporting error or what is exactly the problem?
zgfg said:
It must be TWRP for EMUI 5.01
https://forum.xda-developers.com/p9/development/twrp-t3565703
There is an enhanced version here
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Btw, Fastboot reporting error or what is exactly the problem?
Click to expand...
Click to collapse
thank you, the 2 links recovery do not work on my P9.
So I unlocked the bootloader.
I do :
adb reboot bootloader
fastboot flash recovery "the name of recovery.img"
as soon as i get the message okay, i reboot on the recovery and i still have the recovery stock installed.
The message after validating :
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.823s]
writing 'recovery'...
OKAY [ 0.325s]
finished. total time: 1.152s
chuppito said:
thank you, the 2 links recovery do not work on my P9.
So I unlocked the bootloader.
I do :
adb reboot bootloader
fastboot flash recovery "the name of recovery.img"
as soon as i get the message okay, i reboot on the recovery and i still have the recovery stock installed.
The message after validating :
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.823s]
writing 'recovery'...
OKAY [ 0.325s]
finished. total time: 1.152s
Click to expand...
Click to collapse
ha you have 1 error when you flash recovery write command fastboot reboot hold vol+ button and push enter when phone reboot unplug usb cable fast before reboot recovery in another time stock recovery back and must flash twrp again good luck
It's good he finally flash the second time the TWRP 3.1.1-1 by oldDroid - extended Version.
Root done thanks a lot for this second link
I booted with volume + so he probably already had a TWRP.
Thank you
Related
hey is it possible to root the phone without a developer rom?
Flo5190 said:
hey is it possible to root the phone without a developer rom?
Click to expand...
Click to collapse
Yup. Flash TWRP from here https://mega.co.nz/#!d0cFFCLZ!tZN38HAzpIKQXbsRkwVJBkyGr5f1OUPaIZkxt3Bfiak
and then flash supersu.zip
Kahun said:
Yup. Flash TWRP from here https://mega.co.nz/#!d0cFFCLZ!tZN38HAzpIKQXbsRkwVJBkyGr5f1OUPaIZkxt3Bfiak
and then flash supersu.zip
Click to expand...
Click to collapse
Hi, how to go to TWRP to flash supersu.zip?
vietvp said:
Hi, how to go to TWRP to flash supersu.zip?
Click to expand...
Click to collapse
Go into fast boot and use fastboot flash recovery.img
Kahun said:
Go into fast boot and use fastboot flash recovery.img
Click to expand...
Click to collapse
My rom is stable V6.5.10, i have flashed TWRP successful, but goto Updater -> Reboot to recovery mode and phone still boot to Mi recovery, not TWRP.
D:\Minimal ADB and Fastboot>fastboot flash recovery twrp_recovery_for_xiaomi_leo_en.img
target reported max download size of 1073741824 bytes
sending 'recovery' (46404 KB)...
OKAY [ 1.028s]
writing 'recovery'...
OKAY [ 0.367s]
finished. total time: 1.400s
I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.
Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I have VIE-L29 latest build
EMUI 5.0.1
Android 7.0
1. Bootloader is already unlocked. I used the code from Huawei.
2. Flashed TWRP (twrp-3.2.1-0-vienna.img) to recovery using Minimal ADB and Fastboot (result as shown below).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22456 KB)...
OKAY [ 0.879s]
writing 'recovery'...
OKAY [ 0.173s]
finished. total time: 1.068s
3. Tried several times but failed to boot into TWRP recovery. It just boots into the oem recovery everytime (volume down + power on button + plug in USB)
try to flash TWRP 3.1.1-1 (from here)
I advise you to flash it to recovery2 (not recovery) then just reboot and press vol up more then 3 secs
xzanium said:
try to flash TWRP 3.1.1-1 from here
I advise you to flash it to recovery2 (not recovery) then just reboot and press vol up more then 3 secs
Click to expand...
Click to collapse
sounds good, thanks. But just so as not to mess up:
-fastboot flash recovery2 twrp-3.1.1-1-vie.img
-fastboot reboot
please confirm, and then i'll be on my way to root!
cmd ok
xzanium you rock!
xzanium said:
cmd ok
Click to expand...
Click to collapse
it worked!
i got TWRP to boot on recovery2 and installed SUPERSU
Thanks man!
Root Checker info on my P9
I installed root checker today and it reported that root access was ok, but it also reported the following stats:
Huawei VIE-L29 root statistics
ranked by ease of installation
Summary:
Available Root Versions: 2
Root Available: Yes
Latest Android Version: 7.
HUAWEI Ease of Root Install Rank: 15
additionally, on ease of rooting the app reported:
Rank: 6620 (out of 8066)
Root Install Difficulty: Hard
Well, it wasn't that hard thanks to the help i got in this thread... just saying
Hi I have rooted my phone huawei p9 and i have the twrp recovery and tried installing different rom in my phone but while installing twrp is rebooting and the new rom is not getting installed in my phone. can you please advise?
What ROM Version?
Huawei P9 is very picky on which ROMS it can run. What ROM specifically did you try to install? please include the source where it was downloaded from, size, version, date etc.
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Thanks, this saved my life. I had problems with
"FAILED (remote: Token Verify Failed, Reboot the device)"
After i flashed the last rom i used(Pixel Experince) with this dm-verity disable it workes now !!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
tawa2525 said:
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Click to expand...
Click to collapse
I can't get TWRP to come up. I flash the image and then try to boot to recovery, but there is no recovery. When you try to get fastboot.
ain_gt said:
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
Click to expand...
Click to collapse
I tried that and got fastboot instead of TWRP
funmunke said:
I tried that and got fastboot instead of TWRP
Click to expand...
Click to collapse
So...I figured it out. You are going to laugh at me.
That version of TWRP was garbage. I switched to another version and now I'm up and running.
Thanks to everyone who responded!
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??