Related
LG is most likely developing the Android 6.0 Marshmallow operating system and may release it for its G3 and G4 flagships via an over-the-air (OTA) update, in the coming weeks. Although the update schedule is yet to be revealed.
The company's Korean support site has listed the Android 6.0 Marshmallow update for some variants of the LG G3 and LG G4 flagships, which include the LG G3 F400S, F400K and F400L as well as the LG G4 F500S, F500K and F500L. All these variants are currently running on Android Lollipop operating system.
Click to expand...
Click to collapse
View full post here: http://www.ibtimes.co.uk/android-6-0-marshmallow-update-lg-g3-g4-likely-be-released-soon-1522322
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
I'm guessing this will mean a new root method will be required?
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Also a 6 month+ wait for Telstra to do their "testing". Unless we can simply flash it the way we do now with locked bootloaders and injecting root.
I'm excited for the camera app from the V10 being ported over!!
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
I'm hoping that it'll only be a couple weeks before MM is released to the G4, but I'd be happy if it's before the new year. It would make sense to have it out before Xmas so people might buy the G4 as a gift.
I guess not too many of the general public are going to care/know about the latest release of android, whereas people do want something that can handle iOS 9 or whatever version they're on now.
Here's hoping for a fairly quick release and a screen saturation control!
Amazed at how much the price of the G4 has dropped. I bought mine for £360 three weeks ago and it's dropped another £42 since! Probably £299 by Xmas. Why bother waiting for a One Plus/Nexus etc.?
bustervic said:
I'm excited for the camera app from the V10 being ported over!!
Click to expand...
Click to collapse
+1
It is inevitable i believe because both phones use identical sensors...
frnkly said:
I hope it has better power managment..battery gets warm to hot with some apps and lag is still a problem on non rooted phone..
Click to expand...
Click to collapse
+1
We should get much better battery life, especially in stand-by. But i'm hoping for beter power managment
while in use and a better optimised cpu governor... Lag shoulden't be a problem in MM...
daglesj said:
Here's hoping for a fairly quick release and a screen saturation control!
Click to expand...
Click to collapse
+1
That would be great...
I'm wondering how long it will take Big Red to push this out.
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
Well said, it's a big if... But nevertheless, someone will find out the way to root, someone always does
About the MM release, i believe it will be out around the new year, probbably in early january :fingers-crossed:
Knowbody42 said:
I'm guessing this will mean a new root method will be required?
Click to expand...
Click to collapse
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
karendar said:
Possibly, but at the same time, possibly not.
The current low effort root method actually uses a bootloader exploit which COULD not be patched by the new version (This is a BIG IF). If this is the case, we'd be able to use the same exact method as before to inject root.
---------- Post added at 05:57 PM ---------- Previous post was at 05:46 PM ----------
Also, don't want to be a party pooper, but LG promised the Lollipop release "Soon" last year and ended up taking a long time to release it through most vendors... So I don't trust LG on that front.
Click to expand...
Click to collapse
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
djkinetic said:
The M update will be hell for root on bootloader locked devices....Lets assume they close the initial exploit used in Low Effort Root, that means a new exploit must be found (which certainly is possible but will take time). The problem is right now you can't root on M without a custom kernel, the stock M kernel doesnt play nice with SuperSU (causes bootloops), also by default M restricts read/write access to the system partition even with root. So again a custom kernel is needed to defeat these. If you have a bootloader locked device its going to be very difficult to root your device on M. Hopefully the devs can find something but if you need root best move on to a bootloader unlockable device/variant.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
M will likely require a new bootstack, guaranteed that LG patches the backdoor, i'd be very surprised if they left it open. Even if you inject the current SU binary/SuperSU it doesnt play nicely with a stock compiled M kernel, causes bootloops on Nexus Devices, so that means you need a custom kernel unless Chainfire can figure out how to make it work with the default M kernel.
Click to expand...
Click to collapse
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
karendar said:
I'm not really worried about a root method for M... There will be a method by the time M comes out for our phone.
The current exploit, I'd also be surprised if they didn't patch it(as I mentioned) , but then again, I've seen exploits not be patched by major versions, so it's not impossible. Only a release will tell us.
Click to expand...
Click to collapse
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
biff6789 said:
I'm not as optimistic as you. Yes, the exploit we used to root may still be open (after all, they left it open on the G3 -> G4). But a new problem is present: Starting with Android 6.0 all kernels now use a forceencrypt flag. Even all Nexus users have had to flash a custom kernel which flips the flag to noforceencrypt before they could root - that was never the case in the past and Nexus users could just flash SuperSU on the stock kernel and be done with it. Not anymore. Google is locking things down in the interest of security.
You can try it yourself if you have a Nexus. Flash SuperSU on the stock 6.0 kernel. You'll bootloop as the kernel won't allow the system to boot while SuperSU is installed. Only way to root is to flash a custom kernel with the proper modifications to allow root.
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. No kernel flashing = no way to flip noforceencrypt in the kernel = no root on M Sure, you can maybe find a way to get SuperSU and the root binaries in there, but when you try to boot you'll just bootloop as the system won't let you in.
Maybe a workaround will be found, but this new kernel security is a seriously blow to our ability to attain root on the G4 running M.
Click to expand...
Click to collapse
Yea with the current changes that Google made with M at the kernel level bootloader locked devices have very little hope of being rooted, the reason why we can still root on nexus devices is because our bootloaders are unlockable you take that away and we would be in the same boat, this release of android has pretty much signaled the end of me buying any carrier phones that i know will be locked down. its simply too much hassle for most devs to bother with finding new exploits in the coming android versions.
Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
Man. Sweet.
Sent from my LG-H811 using Tapatalk
Rydah805 said:
I'd say it's coming as the T-Mobile support page says it's in testing/already developed. (And that's a US Carrier variant)
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Sent From My LG G4
Click to expand...
Click to collapse
It does? It looks to me like it says both the g3 and g4 are in Manufacturer Development not testing. The nexus 6 is the only device I see that's in testing. I would be shocked if it comes out before December and I would not be shocked if we don't see it until next year.
biff6789 said:
The reason this is a problem for us G4 users is, since we have locked bootloaders (with the exception of a few international units), we cannot flash custom kernels. .
Click to expand...
Click to collapse
Please, most of the world has unlocked bootloaders.
Mad_Duke said:
Please, most of the world has unlocked bootloaders.
Click to expand...
Click to collapse
Just Europe and T-Mobile USA (AFAIK) at the moment.
The percentage of G4's with unlockable bootloaders is pretty small.
Hope some XDAers are able to get it rooted before it gets patched.
http://www.androidheadlines.com/201...te-available-for-android-root-access-bug.html
This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.
But, can we just load an older build using an auto-loader ?
Artemis-kun said:
This has already been patched and pushed out, BB was actually impressively quick to patch the issue and push out a new update. A few carriers in the US might not yet have signed off on the update, but the vast majority of reports from users say they've gotten this update. I know I have.
Click to expand...
Click to collapse
I haven't.
santimaster2000 said:
But, can we just load an older build using an auto-loader ?
Click to expand...
Click to collapse
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader
Tipika said:
On blackberry 10, when an update fixed security issues, they put the older versions in a blacklist, so you couldn't downgrade with the autoloader
Click to expand...
Click to collapse
This is not BB10, this is Android, and yes, I can downgrade, I've tested it.
can root using this exploit?
A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.
Seeing all those one click root apps i was thinking it was going to be easier to root the priv once an exploit was found
Sent from my Nexus 5X using XDA-Developers mobile app
FrankenDroid said:
A small group of devs wrote a script to get root using this exploit for a few Sony phones. Ive looked through there git and if i understand it correctly then the script should be modifiable to work for the priv but you first need to figure out the physical addresses in the memory for the kernel in order to make it work. I don't know awhole lot about this stuff so correct me if I'm wrong.
Click to expand...
Click to collapse
Could you link me to that post please ?
Boom, right here: https://github.com/dosomder/iovyroot
So does this mean one can downgrade and then root using iovyroot?
Shani Ace said:
So does this mean one can downgrade and then root using iovyroot?
Click to expand...
Click to collapse
Theoretically, yes, you would need to add the absolute kernel addresses of the Priv to the source code, then compile it, but still, you would only get temp root, that's only good for using Titanium Backup and the like.
Ah okay, I understand.
So this root is only temp then? Still hoping something comes out but the community seems very small.
I know this isn't iOS, but i was wondering if Android had something similar to Cydia on iOS. A place where i can find/download new/old(working) tweaks. Updated ones a well.
Any tips appreciated!
Xposed would be the closest thing.
But with that being said, most of the stuff that you would need Cydia for on the iphone can be done natively on android.
MrBigWaffles said:
Xposed would be the closest thing.
But with that being said, most of the stuff that you would need Cydia for on the iphone can be done natively on android.
Click to expand...
Click to collapse
Ahh true. Since android is more "OPEN", then iOS's pain in the ass locked file system. But exposed, i see that on the XDA app. Is that the same thing? Or do i need to download it elsewhere?
AngelIsL33T said:
Ahh true. Since android is more "OPEN", then iOS's pain in the ass locked file system. But exposed, i see that on the XDA app. Is that the same thing? Or do i need to download it elsewhere?
Click to expand...
Click to collapse
Youll need an unlocked bootloader and root.
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
I wouldn't recommend doing this if you're unsure about what you're doing. A stable Xposed is going to be released soon enough according to the devs.
MrBigWaffles said:
Youll need an unlocked bootloader and root.
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
I wouldn't recommend doing this if you're unsure about what you're doing. A stable Xposed is going to be released soon enough according to the devs.
Click to expand...
Click to collapse
Ahh, Im on the snap S8, so locked bL. Guess i'll wait for it to get updated for snap variants.
AngelIsL33T said:
Ahh, Im on the snap S8, so locked bL. Guess i'll wait for it to get updated for snap variants.
Click to expand...
Click to collapse
I recently switched from iOS to Android too, and was looking for the same thing. Xposed is very similar for Phantom and YouTube++ alternatives...
I have it installed on my SM-950U and it works just fine. Look up the new version of Xposed for Android Nougat (7.0 or 7.1) (it should be on XDA) by PurifyOS. The official download links for the frameworks are down, but if you go to page 241 or something someone has them reupped. Flash the framework .zip through FlashFire on your phone after rooting, and then install the .apk in the post.
And... voila! You're done! You should have Xposed working on your version of Nougat (7.0 or 7.1)
Hope this helps
iamnotexisting said:
I recently switched from iOS to Android too, and was looking for the same thing. Xposed is very similar for Phantom and YouTube++ alternatives...
I have it installed on my SM-950U and it works just fine. Look up the new version of Xposed for Android Nougat (7.0 or 7.1) (it should be on XDA) by PurifyOS. The official download links for the frameworks are down, but if you go to page 241 or something someone has them reupped. Flash the framework .zip through FlashFire on your phone after rooting, and then install the .apk in the post.
And... voila! You're done! You should have Xposed working on your version of Nougat (7.0 or 7.1)
Hope this helps
Click to expand...
Click to collapse
When flashing in flashwire , do I select mount read/write?
Edit: nvm I got it. But when I try to install xposed thru the installer, it fails system update and goes to recovery
AngelIsL33T said:
When flashing in flashwire , do I select mount read/write?
Edit: nvm I got it. But when I try to install xposed thru the installer, it fails system update and goes to recovery
Click to expand...
Click to collapse
Yeah, you should mount as r/w. What s8 model do you have?
MrBigWaffles said:
Xposed would be the closest thing.
But with that being said, most of the stuff that you would need Cydia for on the iphone can be done natively on android.
Click to expand...
Click to collapse
I'm quiet disagree with ya,
stock Android without unlocked bootloader and root is almost as bad as ios !!
iamnotexisting said:
Yeah, you should mount as r/w. What s8 model do you have?
Click to expand...
Click to collapse
Regular s8. But the xda app has a exposed section with tweaks. I guess that'll work correct?
Any thoughts as to whether Oreo will affect the already unlocked bootloader on mu US997, and whether TWRP (probably Melina) will be flashable and root attainable? And since I am rooted and somewhat debloated I assume I will need to get back to full stock via Bridge in order to take the OTA until and unless one of our great developers creates a flashable version?
This all assumes the sandwich cookie actually does fall from the sky someday here in the US.
Thanks
Tool Belt said:
Any thoughts as to whether Oreo will affect the already unlocked bootloader on mu US997, and whether TWRP (probably Melina) will be flashable and root attainable? And since I am rooted and somewhat debloated I assume I will need to get back to full stock via Bridge in order to take the OTA until and unless one of our great developers creates a flashable version?
This all assumes the sandwich cookie actually does fall from the sky someday here in the US.
Thanks
Click to expand...
Click to collapse
An unlocked bootloader remains unlocked until you lock it, it has never been done trough updates.
Zefie already told that it should be ok, twrp, as root, added compatibility with Oreo ages ago xD
Killua96 said:
An unlocked bootloader remains unlocked until you lock it, it has never been done trough updates.
Zefie already told that it should be ok, twrp, as root, added compatibility with Oreo ages ago xD
Click to expand...
Click to collapse
Excellent, thanks.
Got a message from Google Pay saying that my phone is rooted or is running uncertified software.
I have a T-Mobile variant that I converted , without root, to international. Anyone else see this issue?
Read. This is an old problem for years. Is your bootloader unlocked? Not rooted? Yes this breaks GPay. Hence, Magisk, root, systemless and Hide.
Easy fix.
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
coolmaster121 said:
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
Click to expand...
Click to collapse
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
plasmamax1 said:
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
Click to expand...
Click to collapse
Thanks for the suggestion.
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
coolmaster121 said:
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
Click to expand...
Click to collapse
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
p51d007 said:
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
Click to expand...
Click to collapse
It was a zip I downloaded and did a local update.
Caltinpla said:
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Click to expand...
Click to collapse
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
Yep
No, works fine. But I don't have a converted variant - all stock.
If you go back to stock as it is with T-variant (search for MSM tool), is it certified again?
https://forum.xda-developers.com/showpost.php?p=80844361&postcount=7
noideas4thisname said:
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
Click to expand...
Click to collapse
Nope, I tried everything I heard of but nothing worked. Hopefully, OP releases an update with the fix soon!