This may be a question that has been asked and answered numerous times. Just got my nexus 6 and want to root and slap custom recovery on it. Must I decrypt the phone before doing so on net or c.f. Auto root? I've tried to root it but something isn't right. That's why I'm asking if I need to decrypt it before rooting. And My boot loader is unlocked. Thanks.
Since you have a Nexus Device, there is really no point using auto root methods as it is a lot easier just to flash SuperSU in twrp.
Sent from my Nexus 6 using Tapatalk
And I can do all this encrypted? I had a nexus 5 previously and rooting that was easier. I want to keep encryption btw.
darklordofthesith said:
And I can do all this encrypted? I had a nexus 5 previously and rooting that was easier. I want to keep encryption btw.
Click to expand...
Click to collapse
Yes you can stay encrypted. I am, lots of us are. You dont have to do anything different to stay encrypted. Unlock it, flash TWRP then flash systemless root with TWRP.
Sent from my Nexus 6 using XDA Labs
Ill just grab The latest su beta. That should be sufficient. Also, if I want to change kernels, I'd need one that's encrypted right?
You mean one that supports device encryption, since an encrypted bootloader is a very bad thing. Just ask any AT&T device owner from the last two years.
To actually answer your question, I do believe that by default all kernels support device encryption. What is different in a custom kernel is whether that encryption is automatically applied or not.
unless you actively decrypt yourself, you are encrypted. to unencrypt, you have to flash a kernel that allows for decrypting, then format your whole phone/storage yourself. only then you will be decrypted. you can do any mod possible on a n6 while still encrypted.
So, if I want a new kernel, just find one that has forced encryption. I definitely want to keep my phone encrypted for safety reasons. Also, will that dreaded message pop up every time I reboot the phone about being corrupted? Also, what kernels force encryption. Thanks.
Very few custom kernels force encrypt, they leave the option to the end user like Simms said if you have a custom kernel and factory reset then it will unencrypt your phone.I'm encrypted and run stock Google images and Franco kernel
So, will I get that dreaded message of a corrupt device after doing everything? I
Well, tried to flash twrp 3.0.0.0 to no avail through nrt. It says it flashed it but every time I reboot to recovery, the stock recovery is still there. My boot loader is unlocked. What gives?
darklordofthesith said:
Well, tried to flash twrp 3.0.0.0 to no avail through nrt. It says it flashed it but every time I reboot to recovery, the stock recovery is still there. My boot loader is unlocked. What gives?
Click to expand...
Click to collapse
dont use toolkits. you learn nothing and occasionally they dont work. you need to flash twrp through fastboot, while youre in the bootloader. and the line you write is fastboot flash recovery recoveryname.img
It used to work through nrt for my nexus 5. So what makes this different? Also can I use the image from nrt or should I download a fresh one.
darklordofthesith said:
It used to work through nrt for my nexus 5. So what makes this different? Also can I use the image from nrt or should I download a fresh one.
Click to expand...
Click to collapse
many things could have broken the toolkit. that's why the far majority of people who actually know what they are doing say to not use toolkits. and why do you need another image? to root, you have to unlock your bootloader with fastboot, flash twrp with fastboot, then boot up with root.
darklordofthesith said:
So, will I get that dreaded message of a corrupt device after doing everything? I
Click to expand...
Click to collapse
Not if you use systemless root. Or a kernel that is modified to avoid that message with the older style root. I have run stock and with Franco's kernel, both with systemless. Never had the message.
Sent from my Nexus 6 using XDA Labs
I even tried to boot to twrp temporarily and it said that i had to modify the system because it was write protected. I never had this much issue with a nexus before.
when i boot into the temp twrp through nrt, i keep getting this keep system read only message. should i do what it says to do?
Do you want to keep it read only or do you want to modify it, your decision
Edit:
Just the system partition I should have been more specific
If I do that, it will still be encrypted and be able to root and install twrp? Without the dreaded corrupted message?
If you modify anything at all the message will show up,unless you run a custom kernel that disables it, and yes you will still be able to root and stay encrypted
Related
I see this annoying error whenever i am in TWRP. I thought I had it resolved when I flashed the stock ROM then flashed my current run CM-12.1-20150902-NIGHTLY-shamu obtained from Cyanogens website.
Then today I let it run the latest OTA and forgot I would lose root. So I attempted to root again only get get stuck at the boot screen. I eventually did a dirty flash of the same CM 12.1 and now I am back to normal and I was able to root again. But I still get the error E: Unable to mount storage.
Also, I am now also unable to see my Nexus in Windows to explore Internal Storage but was able to before I tried rooting.
Thanks in advance.
Sounds like a good time to do full wipe and clean install. Including TWRP and root.
prdog1 said:
Sounds like a good time to do full wipe and clean install. Including TWRP and root.
Click to expand...
Click to collapse
That's the thing, I thought I did all that properly and then flashed the latest CM 12.1 but noticed last night after a failed root that it is now giving the error again.
Would using my backup after I flashed the stock ROM cause the error to come back? I am just looking for the easiest way to avoid reconfiguring my phone and apps again.
tjlmbklr said:
That's the thing, I thought I did all that properly and then flashed the latest CM 12.1 but noticed last night after a failed root that it is now giving the error again.
Would using my backup after I flashed the stock ROM cause the error to come back? I am just looking for the easiest way to avoid reconfiguring my phone and apps again.
Click to expand...
Click to collapse
Good chance it is that CM12 borking it. Flash anything you want. It either fixes it or it don't. Can always flash back to stock to troubleshoot.
Are you encrypted, with a password to decrypt on boot?
If you have like a swipe password , when rebooting into TWRP you will never the normal android to allow you to enter your password, instead you *should* get one in TWRP, however it will just prompt you for an alphanumeric password.
If you cancel out of that, or enter the wrong password (or don't have an alphanumeric password to enter), I believe it gives you this message... and obviously will fail to mount the encrypted partition.
If this is the case, boot back into system, turn off all passwords/security and it should work fine (no need to decrypt)
scryan said:
Are you encrypted, with a password to decrypt on boot?
If you have like a swipe password , when rebooting into TWRP you will never the normal android to allow you to enter your password, instead you *should* get one in TWRP, however it will just prompt you for an alphanumeric password.
If you cancel out of that, or enter the wrong password (or don't have an alphanumeric password to enter), I believe it gives you this message... and obviously will fail to mount the encrypted partition.
If this is the case, boot back into system, turn off all passwords/security and it should work fine (no need to decrypt)
Click to expand...
Click to collapse
I am not really sure what this is so my guess is now. I do have my phone set with a 'pattern unlock to boot and unlock the phone. How do I tell if I am encrypted?
Your encrypted if you did not install a kernel that supports no forced encryption, the reformat your user data partition via fastboot,
The phone is encrypted by default.
the fact that your device requires pattern unlock at boot, and not just to unlock is a pretty good indicator, but try going into security and select encrypt phone. If it does not give you warnings, remind you to charge and offer to let you encrypt, it is because you already are. Turn off the pattern needed to boot at least, if not any unlock security in general before rebooting to recovery to avoid this error.
scryan said:
Your encrypted if you did not install a kernel that supports no forced encryption, the reformat your user data partition via fastboot,
The phone is encrypted by default.
the fact that your device requires pattern unlock at boot, and not just to unlock is a pretty good indicator, but try going into security and select encrypt phone. If it does not give you warnings, remind you to charge and offer to let you encrypt, it is because you already are. Turn off the pattern needed to boot at least, if not any unlock security in general before rebooting to recovery to avoid this error.
Click to expand...
Click to collapse
Well I haven't changed my kernel and it says Encrypted in my settings. So I could potentially stay on my current setup and resolve my error if I install another kernel?
So here's what I hope will be an easy answer, what is the best method to flash a kernel? I have only tried it once and failed since my phone failed to boot afterwards.
Any recommendations on which kernel to use with CM?
Thanks for the help.
tjlmbklr said:
Well I haven't changed my kernel and it says Encrypted in my settings. So I could potentially stay on my current setup and resolve my error if I install another kernel?
So here's what I hope will be an easy answer, what is the best method to flash a kernel? I have only tried it once and failed since my phone failed to boot afterwards.
Any recommendations on which kernel to use with CM?
Thanks for the help.
Click to expand...
Click to collapse
No.
And CM comes with its own kernel, that does not force encryption.
The kernel is not "encrypted" or "decrypted", the stock kernel forces encryption, others don't. But if your encrypted, you are encrypted until you reformat userdata (obviously this wipes phone) so that it is not encrypted.
scryan said:
Your encrypted if you did not install a kernel that supports no forced encryption, the reformat your user data partition via fastboot
Click to expand...
Click to collapse
scryan said:
...and obviously will fail to mount the encrypted partition.
If this is the case, boot back into system, turn off all passwords/security and it should work fine (no need to decrypt)
Click to expand...
Click to collapse
scryan said:
. Turn off the pattern needed to boot at least, if not any unlock security in general before rebooting to recovery to avoid this error.
Click to expand...
Click to collapse
On encryption:
https://wiki.archlinux.org/index.php/Disk_encryption
(not related to nexus, other then it explains encryption, and nexus is encrypted)
You don't need to disable encryption, but obviously since you have your phone set up to require a pattern supply the decryption key to the system, and your booting into twrp BEFORE you can supply the key for decryption... twrp is not going to have any way to read the encrypted partition. Just turn the security off before rebooting to recovery.
Alternatively you can look up threads here on decrypting your phone, and follow those instructions. You will get a very minor performance boost too... but it does mean that if your phone is lost or stolen your data is a little more accessible.
scryan said:
No.
And CM comes with its own kernel, that does not force encryption.
The kernel is not "encrypted" or "decrypted", the stock kernel forces encryption, others don't. But if your encrypted, you are encrypted until you reformat userdata (obviously this wipes phone) so that it is not encrypted.
On encryption:
https://wiki.archlinux.org/index.php/Disk_encryption
(not related to nexus, other then it explains encryption, and nexus is encrypted)
You don't need to disable encryption, but obviously since you have your phone set up to require a pattern supply the decryption key to the system, and your booting into twrp BEFORE you can supply the key for decryption... twrp is not going to have any way to read the encrypted partition. Just turn the security off before rebooting to recovery.
Alternatively you can look up threads here on decrypting your phone, and follow those instructions. You will get a very minor performance boost too... but it does mean that if your phone is lost or stolen your data is a little more accessible.
Click to expand...
Click to collapse
Thanks. I hope to figure this all out tonight.
tjlmbklr said:
Thanks. I hope to figure this all out tonight.
Click to expand...
Click to collapse
The thread on it is a little confusing IMO, maybe just me.
Just remember encryption is about how the data is stored on the partition NOT a setting in the kernel. The kernel only comes into play because the kernel used stock on the nexus 6 has code to check if you are using encryption, and if you are not it forces you to encrypt your data before it boots.
So step one is make sure you have a kernel that does not force encryption. I have not seen a 3rd party nexus kernel with encryption set to enforced, that would be weird.
Step two is to actually go ahead and make your user data partition not encrypted. This has to be done by reformating in fastboot, see tutorial thread for commands. When you reformat, by default the partition will not be encrypted.
Just make sure that when you an update you don't flash the stock kernel and boot, because this will wipe your device when it forces you to encrypt (You could probably power down or cancel some how? Have never tried...)
This would most likely happen if you ran stock, and you fastboot flashed a new system and boot (boot contains kernel)
Alternatively, don't mess with any of this. You don't need to be unencrypted to mount your data in recovery, you just need to set up security in android to not require any kind of pin to boot (I used to just turn unlock to swipe instead of pattern before I wanted to use recovery). There is some performance lost with encryption, but they vastly improved encrypted performance with 5.1.1, and not being encrypted only gives you a tiny bump in performance. just A LITTLE more snappy imo.
scryan said:
The thread on it is a little confusing IMO, maybe just me.
Just remember encryption is about how the data is stored on the partition NOT a setting in the kernel. The kernel only comes into play because the kernel used stock on the nexus 6 has code to check if you are using encryption, and if you are not it forces you to encrypt your data before it boots.
So step one is make sure you have a kernel that does not force encryption. I have not seen a 3rd party nexus kernel with encryption set to enforced, that would be weird.
Step two is to actually go ahead and make your user data partition not encrypted. This has to be done by reformating in fastboot, see tutorial thread for commands. When you reformat, by default the partition will not be encrypted.
Just make sure that when you an update you don't flash the stock kernel and boot, because this will wipe your device when it forces you to encrypt (You could probably power down or cancel some how? Have never tried...)
This would most likely happen if you ran stock, and you fastboot flashed a new system and boot (boot contains kernel)
Alternatively, don't mess with any of this. You don't need to be unencrypted to mount your data in recovery, you just need to set up security in android to not require any kind of pin to boot (I used to just turn unlock to swipe instead of pattern before I wanted to use recovery). There is some performance lost with encryption, but they vastly improved encrypted performance with 5.1.1, and not being encrypted only gives you a tiny bump in performance.
Click to expand...
Click to collapse
LeanKernel decrypt is an option as it should be in all Kernels and is one of the better ones. The top kernel developers make it an option. Many noobs post unencrypted kernels where they only change the ramdisk and there is no other option. Can have performance and encryption as you say especially with the Google code updates.
prdog1 said:
LeanKernel decrypt is an option as it should be in all Kernels and is one of the better ones. The top kernel developers make it an option. Many noobs post unencrypted kernels where they only change the ramdisk and there is no other option. Can have performance and encryption as you say especially with the Google code updates.
Click to expand...
Click to collapse
Super random and unrelated plug for leankernel, but OK thanks. :good:
There are plenty of popular kernels, I have found Zen good, many like Elite and Hells Core as well.
I am sure this is a noob question here so I apologize in advance. I am a bit confused about how to go about disabling / removing encryption on my Nexus 6. When I look into it, it seems to be required to flash a new boot.img. However, you already need to use a modified boot.img to root.
So, once you are rooted, you can change your boot.img without losing root?
Does the modified boot.img from Chainfires post already disable / remove encryption?
Is there a modified boot image that disables encryption and allows root?
When I am in Titanium Backup, I see encryption: DISABLED. Is that telling me that my phone encryption is disabled or that just Titanium Backup Encryption is disabled?
Also, now there is MRA58K/N/R. Chainfires post has the modified boot image from K. Has the boot.img changed at all from K to N to R? If so, how can one still use the modified boot.img from K after flashing to R?
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
simms22 said:
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
Click to expand...
Click to collapse
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Rektifying said:
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Click to expand...
Click to collapse
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
simms22 said:
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
Click to expand...
Click to collapse
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Anyone else care to answer this for me? I am newer to Android period so I apologize again for sounding noob. I just don't fully quite understand how this root method works. So if a modified boot.img is required for root, how can I turn around and flash a different boot.img and still have root?
I am literally sitting here waiting to flash my Nexus 6 to MRA58R until I figure this out. I am well aware how to flash stock images, custom recovery, sideload superSU. I just want to clean flash my Nexus 6, have root, and have encryption disabled.
Rektifying said:
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Click to expand...
Click to collapse
i use despair kernel. technically, any custom kernel is a modified kernel. and it alows for decryption, even though i did not decrypt. i flashed marshmallow, flashed despair, then flashed supersu. now im on marshmallow with root.
what im saying is that i have never used chainfires kernel, so dont know anything about it.
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Rektifying said:
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Click to expand...
Click to collapse
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
simms22 said:
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
Click to expand...
Click to collapse
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Rektifying said:
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Click to expand...
Click to collapse
yes(but im not sure with marshmallow). with all other android builds, yes.
simms22 said:
yes(but im not sure with marshmallow). with all other android builds, yes.
Click to expand...
Click to collapse
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Rektifying said:
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Click to expand...
Click to collapse
yes.
but the thing i dont know about is that the stock marshmallow kernel might prevent root, even though the files are still there. but you can flash any marshmallow custom kernel(for n6).
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
awesome
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
I was trying to figure out the same thing. What modified boot.img did u use for root access and which modified boot.img did u use to remove encryption. Thanks.
Basically any kernel that does not check encryption and force it to be applied... In other words almost any 3rd party kernel... But double check the kernels feature list and make sure it says no forced encryption.
The device will probably give you a "system is corrupt" error with a stock kernel and root installed. I would flash a custom kernel for sure because it usually doesn't force encryption and does support root! I am using elementalx right now and it's a very good kernel for this. Many other custom kernels work just as well! I HAVE used chainfire's kernel, and it does not force encryption, it also supports root, I can confirm this. If you use chainfire's kernel, make sure you format your data to unencrypt. You can use the "format data" option in TWRP or use the fastboot command "fastboot format userdata". Hope I helped!
EDIT: You have to format your data to decrypt regardless of WHICH kernel you choose, sorry if that sounded confusing.
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.
Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.
<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.
Can't we just flash Magisk on TWRP?
yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.
greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.
e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help