Database Users

[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

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?

Lock bootloader after root and ROM custom

Hello, guys.
Recently, i wanted to install the fulmics ROM (which is awesome) on my LG G6 H870.
So, i've done it, the bootloader has been unlocked, it's rooted right now, and i've got the Fulmics ROM which works perfectly.
But, i still have a question. When i boot up my phone, i've got this message :
"Your device software cannot be checked for corruption. Lock the bootloader. etc..."
This isn't a problem, because i can boot up my phone.
But i just wanted to know if i can remove this message, and how ?
Thank you all for your answers and your help.

This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.

normal bro don't worry

[/COLOR]
basicreece said:
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
Click to expand...
Click to collapse
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10

learning_to said:
[/COLOR]
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
Click to expand...
Click to collapse
Magisk manager and use the magisk hide feature.

No sim card - no service / nexus 6P

Hey everyone , yesterday i unlocked my bootloader and flash twrp recovery and everything was fine , and then i flashed a custom rom and still everything was fine , untill i flashed vendor , radio and bootloader to another version's , and flashed the cortex 15.10 version that is based on stock android with the pixel experience , and everything worked fine .. i rebooted it and it's not detecting my sim card anymore , i tried to get back to my previous rom , and didn't work .
So i don't know what to do , i think im stuck on this rom and i don't know what might help , so please anyone knows how to solve this ?

A bug in oreo... Set security to none, reboot, then set security of your choice.

xterminater07 said:
A bug in oreo... Set security to none, reboot, then set security of your choice.
Click to expand...
Click to collapse
Im sorry but im not that good at these things so can you describe more , what do you mean in security ? And where i can change it , and thanks

xterminater07 said:
A bug in oreo... Set security to none, reboot, then set security of your choice.
Click to expand...
Click to collapse
Im sorry i didn't understand from the first time , but i tried it now and it worked , thank you so much i really appreciate it

xterminater07 said:
A bug in oreo... Set security to none, reboot, then set security of your choice.
Click to expand...
Click to collapse
oh!!! my!!!! god!!!!
it works for me !!!
Thanks a lot!!!!
i have spend hours time on fixing it (flash ~wipe ~ flash ~wipe ~~again and again)
i'm using Lineage 15.1 and here is what i did:
Settings -->Secuity & privacy --->Screen lock--->select None---->reboot
everything's ok !!!!
can you belive it??

myt issue has not been resolved, :/ same situation, im running lineage. when i try erasing the modem through adb i get permission denied and trying through the recovery i get no space left on device error >:/. ive tried multiple cables, different ports, newest adb package. im at a loss.

Awesome!
I had the same problem with FireHound 4.6.1 / Android 8.1.0. Flashed new vendor.img and radio.img with no luck. Disabled screen lock security as described above and now it works.
Thanks!

xterminater07 said:
A bug in oreo... Set security to none, reboot, then set security of your choice.
Click to expand...
Click to collapse
No sim card later I installed gapps. This trick solved my issue.

I couldn't help replying to this in the hope that I could also get help. Does this or any other method solve the No Service issue where the SIM card is recognized? Mine shows the network name but still says No Service. I have tried everything I know of, yet no help.

THANK YOU FOR POSTING THIS! I was going crazy trying to figure this out!

I've tried this option on my Nexus 6P but it didn't work for me unfortunately... any other things I can try??

LG G6 H872 Encryption Bootloop - please help

Hello,
I recently went through the ROOT process for H872 (T-Mobile version) and was able to install custom ROMs (PixelExperience_Plus_h872-10.0-20200326-2210-UNOFFICIAL & Havoc-OS-v3.7-20200711-h872-Official).
Every time I try to "Encrypt" the phone, phone asks for pin, restarts, shows android logo, reboots again and then gets stuck in bootloop (up to LG G6 ThinQ logo).
Only way to recover from this state is to boot into TWRP to format the data; and reflash everything.
Bootloader is unlocked.
Using TWRP 3.2.3 Nebula_Alph_20180813 (one from the root instruction).
Please let me know if there is a way to to enable encryption.
Thanks!

Unfortunately force encryption won't work in Custom ROMs. That's why I am on stock

SkylineDiT said:
Unfortunately force encryption won't work in Custom ROMs. That's why I am on stock
Click to expand...
Click to collapse
Thanks for the reply.
Yes, looks like you are correct.
Wonder if there is a ROM with default encryption.

tejtank said:
Thanks for the reply.
Yes, looks like you are correct.
Wonder if there is a ROM with default encryption.
Click to expand...
Click to collapse
Maybe Fulmics lol, But I dont know if there is version for H872. And Fulmics is outdated. You can try to debloat Stock ROM. Put Nova or other launcher

SkylineDiT said:
Maybe Fulmics lol, But I dont know if there is version for H872. And Fulmics is outdated. You can try to debloat Stock ROM. Put Nova or other launcher
Click to expand...
Click to collapse
Thanks for response.
Anyway to hide or bypass the encryption status ?
Stock Image = Encryption works but outdated security patch
Custom ROM = Encryption doesn't work but updated security patch
Not sure which is better... both have some risk

Encryption helps when you lost your phone, without passcode you cant access data
New security patch - helps in app or ir OS security, it harder to hack or to use holes in software to get access to various data when phone is use.

SkylineDiT said:
Encryption helps when you lost your phone, without passcode you cant access data
New security patch - helps in app or ir OS security, it harder to hack or to use holes in software to get access to various data when phone is use.
Click to expand...
Click to collapse
So in your opinion, encryption is priority over security patch?

tejtank said:
So in your opinion, encryption is priority over security patch?
Click to expand...
Click to collapse
For me encryption is priority, because I have sensitive data on a phone: banking app, email client and so on