Database Info

[Q] Solved - Help: all downloads are unsuccessful

Help...no matter which rom i try i cant get any downloads to work...sorry, let me clarify...my market downloads work fine but any downloads form the web fail.
Any thoughts on what to change to fix this? it wasnt always this way...i dont know whats changed that crosses roms.
Solved:
It appears two be a two part issue, some of it is the Download Manager and at least part of the issue was with the Calibre App i was trying to DL from. Specifically, I was accessing the Calibre net share component. When a password is set on the share the gtab download manager is unable to correctly request downloads. I removed the uid/pwd and downloads work again. With the uid/pwd in place logs show an http 401 error.
Now to determine why...

In recovery are you wiping everything? Cause that was my issue at first and I was crossing roms lol
Sent from my HTC Glacier using Tapatalk

I had the same issue when I tried the notion adam browser.
I just reapplied my rom.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk

~BAM~ said:
I had the same issue when I tried the notion adam browser.
I just reapplied my rom.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
That's what i tried first...no joy. Then i wiped caches and stuff and now i've compunded the issue...titanium doesn't see any apps or OS componets...i cant restore what i had.

Darkeyce said:
That's what i tried first...no joy. Then i wiped caches and stuff and now i've compunded the issue...titanium doesn't see any apps or OS componets...i cant restore what i had.
Click to expand...
Click to collapse
When you say you wiped cache and stuff, did you wipe user data as well? If so, then that would explain why Titanium can't see your previous backup (It stores it in internal storage by default).
If that is the case, and you have wiped the data partition, your best bet would be to start over and reload your ROM from scratch.
BigJohn

BigJohn89 said:
When you say you wiped cache and stuff, did you wipe user data as well? If so, then that would explain why Titanium can't see your previous backup (It stores it in internal storage by default).
If that is the case, and you have wiped the data partition, your best bet would be to start over and reload your ROM from scratch.
BigJohn
Click to expand...
Click to collapse
As long as Darkeyce didn't perform a NVIDIA flash or repartition the drive, the backup data should still be there. I've loaded many custom roms by wiping cache and data (factory reset), and all I had to do was reinstall Titanium Backup and restore my apps.

I had the same problem yesterday on my Vegan GTab. GMail wouldn't work either, and my Nook app wouldn't sync with my online account. I didn't try any fix but after shutting down the device last night, I fired it up this morning and everything was working fine.

BigJohn89 said:
When you say you wiped cache and stuff, did you wipe user data as well? If so, then that would explain why Titanium can't see your previous backup (It stores it in internal storage by default).
If that is the case, and you have wiped the data partition, your best bet would be to start over and reload your ROM from scratch.
BigJohn
Click to expand...
Click to collapse
Fixed the TB issues...that was related to the Keramides file...deleted it and all teh TG data came back...but i STIll have the download issue.
All the cache wipes were done, including the user data but that didnt impact the backups.

[Q] Titanium Backup SD Card Question

I'm a little new to rooting and this is my 2nd device that I have rooted and first without an external Sd card. I currently have the ViperXL rom on my HTC One X and I want to try a AOSP Rom. I backed up everything with Titanium Backup but what I was wondering is when I factory reset my phone won't the backup get wiped too? I'm sorry if this is a noob question but I don't want to advance without confirming this because i need to know if I have to copy my backup over to my computer. And I think that the backup is in the SD Card, which i'm not entirely sure about. So also does the SD card get wiped? I'm sorry if this question has been asked already and I will delete this thread if anyone asks.

Factory reset from recovery doesn't touch your "sd card" at all. All of your stuff on your sd card will be fine, including your backups.
However, factory reset from bootloader will completely bork your sd card, and it would need to be formatted to be usable again. So, don't ever factory reset from bootloader.
Hope this helps.
Sent from my Evita

Its a fair question, since it is a little confusing that the "SD card" is not a distinct card per se, but a partition on a larger flash memory chip. But as mentioned above, it will not get wiped unless you specifically select the option in recovery to wipe the SD card.
Also, there is the rare event of some files on the SD being corrupted when flashing ROMs. Its happened to me and others in the past. So its not a bad idea to make a copy of your Titanium Backup folder on your computer "just in case".

