When i try to perform a nandroid, either via twrp or cwm, because they both say my data partition is about 4.65 terabytes. Changing the firmware doesnt seem to help. Currently running CleanROM 1.6.5. any ideas?
Bonetwizt said:
When i try to perform a nandroid, either via twrp or cwm, because they both say my data partition is about 4.65 terabytes. Changing the firmware doesnt seem to help. Currently running CleanROM 1.6.5. any ideas?
Click to expand...
Click to collapse
Having the same issue on a Droid Razr HD, since I first flashed a 4.2 rom in July, I've wiped and formatted every partition on my phone multiple times, restored nandroids, used CWM and TWRP, tried newer versions and older ones, even a couple of custom variants based on CWM and TWRP, but my phone continues to report 1133300Mb as the size of my /data partition when in recovery.
If I try to backup anyway, it errors when my 32GB SD card fills up (I tried formatting it once and it literally filled the 32GB card with an unusable backup file that I just had to delete. I want to try restoring stock via RSD lite but really wanted to backup first, I can do backups WITHOUT the /data partition, but won't that mess things up if I try to restore?
***update
I did a full unbrick restore using RSD and now my partition is reporting correctly. if/when I flash another 4.3 rom, I'll update again with any changes...
Related
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Additional Info
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Semi_Interested said:
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Click to expand...
Click to collapse
Email me [email protected]
Sent from my SGH-T959 using XDA App
Semi_Interested said:
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Click to expand...
Click to collapse
Well, adb would be able to move files from external sd card to the internal one but if you don't know how to use it then Odin might be simpler. I'll pm you some instructions but if you cannot get your phone to be recognized in Odin because of USB issues then I'm not sure how to help.
My sister installed her work eMail which enabled Encryption (I believe only on the Data Partition).
She does not really care about having her work email, so we removed it.
But that still leaves everything Encryted.
After Googling Around it appears you need the Factory RUU to get the Phone Back to Stock.
But that is not availble yet.
Does anyone know a way to either Flash a ROM or Take the Encryption Off.
We tried both TWRP and CW Recovery and neither can do a Backup because they cannot Mount Data.
Any suggestions welcome.
I'm personally on a Sprint HTC One
Perform a factory reset or boot into recovery (I am not sure about the HTC One stock recovery but I did this with my Galaxy S3) and format the /DATA partition.
Use titanium backup to backup all system data and user apps + data to sdcard, copy backup folder off to a computer, factory reset, copy the backup from PC to sdcard, then restore.
xeni said:
Perform a factory reset or boot into recovery (I am not sure about the HTC One stock recovery but I did this with my Galaxy S3) and format the /DATA partition.
Click to expand...
Click to collapse
This worked. CW Recovery Failed. But TWRP worked. It got a whole bunch of failures until the last step that it formatted data. Then I ran it again with no errors.
I was a little surprised formatting DATA now includes the internal SD drive, that really sucks.
Thanks
Having trouble finding a firm answer on this. I have read that encryption has NO effect on Recovery mods since it only encrypts apps, data, and a few other pieces of info. (I thought that there was full disk encryption, but I guess not). So I would like to verify the following questions regarding the use of custom ROMs and Android encryption and I would like to do both, back them up, and maybe even change ROMs without issue.
I am fairly certain I can boot into a recovery mod (CWM or Twerp) without any problems while encrypted. Is this true? (I have seen conflicting answers here and on the interwebs).
If I back up a ROM and data (assuming this is done together in one backup), will I be able to recovery the backup properly and use it even when it was encrypted?
Thanks in advance.
Bakura
You can boot into recovery and flash zips but you will not be able to access your /data partition since that's what's encrypted. For flashing ROMs this doesn't matter since those don't touch /data. However if you have to wipe your user data you will have to set up the encryption all over again.
What this also means is you cannot store your zips on the internal memory of your phone because those will not be accessible to the recovery. You will have to store them on either an unencrypted microSD or sideload them with adb (easy enough to do on CWM, not sure about other recoveries).
Backing up should be fine as long as you backup to somewhere other than the internal memory for the reasons I stated above.
Will the wipe and restore options work?
Hexgore said:
You can boot into recovery and flash zips but you will not be able to access your /data partition since that's what's encrypted. For flashing ROMs this doesn't matter since those don't touch /data. However if you have to wipe your user data you will have to set up the encryption all over again.
What this also means is you cannot store your zips on the internal memory of your phone because those will not be accessible to the recovery. You will have to store them on either an unencrypted microSD or sideload them with adb (easy enough to do on CWM, not sure about other recoveries).
Backing up should be fine as long as you backup to somewhere other than the internal memory for the reasons I stated above.
Click to expand...
Click to collapse
I have a full Nandroid Backup of my phone with 4ext Revovery Touch. So if I encrypt Internal Storage only and if it's screwed up, will I be able to restore the Nandroid backup from recovery (I mean, is it possible to modify (rwx) the encrypted partition from recovery?
Far_SighT said:
I have a full Nandroid Backup of my phone with 4ext Revovery Touch. So if I encrypt Internal Storage only and if it's screwed up, will I be able to restore the Nandroid backup from recovery (I mean, is it possible to modify (rwx) the encrypted partition from recovery?
Click to expand...
Click to collapse
If the Nandroid backup is stored on your SD card, I think so, but you might have to wipe the partition first. As far as I know (someone please correct me if I'm wrong) you can still wipe the encrypted partition, you just can't access any of the encrypted data from recovery.
Yeah, the recovery works just fine!
Hexgore said:
If the Nandroid backup is stored on your SD card, I think so, but you might have to wipe the partition first. As far as I know (someone please correct me if I'm wrong) you can still wipe the encrypted partition, you just can't access any of the encrypted data from recovery.
Click to expand...
Click to collapse
^+1. So I went ahead and encrypted the internal storage. The process was fairly fast (took me under 10 mins).
But entering a password was too much of a hassle. So I performed a full system wipe and restored the backup. No problems.
That actually didn't work for me on the Nexus 7.
I tried to wipe the tablet from recovery but it couldn't mount the /data partition.
I tried to wipe the tablet from the OS but it didn't like the custom recovery so it just rebooted without changing anything.
In the end I had to run "fastboot erase userdata" to wipe it. That worked.
I have now installed CM 10.1 and can report that the encryption process seems to be working fine on the N7. It's taking a while but it is the 32GB model.
Encryption on Android is very temperamental. The general pattern seems to be that if the ROM you're using is based on the stock OS for your device (as AOSP is for Nexus devices) encryption will work fine, but due to the way the memory is mounted on modern Nexus devices, recoveries may be unable to mount the /data partition at all.
However if you are using a ROM based on a non-stock OS for your device (e.g. AOSP on an HTC Sensation) encryption may not even be able to turn on, and sadly fixing this problem when it arises is not high on the list of priorities for most developers, especially if your device isn't popular.
We are lucky that CyanogenMod seems to care a lot about privacy and security recently however. That may mean they focus more on encryption compatibility in the future, and most AOSP ROMs are based on CM, so fingers crossed for that.
But basically be aware YMMV when it comes to encryption on custom ROMs.
I tried to encrypt two Moto G's with the new official CM11, but after reboot and enter pin to unlock, the devices crashes with a black screen.
Encryption with stock firmware works fine.
I have been doing lots of ROM / Kernel experimentation on my VZW S4, and on attempting to take a backup of my most recent good configuration I received an error from TWRP that there is not enough space available because there is not enough space for my /Data partition which TWRP sees as 2438401MB or 2.4TB!
Since it is impossible that my on device /Data partition is 2.4TB, anyone have any suggestions on how to repair?
Or do I need to do a full install via Odin using the repartition option?
Thx.
Wow, it would be cool if you had 2tb, umm sounds like the recovery is corrupt, if it were me, I would try that first, if it does not work, do the odin flash to stock.
Good luck.
I reinstalled the TWRP recovery, and also reflashed a Verizon stock image file...but TWRP is still reporting my /data partition at 2.4TB.
I'm thinking I need to repartition, but have never done so on an Android device.
Recommendations?
I would try reading the odin features and what it does to re-partition. It has that option, but messing with the partition structure will cause a hard brick if not careful.
good luck.
Okay, I did an complete factory restore using the image from the following thread and now have a properly sized /data partition.
http://forum.xda-developers.com/showthread.php?t=2289325
Whew.
Thx.
morgej said:
Okay, I did an complete factory restore using the image from the following thread and now have a properly sized /data partition.
http://forum.xda-developers.com/showthread.php?t=2289325
Whew.
Thx.
Click to expand...
Click to collapse
hehe you got off easy...good deal.
Can you tell TWRP to do its backups to the SD card rather than internal memory?
Thinking about getting an S4 but w/only 9GB free, would like to keep my backups on the SD card I'm going to get for it. I know I could move them there after creating them, but don't want to deal with having to move them back and forth if I need to restore one.
Redflea said:
Can you tell TWRP to do its backups to the SD card rather than internal memory?
Thinking about getting an S4 but w/only 9GB free, would like to keep my backups on the SD card I'm going to get for it. I know I could move them there after creating them, but don't want to deal with having to move them back and forth if I need to restore one.
Click to expand...
Click to collapse
yes. thats what i do. However, I was using TWRP to backup my aokp rom that i set up and it wouldnt back it up and read the size would be 16gigs. However, my slim rom backup just fine without reporting a huge file size.
One day i decided i had enough of cyanogenmod and decided stock samsung was the way to go. I did a full backup with the latest version of clockworkmod, the full backup weights 2.99gb. When i try to restore it using any version of clockwork it gets up to restoring data then says Error while restoring /data!
i can boot back to cyanogenmod however apps are "installed" but they all say that they are not
Please help because i really need this phone
Either the file is corrupt or your sd card card could be damaged. It would be easier to flash stock with Odin and start again.
and if you have to /will go further without old backups, switch to TWRP after having rooted
Strange because i copied it without any errors... oh well. :crying: