device got corrupted - Google Pixel 2 XL Questions & Answers

so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
Did you do a full clean flash of the April factory image with wiping userdata intact?

ilal2ielli said:
Did you do a full clean flash of the April factory image with wiping userdata intact?
Click to expand...
Click to collapse
i did dirty flash but it went to android recovery and from there i did the factory reset beacuse it was not booting

Prattham said:
i did dirty flash but it went to android recovery and from there i did the factory reset beacuse it was not booting
Click to expand...
Click to collapse
Your data was already wiped, so you should just go all the way and do a clean factory image flash. It'll probably fix it.

Cleaned flashed on both slots and worked
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Cleaned flashed on both slots and worked
Click to expand...
Click to collapse
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash

elliwigy said:
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash
Click to expand...
Click to collapse
That makes sense
Sent from my Google Pixel 2 XL using XDA Labs

elliwigy said:
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash
Click to expand...
Click to collapse
How to disable on stock ROM?

pa.pn2 said:
How to disable on stock ROM?
Click to expand...
Click to collapse
if u are unlocked you can do it with fastboot and the vbmeta.img from the stock rom your on..
fastboot flash vbmeta_b vbmeta.img --disable-verity --disable-verification
fastboot flash vbmeta_a vbmeta.img --disable-verity --disable-verification
fastboot reboot
Theres also a file or two probably floating around if u can find it that can be done from root terminal or root shell.. the binary is called avbctl.. i cant recall the commands but if u find it and push to your device just type avbctl and it should list the commands.. its something like avbctl --disable-verity avbctl --disable-verification.. this binary will also let you check if they are already disabled or not..
theres also a zip floating around if u can find it.. this zip is flashed in twrp and will disable them for u
keep in mind if u are not unlocked u probably wont even have the disable commands showing in fastboot.. also, you only really need to disable them if u are getting corrupt errors or boot loops.. of course theres also a chance u have another issue entirely but in my flashing craze majority of time for me disablimg fixes my boot issues after flashing firmwares

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
I've had this happened quite a few times it's usually when I go from custom ROM back to stock when I go to update my new month. Almost every time restore a stock backup in TWRP gets me out of it. And if that doesn't work I try flashing stock image to both slots without the w. I'll try disabling that verity thing next time though if I can't get it to work

So, tried flashing resurrection Rom. Had some issues. So, ran a Deuce with latest full stock like I always do. After the flash, getting "Your device is corrupt. It can't be trusted and may not work properly." Now in fastboot can't even run Fastboot commands from computer. Not responding at all to anything
Any ideas?
Edit:
did some more troubleshooting.
Ran from the zip download:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
Then set the fastboot slot a active.
Then was able to boot recovery.img and then reboot.
Somehow the slot must have been changed/corrupt and wouldn't work? Anyway, all working now.

Prattham said:
Cleaned flashed on both slots and worked
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Hi Pratham,
Could you please help me for this?
My phone got stuck in GOOGLE logo and also showing corrupted status on starting.
I just critical unlocked my phone and its happening.
How to do clean flash ?

navi_j said:
Hi Pratham,
Could you please help me for this?
My phone got stuck in GOOGLE logo and also showing corrupted status on starting.
I just critical unlocked my phone and its happening.
How to do clean flash ?
Click to expand...
Click to collapse
Oh so you got a corrupted mssg as well
Here it is
Just download the factory image
And flash it
You will lose all your data but it will work
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Oh so you got a corrupted mssg as well
Here it is
Just download the factory image
And flash it
You will lose all your data but it will work
Click to expand...
Click to collapse
Or he could edit the flash-all, removing the -w to save his data.
Or even flash just the vbmeta image and see if that removes the corrupt message on boot.
No need to resort to the extreme solutions right off the bat!

rickysidhu_ said:
Or he could edit the flash-all, removing the -w to save his data.
Or even flash just the vbmeta image and see if that removes the corrupt message on boot.
No need to resort to the extreme solutions right off the bat!
Click to expand...
Click to collapse
Well that didn't worked for me i had to clean flash so that's why i said it
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Well that didn't worked for me i had to clean flash so that's why i said it
Click to expand...
Click to collapse
But it might work for him/others, so just saying it's probably quicker and more efficient to try less drastic options first.

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
This has happened to me a few times and what i did was boot into bootloader mode and flash the factory image to start over fresh. I know it sucks losing everything but for me it was the only thing that got me up and running again, not even restoring a backup worked

Related

OnePlus3 Stuck on Logo When Booting

