My Name is Maxton. I am 11 years old and trying to flash a lineage OS Equivalent on my LG V20. Any advice?
Hi Maxton,
Glad you made it here.
1.You might want to read this:
H918 - lafsploit works - trying to install latest official Lineage
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an...
forum.xda-developers.com
to decide if the LOS (Lineage OS) on H918 is for you or not.
2. And if more information needed after that, try searching for H918 Lineage (or, replace H918 with your own model)
3.
You need to start by finding out:
a. what model is your V20: (In settings and also on the label under the battery)
models with unlockable boot loaders WITHOUT using the engineering aboot:
H918 - (use fastboot oem unlock)(T-Mobile)(engineering bootloader dont work on TMO - instant brick!)
US996 - (use unlock.bin from LG) (GSM Unlocked for US Cellular with CDMA)
models that can use "engineering aboot" (leaked dev version of bootloader)
using the engineering aboot: "BUT we have an engineering aboot for the rest of V20s,
and we can just push the engineering aboot, and twrp just like back when dirtycow worked"
H910 - (AT&T) - some reports of issues
H990 - (T-Mobile, Verizon, Unlocked, AT&T for HK[Dual SIM 990N], Global[Dual SIM 990DS and Mexico[990T])
VS995 - (Verizon with CDMA)
LS997 - (Sprint with CDMA)
b. what ARB you're on, ARB0 or ARB1
dial: *#LGMENU#*model# , so if your model is H918 then ( *#546368#*918# )
choose SVC Menu
choose Version
scroll to bottom
c. what software version you are running:
SETTINGS > ABOUT PHONE > SOFTWARE INFO
d. what Android OS you are running - see that in About Phone as well, it is either Nougat 7x or Oreo 8x
With this information about your phone, a lot more of what you read will start making sense.
4. I can't give you the exact step by step, because I don't know it. However, I can give you this advice:
Do not do anything until you fully unlocked your bootloader (if it applies to your model), and verified it is unlocked. Because if you do, you may get in to a catch 22 situation where to fix it you need the unlocked bootloader, but you can't unlock it because the phone won't boot. Once unlocked, think twice before locking it back, accept OTA, etc. Read about that before doing it.
5. Try to read as much as you can before you do anything to it, especially about every situation that causes a "brick" , and about ways out of a brick. There is so much info here, but all dispersed in so many threads, you might want to think of a method of how to make sure that once you read something, you will never have to read it again, or at least be able to instantly find it. You will appreciate that over time.
6. For your second thread, try naming it in a way that has your main question, like "How to get the latest Lineage on H918?". Thing is, people are busy, they read thread titles and open only those they are interested in. Whats worse, sometimes they only search for threads titles containing certain keywords. So, that way more people are likely to read your thread.
On the other hand, some of the best guys here learned what they know by doing it, and breaking many phones in the process. The trick is that this way, you never forget and you don't waste time, so if this way suits your personality better, it is not a bad way to go, it is only things, you'll have many more.
Related
Hi all
Seems I cannot "Xpose" my chinese A2017 in B13 firmware, ad seems our american colleagues have managed to xpose their phones, so I request some help to make the trip.
First of all would like to make some questions to avoid a shoot in my foot, and, may be, others wonder the same questions.
The start point is a Bootloader unlocked, TWRP'd rooted chinese in B13 Fw.
The target is a Bootloader unloked TWRP'd rooted chinese hardware with A2017U firmware with Xposed
What I know
- There are many separated partitions (areas) in a mobile phone, and in those areas lay different and autonomous softwares for different purposes. Some of those areas are very tied to the hardware anod other areas are not so tied. In my case, I recognise
Boot: This area is used to chosse which of the important areas are to be "active" depending the things you want to do.
Is a key area and have some checks to assure the later success of the process. Unlocking the boot means some of those checks are NOT to be performed. Screwing with this area is bricking the phone. You must be VERY careful when messing with thisRecovery: Another key area. Is activated by the boot and allows you to modify other areas. We use this to gain control of the phoneSystem: Where the phone software stays. No system ==> no phoneSystem image: The same..data: Where all our apps stay, and photos and other stuff. Is not so criticmodem: Very critic area, where the "controls" of the radios live. Hardware relatedBluetoothEFS: Another critic area, as here stay the phone identification
Please confirm if this process is possible, which areas of those are not to be touched when changing from Chinese Fw to US firmware, and how would be the process.
And another question.
Being B13 Unlocked TWRP:
What happens if I execute the stock B13 SD firmware instalation procedure?
Will I loose TWRP?
And what happens with the bootloader?
Thank you very much for your help. Will try to build up a guide if successful...
Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.
Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.
Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK
My confusion is that I thought they were for US models.
Well US version has no NFC but had a compass.
Has yours?
Mine has NFC and no compass lol!
darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.
I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
Rooted, is there a way to get past "This application does not work on your device"
I am using the ATT variant of the V20 and have ATT for my carrier.
Using "*#*#4636#*#*" gets you into the Testing menu, once you click "Phone Information" you are greeted with a pop up that says: "Note This application does not work on this device" (picture attached).
I rooted using this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 and installed supersu. Big thanks to runningnak3d for this method.
Given that I had root access I was hoping there would be a way to get around this menu block. My ultimate goal is to be able to turn off certain bands when needed which I believe is available in this menu. In particular, band 2 does not work well in my area and I would like to be able to turn it off when needed.
Where is the programming that tells the phone to not allow us to access this menu, and is it somewhere that we can access and change with root permissions?
https://www.apkmirror.com/
#MeToo
I'm hunting the same solution.
Rooted H910
I've found "How to force 'LTE only' on LG V20" and "LG V20 CDMA to LTE/GSM switch via Hidden Menu"
While *#546368#*910# does work, the RAT Selection menu is absent.
I have not yet tried the APK. Not sure if I should.
---------- Post added at 06:08 PM ---------- Previous post was at 05:54 PM ----------
ColdSnowden said:
I am using the ATT variant of the V20 and have ATT for my carrier.
Using "*#*#4636#*#*" gets you into the Testing menu, once you click "Phone Information" you are greeted with a pop up that says: "Note This application does not work on this device".
Click to expand...
Click to collapse
This really seems like it should be a simple solution.
You can see the Phone Information screen behind the pop-up. It is clearly running, and active.
Would this not be a setting in settings.xml, or something that could be changed with grant / deny in adb shell?
Any devs have any insight as to how LG broke this function??
OK... I'm a network guy, not a programmer.
So, I may be completely off base here.
But, this is what (I think) I see:
The property sheet in question is launched by activity "com.android.settings.RadioInfo".
This appears to be RadioInfo.JAVA contained in settings.jar.
However, /system/framework/settings.jar is far too small to contain the 100+ JAVA files that comprise the structure of the property sheets.
See this and this.
I want to preface that I haven't looked at this at all -- but the first thing I would try would be changing the model in build.prop. It is going to be a quick, stupid check. It is definitely not doing the check against aboot since aboot would return US996 (since that is what the eng. bootloader is from).
-- Brian
runningnak3d said:
I want to preface that I haven't looked at this at all -- but the first thing I would try would be changing the model in build.prop. It is going to be a quick, stupid check. It is definitely not doing the check against aboot since aboot would return US996 (since that is what the eng. bootloader is from).
-- Brian
Click to expand...
Click to collapse
Brian,
I'm glad you're looking at this. Although changing the model doesn't seem like it would do much.
Disabling this menu is something LG is doing across the board. The only exception at this time seems to be the LG made Nexus 5.
What about replacing the H910 settings.jar with one from the US996 (assuming the menu works on the US996)?
A step further: What about flashing the H910 with firmware for another variant?
I bought my H910 because it had the widest range of LTE band support. But, I'm not on AT&T.
Can I get a generic, unbranded ROM that will run on the H910 hardware - and everything works?
They don't disable it across the board because that menu works on the H918 which is why I figured they were doing a model check.
Yes, you can flash US996 firmware onto the H910. There is a thread around here on what you need to backup before doing that.
Since you are rooted, you can also just grab the US996 system image, and flash that leaving the firmware H910.
-- Brian
Hi everyone,
I have a LG G6 (H870DS/SEA) and it's a great device. Even better with Oreo, now the device doesn't have the problems we've had on Nougat.
Let me tell a quick story about security and this device. I've upgraded officially (using LG Bridge) to Oreo one month ago, I think. Everything worked at the time: my bank account, Pokémon GO (which uses SafetyNet) and every single application that depends on device certifications.
Recently, after seeing so many posts about the new ThinQ features, the bright camera mode and the rename, I decided to flash the CIS firmware using LGUP and UPPERCUT to make the G6 detectable by LGUP. No problems, SafetyNet was indeed working at the time (attested using Pokémon GO).
After some time w/out using the device, I decided to go back and use it. Yesterday, I tried to open my bank application and it failed several times with the same error code. I thought that it was some kinda of problem with my account, but then I realized that SafetyNet problems actually does the same things when the CTS profile mismatchs or something else prevents SafetyNet to be attested.
With that in mind, I decided to install a "SafetyNet checker" and see what was actually going on. Boom. SafetyNet failing multiple times. It says my device doesn't support SafetyNet (which is a lie, IMO). Initially, my thoughts were that, upon flashing the CIS firmware, something broke and SafetyNet end up broke. Tried to flash the last SEA firmware, no luck. Tried to revert back to the original SEA Oreo firmware (which I flashed the CIS firmware on top), no luck at all.
Apart from my bank application, Pokémon GO and any application that eventually uses SafetyNet for security checking, everything else works. I just don't know what happened with this, as I don't know if my device is still "official" or a red bright light was powered during the flash process (which, IMHO, I doubt, otherwise I'd have seen this on the start).
At this point, I think I'm stuck into this unless a bootloader unlock comes along sometime (this is not impossible, but let's keep hoping for now) and Magisk + its modules are activated in order to hide SafetyNet approval.
TL;DR:
- My phone is failing on every SafetyNet test and I just don't know why;
- It runs official firmware. However, it went through LGUP flashes 2-3 times now;
- There are no root or bootloader unlock methods to this specific model, so there were no unofficial modifications whatsoever;
- The problem started recently, as the SafetyNet depended applications seemed to work after the first flash;
- The first flash actually changed the region (SEA>CIS), so I just don't know if this is the real problem or this is just an unfortunate coincidence;
- I just reverted the phone to its normal region (SEA), and it keeps failing;
- According to multiple SafetyNet checkers, it just says it's uncompatible and tells something about an empty payload. Neither the CTS profile is available;
- Just in case, if someone wonders about the versions I've used until now, the order of the flashing process is:
SEA Nougat -> SEA Oreo (LG Bridge) -> CIS Oreo (LGUP+UPPERCUT) -> SEA Oreo (20C/LGUP+UPPERCUT) -> SEA Oreo (20A/LGUP+UPPERCUT)
If this problem is also happening with someone, or happened to someone else and eventually had a fix, please show the way. If you had the problem, please answer the questions below:
- Have you ever used LGUP with this device? If yes, which firmware did you flash?
- There was a region/carrier change? (eg.: SEA -> CIS, CIS -> EUR, TIM BRAZIL -> BRA and so on)
- SafetyNet dependents were working after the flash?
- Did you wipe your device after the flash? (if you've answered "yes" to the first question).
Thanks in advance.
Mr. I.
(PS: this is NOT a thread to ask for a bootloader unlock. Please don't answer this just to ask for a solution to this. Thanks!)
Hello, as you all can see I have the T-Mobile version of this phone. I have tried everything and I cant get the device rooted. I bought this phone unlocked from Amazon and I use it on Mint Mobile. I have no idea how or even if it effects the rooting process but, I cant think of any reason why none of the methods I've used dont work. I have tried using the "All In One Tool" and the same thing happens with that tool, that happens with every method I've tried; I can use a cmd window to boot into fastboot but, once I am there none of the commands I enter seem to have any effect. I can explain more but, has anyone experienced this or knows what the problem is?
All the info you need is right here:
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Assuming your phone has been SIM/carrier unlocked by T-Mobile, you then need to request an unlock token from OnePlus. All info in above thread
But I highly highly highly recommend making a backup of your persist partition using the MSM tool before even unlocking the bootloader