Related
So the Verizon 4.0.4 Factory Image was just published by Google, so I downloaded it to my phone for safe keeping. I'm just curious, if I install a custom ROM and I want to go back to stock ICS can I just flash this file like a ROM? Also will I loose root if I do that?
This is what I'm talking about.
Yes you loose root and custom recovery.
CM9 kang powered by TRINITY
actually, no... you have to flash it using fastboot commands, flashing image by image:
fastboot flash bootloader bootloaderxxxxx.img
fastboot flash system systemxxxx.img
fastboot flash recovery recoveryxxx.img
etc, etc, etc...
your phone will be exactly like never touched, that means of course, stock with no root or custom recovery.
barbac666 said:
Yes you loose root and custom recovery.
CM9 kang powered by TRINITY
Click to expand...
Click to collapse
thiagodark said:
actually, no... you have to flash it using fastboot commands, flashing image by image:
fastboot flash bootloader bootloaderxxxxx.img
fastboot flash system systemxxxx.img
fastboot flash recovery recoveryxxx.img
etc, etc, etc...
your phone will be exactly like never touched, that means of course, stock with no root or custom recovery.
Click to expand...
Click to collapse
Thank you, so when I rooted my phone it created a recovery image, and that's what I would want to use to go back to "stock + keeping root"
Right?
Yes make a nandroid backup in CWM , and if you want to go back restore this.
In CWM go to backup and restore.
CM9 kang powered by TRINITY
Big Cam said:
Thank you, so when I rooted my phone it created a recovery image, and that's what I would want to use to go back to "stock + keeping root"
Right?
Click to expand...
Click to collapse
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?
It's alot easier if you use the Nexus tool kit v7, It makes it alot easier by placing the image file in the specific folder and just tapping a key. Then again it's best to keep a placed copy elsewhere as the image tends to get wiped/deleted after flashing (to avoid conflict with other image files).
thiagodark said:
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?
Click to expand...
Click to collapse
I think I got it. I think I slightly misunderstood the true meaning of root.
All I've done so far is unlock the bootloader and flashed the recovery that was instructed in this thread. So the recovery image I flashed there, replaced my "stock" one, but after doing a reboot, the stock recovery replaced my custom one? So I'm now stock with an unlocked bootloader and root?
As for the toolkit, I'm going to look into it, I was just looking to root, and followed the guide I found.
thiagodark said:
don't understand exactly what you mean... the thing is:
"root" means that you have access to root files/partitions, that is it, but the usual way to get root is: unlock bootloader, flash custom recovery using fastboot, flash root file.
now you have a "stock" phone with root access and custom recovery (usually custom recovery is replaced by stock one in the first reboot) and you end with a stock phone + root! that is exactly what you want!
as barbac666 said, you should make a nandroid backup as soon as you flash your custom recovery, even before root it!
why don't you use the tool kit available in dev section?
Click to expand...
Click to collapse
You dont need to flash cwm to get it running. If its only needed to flash su/superuser.apk, you may 'fastboot boot cwm.img', it will take you to cwm.
Misledz said:
It's alot easier if you use the Nexus tool kit v7, It makes it alot easier by placing the image file in the specific folder and just tapping a key. Then again it's best to keep a placed copy elsewhere as the image tends to get wiped/deleted after flashing (to avoid conflict with other image files).
Click to expand...
Click to collapse
Why doesnt he use the toolkit? Because it's better for them if people learn how to do this manually. Scripts are helpful, but dont teach you anything.
Sent from my i9250
bk201doesntexist said:
Why doesnt he use the toolkit? Because it's better for them if people learn how to do this manually. Scripts are helpful, but dont teach you anything.
Sent from my i9250
Click to expand...
Click to collapse
That's exactly why I wanted to do it like that.
On my LG Revolution there was pretty much only one root method and it was a one click, so I've never rooted manually. I'm happy I did.
I have Rom ToolBox Pro that I bought when I had my Revolution so I have access to boot to recovery and manage ROM's. I was just curious about the Google image file.
So at this point, is there really a reason for the Toolbox? Since I'm rooted already, I can do backups from CWM Recovery as well as flashing ROM's and Kernals. I've only ever done this from CWM on the phone so I'm used to doing it on the phone. I read most of the thread and it seams most helpful in the rooting/unlocking process.
Hola,
I am trying to root my sg3 t-mobile, I used Odin to install clockwork and everything went ok (It said Pass). Then i tried install CWM-SuperSU-v0.87 to gain superuser access but I keep receiving the message when I install from recovery:
e signature verification failed
Click to expand...
Click to collapse
and the phone reboots. I used these files for rooting from this tutorial.
Can you help me?
Wow! That is very very old! You should read the sticky threads and search the General and FaQ sections for more recent info.
Also search xda for SuperSU and you'll find the version you should be flashing is 2.46. (Probably all you need)
Or, depending on your firmware build, you can just use Towelroot. (Page 1 in general section)
Sent from my SGH-T999 using Tapatalk
manual root
The thing is that I want to install manually root access because I want to install clockworkmod and a costum ROM. Although I installed towelroot as you mentioned and I granted root access, now if install a costum ROM the towelroot app will be deleted so I loose root access right?
I also tried flashing SuperSu 2.46 before towelroot but still, no root access.
Thnx.
Any rom you flash will be rooted so you don't have to worry about that. Just flash your recovery and then flash your rom. That's it.
Sent from my SGH-T999 using Tapatalk
rooting SG3-T MOBILE without using pc.
Installed Towelroot
Installed Rom Manager -> Clockworkmod
WIPE DALVIK/ CACHE/ FACTORY RESET
Installed CM12 -> GAPPS5.1
BINGO. thnx
Rooting is not required to flash a custom recovery and custom ROM.
audit13 said:
Rooting is not required to flash a custom recovery and custom ROM.
Click to expand...
Click to collapse
Then,what's the root for? So we can just copy the roms/recovery zips into our sd and flash them?
Root allows you to read\write the \system partition, and parts if /data that are also protected. It only affects things when booted into the android OS. There are lots of things you can do with it. Debloat, modify, tweak, etc.
Pretty much all custom roms are already rooted, and all you need to flash them is a custom recovery.
Sent from my SGH-T999 using Tapatalk
hey...been here a while...did a quick search, but probably didnt look kard enough...ive always gotten good help here, so thanks in advance. just got a new note 4 through insurance and its on 5.1.1 and i was previously on, well not 5.1.1...so i need to root it. is it hard and could i get a good link? ...and sorry , but thanks again always gottwn good help here
There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk
i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it
tammyjustin said:
i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it
Click to expand...
Click to collapse
The ad blocker, depending on choice may indicate you should go with method 2 or 3.
Adguard from XDA forum would work with method 1 but only works with the browser in free mode. I know that Adaway webserver wouldn't stay enabled with method 1, systemless root.
You may also consider using FolderMount from Google Play to enable write to sdcard if you keep your titanium backup folders on extSdCard. The app patches /system/bin/sdcard and /system/etc/permissions/platform.xml That app would also suggest method 2 or 3 for root.
Mostly stock your preference? Go with method 2. Only real limitation methods 2 and 3 yield us having to update with Odin or try the return to stock for OTA. In theory, return to stock with method 1 and full un-root may actually fix OTA update if attempt to return to stock and OTA update fails for dm-verity or unauthorized modification. No guarantees though. Rooting means we accept the possibility that we may have to wait for a stock tar to update. Best to wait for confirmation that root is possible and what is required first, anyway.
Edit: the minimum links to root with are end of method 2. The instructions for TWRP flash are actually in method 3. Flash the kernel and SuperSU zip in recovery once TWRP is booted.
Sent from my SM-N920P Note 4 via Tapatalk
yea, i mostly just want toot and stock.. so u suggest method 2...thanks...i hope the instructions are clear cut cayse its been a while since ive rooted, dont want toscrrw up
i use the beast mode kernal?
tammyjustin said:
i use the beast mode kernal?
Click to expand...
Click to collapse
You can choose other kernels for root but Beastmode is closer to stock and easy on battery, IMO.
But yes, starting in Android 5.1.1 for our phone, kernel with root exploit became necessary for root. Flash the kernel then SuperSU zips in TWRP recovery together and boot. Rooted stock.
Sent from my SM-N920P Note 4 via Tapatalk
so i odin... flash twrp, kernal then SU?
tammyjustin said:
so i odin... flash twrp, kernal then SU?
Click to expand...
Click to collapse
Correct. You did mean Odin the TWRP recovery and then in TWRP, flash kernel and SuperSU zips, right?
Sent from my SM-N920P using Tapatalk
correct
samep said:
There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk
Click to expand...
Click to collapse
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!
HarrisY said:
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!
Click to expand...
Click to collapse
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk
samep said:
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.
HarrisY said:
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.
Click to expand...
Click to collapse
Yeah, they're not really that interchangeable as you've discovered. That is why I tried to differentiate the methods to choose a direction and stay the course.
Starting over with method 1 will possibly restore the OTA for update with full un-root. But no guarantee from me. But that's the only way to restore it with that possibility. Using the ##3282# method to get hotspot may break that. I'm not sure but I think flashing the zip in recovery would break that option for two reasons: flashing custom recovery and modifying system. It wouldn't break root, just nullify the reasons to use systemless root when the traditional method is more stable and you have to use Odin to update anyway.
I guess I omitted the hotspot only suggestion should most likely choose method 2? And updated CFAR isn't the traditional system based root we had in KitKat. It's strictly systemless root and experimental as far as Samsung Lollipop is concerned.
Sent from my SM-N920P using Tapatalk
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.
I'm on a stock unlocked 10 in the USA. I'm trying to understand all the root options. I really only want root for a couple reasons which is primarily titanium backup and greenify.
I don't believe I need sunshine for this but believe I need to unlock the bootloader. Correct? My concern is what happens with otas? How will I get them? Will I have to unroot every time I want to apply one? Do I have to apply a new recovery for what I want to do?
I also read that there are potential radio issues when rooting. Will I encounter that?
I'm in the same boat and new to htc. You need to unlock the bootloader to root. You only need s-off if you want to flash firmware from other regions etc.
If you flash twrp/root, you can't get OTA updates. So you would have to flash custom rom which hopefully updates to include the latest OTA (will take some time)
Or... You restore back to stock system and recovery (I think?) then get OTA, then reflash twrp and re-root.
I can't find a clear guide anywhere, there are snippets of information hidden away in several post's. Once I understand, I will flash twrp/root and try Leedroid rom, knowing I can restore via nandroid, hopefully. Also think there are issues if you change system, hosts file, gps.conf etc, it's not clear....
So... waiting for clear guidance on, how to restore back to stock, meaning I can try twrp/root/custom rom.
Missing greenify, adblock, changing kernel params, TBackup to debloat and backup
Sent from my HTC 10 using XDA-Developers mobile app
http://forum.xda-developers.com/showthread.php?t=3373025
Sent from my Nexus 5 using XDA-Developers mobile app
Are there any clear instructions on this?
Sent from my HTC 10 using XDA-Developers mobile app
Also do we lose encryption? If we flash back to stock to take an ota, so we have to wipe every time?
Sent from my HTC 10 using XDA-Developers mobile app
Bump....
If you S-Off and S-On, you lose data because you lose/gain encryption keys. (Or.. well, somethin' like that.)
Thanks but I don't think I need s off. I just want to greenify and backup
Sent from my HTC 10 using XDA-Developers mobile app
km8j said:
I'm on a stock unlocked 10 in the USA. I'm trying to understand all the root options. I really only want root for a couple reasons which is primarily titanium backup and greenify.
I don't believe I need sunshine for this but believe I need to unlock the bootloader. Correct?
Click to expand...
Click to collapse
Correct.
km8j said:
My concern is what happens with otas? How will I get them? Will I have to unroot every time I want to apply one? Do I have to apply a new recovery for what I want to do?
Click to expand...
Click to collapse
In order to root, you will need to flash a custom recovery (TWRP) and the latest BETA SuperSU (either the modified version that leaves forced encryption enabled, or the standard version that requires you to specify that prior to flashing). Doing that alone will not break your ability to receive an OTA update. However, for an OTA to be completely installed, stock recovery is required (which replaces TWRP). After rooting, you can return to stock recovery if you desire, and then you should be able to install the OTA with no problem, provided you haven't modified system at all. However, you'll then have to re-install custom recovery and root again, as the new boot.img that's included in the OTA zip will remove root access. Then you can follow the same procedure to be prepared for future OTAs.
The question really becomes, will you be using either of those apps to modify system? I don't personally know how they work and why they need root access - I'm assuming it's to access information under /data. If they're not touching /system, you should be fine.
km8j said:
I also read that there are potential radio issues when rooting. Will I encounter that?
Click to expand...
Click to collapse
The radio issues aren't necessarily related to root - they're related to removing encryption. Using the modified SuperSU or applying the proper flag to the standard SuperSU prevent this from being an issue.