Hi all,
- bootloader is unlocked
- I have latest OOS installed (9.09 I think?)
- twrp codeworx 3.3.1
- Magisk installed
- developer options enabled, adb enabled
And here's my issue:
- downloaded latest magisk as zip file
- selected reboot to recovery
- twrp asks me for password, I enter my NIP but says "Can,t decrypt data'"
- Provides no option to reboot to system...
- rebooted, goes again to twrp
- rebooted to other menu where you can select fastboot, recovery, system when selecting system it goes to recovery...
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Suggestions welcome guys, I'm at the office and can't try anything now but definitely need input before I screw up things even more
Thanks
liberteus said:
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Click to expand...
Click to collapse
So... Got home, booted via fastboot the PREVIOUS twrp recovery (i.e. NOT this one https://sourceforge.net/projects/ch...rkx-signed-forcedecrypt-dumpling.img/download) and it gave me the option to actually cancel the password and keep the system read only. At which point I was able to reboot to system, and that's it, fixed.
I'll flash the twrp version that got me out of my self digged hole now.
Here's the version I used: twrp-3.2.2-0-20180721-codeworkx-dumpling.img (2018)
Related
Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9
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.
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.
Solved. Just install as described in https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
(before that I restored recovery, sys and boot from backup)
Still TWRP doesn't work... but who cares
Hi,
I tried to root my Moto Z2 Play but I somehow failed.
I can still boot into fastboot and boot twrp from there. but that's all that works.
I tried booting into recovery from twrp which was booted via
Code:
fastboot boot twrp.img
but this results in "no command".
Everything else just shows "your device has been unlocked and can't been trusted". Cannot turn off phone.
I followed this guide
https://devsjournal.com/how-to-root-moto-z2-play.html
but the downloads linked were down, so I tried to replace with more official looking downloads (see below)
I did these steps:
- unlock bootloader - I think this succeeded
- temporary boot twrp from fastboot
- wipe dalvik, data and cache
- backup everything except what I wiped
- other than the guide said, I did not install anything as I didn't have the files on the SD card
- I accidentally rebooted and the device started encrypting again
- I booted fastboot and flashed twrp-3.2.3-0-albus.img (by Junior Passos) into recovery
- I tried around with booting and finally was in TWRP again
- wiped again because of encryption (twrp said is was able to decrypt with standard password?)
- installed universal-dm-verity-forceencrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- installed Magisk 20.4 from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- after that booting did not work any more
- installed https://www.themefoxx.com/dm-verity-forced-encryption-disabler/ version 6.0 (guide mentioned version 5.1 from a different download) in the hopes this would solve the problem, but no.
Any idea how to recover? how to successfully root and TWRP?
Which partitions did the install-zips modify, so which backups should I restore?
thanks