Related
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...
kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.
mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.
My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?
I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/
Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
no issues here on 19J. modified boot image here
bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.
SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Bump
Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out
How is the new update in terms of making the phone better?
gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.
In the Oneplus 3T forum it is reported that flashing the bootloader resets the dm verity. Can we get the bootloader for Oneplus 3 to try the fix?
wrong forum body...
there's a specific forums for questions & requests.
Hi,
I had also this problem on my OP3 (not T version).
Solved with this :
1- on Freedom OS 1.7 (any rom should work), rebooted to TWRP (Official)
2- wiped everything including internal storage. (if already on .28 TWRP wiping data to f2fs and wiping internal storage normally may save you some steps later on)
3- fastbooted the official recovery (v1 downloaded from OP site)
4- rebooted to official recovery and started install from ADB.
5- sideloaded beta 9
6- rebooted to beta 9 ( booted perfectly with no issues)
7- reboot back to official recovery (now it will be v2)
8- wipe cahce (and data if available)
9- reboot to fastboot and fast boot mod TWRP .28
10 - on TWRP the password issue might appear but it';; be fixed after this step
11- on TWRP wipe Data to f2fs (even if it was f2fs) and wipe internal storage (it may show it as 0 size)
12- reboot to system
13- reboot back to TWRP and now it can access internal storage , flash SuperSU (sr5)
finaly reboot to system.
Regards,
Ted
Stop with this thread there are already specific threads for dm.
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
MultiCulti said:
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
Click to expand...
Click to collapse
There's technically no problem other than the annoyance of seeing the warning and using an extra 5 secs
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
qhsusb_bulk said:
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
Click to expand...
Click to collapse
And then flashed back OOS 4.02?? It is still gone
panther124 said:
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
Click to expand...
Click to collapse
Worked like a charm! Thanks for the tip
fuarkgl3 said:
Worked like a charm! Thanks for the tip
Click to expand...
Click to collapse
can u tell me how to restore backup file from flashfire.
phanipk said:
can u tell me how to restore backup file from flashfire.
Click to expand...
Click to collapse
Transfer your backup to your computer and extract the zip, then put your phone in fastbooot mode and click flash-all.bat
there have been so many threads on how to remove DM V. just use the search function dude...
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity (this command is not needed)
fastboot oem enable_dm_verity
snippem said:
And then flashed back OOS 4.02?? It is still gone
Click to expand...
Click to collapse
Sorry for late reply. Yes now i am using OOS 4.0.2 with open beta 7 firmware. Firstly flashed full OOS zip with twrp, secondly i flashed OB7 firmware.
Thanks Sniperle
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Rastko said:
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
Click to expand...
Click to collapse
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
bensen from hell said:
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
Click to expand...
Click to collapse
I'm using TWRP, LineageOS, phh root and it works
---------- Post added at 11:13 ---------- Previous post was at 10:59 ----------
sjaak1234 said:
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Click to expand...
Click to collapse
The ZIP is for the previous use to not trigger dm-verity at all.
The fastboot commands should disable the message if you have already triggered dm-verity.
Ahhh nice, thanks. I thought that is only work with original bootloader and recovery because the OEM in the command. I'll try it at Weekend.
After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!
Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.
Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you
Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.
I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.
I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.
Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?