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.
Related
So, I have been searching a bit on how to root the Nexus 7 2013. The process I have found seems pretty simple, even for me, as someone who never worked with a Nexus device before.
Unlock bootloader, flash recovery and flash the root.
But the first step, unlock bootloader, has a problem: it wipes all the user data (including SD Card data!!). As the tablet isn't mine (but I was asked to root it), I can't simply just clear all of its data and do the whole process. Thinking of that, I googled a bit on how to root without unlocking bootloader, but I have found nothing (all recent Sony phones, with a few tricks and the right tool, can do that) regarding the 2013 model.
I'm not sure if there is actually no way to do that or my search skills suddenly got horribe... So, the thing is: Is there a way to do that? Root without having to unlock bootloader (and, thus, wiping all data)? Or I have to unlock it?
EDIT: I found this Toolkit, but did a search and nothing regarding that in the 22 pages of the thread...
http://forum.xda-developers.com/showthread.php?t=2389107
Another few questions that I'm lost: I still haven't quite understood why I have to flash the stock ROM back after I do the whole process... So, why?
And, also, what do I lose unlocking bootloader? I mean, the tablet isn't mine (it's from my younger brother), so the easiest, the best, so keeping OTA updates for example are essential. Do I lose it? What else?
It sounds, for me, some silly questions, but I'm still confused... Seems like doing that kind of stuff is easier with my Sony phone. I don't know if it is due me being used to it, but Nexus is sounding to be WAY more hard than everyone keeps saying it is...
Thanks in advance...
Tell them what is going to happen if they want root. Backup as much of their data as you can, then unlock it. You should be able to get most data backed up one way or another.
At the moment you cannot unlock without wiping because the bootloader enforces that. There might be a way to get around that in the future, but not right now.
When you root, use SuperSU v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Versions prior to that had an issue with preventing OTAs from completing.
1.60 may have some other issues with changes to OTA survival mode.
Not sure where you read you had to flash the stock rom, but it isn't necessary.
You don't really "lose" anything by unlocking it. Someone might bypass your lockscreen to get at your data, but there is a big inconvenience factor leaving it locked (because eventually you'll want it unlocked, at which point it become more painful to backup/restore your data), so you'll have to decide if it is worth the tradeoff.
The issues with stuff not working after unlocking don't have to do with the unlock itself. They have to do with folks rooting and then using their root power to install changes, which then start breaking things.
If you just install SuperSU 1.55 and don't install themes, APM mods, etc. etc. then everything should still work (except apps which specifically won't work, for security reasons, if they detect root)
@sfhub
Thanks for the answers. As I said, I have some Android knowledge, but still got confused with a new "kind" of device. Once again, thanks
I have been on stock almost all my life, but I once thought what could go wrong with having a rooted phone. I unlocked the bootloader, and tried just booting a custom recovery TWRP, and it worked, although it didn't work before as I heard HTC disabled booting recoveries only. Flashed SuperSU, and VOILA!
I installed a couple of applications I wanted to try, first of them was Titanium Backup, and removed a couple of applications like the default "Internet" browser. I also installed greenify and played with it for while.
Yesterday, I tried installing the latest OTA that fixes the Stagefright exploit, and my phone got soft bricked stuck at the booting screen. Thanks to a Nandroid backup I made with TWRP before rooting - or even after rooting I really can't remember -, which I restored, got the OTA normally but wiped my phone.
Here are my questions:
- Does root only change system files?
- If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
- Would greenify with root cause that?
- Is there any official way to restore the stock system files?
I'm just trying to figure out the exact reason here..
@bingorabbit, I can answer 'some' of your questions.
1. Does root only change system files?
I think so, but Someone Else will have to give you a better answer on this one...
2. If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
Absolutely - & this particular OTA is really, really picky. If it's not absolutely untouched stock, it all goes wrong & your phone will hang on the boot screen, as both yours & mine did.
3. Would greenify with root cause that?
Whilst I don't know greenify, if it needs root, then yes, absolutely, your 'stock' will no longer be 'stock', & this OTA will all go horribly wrong...
4. Is there any official way to restore the stock system files?
Absolutely yes. Find out your CID, read up on how to deal with an RUU, find & download the right RUU, then walk a little further down the rabbit hole
JustinSB said:
@bingorabbit, I can answer 'some' of your questions.
1. Does root only change system files?
I think so, but Someone Else will have to give you a better answer on this one...
2. If I removed the default "Internets application that came with the phone after root "uninstalled" it, does this change stock?
Absolutely - & this particular OTA is really, really picky. If it's not absolutely untouched stock, it all goes wrong & your phone will hang on the boot screen, as both yours & mine did.
3. Would greenify with root cause that?
Whilst I don't know greenify, if it needs root, then yes, absolutely, your 'stock' will no longer be 'stock', & this OTA will all go horribly wrong...
4. Is there any official way to restore the stock system files?
Absolutely yes. Find out your CID, read up on how to deal with an RUU, find & download the right RUU, then walk a little further down the rabbit hole
Click to expand...
Click to collapse
I really appreciate your answer, regarding my 4th question, My CID is HTC__J15 but I couldn't find an official RUU for it, only found ones for the developer/unlocked edition on HTC's web site http://www.htc.com/us/support/rom-downloads.html#unlocked if so, should I change my CID to match the developer edition or can I just go on with that one?
Hey,
you can find more RUU and nand backups here : http://forum.xda-developers.com/showthread.php?t=2701376
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
sliding_billy said:
Just wondering if anyone has toggled Enable superuser off and on in SuperSU and whether there were any issues. I have a couple of apps that check for root and will not run if detected. In the past (ran rooted S3s for the past 3.5 years), I have just been able to turn it off to use the apps and then turn it back on with no issues, but like everyone else am still learning the ins and outs of the Pixel. I am running a Verizon Pixel XL and a non-XL (wife's phone). Both are bootloader unlocked and rooted running NDE63P. I have not had time to update to NDE63X or install TWRP yet, not that any of hat matter to the original question.
Click to expand...
Click to collapse
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
pcriz said:
Are you running a custom kernel?
The reason I ask is because I havent tried the method you mentioned but if it turns out it doesnt work for you, I would suggest flashing(reflashing) a custom kernel because that will knock out root, then boot back into the bootloader and boot to root again.
On second thought I think I missed your intent though, Im thinking more in terms of like Snapchat which checks for root only at login (so if you logged in before rooting you will continue to be good after) as opposed to apps that check every time the app is ran. Disregard if this is not helpful.
I want to say the unroot option in the app didn't work but that may have only been for the earlier releases that were pixel compatible.
Click to expand...
Click to collapse
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
sliding_billy said:
Your are correct in your second thought. Not a Snapchat type issue, but a check each time the app runs. FWIW though , not a custom kernel but I laughed at the thought of flashing one and re-rooting each time I needed to run the apps in question
Click to expand...
Click to collapse
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
pcriz said:
I'll say though if that ends up being the path you take, to unroot and root, you should look into TWRP because at least that way you won't need a computer to fastboot the boot-to-root.img, you can just flash the SU zip.
Click to expand...
Click to collapse
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
sliding_billy said:
Oh yeah. I have been using TWRP for many years. Just waiting for the dust to settle a little on the process of getting from where I am now to using TWRP and finding a suitable custom ROM with a current base.
Click to expand...
Click to collapse
I can't see the initial process of loading it changing. Right now there are issues with restoring but if you don't make a back up it won't affect a thing but it will make flashing mods and updates to the TWRP easier.
Aside from using a tool kit, installing it seems to be spot on so long as all the steps are followed.
So once a stable build comes out I will simply flash in the TWRP I currently have.
Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!
I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.
Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!
Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.
So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .
Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .
So I have successfully unlocked my motorola by following the official guide but am stuck on the next step because I don't know what I'm supposed to download next. I installed magisk from the official github onto my phone but that's about it. Thanks in advance for any help.
Which rom are you using?
So all I have done so far is unlocked my bootloader, do I need to download a rom next. I'm very inexperienced on this subject and saw a video of the different cool customizations you can do with a rooted phone.
So, there are two different things.
1. rooting gives you access to system files, so they can be modified/erased etc.
2. a custom ROM doesn't necessarily give you root access, but it can give you cool customizations built-in, or a newer version of Android, for example.
Personally I'm not a big fan of rooting in general. Because that comes with a couple of caveats. One being that your banking apps won't work anymore, unless you fiddle with magisk stuff to make it show like the device is not rooted, and stuff like that. I don't need root, so I don't generally need Magisk either.
But if you want to try a cool ROM for this phone, and you like stock Android, you could try the Pixel Experience ROM. The only thing that doesn't work (and I don't know how to fix right now), is VoLTE and VoWIFI. But it might work for you.
LineageOS works for VoLTE (with IMS APN added by the user), but still doesn't work for VoWIFI. It could be that it requires a few specific files to be flashed from the stock ROM. I don't know. So far I couldn't get it to work.
So, next step would be either staying on stock ROM, and fiddling with Magisk (but keep in mind some DRM apps won't work, some payment stuff won't work and so on so forth), ooor go flash a custom ROM (such as Pixel Experience), and enjoy it the way it is.
The choice is yours.
One advice I have: don't relock the bootloader unless the option in Developer Options > OEM Unlocking is ON. Doesn't matter if it's greyed out or not. But it needs to be ON.
Why? Because, if something happens and you can't boot because you locked your bootloader on a custom ROM for example (which you should never do, by the way), you won't be able to unlock it again, so you can fix your boot, if that option is OFF. So be very careful with that.
When that option is ON, it means bootloader is allowed to be unlocked (it's unlockable). When it's OFF, it's not. If it's not unlockable, you can't unlock it, so you can't flash anything. Which is really bad if you need to fix something and the only way is flashing.
Ok, I took some time to reflect based on what you said. I really do value being able to use banking apps so i guess I will try to fiddle with magisk stuff after I root my device. Speaking of which I was following this guide and I went through the procedure twice but for some reason after I ran the root checker plus app from the play store it says that root was not properly installed. Not sure what part of the process I did wrong but I await any feedback.
Technically, all you need is Magisk installed. That will also give you root access. You don't need anything else.
But maybe flashing was not done right? I don't know. Do you get an error? If so, it would be good to know which error.