P9 Plus blocked - Huawei P9 Plus Questions & Answers

Hello, I need help, I'm in a big bind.
I have a P9 Plus that I got get root after installing the TWRP 3.1.1.1
Then I tried to change the cust (the one that came with the phone was Vodafone).
I downloaded the file hw_eu.zip from this page: h t t p s: // w w w . tuttoandroid.net /forum/threads/ guida-huawei-p9-plus-cambiare-paese-vendor-oeminfo-cust-upgrade-firmware-6-0[/url] -e-7-0-with-dload.54825 /
I installed it through TWRP but now it has formatted the DATA partition and it does not start, it is in a continuous loop in EMUI eRecovery.
Also, fastboot does not work because I'm afraid that USB debugging is not activated, I get this error when trying to reload the TWRP: "FAILED (remote: command not allowed)"
Does anyone know what solution has to be able to start the phone?
Thank you very much in advance!!

Related

Huawei P10 Lite, TWRP Error 9, pls HALP

Hello everyone,
My phone is in what it seems to be erecovery loop, I tried flashing images via fastboot extracted from update.app file, didnt work at all.My phone is unlocked, I flashed twrp again and downloaded latest stockrom version for my country(asked a friend about it since he has the same phone), I put those 3 files on my usb and connected it to my phone.Opened it in twrp, when i try to flash update.zip i get Error 9.I tried pretty much anyting i could find on this forum and other sources from google, nothing rly seems to work and there isnt anything at all for error 9.Do u guys by any chanse know what is the problem here?
device: Huawei P10 Lite WAS-LX1C432B194 (latest version for my country, Serbia, Eu)
phone unlocked, twrp installed, can do fastboot commands
This is what i get when trying to flash that update.zip
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Installing zip file '/usbotg/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: Success
script succeeded:resut was []
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from
zip failed
[COLOR="red"]Updater process ended with ERROR: 9
Error installing zip file '/usbotg/update.zip'[/COLOR]
Updating partition details...
...done
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
LwannaCM said:
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
Click to expand...
Click to collapse
I already firgued it out, but tnx for the response.
I bought sd card(didnt have one), did dload method, since normal one approach didnt work i used force update approach(dload moved to sd card, power off, hold vol+ + vol- + power button and it installed) also i needed to flash stock recovery beforehand(so it removes twrp, used fastboot to do it, phone was unlocked, power off connect to PC via usb cable and hold down vol- right away, then flash it through fastboot), it cant do force update with twrp still installed.Once it was done i normally booted to stock rom, phone was no longer unlocked, now i unlocked it flashed twrp and rooted it, everything works just fine.Hope it helps some1 with the same problem.
source: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 , there is guide thing for both normal and force update
Thank for the help. It gives me a clue but I am still struggling as the force update approach get stuck at 5%. Thanks anyway.

[SOLVED] Bricked P9 EVA-09C432

Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
bomba697 said:
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
Click to expand...
Click to collapse
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP installations must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start, which steps did you perform and by which tools
Btw, rooting N by SuperSU or O by Magisk is pretty straightforward, but is important that proper, corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
zgfg said:
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP builds must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start which steps did you perform and by which tools
Btw, rooting N by SuperSU or M by Magisk is pretty straightforward, but it is important that proper corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
Click to expand...
Click to collapse
I'm sorry for the poor description but I was in panic.
Starting from EVA-L09C432B3xx, don't remember the exact version, N 5.0.1
TWRP 3.1.0.-1
SuperSU, https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258. I had big trouble trying to root because every time the phone rebooted before finishing the procedure.
I didn't use any tool at all for unlocking bootloader, flash recovery and root. Just adb and fastboot in cmd + TWRP.
BTW, I recovered the phone! Used DC-Phoenix to reset the phone from fastboot and then made a downgrade to b182.
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
zgfg said:
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
Click to expand...
Click to collapse
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
bomba697 said:
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
Click to expand...
Click to collapse
If you recovered and if you are on b182 now, you will hopefully receive OTA upgrades tp go back to N
Btw, working procedure for rooting N was described in thread
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Again, if TWRP was not able to mount Data, was it really proper TWRP from XDA Huawei Nougat threads (adapred to support Huawei N and its encryption), like
https://forum.xda-developers.com/p9/development/twrp-t3565703
Some other TWRP 3.1.x.x, even declared for Huawei, maybe good for EMUI 4 / MM but not for EMUI 5 / N
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
kazshizka said:
EDIT: ...DC-Phoenix. Do you have a link and how to use...
Click to expand...
Click to collapse
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
kazshizka said:
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
Click to expand...
Click to collapse
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
zgfg said:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
bomba697 said:
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
Click to expand...
Click to collapse
Will check out both methods. I'll try it through TWRP first since it should be easier to use an open bootloader rather than a locked one.
@bomba697 will reinstalling stock recovery fix my deleted system issue? coz I'm not sure if I flashed the custom ROM properly anymore
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
kazshizka said:
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
Click to expand...
Click to collapse
Happy that you found the solution! I tried directly flashing the rom but I wasn't able beacuse of the \data mount error.

The problem with installing the firmware on the Asus me 176cx 8gb KitKat 4.4.2

