Related
Hello everyone,
Right now I have another thread for the root over ADB with DirtySanta, I've that far. I have a potential method but I need more information on it from somebody else so I am waiting on a response from him, once i have that I'll work on it. If you guys have any other potential ideas that'd be great.
Thanks,
Abine45
This is my link to the root on ADB. I will be updating it tonight or tomorrow for the convenience of others. Thanks for waiting.
http://forum.xda-developers.com/verizon-lg-v10/general/temporary-root-adb-t3523538
NEW INFORMATION FOUND! I GOT SIGNIFICANT ROOT ACCESS WITH DIRTYSANTA!!!
SO i used the DirtySanta fearing for my life I wouldn't ruin my device, well the v10 failed it. rebooted and it didn't do anything but reboot back into the normal bootloader and stuff. But what i found is that he go the dirty cow to just work under root, so maybe from there we could do something, anybody have any ideas?
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Haxcid said:
people care but it seems kind of like you expect people who have no clue to do any of this to assist. Hence the reason they are willing to pay a rather large sum of money for a bounty.
1. You cannot repackage a TOT file, well you can but, because it is digitally signed so that the locked boot loader will recognize it and allow it access to image the system. Repacking a rooted version on MM or Nougat will brick the phone if it is not digitally signed by LG.
2. You can pull a copy of the boot image with dirty cow but you can do that from the TOT or KDZ. You cannot put a new one in with dirty cow with out bricking the phone.
3. Most likely not. SELINUX policies combined with updates and fixes have removed most of the previous exploits.
4. Nothing personal but if you are asking us where the boot image resides... that does not inspire anyone here to give you a hand. You need to be in the android devs forum asking these questions.
http://forum.xda-developers.com/android/software-hacking
Click to expand...
Click to collapse
How did Tungkick manage to repackage it then? The dirty cow exploit can exchange recovery though on an unlocked bootloader so shouldn't I be able to replace the boot image if done correctly wouldn't it work? I could possibly unpack everything and modify it all and test it but the issue comes back to repacking and flashing?
Ask him, but if you attempt to do this on a locked and encrypted boot loader then you will brick the phone. I mean think about it, if it was really just that simple every phone would be rooted and rom'd. Most phones running 6 or above have had the security vastly increased to make the phone secure so they can be used by government employees. Hence the introduction to SELINUX polices into the kernel which is why getting root is so unbelievably difficult. The locked boot loader resets everything at boot so getting root and maintaining is so hard combined with SELINUX does not allow standard root to perm. write anything to the system partition and then good old hboot kills anything you did mange to write on reboot... you can start to see how difficult this really is.
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
LG are just not popular devices for hacking due to they make if extremely difficult. LG is a Corp. friendly company it is why Verizon loves them where companies like HTC are a bit more user sympathetic.
Funny you say that
beavis5706 said:
Tungkick did this on 5.1 Lollipop not 6.0 Marshmallow. The above mentioned difficulties with increased SELunix security plus 6.0 and up requires systemless root.
Still would love to know why no dev will go near this Phone. Does XDA have some deal with LG to not hack their phones? Very fishy why every dev avoids this device like it has the plague.
Click to expand...
Click to collapse
Funny you say that! Tungick said to me, and i quote "[email protected]#$g you" and blocked me from Facebook. He also told me that he wouldn't tell me because it's a secret. He didn't speak very great English, that's why there is an ing at the end of the F-bomb. I asked Jcase through XDA and he said he wouldn't and so i put it better explanation of help through an email and he said I was harassing him... In which case before hand he said he doesn't develop for LG because he says basically we are A-holes sadly and that we don't live up to our donation pledges.
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
beavis5706 said:
That's what I'm saying though. It's like no dev will go anywhere near an LG device, at least the newer ones anyway.
They can't be much harder to crack than Samsung and those are getting cracked.
The person who rooted 5.1 on V10 basically tells you to F off. Yeah there is nothing odd about that.
Click to expand...
Click to collapse
True, that's why I'm going to try to do it. If you know anything and want to help could use it.
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
qujuanmiller said:
I just installed Linux on my computer gonna try somethings this weekend... We need to keep in touch
Click to expand...
Click to collapse
For sure, message me on xda.
beavis5706 said:
Wish I could help. All I know here is you need systemless root on 6.0+. This has nothing to do with the v10 in particular. Systemless root should work on all devices 6.0+. It has already been achieved on the Galaxy s7 and it has locked bootloader. I don't see any reason why this can't work on the v10.
Click to expand...
Click to collapse
Anybody can help! Do some research and send it and whatever you would like to do. Try different things, Try to modify bits of code and see what you can do! Always gotta start somewhere!
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
beavis5706 said:
Modify code? You just went way above my head. I know about root, certainly don't know how to achieve it. That's why I count on the folks at XDA. I only have one v10, can't afford to brick it. Plus I already have root on 5.1.1 and I heard that 6.0 causes this phone to have problems.
Many, many v10's were offered up in order to attain root. Not one was taken by any dev. Maybe you can still get your hands on one of those.
You need to find someone that knows about systemless root. Without that you aren't getting anywhere.
Click to expand...
Click to collapse
The thing with that is the fact that even if I know how systemless root works, I still have no way to install it, so first I need to find a way to get in the system.
Think I might have a way though
From what I understand systemless root will modify the boot image to attain root. Super SU will decide how to flash based on firmware version. Will automatically root normal with Lollipop and down, will automatically modify boot image on Marshmallow and up. How you will be able to modify the boot image on a VS990 without bricking it I don't know.
In order to do system less root we need a unlocked bootloader... It says that everywhere I'm reading
Hi abine45,
Please read this post completely, the guys here are close to obtain the perma root on android 6, using dirty cow.
https://github.com/timwr/CVE-2016-5195/issues/9
Sent from my E2006 using Tapatalk
I looked at this thread... a bit more technical than I am able to do... did it end up working? Looks like no, but I might have missed something.
Thanks!
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 guys this guide is for who want to root phone without disabling ota updates.
(BOOTLOODER SHOULD BE UNLOCK)
BIG THANKS FOR MAKING PATCHED BOOT IMg @Jan.Pul
IAM NOT RESPONSIBLE FOR ANY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
1)Download patched boot.img from link below
2)copy that patched boot.img to your adb folder
3) adb debugging should be on and oem unlock should be on for unlock bootlooder
4)turn off your device and go into fastboot mode by pressing holding volume down and power key
5) check whether fastboot detect your device or not by typing this command on (cmd) FASTBOOT DEVICES
6) if fastboot shows that your device is connected your good to go
7) you need to boot into patched boot.img for this type a command FASTBOOT BOOT patched_boot.img your device will boot automatically
8) download magisk manager apk from google and. Open ur magisk manager and install ad direct method and reboot
If you get bootloop dont worry just press your power key for 5sec it will boot automatically
PATCH BOOT IMG : https://drive.google.com/file/d/1cU6qOMiHlGdSAbRtMVgTlHummcGksnt6/view?usp=drivesdk
Guessing this is for the Indian/Chinese version and the bnd-l24 is still sitting on the shelf? And rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Yes..But Why?
maximran said:
maximran said:
this guide is for who want to root phone without disabling ota updates.
(IAM NOT RESPONSIBLE FOR AMY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
Click to expand...
Click to collapse
str8stryk3r said:
rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Click to expand...
Click to collapse
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
RaiderWill said:
maximran said:
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
A Question Sir..
str8stryk3r said:
RaiderWill said:
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
kilroystyx said:
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
Click to expand...
Click to collapse
It will not work
Interesting!
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
Asder.mko said:
str8stryk3r said:
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Well, I got the OTA in December itself but since I had rooted and installed twrp recovery, I wasn't able to install the update.
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Before I went ahead an unlocked my bootloader I checked as many sources as I could about if whether or not I'd still be able ota update and the vast majority of the things I read states that what causes the update to fail is not having stock rom and not having stock recovery. The bootloader being unlocked doesn't modify those or any system files so everything should be fine. Unless Huawei changed things specifically for our Honor 7x then there shouldn't be any problems with ota updates. I guess I'll find out when the L24 people start saying they got updates and I don't receive it or can't install it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well, that's quite right. I don't know whether Huawei/Honor implemented THAT thing, but yeah reverting back to stock conditions wand applying OTA wouldn't be an issue!
( P.S - I'm stuck here too as I have OTA update since December but haven't reverted to stock to install it. I don't yet know properly about manual installation! )
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
iammudd said:
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
Click to expand...
Click to collapse
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
str8stryk3r said:
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
Click to expand...
Click to collapse
No need for full fw broh need vendor partitions, device tree, kernel sources
maximran said:
No need for full fw broh need vendor partitions, device tree, kernel sources
Click to expand...
Click to collapse
Lmao, and that's why I'm not a developer. I just know having the stock image files is important so that when something gets screwed up got have something to fall back on.
Bringing Up The Rear...
Asder.mko said:
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
RaiderWill said:
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
Click to expand...
Click to collapse
People like to root and mod their own devices for their own reasons but you're right, a lot of the reasons I modded past devices was because the roms almost always ran better than stock but the 7x imho runs great. Used to be kernels for better battery life and such. I like custom roms because I like to be able to do certain things that stock roms limited as far as customizing goes. A lot of people hate bloat and end up deleting every file on the phone that isn't necessary or to their liking to make the rom as minimal as possible.
But as of now I'm happy with the phone and don't feel the urge to need to root and and a custom recovery. The roms that eventually come would have to offer something worthwhile to flash. But hell, that's subject to change given how I'm feeling that day lol. There's a new AOSP based rom in another thread that sounds promising
RaiderWill said:
Will Huawei / Honor release a stock image of Nougat and Oreo ? ...
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x..
Click to expand...
Click to collapse
I assume that you already know this ... but I should mention it for others that you can run TWRP (if there is a version for one's phone) without flashing it. (I don't have my 7x yet, so I prob really shouldn't be trying to give detailed instructions anyways.) From there, you can make backups of the stock image, stock recovery, etc. (So thx again to this forum for reminding me that I should backup all stock images as soon as I receive my 7x so that MY fingerprints are not all over the backups.)
As to rooting, there ARE at least 2 things that Huawei hasn't provided without root:
Yes, I can make app backups (and/or use the Huawei "easy transfer"... not sure what app that is at the moment) but I'd assume that I won't be able to transfer it to a non-Huawei device. That's why I continue to use Titanium Backup.
USB Mass Storage Enabling (and by extension Selinux Passive mode). I want fast transfer to my desktop, etc.... and I want a drive-letter (yes, there are Win programs which only work with drive letters). Without UMS, I haven't found a way to do that.
It looks like A10 incremental is now available for Global. Anyone know why/where to get the full update?
With unlocked bootloader and root, incrementals won't work.
I may need to lock my bootloader and no longer root to be able to stay in the latest...
maamdroid said:
It looks like A10 incremental is now available for Global. Anyone know why/where to get the full update?
With unlocked bootloader and root, incrementals won't work.
I may need to lock my bootloader and no longer root to be able to stay in the latest...
Click to expand...
Click to collapse
So most people I know aren't rooting phones anymore at the point in time it's kind of pointless there's way too much security against it with almost every phone besides for the Google pixel onepluses was the only company that supported it but now they don't either so if I were you I would in the Google source code for Android the website you can find a flash tool that makes images from your phone's current running images
AkayamiShurui said:
So most people I know aren't rooting phones anymore at the point in time it's kind of pointless there's way too much security against it with almost every phone besides for the Google pixel onepluses was the only company that supported it but now they don't either so if I were you I would in the Google source code for Android the website you can find a flash tool that makes images from your phone's current running images
Click to expand...
Click to collapse
I really like Viper4Android, so root is still valuable for me.
Though, I never heard of this tool you speak of. I will have to look into that! Thanks!
They have more than one, so the problem is they have so much software on their suppository I've spent the last month and a half digging through there and I've only found five things that may do what I need I just haven't had time to try them out but why I still have free time I've been looking into more ways just in case the ones I'm planning on trying but I'm pretty sure I can do it once I actually get to sit down and do it.
maamdroid said:
It looks like A10 incremental is now available for Global. Anyone know why/where to get the full update?
With unlocked bootloader and root, incrementals won't work.
I may need to lock my bootloader and no longer root to be able to stay in the latest...
Click to expand...
Click to collapse
I posted instructions here that I used for the last update. I will be trying them shortly with this latest update.
Root 10T 5G
I've just received today the 10T 5G CPH2415. I unlocked the bootloader in the same way as the Oneplus 10Pro in settigs OEM unlock and ADB Debug. by Powershell: adb devices Adb reboot bootloader fastboot devices fastboot flashing unlock in...
forum.xda-developers.com
Edit: It worked fine, I just updated one of my 10T's. I used boot image from EU A10 update and patched it with Magisk on the phone.
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
2. Is it possible to have paralel apps? Like Island app but no root needed?
3. Is it possible to block bloat installing every update/disable the wizard? (Again, no root)
4. Can you hide/disable every unwanted app or via adb?
5. Hows watching movies on it?
6. Will custom roms exist?
7. Apparently Samsung doesnt use A/B. Is this true?
Korothi said:
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
Click to expand...
Click to collapse
Please clarify on what you're asking. The bootloader comes locked by default. On unlockable devices, it is always possible to relock the bootloader, but you must perform a clean flash of the factory firmware before doing so. Attempting to lock the bootloader on custom firmware will render your device inoperable.
Korothi said:
2. Is it possible to have paralel apps? Like Island app but no root needed?
Click to expand...
Click to collapse
What do you mean by "parallel apps"?
Korothi said:
3. Is it possible to block bloat installing every update/disable the wizard? (Again, no root)
Click to expand...
Click to collapse
No. Root is required to remove bloat.
Korothi said:
4. Can you hide/disable every unwanted app or via adb?
Click to expand...
Click to collapse
Not without root.
Korothi said:
5. Hows watching movies on it?
Click to expand...
Click to collapse
This is a flagship device; I would expect movies would be just fine.
Korothi said:
6. Will custom roms exist?
Click to expand...
Click to collapse
Eventually.
Korothi said:
7. Apparently Samsung doesnt use A/B. Is this true?
Click to expand...
Click to collapse
Yes. Samsung has continued to use the bespoke recovery model. This makes Samsung devices slightly more complicated to flash, but TWRP helps make it easier.
I managed to have a duplicated app (Revolut) setting up the personal area
For social like WhatsApp this feature is integrated and easier.
V0latyle said:
Please clarify on what you're asking. The bootloader comes locked by default. On unlockable devices, it is always possible to relock the bootloader, but you must perform a clean flash of the factory firmware before doing so. Attempting to lock the bootloader on custom firmware will render your device inoperable.
Click to expand...
Click to collapse
Korothi said:
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
Click to expand...
Click to collapse
Worth to mention, Once you unlock bootloader and flash custom binary, you can relock bootloader later after flashing stock firmware first but still it leaves footprint and certain features will be stopped working forever. e.g Samsung Pass and Pay and may be more.
V0latyle said:
No. Root is required to remove bloat.
Click to expand...
Click to collapse
V0latyle said:
Not without root.
Click to expand...
Click to collapse
Yes you can remove, disable unwanted bloatware via ADB commands. Personally I've disabled samsung dex and similiar unwanted programs, removed swiftkey and other bloat....
Klaudas said:
Yes you can remove, disable unwanted bloatware via ADB commands. Personally I've disabled samsung dex and similiar unwanted programs, removed swiftkey and other bloat....
Click to expand...
Click to collapse
Any guide and list of what is safe to remove?
Fl1nt91 said:
Any guide and list of what is safe to remove?
Click to expand...
Click to collapse
There is a guide. Search XDA for this thread "Samsung Galaxy One UI - Optimization Guide". You will find there everything you need to debloat by your needs.
dr.ketan said:
Worth to mention, Once you unlock bootloader and flash custom binary, you can relock bootloader later after flashing stock firmware first but still it leaves footprint and certain features will be stopped working forever. e.g Samsung Pass and Pay and may be more.
Click to expand...
Click to collapse
Safetynet fix will not help?
Also what i meant was not relock state for bootloader. I meant lock. For example MSM tool in oneplus locks bootloader (locks, not relocks)
Also "parallel apps" is a feature where you can setup 2 discords for example. It can be built in or if you have root - island app.
Korothi said:
Safetynet fix will not help?
Also what i meant was not relock state for bootloader. I meant lock. For example MSM tool in oneplus locks bootloader (locks, not relocks)
Also "parallel apps" is a feature where you can setup 2 discords for example. It can be built in or if you have root - island app.
Click to expand...
Click to collapse
I don't understand still between lock and relock
As explained above by @V0latyle default state of device is locked. If you want you can unlock it. But once you unlock and flash custom binary you can never lock again as same state before you unlocked. You can relock bootloader with missing some features forever. Nothing can help to restore said functions.
Samsung have two features which give you dual app
1.Dual Apps
2.Secure folder
With both these utilities you can use same app in two environments. Again not all apps may supported.
dr.ketan said:
I don't understand still between lock and relock
As explained above by @V0latyle default state of device is locked. If you want you can unlock it. But once you unlock and flash custom binary you can never lock again as same state before you unlocked. You can relock bootloader with missing some features forever. Nothing can help to restore said functions.
Click to expand...
Click to collapse
To expand on this: Samsung uses Knox Guard and other features to detect whether custom images have been flashed to the device. If this is true, some apps and functions that depend on Knox status may not work.
This is in contrast to other OEMs such as Google - the Pixel series can be restored to factory stock with a locked bootloader, and there will be no trace of the device ever having been modified.
What you can do, on either stock or custom firmware, as long as you're rooted with Magisk, is use Magisk modules such as Universal SafetyNet Fix to spoof device responses to Play Integrity attestation, as well as "hide" Knox status. However, again, this requires root. Magisk modules cannot be used without Magisk root.
To try to explain this simply:
Stock firmware, never unlocked: Knox OK: secure functions will work.
Stock firmware, locked but previously unlocked, custom firmware never installed including Magisk patch and/or recovery, Knox should be OK.
Stock firmware, locked but previously unlocked with custom firmware, Knox tripped: secure functions will not work.
Stock/custom firmware, unlocked, rooted with Magisk, attestation responses fixed via Magisk module: Knox status should not matter, Android/Google secure functions should work but Samsung apps that depend on Knox may not.
It is not possible to reset Knox status once tripped.
Therefore, if the device has ever been modified, even if it's just a Magisk patch, re-locking the bootloader will not return it to the "pure" factory state. So, if you are wondering whether to unlock the bootloader, understand that once anything is modified, you are committed and there is no way back. If you don't intend on modifying anything, don't unlock.