Hello i have a problem with a friends LG G2 I flashed it lolipop 5.1 and then i wiped the whole internal storage clean and installed new firmware on it i tried flashing 4.4 the second time then the phone did not boot up and the screen was stuck to an error message cant quite remember it.
Anyway my friend sent it to lg and they said to him that the phone was double flashed and it could not be fixed... I need to know if i can recover the phone and if so detailed steps if possible.
Thank you very much (The phone has access to TWRP recovery.)
Please guys it is very important i need help with the matter
It can be unbricked. Your problem was probably flashing wrong bootstack since you got security boot error.
First, if you can get into download mode, do tot/kdz. There is guide here on xda
http://forum.xda-developers.com/showthread.php?t=2432476
Hey! First thing you need to know: i'm stupid af
So yesterday i tried to root my Huawei P9 Lite VNS L31, and everything was doing great: bootloader unlocked and everything.
Because the root didn't seem to work on EMUI, i tried to install another ROM (i'm stupid) with TWRP: so I wipe cache, system and data in order to do it good, i flash the ROM but now when i tried to reboot it didn't boot.
So i figured that i was trying to install a MM Rom on an Nougat (at least it was) device. I then tried another ROM and i didn't work either. After hours of trying to make it work, now it boots on Huawei eRecovery, but i already tried to use it since i made no backup (i'm an idiot), and it seems to fail every time? idk it only show a big red ! mark
Right now i'm still looking for a fix but i would be soooooooooooooooooooo freaking relieved if someone could help me please :crying:
(i'm an idiot)
I DID IT!!!!
So i followed a tutorial made by the website androidmtk (i can't link it it's my first post), and is used the official stock firmware for my phone which you can find on cusumer huawei dot com
DONT FORGET TO BACKUP!!!!!!!!!!!!!!
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?
Hi everyone,
I had issues with the update of my OnePlus 5 as stated on this thread : https://forum.xda-developers.com/oneplus-5/help/oneplus-5-update-fails-t3866533
I tried the solutions that were given to me but it wouldn't work, since TWRP kept returning ERROR 7.
I finally managed to install OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip thanks to twrp-3.2.1-1-cheeseburger.img without getting any error but my phone got stuck at the "Dots turning" logo when I boot.
I looked around a lot trying to find a solution and as far as I understood, it may be due to the addition of Treble to OnePlus. I tried to wipe everything thanks to TWRP and flash my phone back to OxygenOS 5.1.3: OnePlus5Oxygen_23_OTA_036_all_1806131715_b5381c0ef26d9e.zip but it's still stuck.
Could anyone help me ?
Thanks a lot
This guide will help you: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
A HUGE thank you ! It worked perfectly.
Note for people who might see this thread : it locked my bootloader, I had to unlock it back (and wipe all data). Flashed TWRP and Magisk, everything works perfectly
Hi guys, today I made a big mistake by thinking that it would be so easy to root on my S5 +, I was wrong, because it appear that I had the bootloop problem, i resolved it by mistake i was so lucky, I tried to put a BootLoader on Odin on AP section, an error occured on my phone, It reset it and it did come back to life Yeah WTF right ? So now that i've got my phone back ! I'm happy but still, I'm worry about my sim and I want to know if someone is listening to me (because strange things happened lately), that's why I did some research and It appear that an app does exist to prevent such thing ! it's called Snoopsnitch, Amazing isn't it ?
I've got hope that you might be able to help me to root my phone properly this time and avoiding the loopboot issue. If you can led me to do it, it would be amazing.
There is my config. I wish you a good day, night or whatever you are doing on this planet. Kiss. :victory:
https:// ibb.co/FqssRkM
https:// ibb.co/5BPrc7p
Sorry i'm new and i'm not allowed to share my image link so I had to trick the system ><
Thanks for your time and your answers guys. :highfive:
Oh hi, im having the boot loop / logo problem too.
could you explain more clearly what you did to resolve that and is it still good to this day?
ive already used odin3 v3.11 and put the latest stock firmware successfully but the phone still boot loops or if lucky it will get passed the carrier screen (O2) but then as soon as i restart the phone it will boot loop again. (or boot loop randomly, if i dont restart it myself, eventually).
I havent tried TWRP or PIT as im a basic user and just wanted the stock rom.
Any updated advice? ...im worried its the memory/emmc/hardware prob
thanks