Help revive my device.
After updating the tablet from the playmarket of the Youtube application, the tablet freezes, after a reboot, it hangs on the Asus logo and a spinning circle. I couldn’t enter the droidboot from the buttons and, following the instructions from the 4pda forum, after downloading the service firmware, unpacked it to drive C into the folder, then went to the firmware folder by pressing shift + the right mouse button opened the command window and launched the
droidboot with the fastboot boot droidboot.img
fastboot continue
commands booted into the droidboot and in the folder with the firmware clicked on the update_image file, the firmware process started which took a very long time about 7 hours, at the end the tablet rebooted but only until the first screen saver. I waited a long time, but it did not boot. I turned it off. After that, by pressing a combination of buttons, I was able to enter the droidboot, the serial number of the tablet was missing, through a dead robot I was able to enter the recovery.
Then, according to another instruction from 4pda, through a temporary twrp, I tried to install the Ul-KO13-WW-3.2.23.182-user firmware, the installation process started, but it did not install, but the serial number returned and the tablet again hung on the Asus logo and a spinning circle.
I checked the
fastboot oem start_partitioning
fastboot flash /tmp/patrition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
commands after each command was OK. So the flash memory of the tablet is working.
After I checked the root, the rights remained. USB debugging in the developer menu was turned on even when the tablet was working. Then I decided to try installing the service firmware 201 again, as I wrote above, and again unsuccessfully, the serial number flashed again. . And again, through a temporary twrp, I began to install 182 firmware.
And the serial number failed, it was not restored, but the recovery now showed that it costs 182 firmware. After that, when checking, I found out that no root su. I got a complete crash. I tried again to install 201 firmware and now it costs WW 3.2.23.201 in recovery.
On the advice of a person from the 4pda forum, I tried to restore images of 201 firmware boot.img fastboot.img recovery.img via twrp v2.8.7.0 from the 4pda forum, but again unsuccessfully. I showed the person who helped me install the firmware images 201 that twrp gave me an installation error, it read:
Updating partition details ...
E: Unable to mount '/ factory'
E: Unable to mount '/ config'
E: Unable to mount '/ data'.
The person who helped me said that there was no markup table, or rather, the system section was written, but could not find the other sections, since he wrote this script for Android 5. And on KitKat version 4.4, he did not test this script. Now I'm desperate, I really need a tablet in working condition. Because I am very poor, and I do not have money to buy another tablet, I have been sick for 5 years. I live on disability benefits, they pay me $ 50 a month and I can’t buy another one. I beg everyone to help with tips and instructions on how to restore tablet firmware. I need a worker. I need your help.
Even when connecting to a laptop on a Windows 7 tablet in twrp 2.8.7.0 mode, the tablet is detected as K013, but it does not see the internal drive and only shows a microSD card, I suggest that this is because the firmware is installed incorrectly and there are no firmware sections? ? If Who knows, you can install any custom firmware that fits on my tablet.
If someone can write me instructions for restoring the firmware. If anyone has encountered a similar problem, give information and instructions for restoring partitions with links from where to download what and step-by-step instructions for restoring.
Sorry text wrote through translator. I hope the problem is described clearly and someone can help me with the firmware.
I thank everyone in advance who will respond and help restore the firmware.
P.S. I decided to try to flash through Intel Flash Tool Lite, I launched service 201 firmware, reached the 57% band and issued FAILED. I turned off the tablet, I decided to try running TWRP, running the script, and now there are only two errors:
E: Unabled to mount / and
E: Unabled to mount / config, and the amount of internal memory Internal Storage (3916MB) !!! And before that, it was zero and in the device k013 on the laptop it shows the storage along with the memory card. Here's an interesting process

i tried to install oxygen os and not i am stuck with twrp only

i followed all the steps listed in on oxygen os thread but now i am stuck with twrp and can't install any os
so i tried to install my old os back but twrp install section i am not able to acess to .ozip file and also if i try to install anything or even clear cache it shows
E: Unhandled flags: 'wrappedkey'
E : Unable to decrypt FBE device
when i first installed twrp it asked me my screen password and i put the right password in but still its showing unable to decrypt FBE device
help me!:crying::crying:
Did you try to format data (the one where you need to type yes)? I once had the situation where I couldn't decrypt and couldn't format and reinstalling twrp solved that for me.
yes i also did that still nothing
now only thing left is unable to decrypt fbe device
Try putting your problem in the rom thread the dev may help you better
thanks its solved now just need to remove everything with the fastboot command and then reinstalling everthing again from twrp to os

Question Stuck in Recovery (resolved)

Dear guys,
I'm in a situation where I don't know what's best to do, honestly I was left with android 11 where everything was much simpler.
my xiaomi started from OEM miui 13 on which I installed twrp 3.7 with the " Onekey inject TWRP " method, I understood that the method was wrong with android 12 but the phone worked (in recovery mode it did not read the touch).
I loaded the same twrp from fastboot mode, I do a backup of everything (copied to the computer), and trying to install miui.eu, but the phone gave me the following "error "ERROR: 1 / can not mount system".
I tried with the twrp by skkk, launched from fastboot mode, I started the dirty installation of the miui.eu and when finish to install I pressed "Install Recovery Ramdisk".
I restart the phone but after two restarts it returns to recovery, i thought the problem was the dirty installation, so i went to "format data".
From this moment the phone restarts only in recovery, the phone memory is encrypted and cannot find any content (the phone has no password set), connecting it to the computer I cannot copy any content but it is read from fastboot mode.
The errors that appear on the phone are "Failed to mount '/system_ext' '/product' '/vendor' '/odm' (Invalid argument)"
How should you continue? I have no problem to losing any data.
do you recommend to flash a fastboot rom with Miflash?
Thanks a lot

Categories

Resources