I spent a little time browsing around, and I didn't seem to find any straight answers anywhere. I just got my Pixel XL on Verizon, running NDE63P.
Is this build number compatible with dePixel8? I'd like to unlock this bootloader and root the phone before I lose all chance to in the future. On top of that, if it is compatible with dePixel8, where would I find a guide to download fastboot and adb? How would I know if it's working properly with my phone?
Please and thank you to anyone that helps me out here. Again, been out of the Android scene since the S4.
Anthony825 said:
I spent a little time browsing around, and I didn't seem to find any straight answers anywhere. I just got my Pixel XL on Verizon, running NDE63P.
Is this build number compatible with dePixel8? I'd like to unlock this bootloader and root the phone before I lose all chance to in the future. On top of that, if it is compatible with dePixel8, where would I find a guide to download fastboot and adb? How would I know if it's working properly with my phone?
Please and thank you to anyone that helps me out here. Again, been out of the Android scene since the S4.
Click to expand...
Click to collapse
It still works to unlock bootloader on verizon pixel. Jcase said google didnt get the fix out in time for Nov security update so its still a go till Dec update. Adb minimal is at link below just updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
Awesome, I just got the bootloader unlocked. In the past with other android phones I've owned I was able to root only due to Verizon's ways. Now that I'm unlocked how would I go about getting SuperSU installed? Or whatever super user program is used for this phone?
Also, it popped up on my phone right before I unlocked it....Is it safe to install 7.1 updates? Will it relock my phone?
Anthony825 said:
Awesome, I just got the bootloader unlocked. In the past with other android phones I've owned I was able to root only due to Verizon's ways. Now that I'm unlocked how would I go about getting SuperSU installed? Or whatever super user program is used for this phone?
Click to expand...
Click to collapse
Root
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------
Anthony825 said:
Also, it popped up on my phone right before I unlocked it....Is it safe to install 7.1 updates? Will it relock my phone?
Click to expand...
Click to collapse
Updates will only affect root currently. I would update before you root but it's completely separate from whether the bootloader is locked or not.
Yea I found the root information and got it rooted last night. This morning I woke up though and realized I was having blue tooth issues which were causing me to lose connection to the Verizon network. Rebooted the phone and all is well.
Pretty self explanatory. I have the update pending for 8.0 but I've heard mixed reviews of the Oreo updates. So please, if anyone can be honest and tell me weather to proceed, or should I wait and why. Thanks you.
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
liriolebron said:
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
Click to expand...
Click to collapse
What's the best way to check if it's Verizon? And I don't need to root or anything honestly. I'm asking if the bugs with 8.0 are worth updating at the current state.
I recommend unlocking bootloader first and then update
So by unlocking the bootloader, I won't run into problems taking official updates?
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
No. If you modify system (root, Magisk, custom ROMs/kernels, TWRP recovery, etc) then you won't be able to take official OTA updates. But you can take them just fine with an unlocked bootloader.
Also, I'm on stock 8.1 and have no issues to speak of. I say go for it.
Sent from my Pixel XL using Tapatalk
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
FYI If phone is a Verizon version an on 7.1.1 you are able to unlock it. If you update beyond 7.1.1 without unlocking you will Never be able to unlock it. If it's a Google version no worries.
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
asj0422 said:
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
Click to expand...
Click to collapse
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Sent from my Pixel XL using Tapatalk
borxnx said:
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Click to expand...
Click to collapse
He's right though. Unlocking will lead to security issues and may take away the ability to use important apps. If he prioritizes functionality, then it's best to keep it locked but if he wants to tinker, it'll come with compromises.
Since he just bought it, I don't see why he couldn't just warranty it if an update goes wrong, which is extremely rare. From what I've seen from people with bricked devices, the majority of them were unlocked and tried to update using non-conventional ways.
Bootloaders are locked from factory for a reason, not for inconvenience.
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Ndmand said:
Hi,
My HTC 10 is rooted, S-On, SU, boot loader unlocked, and running stock Nougat 7.0. As such, it doesn't get onlver the air {OTA}. I want OREO, and I understand that requires me to unroot. How do I unroot?
I hope to do an OTA and then reroot. If I really don't have to unroot, tell me please what to do to get OREO. My main attraction to rooting is to install AdAway.
Thanks,
Ndmand
Click to expand...
Click to collapse
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
bita said:
These are what I did;
1. restore my stock rom via TWRP (which I backed-up long time ago)
2. flash back stock recovery (which I found form XDA). It will replace TWRP
3. OEM relocked
By then, I could get couple OTAs until I reach to Oreo.
After that, I went all the ways again => unlock bootloader (HtcDev) => flash latest TWRP => and so on.
Click to expand...
Click to collapse
Thank You,
This is exactly what I need. I interpret "OEM relocked" to mean that after flashing, you system was relocked, and you didn't have to separately relock your bootloader. I appreciate your help.
Ndmand
Tarima said:
You really only need steps 1 and 2 from bita's post. If you don't have a stock system backup you can probably find one in the Backups thread.
Else, you can flash an ruu which will take you back fully stock but will also wipe your phone in the process.
Click to expand...
Click to collapse
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Ndmand said:
Great, Thank You, Tarima,
Oddly, I was hoping you'd see my post because if the great help you have given to others. I deleted my stock backup by mistake last year.
My TWRP and Titanium backups are on an SD card, so I will remove the card to protect them during the process in case things go crazy.
I noticed that SU has an unroot button, but I guess that only covers part of the process.
Thank You,
Ndmand
Click to expand...
Click to collapse
No problem. Yes, once you root with superSU, your system partition will be flagged permanently as modified even if you unroot. That's why you need to flash a virgin system backup image. This is also why I root with Magisk, as it makes taking OTA much easier. You may want to consider that as well when you root again.
I don't quite understand Magisk yet, but I will look into it. Thanks for making this doable and understandable.
Ndmand
Do a RUU and update ota , no need to relock bootloader, you will lose data if you do RUU
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
oxineitor said:
Which RUU is the right for the Oreo OTA?
I have installed the developer version, but I haven't received it. Also I knew that HTC had removed the OTA
Enviado desde mi HTC 10 mediante Tapatalk
Click to expand...
Click to collapse
U.S Unlocked has not yet received OTA. To go to Oreo you'll have to run the RUU.
Take the RUU posted by santod on this page:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page254
Newbie Here
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Yank1llaz said:
Hi guys,
For several years now I've been getting help from you people and for that I am very appreciative. This is my first, of what I hope are many more posts.
I recently purchased a Sprint HTC 10 phone here in the Dominican Republic. It was factory unlocked already. It came with stock Oreo software. Yesterday I received an Oreo update, and this immediately locked my phone sim. I couldn't use it. Now thanks to you guys, I slept like at 1 am, but finally managed to get the phone unlocked thanks to this thread.
Now I have a problem. I'm not that of a techie guy to leave the phone rooted. Is it wise to unrooted back again? My main concern is, if I unroot the phone it will revert to having the sim lock, and that's a no go. So my question is: Do I unrooted? Can I, without damaging the phone? And if the answer is no, how do I proceed with my rooted phone to get the best out of it? I saw this video on youtube, it seems nice, but it is from 2015. Do I follow those steps or do something else to take advantage of my rooted device.
I would really appreciate your help.
Click to expand...
Click to collapse
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Tarima said:
The only downside to being rooted is that you won't be able to take OTA updates any longer, or use certain apps that don't work with rooted devices (mostly banking apps). I'm almost 100% sure we won't get any more OTA updates for this phone, so unless you really need to use banking apps, I would leave the device rooted. Plus there are some nice things you can do while being rooted.
If you're rooted with Magisk you can still do all of the above.
Click to expand...
Click to collapse
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
andybones said:
I thought you could take OTA?
I am WAY out of the info as I don't take them, but I'll search a little an come back with any findings.
Click to expand...
Click to collapse
Unless you're rooted with Magisk systemless root, you can't take OTA from a rooted state until you restore a stock system image, which I'm thinking might undo the SIM unlock procedure the OP had to do on his Sprint device.
---------- Post added at 02:43 AM ---------- Previous post was at 02:35 AM ----------
Yank1llaz said:
Thx Tarima. If so, what can I do with a rooted device? What are my inmediate options to upgrade the phone. Any ideas?
Click to expand...
Click to collapse
That's what I was saying, there will 99% for sure be no other updates for this phone, so that's a non-issue. And if there is, you can run an RUU, return to stock, take the update, then do the sim unlock procedure again.
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Tarima said:
I do with root:
- Use Titanium Backup (great app backup app)
- Use F.lux app for blue light reduction
- Use Adaway ad blocker
Click to expand...
Click to collapse
Process for those. Sorry for being such a pain in the behind.
Yank1llaz said:
Process for those. Sorry for being such a pain in the behind.
Click to expand...
Click to collapse
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Tarima said:
What do you mean by "process for those"? They're apps, you just install them from the play store
Actually I think Adaway needs to be downloaded from their own site
Click to expand...
Click to collapse
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Yank1llaz said:
Downloaded the one for blue light. How about the adaway one? When dowloading the files within the app, it does not allow me and reads:
"copying of host file failed"
Click to expand...
Click to collapse
Sorry not sure about that, you'll have to ask in the appropriate forum.
Hi. I am about to purchase a Huawei Mate SE and wanted to know if there is a way to root without unlocking the bootloader. It looks like Kingroot and/or Kingoroot might be an option. I'm not new to rooting phones so I understand most of the basics. From what I read, I won't be able to install a custom recovery and therefore can't install custom ROMs which is fine. I mainly want root for apps like Titanium Backup and Greenify. I don't want to lose the ability to OTA. Is this possible? Thanks in advance for the help.
Kingroot and kingoroot are hot piles of garbage on oreo, and nougat. Pretty sure it only works up to lollipop.
Only way to root is to flash Magisk, and that requires an unlocked bootloader.
Dang. That sucks. Thanks for the response though
no need to install a custom recovery to get root. unlockbootloder densest effect ota. after u unlock ur bootloader you can flash a patch kernel that has Magisk
ReppinTheSouth said:
Dang. That sucks. Thanks for the response though
Click to expand...
Click to collapse
I just ordered this phone also. You should be able to get your bootloader unlocked with a service. See threads.
I sure hope so. Cause i plan on doing some stuff with this device.
Unlocking the bootloader is not difficult, but then there is a stupid bootloader unlocked warning that comes every time the phone restarts. And supposedly there is no way to turn it off for Huawei phones
I was given a Pixel 2 XL by a friend, and it had an unlocked bootloader, but I couldn't tell whether or not he tried to root it. And I couldn't use some GPay features, which I'd like to. So to be safe, I went through the process of flashing a stock image using Google's instructions: boot bootloader via ADB, didn't have to unlock my bootloader as it was already unlocked, and then used flash-all with the stock Android 11 image I had downloaded from Google. Didn't re-lock because I still wasn't sure that it was because of the unlocked bootloader that I couldn't use those features, but upon trying to use them I found it that it is. So now I'd like to lock the bootloader, which Google also has instructions for, but I'm concerned because everything I read makes re-locking sound like a toss-up that might end in a bricked phone.
Do I have need to be worried? Some things I read say to do a factory reset before flashing, some say to flash it more than once, before re-locking the bootloader; is that necessary? Should I factory reset before using ADB/Fastboot to re-lock it? Should I re-flash the stock image, just to be paranoid about it? Or was it sufficient the first time, with no need to reset beforehand because locking the bootloader will erase all my user data anyway?
I just really don't want to brick my phone trying to get it back to a normal, stock state.
Download the latest update and install that. Doing that will wipe the phone and remove root. It'll be like taking it off of the box brand new.
BEFORE you relock it, reboot it and make sure it works. Once you're satisfied that it works, then relock it.
Larzzzz82 said:
Download the latest update and install that. Doing that will wipe the phone and remove root. It'll be like taking it off of the box brand new.
BEFORE you relock it, reboot it and make sure it works. Once you're satisfied that it works, then relock it.
Click to expand...
Click to collapse
Awesome, thank you, that worked well for me.
Did you re-lock the bootloader yet? The old problem of no USB ADB/file access is showing up again for me on build RP1A.201005.004, Oct 2020 with Oct 5th security update.
There's a new factory image, RP1A.201005.004.A1, Dec 2020 that I hope is the fix, but I can't install it because my bootloader isn't unlocked and I can't get ADB to connect other than through wireless.
Double check your USB ADB/file transfer before you re-lock and turn off automatic updates.