Related
Do you think we will ever get something like towelroot for the 5X?
After 5 years of unlocking, messing with bootloaders, kernels, and roms I'm tired. I just want to enjoy my nexus. All I really want is root.
Thanks in advance for your thoughts.
I guess not.
It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk
thesoldier said:
It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
My understanding is that the OP wants root without having to flash all the images, and ROMs, to keep the phone up to date. OTAs are convenient and don't require much effort other than hitting "Reboot now" and waiting a minute or two. Flashing ROMs, right now, means that you have to download the whole ROM with the latest updates and security patches, boot into recovery, flash the ROM and whatever kernel or gapps you need, and then reboot.
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.
daver68 said:
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.
Click to expand...
Click to collapse
This is my situation as well. Especially now that Android security updates should be coming out on a monthly basis, I'm reluctant to give up the convenience of an OTA to get my security patches without needing to flash anything.
OTA updates will fail even if you are on stock and just rooted. I think chainfire is testing a root method that will allow you to take ota's because it doesn't modify the system partition.
This is a nexus device.. Something like towel root is not needed.. Just unlock the bootloader, boot (not flash) recovery and flash supersu..then you have stock just rooted..
Root methods like towel root etc.. Are mostly made for devices where you can't unlock the bootloader.. This is a nexus for Pete sake...It's not needed.. Unlocking the bootloader and rooting is easy enough in nexus devices..
Sent from my Nexus 5X using Tapatalk
Hey, I opened my new nexus 5x a couple days ago and it's been running great. However, I came from an htc one m7 that was rooted and had greenify auto hibernation thing. So, I sorta feel like rooting just for the greenify auto hibernation feature.
The reason why I don't feel like rooting this is because I spend too much time on upgrading (to new versions of a rom, and having to redownload everything over). Do you guys think it's worth rooting? How do you deal with updates of a rom?
If I root, I would just stick to one rom (the most stable one and wait for updates on that I guess, since updates to a rom don't require clean install of rom)
Like you I came from rooted M7 (running ARHD) . I did not even unlock the bootloader on my 5X.. and am quite satisfied.
Either way, you should unlock your bootloader. It is far easier to resolve any issues with your bootloader unlocked.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Either way, you should unlock your bootloader. It is far easier to resolve any issues with your bootloader unlocked.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not to mention, unlocking requires a complete wipe... Might as well get that out of the way
Sent from my Nexus 5X using Tapatalk
so wait, unlock bootloader, as in I should root my phone?
Unlocking bootloader just unlocks it, it doesn't do anything other.
You can decide then if you want to root or not, but it would be wise to unlock it anyway if you ever change your mind because your phone is completely wiped when you unlock it, so it better be the first thing you do with your phone...
You can use the guide here to unlock it
https://developers.google.com/android/nexus/images?hl=en
If you do decide to root, to upgrade to a new version you just flash it manually without wiping your data, so you don't need to reinstall anything. And after that just re-root, and that's it...
As mentioned above as long as you stick with one rom you dont need to wipe internal storage with each update (usually data, system and cache) if that and reinstall su as current versions of superuser dont modify the the system partition.
Root gives more freedom with your phone easy backups with titanium and potentially better battery life or a rom more suited to your needs.
Sent from my Nexus 5X using Tapatalk
The_Automator said:
As mentioned above as long as you stick with one rom you dont need to wipe internal storage with each update (usually data, system and cache) if that and reinstall su as current versions of superuser dont modify the the system partition.
Root gives more freedom with your phone easy backups with titanium and potentially better battery life or a rom more suited to your needs.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh ok. I went to check out the Nexus 5x Android development thread and saw the stock rom of the new 6.0.1 update. But then, i saw someone on the comments asking if they had to flash the radios or something on post #5: http://forum.xda-developers.com/nexus-5x/development/rom-nexus-5x-stock-rom-t3267096
and the guy said, "Yeah, you need the bootloader, radio, vendor images. It's probably easier to just flash 6.0.1 from here https://developers.google.com/androi...mages#bullhead"
so everytime a new version comes out of stock, i need to flash the bootloader, radio, and vendor images?
What if I'm not on stock rom and on a custom rom, then everything will be included in the rom zip file i assume (i just flash the rom, and that's it)?
theBhav007 said:
Oh ok. I went to check out the Nexus 5x Android development thread and saw the stock rom of the new 6.0.1 update. But then, i saw someone on the comments asking if they had to flash the radios or something on post #5: http://forum.xda-developers.com/nexus-5x/development/rom-nexus-5x-stock-rom-t3267096
and the guy said, "Yeah, you need the bootloader, radio, vendor images. It's probably easier to just flash 6.0.1 from here https://developers.google.com/androi...mages#bullhead"
so everytime a new version comes out of stock, i need to flash the bootloader, radio, and vendor images?
What if I'm not on stock rom and on a custom rom, then everything will be included in the rom zip file i assume (i just flash the rom, and that's it)?
Click to expand...
Click to collapse
Custom roms usually dont include radio vendor or bootloader these are flashed from fastboot as opposed to recovery. Custom roms from what I understand mostly modify the system partition. Each thread for the roma tends to have great support. Im currently on uber rom
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Custom roms usually dont include radio vendor or bootloader these are flashed from fastboot as opposed to recovery. Custom roms from what I understand mostly modify the system partition. Each thread for the roma tends to have great support. Im currently on uber rom
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
you can use Nexus root toolkit. all with one click, only what I don't like is the message that appears "we can't control if your device is corrupt".
Is there anybody who know how to prevent that message?
Rooting with this is a piece of cake.
I unroot my new nexus 5 because of the message.
Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?
The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk
How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk
Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.
There's a ton of conflicting info on the interwebs about "how to root" the htc one m8.
I've got an unlocked UK HTC One m8 running the most up to date MM at the moment.
I've just unlocked the bootloader (via HTCDev and ADB) and now I want to root it and then update to use Android Revolution HD rom.
What's the best method? I'm guessing I just flash TWRP and then Flash SU and then Flash the ROM?
Can someone confirm and confirm the correct files I should be using and where to get them... there's so many different places/info
Any help please? :good:
This belong in Q&A, I'll ask the mods to move it.
You don't need to root before flashing a custom ROM, unlocked bootloader and custom recovery is enough.
Flash current TWRP 3.0.2 using fastboot. Then put the ROM on the phone, and flash it.
Okay, that last bit is a bit over-simplified. Before flashing the ROM, you should do a few things: You should make a backup in TWRP of your stock ROM, so you can easily revert if anything goes wrong with the ROM flash (and just good to have a backup of the stock ROM). Backup any data you want to keep, with you method of choice (copy to PC, Titanium backup, cloud, etc.). Then do a default Wipe in TWRP, then flash the ROM.
After the ROM is installed, it will already have root. No need to do anything separate for root. If you were just trying to run the stock ROM, but with root; the proper process would be unlock bootloader, TWRP 3.0.2, and current stable SuperSU (2.78 at the moment).
Super, all done now thanks.
Although I think I'm going to look for a stock droid ROM I just don't get on with sense that much.
Any recommendations? Looking at GPE or CM13 I think.
Cheers
CRNeo said:
Any recommendations? Looking at GPE or CM13 I think.
Click to expand...
Click to collapse
I prefer Sense, so no, I don't have any recommendations.
I'm also not big on ROM recommendations in general. This is a good case in point, as my preference is already different from yours (Sense vs. GPE,AOSP), so what good does my recommendation make? In the time you asked for a recommendation and waited for a response, you could have just flashed one, and tried it yourself for a few hours now. Which is a better path anyway,since only you can device whether you like the ROM or not.
Touché!
And thanks
I will probably do just that and flash this evening and test... I read somewhere about root on GPE being problematic and/or duo camera not working on CM13 guess I'll soon find out!
CRNeo said:
I read somewhere about root on GPE being problematic
Click to expand...
Click to collapse
The ROM installer for the stock GPE ROM in the Development section, lets you pick root when you flash the ROM. It can't be any easier.
Other GPE based custom ROMs are all pre-rooted (as is typical for most all custom ROMs).
Even if stock unrooted GPE, the root process is the same as any other MM ROM for this device (which I already describe in a previous response): Flash current version TWRP 3.0.2 (which you should already have) and flash current stable SuperSU (2.78 at this time).
If you are reading root is problematic for GPE, its probably very outdated info.
CRNeo said:
I read somewhere about duo camera not working on CM13 guess I'll soon find out!
Click to expand...
Click to collapse
Duo camera requires the Sense camera app, and there is no reason to think that Sense features would work on CM13 (which is somewhat obviously missing the Sense framework).
Not positive, but I believe it is possible to install the Sense camera on GPE, since GPE does include the required Sense framework.
Can anyone provide a TWRP file for this tablet
We all gonna appreciate it
有人有twrp吗？我找了好久都没找到能正常使用的
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
PhotonIce said:
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
Click to expand...
Click to collapse
For example if you want to test a few Magisk modules and run into a boot loop ...
PhotonIce said:
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
Click to expand...
Click to collapse
Since when was TWRP specific to flashing ROM only? People use TWRP to perform nandroid backup or for flashing zip files for Magisk modules or whatever. Flashing ROM is just one of the things you can do.
And why would you stick with stock recovery anyway? Having custom recovery like TWRP or FOX is always a good thing, regardless of custom ROM availability or not. People should learn about the fundamentals of a recovery.
chaoscreater said:
Since when was TWRP specific to flashing ROM only? People use TWRP to perform nandroid backup or for flashing zip files for Magisk modules or whatever. Flashing ROM is just one of the things you can do.
And why would you stick with stock recovery anyway? Having custom recovery like TWRP or FOX is always a good thing, regardless of custom ROM availability or not. People should learn about the fundamentals of a recovery.
Click to expand...
Click to collapse
Sorry mate but I am aware of magisk modules and all, that's why I linked a root guide...
Also, on xiaomi devices unlocking the bootloader is a long and tedious process, and the Mi Pad 5 was relatively new when I made my reply, so I didn't want to:
(a) void someone's warranty
(b) encourage them to flash unofficial, untested TWRP (most likely bugged anyways)
(c) brick their device by flashing beta TWRP
Of course, I understand that custom recoveries have many advantages over stock, but at the time of writing my reply, there were no official custom recoveries for this device, and there were only a couple of beta/untested builds.
Cheers!
PS: No one would make a nandroid backup if they weren't going to make modifications to their device (adb/root/magisk), so really, all uses of custom roms stem off of device modifications, which are granted through root access.
EDIT: Sorry I just checked, there were no TWRP builds available at the time of my reply, hence why I provided none and also asked that sarcastic question. At the time, you had to manually patch the boot.img via adb.