Database Users

HELP! Stuck on Setup Wizard P9 Lite (VNS-L31)

hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!

khajiit said:
hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!
Click to expand...
Click to collapse
did you do factory reset? I had some weird stuff going on after recovery, so I booted back to factory reset (vol + and power), after that it worked OK.
Once you requested the bootloader unlock key, your warranty might be void from that point (depends on country). The bootloader gets locked after flashing official firmware via eRecovery though.

yes i did a factory reset, still can't proceed after wi-fi+ configuration.
is there anything else i can do?

I have one question: is it possible with
-frp locked
and
-phone locked
to downgrade via eRecovery? (to b130 or something..)

I have the exact same problem.
I bought it 3 days ago, and suddenly yesterday downloaded Apps (from the Play Store) stopped working. So someone told me to hard reset it. I got into EMUI and did it. Then I rebooted it and now it stuck there. Can't complete the setup wizard.

I found no solution to my problem after reading google & xda-forum for 3 days. Tried everything... nothing worked. Sent it back and (luckily) got a new one. Now i'm more careful for sure.

The store I bought it from claimed that they had numerous similar complaints about the 3gb version. Which is the one I have. They told me I should take it back and that they will give me a new 2gb version along with any difference in money. We will see.

Exact same thing with me stuck at setup wizard so had to send it off for warranty and got a brand new phone yesterday
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app

Help please my Huawei P9 cannot proceed afta WiFi setting it is stuck on "Checking info "and Reply saying "Couldn't sign in"

The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work

Maxai94 said:
The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work
Click to expand...
Click to collapse
Hello,
does ist really work? Is it just installing the androidsystemview.apk and the phone works fine again?

huawei p9 lite bricked ...please i need a help
my phone stoped in fastboot...
phone locked
frp lock
i can´t enter on recovery mode and he not pass the huawei icon ...
please i need help
i do not connect phone to pc ....

contact me to solve the problem

I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.

logjam said:
I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.
Click to expand...
Click to collapse
Reflash the rom you were on using the "dload" method

dariomrk said:
Reflash the rom you were on using the "dload" method
Click to expand...
Click to collapse
Sorry, dont have the previous ROM, I boiught it off someone and they probably did the first update. The factory reset should reset to huawei original but i think this is where my problem sits.
HARDWARE VERSION=NEXT_L09_VN2
BOOTLOADER VERSION=NXT-C900B120_FASTBOOT
KERNEL VERSION=NXT-C900BB140_BOOT
AP VERSION=NXT-C900B140_SYSTEM
CP VERSION=21.750.08.00.010(balong)
Parameter Version:
P-00.00.000 G-17.V271.371 E-40.01.000
does anyone have an international rom for this or any version that can work.

The way i was able to factory reset was
1. going to huawei site. "consumerDOThuaweiDOTcomSLASHjmSLASHsupportSLASHdownloadsSLASHindexDOThtm"
change slash to / and dots to .
2. Select options for your phone, mine was NXT-L09. Will show "HUAWEI Mate 8 Firmware(NXT-L09, Android 6.0, EMUI 4.0, C605B100, Latin America, Channel-Others)"
3. Download, extract onto sdcard in dload folder, restart phone using vol up & vol down & power.
4. phone will complete boot restart but will then loop the boot process.
5. Do factory reset again
6. After huawei logo, different options show and you are then ok to proceed to login to your google account and setup refreshed phone.
Now on NXT-L09C900B100 build, if anyone has nougat rom for this, please share.

For future reference, if anyone gets stuck with this on P9 lite, indeed the instructions provided by Huawei point to VNS-L11C432B161, which doesn't include Android webview and therefore initial setup cannot proceed. The solution is to flash B210 on top of B161:
update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v80562/f1/full/update.zip
which allows you to pass setup as the bug has been fixed. No root/unlock/twrp required.

I can't install any ROM and i have no backup (or OS)

Hey! First thing you need to know: i'm stupid af
So yesterday i tried to root my Huawei P9 Lite VNS L31, and everything was doing great: bootloader unlocked and everything.
Because the root didn't seem to work on EMUI, i tried to install another ROM (i'm stupid) with TWRP: so I wipe cache, system and data in order to do it good, i flash the ROM but now when i tried to reboot it didn't boot.
So i figured that i was trying to install a MM Rom on an Nougat (at least it was) device. I then tried another ROM and i didn't work either. After hours of trying to make it work, now it boots on Huawei eRecovery, but i already tried to use it since i made no backup (i'm an idiot), and it seems to fail every time? idk it only show a big red ! mark
Right now i'm still looking for a fix but i would be soooooooooooooooooooo freaking relieved if someone could help me please :crying:
(i'm an idiot)

I DID IT!!!!
So i followed a tutorial made by the website androidmtk (i can't link it it's my first post), and is used the official stock firmware for my phone which you can find on cusumer huawei dot com
DONT FORGET TO BACKUP!!!!!!!!!!!!!!

Recovery bricked after Nougat update?

First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance

You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.

nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.

kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.

nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)

It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!

nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.

Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.

kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.

Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

Killed P9 Lite instead of getting back to live, maybe there is a last chance?

