Hi, I just changed the battery on my H930 (Italy) and it's back to life. I kindly wanted to know, starting from the already unlocked Bootloader and from an LG Pie, if there is a custom rom, even if not very recent, without any bugs, which retains all the main functions (in particular Hi-Fi DAC, NFC, photos, Wi-Fi, bluetooth ,etc). Furthermore, I would need to use payments with Google Pay and therefore bypass the related checks. If someone can give me a hand of help ... eternal gratitude!
Stock Pie ROMs have been known to be poorly setup by LG. Since they have discontinued their development, these will not be fixed.
In the USA, custom ROMs don't work with VOLTE or VOWIFI... which is why I always recommend stock for USA phones to retain this capability. I don't know if Italy/Europe has any of these issues.
For these reasons, I have always recommended stock Oreo ROMs here in the USA, as these were the most stable and worked well. I have since left my V30 phone but it still has Oreo on it (and still works). For US users, I often recommend US998 ROMs as these work for most carriers (including international). So I might suggest that one to start.
As for GPay, they have gotten quite advanced with root detection. I would recommend skipping root if you can, of course. If you cannot, then I did use Magisk Hide in the past and it worked for me, but that was a few years ago, so I don't know if that works anymore. I would advise NOT using Xposed, as this was being detected as well... besides which Xposed was causing problems anyway, so I found it was not worth the hassle.
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Yes, just unlocking the bootloader can be part of the detection, even if it's not rooted. You often have to go the next step to root and then use Magisk Hide to make it "safe" from there.
Note, at least on older versions, you had to start with the TWRP install of an older version of Magisk. Once installed, then you can update it (usually) without much problem. I recall doing that myself. I believe the TWRP install required Magisk 18.x, and then I had updated to 20.x. You can check the WTF thread to see what that requires, as those instructions should still be valid.
Another option is relocking the BL, of course.
Also note, I know that at one time I had seen where once you fail the security check, you had to clear data for Google Services or something, and maybe even GPay. Otherwise, it "remembered" that you had failed, and would not recheck. By deleting data, it would force it to recheck, so you may need to do this after doing Magisk Hide. Note that you ay need to hide services as well. Again, I'm saying this based on older info... I don't know if things have changed since then.
clalos33 said:
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Click to expand...
Click to collapse
Yes, unlocking the bootloader will cause the security check to fail because you've broken the front door down. You can now do other things like root and make changes to your phone. They know this, so the assumption is if you unlocked the bootloader you are now attempting to take control of your own phone, and they don't want that.
Thank you again for your helpful suggestions. In consideration that I do not plan to use custom rom I will try to lock the Bootloader
Related
Stock Pixel/Pixel XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.111
Suitable for build(s): August 2019
Suitable for devices(s): Pixel XL (marlin) | Pixel (sailfish)
I compiled the stock kernel for the Pixel/Pixel XL and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post. Older versions can be found HERE.
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL, which is no longer being maintained. Thanks for the inspiration, Sakete!)
Wow. I literally just compiled the patched kernel myself just now. What a ninja! While I'll be running my own, thanks for posting this so I didn't have to
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
iissmart said:
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
Click to expand...
Click to collapse
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Cardflip said:
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
Click to expand...
Click to collapse
Good catch, I didn't look that closely before recompiling but they are indeed the same. Oh well! Maybe I'll start going off of tag names instead of branches...
ipeedalil said:
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Click to expand...
Click to collapse
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
iissmart said:
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
Click to expand...
Click to collapse
I think he's asking for the patch itself to be a flashable zip so he can patch the boot image while it's already compiled and on the phone. Which AFAIK is impossible
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I was thinking the same thing, That K is for the Verizon model. good to know.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I'll look into it tomorrow!
Thank you.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I believe the kernel would still work.
It looks like the same kernel is used among NHG47K, N2G47J, and N2G47E, so my patched one should work for all of them. I'll update the post.
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
bobby janow said:
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
Click to expand...
Click to collapse
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
iissmart said:
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
Click to expand...
Click to collapse
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
bobby janow said:
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
Click to expand...
Click to collapse
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
iissmart said:
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
Click to expand...
Click to collapse
I've seen the term 2FA bandied about. I presume that's what you're talking about regarding the lockout. So to clarify, if you don't have an unlocked bootloader you can't sell the device? That seems weird. How do you get your account off? If I gave the phone to my wife she can't add her account?
I've never lost a device either although I have smashed one of them disastrously. But now I have a lot more stuff on the device including some personal pics and videos, password files, banking app and of course AP. I actually think my reasoning was more of like there is so much hacking and theft going on that rather than take a chance let me see what it's like being locked like normal people. It's hasn't been bad at all so far as I'm sure you know since you're not really modded either. I get the OTA on another slot and while it's updating I can use the device and a simple reboot updates it. But the bigger reason is that I got a Verizon model (Pixel 32gb) for $240 and not the $650 the Google one would have cost. I'm not sorry although I will revisit that once the Pixel 2 is released. Black Friday is your friend. I would even have bought the Google Pixel for $350 if they had a deal but they didn't. With a fully functioning 5X I just couldn't justify the full price.
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
coldconfession13 said:
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
Click to expand...
Click to collapse
After extracting the file I just renamed it to sailfish-image and used that in the command fastboot flash kernel sailfish-image. Flashed fine.
Sent from my Pixel using XDA-Developers Legacy app
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
lixoman100 said:
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
Click to expand...
Click to collapse
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Rowdyy Ronnie said:
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Click to expand...
Click to collapse
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
lixoman100 said:
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
Click to expand...
Click to collapse
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Rowdyy Ronnie said:
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Click to expand...
Click to collapse
Thank you again for all the information :good:
Have a nice day.
Anyone using a Custom Rom on LG V20 & V30 with Root or at least GCAM with or without
So I have a T-mobile LG V20 H918 & H930 that are both still on stock 7.0 Android nougat. I'm trying but to decide if I should root and put a custom Rom on them or at least do GCAM while updating them to the latest Stock ROM? I don't really do much but use them for the usual call,text & pictures.
I do do lots of multi tasking tho and need good battery life with speed/performance. I also like most of the stock things that LG offers such as IR remote on the V20, Second Screen & Floating window on V30. I also use the LG Screen writing stuff and other goodies quite a bit. Question is do I do anything or upgrade to all stock? Please give me your best suggestions? My LG V30 is used in good condition and V20 is mint in box use it maybe once a month or so?
1 Peter 2:16*New Living Translation (NLT)
16*For you are free, yet you are God’s slaves, so don’t use your freedom as an excuse to do evil.
New Living Translation*(NLT)
Sent from my LG-H932 using Tapatalk
I had an H932, and I can't think of any reason not to update it to latest Oreo (20s). I know that there is a thing among V20 users to stay on Nougat, but it definitely doesn't apply to V30. Latest Oreo has been great on V30, I believe all models. And it's easy to roll back to Nougat if you don't like it.
Pie on V30 is more debatable: Some users report problems, while others are fine.
I never updated my H932 to Pie (stayed on Oreo 20s). But my wife did, and she hasn't had any problems.
My H932 died, and I bought two US998 V30+ on eBay to replace it (one as a backup and DAP). Both arrived with Pie, and both work perfectly. I did roll back my primary phone to Oreo because an app I use doesn't run on Pie. So I can compare them directly. And while there are pros and cons to both, I probably prefer Pie by just a bit.
But Oreo vs Nougat? Not even a debate
Edit: Oh and then about root: If you think you want to root, then do it while still on Nougat 10d. Otherwise you'll have to temporarily roll back to 10d later to root. My H932 was rooted, and so is my main US998 (the one on Oreo). But I don't really need it for anything, it's just to have the flexibility. To update past Pie, you'll need root and a custom ROM.
QkTreasures said:
So I have a T-mobile LG V20 H918 & H930 that are both still on stock 7.0 Android nougat. I'm trying but to decide if I should root and put a custom Rom on them or at least do GCAM while updating them to the latest Stock ROM? I don't really do much but use them for the usual call,text & pictures.
Click to expand...
Click to collapse
1) In 4 attempts, this is the only correct place you posted these questions. Q&A section.
2) Your T-Mobile V30 is NOT an "H930". Trust me on that.
3) Late 2017 V30 is much better than 2016 V20.
LG V30/V30+
* 1440P OLED (537 ppi)
* Qi wireless charging
* 3.5mm headset jack
* Quad DAC
* DTS 3D stereo (with root to enable LG libs)
* FM Radio
* IP68 dust/water resistance
* rear camera OIS on normal lens - plus 120 degree wide angle lens
* superfast fingerprint sensor
* 64GB (V30) or 128GB (V30+) internal storage
* microSD port for additional storage
* bootloader unlock and root (all variants)
* no notch
___
Reiterating some of what @TheDannemand said...
Latter stock Oreo is far superior to stock Nougat. Stability, improved and even extra stock Camera features, DTS Surround Sound stereo (needs root to enable that stock firmware feature), etc. Many of those came in last few Oreo releases and are not present in Nougat.
But for T-Mobile H932 you need to temporarily be on Nougat to install TWRP and root. That's where the exploit was found. THEN you can update to newer, better firmware, via TWRP-flashable zip (i.e. stock ROM). Whether you then stay on stock rooted newer firmware (like last Oreo or even Pie) or install an LOS-16 custom ROM, that's your choice.
Read all of post #1 (rooting) and #2 (FAQ):
ROOT Your V30 and Custom ROMs FAQ
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
In post #2, especially read the parts about T-Mobile H932 -- Questions 1 and 4.
Your right it is H932, Also do certain apps not behave right with Root such as Snapchat? Because I plan to give this phone to my 14 yo son in a few days. I just bought a LG V60 last night & waiting for it to ship.
He says he is worried of I root it that Snapchat won't work. Thanks for all your help.
ChazzMatt said:
1) In 4 attempts, this is the only correct place you posted these questions. Q&A section.
2) Your T-Mobile V30 is NOT an "H930". Trust me on that.
3) Late 2017 V30 is much better than 2016 V20.
LG V30/V30+
* 1440P OLED (537 ppi)
* Qi wireless charging
* 3.5mm headset jack
* Quad DAC
* DTS 3D stereo (with root to enable LG libs)
* FM Radio
* IP68 dust/water resistance
* rear camera OIS on normal lens - plus 120 degree wide angle lens
* superfast fingerprint sensor
* 64GB (V30) or 128GB (V30+) internal storage
* microSD port for additional storage
* bootloader unlock and root (all variants)
* no notch
___
Reiterating some of what @TheDannemand said...
Latter stock Oreo is far superior to stock Nougat. Stability, improved and even extra stock Camera features, DTS Surround Sound stereo (needs root to enable that stock firmware feature), etc. Many of those came in last few Oreo releases and are not present in Nougat.
But for T-Mobile H932 you need to temporarily be on Nougat to install TWRP and root. That's where the exploit was found. THEN you can update to newer, better firmware, via TWRP-flashable zip (i.e. stock ROM). Whether you then stay on stock rooted newer firmware (like last Oreo or even Pie) or install an LOS-16 custom ROM, that's your choice.
Read all of post #1 (rooting) and #2 (FAQ):
ROOT Your V30 and Custom ROMs FAQ
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
In post #2, especially read the parts about T-Mobile H932 -- Questions 1 and 4.
Click to expand...
Click to collapse
Sent from my LG-H932 using Tapatalk
QkTreasures said:
Your right it is H932, Also do certain apps not behave right with Root such as Snapchat? Because I plan to give this phone to my 14 yo son in a few days. I just bought a LG V60 last night & waiting for it to ship.
He says he is worried of I root it that Snapchat won't work. Thanks for all your help.
Click to expand...
Click to collapse
Can't answer about Snapchat, as I don't use it -- but he may be thinking about apps (Pokemon, some banking apps) which don't work when then sense bootloader is unlocked, whether you have actual root or not.
Simple solution is to use Magisk Hide, which cloaks your bootloader/root condition from nosy apps. It's part of the Magisk Manager rooting module. You choose which apps you want to remain blind.
This still works on older phones like V30 but I understand Google is defeating it on newer phones.
If you decide not to bootloader unlock and root, you still should update to last Oreo KDZ or the only Pie KDZ.
I'd say just don't root unless you have a use or need for it, and if you have concerns about it affecting certain apps. (Magisk Hide works wonders to conceal root, but I don't believe it can conceal an unlocked bootloader. I could be wrong.)
Rooting is more involved and risky on H932 than other V30 models, so there's that too.
You can always go back and root later. One of the amazing things about V30 is that LG never triggered Anti-Rollback (ARB). So even if you don't root now, you can do it later.
It is great to have the freedom to BE ABLE to root if and when you need it. But stock ROM is pretty great on V30 as far as performance and battery life. There are a few system apps to disable (particularly on H932) but that can be done without root.
One of the greatest benefits of rooting is TWRP backups. LG's built-in backup is a pretty good alternative, including backup of app data and many system settings, although not all settings as with TWRP backup.
Then there's the DTS-X audio effects and equalizer, which I don't personally care for, but which many people like. (I prefer bit-perfect rendering by the Quad DAC. For those who want EQ, UAPP has a well regarded one as in-app purchase, which doesn't require root.)
Rooting while you are still on Nougat will indeed save some time later. But temporarily rolling back to Nougat is only a brief step, and the simplest in the entire root procedure for H932.
TheDannemand said:
(Magisk Hide works wonders to conceal root, but I don't believe it can conceal an unlocked bootloader. I could be wrong.).
Click to expand...
Click to collapse
Magisk can hide unlocked bootloader. Some people had unlocked bootloader but for some strange reason didn't want "root", but Safety net still assumed they were rooted since they have unlocked bootloader. The solution was to go ahead and root with Magisk to hide unlocked bootloader -- or relock bootloader. Don't go halfway.
ChazzMatt said:
Magisk can hide unlocked bootloader. Some people had unlocked bootloader but for some strange reason didn't want "root", but Safety net still assumed they were rooted since they have unlocked bootloader. The solution was to go ahead and root with Magisk to hide unlocked bootloader -- or relock bootloader. Don't go halfway.
Click to expand...
Click to collapse
Very cool. I didn't know Magisk could do that. It really is a remarkable platform and tool.
And yes, that's a good reason not to go halfway, among several.
The only scenario I can think of where unlocking bootloader without actually rooting might make sense, is if a user has just performed a Factory Reset (or got a new phone) and know they want to root someday later; just not now, for whatever reason. Unlocking the bootloader now would then avoid a data wipe later. OK, they would still need a data wipe later in TWRP, but at least they'll have a chance to backup first. This is admittedly a bit hypothetical. But an interesting thought exercise :laugh:
TheDannemand said:
Very cool. I didn't know Magisk could do that. It really is a remarkable platform and tool.
And yes, that's a good reason not to go halfway, among several.
The only scenario I can think of where unlocking bootloader without actually rooting might make sense, is if a user has just performed a Factory Reset (or got a new phone) and know they want to root someday later; just not now, for whatever reason. Unlocking the bootloader now would then avoid a data wipe later. OK, they would still need a data wipe later in TWRP, but at least they'll have a chance to backup first. This is admittedly a bit hypothetical. But an interesting thought exercise :laugh:
Click to expand...
Click to collapse
Yeah, there were a couple of scenarios of unlocked bootloader but not root. In each case, the people seems to have been brainwashed that "root" was potentially evil and they didn't understand it's just like being admin of your own PC vs using your employer's computer that you don't own. Today's smartphones are merely powerful handheld computers which can also make phone calls. Yes, I will be admin of my own computer if possible.
These were the most common situations discussed:
1) Bootloader unlock, install TWRP, root on stock firmware to make changes like enable DTS 3D Surround Sound, permanently debloat "unnecessary" files (almost never a good idea with this particular phone), then quickly remove the powerful, "evil" root before it morally corrupts the phone. But keep the changes it allowed.
2) Bootloader unlock, install TWRP, root to install some magical custom ROM with more features and options. Then quickly remove the powerful, "evil" root. But keep the custom ROM because it was "better" than stock OS. I pointed out that without root, they couldn't make and restore TWRP backups -- thus negating one of the reasons for having custom recovery. Some even asked if they could go back to useless stock recovery, maybe re-lock bootloader but still keep the custom ROM.
Every time I tried to question why they didn't want to keep root, they would say they just didn't but were adamant they did NOT want active root on their phones. But wouldn't explain further. Like they didn't understand having ROOT is a mental philosophy, not a weapon. You will always be RENTING your phone, not OWNING your phone unless you are the admin. Unless you have root.
And in each one of those cases, they would still have unlocked bootloader -- NOT pass Safety Net -- and be accused of having root, while not actually having it. There are some apps that will penalize you if they think you are rooted. Do you own your phone or do they? So you have to hide the root with Magisk.
Having root to do something, then giving it up is like driving a nice car to a lakeside picnic, getting out and flinging the keys into the water. What? You aren't going to want to go home? Or somewhere else at any point in time? Grocery store, home, work... You need to keep those keys.
I pointed out many apps like Titanium Backup require root privileges. I have an Auto Restart app that reboots my phone daily right before I wake up, so I have a fresh phone. Requires root privileges. So, does ClockSync, Recovery Reboot, Root Explorer, Shortcut Master, Wifi Password Viewer, Build Prop Editor, Advanced Power Menu... Root is a awesome tool, not an evil weapon.
When our phones become too locked down I can't root my phone, I will be very sad. Because I will no longer really own my phone.
ChazzMatt said:
When our phones become too locked down I can't root my phone, I will be very sad. Because I will no longer really own my phone.
Click to expand...
Click to collapse
Good points there. As always!
I agree about the ability to root. I'll go a step further and argue (as I have before somewhere on XDA) that root should be an official AOSP feature from Google, to be toggled in fastboot. It would make our phones MORE safe, NOT less, since the dev community would have a shared interest in security and in finding and closing vulnerabilities, instead of hoarding them. We could all spend our time constructively instead of having to defeat security measures and jumping hoops to avoid the pitfalls created by OEMs and carriers.
The real risk are apps that gain root access stealthily (which they'll do regardless of whether you are rooted) not ones that request it formally (triggering a prompt and must be granted by the user).
That said, knowing that I CAN root when I want, is enough to satisfy my urge for freedom. Just like I don't run everything as Administrator on my PC, only occasionally when I need elevated permissions.
So I am comfortable advising people NOT to root until they actually need it. Which may be never: On earlier Android phones, we needed custom ROMs or Exposed modules to fill in big gaps in the OS. V30 stock Oreo and Pie are very complete and efficient ROMs. Sure, I recommend a few tweaks and removing a few trackers and bloatware. But those can be done either with or without root.
So while my main V30 is indeed rooted, I actually don't use it for anything
TheDannemand said:
So I am comfortable advising people NOT to root until they actually need it. Which may be never: On earlier Android phones, we needed custom ROMs or Exposed modules to fill in big gaps in the OS. V30 stock Oreo and Pie are very complete and efficient ROMs. Sure, I recommend a few tweaks and removing a few trackers and bloatware. But those can be done either with or without root.
So while my main V30 is indeed rooted, I actually don't use it for anything
Click to expand...
Click to collapse
Only my V30 phone is rooted. My wife's, mother's, sister's, other family and friends V30/V30+ (10 or 11 total) are not.
I used to do that with other phones for people, even installing Custom ROMs. But I don't have time to maintain/update all those.
So, only mine. I decided they don't "need" it. But I do.
ChazzMatt said:
Can't answer about Snapchat, as I don't use it -- but he may be thinking about apps (Pokemon, some banking apps) which don't work when then sense bootloader is unlocked, whether you have actual root or not.
Simple solution is to use Magisk Hide, which cloaks your bootloader/root condition from nosy apps. It's part of the Magisk Manager rooting module. You choose which apps you want to remain blind.
This still works on older phones like V30 but I understand Google is defeating it on newer phones.
If you decide not to bootloader unlock and root, you still should update to last Oreo KDZ or the only Pie KDZ.
Click to expand...
Click to collapse
Can I just do a over the air update on the v 30?
Sent from my LG-H932 using Tapatalk
QkTreasures said:
Can I just do a over the air update on the v 30?
Click to expand...
Click to collapse
Yes. I just assumed since you were still on inferior Nougat -- vs last Oreo or Pie, that something was preventing your OTA updates from working right.
In which case you would need LG Bridge or LGUP to update firmware.
ChazzMatt said:
Yes. I just assumed since you were still on inferior Nougat -- vs last Oreo or Pie, that something was preventing your OTA updates from working right.
In which case you would need LG Bridge or LGUP to update firmware.
Click to expand...
Click to collapse
Ok well I'll try OTA first
Sent from my LG-H932 using Tapatalk
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Swaziboy said:
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Click to expand...
Click to collapse
Maybe just change your way of thinking and directly think of bypassing safetynet.
jjgvv said:
Maybe just change your way of thinking and directly think of bypassing safetynet.
Click to expand...
Click to collapse
Care to elaborate on that any? From my research bypassing it is increasingly difficult as Google has worked to include more advanced tech in the platform.
Install magisk and activate magisk hide.
Download and install Magisk Hide Props Config module in magisk, use this module to install XZ1 fingerprint.
Hey guys, I just bought my RN10 and am waiting for it to arrive. My plan is to turn it into a DeGoogled phone (Custom ROM + MicroG) to use as a daily driver.
As someone who has no experience doing such a thing, but who has been familiarizing oneself with the topic and keeping up with this thread for a bit; I have a few questions that I was hoping I could get some help with:
1.
Is the 168 Hour waiting time a guarantee, or are there some of you who didn't have to wait that long?
-----
I plan to root the device, to pass SafetyNet, get Aurora Services, get Bromite Webview, maybe install oandbackupx, etc...
2.
What is your experience with Aurora services and Bromite Webview?
Do these (+ magisk and microG) need reinstalling after updates?
What is your preferred backup solution? I plan to back up to an SD card.
-----
I will try out some ROMs at first to see what works best for me, before I settle on one. But I am not sure if I can just use my backups from say CrDroid in DotOS for example.
These are the ROMs I am leaning towards (in order of preference): DotOS, CrDroid, and LOS:
3.
What should I be aware regarding backups when trying these ROMs? Can I use backups in different ROMs? Does it apply to oandbackupx or just TWRP ones of data partition?
Would you say they are stable enough for daily driving? (I am aware there are some minor bugs like video recording - not a problem for me)
-----
I am aware that TWRP is in alpha for the RN10 bc of the A/B partitioning system, and that it will be a long time for a stable version to come out.
Once I set on a ROM, I will wait until a stable version is released before I do updates.
4.
What should I be aware of when using TWRP? (specially this alpha version)
-----
I use Ubuntu in my system, and I wonder what is the best approach to Unlock the Bootloader and install custom ROMs there.
5.
Is anyone in this thread also using Linux? What is your experience?
What do you guys think of XiaomiTool V2? Is it reliable?
Or would you guys recommend doing these procedures via fastboot and adb? (android-tools-fastboot & android-tools-adb)
1.
there is no way around 1 week waiting. if you are unlucky you might have to wait another week. this might happen when you didn't use the phone enough in this week period, or if you reset the mi account.
also, from this unlock faq: https://c.mi.com/thread-2262302-1-0.html
If you're facing "User Portrait Scores Too Low Or Black", please create or use a new Mi Account to unlock.
Click to expand...
Click to collapse
what that means can only be speculated. in worst case this means, if you cover your camera so it is black, or if you have low light conditions in your drawer where to phone lies, or at the moment you press the unlock button, you can't unlock your phone.
or if the front camera can't recognize a face with its AI, so the portrait score is too low, it also might not unlock your phone. or if internet is blocked so it can't send the data home.
imho, this is a privacy nightmare, but there are no details anyware and everybody just seems to accept this insanity.
2.
I don't use aurora services, but webview browser work very well and magisk+microG does work if you get it installed once (this can be tricky because you have to find the right versions and variations that work together). if you choose a ROM that allows signature spoofing it isn't so much trouble, otherwise it gets more tricky. The rest works pretty easy with latest Magisk and MinMicroG (other microG variants I had trouble with).
You always have to reflash: 1) custom 3rd party recovery (like twrp), 2) Kernel, 3) magisk if you flash another ROM. this is always the same on every custom ROM.
3.
nandroid backup and restore is messy with TWRP currently. best way is to do backup with oandbackupX as root and/or a nandroid /data backup without encryption pin. backing up system is useless. in case of restoration install fresh ROM, start it up once for setting up encryption of /data, then restore /data partition.
you can't move /data partition between ROMs, you have to backup your apps with oandbackupX or the like.
nandroid backups on ext. SDCard currently don't work. better make space on your internal memory.
4.
TWRP is currently buggy or features not working correctly. don't expect anything that worked before in non virtual A/B environments to work perfectly fine here. upgrading was always tricky due to A and B slot changes, but thats not all a problem of TWRP but of the ROMs too.
Just read the older posts in the threads of CrDroid and LineageOS and TWRP and you will learn a lot what works and what doesn't work.
5.
Just install a virtual PC with windows 10 and use everything related to Xiaomi software in there. (most things are windows only). you can bridge your usb connected phone to the virtual PC.
There is no need for XiaomiTool V2 if you are on custom ROMs. just use fastboot/adb commands as needed.
1.
I plan to cover the front camera and not register the fingerprint scanner until I get a custom ROM on it. So I will discover if that is the case or not and let you guys know here.
2.
What is the best way to install microg? magisk module or flashing it via TWRP? I am under the impression one can go both ways about it.
having to flash the kernel is news to me. is there any post in this sub that I can read more about it?
3.
Okay, I will stick with oanbackupX for the time being then, and read about nandroid.
And could you further clarify what you mean by SD cards not working? Is it only for backups or at all? Does that apply to oandbackupX?
4. thanks I will read those posts. hopefully a stable is out soon though.
5.
I have a notebook that I am not sure is capable enough of running a Win VM. So i would really prefer to do these things on my Ubuntu install if I can. Plus it would be a peace of mind knowing i have all it needs and I am not dependent on having Windows machines near me should I have an emergency with the phone.
Is there any issue with XiamiTool V2? Would it not work to do the things i am trying to do?
Thanks in advace for your reply, they are very clarifying in getting me started on this!
best of luck with unlocking. hope you won't need another week. remember both cameras are eligible for face recognition and brightness measurement.
the way of installing microG may be different for each variation, ROM and phone (remember virtual A/B devices, read-only system, etc.). best way is to read the official installation manual that the microG variant provides. on virtual A/B devices you flash almost everything in Magisk with magisk-modules so you get a systemless patched system. the only thing you flash in recovery, beside kernels and other recoveries maybe, is actually magisk.
about kernels, just read the threads about the two released kernels so far.
well, you might be lucky if you try running the xiaomi software using wine, but it might not work. blame Xiaomi for not releasing all the wanted tools for all OS's.
for unlocking keep in mind that you don't change your setup, keep the same virtual PC, tool, data, etc. in place and don't change anything, they collect also PC data (os, hardware, ip - keep IP the same on PC and phone while unlocking!) for the unlocking process (also a privacy nightmare).. if you want to mitigate that you have to build much more around it than just a virtual pc, though.
I didn't use Xiaomi Tool so I can't really answer that. I think the software is outdated and it's main purpose is to remove some but not all bloatware on non rooted stock rom devices. you can do everything without that tool.
keep in mind that these are unofficial tools and there are many of them, and there are many fake ones uploaded to sharehosters which might be infected with malware. it's hard to find the right sources (but check the official sticky posts in this forum for links) and if you get all these tools by googling around chances are high you get some modified versions with malware.
I'd recommend doing things manually and learning step-by-step how to do things.
Oh damn, I will definitely cover the back camera after I test it then. Thanks for the heads up.
regarding flashing the kernels, I understand it now. I thought I had to reflash the stock kernel every time. silly me
keep IP the same on PC and phone while unlocking!
Click to expand...
Click to collapse
Do you mean keep the phone connected to the same wifi as the PC during the waiting period? bc otherwise I don't think that is possible at all, given that one must turn off wifi and use carrier data to add the Mi account to device.
I am not sure I understand what you mean :\
And the main purpose of the tool is to unlock bootloaders, install custom ROMs, etc. But you are right, latest version is one year old and I would like to avoid it if I can. Also there are 'official' links to download it from the Github page or the tool website.
I'd recommend doing things manually and learning step-by-step how to do things.
Click to expand...
Click to collapse
I agree with you, I will likely do the bootloader unlock procedure on Windows and then install TWRP via fastboot/adb on my Ubuntu laptop, and move on from there. I believe it is possible to do that much on linux right?
regarding the IP, I have the suspicion that they (xiaomi) rate the IPs that you use and for some they might block the unlocking attempt. VPN, TOR and other proxies might be suspicious to them and they might block them (this is not necessarily true for all VPNs, TOR nodes, regions, etc., though). There should be no problem with your default ISPs IP address however, but you'll let your pants down using them.
First unlocking on your phone has to be with mobile data, but you could also use VPN,Tor,etc. there, thats why I'm saying it. Some people I've talked to went as far as buying burner sims just for the unlocking process because they are afraid of what china does with their data.
there should be no problem at all if you use normal mobile data for phone Mi account and your default ISP ip on the computer with the unlock tool. They just spy monitor your phone for that week (until you delete the crap) and if the score is good you are good to unlock the phone. nobody besides them knows exactly what they do but you get a clue when you read their Terms of Service. if your ip address varies geographically very much in this week it might also look suspicious, or if the ip-range is used for many different unlocks. all that obviously plays a role in the score at the end.
ok, I didn't use any other tool for unlocking the bootloader than the original and official xiaomi unlock tool. all the rest can be done without additional tools.
the only things you might need is actually MiFlash (to reset/reflash factory ROMs), MIFlash unlock for unlocking the bootloader, and the latest fastboot+adb versions for all the rest.
fastboot+adb requires the correct phone drivers to work on windows, it might be the same on linux. if they are also available for linux it should be ok. for fastboot try the official general android drivers provided by google, they might also be available for linux (or are already implemented)
I was planning on getting a burner for this. but given the covid restrictions in where I am at, it is gonna be a hassle.
I think Xiaomi does most of that because of the people who buy their phones from China, unlock them, put a custom rom and resell them. I think I should be in the clear though, I wanna get a custom rom working asap, so I wont try using tor and vpn and risk it.
I really don't plan on reflashing the stock rom ever again, unless I absolutely need to. I think i read that there are some cases where one must reflash the stock rom in between custom rom installs(?), but I hope that it is not the case for me. I only plan to try dotos and crdroid, maybe los.
and I would think there is a way to get the drivers for Linux, given that xiomitool v2 does get drivers from somewhere and its available on Linux. I gotta do some digging here though