HELLO please i need help i almost tried everything and search all the possible solutions and tried but still my p9 EVA-L19 is bricked.
During fastboot mode it says bootloader is unlocked and FRP locked.
During my Huawei erecovery mode the only option shows is reboot, shutdown and Download latest version and recovery- which ive tried clicking but failedd even if its connected to wifi.
Cant flash twrp because it fails. (ive tried the nougat and mm version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already downloaded almost all the firmware in my p9 even the compatible or not, including nougat and marshmallow firmwares that I search through the internet and extract the update.app file, ive tried every boot and recovery file on every update.app that ive extracted but still results to "FAILED (remote: Command not allowed)".
I tried the DLOAD process but still stops in 5%. I downloaded the right firmware, region according to my phone, i even downloaded the nougat, i downloaded the firmware on huawei site and put all the file (one at a time) in my sd card but still stops at 5% and fails.
I've tried this method firmware finder it failed because theres no DNS option in my router and contacted my ISP and said they dont enncourage changing dns but i still tinkered my router and change DNS servers on "DHCP" tab. My device connected but still stops at 5% and fails to download the firmware.
https://l.facebook.com/l.php?u=http...GekPE75dbxDE3zm8B9SKwKa7CYqVUYOra4BD8LJ-J011g
This problem all started when i wanted to rollback to marshmallow rom and failed to flash because of my stupidity. After that my phone bricked tried to install custom rom but it says:
failed to mount /product (invalid argument)
failed to mount /vendor (invalid argument)
so again with my stupidity i tinkered my TWRP and change some file system partition i dont know what im doing i panicked then now i cant boot to twrp anymore.
My device only boots to Huawei erecovery and fastboot mode. PLEASE i need help.
I had many bricked devices before but this is the only one i cant solve. Appreciate all your suggestions. thanks!
Obviously, you cannot flash TWRP because FRP is locked (both Bootloader and FRP must be unlocked). So you tried flashing TWRP both for MM and N - again, one must know that flashing wrong TWRP may (further) brick the phone.
Similarly, you tried DLOADing various builds from Internet (only some build types can be installed by DLOAD and only in some order/combinations, otherwise it may again lead to bricks).
There are more methods (more powerful, specially for unbricking), not only the old and depraceted DLOAD (or FF DNS/proxy), but they require both Bootloader and FRP unlocked...
Sorry to say but good that after all your phone still boots to the Bootloader (and without, there will be no hope).
Friendly advice: invest 15 Euros or so to their credits and try DC Phoenix - AFAIK this is the only tool that knows a back-door through the locked FRP:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Their HowTo is not very informative and people complain thar their online help is not much better either, but if you search XDA you will find posts/threads praising their tools, unbricking them phones where nothing else worked anymore (cannot help you with DC Phoenix, TG never needed to use it)
Just reading this, and i can confirm, that , i think, dc unlocker helped me. As i remember it was quite easy, compared to everything i tried before.
Related
Hello, my Mate S is now realy bricked. My english is not good, please dont forget it please.
Ok, my Phone is a Vodafone Phone and i go today back from Marshmallow to OFW from Vodafone with rollback. It working nice but Fingerprint dont work. Now i have update my Phone with OTA to 120 (i think) and i will install TWRP but it dont boot anymore in recovery mode only systrem. So i flash origin recovery back to phone and now it dont boot anymore. Now i will go to Recovery but Phone only boot to eRecovery (i never have see that) and it tell me that it will download recovery from wifi. Now i make a wifi conection but it cancle with error.
Whats up now !?
I have the old FW back (110+114+145) but it is bricked and dont boot only fastboot, no system, no recovery anymore.
Who can give me a the OTA update from Vodafone 120 ?!
What can i do that recovery work again !?
Realy Thanks for help
P,S. I think the Problem now is, that i have flash the recovery.img for the old 110 FW, but i have forgotten that i have the boot.img from OTA (120 i think) please send me the boot and recovery from OS 120 (or the last Vodafone OTA) Thanks
download L09C432B145 from http://forum.xda-developers.com/mate-s/general/index-collection-mate-s-firmware-t3349258 and extract update.app with huawei update exctrator. Now boot your phone in fastboot mode and flash System.img, boot.img, cust.img and recovery.img. reboot your phone and do a factory reset (just in case). It should work again
Thanks for Help, i have test all that but it dont work. I have test it with OS 145, 114, 110. I think that i must have a working Fastboot that work with boot + recovery another way i cant see enymore.
I realy dont understand what is wrong with TWRP, before it work with all OS from Mate S only from F... Vodafone. I go back because Fingerprint dont register anymore.
Ok, i have make Photos from eRecovery, there i can connect to ethernet but it break up with error message:
Sorry for bad quality but i only have a iPad here for Photos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry to tell you,
I had the same problem, nothing worked, only erecovery and bootloader worked but fastboot commands did nothing, flashed cust, recovery, system...images from different roms.... nothing worked.
Problem was, motherboard f...ked up...
Sollution new motherboard, i senden back to huawei and they changed it and send it back, everything quick and good...
But lost every data on the phone....
So you can only send back to HUAWEI... sorry...
can you acsess twrp ???
sorry, that i answer so late.
For all they have the same problem. Look when you have buy your phone, when it is not 6 mounth you can change it with huawei they have a service and do that in 24 hours. When it have a Provider branding, you dont have a chance to debrick it (missing rights to flash via adb what you need) .
Huawei will change your phone in a banding free phone and you dont will have problems again.
Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.
infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha
Hi, I stupidly updated my phone (which I got yesterday) to nougat via Firmware Finder. Now I'm stuck on something called NRD90M test-keys.
I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I boot the phone I get that, and when I press the power button it boots, but boots into the Android version 7 Emui version 5 NRD90M test-keys. The Bluetooth doesnn't work, the camera app is gone, clock app is gone.
I've tried this
https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091
I've tried doing the rollback with HUAWEI_P9_Rollback_Package_EVA-L09_EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0_C900B300 from the huawei website but it does the update then goes to user reset and it fails every time and then when I boot up it's still Nougat 7.0, Umui 5.0 nrd90m test-keys
It's a Huawei P9 EVA-L09, I've searched high and low for an answer and can't find anything
Follow this thread to solve your problem
https://forum.xda-developers.com/p9/help/huawei-p9-brick-easiest-to-unbrick-t3662350
Rafa Mistry said:
Follow this thread to solve your problem
https://forum.xda-developers.com/p9/help/huawei-p9-brick-easiest-to-unbrick-t3662350
Click to expand...
Click to collapse
Sorry, should've verified. The phone boots after I press the power button on that screen, but it boots into the nrd90m nougat version which hasnt got the camera, clock, bluetooth and other things which I need for the phone :/
bengax said:
Sorry, should've verified. The phone boots after I press the power button on that screen, but it boots into the nrd90m nougat version which hasnt got the camera, clock, bluetooth and other things which I need for the phone :/
Click to expand...
Click to collapse
What is your ANDROID Version?
Rafa Mistry said:
What is your ANDROID Version?
Click to expand...
Click to collapse
https://forum.xda-developers.com/p9/how-to/update-method-problems-to-version-t3660717
Solution here is # tried
Fixed to an extent, I downloaded the full firmware for 6.0 and emui 4.1 and unlocked the bootloader then ran that with the 3 button updater. Currently EVA-LO9C900B168 and I'll leave it at that until I understand more about this phone and all this flashing stuff.
NRD90M Test keys
Hi there!
I got past the issue this way:
By buying credit for DC-Locker or funkyhuawei tools... Do some reading and get familiar with what their tools can do and what tools you feel comfortable with. Opt for a 3 or more days pass incase you need retries.
1. Downloaded the correct UPDATE firmware for your device and opened it in the Phoenix 56 program (can find it somewhere in DC-unlocker).
2. In Phoenix select advanced... deselect all files and select only RECOVERY2 to be flashed.
3. Now go to the folder where you downloaded a suitable custom recovery to. Rename the custom recovery (twrp) to RECOVERY2. Before clicking on update, make sure to copy the renamed twrp recovery that you renamed to RECOVERY2.
4. Paste RECOVERY2 into folder where the Phoenix program temporary extract the update files to... Choose to replace the RECOVERY2 (the temp files appears in the same folder where Phoenix.. exe is)
5. Proceed to click update... (I am not going to explain all the details but some common sense is required) ...If it was successful proceed or try again.
6. Leave the phone plugged in on fastboot mode when done flashing. Do not restart after flashing!
7. The red LOCKED ON FASTBOOT should now be green! This is just Temporary until the phone reboot.
8. Now use the rebranding flash tool from funkyhuawei to rebrand your device to the preferred firmware for your phone... When done and reboot, the build number should be correct and you now should be able to update it via HiSuit or update Centre...
Hi, after the january update my Mi A2 got stucked at Android One logo.
Bootloader is locked (OEM Unlock option NEVER was checked), phone enter in fastboot mode but there's nothing that can i do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried the testpoint method, i followed this steps: en.miui.com/thread-5444263-1-1.html
Phone enter in EDL mode, but at the end of the process in XiaoMiFlash i receive an error: "ACK count don't match"
I don't know why this occours, searched the whole internet but not find a solution.
Also i tried to unlock the bootloader via MiUnlock tool, but i receive this message:
Please help, my phone is bricked after this update, and all i've tried don't work.
Don't know what to do, any suggestion or the steps to solve it? Thanks!
walpaiva said:
Hi, after the january update my Mi A2 got stucked at Android One logo.
Bootloader is locked (OEM Unlock option NEVER was checked), phone enter in fastboot mode but there's nothing that can i do.
I tried the testpoint method, i followed this steps: en.miui.com/thread-5444263-1-1.html
Phone enter in EDL mode, but at the end of the process in XiaoMiFlash i receive an error: "ACK count don't match"
I don't know why this occours, searched the whole internet but not find a solution.
Also i tried to unlock the bootloader via MiUnlock tool, but i receive this message:
Please help, my phone is bricked after this update, and all i've tried don't work.
Don't know what to do, any suggestion or the steps to solve it? Thanks!
Click to expand...
Click to collapse
In worst case scenario u can send it to warranty. They will fix it, but you probably will need to pay shipping fees
walpaiva said:
Hi, after the january update my Mi A2 got stucked at Android One logo.
Bootloader is locked (OEM Unlock option NEVER was checked), phone enter in fastboot mode but there's nothing that can i do.
I tried the testpoint method, i followed this steps: en.miui.com/thread-5444263-1-1.html
Phone enter in EDL mode, but at the end of the process in XiaoMiFlash i receive an error: "ACK count don't match"
I don't know why this occours, searched the whole internet but not find a solution.
Also i tried to unlock the bootloader via MiUnlock tool, but i receive this message:
Please help, my phone is bricked after this update, and all i've tried don't work.
Don't know what to do, any suggestion or the steps to solve it? Thanks!
Click to expand...
Click to collapse
Try keep rebooting the phone until it boots back to Android.
If can't try boot into recovery by pressing volume up and power button at the same time, if you get "no command" error, press power button and you are in. Perform a factory reset.
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!