I'm having a strange issue when flashing updates and magisk on my s21 ultra
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
Only way to fix it is to do factory rest or flash normal CSC, but that wipes my data so I want to avoid it.
I've checked the logs and saw an error saying
Unable to set property "ro.boottime.init.mount.cache to" "3"
I've tried wiping cache in recovery as well, but that didn't help.
I also have the same issue when I flash magisk boot image with odin. it bootloops to recovery, and the only way to fix it is to do factory reset. Surprisingly the device is still rooted after the reset.
Have the same problem here, anyone here who have a solution for this?
Related
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.
Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?
Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...
So my phone was stuck at Android is starting, so I tried to perform a factory data reset through the settings menu. Now it will only boot to TWRP no matter what I've tried. I've formatted everything reinstalled the system and all that. Anyone have an idea besides full on reflash?
cabagekiller said:
So my phone was stuck at Android is starting, so I tried to perform a factory data reset through the settings menu. Now it will only boot to TWRP no matter what I've tried. I've formatted everything reinstalled the system and all that. Anyone have an idea besides full on reflash?
Click to expand...
Click to collapse
Have u try select start menu from the bootlooder?
You can try:
Update or reflash twrp to latest version
Reflash your boot.img
I have the XT 1805
This is the European Dual Sim version 32GB.
I unlocked the bootloader and got root using this: https://forum.xda-developers.com/moto-g5s-plus/development/root-moto-g5s-plus-t3673287
I was unsuccessful flashing the TWRP recovery from the link in the OP. Other people in that that thread noted similar issues. I flashed TWRP from this link:
https://forum.xda-developers.com/showpost.php?p=74105503&postcount=27
Whenever the phone boots, it boots directly to TWRP.
I also enabled encryption.
TWRP says the encryption password is incorrect.
When I cancel the ready process, I can go into TWRP and boot to bootloader from TWRP.
From the bootloader/fastboot screen I can boot into system.
I don't want to jump through these hoops every time I reboot. How do I fix this?
Also, I cannot factory reset. Factory reset takes me to TWRP. After I do the bootloader dance, I'm back to the system before the factory reset. It's as if factory reset never happened.
crobjam said:
I have the XT 1805
This is the European Dual Sim version 32GB.
I unlocked the bootloader and got root using this: https://forum.xda-developers.com/moto-g5s-plus/development/root-moto-g5s-plus-t3673287
I was unsuccessful flashing the TWRP recovery from the link in the OP. Other people in that that thread noted similar issues. I flashed TWRP from this link:
https://forum.xda-developers.com/showpost.php?p=74105503&postcount=27
Whenever the phone boots, it boots directly to TWRP.
I also enabled encryption.
TWRP says the encryption password is incorrect.
When I cancel the ready process, I can go into TWRP and boot to bootloader from TWRP.
From the bootloader/fastboot screen I can boot into system.
I don't want to jump through these hoops every time I reboot. How do I fix this?
Also, I cannot factory reset. Factory reset takes me to TWRP. After I do the bootloader dance, I'm back to the system before the factory reset. It's as if factory reset never happened.
Click to expand...
Click to collapse
First of all we need to make a fresh start so
1) let's flash the stock ROM on our device
2) now once we are on stock it time we flash a valid TWRP recovery file here's the link : https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910
3) once it's done let's boot to the recovery and if it asks for any password or pin let's cancel it and swipe to allow modifications now let's go into wipe section > format data > type yes.
4) once it's done let's go to reboot section and reboot to recovery. Once again let's boot back to recovery if we get any red lines highlighting " unable to mount system " so to fix it let's go to mount and mount system,data and now flash magisk or super su if we want root or straight away flash a custom ROM due to this atleast we will not get a system status modified in our bootloader
Thanks for reading .
Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
flash no-verity-opt-encrypt zip file?
topgunpilott said:
Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
Click to expand...
Click to collapse
Contact me on [email protected]
I will help you