Thanks
redpoint73 said:
Its a fair question, since it is a little confusing that the "SD card" is not a distinct card per se, but a partition on a larger flash memory chip. But as mentioned above, it will not get wiped unless you specifically select the option in recovery to wipe the SD card.
Also, there is the rare event of some files on the SD being corrupted when flashing ROMs. Its happened to me and others in the past. So its not a bad idea to make a copy of your Titanium Backup folder on your computer "just in case".
Click to expand...
Click to collapse
timmaaa said:
Factory reset from recovery doesn't touch your "sd card" at all. All of your stuff on your sd card will be fine, including your backups.
However, factory reset from bootloader will completely bork your sd card, and it would need to be formatted to be usable again. So, don't ever factory reset from bootloader.
Hope this helps.
Sent from my Evita
Click to expand...
Click to collapse
Thanks to both of you guys and thanks Redpoint for that one message you sent me on the at&t website that the One X WAS rootable. You helped me alot.:laugh:

Another Titanium Backup Question
Hey guys I know that this isn't the same question that my topic asks but I have another problem. I used titanium Backup and saved everything in my ViperXL rom for my HTC One X Att. Then i switched to a Sense 5 rom and whenever i try to restore my data my phone seems to freeze and when i reboot it doesn't show any applications or anything. It says that the titanium backup is restored but it doesn't show anything except a notification in the status bar saying a reboot is recommended. So then I go and reboot and the only thing i can do is access the apps in my lockscreen. When i boot up and try to open the app drawer nothing is in it and there is only blinkfeed and my other screen nothing seems to work. I know that i should post this in the Rom Thread and i would but as a junior member with only 8 posts including this one i can't post in Android Development yet. The link for the thread with the rom is here in case anyone wants to know what rom i'm trying this on and my backup is made from a viperxl rom. If anyone needs more details i can provide more. And on a side note whenever i factory reset it takes me back to the rom and it is working but none of my apps that i had in my backup are there. It just seems to go back to when i originally flashed the zip. thanks a lot and here is the sense 5 rom link im using.
http://forum.xda-developers.com/showthread.php?t=2293032
Is there any way for me to get titanium backup to work or would i have to download each app manually? And in case its necessary i do have a full backup of the entire viperxl rom in case i have to make more titanium backups.

It sounds to me like you're restoring system data yeah? It's not a great idea to restore system data from a different ROM, as it most likely is not compatible. So if you're changing ROMs the idea is to only restore user apps.
The reason it was still playing up after you did a factory reset is because factory reset does not wipe the system partition, and that's the partition you messed up by restoring system data using Titanium.
My advice would be to reflash your ROM. Do a full wipe (cache/dalvik/factory reset/system) first. Then boot into the ROM and use the "restore missing apps with data" option in Titanium.
Sent from my Evita

Thanks
Thanks I thought that, that was the problem or something similar because i was wondering how some of my Venom apps would work on my non Venom One X. I'm loving my Sense 5 rom but it's a shame that i can't restore all data. I would love to be able to see my call logs, sms history, and have my phone set up in the same way but obviously that one would be a problem because of compatibility and other things like lack of apps or widgets.

As mentioned, you should only use Titanium to restore user apps (and their corresponding app data), not system data. Restoring system data across different ROMs is a nearly surefire way to cause issues (as you have found), as the different ROMs tend to handle the system data differently (store them in different locations, etc.).
There are various ways to backup and restore call longs and SMS. I personally use the app SMS Backup+, which syncs your SMS to your GMail. But there are other solutions that work fine, as well.
https://play.google.com/store/apps/details?id=com.zegoggles.smssync
As far as settings and configuration, I've always just done it manually, after flashing a new ROM. Trying to restore this across significantly different ROMs (such as Sense 4+ to Sense 5) is probably not feasible. Doing it manually doesn't take much time at all.
---------- Post added at 09:34 AM ---------- Previous post was at 09:28 AM ----------
soloflyer12 said:
thanks Redpoint for that one message you sent me on the at&t website that the One X WAS rootable. You helped me alot.:laugh:
Click to expand...
Click to collapse
Your very welcome. Nice to see you here!

Thanks again
You guys have been very helpful and with this post I now have 10 posts, so now i can post in android development with my other rom related problems.

TWRP error 255, unable to restore my backup

-Hello, today i wanted to restore a recent TWRP backup but i encountered an error while restoring datas (54%). I tried other backups many times and same error , i made a new backup from current ROM and again same error.
-Perhaps TWRP is making corrupted backups or is corrupted itself.
- If i delete the data.f2fs.win001 partition from backups or untick data before restoring it works but important system files are missing. Here is what i get in TWRP log:
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/00867e6ad793a5eb/2017-05-21--08-51-47_LMY48T/data.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/BACKUPS/Rooted Xposed customized LineageOS 05.12/data.f2fs.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
Any help/advice would be greatly appreciated

