Related
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
I've searched tried many things can't get a recovery to work. I'm on the latest version of N rooted with auto root. Now what.
Flash the latest 6.0 vendor image and TWRP will work, however 7.0 wont boot without the 7.0 vendor image. So if you're wanting 7.0 to boot, flash 6.0 vendor>flash twrp>do whatever>flash 7.0 vendor>boot into Android.
Vekhez said:
Flash the latest 6.0 vendor image and TWRP will work, however 7.0 wont boot without the 7.0 vendor image. So if you're wanting 7.0 to boot, flash 6.0 vendor>flash twrp>do whatever>flash 7.0 vendor>boot into Android.
Click to expand...
Click to collapse
Can I trouble you for the link for trwp. IMG.
Googling TWRP for Nexus 6P is pretty easy..
https://twrp.me/devices/huaweinexus6p.html
Tried the method above no go.
Adb flashed latest marshmallow image. Then trwp. 3.02 or the latest. Could not get past frozen trwp screen.
pospower said:
Tried the method above no go.
Adb flashed latest marshmallow image. Then trwp. 3.02 or the latest. Could not get past frozen trwp screen.
Click to expand...
Click to collapse
You're being pretty vague in describing what you've done which makes it very difficult to help you. Are you currently on Marshmallow or Android N? If you're on Android you need a modified boot.img and you must also fully decrypt.
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
HelpMeXDA said:
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
Click to expand...
Click to collapse
This question is hard to answer... will it work? Maybe, we don't know. The problem is if you are rooted, you did it for a reason (or I would assume so) and you have made some changes to the /system partition over time. Doing a full unroot will not undo those changes. So if you do a full unroot, and fastboot the correct recovery image, then accept the OTA, the recovery is going start the OTA's installation script attempt to process it where it will start a checklist of items to verify, bootloader, boot image, system image, etc... the problem is we don't know what changes will cause the update to error out and which will allow it to apply.
To be honest, I don't think I have heard anyone say they have been able to successfully take this update without going back to pure stock, but ymmv.
The best thing to do would be to return to pure stock via the factory firmware images, we have a known good one of the May 2016 security update.
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.
Just saw this on the developers website
https://developers.google.com/android/images
Have any Magisk users has success removing images, downloading the ota, and reflashing Magisk to the other slot before rebooting? The download always fails for me.
GroovinChip said:
Have any Magisk users has success removing images, downloading the ota, and reflashing Magisk to the other slot before rebooting? The download always fails for me.
Click to expand...
Click to collapse
Yeah - I've never been able to get that to work and seems more complicated than just flashing factory (with -w removed) or sideloading OTA and then just reinstalling MAGISK....
I was curious if the current version of MAGISK worked on top of March 2018 security updates. I haven't seen any posts saying otherwise, but would be interested to see some confirmation that some have tried it successfully (regardless of actual upgrade method)....assume we will again have to remove all password/pin prior to upgrading to get passed the TWRP decryption issues that emerged with the Feb 2018 updates. I haven't seen any new versions of TWRP released to resolve that issue yet.
sb1893 said:
Yeah - I've never been able to get that to work and seems more complicated than just flashing factory (with -w removed) or sideloading OTA and then just reinstalling MAGISK....
I was curious if the current version of MAGISK worked on top of March 2018 security updates. I haven't seen any posts saying otherwise, but would be interested to see some confirmation that some have tried it successfully (regardless of actual upgrade method)....assume we will again have to remove all password/pin prior to upgrading to get passed the TWRP decryption issues that emerged with the Feb 2018 updates. I haven't seen any new versions of TWRP released to resolve that issue yet.
Click to expand...
Click to collapse
I just flashed update and magisk and so far no problems.
Great to hear! Really appreciate you sharing your success. I'll be taking the plunge this evening or tomorrow. Will share anything relevant that comes up.
Anybody have any luck flashing the OTA in TWRP? I keep getting error 7
For anyone that has problems: follow this guide
Works on every update, also I did it yesterday.
Now running march update + magisk + custom kernel flawlessly.
sb1893 said:
Great to hear! Really appreciate you sharing your success. I'll be taking the plunge this evening or tomorrow. Will share anything relevant that comes up.
Click to expand...
Click to collapse
I just upgraded to March Security patches...and I can confirm that it went smoothly. I flashed factory (removed -w). Then fastbooted twrp (after removing security pattern). Flashed MAGISK v16. Confirmed root and MAGISK Hide working as expected. Confirmed SafetyNet passing. Re-setup security and fingerprints (probably took the largest portion of time). Up and running - all looks good. Total process probably took less than 30 minutes.
no problems for me either. i flashed the march full factory image and rooted with magisk v16. i didn't permanently install twrp. i just fastboot booted it. i did confirm that twrp wasn't able to decrypt my phone, so i set screen lock security to none and then twrp was able to boot.
TENN3R said:
For anyone that has problems: follow this guide
Works on every update, also I did it yesterday.
Now running march update + magisk + custom kernel flawlessly.
Click to expand...
Click to collapse
can i ask which kernel are you using? i am currently running stock+ magisk and was wondering if i could further extend the battery life beyond 5.5hrs sot
Android P dev preview 1 was released today.
Sent from my Pixel XL using XDA Labs
samad.ansari said:
can i ask which kernel are you using? i am currently running stock+ magisk and was wondering if i could further extend the battery life beyond 5.5hrs sot
Click to expand...
Click to collapse
I used elementalx for a very long time, awesome kernel, but recently I switched to linux stable kernel, which is pure stock but updated to latest linux stable available (more security patches at kernel level).
And since pure android phones are always the best with stock files, I'm very happy with this kernel.
TWRP was updated to 3.2.1-1 yesterday and is now able to decrypt the data partition!!
https://dl.twrp.me/marlin/
themastermonk said:
TWRP was updated to 3.2.1-1 yesterday and is now able to decrypt the data partition!!
https://dl.twrp.me/marlin/
Click to expand...
Click to collapse
Confirmed. I was able to successfully fastboot boot TWRP-3.2.1-1 on my Pixel XL running March Security update. And I used my pattern to unlock and it successfully decrypted. Good news. Removing / restoring security/fingerprints was the most time consuming part of applying updates. Great work and many thanks @Dees_Troy!!!