Hello, short Story before. I got a full Hand of non working mobile phones because being full of a hell of viruses.
5pcs. younger ones.
2 Huaweis and 3 Samsungs.
Well so far 4 PCs. are saved.
Getting into the phone wasn´t possible anymore. Data not important so I resettet over the Buttons to original Status. -> Worked fine.
But one Piece which is a Huawei P9 Lite guess it is a single sim? was the button method not possible cause it wanted a Software update and Installation of WLAN failed (EMUI)
Getting into the phone for any informations was also not possible because of all the viruses and not working right ahead anymore.
Well ok -> will use High Suite for stock Firmware -> this mobile phone is not supported and also couldn´t activate MTP as I am not in the phone. So far.
Next Idea -> ok. will take the C900B300 and go back to Marshmallow. From original HUAWEI site.
Took the European Version in German. Did it over EMUI (hold 3 Buttons) and worked so far but when I turned on I was stucking on the WIFI+. Even pressing the button -> further nothing anymore. So I thought -> maybe another stockfirmware useful.
Again C900B300 and then I think I did the big mistake. Took out the sdcard during it was rebooting (HUAWEI was already visible) and now it is big crap. Stucks at HUAWEI. Turning off not possible. This EMUI is not possible anymore. Just with a trick I am able to get into fastboot. Yeah. But what then? Reading TRWP which I know from Samsungs but putting it on with ODIN. ODIN doesn´t work with Huawei. Do I Need TRWP to get it back to normal Firmware? Mobile phone was never customized or anyhting else. just normal stock was on it and is the wish to get a clean back. Resetting to factory was not possible anymore.
So my questions, even I know it is my fault. Any rescue possible?
What could be the best stock Firmware. I Guess it is a single sim from Austria unlocked and unbranded. Would also take Nougat again. Just wanted to get it back to normal working and now I guess I have a big letter holder. Model from the backside is VNS-L31. More I don´t have.
Thanks a lot for any help for my being an idiot. Samsungs are much more easier than HUAWEIs.

Blimey mate,
This really just boil down to what partitions were damaged in your case- Most likely your system and data,
however since you are still Technically running unmodified emui you could manage to sort of salvage it.
The logic is this:
Most custom roms for the p9 lite build on top of emui (patching the system image) rather than replacing it (like the way samsung smartphones do)- so you could flash the rom, it would wipe your phone clean of viruses in the process and then proceed to do a hard restore back to emui.
1.) get your phone into fastboot and flash this twrp http://www.meticulus.co.vu/p/forum.html#nabble-td27
2.) Then flash this rom : http://www.meticulus.co.vu/p/ressurection-remix-for-hi6250-devices.html MAKE SURE YOU FOLLOW THE INSTRUCTIONS ON THIS SITE VERY CAREFULLY
3.)Follow this guide to do a hard restore https://forum.xda-developers.com/huawei-p9lite/how-to/tips-revert-custom-rom-to-official-t3668413
good luck!!! if you have any questions hit me up!

Hi
Hi Exiatron00,
thanks a lot for your maybe solution way. Will do it this evening after work and come back.
Hopefully it works cause as mentioned in other threads -> don´t think that the original owner opened the Debugging so that I can work over a tool. FRP locked is in fastboot. This was already mentioned in other posts which I have read here in the forums.
Thanks for your step by step explanation. Will do it. Hopefully it works. I am really pissed of my own that i was unpatient with the sdcard. That´s a mistake which shouldn´t happen. Anyway it did. So i will try to do everything to get back working again. I am from IT so I am not such a DAU but newbie with HUAWEIs. Most are Samsungs.
Will give Feedback.
CU

If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.

Hi,
well adb for flashing not working as device not found. Hi Suite installed. Guess that the USB Debugging is not enabled. hrmpf.
There is a similar thread of somebody with no enabled USB Debugging.
https://forum.xda-developers.com/nexus-4/help/fastboot-recovery-remotely-enable-usb-t2177440
He writes an solution how to enable in fast boot mode with using N4 toolkit.
Search for a p9 lite toolkit and found this
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
may could work?
Big **** -> as Long as USB Debugging is not enabled as Long I am not able to Flash TWRP over adb.
If I connect to PC Hi Suite opens automatically. So driver should be fine as pc recognize the phone.
hm?

Got it working somehow
Exiatron00 said:
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Click to expand...
Click to collapse
Hi Exiatron00,
got it working somehow!!!!
Bought a 3 day licence for DC Phoenix where you are able to put Firmware even in fastboot with FRB lock and no USB Debugging on.
So I got the IMEI and Fitting Version which is a L11.
Downloaded it original from Huawei as I still want a original stock Rom not customized which was
HUAWEI P9 Lite Firmware (VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU) only wokring one.
BUT the big Problem is that the apk Android System Web View is missing in the ROM. A known Problem by HUAWEI. Yeah now I am stucking in the Setup wizard like this guy who mentioned also the solution whell the reason of this Problem.
https://forum.xda-developers.com/hu...stuck-initial-setup-upgrade-to-t3498097/page2
So my question now. How do I get the apk on the phone still no USB Debugging? Does anyone have this Version original incl. this apk? Maybe an img. from a running working System?
Only way I am able to put the Firmware on is DC-Phoenix. It is valid still two days. Maybe someone can help me? Please?
So an Image of VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU incl. Android System Web View, so that I can go ahead and use the phone again please?
Thanks a lot.
Kind Regards.