Related
I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta
Why not just unlock? You can always lock it again if you want to return to factory.
^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:
Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.
Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.
Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
Okay, I think I know the answer to this question, so forgive me. Just want to be sure before I go blow $500.
For the Nexus devices, regardless of the carrier, we'll be able to root them and ROM them as well as install new Kernel's because the bootloaders will be unlocked?
If that's correct please say so. If it's only partially correct, please explain it all to me.
Disgruntled Verizon User with a S6 Edge
THANK YOU IN ADVANCE!!!
Yes, its easy as pie.
nexuses are always devs favorites...
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Yes! Though I am not sure about the Pixel C. I am wondering if Google giving products the Pixel name means they lock them down? Sorry, little off topic.
I'm only curious how/if Google has the fingerprint security locked down when it comes to root
shimp208 said:
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Click to expand...
Click to collapse
Thank the sweet, tiny, infant squishy baby Jesus! I have yet to own a nexus phone (fed up with my GS5) and am about to pre order the 5X. I miss getting to try out different roms and such, so i'm really pumped about the 5X. the 6P is just too big of a phone for me i think.
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
owenrg said:
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
Click to expand...
Click to collapse
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
If I unlock bootload, will I have problem with OTA?
shimp208 said:
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
Click to expand...
Click to collapse
Awesome thanks!
Sent from my iPad using Tapatalk
menaceinc said:
If I unlock bootload, will I have problem with OTA?
Click to expand...
Click to collapse
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Thanks, I will just do that, unlocking bootloader. I really missed OTA as my current N5 is rooted.
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
In my experience, installing an OTA over a rooted phone would just kill root and you'd have to root it again, however, installing a custom ROM, the developer usually kills OTA so that all the custom stuff doesn't get jacked up.
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
Rooting will effect the built in method of OTA updates. This is not a problem though. 99% of the time you will have access to the updated via the nexus factory image site before you receive notification of an OTA update on your device. Download the update and extract the boot, bootloader, radio, and system images. Flash via fastboot in bootloader mode and you will update your device without losing data/settings. I believe that you can flash img files with recent TWRP builds also.
To root after update just reboot to TWRP recovery and reboot. You will be prompted to install root before system reboots.
May seem a little overwhelming if its your first nexus device but a lot easier than updating a non nexus rooted Android device.
For more info check out any one of the recent nexus routing guides sticky threads
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
SlyUK said:
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
Click to expand...
Click to collapse
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
metpage said:
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
Click to expand...
Click to collapse
Yes thats true, but I haven't heard of many people who have had problems with Wugfresh and it is a popular method. Everyone is different
I always rooted my Nexus (N4, N5 & N7), but I am not going to root my new upcoming Nexus 5X. Why? It just too much to flash/root since Google will release monthly security updates. Yes, I did use "fastboot flash xxx xxx.img" method. However, I will unlock the bootloader in case I change my mind in the future. With unlocked bootloader, I can always fix phone via flash factory images.
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
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.