Hi there, its me again. A while back, I wrote a post about my Nokia Lumia 520 not entering Flashing mode. While this issue is resolved, I am still unable to properly use the device.
I had recently decided that I would like a different operating system on it. Something that would at the very least allow me to use the phone as an actual phone. The solution: Android.
While flashing mode is now available to me, I am unable to unlock the bootloader. I made the mistake of upgrading to the latest firmware, which is not supported by WPinsider. To fix this, I would need to downgrade the firmware to an older build that WPinsider can work with. I have found one, but it doesn't work. WPinsider reports The GPT read isn't valid. Couldn't fine the text "EFI PART". I am unsure of what this means.
I would like to know of anyone knows what this error exactly means, and if there is a way to fix it.
Thanks in advance!
Related
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 have a problem with my LG G6 H870 which concerns modding. I explain everything:
I have already modded my LG G6 in the past: root, custom roms, drivers and more, until I decided to return to the original system, the latest version, namely the v30b (in my case with the TIM brand (Italy).
Lately, with the desire to resume modding my device, I realize that LGUP does not work giving the following error: 0x81000302; and saying: Use the latest DLL. I confirm that I have changed versions of LGUP and also DLL, to no avail. The only version, of which I can't find the link, was one with a patch that allowed me to "force" the flashes. However, I don't want to use this latest version but permanently fix the problem. I think the problem lies in the last flash I made, in fact I find myself with an OEM (ORIGINAL) unlock key, which turns out to be wrong at the time of the flash via fastboot. Trying, when in doubt, to download another original key from the lgdeveloper site, I discover that the system replies with IMEI 0, thus understanding why the key was wrong. I would like to point out that I downloaded the current version (v30b TIM brand) from the LG-Firmwares website (with which I have never had any problem). I hope someone can help me to solve my problem permanently.
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
next time try to get more comercial, vastly sold, phone. choosing Qualcomm helps a lot
metafaniel said:
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
Click to expand...
Click to collapse
Hi, how did you change the updater script file? I have an Y6 MYA-L11 phone but i'm not able to skip model error message (I tried to change all "SCL-L02" with "hwmya_L6737" in the updater script file but it didn't work).
Another question, did you finally find a working rom?
Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.
s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .