Potentially Bricked Device, Help please! - Huawei P9 Questions & Answers

Hello, I'm really hoping someone can offer me some assistance with this issue.
I currently have a rooted P9 but had some issues earlier which resulted in the /data partition being unable to be mounted. I have tried everything I have read online to attempt to fix this. I cannot format or advanced wipe in TWRP, I am unable to wipe through bootloader and I have no idea what to do now. I am still able to boot to system but cannot flash stock rom or format partitions. The data partition is in the f2fs format which I believe means that it is encrypted. I have installed this recovery and am still having the same issues, I can't think of anything else I can do so I am open to any suggestions or support. I have the latest TWRP installed.
When trying to flash stock recovery I get
"target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 0.744s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s"
However when I managed to install stock earlier it said that there was an error getting the package info failed. I don't know what has changed but it now won't allow me to flash recovery whereas it would before.
Thanks!

Related

!!!help!! Please

just wondering if anyone can help me out here, i was trying to flash the cyanogen 1.4 recovery image to my g1 1.6 phone using fastboot so i erased my stock recovery image, only to get the message "remote: signature verify fail" so im now stuck with no recovery image and dont know how to get it back, can anyone help me out please?
update
i get this error now... someone plz help
Code:
C:\android-sdk-windows-1.6_r1\tools>fastboot flash recovery /sdcard/cm-recovery-
1.4.img
error: cannot load '/sdcard/cm-recovery-1.4.img'
instead of having the recovery image on your sd card, put it in the directory you're running fastboot from and just enter:
fastboot flash recovery cm-recovery-1.4.img
i just did it and it gets stuck here
ps once it sends it to the phone the phone disconnects from my comp (can no longer see it under my computer)
Code:
C:\android-sdk-windows-1.6_r1\tools>fastboot flash recovery cm-recovery-1.4.img
< waiting for device >
sending 'recovery' (4002 KB)... OKAY
writing 'recovery'...
Have you tried putting the recovery image into the root of the SD and running a terminal command:
Su(enter)
flash_image recovery /sdcard/cm-recovery-1.4.img(enter)
I usually rename the .img to like cm14.img(makes it easier to type)
yeah i have but it still says it cat find the file
So you have no recovery IMG ?
yeah
Was that a "Yeah i dont" or "Yeah i do" ?
yeah i do now but i cant flash the cm 1.4 it wont let me i lost root too so i tried to root with the 1click method but its pathed so im gonna just downgrade now and re root that way
Well once you root with the one click way its gonna get you Amon-RA's recovery img witch is better then CM's recovery IMG.
ok so i tried to unroot the phone but when i try to apply the stock spl it says this
Code:
C:\android-sdk-windows-1.6_r1\tools>fastboot flash update spl.zip
sending 'update' (205 KB)... OKAY
writing 'update'... FAILED (remote: partition does not exist!)
help im loosing hope
UPDATE
ok soo i have great success lol
Code:
C:\android-sdk-windows-1.6_r1\tools>fastboot flash recovery cm-recovery-1.4.img
sending 'recovery' (4002 KB)... OKAY
writing 'recovery'... OKAY
THANK YOU ALL! for your great help!! seriously i hope this thread helps someone else sometime

[Q] TWRP flash via Fastboot failing

I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.

Problems with VZW Developer Edition Rooting