Nobody has a clue? :/

I got the same error time ago on my 6X, i solved it thanks to an old backup made before debloating some system files and no one could gave me some help about, so at the end, this is the only idea that I've got; I've surely deleted some system path while debloating, and TWRP wasn't able to restore that path anymore. Give a look to this https://github.com/BuildingAtom/CleanTwrpTar/blob/master/README.md it's a software which i was almost trying, if i wouldn't solved before do that. Hope it could be helpful!

I'll try tommorow, thanks a lot for your time

No problem, as you can see even in my thread https://forum.xda-developers.com/honor-6x/help/twrp-extracttarfork-process-error-255-t3692826 I've got no useful answers, and it's like this in EVERY extracttarfork() error 255 thread here on XDA. Even other phones obviously got this error, and there was only some vague ideas about the reason of this issue... Maybe writing directly to TWRP team could provide a valid answer to this

Yes I saw this huge lack of answers about this issue, you're right that could be a great idea

I have same issue and can't found a solution the restore backup is not trust-able, beware!

mrhamed said:
I have same issue and can't found a solution the restore backup is not trust-able, beware!
Click to expand...
Click to collapse
me too facing same issue

It seem the compression procedure is problem, so I never use compression.

I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.

Full(!) backup via ADB

Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.

andy01q said:
Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.
Click to expand...
Click to collapse
It can backup/restore your data, it can not backup your ROM/firmware, if you are not rooted, you will only be able to backup/restore user data, you will not be able to backup/restore any of your system apps/system app data, or any other part of system data and system settings, that will require rooting the device.
If you want a complete backup of the operating system and everything else on the device, you will need TWRP.
Sent from my SM-S767VL using Tapatalk

I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.

andy01q said:
I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.
Click to expand...
Click to collapse
Try flashing a newer or slightly older version of TWRP, it might fix the bugs that you are experiencing in TWRP. Is TWRP set to store your backups on external? Or is it set to store backups on your internal storage? Storing backups in internal takes up too much space, it's best to store backups on external.
As for adb...
https://forum.xda-developers.com/galaxy-nexus/guide-phone-backup-unlock-root-t1420351
There are several switches that can be used to be specific about what you want backed up and what you don't.
Sent from my SM-S767VL using Tapatalk

I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.

andy01q said:
I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.
Click to expand...
Click to collapse
How much free space do you have on internal storage? If there is less free space than your system, data and cache partitions combined, that may be why it is failing. Clear some space. I say this because when the backup is being created, the data that you want included in your backup is being read bit by bit from their partitions and then written into cache bit by bit and then it is read from cache bit for bit then it is written to its final storage location bit for bit. If there is not enough space to write it all into cache before writing it to its final location, it will fail.
The same rule applies when you move files from internal to external or vice versa, the same rule also applies when you are extracting files. It requires enough free space to write that data into cache before it goes where it is actually going.
Sent from my SM-S767VL using Tapatalk

Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.

andy01q said:
Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.
Click to expand...
Click to collapse
I can't help how you feel and you are entitled to feel however you wantl, but, at the end of the day, it is still only how you "feel", that doesn't make anything true or false. Just saying.
I didn't post anything to make you feel any kind of way, I was merely attempting to be as informative as I could because one can never gauge what someone else knows or understands before your interaction with them.
I've seen some other issues with TWRP backups failing and/or being unreadable, the solution is not a singular solution, there are several reasons why it fails and several fixes to solve it. Have you tried doing some google searches for:
"TWRP backups fail at 40%"
That pulls up some information that might apply or may not, you'll just have to peruse what you find to see if any of seems like it might be what you are experiencing and then try some of the solutions that others have tried. You might get lucky, you might not.
I'm more interested in helping you "find" an answer than whether I "know" the answer or "tell" you the answer.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Have you tried doing some google searches for:
"TWRP backups fail at 40%"
Click to expand...
Click to collapse
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.

