Develop Bugs

Rooted, No Gapps and can't access TWRP (V500)

So basically I flashed TWRP and it worked. Then, I installed pure AOSP ROM (forgot which one) without the gapps. And that's when I realize, I haven't really root the ROM and when I try to get to TWRP via buttons, it didnt work. It shows that secure booting error and cause : boot certification verify.
Can anyone please write the procedure to boot to TWRP again? Thanks in advance.
(Please note that I don't have root and GAPPS, so no flashify etc. Also, I have an unlocked bootloader)

Enable USB debugging and try ADB:
Code:
adb reboot recovery

Another way with the hardware keys:
http://forum.xda-developers.com/showthread.php?t=2712647
I just tried it and you can confirm the factory reset 3 times as described without having a real factory reset. Instead of a factory reset it just starts TWRP after a short while.

Cannot update 3.2.8 to 4.0.1 without getting dm-verity warning

So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again

Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.

Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups

install beta 7 firmware

Don't bother! It's not worth it! It's just a stupid message!

I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.

It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .

cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.

bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip

Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh

I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.

Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.

Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards

I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

startup problem after installing new ROM by TWRP

after receiving a phone with a problem Gyro sensors and aceelérmetre, I tried to solve the problem by installing twrp and trying other ROMs, but one moment the phone does not want to start and stays every time in the start screen installation infinitly
i still have access to twrp, and i tried all knowns solutions except flashing throw EDL mode
Please help me

More details required!
What rom did you try to install.
And before testing other roms. You should have checked that it wasn't a hardware problem (faulty device) with stock rom.
^^^ Tap on kernel version a few times in about would open a service menu, where it is possible to test hardware.
MIUI doesn't boot with TWRP installed if you don't flash lazyflasher or use a TWRP version that includes it.

Question: does your phone stay permanently in this mode? What rom did you install and what type of ARP do you have? What version of twrp do you have? I remember I had the same issue because I force encrypted my phone accidentally but then it just didn't start sometimes. That's why I am asking.
Option 1: go back to twrp -> format your device (should erase all sort of encryption and it has the same effect as a factory reset as well) -> reinstall custom rom and your stuff again -> flash lazy flasher or Magisk (that should take care of dm verity & force encryption as well).
Option 2: check your ARP version (fastboot getvar anti) custom roms usually don't have any firmware whatsoever and as long as you don't downgrade you are safe anyway. Just to be safe: if you are on version 3 everything should be fine, if you are on 4 you have to do some research what to do but it's not a big deal to be honest.
Option 3: Install redwolf instead of twrp (then you don't need to flash lazyflasher as well) -> install rom.
Tell me if anything has worked.
Installing recovery either via fastboot flash recovery recovery.img -> power off -> power on + volume up -> allow modification to system partition.
Or do it like fastboot boot recovery.img -> install (in your recovery) -> select image (bottom right) -> flash recovery.img (works especially good with ARP v4)
Either way after that do your thing in case you want to change/update your twrp or redwolf.

Boot screen problem
I am using orange fox recovery r10. When i flash havoc os 3.0, evolution x os and other os it always stuck in boot screen. It just opens with the pixel experience rom only. And when i tryed to restore my phone rom it shows "mount read only" . I am using redmi note 5 pro (whyred). Please help me to solve my problem.

if i were you, i will boot to twrp - boot to fastboot - flash miui using fastboot. if you're not confident google how to do it.

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!

mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.

Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps

mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.