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!
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 !
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
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space
mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.
Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system
Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?
mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?
airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.
airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!