Develop Bugs

[Q] ADB sideload with TWRP fails for 4.4.3 OTA (Nexus 7 LTE)

Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!

Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.

Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.

endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.

Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:

[Q] 5.0.1 Rooted to 5.0.2 Without Data Loss

For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.

Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps

I'm having the exact same problem. I'm attaching what's appearing on TWRP.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.

I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.

You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.

yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app

^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.

newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx

mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?

Honor 7X Oreo Stock Recovery

Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.

Could you share your twrp? Thanks!

Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"

holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500

mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.

Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)

Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?

mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?

Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.

mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading

Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead

Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help

Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me

Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman

mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.

kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work

mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response

kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option

mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.

aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?

Issues on top of issues rooting Pixel 2 XL! Help? :(

First, I followed a tutorial precisely and ended up with a bootloop. It was just stuck at the white screen with a G. This was only after flashing the patched_boot.img file that Magisk gave me. I searched for hours online for an answer for that, and my device isn't listed when I type "adb devices." It's just blank. I uninstalled and reinstalled the drivers, I used different usb ports, different cables, I'm using the latest Google usb drivers, as well as the latest adb/fastboot files.
I wanted to push twrp to my phone via ADB, so I can flash magisk that way and fix this issue. I've read that it fixed my problem for other people, but sadly I'm unable to so far. When I try using the command "adb push twrp.zip /sdcard/" I get the following error:
"adb: error: failed to get feature set: no devices/emulators found"
In case anyone was wondering this is the tutorial I initially followed: https://youtu.be/M-0NIUUvYI4
I really don't know where to go from here. I've been looking around for 6 hours straight. All help is most appreciated.

Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the response, Ricky. I tried using the ADB sideload feature in TWRP but it just stuck at "Starting ADB sideload feature..." and eventually fails. Then I used a flash drive and connected it to the phone via the adapter, and that worked. Unfortunately, after flashing those files it was still stuck at the same bootloop screen. I went back to TWRP and now the usb flash drive isn't being recognized. What should I do?
Edit: I was able to FINALLY get it out of the bootloop! I tried this script earlier and it didn't work, but it was because I didn't have the critical partitions unlocked (https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778). Unlocked them, ran the script, works perfectly now. However, now I'm going to root it via TWRP and use the files you mentioned. Will do that tomorrow after sleep!

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.

Mr December said:
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.
Click to expand...
Click to collapse
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:

Badger50 said:
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:
Click to expand...
Click to collapse
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?

Mr December said:
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?
Click to expand...
Click to collapse
This is how I do my monthly updates

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Thanks bro I'll give it a shot today :laugh:

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen

Mr December said:
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen
Click to expand...
Click to collapse
You are correct :good:

Unable to flash OTA update

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?