Related
I have a D855K (Telstra Australia). I recently upgrading to 10i, using the firmware: LG-D855 A6KG D85510i 00_6 16GB Hong Kong http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW436606432109876543213/D85510I_00.kdz
Before the upgrade, I backed up in LG PC Suite, then imaged with a full wipe, and then restored the backup via LG PC Suite again.
I now can't take photos or videos with the native camera app (haven't tried any third party apps yet). Photos just fail silently, and videos say "Failure to write". I've done some googling, and people having complained about 4.4.x breaking the ability to write to SD cards, but I don't have an SD card in my device. It's just internal storage. Also note that I haven't rooted the phone since the firmware update.
Has anyone else had this issue, or can provide any advice at all? I'm going to get a third-party camera app to see if that can at least let me take some pics if I need to in the meantime, but I would like a fix not a workaround.
Cheers.
I just installed Camera360 and it has the same issue. With photos, both apps save a thumbnail with nothing in it, then warn that the album has changed and you need to refresh the folder. When I do, the folder is empty.
Initially I was running 10d, then then 10b because of a boot loop issue. So it could be a range of things causing this
The Camera360 app works fine (ie can save pictures) if I change the folder to DCIM, instead of DCIM/Camera.
I have used Purpledrake to root my device, and installed a Terminal app. I can navigate into DCIM, but can not do anything at all with the Camera folder. I can't navigate into it, delete it, chmod or chown it. It appears to have all the same permissions as every other folder under the emulated sdcard, but refuses to do anything. I haven't tried it via adb but I doubt it would make any difference.
Any thoughts would be greatly appreciated.
I managed to run e2fsck, and it appears that my data partition has some corruption. But e2fsck can't fix it unless the partition is unmounted. I set up adb but couldn't get to a point where the partition (/dev/block/platform/msm_sdcc.1/by-name/userdata) was not in use. I booted into recovery (adb reboot --bnr_recovery) and it still mounts the /data partition, and on top of that I don't seem to be able to elevate to root. I am only new to the Android ecosystem, so please forgive any ignorance. My google-fu doesn't appear be very helpful either. Any suggestions welcome.
Have you got the nandroid backup?? If so, How about restoring it back?... Have you tried it?? Hope it works...
mustang2012 said:
Have you got the nandroid backup?? If so, How about restoring it back?... Have you tried it?? Hope it works...
Click to expand...
Click to collapse
I was under the impression I couldn't do a nandroid backup until I had a recovery rom installed, which isn't available for the D855 yet... since the partition appears to be corrupted, I suspect formatting the data partition would solve the problem. But I don't really want to lose the customisations I've done. I wouldn't be surprised if the LG PC Suite backup is like an image of the partition, which means it might restore the corruption if I used it.
aussiewan said:
I was under the impression I couldn't do a nandroid backup until I had a recovery rom installed, which isn't available for the D855 yet... since the partition appears to be corrupted, I suspect formatting the data partition would solve the problem. But I don't really want to lose the customisations I've done. I wouldn't be surprised if the LG PC Suite backup is like an image of the partition, which means it might restore the corruption if I used it.
Click to expand...
Click to collapse
Tethered twrp recovery could have you saved your nandroid backup which then you be go back to fully functional status of your phone... Sorry I am new to LG G3 myself coming from galaxy s4.
I looked into those recovery boots but it seemed a bit more complicated than I could be bothered with at the time. The thing is, my phone is still fully operational. The only thing is that the Camera folder appears to be corrupt. Even just changing the path that the default camera app saves to would fix the visible issue, however the corrupt filesystem means I could be in for a lot more pain if I can't sort that out. I'm hoping that someone can point me in the right direction to be able to use e2fsck on the data partition (I think all I need to be able to do is unmount the partition so it's not in use). Otherwise, formatting the data partition will likely be the solution, which I'm trying to avoid.
aussiewan said:
I looked into those recovery boots but it seemed a bit more complicated than I could be bothered with at the time. The thing is, my phone is still fully operational. The only thing is that the Camera folder appears to be corrupt. Even just changing the path that the default camera app saves to would fix the visible issue, however the corrupt filesystem means I could be in for a lot more pain if I can't sort that out. I'm hoping that someone can point me in the right direction to be able to use e2fsck on the data partition (I think all I need to be able to do is unmount the partition so it's not in use). Otherwise, formatting the data partition will likely be the solution, which I'm trying to avoid.
Click to expand...
Click to collapse
No expert here but have you tried restore upgrade errors with pc suite. Hopefully will fix your problems and it doesn't wipe your phone. So you will just have to reroot afterwards.
p70shooter said:
No expert here but have you tried restore upgrade errors with pc suite. Hopefully will fix your problems and it doesn't wipe your phone. So you will just have to reroot afterwards.
Click to expand...
Click to collapse
A good suggestion! I tried to use that feature a week or so ago when I have my phone in a reboot loop. Unfortunately it only said "You have the latest version of the software, go away". It was a little politer than that, of course, but my response was not polite at all. I will give it a go again tomorrow when I have access to the same computer I was doing it with before, and see how I go. I'm not hopeful that it will help, but worth a shot.
aussiewan said:
A good suggestion! I tried to use that feature a week or so ago when I have my phone in a reboot loop. Unfortunately it only said "You have the latest version of the software, go away". It was a little politer than that, of course, but my response was not polite at all. I will give it a go again tomorrow when I have access to the same computer I was doing it with before, and see how I go. I'm not hopeful that it will help, but worth a shot.
Click to expand...
Click to collapse
Was that using restore upgrade errors tho or software update? It worked for me when I was having continuous f/cs when I bootlooped I had to use the flashtool. Can't wait for a custom recovery
It was the Restore Upgrade Errors option. Part of the problem is that there have been no OTA updates for my phone. Checking that XML file at LG shows no firmware at all. I think that cripples the repair functionality a bit.
aussiewan said:
It was the Restore Upgrade Errors option. Part of the problem is that there have been no OTA updates for my phone. Checking that XML file at LG shows no firmware at all. I think that cripples the repair functionality a bit.
Click to expand...
Click to collapse
Ah ok, bummer. How about flashing the kdz again or a different one without wiping, that might do it, its sort of the same process.
p70shooter said:
Ah ok, bummer. How about flashing the kdz again or a different one without wiping, that might do it, its sort of the same process.
Click to expand...
Click to collapse
Unfortunately I don't think the OS partition is the problem. I don't have force quits or the like happening. It's the data partition that has some corruption. I can run e2fsck in no-change mode and it tells about a range of issues. But I can't fix them unless the partition is not in use. Doing anything that keeps the data partition intact, eg flashing the firmware, is not likely to resolve the problem.
Well, I'm flashing the firmware again. I changed the runtime from Davlik to ART after some reading, and the phone stuck at the LG boot logo. I will not restore the backup I did last week, in the hopes that it doesn't screw up the data partition again. At least I get to have some fun tweaking the OS again I guess...
And I can successfully take photos again!
I am still interested to hear if anyone knows of a non-destructive way to fix this kind of issue. e2fsck is on the device, but I can't seem to run it. I'm using Linux knowledge here, but is there a way to set a dirty flag on the partition so that the OS automatically runs e2fsck on next boot?
aussiewan said:
And I can successfully take photos again!
I am still interested to hear if anyone knows of a non-destructive way to fix this kind of issue. e2fsck is on the device, but I can't seem to run it. I'm using Linux knowledge here, but is there a way to set a dirty flag on the partition so that the OS automatically runs e2fsck on next boot?
Click to expand...
Click to collapse
May you tell us how did you fixed it?
As per my post directly before the one you quoted, I had to re-flash my phone to recover from changing the runtime from Davlik to ART (it got stuck at the boot logo). I chose not to restore my backup, which may have re-introduced the problem. A full wipe of a phone will fix a lot of problems... but as I said, it would be nice to know of a less destructive way to do it.
Fix!
Probably a bit late but adding this in case anyone else has the issue.
To fix it on a rooted device, enter TWRP recovery, go to Wipe > Advanced Wipe
Select Internal Storage. and swipe to wipe. (this will delete everything on the Internal "sdcard". That is not apps or settings, but it is saved files and some game files etc.
I'm using the most recent version of TWRP for the 5x. I usually check boot, system, data which I believe are the default items that are checked for making an nandroid. I also use enable compression to try and shrink the file. The last few times I have made a nandroid then tried to restore it, there have been issues. One time it wiped out all my text messages, another time it asked me in the beginning for my start up pattern to unlock the phone and kept error despite it being correct. I've never had these issues before making and restoring nandroids on my Nexus 6. Is anyone else having these issues ? Do I need to backup the vendor image as well ?
I'm backing up directly to a USB Thumbdrive from OTG if that matters
You need to back up vendor also.
Also you should use the unofficial TWRP 3.0.2-3 as 3.0.2-2 has bug with larger partitions.
Team,
I just recently bought a Google Pixel and was attempting to transfer my contacts and messages and stuff from my HTC One M8 to my Google Pixel. However, my HTC One M8 was still on KitKat (4.4.2) and would not work with the transfer tool. So then I said let me take a TWRP backup of my phone before i start attempting to update it.
I attempted to download a rom to flash via TWRP but it did not work so I naturally tried to restore back to the TWRP backup I took.
Except now everytime I try to restore the backup I took all I get is extractTarFork() process ended with ERROR: 255
I have attempted to google all day with no luck.
Anyone dealt with this and have resolved it?
Thanks!
bef349 said:
Team,
I just recently bought a Google Pixel and was attempting to transfer my contacts and messages and stuff from my HTC One M8 to my Google Pixel. However, my HTC One M8 was still on KitKat (4.4.2) and would not work with the transfer tool. So then I said let me take a TWRP backup of my phone before i start attempting to update it.
I attempted to download a rom to flash via TWRP but it did not work so I naturally tried to restore back to the TWRP backup I took.
Except now everytime I try to restore the backup I took all I get is extractTarFork() process ended with ERROR: 255
I have attempted to google all day with no luck.
Anyone dealt with this and have resolved it?
Thanks!
Click to expand...
Click to collapse
Did you try updating TWRP? I had something like this happen a few years ago with my S3 and updating my recovery fixed it.
xunholyx said:
Did you try updating TWRP? I had something like this happen a few years ago with my S3 and updating my recovery fixed it.
Click to expand...
Click to collapse
yep, I had updated to twrp 3.0.2.0...still no luck
there has to be a way to fix this
so now even more weird. I downloaded Titanium Backup to try and extract from my TWRP backup, and nothing is there!
how the f is that possible!? does this mean my data is forever gone?
NoCall log, you should backup your calls with CALL LOG BACKUP & RESTORE apk from play store.Messages,you should backup with SMS BACKUP AND RESTORE apk from market(witch also can make a backup of all your sms/mms & call log!!!),so it's an one app for all.Both app make folders on your internal/sd memory that contain files selected by name and date,and you can just transfer this folders from M8 to Pixel and download those apps from playstore on your new Pixel phone,and restore calls/sms..About Titanium restore,isn't M8 ARM phone and Pixel is ARM64(or x86,I'm not sure)?so you can't restore those apps in TB cuz they're different versions with diferent screen DPI,and I suppose they won't work or TB gives you error cuz of that.You can only restore data from TB ,and it's very probable that some of those "restore' s" will give you problem due thing I sad in upper text and also cuz of big difference in Android versions(4.4>7.0+).
I hope you understand what I try to say,English is not my language,and I'm just trying to help you.I didn't by Pixel yet,I plan to,and this is what I would use in mind doing those transfers and restore procedure.
I had LGG4(ARM64),I transfered all my TB folder from M8(ARM),and when restoring ARM>ARM64 ,many of them force closed or mail function.But ONLY data restore allways worked on already installed app.
And about your error and problems on m8 with TWRP,yes try with some other and maybe older versions of TWRP(if m8 is on 4.4.4 ,then maybe latest recoveryes have problem to do backup and restore.In the end,try to flash stock RUU for your version on it,then TWRP+superuser,to try to fix all.BUT BEFORE Ruu Move all your TB and other data from internal memory/sd to computer or some other external drive-in case you lost or overwrite your data on phone.
Maybe someone will point you in right direction,maybe someone already had that problem.
Sent from my HTC One M8 [6.0 Gpe]
shawek said:
NoCall log, you should backup your calls with CALL LOG BACKUP & RESTORE apk from play store.Messages,you should backup with SMS BACKUP AND RESTORE apk from market(witch also can make a backup of all your sms/mms & call log!!!),so it's an one app for all.Both app make folders on your internal/sd memory that contain files selected by name and date,and you can just transfer this folders from M8 to Pixel and download those apps from playstore on your new Pixel phone,and restore calls/sms..About Titanium restore,isn't M8 ARM phone and Pixel is ARM64(or x86,I'm not sure)?so you can't restore those apps in TB cuz they're different versions with diferent screen DPI,and I suppose they won't work or TB gives you error cuz of that.You can only restore data from TB ,and it's very probable that some of those "restore' s" will give you problem due thing I sad in upper text and also cuz of big difference in Android versions(4.4>7.0+).
I hope you understand what I try to say,English is not my language,and I'm just trying to help you.I didn't by Pixel yet,I plan to,and this is what I would use in mind doing those transfers and restore procedure.
I had LGG4(ARM64),I transfered all my TB folder from M8(ARM),and when restoring ARM>ARM64 ,many of them force closed or mail function.But ONLY data restore allways worked on already installed app.
And about your error and problems on m8 with TWRP,yes try with some other and maybe older versions of TWRP(if m8 is on 4.4.4 ,then maybe latest recoveryes have problem to do backup and restore.In the end,try to flash stock RUU for your version on it,then TWRP+superuser,to try to fix all.BUT BEFORE Ruu Move all your TB and other data from internal memory/sd to computer or some other external drive-in case you lost or overwrite your data on phone.
Maybe someone will point you in right direction,maybe someone already had that problem.
Sent from my HTC One M8 [6.0 Gpe]
Click to expand...
Click to collapse
Thank you for your reply; I wish I had asked before attempting.
Here is what I see from the bootloader screen in case it helps --
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.18.0.0000
RADIO-1.09.20.0702
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.21.605.2
eMMC-boot 2048MB
Aug 7 2014,20:26:27.26992
--
I took the full backup of my M8 using some version like TWRP v2.8.0.? I tried to restore the backup and it kept throwing me that error. So I said, lets try to flash the latest version of TWRP and that is what I did. I attempted restoring through the latest TWRP but still I get the same error. I have also tried to extract the backup using Cygwin with no luck. Titanium Backup also does not see it as a valid backup.
I am still on Android 4.4.2 (I had a backup from 2014 I was able to restore to in the meantime and is rooted).
The only place the data from my M8 is, is in the TWRP backup file which refuses to restore. All data on the phone was formatted and overwritten as I tried to flash a newer rom on it with no success. I have not tried to restore the data to my pixel and will not do so. All I need to do is restore the M8 backup to the M8 and try the methods you listed but I cannot get past this TWRP error. Or, get the backup to extract properly without throwing errors so that I can get the appropriate .db files from within
I am sure there is a fix involved with TWRP or is my wishful thinking sore out of luck?
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.
Hello all-
In the process of trying to upgrade to OOS 5. I made sure to make a backup of the entire system (system image) in TWRP before proceeding. I also backed up the Boot image and Modems. I had the entire OOS 5 rom ready to flash but before doing so I elected t wipe Dalvik/Cache, Cache, Data & System as I always thought you have to do a fresh clean install when changing versions (7.1.1 to 8.0). The first error I encountered was that it couldn't flash the file. Then when I tried to restore my backup...it does the process with no errors yet when I try to reboot I am told no OS installed. What has happened and what can I do since I always make these backups to be safe?
Thanks all!
Plug your phone on a PC (with the phone in recovery mode), move your backup (sdcard/TWRP/backup) on your PC to keep it safe. Next follow the mega unbrick method 2 (just Google it) on OnePlus forum, update your phone to the version that you were and reflash TWRP and copy your backup from your PC to your phone (in the same location than before) and try to restore your backup.
Error installing OOS 5
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
DroidJay123 said:
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
Click to expand...
Click to collapse
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Striatum_bdr said:
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Click to expand...
Click to collapse
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
DroidJay123 said:
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
Click to expand...
Click to collapse
Yes update from within TWRP. I think superSu 2.85 should be good or Magisk 14.0
Hello
This is a TWRP recovery for Motorola Moto G5 Cedric for arm64 ROMS, with encryption support, backup support for persist and efs partitions and possibility to flash/backup logo boot image.
I need review and test, especially for the storage decryption and/with LineageOS fingers-crossed. I was able to test it on my device (XT1676 3Go).
It is my first ROM so it is possible that there are bugs.
- Be carefull, there are problems with the backup system :
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
- freeZbies
Click to expand...
Click to collapse
Changelog
TWRP 3.2.3-2
add sdcardfs
add FB2PNG for screenshot
fix brightness path and define it at 160
fix time zone error
fix incorrect lun path for USB
You can download it here :
TWRP 3.2.3-2 (md5: 0dbd3846593ae907d3391596876c1f35)
TWRP 3.2.3-1 (md5: 404b54d27653b5a1ec5b59023f53d3cb)
TWRP 3.2.3-0
Sources :
https://github.com/Akipe/twrp_android_device_motorola_cedric
https://github.com/Akipe/twrp_android_device_motorola_msm8937-common
Manifest :
https://github.com/Akipe/android_development_manifest
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Guttergorm said:
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I added the functions you wanted. Can you try and tell me if everything is ok?
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
mikefive said:
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
Click to expand...
Click to collapse
Thx for testing :good:
Akipe can u help us to build treble rom for cedric???
Works nicely, thanks.
I just tested it and it decrypts my internal storage normally.
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
Hello ! Thank you for your test and sorry for your backup
I will test the backup system and add a warning
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Akipe said:
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Click to expand...
Click to collapse
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
freeZbies said:
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
Click to expand...
Click to collapse
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Akipe said:
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Click to expand...
Click to collapse
I was on stock oreo, so its arm, not arm64
freeZbies said:
I was on stock oreo, so its arm, not arm64
Click to expand...
Click to collapse
Oh ok, there are chances that's why the backup did not work .
This recovery is mainly intended for arm64 rom !
Just wanted to say that everything worked well for me in backing up and restoring the OmniROM, on both decrypted and encrypted phone.
Thanks @Akipe for the great job
Can you update it to latest TWRP?
Sent from my cedric using XDA Labs
forgot password to decrypt??
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
nurvus said:
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
Click to expand...
Click to collapse
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
TheFixItMan said:
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
Click to expand...
Click to collapse
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
nurvus said:
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
Click to expand...
Click to collapse
Backup efs if you want to preserve your current emei state or need to restore it in future