Develop Bugs

random noob questions...

OK,
1st Hi all and thanks for not bashing my lack of knowledge. I have done many searches and am now more confused than before.
I am comming from a droid X, I did the z4 root on it to get wifi tether working, it was on 2.2.1 I believe. Well it went very good, but I never got a push for an update. Got the new GN on verizon and tried to restore it back to stock, didn't work, so instead of selling it I gave it to my mom. Also, did this on a friends and he did get the update push and lost the root and superuser access.
This story is just so you know I am a complete noob. Other than following someones set by set on using Z4 I have really not done anything and have some questions on my new phone.
1. why would I want to unlock the bootloader?
2. after reading about the wifi hotspot by svtp do I need to root?
3. If i root and/or unlock the bootloader will this stop the updates from google (main reason I bought the phone)?
4. I am not into overclocking or modding but I want to be able to have wifi if I ever need it. That is the only thing I want.
Basically I am looking to unlock the wifi and still get all the google updates, is this possible? As of right now I think buying the svtp app is my best bet, I just don't want an unexpected bill showing up.

ok, still not rooted or unlocked. cannot get svtp to work wifi

Follow this guide --> http://forum.xda-developers.com/showthread.php?t=1382163

re #1: you need to unlock the bootloader to do pretty much anything non standard with your phone.
Since unlocking the bootloader wipes all data on the phone it's a good idea to do it early. You can leave it otherwise stock while you think about it, you can even relock it if you need to return the phone for some reason.
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
hth

Clancy_s said:
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
Click to expand...
Click to collapse
Just to add further to this... not only will custom ROMs stop you from getting OTA updates, having custom recovery (ClockworkMod) will prevent them from applying, even with the stock ROM. If using a stock ROM with custom recovery, you'll need to do the update manually. If you wait until you get the update notification, your phone should have downloaded the update to /cache. You can then use the custom recovery to apply the update. Alternatively, you can look on these forums for someone to post the URL to the OTA update zip file, download it, and flash it manually (this way you don't need to wait until your phone gets the update, you can download it and have it sooner).
In either case, you'll usually need to re-root, as stated. This is easier with a custom recovery, because you should just have to flash superuser immediately after flashing the update, before rebooting.
Until CM9 is stable, I'm running the stock ROM with ClockworkMod recovery. I can download the OTA updates manually and flash them with ClockworkMod then flash superuser and I'm good to go. Custom recovery makes it nice and easy to retain root, as well as the ability to do nandroid backups, etc.

Root without unlocking bootloader someday?

I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta

Why not just unlock? You can always lock it again if you want to return to factory.

^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:

Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.

Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.

sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.

sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).

Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.

Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.

Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail

Questions regarding rooting.

I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 

Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.

Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.

Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.

Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.

You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu

Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.

The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app

Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt

[Q] Android system update.

My question is regarding the system notification that says "system update downloaded" bassicly this update is a February 2016 security patches for Nexus 5X. Now my question is : Is it safe for me to install it ? ( I am rooted ( systemless), have twrp installed while on stock rom), if it isn't then how can I get rid of this notification?

yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work (manual flashing via PC, FlashFire by Chainfire). you should be able to get rid of the notification by long-pressing it (which may disable other notifications as well).

Broken303 said:
yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work (manual flashing via PC, FlashFire by Chainfire). you should be able to get rid of the notification by long-pressing it (which may disable other notifications as well).
Click to expand...
Click to collapse
"yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work"
I am sorry maybe I am having troubles with reading with understanding but can I safely install it or can't I?

wojwem19 said:
"yes, you can safely install it. no you won't be able to without further setup because of the way OTAs work"
I am sorry maybe I am having troubles with reading with understanding but can I safely install it or can't I?
Click to expand...
Click to collapse
sorry, wasn't the best way of explaining it. you are safe to flash it, in the sense that it won't (or shouldn't) mess up your system. the system won't let you though, because in the process of the OTA update your system gets checked for modifications (root, adblockers, xposed...). if that process failes, so does the OTA update process and you get send back to your OS as it was and eventually the notification will pop back up again. therefore if you want to take the update, you have to flash it another way. one way is using your pc, there are even toolkits which automate most of the process and guide you through it (there are some very detailed and useful guides here on the forum, just do a quick search). another option is Chainfires FlashFire (which still has its quirks).

So, can you tell us how to install it via PC or provide the link that explains how to do it? Because the notification in not.center is a bit of annoying. Thanks!

Bottom line: you can not install an OTA if you have modified the system which means if you are rooted or have installed a custom recovery the OTA will fail. Even if you use a PC and use the ADB program, it will fail. There are many ways to update your system to the latest release using fastboot. Searching this forum has spelled out this process countless times. the search bar is your friend.

Problem that I now have is that it restarts to update, then it enters TWRP custom recovery. I flashed back the stock recovery to keep important OTA updates.

Yaz75 said:
the search bar is your friend.
Click to expand...
Click to collapse
exactly, thank you.
just as an example: searching the N5X forum for 'toolkit' leads me to several threads. this is one of those and further leads me here. oh, look, there is even a faq-section there and more specifically several possible solutions using this toolkit alone.
i don't intend to sound mean here, but with quick checks like that you can not only safe yourself some time.

M8s on Marshmallow - systemless root - how?

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 .