My problems started when I was on version 3.2.4 and could not update to 3.2.6 or 3.2.8, the update downloaded (OTA) and got stuck on the installation page after my phone rebooted. I previously has TWRP installed but uninstalled it before trying the OTA update and have again managed to install it. When I click "Install" in TWRP and look at /sdcard the folder is empty with the exception of a TWRP folder. I have tried to use adb sideload toOnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a (cant link since this is my first post, sorry) but got an error 7. Any ideas on how I can fix this?
ng150716 said:
My problems started when I was on version 3.2.4 and could not update to 3.2.6 or 3.2.8, the update downloaded (OTA) and got stuck on the installation page after my phone rebooted. I previously has TWRP installed but uninstalled it before trying the OTA update and have again managed to install it. When I click "Install" in TWRP and look at /sdcard the folder is empty with the exception of a TWRP folder. I have tried to use adb sideload toOnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a (cant link since this is my first post, sorry) but got an error 7. Any ideas on how I can fix this?
Click to expand...
Click to collapse
Sounds like your encrypted? Not sure what version of twrp you are on but this is the one that most have found luck with.
Ducter said:
Sounds like your encrypted? Not sure what version of twrp you are on but this is the one that most have found luck with.
Click to expand...
Click to collapse
If thats the case running the command fastboot oem lock
And then fastboot oem unlock will help to wipe everything and remove encryption
v.konvict said:
If thats the case running the command fastboot oem lock
And then fastboot oem unlock will help to wipe everything and remove encryption
Click to expand...
Click to collapse
Are you trying to get him into more trouble that he's already in?
Locking the bootloader while having custom recovery will result in a brick!
And there's no reason whatsoever to lock the bootloader on OP3 once it has been unlocked. Everything works with unlocked bootloader (including official OTA) so just keep it at that.
To remove encryption you have to format data partition - command: fastboot format userdata.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Are you trying to get him into more trouble that he's already in?
Locking the bootloader while having custom recovery will result in a brick!
And there's no reason whatsoever to lock the bootloader on OP3 once it has been unlocked. Everything works with unlocked bootloader (including official OTA) so just keep it at that.
To remove encryption you have to format data partition - command: fastboot format userdata.
Click to expand...
Click to collapse
Wierd coz it happened to me the other day. After i flashed unofficial recovery . so i did that and it wiped everything
v.konvict said:
Wierd coz it happened to me the other day. After i flashed unofficial recovery . so i did that and it wiped everything
Click to expand...
Click to collapse
Lucky guy then
But still, many people bricked their devices when they tried locking bootloader without stock recovery and ROM. Better not to push your luck, especially when there exist better ways of doing stuff (wiping internal storage in this case).
Sent from my OnePlus 3 using Tapatalk

"Fingerprint Hardware Not Available" and missing WiFi

Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
absoluthamm said:
Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
Click to expand...
Click to collapse
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Badger50 said:
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Click to expand...
Click to collapse
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
absoluthamm said:
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
Click to expand...
Click to collapse
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Badger50 said:
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Click to expand...
Click to collapse
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
absoluthamm said:
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
Click to expand...
Click to collapse
Darn! Oh well, if your still having trouble after you fastboot the stock boot.img, you may have to dirty flash the factory image. If that doesn't work, then a factory reset or a clean flash of the factory image might be needed. If that doesn't work, then you may have to run it in safe mode for a while. Finally, if that doesn't work, your hardware/software may be hosed and RMA here you come. Lets hope it's not that serious
This happened to me on the Pixel 2 when updating to the January image, I had do a full image wipe in order to fix it.
bro i am worried i wiped data cache vendor and flashed RR rom now the sim is not inserting and wifi bluetooth fingerprint music everything is not working ..what should i do

cannot flash any roms, errors

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.

Boot hang, TWRP Recovery unresponsive

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!

help needed here bootloop

this happens to me for the 2nd time, i clean reflashed factory image of android 10, then installed a kernel, twrp and magisk, after installing some magisk mods device bootloops in restarts directing me to twrp recovery, i deleted them using file manager but still the device bootloops and they are not the reason behind the bootloop as they we working before,
something to add is that device selinux is set to permissive and not enforcing, idk if this is the case or no
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
wolfeyes30 said:
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
Click to expand...
Click to collapse
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Nightf0x_007 said:
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Click to expand...
Click to collapse
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
wgrant said:
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
Click to expand...
Click to collapse
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Nightf0x_007 said:
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Also, I saw in your other thread that you're using the Canary builds. I'm using magisk 19.3 without issue and twrp 3.3.0 with the system mount error that comes up but it still flashes what ask it to. For twrp I flashes the img file to the recovery partition and it's working just fine, no need to use the zip.
wgrant said:
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Click to expand...
Click to collapse
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Nightf0x_007 said:
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Click to expand...
Click to collapse
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
wgrant said:
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
Click to expand...
Click to collapse
the script only flashes slot B in here is that normal ?
Nightf0x_007 said:
the script only flashes slot B in here is that normal ?
Click to expand...
Click to collapse
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
wgrant said:
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
Click to expand...
Click to collapse
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Nightf0x_007 said:
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Click to expand...
Click to collapse
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
wgrant said:
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
Click to expand...
Click to collapse
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Nightf0x_007 said:
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Click to expand...
Click to collapse
You data partition may be corrupt and needs to be wiped.
wgrant said:
You data partition may be corrupt and needs to be wiped.
Click to expand...
Click to collapse
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Nightf0x_007 said:
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Click to expand...
Click to collapse
Did you manage to get it to work?
leqacy said:
Did you manage to get it to work?
Click to expand...
Click to collapse
Yes, i flashed .19 image then sideloaded .20 ota, tell now things good returning my data step by step
But after i did this intalling twrp after that when i boot os then reboot phone bootloops so i didnt install twrp after that (reflashed .19 ........)

Categories

Resources