Bricked my OP8T (unlocked bootloader, rooted) in a failed OS update attempt. I'm pretty sure I was running OS 11.0.8.12, attempted updating to 11.0.11.11 following Magisk OTA update instructions to keep root. It seemed to mess up as when I viewed OS info, 11.0.8.12 was still listed, but then phone calling, wifi, audio all were broken. So I then attempted the local upgrade option, which didn't work at all. After rebooting, found myself in Qualcomm crash boot, but was able to still get to fastboot using Vol Up + Vol Down + Power key combination.
I've attempted switching active boot slots and that didn't fix anything. My slot a seems to have considerable issues so been trying to reflash images to b slot. I've extracted all images from payload.bin from both 11.0.8.12 and 11.0.11.11. I also have magisk patched boot images for both versions of OS's on my PC. When I've attempted flashing 11.0.11.11 system image, I get errors regarding can't resize partition, not enough space. I've tried 'Fastboot delete-logical-partition product', but still received same error. So I've thought, I'll just reflash the 11.0.8.12 images and try to get my phone back to bootable.
I've ran the following commands to attempt to get back to bootable phone:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot bootloader
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot--disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot bootloader
Issue is now that whenever I attempt to reboot the phone, it automatically boots back into fastboot :/ I've attempted wiping the cache too in hopes it would help but no dice.
Curious if there is a way to recover the phone without wiping my data partition. I've got most apps and settings backed up but it's still a hassle I'd prefer to avoid. Would it be possible to boot into TWRP using 'fastboot boot twrp.img' to pull the user data partition to local pc? Then wipe the phone and install fresh OS? I've heard that twrp can't decrypt the user data partition for stock OP Roms?
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Qnorsten said:
TWRP have always been able to decrypt user data for stock OOS roms. The latest twrp version can even flash OOS rom (thanks to a patch by a helpful community member).
If I where you I would try to boot latest TWRP and see if that can decrypt the data (do not freak out if it can't there might still be a way to save the data).
If it can decrypt data I would perform a backup of the data partition and then copy your whole internal sd over to your computer just to be safe.
After that I would try to flash the latest OOS ota in TWRP and see if that fixes it. If not you can try to format data and reboot. If that fixes it you can just restore your data backup. If that don't work I would use the MSM tool and then unlock bootloader and restore data backup.
If TWRP are unable to decrypt the data I would sideload the OOS ota in TWRP and see if that fixes it (it did for me when I had a similar problem). If not your data is lost and you might need to use MSM tool.
I would wait to install magisk until I made sure everything boots without it.
Click to expand...
Click to collapse
Unfortunately I wasn't able to get TWRP to decrypt my data :/ Tried using TWRP with stock boot image flashed as well as with magisk patched boot image.
Tried using the following guide here to see if I could make it happen while saving my data but was unsuccessful. Ah well, glad I use Swift Backup and SMS Backup & Restore. Should make restoring phone to prior state a bit easier, but still a little pain in the butt.
I'm pretty sure I've run into issues in the past with upgrades on OnePlus and new versions not being able to decrypt previously encrypted user data. Hence why I was resistant to upgrading for the last 5 months. Hopefully the upgrade to the december update goes a little smoother.
Appreciate the advice/guidance @Qnorsten!
Sorry to hear that didn't help. I never had any problems with any updates, except when I was messing around with TWRP and that was my own fault.
Older OOS versions can't decrypt data from newer versions but if you flash a newer one it should work.
Have you tried sideloading the latest full OOS ota zip in TWRP?
Related
Has anybody tried this... If so does it work? https://www.xda-developers.com/lineageos-15-1-resurrection-remix-available-project-treble/
Feel free to give it a try!
Flash the system image from TWRP, reboot to recovery, then flash Gapps (if desired). Keep a backup factory system image handy if needed.
@Telperion I wish I could... Unfortunately I don't have the pixel 2. I am very much thinking about buying one though.
I'm sure it works, there's just not been much need to run a custom ROM. I'm on P DP1 and there's not yet a P GSI so I'd have to downgrade to 8.1 before flashing.
Telperion said:
Flash the system image from TWRP, reboot to recovery, then flash Gapps (if desired). Keep a backup factory system image handy if needed.
Click to expand...
Click to collapse
When I tried installing TWRP on my Pixel 2 a few days ago, I found the ui does not respond to screen touches.
It might be simpler to just use fastboot flash a GSI.
Note that to get a GSI to work on the Pixel 2, you also need to adjust the contents of the "vbmeta" partition, which can be done using "fastboot".
There are details about it here https://github.com/phhusson/treble_experimentations/wiki
Can confirm lineage, resurrectionremix and aosp gsi by phh all work, although the twrp bug jamuir mentions did occur for me. I got around this by just flashing the gsi through the bootloader and not twrp. If you want to flash some gapps after flashing system and vbmeta (needed for pixel2), just fastboot boot twrp.img instead of rebooting to recovery. Here are basic steps I followed:
clean flash phone or do a factory reset from twrp, then boot to bootloader
fastboot flash system system-arm64-ab.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img #from factory image
#and if you want gapps
fastboot boot twrp.img
adb push opengapps.zip
flash your gapps
You'll get the "vendor mismatch" warning we've all come to know and love, as well as a "Hardware Overlay Picker stopped working" message on startup. Other than that, they all work.
I understand the premise of project treble, but I wonder what's the implication for custom rom developers. I'm probably mistaken, but it seems like they could just do a one-size-fits-all build for all devices now?
The twrp "not responding to touch" bug happens when you reboot into recovery straight from system using the advanced reboot menu. To prevent this, simply power off the device, and use the button combination to boot into twrp, voila, touch is now working.
Got my pixel from swappa the other day. So far I:
1. Unlocked the bootloader
2. temporarily booted into TWRP 3.3.0-0 (3.3.1-0 wouldnt let me format for some reason)
3. Installed the most current microG lineage build. (and then also flashed magisk 19.3 immediately after)
It boots into lineage, but when I boot into recovery, it gives me the lineage recovery. Since when does lineage wipe out twrp?
I tried sideloading over adb and also right through the temporary twrp, but it doesnt make a difference. Also - in lineage, I see no sign of magisk - which is normally there after installing a rom and then magisk.
I also tried the twrp-pixel installer.zip, which also did NOTHING.
Am I missing something? This is my first phone with the weird dual partitions - is that why its so weird? Ive never had this problem before.
EDIT: Also when trying to flash twrp via fastboot it gives me
"(bootloader) Flashing active slot "_a"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.016s"
Hi mate, here's a link regarding the lineage recovery thing. It may explain some of what you have occurring.
https://lineageos.org/Changelog-19/
I had twrp on my pixel a while back and it was sticking so not sure what that's all about. If you have booted twrp.img, flashed ROM, flashed twrp zip and rebooted it should be on both slots. You may need to activate root in Dev options to get root up and running, been a while since used it so that might not be accurate as currently on Q.
after flashing a rom you need to flash the twrp-pixel installer.zip right after. Then reboot into recovery (dont need to fastboot since the zip installs twrp to the boot.img ramdisk) to switch slots (switches automatically). Back in recovery you can install magisk.
Devices with A/B partitions do not have a recovery partition. What we think of as recovery is actually part of the boot.img file. When you update the OS, you update the boot.img. The TWRP installer .zip finds and unpacks the boot.img, then modifies it to make the device load TWRP instead of stock recovery. By default, the TWRP installer installs to both A & B partitions. If you screw something up (like flashing the wrong version of TWRP, for example) and put yourself into a bootloop, you can often recover by simply flashing the original boot.img file with fastboot flash boot boot.img .
Here's an article which was written by XDA to help explain the differences in how A/B phones work, and the ramifications for us flashers:
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
restoring a TWRP backup is successful, but on boot the phone locks up with this error.
dm-verity device corrupted
"kernel_restart"
it will not continue. i still have TWRP installed. but cannot restore.
i tried running the following commands with no change
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
any ideas?
mlkemac said:
restoring a TWRP backup is successful, but on boot the phone locks up with this error.
dm-verity device corrupted
"kernel_restart"
it will not continue. i still have TWRP installed. but cannot restore.
i tried running the following commands with no change
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
any ideas?
Click to expand...
Click to collapse
Can you boot TWRP still? If so, restore Data ONLY, flash full OOS zip version the backup is from, twrp installer, reboot twrp, flash full OOS zip again, TWRP installer, reboot twrp again, flash magisk and other mods you have/had/want. If you can't access twrp, use fastboot ROM to restore your phone.
how can I reset my phone so it boots. Do I need to fastboot flash oxygenOS or can I just install the zip file through TWRP?
Would fastboot flashing 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip work?
doctor_whooves said:
how can I reset my phone so it boots. Do I need to fastboot flash oxygenOS or can I just install the zip file through TWRP?
Would fastboot flashing 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip work?
Click to expand...
Click to collapse
Hard to say, without knowing how your phone got into this (no boot) state. What other things you tried, etc.
Fastboot flashing the (stock fastboot) ROM may work. As you figured, it will restore stock ROM and wipe the device. Can't be installed with TWRP, as far as I know.
If you have (or find the right) full OTA zip, you should be able to flash that with TWRP.
I been trying to flash some system images I find on the treble forum and nothing is flashing.
My bootloader is unlocked and I'm rooted with magisk
Whenever I run "fastboot erase system" I get a permission denied error and doing "fastboot format system" I get an error about a raw filesystem
Trying to flash an image without wiping I get an error about resizing the system partition.
Am I doing something wrong? It's been years since I've tinkered with Android so I'm out of the loop on Android's dynamic partitioning etc etc
Edit: Figured it out
https://forum.xda-developers.com/mo...de-how-to-flash-generic-image-moto-g-t4131199
for anyone wondering, i just figured it out, the moto g stylus has 2 fastboot modes? one is the bootloader (adb reboot bootloader) and the other is fastbootd (adb reboot fastboot)
booting into fastbootd solved my flashing and wiping issues
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
Code:
adb reboot fastboot
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
ilia3367 said:
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
Click to expand...
Click to collapse
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
DMedina559 said:
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
Click to expand...
Click to collapse
Same boat. Bootloop if I try to get it to start unencrypted. Booting at least once into a clean boot, then flashing without formatting first let me patch magisk. Have a suspicion the phone isn't too happy about being unecrypted.