Related
I updated to beta Nougat using a non-official-beta method and am somehow stuck with NRD90M test keys as my build number. The rom works ok for the most part, the only thing which doesn't seem to work properly is Themes.
Would now like to know what the appropriate process is to go to the new and official stock Nougat for EVA-L19. Thanks community!
So was I and I posted about it here and got the right advice to roll back:
forum.xda-developers.com/p9/help/nougat-update-borked-p9-2-imeis-t3534530#post70475746
thank you zemblance! so it would appear that i would have to rollback to stock then only update to official nougat using the built-in updater huh?
Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13
z4d02 said:
Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13
Click to expand...
Click to collapse
not sure which TWRP i used but its fixed now. i did the rollback to lollipop. now on B190 but now Themes is being wonky and I have no magazine unlock. :/
Flash 136 again, there should be two folders hw and dt that need to be in the dload folder too.
If they aren't there you could try flashing the l09 136 first then the l19 one straight after.
Sent from my EVA-L09 using Tapatalk
Ya tone obnaveli eto rom no skajite pojalusta kak vernutsya moy zovoskoy emui 4.1 honor 6x
So I managed to get myself into this bind as well back in January, but I just didn't have the stamina to fight it and I've been running that crap ever since. Now I thought it time to take care of it.
This is the scenario. I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version.
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?
Farmfield said:
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?
Click to expand...
Click to collapse
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.
chris5s said:
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.
Click to expand...
Click to collapse
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?
Farmfield said:
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?
Click to expand...
Click to collapse
Ok, so get the 2 files for the ROM you want, and flash update zip then hw data update zip next.
It worked in either TWRP or dload method for me. Of course, for dload method you need to unzip and flash each zip in turn, or TWRP can flash one after the other. Flashing will relock your bootloader...
Well, if you note my post count and alike, I'm not really a newbie here, I got 10 years experience messing about with custom Android ROM's and about the same experience of general Linux experience on top of that, so when I don't wanna do this without some trustworthy information on the workflow, etc, you should get there's good reason. So posting replies like -Oh, just flash something, it'll work out!, that looks a lot to me you just having been really lucky not getting into the situation I did.
So I will repost the question I posed and hopefully someone with that know how will reply.
I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version. What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
Just to clarify....
I had an unlocked EVA-L09 with TWRP, running build NRD90M test-keys, and I wanted to fix it....
So, I downloaded update.zip and update_data_full_hw_eu.zip and flashed them one after the other using dload method. It worked. That was my workflow.
Just trying to help out, don't get shirty about it....or you can wait for someone who's been on the forum longer than me, or who has a higher post count than me. Btw, I've received help before from folks with very low post count and I know it's no indication or predictor of noob-ness.
Peace out...
*I* did the exact same thing and then spent the following 30 hours trying to get it to even boot.
And I really didn't want to be rude, but if I got that kinda post number, I'm not likely to ask for help with something like this unless I really needed it. As I said, I have a lot of experience of this stuff and I still messed up immensely trying this the first time, so I'm not even going to try before I have someone who really knows what *NOT* to do give me some hints on how to avoid getting into the same spot - because I'm not doing another 30h trying to save this phone if I mess up again, I'll just smash it and buy something else, like a used Nokia 3310, because it's just not worth the stress.
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
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:
Hi everyone! I decided to go back to stock from LineageOS 14.1, because 3D and AnTuTu Benchmark didn't work, just showing black screen and nothing happened. In any game did the same. So I decided to restore a TWRP backup, and I did that. It restored, but when i tried to boot up, it just stayed on the Honor logo. I tried to put the UPDATE.APP onto my SD-CARD and try to reinstall the OS, but I noticed something in TWRP, /data didn't mount for some dumb reason. I didn't think that was something bad so I ignored it. After installing the UPDATE.APP, it still does the same, stuck on Honor logo.
I know I f*cked it up, but now I want to get it fixed. Please help me !
Downgrading to EMUI 4.1 will fix it.
erayrafet said:
Downgrading to EMUI 4.1 will fix it.
Click to expand...
Click to collapse
Tried downgrading to EMUI 4.1, and downgraded well, until it remained on the Honor logo screen. I tried with different versions of NEM-L21C432 stock roms for my phone, and only the ones with 13x worked to upgrade to, but the Nougat ones didn't. And it also blocked my bootloader again, because of the downgrade to EMUI 4.1 by holding both volume buttons and the power button.
If you downgrade, first u have to use downgrade package and then install rom version NEM-L21C432B132 and then use updater in settings to upgrade to nougat, dload method doesn't work with emui 5 roms.
co5oos said:
If you downgrade, first u have to use downgrade package and then install rom version NEM-L21C432B132 and then use updater in settings to upgrade to nougat, dload method doesn't work with emui 5 roms.
Click to expand...
Click to collapse
The thing is I came back from a custom rom, more exactly the Lineage 14.1 developed by Meticulus, but it was EMUI 4.x based, so... yeah. It shows that the EMUI version is installed is NEM-L21C432B130. I tried upgrading through update.app and no luck. However, the bootloader locked. So, I send HuaweiMobileUK a tweet to give me the bootloader code for my phone. And sure enough, 2 days later, I have the bootloader code and unlocked the phone. I am going to attempt to install TWRP and then wipe everything except the SDCard and flash the update.zip with TWRP. I will try that and let you guys know if it worked.
Bogdan008 said:
The thing is I came back from a custom rom, more exactly the Lineage 14.1 developed by Meticulus, but it was EMUI 4.x based, so... yeah. It shows that the EMUI version is installed is NEM-L21C432B130. I tried upgrading through update.app and no luck. However, the bootloader locked. So, I send HuaweiMobileUK a tweet to give me the bootloader code for my phone. And sure enough, 2 days later, I have the bootloader code and unlocked the phone. I am going to attempt to install TWRP and then wipe everything except the SDCard and flash the update.zip with TWRP. I will try that and let you guys know if it worked.
Click to expand...
Click to collapse
Ok, so I tried wiping everything except the MicroSD Card and installing the update.zip FULL-OTA MF NEM-L21C432B132 and it worked. The phone still has the bootloader unlocked and now it works perfectly. So this is a good solution that worked for me ! Thank you guys for help anyways!