Related
I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?
install a stock rom then re-install cwm 5.0.2.7
Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.
Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.
Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?
Factory reset?
Have you tried doing a factory reset with Kies?
be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...
I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!
Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.
Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?
That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.
What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?
Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?
I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs
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,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Just moved from an old Galaxy S6 to the Pixel 2 Xl and I am confused about what partitions i need to select to make a proper backup with TWRP.
Is boot/sytem/data enough?
I dont know what to do with the remaining partitions: system image/vendor/vendor image.
Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:
Az Biker said:
Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:
Click to expand...
Click to collapse
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D
ProoN said:
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D
Click to expand...
Click to collapse
I believe things and processes have changed with Android 10 (Q) as far as TWRP and backups.
Post your question here as it is permitted here by the OP and there is a lot of help here.
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