Related
I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.
Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.
I did flash the factory image which is what resulted in the partition error.
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:
TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.
It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...
galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???
so actualy there is option to go back in versions?
that's nice!
I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?
Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Try to RMA
zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Badger50 said:
Sorry to hear that. Don't know if this will help, but it's worth a shot. If you RMA it, you are essentially telling Google that you messed up, but want them to replace it because of user error. Don't know if they'll go for that. Like the ol saying goes...you break it, you buy it
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Even if pay for fix, it is acceptable. It is a fact that I do wrong thing, and I am willing to pay for it.
But if can find a easy way except RMA is better.
Overall, please some advice about how to solve this. Thanks.
Does anyone know if qualcomm flash can flash image without oem unlocking?
zyf0330 said:
I use flashfire to flash OTA but fails. Now I cannot boot system and recovery. At the same time, I didn't enable OEM unlocking, so cannot flash stock image.
What should I do?
@xunholyx
Click to expand...
Click to collapse
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
v12xke said:
Flashfire is a root app. It will not run without root. I think maybe you've left out a few details. Have you attempted to fastboot boot TWRP? I don't know if it will work but it's worth a try. Without access to Recovery, you can't even sideload a rescue OTA.
Click to expand...
Click to collapse
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.?
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.
v12xke said:
I asked if you have tried to fastboot BOOT twrp, not flash it. Put twrp.img in your ADB folder and "fastboot boot twrp.img". BTW if you have recovery, you can sideload an OTA. You can't flash a full image, but you can sideload a full OTA.
Edit: I suggest you study the new fastboot commands. It is possible to set A or B active.[/QUOTE
Sounds about right fasboot twrp . That has saved many phones.
If you can't figure out what to do pay a Dev to use TeamViewer to help you out.
I did that 5 years ago until I understood
ADB commands
Click to expand...
Click to collapse
boot, set active, flash, flashing of fastboot all don't work, because bootloader is locked.
Just reread your post. You can save you phone. You need latest platform tools from Google. Then 8.1 ota image from Google. Learn fastboot commands.
When people start to jump ahead and push,click,touch things they shouldn't you end up here.
Fyi all files for easy reference should be in the plat-forms tools folder.
Download them now.
So let's start:
Fastboot --set-active=_a will set to "a" partition, usually not bootable
Fastboot --set-active=_b will set to "b" partition, usually bootable
Try this:
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_a
On phone scroll to recovery factory reset
Then
Boot boatloader (pwr button and volume down same time from phone off state)
Fastboot --set-active=_b
On phone scroll to recovery factory reset
If USB debugging wasn't turned on, boot to recovery and and side load 8.1 ota.
Follow instructions in recovery side load menu
I think it's "adb sideload filename.ota.zip"
Factory reset after boot
Or just get platform tools and 8.0/8.1 imagine depends on what you are on and restore. Probably won't work since OEM/debugging not switched on.
If you get it up and running unlock the phone to help you in the future. Yes both OEM and critical.
Good luck
matt1313 said:
Just reread your post...
Click to expand...
Click to collapse
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
v12xke said:
Well, maybe you missed OP's post #10. Locked bootloader and no recovery mode = dead in the water.
Click to expand...
Click to collapse
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
[email protected] said:
I'm on same boat with him.. Unlocked version, latest platform tools, Windows 10, Bootloader says "Locked", fastboot devices show serial no. and good works.. But fixing is not possible... Locked bootloader and not accessible recovery... All known fastboot commands return with "........ not allowed in Lock State".. RMA seems one way for us..
Click to expand...
Click to collapse
Why can't you get to recovery? Stock recovery?
If so sideload ota
matt1313 said:
Why can't you get to recovery? Stock recovery?
If so sideload ota
Click to expand...
Click to collapse
Stock.. Because all possible accessing process to recovery ending with " Can't find valid operating system. The device will not restart". Same issue with sideload ota.. "Flashing is not allowed in lock state"... I have not felt so helpless for a long time.. What a chance..
matt1313 said:
I read it. He wasn't to clear.
Which phone? Unlocked version or Verizon version
Which platform tools
Windows, mac, or Linux
What does the bootloader screen say?
Fastboot devices what does it say??
There is a lot of possibilities. Messing with partions usually causes errors. Though from reading sounds like ot can be fixed.
Click to expand...
Click to collapse
The only thing that matters is that the bootloader is locked (no fastboot is possible) and no recovery mode (no adb is possible). Done. OP is from China where there is no RMA, so he is "extra" S.O.L. I recognize you are wanting to help, but those are the facts.
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
zyf0330 said:
I must have forgot some what I did.
At first, I can boot twrp, but I do wipe then change slot in it. So now I am in slot which has no system and recovery, and cannot change slot in fastboot too. So I cannot do sideload.
I just don't know I can do sideload to fix when bootloader locked. And after I know it, I cannot boot recovery.
Click to expand...
Click to collapse
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Wait until just after Christmas, then contact Google and say you got it as a present and it says no operating system when it turns on. They're RMA it.
matt1313 said:
I understand he is more then likely SOL but I have time and want to try to help. Xmas miracle!!!! lol
what happens when you start the phone what does it say?
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
If your locked how did you boot TWRP?
what did you wipe in TWRP?
Can you get to it again and select slot B?
Click to expand...
Click to collapse
As I said, phone is booting only one screen that says "Can't find valid operating system. The device will not restart"..
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
stevew84 said:
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
Click to expand...
Click to collapse
Is this when you fastboot into twrp, or do you have twrp already installed? Have you tried disabling screen lock before you enter twrp? And I assume you've run both bootloader unlocking commands as well?
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
stevew84 said:
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
Click to expand...
Click to collapse
Typically you need to have fully unlocked the bootloader with these 2 commands...
fastboot flashing unlock
and.....
fastboot flashing unlock_critical
Especially the critical, or else you won't be able to flash any roms. I don't know if skipsoft will do this. I know the Deuces scrip will. To find out what is/isn't unlocked run.....fastboot getvar all....
Then you'll know. If you have to unlock critical, which I think you will, it'll wipe your phone completely. So backup your files and such before you do :good:
Any manual methods that work? I mean to flash the roms.
stevew84 said:
Any manual methods that work? I mean to flash the roms.
Click to expand...
Click to collapse
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Badger50 said:
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Click to expand...
Click to collapse
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
stevew84 said:
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
Click to expand...
Click to collapse
Well that changes things a little. You at least have unlocked one partition then. And you can update factory images via fastboot? If so, then your fully unlocked. So you've got a twrp decryption error on slot B. You may want to disable screen lock security, and try again. You could also try fastbooting into twrp as well with screen lock also disabled.
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
stevew84 said:
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
Click to expand...
Click to collapse
Again, run the.....fastboot getvar all....and see what you get :good:
Thanks.
Badger50 said:
Again, run the.....fastboot getvar all....and see what you get :good:
Click to expand...
Click to collapse
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
stevew84 said:
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
Click to expand...
Click to collapse
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Badger50 said:
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Click to expand...
Click to collapse
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
stevew84 said:
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
Click to expand...
Click to collapse
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Badger50 said:
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Click to expand...
Click to collapse
Jesus christ. I'm in a cmd window right now, with the latest platform tools installed.
I ran the command just as you typed, (I'm in bootloader, bootloader version tmz20j by the way). Also, my bootloader version has changed a couple of times during all of this. It was tmz20bb, then tmz12g when I flashed the latest June image...now it's this 20j version.
Anyway, this is what I'm typing and this is what I get in return:
fastboot --set-active=b
fastboot: error: Device does not support slots
I'm at a real loss, obviously this damn device supports slots.
EDIT: OK hold on, when I flashed the June image bootloader version, ran the slot command in ADB, I was able to navigate to the right slot.
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
stevew84 said:
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
Click to expand...
Click to collapse
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Badger50 said:
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Click to expand...
Click to collapse
Thanks.
Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!
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?