Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions - Huawei P9 Lite Questions & Answers

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?

Related

Yoga Tablet 2 1050L Firmware Upgrade!

Today i receive notification about upgrade, im now donwloading it but cant find what update is it...
its not something 50mb update, its 1.37GB update.
nothing on lenovo's web pages.
maybe someone knows what will bring this update???
i cant add screenshot (( what can i do???
Let us know if you see any significant changes when it's complete.
sure, its about 60% now.
rframe said:
sure, its about 60% now.
Click to expand...
Click to collapse
while i cannot say what is new (not having an 1050L tab) i did downloaded and checked inside
this is what he does:
1. writes on ESP a new x64 bootloader
2. writes a new boot image
3. writes a new fastboot image
4. updates the bios with a new capsule (and by the size it writes over all the bios region)
5. writes a completely new system image (however it does it by using the patching way, even more using the block-update)
all in all excepting your data partition (where you have your personal data/preferences and the apps you personally installed) it will do a fresh new install of everything
problems one could have:
1. obviously if you had an unlocked bootloader you will need to flash back again
2. if the bios updates also the security part it's possible that you will no longer be able to use the unlocked bootloader
3. the new system is wrote by block patch (they could have wrote by flashing method) and this means you can have problems if you modified it (ie mounted at some point and changes something on it) by rooting or something else
on the bright side now someone could build a 'stock' rom for this model using this ota (so you can flash lollipop stock rom from lenovo and even a recent one by means now known)
So is it still 5.0 and not 5.1? Seems excessive for a bug fix build.
10x, i have stock not rooted not modified.
its 99%, i will write today if android version will be changed.
its 02:22 am on my clock and i must sleep tomorrow i will check what will be changed.
derpadoodle said:
So is it still 5.0 and not 5.1? Seems excessive for a bug fix build.
Click to expand...
Click to collapse
some props extracted from the build.properties in the new system image
ro.build.version.incremental=YT2-1050L_USR_S100192_1511191319_WW52_ROW
ro.build.version.release=5.0.1
ro.build.version.security_patch=2015-12-01
ro.product.ota.model=YOGATablet2-1050L
ro.product.name=YT2_10_row_lte
so no, it's still 5.0
it's big but it's also lenovo , joke aside this way it's better than incremental patches and it also gives you basically a stock rom (well first someone should compile it)
Ahh right, just stagefright patches then no doubt.
Yeap, its still 5.0.1
We recommend not to upgrade if you want to change?
i didnt find something changed. but i think the overall performance is increased and it better gets wifi signal...
They fixed also the new user problem
Now u can add new user or switch to the guest mode
Is there anyone noticed anything else?
Is the bios now is x64?
Has anyone received an update for the 1050F model?
firmware update 1050L not possible
Every time I try to install this update, which comes up every day, I get the message that my SD-Card is making problems.
But even if I officially unlink the SD-Card and take it off, the error message stays the same and I can't update.
How can I solve this problem?
Does anyone knows where can I download this firmware? YT2-1050L_USR_S100192_1511191319_WW52_ROW

[Q] How can I reset this phone?

Here my problem:
-When i was able to use B052 then flashing B190 then update to Emui 4 and everything work as well.
-Now i cannot do any kind of update.
-I try to flash B052 via fastboot, the device is boot but i got strange launcher, some settings are missed or empty, to not talk about Balong bug.
My device is come with single sim firmware, how can i install the first shipped version?
I'm really unhappy from this phone. I try every kind of solution but without succeed, any help will be thanked.
haky 86 said:
Here my problem:
-When i was able to use B052 then flashing B190 then update to Emui 4 and everything work as well.
-Now i cannot do any kind of update.
-I try to flash B052 via fastboot, the device is boot but i got strange launcher, some settings are missed or empty, to not talk about Balong bug.
My device is come with single sim firmware, how can i install the first shipped version?
I'm really unhappy from this phone. I try every kind of solution but without succeed, any help will be thanked.
Click to expand...
Click to collapse
Do you remember the build no. which device came with? By the way did you try updating your phone by "force update" (by pressing all three buttons while phone is off). You can also update it via hisuite.
Suleiman01 said:
Do you remember the build no. which device came with? By the way did you try updating your phone by "force update" (by pressing all three buttons while phone is off). You can also update it via hisuite.
Click to expand...
Click to collapse
that the problem, i don't remember, will try to switch to dual sim then convert to single sim and see if solve the problem or will get back to reparation service.
haky 86 said:
that the problem, i don't remember, will try to switch to dual sim then convert to single sim and see if solve the problem or will get back to reparation service.
Click to expand...
Click to collapse
I think due to balong bug you are having these problems(I had balong bug too when I converted to official firmware from sokkoban rom). You just need vendor file of your phone. I have it but it's for dual sim.
Suleiman01 said:
I think due to balong bug you are having these problems(I had balong bug too when I converted to official firmware from sokkoban rom). You just need vendor file of your phone. I have it but it's for dual sim.
Click to expand...
Click to collapse
Thanks, it's look like solved by reflash B049, everything is working as should be, I don't think to touch again... for backing up for testing cm builds..
haky 86 said:
Thanks, it's look like solved by reflash B049, everything is working as should be, I don't think to touch again... for backing up for testing cm builds..
Click to expand...
Click to collapse
Maybe you should take a break for a while. Might refresh you up

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.

Axon 7: No connectivity after upgrade to 7.1.1

Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
SlickRobie said:
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
Click to expand...
Click to collapse
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Choose an username... said:
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Click to expand...
Click to collapse
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
SlickRobie said:
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
Click to expand...
Click to collapse
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
It may help understanding to know that there are 3 models.
A2017 is the Chinese one, A2017U is the American one and A2017G is multinational/European. There are different telephony frequency bands in use around the world and the Chinese one also has different storage and memory. A bit bummed they held that back from the rest of the world.....
Choose an username... said:
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download [https:// androidfilehost.com/?fid=457095661767137840]this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
Click to expand...
Click to collapse
Thank you for quick response.
Yes, you are correct, warranty is non-issue anyway and I will make sure it is for A2017 (not A2017G/U). Wish I had just checked the back of the phone then I would not have ended up here but it is nice to learn new things, however painful..
Thanks for the heads up on the process as well. There goes my weekend but the boss (wife) is away so it is okay.
I will report if I manage to get it working next week. Wish me luck.
Robie
Update.
I spent the weekend on this and sadly didn't get anywhere. I followed the instructions and download from here:
http://https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873.
Unfortunately, no joy. I can get my phone in EDL mode (drivers downloaded & suetup successfully, COM port is correct, etc) but the following commands just sit forever. They don't respond at all.
axon7backup.exe -p COM# -d
axon7root.exe -p COM# -r
Not sure where to go from here. If anyone has any ideas then please let me know.
Thanks.
Robie

How to make my VNS-L21 C432 B503 EMUI 5.0.3 Single-Sim to a Dual-SIM?

Hello everyone,
i would need help - if its possible anyway - to get the Dual-Sim working on my SS P9 lite.
Until now i was able to unlock BL, install TWRP Elite and SuperSU 2.82.
What do i have to do next?
Thank you in advance...
(PS: flashed some oeminfo - did not work, so i flashed back my original bached up oeminfo -
strange thing is that *#*#2846... is not working anymore - i recognized that because i wanted to
reinstall from HWOTA mode...? Should i orry about that?)
crouso said:
Hello everyone,
i would need help - if its possible anyway - to get the Dual-Sim working on my SS P9 lite.
Until now i was able to unlock BL, install TWRP Elite and SuperSU 2.82.
What do i have to do next?
Thank you in advance...
(PS: flashed some oeminfo - did not work, so i flashed back my original bached up oeminfo -
strange thing is that *#*#2846... is not working anymore - i recognized that because i wanted to
reinstall from HWOTA mode...? Should i orry about that?)
Click to expand...
Click to collapse
Hello,
had you already took a look at @k1ll3r8e's thread ?
He made a toolkit that can do what you need.
Best regards
Edit:
Dude you can do that also without the toolkit.
You only need the right oeminfo dual sim
and the correct rom.
Feel free to ask...
hello dadditz,
thank you for your reply! Of course i read a lot here and other sites, and also found the P9 toolkit! But my problem was/is, that i cant "upgrade" to VNS-L21C432B160 because i already was on VNS-L21C432B503 ... so i tried different things, but it did not work. Always the menue "Dual sim configuration" was not in the settings menue... and the image felt little bit "laggy"...
BUT
i was giving it another try - i downgraded from Nougat to MM with this ... tutorial and repeated the steps listed in the P9 lite toolkit... and now i have the Dual-Sim menue in the settings dialogue... and it is working
Because its not "enough" i wanted to return to Nougat - until now with no success... so am i now stuck on VNS-L21C432B160 ?
I tried some images from 380/370/336 but the huawei recovery always stops on 5% and denies the update - how can i upgrade again?
kind regards
crouso said:
hello dadditz,
thank you for your reply! Of course i read a lot here and other sites, and also found the P9 toolkit! But my problem was/is, that i cant "upgrade" to VNS-L21C432B160 because i already was on VNS-L21C432B503 ... so i tried different things, but it did not work. Always the menue "Dual sim configuration" was not in the settings menue... and the image felt little bit "laggy"...
BUT
i was giving it another try - i downgraded from Nougat to MM with this ... tutorial and repeated the steps listed in the P9 lite toolkit... and now i have the Dual-Sim menue in the settings dialogue... and it is working
Because its not "enough" i wanted to return to Nougat - until now with no success... so am i now stuck on VNS-L21C432B160 ?
I tried some images from 380/370/336 but the huawei recovery always stops on 5% and denies the update - how can i upgrade again?
kind regards
Click to expand...
Click to collapse
Hey,
I think you could save yourself from going back
at MM, but, the omelette is made now ...
Have you already done a factory reset + wipe cache in stock recovery ?
Tell me a little bit when you reboot the device
does any warning text come out ? if yes, what color ?
Dadditz said:
Hey,
I think you could save yourself from going back
at MM, but, the omelette is made now ...
Have you already done a factory reset + wipe cache in stock recovery ?
Tell me a little bit when you reboot the device
does any warning text come out ? if yes, what color ?
Click to expand...
Click to collapse
Well, when i was on Nougat, i was not able to see the "Dual Sim Settings" in the settings menue - i tried 20 times
i think... when i went "back" to MM the menue was immediately there...
I did the factory reset and wiped cache in stock recovery menue.
Booting up my device seems all fine - bootloader is relocked, no warnings or anything...
HiSuite told me that my device "has the latest developer version" and no upgrade would be available...
I tried to flash the firmware with TWRP - without success...; when i try dload the phone stuck on 5%... i also
tried the "-PV" versions - without any luck...
So i really have no idea left how to upgrade from this version?!
crouso said:
Well, when i was on Nougat, i was not able to see the "Dual Sim Settings" in the settings menue - i tried 20 times
i think... when i went "back" to MM the menue was immediately there...
I did the factory reset and wiped cache in stock recovery menue.
Booting up my device seems all fine - bootloader is relocked, no warnings or anything...
HiSuite told me that my device "has the latest developer version" and no upgrade would be available...
I tried to flash the firmware with TWRP - without success...; when i try dload the phone stuck on 5%... i also
tried the "-PV" versions - without any luck...
So i really have no idea left how to upgrade from this version?!
Click to expand...
Click to collapse
Use Firmware Finder to force the upgrade, download it from the store.
VPN method worked fine for me (i was on android 7).
Inside the app all the info, anymore
a thread is present here on XDA.
Give it a try...
You're on B160, go for B370 PV version, check compatibility otherwise choose for full ota one.
Good luck
Cheers

Categories

Resources