Database Users

Anyone have a XT1575 7/19/2016 update TWRP package?

Anyone have a XT1575 7/19/2016 update TWRP package?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please post if you do, my rooted phone now enters boot-loop because I accidentally hit "Yes, I am in"....
Thanks in advance!!!

I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.

captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
Do you still have root, etc.?

captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
HeatR216 said:
Do you still have root, etc.?
Click to expand...
Click to collapse
Yes i would like to know! I would love to be able to run the OTA update without causing issues, and if all i have to do is wipe dalvik n cache on boot after the OTA update that would be awesome!

Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.

Mine is full wipe >> flash stock 24.49-18-3 >> update 24.49-18-4 via OTA then flash Su 2.62-3 >> Done.

captainmalcolm said:
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Click to expand...
Click to collapse
I still dont get you, first you say the update does not work, then you said it worked after you cleared dalvik and cache in twrp after it had been applied making it work?

Not TWRP flashable, but someone posted the full firmware here.
I could not get the OTA to go on my phone, kept failing.
I just fastboot flashed everything in that zip according to the flash script that came with the zip except recovery and didn't wipe userdata. Booted into new system to confirm everything was ok, then TWRP flashed systemless supersu and Frankenclark. All is good. Not as simple as TWRP flashable, but way less disruptive than restoring to bare bones stock to take an OTA.

How long does it usually take on a new twrp zip?

oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!

nd4spdbh said:
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
Click to expand...
Click to collapse
yep. just waiting for twrp zip.

Samsung Galaxy S7 bootloop

I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)

k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.

TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.

k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)

TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, i just tried a factory reset and that fails too. Unable to mount /data.

k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?

EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.

k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp

Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)

I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.

I can't back up after restoring a backup- please help

Hello all,
I recently bought a brand-new ZE552KL and have since unlocked the bootloader, flashed TWRP 3.2.1, flashed ViperOS 7.1.2, flashed Magisk 15.3, flashed Xposed v89r5-v90b2, and made several backups. However, each time I restore one, I lose all progress in the most evil manner I've encountered to date: Any time I try to back up my install after restoring from a backup, it fails, claiming my system partition is only 7MB in size.
Now, at first I thought this was simply a bug in the latest TWRP- 3.2.1 is so new, after all- so I flashed back to 3.1.1, reflashed ROM/GApps, went through first boot, and began making backups as normal. Only, when I tested one of them by restoring, booting to system, changing things, booting back into recovery, and attempting to back up, well, you guessed it... 7MB system partition. I have no idea what's causing this, but it kinda invalidates the point of having backups in the first place. Any help would be appreciated.

Hi, i never find a solution for backup / restore with TWRP. Always doing all from begining.

I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?

auroraPLG said:
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
Click to expand...
Click to collapse
Try to flash twrp 3.1.1 (20171023) from here https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA

[email protected]@ said:
Try to flash twrp 3.1.1 (20171023) from here
Click to expand...
Click to collapse
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Code:
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?

auroraPLG said:
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
Click to expand...
Click to collapse
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?

[email protected]@ said:
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
Click to expand...
Click to collapse
1. No. No bootloop. I don't understand where you got this idea. As I said, old TWRP failed to restore Data. However, I'm pretty sure it was the Data partitions in my latest backups, due to making files immutable- not the recovery itself.
2. No, I want to restore ViperOS.

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Hi, this is the right configuration for a backup ?
Please confirm me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Picture from howtogeek.com

@dekson9
Yes, that is the correct. System partition is the OS, and the data partition is your apps and config data.
So, when you make a backup, can you confirm the size of the backup files, should be something like system.ext4.win000, 001, 002.
Maybe try unmounting and remounting the system partition while in twrp before the restore? You can toggle the button at the bottom right (4 horizontal lines) to see if there were any errors.

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Well, I tried it your way. Not gonna lie, I don't understand why a full backup would cause that problem. But it turns out you're right. I've gotten that kink worked out thanks to you. Now if I could just fix the hardware clock... but that's another adventure for another party, I'm sure. I'm off to press that thanks button.

@auroraPLG
Glad you got it sorted, happy flashing!

@wang1chung
Thank you! I think I'm gonna play around with backups and pull logs and see if I can't figure out what causes this particular bug.

[GUIDE] Twrp Remove decryption password Xperia XZ

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device

Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.

omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation

Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.

omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.

awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]

omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?

awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.

redundant

How To Disable Force Encryption ?

So, Everytime Whenever I Flash A Custom Rom,My Device Gets Encrypted Automatically & Sometimes Roms Fails To Decrypt Data Even If I Type Right Password,if i flash another rom without formatting data. I tired dm-verity,force encryption & lazy flasher also but that doesn't woks,if there is anyway to fix it so pls help me out!

Now, I may not be much of help, but I think the encryption thing happens because you don't remove your saved fingerprints from the phone... OR it might be a TWRP bug, as the same thing happened to me when I wanted to switch from LOS back to MIUI; had to format /data & lose everything from the internal storage as no passwords worked in TWRP :crying:

Add pin as screen lock
jaxx08 said:
So, Everytime Whenever I Flash A Custom Rom,My Device Gets Encrypted Automatically & Sometimes Roms Fails To Decrypt Data Even If I Type Right Password,if i flash another rom without formatting data. I tired dm-verity,forece encryption & lazy flasher also but that doesn't woks,if there is anyway to fix it so pls help me out!
Click to expand...
Click to collapse
I had the same problem but when I set pin as screen lock the TWRP was able to decrypt my storage and everything is working!

From a telegram support group for redmi note 7:
// Encryption In Lavender //
Encryption is the process of translating plain text data (plaintext) into something that appears to be random and meaningless (ciphertext), when your device gets encrypted, it will ask for random password on startup and recovery, you cant access your internal storage and the only way to fix it is by formatting the data (doing this will also wipe your internal storage)
1) Changing from AOSP/LOS/CAF/GSI to MIUI or vice versa would almost certainly require formatting data
2) Changing from one custom ROM to another custom ROM may or may not require formatting data - see point number 3 below
3) On this device, there are different Pie encryption protocols, and they are not always compatible with each other. If you move from a ROM using a different encryption protocol from your current ROM, you will need to format data, because the pin/password will always be considered to be "wrong" by the new ROM. Some ROMs will just cheerfully format and encrypt without telling you, and you will have lost all your internal storage.
Conclusion - Never change your ROM without first backing up your precious data
Click to expand...
Click to collapse
The only workaround that I've found and that seems to work is to flash magisk just after the rom without rebooting to system, in this way I noticed that generally password is not required

The only workaround that I've found and that seems to work is to flash magisk just after the rom without rebooting to system, in this way I noticed that generally password is not required
Click to expand...
Click to collapse
Thats what I have found too, but am not 100% sure if there is an issue with TWRP as the PIN I use is always wrong and it kills the process. Very frustrating as I cannot mount data so cannot perform a backup

its due to dm-verity which is a "security" android feature and depends whether it is enabled or disabled. It also depends on if your recovery properly supports decryption. typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting or a specific dm-verity disable patch if you wish to not install magisk. If you happen to have a encrypted partition and can got get in due to wrong password or non properly supported recovery ...then you are forced to format the partition thereby losing your data.

Can't you set password for screen lock after disabling force encrypt on your phone?
Edit: Never mind, it doesn't work in case of lavender.

XeoNoX said:
its due to dm-verity which is a "security" android feature and depends whether it is enabled or disabled. It also depends on if your recovery properly supports decryption. typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting or a specific dm-verity disable patch if you wish to not install magisk. If you happen to have a encrypted partition and can got get in due to wrong password or non properly supported recovery ...then you are forced to format the partition thereby losing your data.
Click to expand...
Click to collapse
Thus, "typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting".
I tried in the following steps
- flashing the full stock rom;
- reflashing the Orangefox recovery (since stock recovery replaced Orangefox);
- installing Magisk inside Orangefox.
Spoiler: Screenshot 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Furthermore, I checked two boxes below
- Disable DM-Verity;
- Disable Forced Encryption;
in the Orangefox settings both before and after flashing the full stock rom.
In addition, in fastboot mode, I flashed a Magisk-patched boot.img (that had been patched, before flashing the full stock rom, in a previously installed same stock rom).
All the above steps were performed before booting into system.
Finally, the data partition remained encrypted...
Would it be still possible to disable dm-verity?
Thanks.

Disable Forced Encryption cannot remove encryption, it can only disable forced encryption. to remove encryption, format data.