KitKat to Marshmallow update diary, kept apps and settings, rooted - Nexus 7 (2013) General

I managed to upgrade my Nexus 7 2013 LTE from KitKat to Marshmallow using factory images yesterday and took some notes. All apps and settings kept (or at least I haven't noticed any issues other than no Xposed) and rooted. I figured someone might find this useful.
So, short version: upgrading directly from 4.4.4 to 6.0 with factory images didn't work without wiping data and where's the fun in that? So I took a longer route and went 4.4.4->5.02->5.1.1->6.0.0. It's possible I could've gone from 5.0.2 to 6.0 or 4.4.4 to 5.1.1 directly but I'm not going to try and see if that's the case. Enjoying Marshmallow now.
Basically, I did the same thing for all three update steps:
Unpacked factory image, rebooted to bootloader, flashed bootloader, radio, system.img, boot.img, cache.img. I rebooted to bootloader after flashing bootloader and again after flashing radio, same thing the flashall.bat does. Don't know if it matters.
Booted to TWRP recovery, flashed supersu zip and renamed /system/recovery-from-boot.p to keep TWRP.
Booted system and grew some gray hairs while the boot animation went on and on until it finally got to the long "optimizing apps" phase.
For 6.0 I flashed a modified kernel and supersu beta 2.52.
So, enjoying Marshmallow now. No issues so far. Root cloak detectors seem to be becoming a plague and I've only used an Xposed module for that.

Related

Updating firmware and root?

Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info

6.0 OTA issue

I recently got the OTA notice on my Pure so I returned to stock, took the update, set the phone up, fastboot flashed twrp 2.8.7.1 and have tried to install SuperUSER a couple different times. Each time I get to the Android bootup screen, not the new boot screen and it freezes there. Anyone have any ideas?
In order to get root on MM you currently (possibly permanently) need a modified boot/kernel. Chainfire talks a little about it HERE
A flashable zip with the modified boot.img can be found HERE

TWRP won't load after initial install, and root doesn't work.

I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.

Just trying to figure out if my phone is recoverable - can't boot after root attempt

Feel free to scold me, I'm not too upset but would like to fix the phone if it is possible.
Background - Phone is a Moto G4 16gb, XT1625, running android 7.0 nougat. Phone resets a lot so before replacing it I thought I would try rooting and loading a different ROM to see if it helped. I followed THIS guide:
https://theunlockr.com/root-motorola-moto-g4-moto-g4-plus/
I successfully unlocked and flashed TWRP recovery. I then tried to flash supersu v2.82 as a zip through TWRP, and upon completion the phone no longer boots up.
I can access the bootloader and and access TWRP recovery, but otherwise wiping data/factory reset or re-flashing supersu does nothing. I also tried flashing supersu as a systemless root install. I just get a black screen and a flashing white led at the bottom when charging/trying to power on. I only after the fact happened to read something about an elementalx kernel for nougat so I'm thinking maybe this was the problem.
I this a hard brick or a soft brick or just in an unbootable state? Is there a way to recover? Thanks.
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
dskater411 said:
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
Click to expand...
Click to collapse
Glad to hear you got your device fixed. For future reference, it's likely the ElementalX kernel that got you out - with stock Nougat on our devices, you can't root the stock Motorola kernel. You'll soft brick your device otherwise.
The problem with those guides is that they often don't mention that step - whilst the procedure may work for our devices with Marshmallow and Oreo, it just won't work for Nougat. Also, that article is over 2 years old, before we got Nougat onto our devices. If you wanted to flash a custom ROM, root is not needed, you just need an unlocked bootloader and TWRP.
As an aside, SuperSU is obselete, and likely abandoned by its developer. You may wish to flash magisk as your root solution, which would necessitate uninstalling SuperSU, reflashing the stock Motorola kernel and then ElementalX, then magisk.

Problems with updating to August Update

Hi! I wanted to switch from Pixel Experience back to stock, I flashed V10.0.11.0 using the official fastboot image (I used flash_all.bat). However, when I try to install the August update using OTA, it always fails for no reason. I had TWRP and Magisk installed with Pixel Experience, but reflashing everything should have deleted those. Also, I didn't flash Magisk or TWRP. I didn't even boot temporary TWRP - everything should be completely stock, but the OTA still fails. What am I doing wrong?
Edit: Curiously, Google Play shows that my device is not certified. How the hell is my phone still not considered stock? I tried reflashing multiple times, and even locking the bootloader, but the OTA still fails, and the phone is still not certified!

Categories

Resources