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.
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
joloxx9joloxx9 said:
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
Click to expand...
Click to collapse
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Click to expand...
Click to collapse
Could you please tell me How can I fix IT?
joloxx9joloxx9 said:
Could you please tell me How can I fix IT?
Click to expand...
Click to collapse
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Click to expand...
Click to collapse
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
joloxx9joloxx9 said:
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
Click to expand...
Click to collapse
for future reference, there is a "Repair filesystem" option in twrp. It says it runs e2fsck, which works for ext4. It won't hurt an f2fs filesystem, but I don't think it will repair it either. I'm seriously considering switching my /data to ext4 just so I have proper recovery tools.
My OP3T does have fsck.f2fs on the system, which means you can fix your data by opening a Terminal session from TWRP and then running :
Code:
fsck.f2fs /dev/block/dm-0
should fix your data corruption should you see this error again. For ext4, you use e2fsck rather than fsck.f2fs. This is also what you would use on /system (which is /dev/block/sde20 on my phone) should that ever be mounted read/write and get corrupted (pretty low chance even if you do mount it read/write as writes are low frequency and ext4 has a rock solid journal).
WARNING: Device numbers are for my OP3T and may be different on other devices or even on non-US devices.
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
i accidentally deleted a file or an apk i uninstalled and restarted my phone and it acts like its loading but just goes to the green n white htc screen and reboots minutes later is their anyway to fix this without loosing all my data? thank you guys for any help
i have a backup om last year i can restore the partition the files would be on but im just asking would i just restore the boot partition? or would i need to do the system
jaken1913 said:
i have a backup om last year i can restore the partition the files would be on but im just asking would i just restore the boot partition? or would i need to do the system
Click to expand...
Click to collapse
Uninstalling an APK should not throw you into a bootloop unless you deleted some very important system file, at which point doesn't make any sense because any system files would not be an APK necessarily. You need to provide more information for anyone to help you TBH....
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes