Related
Rooted XT926 Build is 9.16.6. Updated SuperSu and busybox, but still not working. Getting a write error -11 code, then "unlocked: no" in cmd script. What am I doing wrong? All usual stuff is done ie: debug, unknown etc.
I had that same problem and it turned out to be my USB port on my laptop. It rooted just fine, but when I tried unlocking it wouldn't work. A computer reset and different port worked for me.
Sent from my XT926 using Tapatalk 2
One20One said:
I had that same problem and it turned out to be my USB port on my laptop. It rooted just fine, but when I tried unlocking it wouldn't work. A computer reset and different port worked for me.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the idea! I tried it, but it still did not take. Frustrating mainly because as I read through threads on it, nobody really seems to have any issues. Thanks again!
tigerfaninnc said:
Thanks for the idea! I tried it, but it still did not take. Frustrating mainly because as I read through threads on it, nobody really seems to have any issues. Thanks again!
Click to expand...
Click to collapse
Did you ever update to 9.18.79 then flash back down? Once you update, the exploit is patched and you cannot unlock the bootloader. The -11 is what I was getting when trying to run the exploit.
All,
I already know there is a 'guide' on how to do this, however, that is a manual process that one must perform every time we do a system update, or whatever.
I created a flashable you can flash in recovery that will write the line is it does not exist. I have tested this a few time on my 5x, and it works flawlessly, simple, and easy.
This is only for stock 5x unmodified build.prop file. This MAY work on the 6p but not making any promises on that one.
Also this ONLY modifies the build.prop file only if need be
Best Regards
This is great and all, but do you know if you can add the last extra line in? It's for us Sprint users, the whole put global tether thing.
Sent from my Nexus 5X using Tapatalk
iamterence said:
This is great and all, but do you know if you can add the last extra line in? It's for us Sprint users, the whole put global tether thing.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How about providing that line for me?
carm01 said:
How about providing that line for me?
Click to expand...
Click to collapse
adb shell settings put global tether_dun_required 0
Sent from my Nexus 5X using Tapatalk
iamterence said:
adb shell settings put global tether_dun_required 0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
so its just:
global tether_dun_required 0
Correct with that space in there?
carm01 said:
so its just:
global tether_dun_required 0
Correct with that space in there?
Click to expand...
Click to collapse
Yes, with the space. I don't know if the other half is needed (adb shell settings put) but maybe someone could test it for you? Not me because I already have tethering set up on my phone and will be away from my computer for the rest of this month
Sent from my Nexus 5X using Tapatalk
iamterence said:
Yes, with the space. I don't know if the other half is needed (adb shell settings put) but maybe someone could test it for you? Not me because I already have tethering set up on my phone and will be away from my computer for the rest of this month
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was just reading the following guide:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-unlock-tethering-nexus-5x-t3231301
On page 5 i believe people are stating that this is unnecessary to get tether to work.
I already asked in that thread what that does, because in my testing it does not do anything for wifi tether. I'm still on VZW with grandfathered unlimited plan. I can't say about sprint users. Maybe one will chime in that successfully got it to work and if that line is really needed.
carm01 said:
I was just reading the following guide:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-unlock-tethering-nexus-5x-t3231301
On page 5 i believe people are stating that this is unnecessary to get tether to work.
I already asked in that thread what that does, because in my testing it does not do anything for wifi tether. I'm still on VZW with grandfathered unlimited plan. I can't say about sprint users. Maybe one will chime in that successfully got it to work and if that line is really needed.
Click to expand...
Click to collapse
It is necessary for Sprint users, like me. Maybe have a separate Sprint zip?
Sent from my Nexus 5X using Tapatalk
iamterence said:
It is necessary for Sprint users, like me. Maybe have a separate Sprint zip?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I don't know how to implement that command into a flashable zip file atm. I will have to ask around, most likely tomorrow i will post it in the general section.
I am wondering if that writes to some file, and if so what. I am thinking possibly an xml file.
Maybe one of the XML file within: system\customize ? idk, but it sounds like it would write something somewhere.
If i could examine a sprint rom.zip I might be able to locate it if it has it enabled
carm01 said:
I don't know how to implement that command into a flashable zip file atm. I will have to ask around, most likely tomorrow i will post it in the general section.
I am wondering if that writes to some file, and if so what. I am thinking possibly an xml file.
Maybe one of the XML file within: system\customize ? idk, but it sounds like it would write something somewhere.
If i could examine a sprint rom.zip I might be able to locate it if it has it enabled
Click to expand...
Click to collapse
That's the thing, there are no specific Sprint ROMs. All ROMs are the same, but when it comes to service that's where things get mucky with this. So maybe it is something within a data provision XML or something. Because without that line, yes, tethering is enabled, but it doesn't connect. After that line is implemented, then everything works as normal.
Sent from my Nexus 5X using Tapatalk
Has anyone tried it on T-Mobile?
Where you able to get the zip to work on Sprint? Thanks so much for creating this!
Hello,
I'm trying to figure out how to use this on my nexus 5x. I'm looking over the instructions on the nexus 5x beginner's tutorial, and was wondering how you actually run this script. I've performed the` manual tethering = true` thing before, but i haven't figured out how to use this one. I've restored everything to factory state and the only thing different from OEM is that the Bootloader is unlocked. I've tried to `adb sideload` the zipfile, but i get an error stating "verification failed, installation aborted" error. Thanks a lot for your help guys
carm01 said:
All,
I already know there is a 'guide' on how to do this, however, that is a manual process that one must perform every time we do a system update, or whatever.
I created a flashable you can flash in recovery that will write the line is it does not exist. I have tested this a few time on my 5x, and it works flawlessly, simple, and easy.
This is only for stock 5x unmodified build.prop file. This MAY work on the 6p but not making any promises on that one.
Also this ONLY modifies the build.prop file only if need be
Best Regards
Click to expand...
Click to collapse
kevindtx said:
Hello,
I'm trying to figure out how to use this on my nexus 5x. I'm looking over the instructions on the nexus 5x beginner's tutorial, and was wondering how you actually run this script. I've performed the` manual tethering = true` thing before, but i haven't figured out how to use this one. I've restored everything to factory state and the only thing different from OEM is that the Bootloader is unlocked. I've tried to `adb sideload` the zipfile, but i get an error stating "verification failed, installation aborted" error. Thanks a lot for your help guys
Click to expand...
Click to collapse
If you want to use it, you must enable OEM unlock in developer options, and unlock bootloader in fastboot mode, and flash TWRP.
What actually does this mod?
CNBLACK said:
If you want to use it, you must enable OEM unlock in developer options, and unlock bootloader in fastboot mode, and flash TWRP.
Click to expand...
Click to collapse
Hey CNBLACK,
I believe I did what you've detailed. If it makes sense- this is what i did from completely stock.
1) Unlock USB debugging, and eventually unlock the bootloader
2) Reboot into fastboot mode,
3) fastboot boot TWRP-3.1.~ (whatever the latest build is)
4) adb sideload/install Enable_tether.zip
5) reboot.
The reboot stays on the 4 dot animation screen for 5+ minutes. Should i be waiting longer, or did I make a mistake during the TWRP flashing section? Thanks again for your help!
Update #2: Alright, in order for everything to work, i had to root my phone... So yes, it works for me now
Update: it eventually booted up after doing aforementioned steps. However hotspot will still not work- it still checks for subscription status. I'm running the Android 8.0.0 Security patch level: Sept 5, 2017 Build number: OPR4.170623.006.
kevindtx said:
Hey CNBLACK,
I believe I did what you've detailed. If it makes sense- this is what i did from completely stock.
1) Unlock USB debugging, and eventually unlock the bootloader
2) Reboot into fastboot mode,
3) fastboot boot TWRP-3.1.~ (whatever the latest build is)
4) adb sideload/install Enable_tether.zip
5) reboot.
The reboot stays on the 4 dot animation screen for 5+ minutes. Should i be waiting longer, or did I make a mistake during the TWRP flashing section? Thanks again for your help!
Click to expand...
Click to collapse
---------- Post added at 08:15 PM ---------- Previous post was at 07:48 PM ----------
AFK269 said:
What actually does this mod?
Click to expand...
Click to collapse
This MOD's goal is to enable your nexus 5x to be used as a wifi hotspot without having to pay for the "upgrade" with your wireless provider. Not sure if it's just me, but even with the line
net.tethering.noprovisioning=true
Click to expand...
Click to collapse
in my build.prop, my phone still checks for subscription status, and therefore will not allow me to start a hotspot.
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.
Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^
tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.
Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?
D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.
xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0
I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672
How did the OP pass the cert check and update checks?
TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.
Is a tone working on this at all by chance? Just curious? .aybe point me in the direction of a sick thread or something please and thank you!
Slipknot8Wwe said:
Is a tone working on this at all by chance? !
Click to expand...
Click to collapse
Nope and never will. There probably is a chance right now if a good programmer could cipher through the mechanism by which the pixel 2 fastboot bug is being exploited. The bug more than likely exists on all pixels. Just need to figure out the proper code to send.
Unfortunately it's beyond my skill set.
Sent from my Pixel using Tapatalk
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
b00ster23 said:
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
Click to expand...
Click to collapse
I tried it as well as some xl and 2xl people. It only works on the 2. An assembly language programmer with a debugger might be able to trick the other pixels into thinking they're a 2 and unlock. All I know is a possible way, not the how. I keep typing this in hopes a programmer might see it and give it a shot.
Sent from my Pixel using Tapatalk
b00ster23 said:
Feel free to try the ADB command "fastboot flashing lock_critical" Was going to try it later this afternoon. Know that its working for the Pixel2 on 8.1
Click to expand...
Click to collapse
Ya I've all ready tried it
baknblack said:
I tried it as well as some xl and 2xl people. It only works on the 2. An assembly language programmer with a debugger might be able to trick the other pixels into thinking they're a 2 and unlock. All I know is a possible way, not the how. I keep typing this in hopes a programmer might see it and give it a shot.
Click to expand...
Click to collapse
That's mainly why I posted it to potentially light a fire under someone's ass. I could not imagine that there is not a way.
baknblack said:
Nope and never will. There probably is a chance right now if a good programmer could cipher through the mechanism by which the pixel 2 fastboot bug is being exploited. The bug more than likely exists on all pixels. Just need to figure out the proper code to send.
Unfortunately it's beyond my skill set.
Click to expand...
Click to collapse
Ya same with me. I've tried everything that I can think of and have researched for all past commands for bootloader unlock.
Has anyone else given it a go on this phone yet? So far I think its working pretty well, with only a couple slowdowns.
Has anyone else noticed a bit of a slowdown with wifi? Sometimes I have to kick it over to LTE to login to apps, even though I can run speed tests and things.
Just wanted to see what other people were experiencing with the beta, sorry if this the wrong place for this.
Other than poor "stand by" battery drainage for me, I think it works pretty good.
But, Android Q it's not on Pixel 3A, isn't it?
Xtremeviper said:
But, Android Q it's not on Pixel 3A, isn't it?
Click to expand...
Click to collapse
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Xtremeviper said:
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Click to expand...
Click to collapse
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Hello,
Do you know if Android Q will brings face unlock ?
Even if it's not safe as the finger print sensor
Xtremeviper said:
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Click to expand...
Click to collapse
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
jmtjr278 said:
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
crackedvenom2 said:
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
Click to expand...
Click to collapse
Many Thanks!!! I succeed!
antp121 said:
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Click to expand...
Click to collapse
I've actually been getting the same thing. I also keep having an issue with wifi, I think I'm going go back to pie and see if it's still doing it. I just really like the new gestures and don't wanna give them up lol
I've been running it for a few weeks. Side loaded the OTA as soon as I got the phone. They took down the OTA file but it's posted in this thread. I've had no issues other than a few apps not being comparable yet and there is no working Magisk out for Pixels 3/3a with Q beta.
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
Yes
sd_N said:
Yes
Click to expand...
Click to collapse
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Axe_L_Thief said:
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Click to expand...
Click to collapse
Simply "opting out" of the beta by pressing the button on the web page will not change anything. But as soon as you (download and) install Pie, my guess is that it will erase everything including any esim profiles. When you go from one major release to another - especially a downgrade - the phone is typically going to be wiped completely. It purposefully erases all information to ensure there isn't any conflicts between the two OS versions.
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Sent from my Pixel 3a using Tapatalk
upinsmoke7610 said:
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Click to expand...
Click to collapse
DP4 was pulled iirc. You can still sideload it.
Anybody having any issues with it so far?
Sent from my Pixel 3a using Tapatalk
So far I'm having no issues with the beta, but did anyone else get a small update today? Any idea why?