Develop Bugs

[Q] From rooted Kitkat to Lollipop

Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks

Walter_White said:
Hi!
My Z1C is rooted, has dualrecovery and is running a stock 4.4.2 (14.3.a.0.757)
I also have a lot of customizations via XPosed.
What would be the easiest way to upgrade to a Lollipop version? Someone suggested I can just upgrade and use towelroot afterwards to regain root, but I could not find any verification of that.
Is it safer to flash a pre-rooted zip and if so can anyone point to a decent source?
Also, will XPosed Framework still be functional on Lollipop? I hear there are so many headachy changes to the security layout that I am not sure of that, but right now I'Äd feel safer with a version that has Stagefright fixed...
Let me know what you think!
Thanks
Click to expand...
Click to collapse
AFAIK, there is currently no 'one click' root for 5.1. There is a thread about a Kingroot-to-Supersu method that I can verify works for 5.0.2. You can root 5.1, but either by fastboot, (requiring unlocked bl), or downgrade method, (which you're already on step 1 with KK). There seems to be varied reports about PRFs, but I'm sure you can find a good one by now. I think the main question is if you're hoping to save app data, Xposed settings, etc., to restore afterwards. If so, I would say it's very iffy. You could try Titanium or something, but I wouldn't be surprised if you get some glitches.
As far as Xposed, it works great on 5.0 or 5.1, and there's new developments coming steadily.
Search Z1c 'general', and 'android development' forums for downloads, etc.

Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.

Walter_White said:
Forgot to mention, BL is unlocked with dualrecovery.
Thanks for your advice so far. Root procedure for 5.1 with unlocked BL is already outlined in a thread here?
And yeah, I agree, trying to save app data / settings is bordering on impossible now, I fear TiBackup has outlived its usefulness when it comes to ROM migration. Spent half of today getting my Z1C apps to Z5C and still not nearly half done.
Damn gremlins.
Click to expand...
Click to collapse
To root with unlocked bl, flash stock ROM w/ Flashtool, then flash this with fastboot -http://forum.xda-developers.com/sony-xperia-z1-compact/general/ub-root-init-d-support-recovery-busybox-t3202799 - done. Then you can install Xposed, custom kernel, etc..

Thanks!
Will try this as soon as I managed to migrate my stuff fully to my new Z5C. Migration without TiBackup is a real PITA

Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated

Walter_White said:
Just making sure, when using your route "flash any stock and then follow up with the mentioned file" it means I can jump straigfht from 4.4.2 into the 5 era? Or Do I have to go to 5 for some compatibility reasons. I recall there was something like this sometime back when there was a major new version.
As far my planned procedure for tmw is:
TWRP backup
CWM backup
TiBackup
copying required stuff to the computer
then flash http://forum.xda-developers.com/son...al/stock-14-6-0-368-ce1-dualrecovery-t3216740 as this seems to be the most recent version including updates of the recoveries, pre-rooting already combined. This saves me the step from bone stock to pre-rooted stock as I would have to make in your suggestion.
Also, I want to as well try to use the DRM Feature Fix Mod (http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672), so I will flash the LP version of that one afterwards.
This should work, or am I missing anything significant? I can very well toss the data, the Z5C is now my main phone,, the Z1C has been given a 2nd life with a new backplate and battery I just put in so I'd hate to brick it.
Please confirm that I have a general idea of what I am doing lol... Using flashtool etc. is known to me but selecting the right ROMs remains a mystery unless you follow XDA daily...
Much appreciated
Click to expand...
Click to collapse
Sorry, not sure if you were responding to me... As far as backing up and restoring data, I can't say for sure what's best, going from kk to lp. If you're going from stock to stock, probably built-in Google backup would do the trick. 3rd party stuff is chancy when switching versions in my experience, but Titanium might do OK. I don't think you can backup any kk data in recovery, then restore it on lp. Maybe someone else can tell you otherwise. As far as root in on lp, with unlocked bl, all you need is to flash stock ROM in flash mode with Flashtool, then flash the IMG I linked. - done.

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

Help with rooting Htc M8 marshmallow

Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help

Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.

redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?

Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.

1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.

Root & Rom Advice from the Ground Up

I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!

If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?

1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.

mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?

jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.

alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?

The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?

Clarification Desired: TWRP and rooting

Hello all, sorry if I've happened to missed the guides.
I've rooted a few phones in the past and installed custom rooms, however, I do so infrequently and every time things change.
I only have a loose grasp of GIS roms, so I'll just let that one slide.
I have the mi A2 lite (obviously) and would like to root it or get a custom room that works well.
I don't mind stock, since it is not bloated.
I installed twrp, upgraded from android 8 to 9, then twrp disappeared.
I've read somewhere that I need to disable encryption for twrp, but maybe that's no longer possible that I'm on Android 9.
If I stay stock, will or will I not be able to continue OTA?
TL;DR: Hoping for a basic guide for how to root. I wouldn't mind custom rom, but stock is fine.
Thanks!

You dont have to install TWRP for root
You could install magisk and get OTA updates