Database Users

G1 hangs after 1.6 update

Hello,
For the third time in one month, my G1 device hangs on the boot screen.
I've send the phone to tmobile two times and they fixed it.
When it comes back, it has firmware 1.5 CRB43.
But now the problem:
After a while, the phone comes up with an notice that a download is ready
(1.6), i choose install, the phone reboots a few times and then gets stuck on the boot screen. I don't know how to fix this or what is causing this problem.
I never rooted the phone, just using the official OTA updates.
I just don't understand why the official OTA 1.6 update is causing this to my official Tmobile G1 phone (bought in the shop).
Anybody who has an idea to get my phone to work again?
I can acces the recovery mode, but reset doesn't fix the problem.

You would have been better off getting cyan rom if you have root, since ota 1.6 is laggy like hell.

thomas_1984 said:
Hello,
For the third time in one month, my G1 device hangs on the boot screen.
I've send the phone to tmobile two times and they fixed it.
When it comes back, it has firmware 1.5 CRB43.
But now the problem:
After a while, the phone comes up with an notice that a download is ready
(1.6), i choose install, the phone reboots a few times and then gets stuck on the boot screen. I don't know how to fix this or what is causing this problem.
I never rooted the phone, just using the official OTA updates.
I just don't understand why the official OTA 1.6 update is causing this to my official Tmobile G1 phone (bought in the shop).
Anybody who has an idea to get my phone to work again?
I can acces the recovery mode, but reset doesn't fix the problem.
Click to expand...
Click to collapse
try manually flashing the OTA. you can download the update from here
http://getyourdroidon.com/builds/ota/signed-kila-DRC83-from-CRC1.c41b93c1.zip
rename it to update.zip and place it on the root of your SDcard
boot up your phone holding Home+Power
Press Alt+L
Press Alt+S
(it should say something about updating)
your phone should reboot automatically
pm if you need anymore help/clarification

@B-man007,
Okay, i've tried the file you said.
It says (in this order):
Finding update package
Opening update package
Verifying update package
Installing update
Installation aborted
So it doesn't install that file, really quick after the installing update the screen flashes and it says installation aborted.
I have an dutch (european) phone, your file looks like an usa update.
I also tried an EU version, but it gives the same error.
The problem is, i don't know which firmware version is on the phone right now.. I guess something between CRB43 and DRC92. Or maybe it has no firmware at all because it just hangs on the opening screen.
@Ace42, i don't have root, never had. Just using official OTA updates.

thomas_1984 said:
@B-man007,
Okay, i've tried the file you said.
It says (in this order):
Finding update package
Opening update package
Verifying update package
Installing update
Installation aborted
So it doesn't install that file, really quick after the installing update the screen flashes and it says installation aborted.
I have an dutch (european) phone, your file looks like an usa update.
I also tried an EU version, but it gives the same error.
The problem is, i don't know which firmware version is on the phone right now.. I guess something between CRB43 and DRC92. Or maybe it has no firmware at all because it just hangs on the opening screen.
@Ace42, i don't have root, never had. Just using official OTA updates.
Click to expand...
Click to collapse
goto unlockr which is here for root.
http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/

I've tried that website, but it's not working in my case.
Trying to install the original SPL gives an error (no signature files found).
I also can't install the Original DreaIMG.nbh file, it keeps saying:
00028002 not allow in bootloader.

Yoga Tab 2 830f Is there a soft brick fix?

I've searched but apparently it seems like most of the answers have been deleted or redacted.
My problem...
I was just given a Yoga Tab 2 from my sister who has given up on trying to fix it.
The tab was on 5.01 and rooted when she got a system update. She ran the update but now the tablet freezes during/after the boot animation.
It will go into fastboot but is not recognized by ADB.
She tried to install the original Lollipop firmware through recovery but ended up getting a system 7 error.
This is exactly what I see when in the bootloader screen
FASTBOOT MODE
PRODUCT_NAME - YT2
VARIANT - YOGA Tab1
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - Blade_21.x64.0005.R00.1504101447 FFD8_X64_R_
SERIAL NUMBER - BaytrailD454B***
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
I know nothing about Lenovo and how they do things but I know that with HTC you have to go back to 100% locked and stock before you can install an OTA. If you do try the OTA usually just won't install but unfortunately this thing seems to be at least soft bricked.
Is there a way for me to maybe roll back? I've read about people going back to KK in order to get the LP OTA but all links to the KK firmware are gone.
Thanks a lot, I appreciate any help I can get...
BTW, She is under warranty but of course she was rooted and is worried that repair will cost her almost as much as she paid for the Tab when they realize and void her warranty.

If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.

corasman said:
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
Click to expand...
Click to collapse
Thank you. I used the Restore KitKat Bios you posted along with an 830F specific KitKat firmware from the Russian Lenove site. Worked fine after editing the flash.xml file to allow for a larger system.img file.
The tablet is now back from the dead. Unfortunately it gets the 5.0 update but fails in the Lenovo Recovery when trying to flash the OTA. It gets to 100%, stays like that for a bit and then a blue X saying flash failed. After that I'm back to a black screen and have to reflash the kitkat firmware to get up and running again.
I have no idea why the OTA flash constantly fails but I guess I have to do a bit more research and hope I can get her up to date.

Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024

corasman said:
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
Click to expand...
Click to collapse
Outstanding!!! I entered the code in contacts and it gave me a menu of different countries to choose from. I Chose US and she rebooted, went into recovery, ran a bit and rebooted into another fresh install which looked completely different. We're talking different wallpaper, and different apps. After that it successfully installed 4 or 5 OTAs and as far as I can tell it is now completely up to date!
Android Version is 5.01
Build is S100250-160119
Kernel Version is 3.10.20-x86_64byt-g9f7fad7
Security patch is dated 2016-02-01
I'll wait a few days before I root and install Xposed just to be 100% certain it's up to date.
Of course my sister will probably ask for it back now.
Either way, THANK YOU VERY MUCH corasman!!! Your help has been invaluable!

I am so pleased it worked for you, ionioni helped me so much and now I am trying to do the same for others.

Huawei Y625-U51 Soft Bricked?

I soft bricked my Y625-U51 (I bought it as a second phone to mess around with) and tried to install a version of cyanogenmod not made for this phone, this threw it into a boot-loop, effectively soft-bricking it, the thing is, i could just flash the stock firmware from the huawei site onto the phone right? Problem is, they don't have it up for download, or any info on it, and all the versions i found online, are older than the currently installed firmware, giving me the "can't install this package over newer build" Error, what do i do? I would be fine using the older firmware, but is there a way to disable the time check, and/or does anyone have a newer version of the firmware?

I need solution too
Dax1240 said:
I soft bricked my Y625-U51 (I bought it as a second phone to mess around with) and tried to install a version of cyanogenmod not made for this phone, this threw it into a boot-loop, effectively soft-bricking it, the thing is, i could just flash the stock firmware from the huawei site onto the phone right? Problem is, they don't have it up for download, or any info on it, and all the versions i found online, are older than the currently installed firmware, giving me the "can't install this package over newer build" Error, what do i do? I would be fine using the older firmware, but is there a way to disable the time check, and/or does anyone have a newer version of the firmware?
Click to expand...
Click to collapse
I am having same problem with same phone cant find firmware newer than installed V100R001C577B111 or one that i found needs to be installed through cwm or twrp and cannot be installed through stock recovery..

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?