I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
No
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
No
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
haha, thought so.
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
ShadowWeasel said:
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
Click to expand...
Click to collapse
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
Digital DJ said:
I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
Click to expand...
Click to collapse
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
Click to expand...
Click to collapse
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about bootloader and root.
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about a unlocked bootloader and root.
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Sent from my Pixel using Tapatalk
baknblack said:
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Click to expand...
Click to collapse
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
ShadowWeasel said:
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
Click to expand...
Click to collapse
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Sent from my Pixel using Tapatalk
baknblack said:
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Click to expand...
Click to collapse
I may check the deep web for some answers
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Nick80835 said:
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Click to expand...
Click to collapse
Don't need to modify the bootloader. Would just need to jump into the fastboot code in the same exact place with the same exact instruction that caused the rogue routine to run on the pixel 2. I would think it would be reasonable to assume the same coding bug that exists on the 2 might also be present in the other pixels. But, we'll never know unless someone with the knowledge were to try it.
Sent from my Pixel using Tapatalk
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Click to expand...
Click to collapse
For the Pixel yes you do. You can't root without an unlocked bootloader
For what it's worth, it is relatively common any more, from what I hear, that an unlocked bootloader is required to root. The VS985 (Verizon) LG G3 was an exception in that the bootloader had an exploit that could be taken advantage of to effectively allow everything that an unlocked bootloader does. The HTC 10 is an exception in that you can just S-OFF and never unlock the bootloader and it's just as good if not better. There are always exceptions - when there are other avenues someone is clever enough to find, but as a rule going the other direction, if you can unlock the bootloader of a device, then you can usually easily root the device. As someone else said, on the Pixel, an unlocked bootloader has always been required to root.
Related
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Jut install SuperSU ZIP using TWRP recovery
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Could you read my post first?
squid2 said:
Your bootloader must be unlocked to use this recovery.
Click to expand...
Click to collapse
unlocking bootloader = voiding warranty.
shawly said:
Could you read my post first?
unlocking bootloader = voiding warranty.
Click to expand...
Click to collapse
If you're worried about voiding the warranty, you're on the wrong site.
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
I used to root in one click in just one method on my previous phone xperia sp but i dont know this phone have any toll which will work or not?
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
zephiK said:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
Click to expand...
Click to collapse
Also this.
Ragarianok said:
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
Click to expand...
Click to collapse
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, I also don't plan on using custom roms, I just want the root features so I can undervolt like I said and IF I could root it permanently without unlocking the bootloader, why not?
I'm not worried, it would just be convenient to have root without losing the warranty, that's it.
As far as I know you may be able to do it search kingroot in Google then download the apk and install it then open in and follow the instructions
shawly said:
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, ...
Click to expand...
Click to collapse
Then leave the device stock ...
If you want the best of both worlds (root & warranty), then go buy a Nexus. Motorola drew a line in the sand as to what they will support, while still empowering owners with the option to unlock the bootloader.
Sent from my MotoG3 using Tapatalk
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Not really. While I've unlocked my previous phones, my new g3 I'm leaving locked for the first year, while the warranty lasts. But this site still has a few helpful stuff.
Ragarianok said:
...You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever...if you're worried about voiding your warranty, you shouldn't be trying to modify your device...
Click to expand...
Click to collapse
He just wants the warranty, but he doesn't care about rooting it because there's not really anything wrong with rooting if you know what you're doing and how to fix it.
Sent from my MotoG3 using XDA Free mobile app
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
And to answer the question; you need to unlock the bootloader to root
Sent from my MotoG3 using XDA Free mobile app
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Jdwright0819 said:
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Click to expand...
Click to collapse
Towelroot is exploiting a bug in the Linux Kernel in order to root a device. This bug was already fixed in June 2014.
On all Kernels with a later build date Towelroot will most likely not work.
For sure it will not work on the Moto G3 with a kernel build date more than one year after this bug was fixed.
Thanks!
shawly said:
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Click to expand...
Click to collapse
It's probably been answered already but those exploits are security flaws with the SE Linux system and so with each release of android these have been patched, by 5.1 these security holes have been fixed and now by locking the bootloader
It's like just locking down and modifications to the system partition so unfortunately you can't root without unlocking, unless you have android versions lower down
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
I have unlocked bootloader and i m on stock recovery amd on stock rom without rooted. Can i install twrp without pc
Are you root yet
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Ankur1 said:
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Click to expand...
Click to collapse
What version of TWRP did you use coz I know there were some bugs on the moto range with TWRP 2.X.
I would completely wipe device using stock recovery, including dalvic/cache/data everything just to be on the safe side, then download the TWRP zip to your computer and flash it on using ADB.
Boot up normally and move the superSU zip from the link to your phones internal storage. Then reboot to TWRP, select install and pick the zip file.
superSU.zip:
http://dl-1.va.us.xda-developers.com/3/6/5/5/4/0/1/BETA-SuperSU-v2.62-3-20151211162651.zip?key=u0OeGV4-4s02KJXqrXJ-gg&ts=1466705675
If you get stuck this might help:
https://motog3.com/unlock-bootloader-install-twrp-root-moto-g3/
No longer works
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Perhaps you can offer wisdom on this? I rooted my Moto G 3rd Gen once, wrecked something and had to go back to factory, then try to reroot again. Problem. No matter what I do in setting the device back to factory, the bootloader stays unlocked and reads the system software as "modified" which then seems to bork installing SuperSU. I install SuperSU via twrp and it goes fine, no errors, but when I reboot the system is lost in a loop of the "bootloader unlocked" screen.
So I cannot RE-lock the bootloader (ala setting the phone back to true factory) and after I flash SuperSU the phone refuses to successfully bootup.
Any aid? Ideas?
I had failed to backup my phone the first time with twrp and so to set to factory I downloaded the stock retail xml.zip for my phone and reflashed the entire thing via fastboot. Reinstall twrp, and try to root and the endless boot loop begins.
So I came to this thread to look into the possibility rooting my phone via another means that MIGHT work.
Just a thread for the few USCC people here - I've tried to UL the bootloader using TMO instructions - no go. It will reboot into the bootloader but it asks for the unlock.bin key (fastboot oem unlock returns an unknown command error). So at least theirs that much
Phone will also boot into recovery, and I get the associated normal options there (clear, mount /system, wide device/cache, load update via ADB, load update via SD, view recovery logs, etc). Interesting thing happens when I select "run graphics test" from the recovery menu - it gives an error, then the "no command" icon, then multicolor circles rotating - but it says "erasing" then "installing system update" then goes back to the recovery menu. Not sure if it's normal, but it's interesting.
I'm not a dev or a software guy really, but would like to hear some thoughts on the USCC version...would love to have root like the TMO - especially since it will get into the fastboot menu. Wish I knew more so I could be more help.
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Killah1994 said:
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Click to expand...
Click to collapse
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
elliwigy said:
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
Click to expand...
Click to collapse
There you go, knew I was getting something mixed up.
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Sent from my LG-US996 using Tapatalk
jayochs said:
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Click to expand...
Click to collapse
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
does he have a copy of the debug kernel? you can pm me a link if possible thatd be great so we can take a look at it.. if it is an eng kernel, it could potentially help to root other variants with locked BLs
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
---------- Post added at 02:41 AM ---------- Previous post was at 02:41 AM ----------
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
hopefully you are able to as it shouldnt really take any time at all lol.. it would really help a lot of ppl out if it is in fact a debug kernel..
the root we have is a temp tcp root shell using a context we cant really do anything we need to do at all so it was pretty much a dead end so far
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
I will pay you for the debug files
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
you wont b doing anything to the phone.. if u have an adb root shell would just be copying a few files from the phone.. we can even tell you exactly what commands to use to make it easy.. we can invite you to a google hangout even so we can explain each step
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
Whay are you asking for the phone?
I was looking to get what I spent for it, around $800
elliwigy said:
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
Click to expand...
Click to collapse
yeah, the US cellular us996. it's different from the American unlocked us996. according to LG anyway, it lists it as two different phones.
I'm not on a US cellular one. I'm in an unlocked one with Verizon. the post above you said unlocked had unlocked bootloader. mines as unlocked as you get, and it doesn't have an unlocked bootloader.
Sent from my LG V20 US996
http://developer.lge.com/community/...nuId=38&contsTypeCode=QUE&prodTypeCode=MOBILE
Make yourselves heard. Let LG know we want the bootloader to be unlockable on the US996. I've talked to their live chat and they claim that they "didn't know people would want to unlock their bootloader". Show them we do.
Abumarf said:
I was looking to get what I spent for it, around $800
Click to expand...
Click to collapse
Ok if you download terminal emulator and type in get prop and send me the screen shots so i can verify it is indeed a debug kernel i will buy it from you but i would like to have proof of debug kernel
Sure, here it is: https://drive.google.com/file/d/0BwI6DTQJV37Ob1BwRkRab0xPRkk/view?usp=drivesdk
Also the phone is already up on Swappa
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
@rickberg forgot to tag you
https://www.xda-developers.com/oneplus-root-access-backdoor/
Is it possible to have something like these be implemented into the s8 qualcomm variants?
Not sure if we can even exploit this in order to unlock bl and install magisk.
S8 and S8+ don't have the EngineerMode system app. Rooting Nougat with bootloader locked Snapdragon S8/S8+ is accomplished via combo firmware bootloader + combo firmware boot image (and recovery.img), and initially via SamPWND or SamFail method. SamFail is quicker & easier than SamPWND. Carrier specific bootloader locked Snapdragon S8/S8+ firmware is not currently rootable due to dm-verity enforced by boot image. Dm-verity is not currently removable in carrier specific locked bootloader Snapdragon S8/S8+ boot images as boot image cannot be modified due to secure boot. I will never buy a phone with bootloader that can't be unlocked again!
jhofseth said:
S8 and S8+ don't have the EngineerMode system app. Rooting Nougat with bootloader locked Snapdragon S8/S8+ is accomplished via combo firmware bootloader + combo firmware boot image, and initially via SamPWND or SamFail method. SamFail is quicker & easier than SamPWND. Carrier specific bootloader locked Snapdragon S8/S8+ firmware is not currently rootable due to dm-verity enforced by boot image. Dm-verity is not currently removable in carrier specific locked bootloader Snapdragon S8/S8+ boot images as boot image cannot be modified due to secure boot. I will never buy a phone with bootloader that can't be unlocked again!
Click to expand...
Click to collapse
I agree...so sad I want to install a custom ROM and can't on my 955U.
"I will never buy a phone with bootloader that can't be unlocked again!"
Agreed!....
I had to learn this lesson the hard way too. I bought two SM-G955U1 devices from B&H Photo Video, Fortunately, I learned this lesson quickly enough to be able to return the devices within the sellers terms.
I am currently waiting on a credit/refund for the devices, and still trying to decide if I am going to give the SM-G955F or FD a chance. My understanding is that they have the option to unlock the bootloader in the developer section... If not, I will probably look at the unlocked LG V30 or the One Plus 5T as a viable replacement phone.
If I only had to pay $50-100USD to obtain the phone, I could understand and deal with all the locked down elements, bloat and marketing feces. but at the prices they are charging for these phones, the answer is not only "NO" but "Hell NO" I am not putting up with with all that crap at that price.
if anyone interested, here is the engineering apk extracted. https://mega.nz/#!UvxAiKpB!gxYRldksa5Jd0xLpRRBkTt3evV2WIUHdHT_aSUqgqpg
012345678 said:
if anyone interested, here is the engineering apk extracted. https://mega.nz/#!UvxAiKpB!gxYRldksa5Jd0xLpRRBkTt3evV2WIUHdHT_aSUqgqpg
Click to expand...
Click to collapse
I wonder if it can be given root privilege's using ADB on a stock phone?
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
012345678 said:
if anyone interested, here is the engineering apk extracted. https://mega.nz/#!UvxAiKpB!gxYRldksa5Jd0xLpRRBkTt3evV2WIUHdHT_aSUqgqpg
Click to expand...
Click to collapse
I wonder if it can be given root privilege's using ADB?
Was wondering because we might be able to boot TWRP to gain root without unlocking the bootloader and replacing recovery but not too sure if the boot sector is re-written for root access...
Even if it worked it doesn't matter.
You can't disable selinux or turn off dm-verity on the stock abl/boot.img/devcfg.mbn
Those are the minimum 3 files you need from the factory images to boot without selinux and dm-verity.
With those 3 files you are at 80% battery.
None of this has anything to do with bootloader security, which has absolutely positively nothing to do with root or your bootloader being unlocked.
Magisk needs an unlocked bootloader to patch the kernel to get around selinux and to patch the root filesystem to start itself up while it still can.
We already have root in two different ways (sampwnd and samfail via jrkruze's ROMs)
[delete]
old_fart said:
I think I got a update patch from sammy and now I am able to charge to 100 percent.
I am not joking...
.
negative thought... was yesterday's update to cover / fix an exploit ?
Click to expand...
Click to collapse
What update or software version are you on also what steps did you take to get 100% charge is it real 100% charge screen shot at 100% charge for proof and rooted right?
---------- Post added at 04:08 AM ---------- Previous post was at 04:06 AM ----------
Davilince said:
https://www.xda-developers.com/oneplus-root-access-backdoor/
Is it possible to have something like these be implemented into the s8 qualcomm variants?
Not sure if we can even exploit this in order to unlock bl and install magisk.
Click to expand...
Click to collapse
Dude s8 well never be rooted perm bl unlock on at&t never. Fact
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.
Why did you relock it in the first place
KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support
I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol
I know I'm probably out of luck here, but I've seen some mention of some kind of "Q method" for unlocking the bootloader so I was curious if I missed something along the way and there's a method to unlock the bootloader that doesn't involve requesting the BL unlock code from T-Mobile/OnePlus?
I'd really like to install TWRP so I can root with magisk and enjoy rooted stock, but requesting that code instantly voids the warranty even if you never use it and this phone hasn't been on the market long enough yet to be certain there aren't some defects that might pop up and I don't want to get stuck paying the insurance deductible for something a warranty request would normally take care of for free.
Again, I know I'm probably asking the impossible, but is there some new method (all forum searches have returned the normal method) to unlock the BL without signaling T-Mobile that I'm being a cheeky monkey?
Unlocking the bootloader can be done without getting a code from OnePlus by converting your T-Mobile device to the international version, but this still requires a SIM unlock (which as far as I know does not void your warranty).
While the second poster is right.....you are also right about the Q method u need dp3 just somewhere around here you could even Google it that's how I found it. Basically use the msm tool to flash international rom (done without root or unlocking bootloader because it's a stock ROM) then u flash "Q" dp3 once done then boot into it go to settings tap build number 7 times to developer settings then you can tap "oem unlock" is fastboot command to unlock the bootloader. Then from there you can pretty much flash back to regular oos android 9 root it etc.... Im sure there is a Guide somewhere. But that is the gist of it
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
Here u go?
Thanks to both of you for answering my question! And it was even the answer I was hoping for! Now I can root my phone and just restore the original Bootloader if I need warranty service, just like the old days!
Hah. And now, while trying to find a way to do this on the OnePlus 9 the top Google result is my own thread for doing it with the OnePlus 7 Pro