If I root? - Nexus 7 (2013) Q&A

Will I lose the ability to get the 4.4 ota update when available?

If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.

Are you sure? lol.
Well if you lose root, you can always re-root?
Are you rooted and have a custom recovery?

REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
Custom recovery is fine (from the standpoint of the OTA verification check). Custom kernel will cause OTA to fail, as would any changes/modifications/removals to/from /system (ie the ROM)

To root I need an unlocked bootloader?

SysAdmNj said:
To root I need an unlocked bootloader?
Click to expand...
Click to collapse
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.

Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...

sfhub said:
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.
Click to expand...
Click to collapse
Wish I knew this before I installed all my apps lol. Its easy to unroot and lock back up in case?
alpine101 said:
Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...
Click to expand...
Click to collapse
You mean 4.3 is fine with you? Battery life and performance?

Or just wait until your current Custom ROM gets updated to the 4.4, and then flash with that newly created ROM. Boom. 4.4.

I just got this yesterday and I like it so far, reading on it isnt bad. Even at night, some apps have night mode etc. I dont feel like rooting/unlocking just yet, let alone custom rom'ming, until I'm sure I'm keeping it. Would like to hear the nexus 10 announcement but honestly the size of the nexus 7 is comfortable to carry around. The weight is good, and it kind of fits it in my old nexus 7 rubber case. If I do keep it, definitely looking forward to 4.4 custom roms and a better fitting case.

REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?

I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
REDFOCZ said:
I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whats your primary use for your n7?

Web browsing, video watching, and reading magazine's.

Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
SysAdmNj said:
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
Click to expand...
Click to collapse
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.

sfhub said:
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.
Click to expand...
Click to collapse
Thanks for the explanation. I think I'm just going for it as I didnt see any announcements of the nexus 5 or kit kat, let alone nexus 10 I'll just keep my nexus 7 2013. I did more reading on this device the past two days then I've done on my previous nexus 7 and nexus 10 tabs. In other words I like it, good enough to keep. Comfy size, weight etc. Now to find the best rom for battery life with a kernel that would let me double tap to wake

Related

Help for a somewhat new person.

I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?

[Q] Keeping Root with OTA Update

As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Gbcue said:
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Click to expand...
Click to collapse
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
phazerorg said:
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
Click to expand...
Click to collapse
Even with stock recovery this is possible? I don't want to re-root and lose data.
Gbcue said:
Even with stock recovery this is possible? I don't want to re-root and lose data.
Click to expand...
Click to collapse
Not with stock recovery. But if you have an unlocked bootloader it's still no problem. You can boot to a custom recovery without even having to actually flash it if you want to keep stock recovery. So you just let the OTA install as normal then use fastboot to boot CWM or TWRP and flash SuperSU and you're done and rooted.
If your bootloader is unlocked, you might as well take advantage of it even if you want to remain mostly stock
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
madd0g said:
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
Click to expand...
Click to collapse
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
phazerorg said:
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
Click to expand...
Click to collapse
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Questions in the Q&A, this is the general forum..
Read the rules sticky..
Beamed from my Maguro.
GldRush98 said:
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Click to expand...
Click to collapse
SuperSU 1.43 update
add3421 said:
So is there a like guide on how to keep root when doing a system update? I have STOCK 4.2 Rooted and it is saying I should download an update. I do have TWRP installed. Is there another stock already rooted 4.3 I can download? Any help would be great so I dont have to factory reset.
Thanks!
Click to expand...
Click to collapse
Why even bother with this crap, flash the update, boot, flash custom recovery after and flash new SuperSU. You would be done before even typing this post.
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
If I have CMW Touch recovery can I install the OTA? I have received the notification but I don't know if I will be able to install it. Is there any way to revert back to Google's recovery just like installing a custom recovery? I mean not loosing data or having to so a factory reset.
Enviado desde mi Galaxy Nexus
str355 said:
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
AMKhatri said:
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
Click to expand...
Click to collapse
Which version of the toolkit?
krackers said:
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
Click to expand...
Click to collapse
This is the command you want "fastboot boot twrp.img"
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
add3421 said:
ok cool, do you happen to have a link to the exact update i can download? for some reason when i click install it says restarting now.. but never does.
Click to expand...
Click to collapse
I used the link in this thread --> http://forum.xda-developers.com/showthread.php?t=2377390
SuperSU.zip from here (v1.45 now) --> http://forum.xda-developers.com/showthread.php?t=1538053
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 after running update.
FWIW: Even though I've successfully used this kit a dozen times on four different devices, root was not working correctly (no su binary found) for me so I had to load the app via twrp which did correctly load from the toolkit after the kit installed 4.3.
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 and it worked perfectly for me