andy01q said:
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.
Click to expand...
Click to collapse
Flash an older version or newer version of the exact same ROM as what you have but not doing any of the wipes, just flash ROM and that's it. This is called a "dirty flash", it will not wipe any of your data unless you specifically tell it to.
Alternatively, you could just do a backup via TWRP without including system and boot, just data and maybe cache(cache isn't necessary and might even cause issues if you restore it). Then, if you need to restore, flash the ROM the backup was created from then reboot to system, then boot back into TWRP then use "advanced restore" in TWRP to restore data and cache, this "should" give the same result as including system and boot in the TWRP backup along with data then restoring everything from that backup.
Also, can you post a copy of your recovery logs to some hosting site then link it here, someone here might be able to see something in the log that needs addressing, preferably the logs from the failed backup processes, if they errored in different ways, post the differences also. You should be able to find your logs if you haven't wiped the device.
Sent from my SM-S767VL using Tapatalk

Stuck in recovery after rom update

Hello,
I just updated the rom Evolution X 11 on my Xiaomi Mi 9T Pro after using an older version for about half a year.
Now my phone does not boot anymore, its stuck in recovery (TWRP). Also all data seems to be encrypted and TWRP is not asking for a password.
Is there a way to get my phone to boot again or at least backup my data before I do a full wipe?

You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!

PhotonIce said:
You should always do a full twrp backup before messing with roms.
The best solution would be to backup the "Data" and "Internal Storage" partitions. Data contains all apps, their appdata and settings, while internal storage contains all of your own files (photos, videos etc.). After you back these up, wipe your phone (system, data, cache, dalvik) and flash the version of evolution x you were using previously. Now restore data and internal storage and your device should be back to normal.
If you get a bootloop while booting after restoring data and internal storage, then wipe the device again and this time flash evolution x, but only restore internal storage. This way, it should boot and you will be able to recover your files, though your apps will be gone.
If you only restore internal storage then it will no doubt boot up and you will have access to your files, but since you'll have already backed up the important stuff (data + internal storage), you might as well try restoring data as well, as there is no harm, and if the phone boots correctly after restoring both partitions, your phone will be as it was before your updated your rom.
This happened a while back to me with my J5, the issue was that I made a full TWRP backup, then began to test other roms. After I was done, I tried to restore my backup, but it would constantly fail. I sat down for a while, confused and sad about how my TWRP backup had failed me. I tried every solution I could think of, eventually this solution I've mentioned in the above paragraph came to my mind. Thank god for putting it into my mind, otherwise I would've lost a lot of stuff (mainly whatsapp chats which werent backed up, and a lot of apps which I took the time to pain-stakingly configure in the best way for my device).
Anyways, enough of my story, hope this helps you out! If it does, message back here and let us know, and also mark my post as the solution if it was able to help you, so that anyone else who stumbles upon this thread can be saved too!
Cheers!
Click to expand...
Click to collapse
Thank you for your help but backing up the data and internal storage doesnt seem possible right now because all the data is encrypted in TWRP...

If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.

PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
That sounds like a good idea. I found the old version on my PC.
Now I just need a way to install it... because twrp cant read the file. I tried with adb sideload but that results in an error for some reason. Flashing Magisk for example with adb sideload is possible.
Edit: Got it to work by using a tool called "Large Address Aware". Now waiting for the results...

PhotonIce said:
If you can't backup anything, then wipe system, cache and dalvik, and flash the version of evolutionx you were previously using. Then boot, it should be fine. If it wont boot (give it some time, it will take the time of a fresh install), then this time wipe system+data+cache+dalvik, then flash whichever rom you like and you'll be able to access the files.
You can also try using platform tools and fastboot or adb ( i dont remember exactly which one) to copy the filess from your phone onto your pc.
Sorry if this doesn't apply to your situation, I've never used a phone which has been encrypted, as such I have no experience with them.
Click to expand...
Click to collapse
This did not help unfortunately... Im still in the same recovery-bootloop and my data is still encrypted.

It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.

PhotonIce said:
It's probably still bootlooping as the data partition got modified when you flashed the newer version of evolutionx, and now it will not work with the old one. You can try wiping system+data+cach+dalvik and then flashing any rom of your choice. This will give you access to your internal storage (photos, media etc), but it will remove your apps and their settings. Whatsapp images are stored in the internal storage so you won't need to worry about those.
Again, this is risky, as it may not work (I don't know much about encryption), or you might still not be able to access your files after flashing the new rom. Proceed at your own risk.
Click to expand...
Click to collapse
Thank you for still helping me out but I already did a full reset yesterday. I did not lose much except for the time setting it all up again.
I still dont really get the point of encrypting all your data if you cant decrypt it even if you know the password...