Related
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
You don't flash a factory image in TWRP. Unzip the file and flash the individual images: boot, system, and vendor. Try that method or use ADB sideload to install the full OTA image. Full OTA images can be downloaded from the same site.
Sent from my Nexus 5X using Tapatalk
I'm assuming you have ADB / fastboot in place (if not, google it): unzip your factory image to a given folder. Navigate to this folder using prompt / terminal. Turn on your phone with vol down pressed and leave it at that screen. Plug it onto your computer and type fastboot devices - you should see a line with a bunch of numbers. If Windows, run flash-all.bat. If Mac / Linux, run flash-all.sh. Your phone should get back to life in a few, sit back and relax.
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
wizardwiz said:
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
Click to expand...
Click to collapse
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
ultyrunner said:
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
Click to expand...
Click to collapse
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked.
I wasn't talking about using a manual fastboot option to flash an indevidual image.
wizardwiz said:
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked. I wasn't talking about using a manual fastboot option to flash an indevidual image.
Click to expand...
Click to collapse
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
ultyrunner said:
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
Click to expand...
Click to collapse
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
wizardwiz said:
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
Click to expand...
Click to collapse
No we're not in competition. My point was you gave him one option with the least control and not remotely the best option to get his device up and running, particularly making an assumption he has a locked bootloader, when you never asked. If he is able to use a command line to run a flash command, then pointing him to the guide is the best bet. If something goes wrong with flash-all scripts then he's probably going to be really lost.
I am following this guide here to root oneplus 6t (european variant), 9.0.5 Android:
https://www.xda-developers.com/onepl...otloader-root/
bootloader is unlocked and I can see there is a positive connection between phone and PC by checking the output on adb devices and fastboot devices. both work as intended.
the problem is that when I try to adb sideload, it says that I need version 1.0.32. so this means I cannot flash the custom recovery.
any tips? been looking online for quite some time now and cannot figure out what to do anymore. where can I find this 1.0.32 adb version?
I am a long time user on nexus 5 and just bought this phone, want to root it aswell. (note: this does not mean I have high level of knowledge on these types of hacks, just wanted to have this clear.)
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
nikexv2 said:
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
Click to expand...
Click to collapse
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
cesar.maranhao said:
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
Click to expand...
Click to collapse
You need to flash the zip from within the recovery that you booted using adb, not sideload it.
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
cesar.maranhao said:
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
Click to expand...
Click to collapse
wrong twrp used. you correct twrp and it will work. like this twrp https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752 or https://forum.xda-developers.com/devdb/project/?id=27466#downloads the choice is yours alone to make.
you are asking for help with 6t in the 6 form. whats wrong with this? you should be at this link https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...
cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot
Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.
Everytime I try to boot twrp It says waiting on device. What's that mean
[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.
After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!
Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
SMcC2 said:
Attempted to update from the latest stable 10.3.12 to 11 by flashing the full OTA zip in TWRP.
Install failed and phone locked up.
Attempting to boot to recovery or system results in Qualcomm Crashdump Mode.
I can get to Fastboot, but I'm not sure if I should try flashing twrp.img or pull boot.img from the OTA or what.
Anyone have any suggestions?
Click to expand...
Click to collapse
An attempt to flash TWRP and reflashing should go.
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
I did not have time to wait so before bed I just reset everything.
I ended up using the MSM tool located here:
The Complete Guide to Unbrick OnePlus 6/6T from a Hard-Brick using MSMDownload Tool
Unlocked bootloader, installed TWRP & Magisk, installed A11 zip, everything is working again now.
Good luck!
BenoMosko said:
Hi,
I'm having kinda same issue.
I'm on stable A11 oneplus 6t,
i'm trying to boot into twrp in order to install new recovery and root with magisk.
when fasboot boot twrp.img i'm getting a qualcomm crashdump.
tried different twrp img's with no success..
maybe someone figure it out?
thanks
Click to expand...
Click to collapse
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Artificial_Intelligence said:
Hey, I'm having the same issue. Did you end up figuring out how to solve this?
Click to expand...
Click to collapse
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
s.seila said:
Flash temporary recovery first ( lineage recovery ) then from fastboot.. boot into recovery.
You will see lineage recovery.
Select apply update - > update from adb ....
Then "adb sideload <twrp image>.img...
(probably it ask to verify choose yes)
Go back select advanced restart ( not sure the right word ) -> reboot to recovery.
Then you will have twrp installed.
If you only want to root why not flash magiskpatched image there no need TWRP just to root.
Click to expand...
Click to collapse
Hm but how would I install lineage recovery? Flashing recovery through fastboot doesn't work on the new devices anymore right?
I also tried booting lineage recovery without flashing but that also didn't work (although it didn't get stuck on crashdump but booted into the regular OS instead).
I did notice that it seems to be related to OOS 11 firmware. On 10 booting into TWRP works just fine and as soon as I upgrade to 11 it stops working (maybe this means it's fixable?). What I used as a workaround for now is to have 10 firmware in one slot, upgrade other slot to 11 and flash TWRP to both slots from the 10 slot. Seems to work so far but is not ideal IMO. I'm not a developer sadly but maybe someone smarter than me will come up with a solution.
What do you mean by "new device"?? New OOS version right??
I use this method all the time with oos 11.x.x.x.x to install TWRP so i can install Custom ROM later.
no need to go to oos 10 you can flash it from newest oos11.
---------------------------------------------------------------------------------------------------------------
First boot into fastboot mode.
to install lineage recovery
fastboot flash boot <lineage recovery image>.img
download from here https://download.lineageos.org/fajita
menualy select and boot to recovery. It will boot to lineage recovery.
lmao it appear in two posts. deleted 1.