Database Users

Flashing OTA using TWRP

I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you

LifeOfNexus said:
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
Click to expand...
Click to collapse
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
but is this going to delete data and applications

sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No if you read the guide carefully. It states how to flash everything WITHOUT losing any data or applications.

Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This guy has lots of great advise. I always see him giving great advise all over XDA. fastboot and adb are the icing on the cake for nexus devices. ?
Sent from my Nexus 6P using Tapatalk

sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No it doesn't, did you read my guide at all? It probably isn't the best idea to be giving out false information.

Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.

I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated

David522d said:
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
Click to expand...
Click to collapse
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.

Heisenberg said:
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Click to expand...
Click to collapse
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!

David522d said:
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
Click to expand...
Click to collapse
All through fastboot, the radio and bootloader will be updated when you flash the factory images.

wietse1988 said:
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
Click to expand...
Click to collapse
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.

dratsablive said:
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
Click to expand...
Click to collapse
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better

David522d said:
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
Click to expand...
Click to collapse
I had to update TWRP afterwards.

I Flashed twrp and then did the newest factory image and kept my custom recovery and now it started up in a boot-loop
Please someone help me!
Edit
I cleared the cache in recovery and it booted
Why am I getting a "Your Device is Corrupt. It can't be trusted and may not work properly."

Root on Android 7.1 beta

Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it

Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys

I can confirm CF-Autoroot works without flaws!

I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.

What recovery are you guys using? latest 3.0.2-3?

Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps

does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:

RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.

I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!

Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???

I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.

Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.

I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?

ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire

Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.

Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader

Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo

odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/

odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?

It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

May images are up. (SU may be broke)

Three again. Verizon, Dutsche and every one else. Flashing now.
So far full images only, no OTA.

OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?

sliding_billy said:
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
Click to expand...
Click to collapse
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.

TonikJDK said:
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
Click to expand...
Click to collapse
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.

sliding_billy said:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
Click to expand...
Click to collapse
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.

Kisakuku said:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Click to expand...
Click to collapse
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.

The VZ OTA will download if you set the date to May 4th.

just checked my phone and got Verizon update without changing date

My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.

what will happen to supersu if try to flash this full factory image via flashfire and

bush911 said:
what will happen to supersu if try to flash this full factory image via flashfire and
Click to expand...
Click to collapse
It will be gone.

Pixel users are reporting bootlooping on the May update after flashing TWRP only
https://forum.xda-developers.com/showthread.php?p=72121371
https://forum.xda-developers.com/showthread.php?p=72120712

What are the chances that this was done purposely? "Breaking root and twrp"

DR3W5K1 said:
What are the chances that this was done purposely? "Breaking root and twrp"
Click to expand...
Click to collapse
Anyone try Magisk? I imagine same result.
Sent from my Pixel XL using Tapatalk

I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.

if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore

itchy67x said:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
Click to expand...
Click to collapse
Just use April's bootloader.

Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
thx that works

Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.

dowlf said:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
Click to expand...
Click to collapse
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?

January Images Posted

The January updates are up.

OTA is live too. Just 50.8 MB for 1st Gen XL.

ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now

ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.

sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?

TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.

Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!

Does anyone have the January pre-rooted boot.img?

BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.

sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.

^^^
This is a 1st.........never seen anyone ask for it........LoL

BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...

crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work