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.
Related
Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.
GO!
SunEpicMist said:
Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.
Click to expand...
Click to collapse
try this
https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Restore to latest Marshmallow firmware.
Be sure to have locked bootloader (both from ADB and developer settings), then upgrade via OTA.
You just have to check and confirm for update.
It worked for me
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.
Hello,
On clean G5s, I followed the guide bellow, in order to unlock bootloader, install TWRP and get root. I successfully unlocked bootloader, installed TWRP, flashed Magisk.zip with TWRP but then, the device is unable to boot the system. It only boot on TWRP.
https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200
The warning message on boot is displayed, then after 1 minute, only TWRP started. I can still access to bootloader (with vol. down+pwr). If I select reboot system, in bootloader or TWRP, the device still reboot in TWRP only (after 1 minute of warning message "unlocked device...").
I think the device is bricked.
Could you tell me how to unbrick it please?
Thanks in advance.
philippe734 said:
Hello,
On clean G5s, I followed the guide bellow, in order to unlock bootloader, install TWRP and get root. I successfully unlocked bootloader, installed TWRP, flashed Magisk.zip with TWRP but then, the device is unable to boot the system. It only boot on TWRP.
https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200
The warning message on boot is displayed, then after 1 minute, only TWRP started. I can still access to bootloader (with vol. down+pwr). If I select reboot system, in bootloader or TWRP, the device still reboot in TWRP only (after 1 minute of warning message "unlocked device...").
I think the device is bricked.
Could you tell me how to unbrick it please?
Thanks in advance.
Click to expand...
Click to collapse
Once again flash the stock rom and then try to flash twrp again
Which twrp did u flash
I get the feeling that you dont have an os installed.
Anyway, I'd suggest you do the following:
- get a micro sd card
- in TWRP make a complete backup first (to micro sd)
- backup all your personal data (pictures etc) if there is any (to external storage such as micro sd or computer)
- format data under 'advanced wipe' and also wipe caches and system
- copy e.g. lineage 14.1 (https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918) to your micro sd and flash it from there..
If the flashing procedure was successful (I don't see why not) you are now running the latest lineage os for our device (android 7.1.2) which now you can root by flashing magisk..
good luck
Unbricked
Done!
Unbricked and rooted successfully my G5s (XT1794, Android 7.1.1) with Linux.
Here steps followed:
https://forum.xda-developers.com/showpost.php?p=77180604&postcount=33
Hello, I haveNokia 6.1 (2018) and I have just got it into a strange state. It happened during custom rom install, or to be more precise during the set-up (probably). I have finished setting up the Omni ROM from this thread (https://forum.xda-developers.com/nokia-6-2018/development/rom-omnirom-t3945850) and wanted to install magisk to have root.
After downloading the .zip file, I rebooted into TWRP (through the fastboot mode and using the "fastboot boot image.img" command) and TWRP asked for a password to decrypt the storage. I tried password that I am pretty sure is correct, but the TWRP insisted it is incorect. I tried several variations to it in case I made a misclick during a setup but no luck. I wiped everything (system, cache, data, sd) and through a fastboot mode I uploaded stock boot, vendor and system to both slots.
After the reboot, I am stuck on the password (system PIN, to be precise - not the SIM PIN, that is OK) screen. When I enter an incorrect PIN, it will say that the PIN is incorrect, but when I enter the correct one, screen just goes black for a while and I am back at the screen to enter the PIN.
Is there a way to get out of this mess? I am able to get into fastboot mode and boot recovery.
Any help would be much appreciated.
More details about the process as I forgot to include. TWRP used was 3.2.3 from this thread (https://forum.xda-developers.com/no...recovery-twrp-3-2-3-0-touch-recovery-t3825545). Stock FW (Nov 2019 version) used was from this thread (https://forum.xda-developers.com/no...de-how-to-make-backups-restore-stock-t3889815)
Before the OMNI ROM install I have tried stock system with custom vendor (version 2.2 from the thread linked in the OMNI ROM thread) which could also contribute to the failure, but the phone did not even boot (it got stuck on the "android one" logo). I hoped that I could at least get the ability to convert SD to internal storage, as that feature is disabled on stock, but with custom vendor it works (tested on the OMNI rom, which I managed to install correctly before)
I have also found here an OST tool, which could potentially help with the situation (I am not sure) but I am missing the original firmware files to use with this tool.
The problem must be with the internal storage encryption, which got messed up in the process (I am not still sure, what went wrong). Am I correct that now I would need to find the original loadout (is there something as RUU available fror this model?) and basically revert everything including the bootloader unlock and start from the begining? Could someone here point me in the right direction how to fix this issue?
If the only way is to pay someone to fix this issue, I will gladly provide any reasonable amount if it will resolve my problem.
So all I had to do was boot into TWRP and do a factory reset from there. How stupid of me that I did not try this.
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.