So I looked around and couldn't find an answer on this, but I am in a situation where I can't have a rooted phone if I want to access my corporate email which is very important.
On the the problem. I really want to flash a custom rom, but they all obviously are rooted. Is there anyway to unroot a custom rom? I really don't need root access, but I do want to flash a kernel and Pure Shamu if possible.
Any help would be awesome. Thanks in advance!
You can simply un-root using super su settings. There's an option for full unroot. Reboot after doing it and you are good to go.
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Actually they all aren't rooted, in many cases they don't come with root, you have to flash it separately. Alternatively you can unroot as mentioned.
cupfulloflol said:
Actually they all aren't rooted, in many cases they don't come with root, you have to flash it separately. Alternatively you can unroot as mentioned.
Click to expand...
Click to collapse
This...
as long as your bootloader is unlocked, and you have a custom recovery, you can flash any rom or kernel without ever having root. you dont need root to flash them. the only reason you need root is is to use root apps or control the cpu with.
desairs said:
So I looked around and couldn't find an answer on this, but I am in a situation where I can't have a rooted phone if I want to access my corporate email which is very important.
On the the problem. I really want to flash a custom rom, but they all obviously are rooted. Is there anyway to unroot a custom rom? I really don't need root access, but I do want to flash a kernel and Pure Shamu if possible.
Any help would be awesome. Thanks in advance!
Click to expand...
Click to collapse
Install custom sys, install terminal emulator (if it doesn't already come with it), type in the following;
**********
su
mount -o remount,rw /system
mv `which su` "`which su`IamNOT"
sync
reboot
**********
Now you still have root, but it is undetectable.
doitright said:
Install custom sys, install terminal emulator (if it doesn't already come with it), type in the following;
**********
su
mount -o remount,rw /system
mv `which su` "`which su`IamNOT"
sync
reboot
**********
Now you still have root, but it is undetectable.
Click to expand...
Click to collapse
One question, what is custom sys?
Also, I have installed pure shamu and didn't root it but the MDM we have shows I am rooted.
desairs said:
One question, what is custom sys?
Also, I have installed pure shamu and didn't root it but the MDM we have shows I am rooted.
Click to expand...
Click to collapse
I think he means the ROM of your choice. Might be wrong though.
desairs said:
One question, what is custom sys?
Also, I have installed pure shamu and didn't root it but the MDM we have shows I am rooted.
Click to expand...
Click to collapse
one way to see if you have root or not, thats via a terminal emulator app. open the app, type su, press enter, if you get a #, then you have root.
rootSU said:
I think he means the ROM of your choice. Might be wrong though.
Click to expand...
Click to collapse
"ROM" is really NOT the right terminology. I think that really dates back to video game cartridges, which really were Read Only Memory.
doitright said:
"ROM" is really NOT the right terminology. I think that really dates back to video game cartridges, which really were Read Only Memory.
Click to expand...
Click to collapse
Yes it's historic. Though it is read only until you mount it with read/write permissions. You can reprogramme any ROM from the original age of consoles anyway, so nothing is ROM really. Right or wrong though, thast what we call em
Related
So I installed the retribution ROM after rooting. I thought I had forgotten to clear the caches in CWM recovery so I cleared them after I installed the rom and now I apparently have no root. Superuser tells me it can't gain root access.
So my question is, can I reroot on a custom rom?
It seems like a newbish question but I have to be extra careful, since if I mess my phone up I can't get a new one. Any help will be greatly appreciated, and will recieve homemade cookies like grandma used to make.
While I'm at it, I have another semi-related question. Can I switch to razodroid from this rom directly? I don't have access to a computer with odin riggt now and never made a backup of the stock rom. I know, that was dumb.
Firstly are you able to update the su binary in the Superuser app?
Next, out of interest what exactly happens if you type "su" followed by enter in a terminal emulator or an adb shell? The prompt symbol should either change from $ to # or you will get "su: not found". If the symbol has changed to # but you still don't have root permissions then enable "USB debugging" and "Allow mock locations" in Settings > Applications > Development. I know this sounds unrelated but this is a Rafael kernel issue.
If however you get "su: not found" then your phone is basically not rooted. There are two ways that I can think of to fix this. Either update to the latest kernel, which automatically roots your phone by installing the su binary again or flash the ROOT-S5830C-i-M.zip (from the sticky in this forum) from stock recovery.
If you choose to update the kernel then read the recent posts in the kernel thread and be sure to select the correct recovery for your filesystem format. Be sure to enable "USB debugging" and "Allow mock locations" again after you update.
If you choose to flash ROOT-S5830C-i-M.zip then from taking a look at the updater script inside the zip file, all this basically does is transfer the su executable binary along with busybox and a couple of other programs to your /system/xbin folder. I very much doubt that flashing this will brick your phone, at the very worst you might have to re-install your ROM. My thinking behind this is that you are not even touching the bootloader, kernel or ramdisk. However I can't give you a 100% guarantee because I am not quite knowledgeable enough yet when it comes to Android !
By the way for your information, su is a program that grants the current user permissions of another user (root is the default). It generally exists on all linux systems but it has been removed on Android deliberately to deny root permissions. If you don't have it then the only way to install it is via recovery/download mode because you need root permissions in the first place in order to install it to your system partition!
With regards to Razodroid the dev recommends flashing from stock. Sorry I don't feel confident enough on that one to give you a definitive answer but its probably something to do with the fact that each ROM modifies your system partition. Again, soft-brick is the likely worst-case scenario if you don't flash from stock.
Before flashing anything always do a nandroid backup in CWM and also backup your bml15 partition (IMEI number) with the Galaxy Toolbox app if you haven't done it. If you really can't get access to a PC and Odin then yeah, you probably need to be a little more careful than normal. ..
makeyourself said:
Firstly are you able to update the su binary in the Superuser app?
Next, out of interest......................................................................................
Click to expand...
Click to collapse
no need to go through all that for a simple thing.....
if your phone cannot get root access, simply root it by flashing the update.zip from HERE.
as far as the 2nd ques is concerned, you can flash other rom without flashing the original firmware....but its safer if both the roms are based on the same firmware.
Only trying to help even if it was a bit thorough: rolleyes:
Sent from my GT-S5830i using xda app-developers app
Okay, so I can just root like normal? Good, I'm glad I don't have to go through some convoluted process. And I'm checking now. Does baseband and all that matter? Like XXLA and all that?
M.Alexander.156 said:
Okay, so I can just root like normal? Good, I'm glad I don't have to go through some convoluted process. And I'm checking now. Does baseband and all that matter? Like XXLA and all that?
Click to expand...
Click to collapse
yes you can....
baseband should not matter much.....but it is better as i suggested
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
makeyourself said:
Only trying to help even if it was a bit thorough: rolleyes:
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
ya ok.....i appreciate that
Like the title says im after the system dump for this device, it has already been leaked as a few sites are reporting having it so if anyone has it or knows where to find it please share so i can extract wallpapers sounds apps etc to share
Any advice on how to do a system dump? I should have my First in a few days.
fungflex said:
Any advice on how to do a system dump? I should have my First in a few days.
Click to expand...
Click to collapse
I have mine right now but I don't know how to go about dumping the system.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Do you have the Android SDK installed and are familiar with using adb?
dstaley said:
Do you have the Android SDK installed and are familiar with using adb?
Click to expand...
Click to collapse
Absolutely to both.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Could you check to see if it's possible to disable LTE? or did AT&T do something to prevent that as it does on every phone but the iPhone?
Sent from my SAMSUNG-SGH-I747
rooobbbbb said:
Absolutely to both.
Click to expand...
Click to collapse
IIRC, you should just be able to `adb pull /system` to get the important bits. It's not a full dump, but I think you need root level access for that. And the only way I know how to get root access is to flash a zip through recovery, and TWRP/CWM hasn't yet been released for the First.
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
rooobbbbb said:
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
Well, considering that it doesn't come out until tomorrow, I'd be willing to say yes.
I was wondering why no one was posting anything about it. Lol
Sent from my HTC first using xda premium
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Do you have a retail AT&T First? Can you confirm that retail AT&T First is unlockable via htcdev?
Sent from my SAMSUNG-SGH-I747
Yes, this is a retail model, and yes, the bootloader was unlocked via htcdev.com.
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
dstaley said:
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
Click to expand...
Click to collapse
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
nuclear_eclipse said:
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
Click to expand...
Click to collapse
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
dstaley said:
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
Click to expand...
Click to collapse
No good, but thanks for providing the link. The only shot we have left is waiting for the RUU to be leaked so we can pull recovery out of it, and get a CWM/TWRP made from it.
What is RUU and how does that help us? Sorry, just coming from a Nexus-only world, so I'm not familiar with modern HTC/Samsung devices.
Sent from my HTC first using xda premium
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
TRF-Inferno said:
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
Click to expand...
Click to collapse
RUUs for the HTC One were first available on March 26, just about a month after its announcement (and, oddly, a few weeks before it's general release). Since these have to be leaked by HTC, there's no telling when we will see those. Is there any chance another root exploit exists in stock Android 4.1.2 that we could exploit in order to get root?
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
WOW, just WOW, awesome work rbox!
I was definitely not expecting this.
rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)
..
JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm
Rbox do you know if the bootloader can boot from usb?
Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Truly amazing. Can't wait for full fledged android on this.
Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.
jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.
rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Hi, I unlocked the bootloader and it was successfully. Thank you rbox
barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.
Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.
nice, thanks rbox, you rock.
Guys I just have a question,
I will be receiving my nexus 6 tomorrow and I plan on unlocking the boot loader and rooting it, but what I am curious about from reading all the threads is a few things.
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
My question is this. I plan on installing cm12 on my device and i like the idea of having my device descrpyted. I am told I have to flash the script I believe made by chainfire, but i also read u can flash another kernel. Which would i have to do? I read some say that u have to do the one made by chainfire first, and others said u just have to flash another kernel.
Also since the cm12 comes encrypted as default and lets say I "dont" want to descrypt do I have to before I flash cm12 even though its set as default encrpyted just like stock?
the_rooter said:
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
Click to expand...
Click to collapse
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.
What chain fire thing? Chain fire doesn't have anything in relation to encryption from what I know. Go to Android development and find the unencrypt thread and from there you'll find out how to unencrypt.
Do note that your data will be wiped. You'll have to flash a custom kernel before your phone starts up otherwise your phone will be encrypted again.
Most custom kernels have encryption patches to accelerate the encryption i/o speeds. You're better off just leaving it enabled if you want to keep things simple.
Sent from my Nexus 6 using Tapatalk
rootSU said:
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.
Click to expand...
Click to collapse
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Edit:
Also I wasnt sure who made the descrypt file to flash, and yes i know it does a FDR, but wouldnt it be better just to flash a custom kernel? Most kernels are already descrypted. Sorry if i repeated anything.
the_rooter said:
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Click to expand...
Click to collapse
Yes, but you wont have root at that point so, no...
rootSU said:
Yes, but you wont have root at that point so, no...
Click to expand...
Click to collapse
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.
the_rooter said:
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.
Click to expand...
Click to collapse
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.
rootSU said:
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.
Click to expand...
Click to collapse
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.
the_rooter said:
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.
Click to expand...
Click to collapse
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.
zephiK said:
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.
Click to expand...
Click to collapse
Thanks for you help guys. With this being my first nexus phone i think i understand now.
the_rooter said:
Thanks for you help guys. With this being my first nexus phone i think i understand now.
Click to expand...
Click to collapse
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.
zephiK said:
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.
Click to expand...
Click to collapse
well yeah but like i said i am on big red and this is the first nexus device they are allowing since the gnex days
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.
Thank you for moving to the appropriate location.
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.
simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?
cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.
Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!