SuperSU and Stock Recovery

is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
You need a custom recovery (TWRP or CWM).
bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.
BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.
ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....
bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.
ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"

Root and update OTA?

Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?
ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.
ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.
santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.
jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.
jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them

So when are we going to get us some custom ROMS, already?

Just picked up this bodacious device and I AM FIENDING FOR SOME CUSTOM WAREZ.
Just got my phone and haven't found the firmware yet to even root the device. Give it some time. Might be more difficult on Android 10 as well. At the least we should have root and some basic mods soon. I gotta do a bit of research though before I start devolping and feel comfortable releasing anything. Been over 5 years since I've don't anything with a phone so I'm excited to get into it too man! Just gotta be patient so we don't end up with $300 bricks
I Rooted my Moto G Stylus today with Magisk using the Patched Boot Image method!
It won't let me post the link's here cause I'm a new member but just search on Google for Stock Firmware for Moto G Stylus and it will come up the website you want is getdroidtips. Also for information on how to Root using Magisk and using the Patched Boot Image method search in Google for Magisk Patched Boot Image you want to go to the website that says Installation Magisk GitHub Pages.
JoshPhillySportsFan1 said:
It won't let me post the link's here cause I'm a new member but just search on Google for Stock Firmware for Moto G Stylus and it will come up the website you want is getdroidtips. Also for information on how to Root using Magisk and using the Patched Boot Image method search in Google for Magisk Patched Boot Image you want to go to the website that says Installation Magisk GitHub Pages.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/
The frmware matches the phone I bought at Best Buy.
mrbubs3 said:
Just picked up this bodacious device and I AM FIENDING FOR SOME CUSTOM WAREZ.
Click to expand...
Click to collapse
Doubt any ROMs will appear.at least there is a way to root. But as far as ROMs. As long as any new device ships with Android 10 twrp recovery is not supported with it.
Yeah it's sad I really hope someone comes up with another Custom Recovery or I hope someone updates TWRP to work with Android 10 cause TWRP hasn't been updated for a lot of device's in awhile.
---------- Post added at 01:29 AM ---------- Previous post was at 01:16 AM ----------
I'm just happy to have Root for this phone! I'll never buy a Carrier Locked phone again cause you can't Unlock the BootLoader on Carrier phone's so you basically can't Root them if you find a way to Root them your lucky but it's much harder if the BootLoader is locked. Thankfully Magisk make's it much easier to Root unlike in the past when we had to use the SuperSU App plus Magisk is Systemless Root unlike the old SuperSU App so it also make's it much easier to UnRoot and return to Stock.
JoshPhillySportsFan1 said:
Yeah it's sad I really hope someone comes up with another Custom Recovery or I hope someone updates TWRP to work with Android 10 cause TWRP hasn't been updated for a lot of device's in awhile.
---------- Post added at 01:29 AM ---------- Previous post was at 01:16 AM ----------
I'm just happy to have Root for this phone! I'll never buy a Carrier Locked phone again cause you can't Unlock the BootLoader on Carrier phone's so you basically can't Root them if you find a way to Root them your lucky but it's much harder if the BootLoader is locked. Thankfully Magisk make's it much easier to Root unlike in the past when we had to use the SuperSU App plus Magisk is Systemless Root unlike the old SuperSU App so it also make's it much easier to UnRoot and return to Stock.
Click to expand...
Click to collapse
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app
talkingmonkeys said:
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure, but I thought the same thing. I also remember an app called Safestrap that I used on my Droid Bionic because of the same thing. It was kinda like have a dual boot machine.
talkingmonkeys said:
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The bootloader is unlockable, though.
One thing I think would be of value is a kernel with Kcal. Total control over RGB colors and Saturation. My last phone was LCD and with Kcal baked into the kernel and using Color Calibration app or Kernel Adiutor, cranking up the saturation really made a difference. Bland orange color went to vibrant red. I don't care about all the other tweeks to use AKT rpofiles etc. I just want more control over the screen. Keep it simple for less hassle.
Since we can't install a custom recovery, we have whatever magisc modules work, whatever exposed works, and a custom kernel. I think the stock ROM is ok as is. Just wish I could control the color more.
And of course we have to hope the custom launchers can catch up with gestures.
---------- Post added at 05:46 PM ---------- Previous post was at 05:29 PM ----------
Flashify is still in the Play store. It hasn't been updated since 2015. It looks to me like it is an onboard ADB solution. No PC needed. It appears to be using Fastboot, so it may still be compatible. But first you have to be rooted using ADB. Without TWRP, you can only flash .img file. No .zip files. So you can use it to flash a new kernel, but you can do that with ADB.
---------- Post added at 06:01 PM ---------- Previous post was at 05:46 PM ----------
We may not need a custom kernel to get kcal. Found this where someone with a G3 and root added a few files and a script and got color control with the stock kernel. Once I root, I'll give it a try.
https://forum.xda-developers.com/lg-g3/general/color-control-display-stock-kernel-t3309677
bencozzy said:
Best we can do is magisk modules to systemlessly modify the rom for debloating and theming etc.
Luckily we will still be able to use fastboot to change kernels. So we should be able to push this hardware a bit that way.
Click to expand...
Click to collapse
yes but then when the debloat script bricks your phone, how do you recover?
bencozzy said:
Fastboot the factory image of the firmware.
Click to expand...
Click to collapse
I tried running the script to do that from my old moto g6 and failed. Read somewhere that on the moto g stylus you had to adb sideload the stock rom from recovery, but I dont seem to have a stock recovery, and of course TWRP is not available for this phone. Are you saying that you have actually succeeded in fastboot flashing the factory image? If so, could you post exact instructions? Thanks!
You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/
androiddiego said:
You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/
Click to expand...
Click to collapse
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?
fronto said:
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?
Click to expand...
Click to collapse
When you get the NO COMMAND icon, press and hold power, then hit volume up quickly and release. (Don't hold the volume up hardly at all)
You then get into recovery. Stock recovery. The stock firmware has a stock recovery img in it, so you do have a stock recovery.
I got the stock rom
Sent from my moto g stylus using Tapatalk
It was bootstrap
fronto said:
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?
Click to expand...
Click to collapse
androiddiego said:
You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/
Click to expand...
Click to collapse
how do you go about installing the rom/img? using adb and getting error 21 codes with signature verification failed.
is there a custom recovery that you're suppose to use?
androiddiego said:
When you get the NO COMMAND icon, press and hold power, then hit volume up quickly and release. (Don't hold the volume up hardly at all)
You then get into recovery. Stock recovery. The stock firmware has a stock recovery img in it, so you do have a stock recovery.
Click to expand...
Click to collapse
Thank you! This worked!!! Never had a phone before that I had to do that to get to recovery. Android 10 thing? Kinda a pain but it works. Now I feel more secure about going ahead and debloating this phone knowing if I mess it up, I can always re-flash.
Thanks!
EDIT: I am back to thinking this phone is bogus. Stock recovery does not seem very useful. Cannot connect with ADB despite latest ADB and latest Moto USB drivers. Cannot install from SD card either. It wont mount the SD card seemingly no matter what. So, although we do have a stock recovery, there does not seem to be a way to flash the stock rom back it it.
fronto said:
Thank you! This worked!!! Never had a phone before that I had to do that to get to recovery. Android 10 thing? Kinda a pain but it works. Now I feel more secure about going ahead and debloating this phone knowing if I mess it up, I can always re-flash.
Thanks!
EDIT: I am back to thinking this phone is bogus. Stock recovery does not seem very useful. Cannot connect with ADB despite latest ADB and latest Moto USB drivers. Cannot install from SD card either. It wont mount the SD card seemingly no matter what. So, although we do have a stock recovery, there does not seem to be a way to flash the stock rom back it it.
Click to expand...
Click to collapse
What about fastboot? I am curious, because I am leaning on buying this phone.

Categories

Resources