I do have a decrypted OP5 and I did try to flash both the latest OOS stable & the latest OB and to run it unrooted.
After wiping everything but the internal storage and flashing latest OOS, I did flash the "No Verity" and did reboot the device.
It shows the unlocked bootloader warning, the first Android boot screen and right after that, when it normally would go to the boot animation screen, it kinda rapidly restarts, gets back to the unlocked bootloader message and after that it boots back into TWRP.
The outcome is always the same, unless I flash magisk after the No Verity. Doing so it boots into the OS with no problems whatsoever.
Does it has something to do with the decryption or what should I do in order to run it without root of I want to?
Related
Hey,
I had AOSP rom and i decided to go back to OOS. (xXx rom)
I entered TWRP, Cleaned Data,Cache,Dalvik,System.
And Factory reseted it.
Installed the xXx rom, and i got on the splash screen instead of "Bootloader Unlocked"
And i'm getting "<!>"
And i couldn't boot.
And i can't press volume keys to get to recovery or bootloader, but it boots straight to bootloader.
i entered to TWRP again (Via bootloader), reflashed stock OOS.
It booted, and then i entered bootloader to flash TWRP again, and it didn't succeeded
I enter only Stock Recovery and every time i try to flash Recovery it's succeed but it's does nothing, still entering Stock OOS recovery.
Now i stuck at stock OOS, and stock rocevery.
Can't flash anything.
Can someone tell me what to do?
Best is via ADB flashing latest BlueSpark TWRP (fastboot devices, fastboot flash recovery (name of TWRP).img and then format all so you start with a clean plate. Then move your ROM from PC to Internal and proceed further. But IMO a "format" is needed. Also siakantabg made a flashable zip from the old bootloader. Flash this zip in TWRP first after formatting en wiping everything.
Link old bootloader: https://forum.xda-developers.com/oneplus-5/themes/mod-bootloader-changer-t3800862
Android Nougat AQDG
Flashed TWRP but it booted to phone, then locks up at boot screen. This is usually dm-verity at work. Flashed stock firmware but phone still won't boot to recovery, verity appears to kick in immediately upon first boot.
How to get past this?
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com
I have a Huawei P10 Lite WAS-LX1. I had its bootloader unlocked in a phone repair shop (by shorting testpoint).
Now it always greets me with the message "Your device has been unlocked and can't be trusted".
I can load the boot into the bootloader and I can flash TWRP (I tried 3.4.0 and 3.3.1 from DarkJoker360 and also the one from Pretoriano80).
I am also able to flash system images, for example LineageOS from DarkJoker360.
At first that seemed to work to some extent: the new system kept crashing but at least it was booting.
I tried again and again and at some point I wiped everything but the sdcard using TWRP (that is, including the vendor partition). I suspect that's what I did wrong, because presently I can no longer boot into the ROM I am flashing. Instead, the phone waits for a few seconds, then vibrates once and restarts. The second time, it boots into "Huawei eRecovery" (where I can "Download latest version and recovery", "Wipe data/factory reset", "Reboot" or "Shutdown"). I am afraid of attempting to go back to the stock ROM as I wouldn't want the bootloader to become locked again.
Since I can still boot into both the bootloader and the recovery, I have hope I can recover. But I don't know how.
Does anyone understand what happened (and could explain)?
Also, does anyone know how I could boot into the ROM again?
Never mind. I went back to stock. Also, the bootloader became locked again during the process, so I will not try again.
Hi - I am trying to update my OP6T to OOS v11.1.2.2 and keep root.
I patched my boot.bin file, and was attempting to boot the phone into TWRP in fastboot to create a backup before proceeding.
However, when I try to boot into TWRP using fastboot boot twrp-3.6.2_9-0-fajita.img, I always end up in Crashdump mode.
Is there a way for me to fix it?
Thanks,
¿GJ?
OK ... I was able to boot into TWRP v3.6.2 and create a phone backup after I swapped slots and then pulled some shenanigans. I doubt that the backup is really usable, though, based on what I needed to do to create it.
So, this appears to be my current configuration:
I'm currently on the previous version of OOS 11
I'm rooted with Magisk v25.1
One slot bootloops into TWRP
The other slot boots up into OOS 11 fine, but can't boot into TWRP - even when booting into a TWRP image through fastboot mode.
How can I clean this up? And, how can I upgrade to OOS v11.1.2.2, keep Magisk root, and not lose any data in the process?
Do you have a Android 12 Custom Rom installed