Related
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
my phone still works on slot B but Slot A just reboots straight to twrp and ive tried to factory reset it to factory and fastbooting the boot.img again
Veid71 said:
my phone still works on slot B but Slot A just reboots straight to twrp and ive tried to factory reset it to factory and fastbooting the boot.img again
Click to expand...
Click to collapse
Unless your setup to dual boot you can only boot your active slot
mac796 said:
Unless your setup to dual boot you can only boot your active slot
Click to expand...
Click to collapse
is there a way to change the active slot? i was trying to install magisk and trying to fix slot A and now slot B wont start up. so now neither of them will turn on, Slot A just bootloops and slot B just turns to twrp now
Known problem with magisk. Just use su, but use old sr3. New beta is killing twrp
I would honestly do a flash-all.bat of the latest factory image separately to both slots a & b to clear any risidual problems that might currently exist and then start over with whatever flashing you want to do from there. I'm assuming you know you need to use the unofficial build of Magisk on the Pixel because the official version does not work. Unofficial Magisk apparently has its own dedicated thread now but used to be hosted in the Paranoid Android rom thread. You could probably go to either place to find out what the latest version of Unofficial Magisk is that is stable and people are using without problems. If you want to pass Safety Net with root you can't do it with SU. If that doesn't matter you can use SU like the previous poster suggested but people are using Unofficial Magisk on the Pixel without issues --you just need to use the right version and the version of Magisk Manager that is compatible with it.
Yep did the same.
Flashall.bat on active slot.
Then set the other one as active via fastboot
Than flashall.bat again
Was the only help for me.
mikaole said:
Yep did the same.
Flashall.bat on active slot.
Then set the other one as active via fastboot
Than flashall.bat again
Was the only help for me.
Click to expand...
Click to collapse
Yeah I figured out the issue was that I did a factory reset but I didn't reflash the ROM so I guess it didn't know what to boot into? But as soon as I flashed the ROM it worked also where can I get sr3? I've looked on the su thread but it doesn't have a link for it for some reason
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
I don't have a solution, unfortunately, but I am experiencing the same issue.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
You said you were using "fastboot flash boot" twrp. If that is the command you used, it should be "fastboot boot" twrp
Sent from my Pixel 3 XL using XDA Labs
I had this too. The fix that worked for me. Haven't tried the time to reproduce is. When you fastboot boot twrp.img and it loads. Touch will stop.
Then reboot via buttons and get to fastboot again by buttons (power and vol down). Select recovery and wait for recovery to boot again. Once that happened touch worked again for me.
I tried various other versions of twrp and none work. But this did.
Again not sure if I can reproduce this as I have not had the time.
Also have not had the chance to try rebooting into twrp from system after flashing it to see if the issue continues.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
Don't fastboot flash the image. Put the twrp.zip file on your phone. Then boot the twrp.img. Once in twrp install the zip.
c_86 said:
I had this too. The fix that worked for me. Haven't tried the time to reproduce is. When you fastboot boot twrp.img and it loads. Touch will stop.
Then reboot via buttons and get to fastboot again by buttons (power and vol down). Select recovery and wait for recovery to boot again. Once that happened touch worked again for me.
I tried various other versions of twrp and none work. But this did.
Again not sure if I can reproduce this as I have not had the time.
Also have not had the chance to try rebooting into twrp from system after flashing it to see if the issue continues.
Click to expand...
Click to collapse
I could not get this method to work for me. I keep booting back into the stock recovery. It seems that my installation of TWRP is gone.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
What are you using for your screen lock security? If something other than PIN, try either setting it to PIN or None. There is a dedicated TWRP thread where you may find your answer or at least get more visibility.
lollyjay said:
You said you were using "fastboot flash boot" twrp. If that is the command you used, it should be "fastboot boot" twrp
Sent from my Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
That's what I meant. I was running on no sleep when I typed this. I was typing in the right command. Lol I just mixed up the old command with the new one when typing my problem out because the old one was fastboot flash recovery twrp...
jd1639 said:
Don't fastboot flash the image. Put the twrp.zip file on your phone. Then boot the twrp.img. Once in twrp install the zip.
Click to expand...
Click to collapse
Yeah. I accidentally said I typed in that command. I don't type in flash. I do use fastboot boot twrp.... I was just sleep deprived when typing out my issue. I do it the way you're supposed to, but it just doesn't work.
godraistlin said:
That's what I meant. I was running on no sleep when I typed this. I was typing in the right command. Lol I just mixed up the old command with the new one when typing my problem out because the old one was fastboot flash recovery twrp...
Click to expand...
Click to collapse
OK np :good:
Sent from my Pixel 3 XL using XDA Labs
v12xke said:
What are you using for your screen lock security? If something other than PIN, try either setting it to PIN or None. There is a dedicated TWRP thread where you may find your answer or at least get more visibility.
Click to expand...
Click to collapse
I use a pattern, but I tried it with no pin at all, and it's still unresponsive.
godraistlin said:
I use a pattern, but I tried it with no pin at all, and it's still unresponsive.
Click to expand...
Click to collapse
Ok, well I have always used a PIN for the screen lock and have never had a problem. I use the same PIN in TWRP. Worth a shot.
v12xke said:
Ok, well I have always used a PIN for the screen lock and have never had a problem. I use the same PIN in TWRP. Worth a shot.
Click to expand...
Click to collapse
I flash new ROMs almost weekly and have never had this issue. My last resort is to use the flash-all.bat putting the phone back to factory, and seeing if the issue continues.
gordopa1 said:
I could not get this method to work for me. I keep booting back into the stock recovery. It seems that my installation of TWRP is gone.
Click to expand...
Click to collapse
Ya I don't know then. That's what I did and got touch back. Might have been a 1 off
godraistlin said:
I flash new ROMs almost weekly and have never had this issue. My last resort is to use the flash-all.bat putting the phone back to factory, and seeing if the issue continues.
Click to expand...
Click to collapse
I flashed back to the latest stock image and TWRP was able to boot normally.
gordopa1 said:
I flashed back to the latest stock image and TWRP was able to boot normally.
Click to expand...
Click to collapse
Yeah, that's what I just did as well, and twrp is functioning normal again. I bet it had something to do with the way AOISP updates install. That's the only thing I can think of.
godraistlin said:
Yeah, that's what I just did as well, and twrp is functioning normal again. I bet it had something to do with the way AOISP updates install. That's the only thing I can think of.
Click to expand...
Click to collapse
That's the odd thing. I didn't do the ota I direct down loaded the zip and flashed it manually. And still had the issue but corrected it with my previous method.
I experienced the same TWRP gone after the update, but I flashed it again with Fk manager. It then booted perfectly into TWRP version 3.5. From there, I reflashed Magisk. Now all is working perfectly.
Sent from my Pixel 3 XL
Eudeferrer said:
I experienced the same TWRP gone after the update, but I flashed it again with Fk manager. It then booted perfectly into TWRP version 3.5. From there, I reflashed Magisk. Now all is working perfectly.
Click to expand...
Click to collapse
Fk manager?
FK Kernel Manager from Francisco Franco on the Google app store. It lets you flash any zip file, as well as tweak your kernel.
Sent from my Pixel 3 XL
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 ........)
so i permanetly installed twrp and was trying to put on a custom rom. I wiped everything and now twrp wont boot at all from the boot loader. i tried the temporary boot in fast boot and it still wont boot and i have no recovery os. PLEASE help to get andoid ten back on or anything i cant afford to loose this phone !
anntaoo95 said:
so i permanetly installed twrp and was trying to put on a custom rom. I wiped everything and now twrp wont boot at all from the boot loader. i tried the temporary boot in fast boot and it still wont boot and i have no recovery os. PLEASE help to get andoid ten back on or anything i cant afford to loose this phone !
Click to expand...
Click to collapse
TWRP is not compatible with Android 10. I hope someone can help you out.
i have twrp on my phone but cant install any apps the boot loader never shows up i keep getting error 7s when trying to install a rom. i just want to get the factory os back on. THere has to be a way
anntaoo95 said:
i have twrp on my phone but cant install any apps the boot loader never shows up i keep getting error 7s when trying to install a rom. i just want to get the factory os back on. THere has to be a way
Click to expand...
Click to collapse
Can you just flash back to a factory image??
Grab factory image from https://developers.google.com/android/images
And you'll be all set. Yes, you'll lose root and any data, but you'll be back on stock.
Thanks so much.so i tried flashing the os before and it failed. this time i went back and copied and pasted the fastboot files into the os folder with the script. It worked perdectly. I really want to put roms on my phone. I think i may have messed something up when installing twerp and formating and wiping the data
Afaik, twrp is not (yet) installable, so you'd have to
Code:
fastboot boot twrp.img
every time to access twrp. Android 10 is still very young, so have a little patience, and in couple of months you'll have plenty of fun with ROMs
And congrats for success, even if it is returning to stock.
calinorg said:
Android 10 is still very young, so have a little patience.
Click to expand...
Click to collapse
To be honest, I doubt TWRP will ever fully work on Q for the newer pixel devices. We have a logical partitioning system so it's impossible to mount /system /vendor and /product to be writable.
From what I've been hearing, custom rom developers have just been flashing their ROMs while in stock recovery. I'm going to assume that'll be the norm when Q ROMs are released for us.
Sent from my Google Pixel 3a XL using XDA Labs
I do believe someone will come up with a solution. If John wu managed to get magisk working (and rooting is ever so harder with new Android partitioning system), I don't see why couldn't we have twrp. Maybe it won't be installable, but it could work...