Hi, i updated my P10 to Oreo, after bricked, and now i can't find the System folder.
I allready installed in fastboot mod, but still nothing. Is there a way to get it back?
Thanks
what? Please one more time and now clearly.
You can still use one of many methods to flash oreo firmware again. The methods are here on XDa described well.
Related
Hi Guys,
I really need help here. I am using Huawei P9 EVA-L19.
I once unlocked bootloader, installed TWRP and rooted my phone. After 1 day I using it, I tried to flash to unofficial emui 5 which is follow the instruction from here; https://forum.xda-developers.com/p9/how-to/huawei-p9-eva-l19-android-7-0-nougat-t3532649
However, after I done flash it. I found out that there's a lot of application I can't access including my camera ( which totally gone from my phone ). I decided to flash back to emui 4.1.
The issue that I'm facing right now is, I can't even access to TWRP. I tried a lot of ways to install TWRP and try to boot. Nothing happen. I've tried to use Dload, I tried using CMD it seems never success.
Now, I really need someone to help me on this issue. I know there's a lot of people who facing the same issue that I'm facing right now. Or someone who already solve this issue please assist me. I'm already give up on this.
Thanks in advance.
Hello guys,
i did a mistake yesterday and accidently hit the update button of the official update dialog from mm to N on my p9. Because you cannot cancel it, it proceeded the whole process...
Now i'm stuck on the new Version and first problem were missing apps like updater, and camera?!
I was looking for the new buildnumber and it says NRD90M test-keys.
Previously i was on root but dont know the buildnumber (some MM), bootloader is unlocked.
I searched a lot on xda but did not find a similar problem with a solution that i would try.
Can anyone help me how to fix that problems? I read about a rollback but didnt find a way to do that. TWRP is loading if that helps in any way.
Goal is to get root to work with magisk maybe and an up-to-date nougat rom (and Camera back since 3rd party isnt that great).
If any other info is needed ill provide that.
Thanks in advance!
I did some research an tried a few more things.
Here's whats not working:
-flashing b136 with dload from paulobrian's thread. fails at 5% mark
-relocking bootloader with srk-tool and fastboot. resulst in: failed remote root type is risk
-flashing several other full versions
i flashed (succesfully) stock recovery following this tip: https://forum.xda-developers.com/showpost.php?p=67754200&postcount=4
system is booting but weird behaviour as described.
I read something about succesful flashing stock only with locked bl and only locking bl with stock recovery but this doesnt work for me.
Any tipps are much appreciated.
I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time
SonicAndreev said:
I have been using my Huawei Honor 5C for 6 month. Week ago, I decided to try updating my firmware from android 6 to 7. I have bricked my phone at all, as FRP was locked. I bought a DC Phoenix license and flashed some files, which I recieved from DC Support.
Everything was OK, but two days ago I tried to root my phone and install TWRP. When I try to do that, it gives me:
Fastboot: FAILED (remote: image verification error)
Contacting with DC Support doesnt give any help, as they dont know why it happens.
Did smb has the same problem as mine? If so, how did you solve it? I dont wanna buy DC license for a second time
Click to expand...
Click to collapse
Try installing the stock rom clean. It might help.
Shubho20 said:
Try installing the stock rom clean. It might help.
Click to expand...
Click to collapse
I have already tried. It doesnt help.
SonicAndreev said:
I have already tried. It doesnt help.
Click to expand...
Click to collapse
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.
ConradP said:
You probably messed up like me.
I think you should download full update of the 6.0 firmware and then ^take out^ boot.img recovery.img. And system.img. Then install it through adb. 1.boot 2.recovery 3.system. It should help.
Someone told me about it in Nem-L21 Nougat tread.
I left my in Huawei seewis centre. They exchanged motherboard - it Was easiet way for them.
Click to expand...
Click to collapse
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...
SonicAndreev said:
I have already tried it. I downloaded NEM-L51C432B130 FullOTA, unzipped it using Huawei Extractor app and flashed boot, cust, system, recovery and recovery2. After that, i rebooted my phone and had a critical error screen, which said me that I need to flash system partition (but I have flashed it). I also tried flashing rollback first, but it gives the same error. Finally, I fully flashed beta rom of android 7 and the phone has booted. The problem is that one archive of Android 7 rom has extra "data" folder, which contains system apps such as Bluetooth, Finger Scanner, Update Utility, EMUI Explorer and some others. Without them I cant use my phone, cause I often use these options. This archive with "data" folder needs to be flashed through TWRP, but I cant install TWRP on my phone (see thread question). I dont know what to do...
Click to expand...
Click to collapse
This phone is harder to master with custom roms then my previous LG G2.
ConradP said:
This phone is harder to master with custom roms then my previous LG G2.
Click to expand...
Click to collapse
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.
SonicAndreev said:
I know. I has Nexus 7 and it has the easiest way for flashing firmware. I dont understand why Google (or Huawei for EMUI) didnt preinstalled a small extended board with stock ROM for rescue purpose. So that, if somebody bricked his phone, he could be able to fastly rescue his phone and make it work. The worst problem of fastboot is that fastboot partition can be damaged, while you flash something. Anyway, android devs are better made FRP lock, which is useless and can be easily removed... Or they are better made some new androids every 3-6 month, wow, thats cool (no)
This problem had no solution yet. There is only one way, how I could make my phone fully-workable - wait for a stable ROM of Android 7 abd flash it through fastboot.
Click to expand...
Click to collapse
Yes, I totally agree.
And I am waiting for the Nougat release - after the beta I am missing some options - like dualscreen.
hey bro just unlock bootloader....(because this error for only bootloader lovked)
sahildutt said:
hey bro just unlock bootloader....(because this error for only bootloader lovked)
Click to expand...
Click to collapse
What? Explain your problem more.
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
I'm using a rooted huawei p9 Eva l19 on b390 stock firmware. Unfortunately she is sick and her Bluetooth is not working. I read on the net that clearing the cache of the Bluetooth app would help but I can't find the app in settings.
Any suggestions
Pls reply
Hmm, i am on the same boat.
Will watch your thread too, hope someone will have a solution.
rwa66 said:
Hmm, i am on the same boat.
Will watch your thread too, hope someone will have a solution.
Click to expand...
Click to collapse
Well seems like no one is wanting to help :crying:
Rollback to Marshmallow & Again update to Nougat
Great, thanks Rafa Mistry!
I tried to go back to B182, that's Marshallow, failed at 5%.
But I searched a bit and i think we can use the procedure suggested here, Abhisht009.
I don't have the time to try right now, but i will do it tomorrow night, let's hope we will have good working phones soon again.
If you need back to Android use rom from Huawei website and download Android 6 than use method 3 buttons
rwa66 said:
Great, thanks Rafa Mistry!
I tried to go back to B182, that's Marshallow, failed at 5%.
But I searched a bit and i think we can use the procedure suggested here, Abhisht009.
I don't have the time to try right now, but i will do it tomorrow night, let's hope we will have good working phones soon again.
Click to expand...
Click to collapse
I dont have time right now to do this but I know how to
You must first download the rollback package for your p9 model from the huawei website
Then download an older version of marshmallow (not B182, use an older one)
First install the stock recovery
Flash the doll back package using dload
Boot up
Flash the marshmallow firmware
Done
You should probably remove the fingerprints before
Tell me if it works
After trying loads of older MM firmwares, which all gave me compatibility errors, i ended up flashing mOOnlight ROM.
Bluetooth is working, all is good now.