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 ........)
Related
Got my Pixel XL and updated to NMF26O 7.1.1 by OTA. Then, unlocked bootloader, flashed TWRP RC1 and SuperSU V2.79 SR1. Worked no problem as well as did TWRP backup twice. I noted that Slot B is being used when I rebooted from TWRP.
Tonight, I flashed custom kernel, FK-R6, by using "fastboot flash kernel fk-r6". It said flashing ok and I rebooted. Surprisingly, the Pixel boots back to its former version of NDE63H 7.1, as well as the kernel is remain stock. Of course, the root was gone, but, all app and data are kept.
Booted TWRP and found Slot is A is being used. So, I changed back to Slot B. Rebooted and it still remains NDE63H.
My question is how to keep boot Slot B and in case I can keep boot with Slot B, does the custom kernel keep? I read something about a setting in TWRP to keep the Slot. But, I am not experience to make sure what to do next.
And any possible cause the change the boot to Slot B?
One more dumb question, what if I flash bootloader, recovery, kernel and etc to both Slots to ensure the system and setting keep to the same?
Million Thanks
CK WONG
I'm not familiar with Franco's kernel, I use ElementalX. I've never had a problem with it and I like that it can be flashed from TWRP.
As far as the OTA, everytime you flash an OTA, it will be flashed to the opposite Slot so you may want to try starting in Slot B, sideload the OTA from within TWRP RC1, reinstall TWRP, SU and kernel to see it it works.
lightning413 said:
I'm not familiar with Franco's kernel, I use ElementalX. I've never had a problem with it and I like that it can be flashed from TWRP.
As far as the OTA, everytime you flash an OTA, it will be flashed to the opposite Slot so you may want to try starting in Slot B, sideload the OTA from within TWRP RC1, reinstall TWRP, SU and kernel to see it it works.
Click to expand...
Click to collapse
Thanks for your quick reply.
It seems setting the slot by TWRP cannot make the change stayed. As, I have flashed custom recovery, I would think of a fresh install by fastboot commends. At this time, I can only think of three options:
1. Try the "fastboot --set-active=_b". But, I am not sure the Slot B is okay or not. Perhaps, the bootloader detects something wrong on Slot B, then, it automatically changes to Slot A;
2. Restore the nandroid of NMF26O to slot A by using TWRP. But not sure it will restore to Slot A as wish; or
3. Update the NDE63H to NMF26O by using fastboot commend that equal to a fresh install of which is my last resource.
I hope some of you can enlighten me comments.
CK
P.S. Just tried using TWRP to set to Slot B. Reboot to bootloader and read boot to Slot B. However, the phone restarted three times and goes back to Slot A boot. I wonder whether the flashing of kernel on Slot B was unsuccessful or not.
Anyone know the any command to check the Slot contents by using fastboot?
smallvan said:
Thanks for your quick reply.
It seems setting the slot by TWRP cannot make the change stayed. As, I have flashed custom recovery, I would think of a fresh install by fastboot commends. At this time, I can only think of three options:
1. Try the "fastboot --set-active=_b". But, I am not sure the Slot B is okay or not. Perhaps, the bootloader detects something wrong on Slot B, then, it automatically changes to Slot A;
2. Restore the nandroid of NMF26O to slot A by using TWRP. But not sure it will restore to Slot A as wish; or
3. Update the NDE63H to NMF26O by using fastboot commend that equal to a fresh install of which is my last resource.
I hope some of you can enlighten me comments.
CK
P.S. Just tried using TWRP to set to Slot B. Reboot to bootloader and read boot to Slot B. However, the phone restarted three times and goes back to Slot A boot. I wonder whether the flashing of kernel on Slot B was unsuccessful or not.
Anyone know the any command to check the Slot contents by using fastboot?
Click to expand...
Click to collapse
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
smallvan said:
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
Click to expand...
Click to collapse
Use Google's flashall bat. That should flash both slots.
Sent from my Pixel XL using XDA Labs
smallvan said:
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
Click to expand...
Click to collapse
Use a modified flash all so that you tell it to skip slot A. Should put slot B back to stock
aholeinthewor1d said:
Use a modified flash all so that you tell it to skip slot A. Should put slot B back to stock
Click to expand...
Click to collapse
Thanks you guys kind words. Just reflashed back to stock 7.1.1 with user data erased. Have to re-do root and settings from the beginning.
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 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
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.
This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.
ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on