Related
Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.
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 !
Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/
Reserved!
Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?
Hurray for progress!
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478
This makes me smile. Thanks Troy and TeamWin!
Thanks Dees_Troy and Team for getting this started!
Things are looking up, thanks guys!
Awesome to see action with this phone! Thanks!!
You da man
sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.
Nice! Great to see the progress
Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324
sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?
cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs
Great to see...this is the start!
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
stevew84 said:
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
Click to expand...
Click to collapse
Is this when you fastboot into twrp, or do you have twrp already installed? Have you tried disabling screen lock before you enter twrp? And I assume you've run both bootloader unlocking commands as well?
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
stevew84 said:
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
Click to expand...
Click to collapse
Typically you need to have fully unlocked the bootloader with these 2 commands...
fastboot flashing unlock
and.....
fastboot flashing unlock_critical
Especially the critical, or else you won't be able to flash any roms. I don't know if skipsoft will do this. I know the Deuces scrip will. To find out what is/isn't unlocked run.....fastboot getvar all....
Then you'll know. If you have to unlock critical, which I think you will, it'll wipe your phone completely. So backup your files and such before you do :good:
Any manual methods that work? I mean to flash the roms.
stevew84 said:
Any manual methods that work? I mean to flash the roms.
Click to expand...
Click to collapse
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Badger50 said:
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Click to expand...
Click to collapse
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
stevew84 said:
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
Click to expand...
Click to collapse
Well that changes things a little. You at least have unlocked one partition then. And you can update factory images via fastboot? If so, then your fully unlocked. So you've got a twrp decryption error on slot B. You may want to disable screen lock security, and try again. You could also try fastbooting into twrp as well with screen lock also disabled.
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
stevew84 said:
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
Click to expand...
Click to collapse
Again, run the.....fastboot getvar all....and see what you get :good:
Thanks.
Badger50 said:
Again, run the.....fastboot getvar all....and see what you get :good:
Click to expand...
Click to collapse
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
stevew84 said:
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
Click to expand...
Click to collapse
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Badger50 said:
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Click to expand...
Click to collapse
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
stevew84 said:
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
Click to expand...
Click to collapse
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Badger50 said:
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Click to expand...
Click to collapse
Jesus christ. I'm in a cmd window right now, with the latest platform tools installed.
I ran the command just as you typed, (I'm in bootloader, bootloader version tmz20j by the way). Also, my bootloader version has changed a couple of times during all of this. It was tmz20bb, then tmz12g when I flashed the latest June image...now it's this 20j version.
Anyway, this is what I'm typing and this is what I get in return:
fastboot --set-active=b
fastboot: error: Device does not support slots
I'm at a real loss, obviously this damn device supports slots.
EDIT: OK hold on, when I flashed the June image bootloader version, ran the slot command in ADB, I was able to navigate to the right slot.
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
stevew84 said:
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
Click to expand...
Click to collapse
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Badger50 said:
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Click to expand...
Click to collapse
Thanks.
Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!