Related
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.
My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Try using adb to pull your files on your computer. Though since TWRP can't access internal storage, I doubt adb will.
You could also try to dirty flash the full ROM of whatever version of OOS you were using before (flash full rom in TWRP, wipe cache/dalvik, flash SuperSU or Magisk). This should restore most of your corrupted system and boot images. Since you tripped DM-verity, you will have to root again before rebooting. The no-verity/encript zip that's floating around the forums might also work? This shouldn't delete any of your user data, though I can't be certain if the dirty flashed ROM would be able to decrypt it.
Anova's Origin said:
Try using adb to pull your files on your computer. Though since TWRP can't access internal storage, I doubt adb will.
You could also try to dirty flash the full ROM of whatever version of OOS you were using before (flash full rom in TWRP, wipe cache/dalvik, flash SuperSU or Magisk). This should restore most of your corrupted system and boot images. Since you tripped DM-verity, you will have to root again before rebooting. The no-verity/encript zip that's floating around the forums might also work? This shouldn't delete any of your user data, though I can't be certain if the dirty flashed ROM would be able to decrypt it.
Click to expand...
Click to collapse
Try to dirty flash the rom you have now instaled. If you can't from TWRP, then try sideloading it. Good luck
Thank you for your tips, but didn't work
Tried wipe cache/dalvik -> sideload 4.0.2 -> sideload SuperSU -> fastboot twrp 3.0.3-0 (all of these I had before). And also only wipe cache/dalvik with a sideload of just the ROM, but I still get "Can not encrypt phone" when booting.
What does the SuperSU change in the system? And why does it not trigger dm-verity when flashing SuperSU, but when i remove it? I'm so confused. Is it even possible to get the phone in the same state as before uninstalling SuperSU, so it's bootable?
Systemless SuperSU modifies the /boot partition. Scripts have been added to the SuperSU installer to prevent dm-verity from detecting changes, which is why it doesn't get triggered when you root your phone after enabling system access in TWRP. Whenever you flash OOS (which has dm-verity enabled by default), you must root immediately before rebooting or it will replace TWRP with the stock recovery. Future attempts to enable TWRP without rooting will trigger dm-verity.
It's odd that you phone states that it cannot encrypt storage rather than decrypt it at boot. If you still have access to TWRP, try clean flashing OOS on your phone (use the wipe feature in TWRP). This will wipe /data and all your apps, but leave behind user files such as music and photos. Then flash OOS and immediately root before rebooting. Both SuperSU and Magisk will prevent OOS from attempting to encrypt /data on boot, which it does by default.
You didn't by any chance make a nandroid backup before unrooting did you?
Anova's Origin said:
Systemless SuperSU modifies the /boot partition. Scripts have been added to the SuperSU installer to prevent dm-verity from detecting changes, which is why it doesn't get triggered when you root your phone after enabling system access in TWRP. Whenever you flash OOS (which has dm-verity enabled by default), you must root immediately before rebooting or it will replace TWRP with the stock recovery. Future attempts to enable TWRP without rooting will trigger dm-verity.
It's odd that you phone states that it cannot encrypt storage rather than decrypt it at boot. If you still have access to TWRP, try clean flashing OOS on your phone (use the wipe feature in TWRP). This will wipe /data and all your apps, but leave behind user files such as music and photos. Then flash OOS and immediately root before rebooting. Both SuperSU and Magisk will prevent OOS from attempting to encrypt /data on boot, which it does by default.
You didn't by any chance make a nandroid backup before unrooting did you?
Click to expand...
Click to collapse
Sorry, I was wrong there, of course it's decrypt, NOT encrypt
I can flash twrp with fastboot and use it partially (says phone is encrypted, so limited options). I do not have access to /data or /system i belive, but I can sideload with the ADB function in TWRP. Tried to access files from twrp, but no go.
If dm-verity is not triggered when just flashing for example 4.0.2, why do I need to root it and install twrp? Is that so that I in some way could get it "un-triggered"?
Yep, I did a nandroid before, but was so stupid that I didn't backup to my computer. It's sitting inside the phone, encrypted
Dude I tried to unroot the N5X of my girlfriend the other day as snapchat didn't let us login with root. Phone was also decrypted, but after you boot it it will encrypt. If you stop the process (because you thought it was bootlooping, as those little motherf*****s don't tell when they are busy encrypting) and I am sure you did, the data is lost. That's exactly what happened to me. Don't try to encrypt or rescue anything. It wont work. Wipe the filesystem and start all over.
I am sorry though.
EDIT: I might be a little late, didn't check the date. But that encrypting stuff is serious, It should at least display a text with "ENCRYPTING..." or so. I let my phones encrypted since that day.
orreborre said:
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Click to expand...
Click to collapse
I don't understand why unrooting will have any problem with phone being encrypted.
I have done this unrooting process without a hiccup and my phone is also factory-encrypted so there's that.
What version of TWRP were you using? Try flashing the full OOS zip in TWRP but please flash the latest TWRP before doing so.
mharis05 said:
I don't understand why unrooting will have any problem with phone being encrypted.
I have done this unrooting process without a hiccup and my phone is also factory-encrypted so there's that.
What version of TWRP were you using? Try flashing the full OOS zip in TWRP but please flash the latest TWRP before doing so.
Click to expand...
Click to collapse
I believe what they meant was they were unaware their phone was decrypted. Unrooting will cause the phone to begin encrypting on boot, and I imagine OP cancelled it (as the phone does not say when it is encrypting)
orreborre said:
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Click to expand...
Click to collapse
I had a different issue but same like this....
i unrooted my phone and my device was decrypted.....
after reboot the phone encrypted automatically and all my datas were lost...
the dm-verity was are triggered....
Hello, I just unlocked my bootloader and want to check out Havoc OS.
I downloaded latest TWRP and Havoc OS and followed the [All-in-one] guide here. Everything worked fine but, after I bootloader into TWRP for the first time the storage is encrypted and I can't see the internal storage. If I reboot, I am losing TWRP and stock recovery is showing up.
I can't flash from sdcard as it gives either error 1 or error 7. How can I permanently flash TWRP and Havoc? I don't mind a factory reset.
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:
I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!