I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark
There is another thread that talks about a particular flashing order. I wonder if that is your problem?
Sent from my Nexus 6 using XDA Free mobile app
Deckard_9732 said:
I tried 6 ways to sunday to update to 6.01 on a shamu nexus 6 to no avail :crying
I am unlocked, no encryption, rooted on MRA58X 6.0.0. When I try to upgrade it just bootloops.
I am fastbooting new MMB29K 6.01 bootloader.img, new radio.img, new system.img, new unencrypted boot.img, and flashing in TWRP SuperSu v2.61 prior to first reboot.
Can someone tell me what is up???? I want to stay encrypted
Thanks, Mark
Click to expand...
Click to collapse
These contradict each other, no?
Out of curiosity, what are you coming from, 6.0? Were you running any ROM of any sort?
Last question...when TWRP is about to reboot and it asks if you want it to install root, you're choosing 'No' right? 2.61 is the system-less root, and if TWRP is trying to flash it's version it'll cause problems.
I know some of these may seem simple and 'duh' moments, but I just spent the past 60 minutes trying to find out why I couldn't update only the radio......it was the radio for the N5, so we've all been there
I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.
Deckard_9732 said:
I'm coming from MRA58X 6.0.0 and no custom rom. I do have the hells core kernal v11 ... and no I select 'No' when rebooting from TWRP to install SuperSu. Shamu Nexus 6 works great with MRA58X 6.0.0 unencrypted and rooted with hells core v11 kernal and SuperSu v2.52. I dont know how to upgrade to 6.0.1 and stay encrypted? hells core has v12 kernal 6.0.1.
Click to expand...
Click to collapse
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.
hayzooos said:
I haven't been modding my N6 much at all, but I do remember reading something about when using custom kernels. I cannot remember exactly what it was, but there was an issue when you would use a custom kernel then trying to go back to stock.
Did you flash the new custom kernel before you ran into the bootloop? If so, I'd try booting it up bone stock and see if you can get it going that way. Then make one mod at a time and see what's causing the issue.
Click to expand...
Click to collapse
That would force encrypt it again.
But the way is to back to stock as much as possible. No root, no custom kernel, factory reset. The only thing needed is a modified stock boot.img with the fstab changed to encryptable.
Related
so heres the situation
running stock mra58k rooted with elementalX
encrypted
rooted with su2.46
can i just flash system.img from mra58n to upgrade then reroot?
darthchilli said:
can i just flash system.img from mra58n to upgrade then reroot?
Click to expand...
Click to collapse
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).
Face_Plant said:
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).
Click to expand...
Click to collapse
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.
haibane said:
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.
Click to expand...
Click to collapse
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.
Face_Plant said:
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.
Click to expand...
Click to collapse
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?
haibane said:
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?
Click to expand...
Click to collapse
You cannot flash an OTA if you are rooted.
danarama said:
You cannot flash an OTA if you are rooted.
Click to expand...
Click to collapse
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.
haibane said:
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.
Click to expand...
Click to collapse
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.
danarama said:
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.
Click to expand...
Click to collapse
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Also not sure if you know the answer to this, but could I move to the systemless root variant after doing the system.img and boot.img flash? I would assume this would become possible because the system.img would clean anything done by the standard root.
haibane said:
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Click to expand...
Click to collapse
No probs.
This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...
haibane said:
This is probably going to sound insane...
Click to expand...
Click to collapse
yeah....
haibane said:
This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...
Click to expand...
Click to collapse
Be careful what you wish for, you just might get it.
I was running mra58k custom rom chrome and was no force encryption and rooted on elemental kernel i up o mmb29k and re rooted my phone installed with elementalx kernal but it still shows encrypted then i went back to mra58k still same problem:crying:
arturotoledo said:
I was running mra58k custom rom chrome and was no force encryption and rooted on elemental kernel i up o mmb29k and re rooted my phone installed with elementalx kernal but it still shows encrypted then i went back to mra58k still same problem:crying:
Click to expand...
Click to collapse
Just because the kernel has "No force Encrypt" doesn't mean that it force decrypts your phone. No kernel will force decrypt your phone as it causes data loss.
If you decrypt your phone (you can search around for this, it wipes userdata). Your phone will not show as encrypted anymore. If you then flash a kernel that force encrypts, it will encrypt your device when it boots... even though you obviously wanted it decrypted. This is what "no force encrypt" means.
Also, when making threads always give a title to the thread for what you're looking for. "Nexus 6" as a title in a Nexus 6 Q&A thread is worthless for people scrolling through for topics that they think they might be able to help with.
I am brand new to the Nexus 6 but not Android. I cannot for the life of me obtain root with Build Number MOB30I. I got TWRP installed correctly and tried to install SuperSu but after I do and reboot my system, it goes to the "unlocked bootloader" warning then shuts off. What am I doing wrong? I have never had any problems when rooting before. Am i swiping/selecting something wrong when installing SuperSu?
Any help would be greatly appreciated, thank you!
videotape74 said:
I am brand new to the Nexus 6 but not Android. I cannot for the life of me obtain root with Build Number MOB30I. I got TWRP installed correctly .....
Click to expand...
Click to collapse
You need TWRP 3.0.2.0.
When bootloader is unlocked you may try to flash a prerooted rom in TWRP.
http://forum.xda-developers.com/showthread.php?t=3059493
And what version of SuperSU are you using? No reason to use anything but the latest (currently 2.72).
I also have MOB30I and have flashed SuperSU 2.72 in TWRP (3.0.2-0) without any problems
Thanks guys, do I allow system modifications in TWRP or leave it as read only?
Depends... Do you need system to be completely stock (apart from rooting and custom recovery, obviously) for some reason? If the answer is "no" or "I don't know", allow.
Does anyone know of a stock, un-encrypted, no root, nougat ROM? Tried a few "stock" roms and removed SU within the actual file. But all that does is cause issues. Any ideas?
Factory images of Android 7 were just released and Google makes them readily available to everyone. Download one and flash it using Fastboot. Problem solved.
I misread your post and missed that you were looking for an unencrypted ROM. There isn't one that I'm aware of...yet. Wait a few days and Pure Nexus should be released.
Use the factory image with a custom kernel/modified boot image that doesn't force encryption.
So like ElementalX Kernel. All I would have to do is, flash factory and than ElementalX and I should be ok?
Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.
The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.
Dopamin3 said:
The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.
Click to expand...
Click to collapse
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!
H4X0R46 said:
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!
Click to expand...
Click to collapse
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.
Dopamin3 said:
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.
Click to expand...
Click to collapse
I ended up using magisk for my issue, it disables dm-verity and turns off forced encryption, hopefully new kernel will be around soon and I have a good feeling they will be!
H4X0R46 said:
Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.
Click to expand...
Click to collapse
I was curious about this as well since I recently unencrypted my phone. Turns out SuperSU fixes forced encryption so as long as you flash it in your recovery before booting your phone back up you should be good. On 7.1.1 stock at the moment without encryption and all I did was flash the new radio, boot, and system images in Fastboot. I then booted into recovery, flashed SuperSU and rebooted. So far, so good.