Please bare with me, I am probably a "C" student in the knowledge of this stuff. I've successfully rooted and rom'd the Galaxy Nexus many times but I'm having trouble with the new Moto X.
I unlocked without issue
Tried to follow the TWRP instructions (which clearly assume some existing knowledge). Not quiet sure what happens with Mfastboot but I got that from a download.
The TWRP flash failed. Can't remember the exact message but I think it was a binary size error.
Now the phone will not boot at all, it just goes back to the bootloader.
I am currently running the repair from the Motorola Device Manager and then I'll have to start again.
So what might be wrong ?
Bricked for a second time.
Here is the error
C:\MOTOX>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (7 KB)...
OKAY [ 0.238s]
writing 'recovery'...
Invalid boot image
FAILED (remote failure)
finished. total time: 0.518s
homemadehitshow said:
Bricked for a second time.
Here is the error
C:\MOTOX>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (7 KB)...
OKAY [ 0.238s]
writing 'recovery'...
Invalid boot image
FAILED (remote failure)
finished. total time: 0.518s
Click to expand...
Click to collapse
The img file should not be 7 KB. It's around 9 MB. Make sure that you have left clicked the link for the file from the other thread and go to the goo.im page. Then download from there. If you try to right-click the link and "save as", you'll get that 7 KB file.
thesourgin said:
The img file should not be 7 KB. It's around 9 MB. Make sure that you have left clicked the link for the file from the other thread and go to the goo.im page. Then download from there. If you try to right-click the link and "save as", you'll get that 7 KB file.
Click to expand...
Click to collapse
This.
Make sure your bootloader is unlocked and that you have the 4.4 compatible twrp file downloaded (check md5). Sounds like you've got the bootloader part done but do not have the recovery file rather you've saved the link.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2534850
There he has the file you'll need. It should be about 9.62 MB in size. Be sure to compare the MD5 with the one on goo.im: cb7808078a6746dc87e6eaeb4f145dc0
Yes, file size was wrong and it worked after I redownloaded it.
Thanks.

Mate S no OS Installed

hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
can you reach twrp?
if so, then reboot into bootloader through twrp..then in bootloader you can flash the stock boot.img and recovery.img of the b145..
after that you should be able to reboot normal..
Gesendet von meinem Mate S CRR-L09 B321
Thanks for your support..yes i can reach in twrp and in the bootloader..but My answer is :must i do flash of stock boot.img and recovery.img through fastboot e rescuemode?if so i made it yet and it doesnt work because frp is locked and i have return error with adb fasttool!!
SuperSU 2.42
frisko76 said:
hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
Click to expand...
Click to collapse
Try flashing SuperSU 2.42 from TWRP and see if you´re able to boot. When I installed versions newer than 2.45 I ended up in bootloop.
Edit: Sorry, I mean 2.62 is the right one and over 2.65 will end up in loop. Anyway, try 2.62.
ok..i try this way to install supesu 2.62..this screenshot is result when i reboot into bootloader trought twrp..i not understand because i have this error :command not allowed
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash boot bo
ot.img
target reported max download size of 471859200 bytes
sending 'boot' (23552 KB)...
OKAY [ 0.632s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash recover
y recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31372 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.865s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>
excuse me but i not post an image!
i have tried to install supersu 2.62 but return message error no os install and the device not have supersu do you want to install??i already installed supersu and i have this message after?..i tried to install supersu 2.75 and i have only the message no os installed..but the phone are same in bootloop....can i search an tool for erase frp tool?for Samsung exist and for sony experia..for huawei?
hello,i verified only method for resume device is use dc unlocker for price 15credit... ...but i have an other idea..i have an other huawei mate s,original stock recovery..can i try to unlock bootloader and developer option , install twrp and try backup for use in the other device ???..is same firmware b145 eu...it could be right way for resume my device?thanks

(((SOLVED)))bricked phone failed <remote: sparse flash write failure>

Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
xtcislove said:
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
Click to expand...
Click to collapse
I don't think this would work since all of this happened because I tried to overwrite both recovery and recovery2 with twrp which ended up soft bricking my phone. So basically the only thing that would flash is the recovery, recovery2 and boot images.
felroric said:
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Click to expand...
Click to collapse
Yes, I did.
You have to flash the same version of Android you wiped before.
It happened with me when I wiped N system then I tried to install MM, the solution was just flash N system.
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
You get error every time cause your frp is lock
Rafa Mistry said:
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
You get error every time cause your frp is lock
Click to expand...
Click to collapse
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
IDontKnowAnythingAtAll said:
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
Click to expand...
Click to collapse
Your twrp is installED?
Rafa Mistry said:
Your twrp is installED?
Click to expand...
Click to collapse
Well, My phone is working now. But yeah I had twrp
IDontKnowAnythingAtAll said:
Well, My phone is working now. But yeah I had twrp
Click to expand...
Click to collapse
I have the same problem. How did you fix it?

Categories

Resources