Hello everyone!
I have a LG V20(F800L) and Android 9.0 (the latest official version). I have used it for a long time before, and there is nothing wrong with the hardware of the mobile phone, but I am a little tired of the system. I'm going to change a custom rom. After demotion, unlocking, root and rec, it will be displayed as us996 and Android 6.0 on the computer.
The problem now is: the rom can't be brushed, and there is no system installed in the mobile phone. If it is turned on, it will always stop at the LG boot interface and can only be turned off by pressing the battery.
You can manually enter the rec and perform various cleaning and installation operations, but I tried to write all the ROMs (basically us996 and vs995) that I could find on the XDA forum, and all failed.
I don't know what the problem is. (Maybe writing official firmware can succeed? But I heard that this would lead to re-locking. And it's meaningless for me to brush the official firmware, because I was the latest official version, Android 9.0 and kernel 3.18, and I don't want to go back to the original starting point. )
My ultimate goal is: the kernel can be upgraded to 4.4, and the newer the Android version, the better (the latest version that can be found at present: Lineage 19.1). Now it seems that the purpose has not been achieved.
Who can point out what the problem is? How should we solve it? Thank you very much!
Related
I would like to update my S4 to Lineage OS 14.1 and I have an older version of TWRP 2.8.4.0 recovery on my phone. What is the best way to upgrade to the newer ROM? Do I need to update TRWP recovery in order to install Lineage OS 14.1 or will it work with the older version? Its been a while since updating my phone could you someone point me in the right direction.
Update,
I've tried updating to a newer version of twrp via the app store and downloading the new update. For some reason when I browse from the file from twrp cannot find the img file. Any idea of why this is, I save files to specific directory where I can find them.
Thanks
I am in the same boat, however I am currently on cyanogenmod 13.
Where did you find v14.1 for jfltespr?
FYI I set it and forget it and try to update to the latest greatest yearly.
I am under the impression that there is no active maintainer for lineageOS however it appears to have forked.
so far I have found these options:
OCTos: https://forum.xda-developers.com/galaxy-s4-sprint/orig-development/rom-team-octos-oct-n-t3537546
Vanir & Commotio: https://forum.xda-developers.com/galaxy-s4-sprint/development/rom-vanir-commotio-05-30-2017-t3614632
I am torn, I want the latest (and acquire the security updates) but I know little to nothing of either of the two above;
plus I am very rusty in trying new ROMS.
would be interested to see what you come up with
I did come across this, but not sure about installing it. I'm on a older version twrp, didnt know if the latest version is required to install some of the newer roms.
https://androidjungles.com/install-...icial_Android_Nougat_ROM_In_Samsung_Galaxy_S4
If you use twrp recovery, how were you able to update it? It keeps failing for me.
i am not so sure that the link is for a jfltespr
seems to be for a different device jfltexx (the international version).... see http://www.lineageosrom.com/2016/12/list-of-devices-getting-official.html
qu1nn said:
i am not so sure that the link is for a jfltespr
seems to be for a different device jfltexx (the international version).... see http://www.lineageosrom.com/2016/12/list-of-devices-getting-official.html
Click to expand...
Click to collapse
Yea I know, I kind of figured that.
Hey guys,
I have a LG d802 phone which a relative asked me to update (i.e install a custom ROM) because his version of Android, 4.4.2 is having its support dropped for different, important applications he uses and he would need to throw this perfectly healthy phone away otherwise.
I am no expert at Android rooting, but I know the basic idea anyway. However, when I look up this device on TWRP.me (as well as their official app), it gives no results. I find it strange that the international variant of this phone would be unsupported; especially since I have seen threards on XDA as well as YouTube videos posted about running TWRP on this device. I am reluctant to try flashing files from random Dropbox (or similar) links however, especially if they are a few years old.
Could someone please provide an explanation how I go about to flash TWRP on this device, and if there is any special rules regarding installing a custom ROM (in my case, ResurrectionRemix) and GApps?
Also, I understood I need something called "loki", what is this and how do I use it?
Running Android 4.4.2, everything in stock except I enabled USB debugging.
Thanks a lot for any assistance!
Apologies for cryptic title. My Mi A1 has multiple issues and a patchy update history. I don't know how to narrow this down to a single, simple question. Hope someone can help to make sense of this.
History: Bought new with stock Android One, Oreo. Few months later updated to Android One, Pie (official update). This caused big problems with wifi (connections constantly dropped and VERY slow downloads). Thought about reverting to Oreo, but decided to change to Lineage (which at the time was Oreo). So I downgraded from Android One Pie to Lineage 15 (Oreo). Generally worked OK, but with 3 big problems:
1. No sound during phone calls (I can't hear them, they can't hear me). Found a workaround involving editing the build.prop file (sorry, can't post link), but fix is temporary and needs regular re-boots.
2. Fingerprint sensor not working (no options to set fingerprint).
3. Camera app lost functionality related to dual lens.
I subsequently updated from LOS 15 (Oreo) to LOS 16 (Pie). Issues still there.
I wonder if I have some missing/incompatible vendor firmware components, but I don't really understand how this works. If I download and install, say, a LOS rom, does it contain EVERYTHING my phone needs to work, or do I need to already have some proprietary bits somewhere on the phone?
Is my best bet to start afresh (clean slate) and if so what would you recommend? Any help/insight greatly appreciated!
Hey pal, the Android Pie Firmware has some kind of anti-roll back protection, so when you install a non-pie ROM such as LOS 15 using Pie Firmware you'll have that problems like no-fingerprint, no incall audio, etc. If you install an Oreo Firmware with an Oreo ROM, you'll have fingerprint but no IMEI/Signal (and other problems).
You have 2 options:
1) Update your firmware to the latest Pie version and install a ROM like Pixel Experience or HavocOS (both Pie) and you're set, IMEI, Signal, Audio and Fingerprints will be working OK.
2) Install the latest Pie compilation using MiFlash and leave it stock.
Greetings.
Thanks for prompt reply! Can you spell something out for me please?
Regarding 1) I have already updated to LOS 16, which is Pie. Is that what you meant by "update your firmware to the latest pie"? Or do you mean a stock firmware? If the latter, then I could find a MIUI rom (from en.miui.com) but not Android One.
Regarding 2) Again, by "latest Pie compilation" do you mean the stock rom, like the MIUI mentioned above?
Thanks
Hello, I have updated my max pro m2 to latest version provided by asus. However, i have came across various telegram groups claiming that the latest update is creating problems and device is getting stuck into bootloop. Some are stating it as a buggy update and some are saying it is caused by problem in motherboard. Can i get some insight in this matter. If this is caused by the software then what should I do now as i have already updated. Should i switch to any custom rom?
*
Software Version WW-16.2017.2002.073
imjeetmishra said:
Hello, I have updated my max pro m2 to latest version provided by asus. However, i have came across various telegram groups claiming that the latest update is creating problems and device is getting stuck into bootloop. Some are stating it as a buggy update and some are saying it is caused by problem in motherboard. Can i get some insight in this matter. If this is caused by the software then what should I do now as i have already updated. Should i switch to any custom rom?
*
Software Version WW-16.2017.2002.073
Click to expand...
Click to collapse
Yess, we have seen around 20+ cases in which devices were bricked, the device stuck at splash logo, and flashing through fastboot mode is also restricted.
I would recommend you to switch to custom roms, or use stock version 072 or previous ones.
Most of the user's had the same 073 stock rom who faced this.
Mine one also got same problem this morning but it is able to go to recovery mode. so should i attempt factory reset from there first or directly go for flashing the rom into it.
Hello! I've modded already some devices, but I never got in my hands a device that lived so long.
Since I cannot find any infos about using latest Magisk on a such old device and I don't want to mess it up, I wanted to ask here some questions.
First: generally, is ok to use a recent version of Magisk on every device, or there are some devices with some kind of differences that needs a "custom" or "specific" version of Magisk?
Second: is ok to use directly the Releases on https://github.com/topjohnwu/Magisk/releases ? I saw that this is the only official way to get it and that magiskmanager is not a related site.
Third: any advices on modding the P8 Lite 2015?
Model runs MIUI 4.0.3 and it's on Android 6. It's the single-sim version.
I already have TWRP working and phone is factory-reset. Yes, I had access to my unlock code, so it was pretty painless to unlock it.
It needs to be fully functional, so I cannot use custom ROMs (it seems like all have problems with YouTube and/or Camera). If there are some advices here, I'm free to listen.
I was planning on installing Magisk (root, generally) to uninstall Huawei crap plus a better control over kernel, if there is any on this device.