Related
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
You have to wait until the guys here find a way for p eople to root once they have 2.2 . That could take anywhere from a few days to a few weeks
Most likely you are NOT going to be able to root since you ran the OTA update for 2.2....
That is why you should read what you are flashing and know the consequences prior to doing so. Every thread that contained the download for the 2.2 leak said that it will make you lose root and the ability ( for now ) to gain root status.
You need to wait until one of the geniuses figure out a way to do it.
Sorry about your luck.
The best way is toast method...
Good luck!
Sent from my PC36100 using XDA App
UND3RTAK3R said:
The best way is toast method...you can email me if you have any problems [email protected]
Good luck!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not gonna work since he used the 2.2 update man.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
1. wrong forum, should be in Q&A
2. if you did the manual update from Sprint, you will have to wait until the devs here create a root method for stock 2.2 is developed. Any existing root method will not work at all.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
You installed the plain OTA update? The one that says "not rooted yet" on the thread title?
For each new update, HTC tries to protect its software from being rooted. The last update required users to exploit a Flash Lite vulnerability and took a while. You will probably have to wait a long time before you can root this, since it doesn't have Flash Lite.
For future reference, root first THEN update to a rooted rom released by our devs. You can't just install Ava's rom on top of stock 2.2, it prevents you from doing so.
I'm sorry but HOW MANY posts were there saying if you want to keep root, DO NOT INSTALL THE UPDATE?? Ugh...
And yes I know this isn't constructive but sometimes people just need a slap on the back if the head.
Sent from my PC36100 using XDA App
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Hours my my day wasted....HOURS!!!
Where's my AR-15
Wow, just wow.
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Here we go again
Sent from my PC36100 using XDA App
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
By digging thru it and finding an exploit.
Which will most likely happen for the 2.2 update as well, just not as of yet.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
xeno314 said:
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
Click to expand...
Click to collapse
Beat me to it and said it better.
bludragon742 said:
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Click to expand...
Click to collapse
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. They showed up before any official sprint OTA. Lets also not forget the hundreds of posts warning people that this would happen.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
The "rooting method" allows you to get into restricted areas of the phone to install stuff. The act of rooting is breaking into the phone itself, not into the rom. The rom itself is fully accessable and can be hacked up, its just getting it onto the phone is the hard part.
Essentially your phone, stock, is a box that's locked from the inside. For older versions people figured out how to unlock it, so that you can put any hacked up rom onto it. The new OTA, no one knows how to get in yet.
Don't know if that makes sense. It's pretty easy to understand if you understand OS permissions.
EDIT: what the other guy said.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
Because someone takes the CONTENT of the update, and applies it piece-by-piece to an already rooted image, ignoring the bits that replace HBOOT and etc.
Mad06STi said:
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. .
Click to expand...
Click to collapse
I'll tell you why. The thread gets to 200 pages. There are people saying it works, sucks, bricks, awesome, hate it, stay away, success, etc. After reading 40 pages of it you have no idea up from down. Speaking from someone that is not familiar with Android rooting. It's frustrating. Then you go to one of the other 50 threads and it's all the same.
I never saw anywhere that if I installed the leak i'd be screwed. I'm fine with that though. I have 2.2 and can wait. Just annoyed i've spent hours of my day on this.
This thread was a funny read.
Sent from my PC36100 using XDA App
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?
douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.
You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse
For me, I had to run Kingoroot from my laptop, and Kingroot never worked.
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.
I used to be more active on these forums before I got my oneplus 5T and one of the biggest reasons was I wanted a clean fast OS without all the bloatware that many other manufacturers put on their phones. I tried a search but I did not find what I was looking for, so I apologize in advance if this is already covered in another thread.
Anyway, I picked up a 5T about a year ago while visiting family in Europe. (I'm the 2nd owner to the phone) I never bothered to install TWRP or anything else bcs the phone was running really well with stock. All OTA updates have been installing whenever they were released.
Now to my question. While trying to install workspace one app from playstore (my company requires it) the app won't install bcs it claims my phone is rooted. That is the only app that I have ever had any issues with.
I ran root check witch states "sorry! Root access is not properly installed on this device"
How do I unroot my phone if it's really rooted? Or lock the bootloader? maybe that's the same? TWRP is not installed, when I boot into recovery I get into oneplus stock recovery software.
Hi, unfortunately I can't tell you right off if your phone is rooted. If root checker is saying no, then maybe you aren't, but still check if you have magisk or some other root solution app installed. When you got it from someone, they also could have flashed ROMs etc and when they returned it to stock for resale, they night have missed something like relocking bootloader, even if they did re install stock recovery. If I were in your shoes though, I would reboot to bootloader and check if it's unlocked or not. If it is, it's a simple "fastboot oem lock" from terminal. If that's not the case or solution, I dunno what to say. One thing that I would do if I were desparate is to try to take a backup of all the music/pics/texts/whatever other essential bits of data. Then I would reinstall stock recovery, as well as the latest official (not beta) Oxygen OS from oneplus's page. You can find it under the support tab and then software upgrade, then choose the device. Not only that but maybe completely nuke it, as in format, wipe, etc. And lock the bootloader and also let it get encrypted and stuff.. in other words, restore to as stock as possible. Then once you are done you can test. If this fails and bricks, there's a unbrick guide somewhere here for our phone, and also the backup is there for you. If you successfully restore to stock and this does not work, then maybe it is just the app that has a problem with not super stock Android (OOS). I must warn you that this process is risky and I am in no way gonna be responsible for lost data, because I did say make a backup and also it is up to you to do this. I hope this helps a bit, and if you aren't super familiar with the process it may take a while, around an hour if you do not run into any hitches and your download speed is good enough.