[Q] Custom ROMs + Encryption - Android Q&A, Help & Troubleshooting

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.

Related

[Q] Flash Kernel Using CWM

I am posting here as there is not sub-forum for Xperia Pro.
I want to flash kernel using CWM already installed on my phone. Is it possible? If so, how do I go about it?
PS: I found a thread which is for Samsung phones here.
I don't think so
There is no way to flash a Kernel for SE phones faik
Were is our moderator!
Sent from my MT15i using Tapatalk
Can anyone tell me why kernel cannot be flashed via flash_image and the like. Is it because /boot partition is locked in Xperia phones? Or because the there is no proper flash_image made for Xperia phones?
That's something like ; doing a bypass surgery while you're awake
Something like that ^
Qwerty123 \m/ said:
That's something like ; doing a bypass surgery while you're awake
Something like that ^
Click to expand...
Click to collapse
I am not a complete nooby. flash_image can be used on (at least) Samsung phones, to flash kernels.
I have a nokia n900(linux kernel)...and i can flash kernels from the phone itself...dual boot maemo OS and android...restore the whole system image on the phone itself...but on neoV...it is not possible.
dont know about other android phones because neoV is my first android.
On PC you can update BIOS, on some motherboards you can do it from Windows, on others you can use some utility in BIOS setup program, on another motherboards you need true DOS and use BIOS flash program, same is with PC video cards, with PDAs...
ameer1234567890 said:
Can anyone tell me why kernel cannot be flashed via flash_image and the like. Is it because /boot partition is locked in Xperia phones? Or because the there is no proper flash_image made for Xperia phones?
Click to expand...
Click to collapse
Because SE xperia phones DONT HAVE recovery partitsion!
taaviu said:
Because SE xperia phones DONT HAVE recovery partitsion!
Click to expand...
Click to collapse
Exactly what does flashing a kernel with flash_image have to do with recovery partition?
ameer1234567890 said:
Exactly what does flashing a kernel with flash_image have to do with recovery partition?
Click to expand...
Click to collapse
The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
Here are the standard partitions on an Android phone:
/misc - not sure what this is for.
/boot - bootloader, kernel
/recovery - holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system - operating system goes here: Android, Sense, boot animation, Sprint crapware, busybox, etc
/cache - cached data from OS usage
/data - user applications, data, settings, etc.
The below partitions are not android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio - the phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax - firmware for Sprint's flavor of 4G, WiMax.
During the rooting process, a critical piece of the process is disabling a security system built into the bootloader that protects these partitions from accidental (or intentional) modification. This is what's referred to as "unlocking NAND." The security system can be set to active or inactive. S-ON means the security is in place (NAND locked). S-OFF means the security is off (NAND unlocked). When S-OFF, you have the ability to modify all partitions. With S-ON, you only have write access to /cache and /data. Everything else is read-only.
When you flash a custom ROM, that ROM typically includes a kernel and an OS. That means the /boot and /system partitions will be modified at a minimum. Some ROMs require a clean install, so a format of the /data and /cache partitions is sometimes built into the .zip that you flash. This is essentially doing a factory reset. See next paragraph.
When you do a factory reset (AKA: wipe, hard reset, factory wipe, etc.), you are erasing the /data and /cache partitions. Note that a factory reset does NOT put your phone back to its factory state from an OS standpoint. If you've upgraded to froyo, you will stay on froyo, because the OS lives in /system, and that is not touched during a factory reset. So "factory data reset," as it says under Settings > SD & phone storage, causes confusion. It's not a factory reset. It's a factory DATA reset. Now you know the distinction.
The SD card can also be partitioned to include a section dedicated to storing user apps. To create the partition, your SD card needs to be formatted. Typically a user will copy all the contents in the SD card to a PC hard drive, wipe the card and partition it, and then copy everything back.
Original http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
taaviu said:
The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
Here are the standard partitions on an Android phone:
/misc - not sure what this is for.
/boot - bootloader, kernel
/recovery - holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system - operating system goes here: Android, Sense, boot animation, Sprint crapware, busybox, etc
/cache - cached data from OS usage
/data - user applications, data, settings, etc.
The below partitions are not android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio - the phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax - firmware for Sprint's flavor of 4G, WiMax.
During the rooting process, a critical piece of the process is disabling a security system built into the bootloader that protects these partitions from accidental (or intentional) modification. This is what's referred to as "unlocking NAND." The security system can be set to active or inactive. S-ON means the security is in place (NAND locked). S-OFF means the security is off (NAND unlocked). When S-OFF, you have the ability to modify all partitions. With S-ON, you only have write access to /cache and /data. Everything else is read-only.
When you flash a custom ROM, that ROM typically includes a kernel and an OS. That means the /boot and /system partitions will be modified at a minimum. Some ROMs require a clean install, so a format of the /data and /cache partitions is sometimes built into the .zip that you flash. This is essentially doing a factory reset. See next paragraph.
When you do a factory reset (AKA: wipe, hard reset, factory wipe, etc.), you are erasing the /data and /cache partitions. Note that a factory reset does NOT put your phone back to its factory state from an OS standpoint. If you've upgraded to froyo, you will stay on froyo, because the OS lives in /system, and that is not touched during a factory reset. So "factory data reset," as it says under Settings > SD & phone storage, causes confusion. It's not a factory reset. It's a factory DATA reset. Now you know the distinction.
The SD card can also be partitioned to include a section dedicated to storing user apps. To create the partition, your SD card needs to be formatted. Typically a user will copy all the contents in the SD card to a PC hard drive, wipe the card and partition it, and then copy everything back.
Original http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
Click to expand...
Click to collapse
As I had mentioned before, I am not a nooby.
ameer1234567890 said:
As I had mentioned before, I am not a nooby.
Click to expand...
Click to collapse
Then show us HOW to install kernel via recovery?
Dont talk about Samsung and HTC option to install kernel via recovery. I have HTC Desire my second phone and yes i know there is option install kernel via recover(also im tested ALL desire roms and kernel already).
SE xperia have just different partitions layout and we simply cant flash kernel via recovery.....BUT i dont want tell you its IMPOSSIBLE.
Be nice and show us how to do that
PS:im tottaly noob.
Boot holds kernel and initrd not the actual bootloader, that is what should be writable. Provided the actual bootloader is not damaged it should be possible, however because there is no recovery partition it is riskier, but s1tool can restore bootloader......
Hmm
Sent from my MT11i using Tapatalk
I have S2(of course i have and xperia neo) and i dont flash with CWM i flash with odin or heimdall; CWM method is not sure.
In my opinion,and i'm NOT an expert, it easy to flash a kernel for xperia with flashtool or using fastboot from adb.
OK guys, you might have misread it. I am looking for a way to flash kernel not just using CWM (eventhough the title says so), but using any method without having to connect to a PC. One such possible method is to use flash_image in terminal, which does not work in my phone.
PS: The fact that I am not a noob doesn't make me a pro.

[Q] Talk, Trebuchet errors. Explain cm10 boot menu? iamafan's build

Hi all, I built my sdcard per: http://iamafanof.wordpress.com/2012/...r-nook-tablet/ (built by"Succulent")
My kids have two NT's. With two 16GB Sdcards, one class4 the other class 10. I know class4 is recommended, but one poster in forums said he's taken images of CM built on class4's and applied this image to class 10's in several cases and has had no problems. So I thought what the heck, can't hurt to try, so that's what I did (using Winimage). It booted fine 5 or 6 times for me, and I installed several APK's of games from Humble Bundle . I turned over the Nook to my little girl and she brought it back to me later showing she gets errors on boot, after swiping the lock symbol to unlock it. One is "Unfortunately, Talk has stopped". If you click OK on this, you get ""Unfortunately, Trebuchet has stopped". Clicking OK on this does nothing, it keeps popping up indefinitely. I don't know if the sdcard is hot pluggable (can be removed with power to the tablet), but she did admit to doing this. So I'm wondering if some corruption occurred to the CM build on the sdcard. Has anyone seen these errors? I could reflash it from the image I made off the class 4, but want to understand what happened so we don't run into it again. The funny thing is, I don't recall the startup wizard off the 1st class4 card prompting me with several screens regarding Google crap like it did on the 2nd card which was flashed from the same image. That was even after telling it I had no Google acct hoping it would leave me alone.
can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
baytee said:
...
So my question is, can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
Click to expand...
Click to collapse
Yes,
internal boot - boots Rom in emmc
Internal recovery - recovery in emmc
Sdcard boot - boots your sdcard Rom.
Sdcard recovery - boots sd card recovery ( keep recovery.img in root of sdcard for it to load recovery)
Sdcard altboot - alternate recovery ( not necessary, unless you want both cwm and twrp at same time)
Fastboot - fastboot mode , fastboot commands to flash .img file etc with this method .
As for your problem, try entering recovery, wipe cache and dalvik cache partition (I've done this on emmc version, never tried sdcard version of any Rom) this may solve the issue. If not try factory reset.
And removing sdcard while device is switched on is called hot swapping , hot plug is a CPU governor. Not sure if sdcard roms are hot swappable, but I think not.
Sent from my ST27i
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? Once you get into it, you have various choices like the ones you mention? (I'd read that this choice was to backup your NT to sdcard). And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
baytee said:
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? I'd read that this choice was to backup your NT to sdcard. But once you get into it, you have various choices like the ones you mention? And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
Click to expand...
Click to collapse
Um I don't know much about how it works for sdcard Rom. I've always only used emmc version. I guess if you were to enter recovery, it would access the stock cache partition by default , and we aren't trying to clear that.
Try this - use titanium backup (only talking about your sdcard Rom here, nothing to do with your stock) and in options, you may be able to wipe your cache or dalvik cache.
Or,
boot into your sdcard Rom, in settings > backup and restore > factory reset. This will delete all user data and return Rom to original Cm10 that you flashed on sdcard.
Or if it's only google talk and trebuchet launcher issue, install a new launcher (go launcher, adw etc) , then use titanium backup to uninstall trebuchet and talk.
Sent from my ST27i
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
baytee said:
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
Click to expand...
Click to collapse
In cwm, enter mounts and backup, then (if) you see /sdcard /cache, mount that and format that ONLY.
Do not format anything else as some options can brick device (Rom, bootdata, factory etc)
Wiping cache is safe (99%)
Again, I have never used sdcard Rom so I don't know what will show up in your recovery. But if you see something like sdcard cache, it can be cleared. If it doesn't specify sdcard, let us assume it refers to stock emmc.
Sent from my ST27i
How do I get into CWM?
baytee said:
How do I get into CWM?
Click to expand...
Click to collapse
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
digixmax said:
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
Click to expand...
Click to collapse
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
baytee said:
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
Click to expand...
Click to collapse
Why backing up now when it's not working? Fix your issue, then make a backup. So the next time there's a problem you can restore to working condition.
Sent from my ST27i
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
Click to expand...
Click to collapse
I don't know about your bootloop issue, but I don't think it's a sdcard class issue.
Anyhow, now that you have stock backup, aren't you going to consider flashing cm10 internally? Do you actually use stock?
Sent from my ST27i
I'm a little leery of it, at least while it's under warranty. I don't know how reliable recovery is.? Besides, my daughter wasn't thrilled with it being down for several days with me fussing with it and asked if she could have her "B&N boot" back I admit It is a bit of a pain having to pull it out of it's case, lift the flap, pop-in or out the sdcard to switch between them. (& also to have to remember to always turn it off b4 removing/inserting)
I may do it in the future though. Thanks for the help
FWIW, you don't have to actually remove the card to boot into stock. Just reboot, hold "n" to get into Cyaonoboot menu and choos "int boot" or something like that, and it will boot to stock with the sd-card still inserted.
Great, thanks for that tip!
Card died
I think many of these symptoms could have been caused by a dying card. It did have a corruption error once, and then it finally completely died. Just for anyone else that runs into these.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
...
Click to expand...
Click to collapse
FWIW, /cache does not need to be backed up, which should help reduce the backup space requirement.

Installing ROM with Encryted Data or Remove Encryted Data?

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

[Q] Data Recovery from sick galaxy s3

My partner's phone has suddenly decided of its own accord that it wants to reformat the internal memory, presumably due to some sort of unrecoverable data corruption. The message that came up informing us of that was something along the lines of "Phone memory is damaged. The data partition is damaged, you should restore your phone to factory settings. Doing so will delete all your data" and then a single button saying "Restore phone to factory settings". (I say something along the lines because that is a translation from the actual Spanish message that comes up)
So, she has a bunch of data that she would prefer not to lose (mostly backed up, but some apps not, and photos missing for last month or so of our daughter - usual story).
So I have been hunting around to see if it would be possible, and mostly what I have found isn't too optimistic. I did however find the following link that did seem somewhat promising:
http://forum.xda-developers.com/showthread.php?t=1994705
So it is for the Nexus and the title refers to internal data, but then also refers to SD cards, but the process does seem to refer to internal data. I have a bunch of questions about the process in the context of an S3:
1. Anyone think this process is transferable to the S3? If so what is the equivalent data partition name? For the Nexus it appears to be /dev/block/mmcblk0p12. Would that be the same for the S3?
2. I am going to have to root this device first unfortunately (meaning I am going to have to write to the internal memory ahead of doing the RAW dump, obviously not ideal, but I see no way round it). Is the process described here (root only option):
http://forum.xda-developers.com/showthread.php?t=2046439
appropriate, or am I going to need to somehow find out what version my partner was on (not 100% sure but I think it was 4.1.2) and adjust accordingly?
3. Do I have to have a fully working version before I can install busybox, or is that something that can be put in place using CWM?
4. Likewise do I have to have a fully working version before I can get ADB working or can I get ADB to work with CWM? I have found a couple of threads that suggest ADB works natively with CWM and others that suggest not.
5. I know how to turn on USB debugging if I can get into setttings of a normal Android system, but how do I do that without a working version, can that be done via CWM?
I guess basically I want to know what would be the minimal set of steps that I can run through to get Busybox installed on the phone, (presumably rooted) and talking ADB to my PC. I say minimal set of steps becuase the less writing I do, the more data might be salvagable.
I am surprised that there isn't some bootstrap version that can't just pull off the existing data and allow you to manipulate it elsewhere (which is what the process I have put the link to seems to do) but it seems much more involved than just a bootstrap.
Be gentle with me - I am just a noob!
bobalucci said:
So, she has a bunch of data that she would prefer not to lose (mostly backed up, but some apps not, and photos missing for last month or so of our daughter - usual story).
Click to expand...
Click to collapse
if its only that I would do it a bit more simpler:
for app data: make a nandroid backup and after the reformat you can use nandroid manager to restore your apps and their data (if you simply restore the damaged data partition as a nandroid backup the problem could accur again). but maybe if the apps and data are damaged because of the damaged data partition they could maybe not be restored.
for photos etc. you can flash philz touch and then follow the steps in the main thread of philz touch on how to put the aroma.zip onto an external sd card (just search for aroma in the thread, you'll find it). aroma is like a file browser with root priviliges which can be executed through recovery. with that you can copy your photos onto the external sd card
btw. I am not sure if the standard factory reset wipes the internal sd cards data. if you only format your data partition photos etc. shouldn't be affected (for example through philz recovery you can just format data partition).
Data Recovery from sick galaxy s3 (installing custom recovery)
Thanks for that... that makes sense... any way I can get the custom recovery onto the phone without having already reformatted the data partition? All the methods I have seen for installing a custom recovery require normal access to the phone... and I don't have that at the moment - just to a screen that tells me that it will reformat the data partition - and I don't want to do that if I can avoid it - as it will modify the data I am trying to save.
Darkened_Sky said:
if its only that I would do it a bit more simpler:
for app data: make a nandroid backup and after the reformat you can use nandroid manager to restore your apps and their data (if you simply restore the damaged data partition as a nandroid backup the problem could accur again). but maybe if the apps and data are damaged because of the damaged data partition they could maybe not be restored.
for photos etc. you can flash philz touch and then follow the steps in the main thread of philz touch on how to put the aroma.zip onto an external sd card (just search for aroma in the thread, you'll find it). aroma is like a file browser with root priviliges which can be executed through recovery. with that you can copy your photos onto the external sd card
btw. I am not sure if the standard factory reset wipes the internal sd cards data. if you only format your data partition photos etc. shouldn't be affected (for example through philz recovery you can just format data partition).
Click to expand...
Click to collapse
Data recovery sticky ???
http://forum.xda-developers.com/showthread.php?t=2344125

Wiped data before flashing ROM but it's still showing up

I'm pretty new to flashing ROMs. My phone is rooted using all in one toolkit, s-off with sunshine. TWRP is my recovery.
I made a backup of my rooted stock ROM , then used TWRP manager to flash cm11. I checked to wipe all the data and dalvik before flashing. Cm installed with no issues.
Once I finished setting it up, I installed es file explorer again and noticed that all my files from my internal storage are still accessible. Its just listed under 0. Everything is still in tact tho.
Did I do something wrong? I don't understand why I still have all these files.
mattprice86 said:
I'm pretty new to flashing ROMs. My phone is rooted using all in one toolkit, s-off with sunshine. TWRP is my recovery.
I made a backup of my rooted stock ROM , then used TWRP manager to flash cm11. I checked to wipe all the data and dalvik before flashing. Cm installed with no issues.
Once I finished setting it up, I installed es file explorer again and noticed that all my files from my internal storage are still accessible. Its just listed under 0. Everything is still in tact tho.
Did I do something wrong? I don't understand why I still have all these files.
Click to expand...
Click to collapse
You have to have internal storage checked for it to be wiped
^^^This. The data that was wiped was system data, not your personal data.
Thanks for responding so quick,
I checked all of the options under install on twrp manager. Looking back, it says wipe data, wipe cache, wipe dalvik. There wasn't an option for wipe internal storage.
Is there anything I can do to fix this now? Or would I just have to go into twrp and reflash cm from recovery, making sure to check wipe internal storage?
Also, if I leave it as is, is it going to cause any problems?
mattprice86 said:
I checked all of the options under install on twrp manager. Looking back, it says wipe data, wipe cache, wipe dalvik. There wasn't an option for wipe internal storage.
Is there anything I can do to fix this now? Or would I just have to go into twrp and reflash cm from recovery, making sure to check wipe internal storage?
Click to expand...
Click to collapse
First off, ditch TWRP Manager, its a needless middle man (you're talking about the TWRP Manager app, right?).
If you boot into TWRP and select Wipe, you will see under "Advanced Wipe" there are a slew of wipe options (but be careful what you pick, as there are options to wipe things like the removable SD).
HOWEVER, you don't need to wipe the internal storage to flash a ROM. Yes, you need to wipe user data (/data) in most cases, and also cache and Dalvik. But wiping internal storage (virtual SD, also called sdcard on ES File Explorer, or sometimes /0) is not needed. For most practical purposes this partition is treated like a removable SD card. In fact, by default, backups like your TWRP nandroid and Titanium Backups are stored here. So if you wipe, you will lose those (unless you move/copy them to the removable SD or somewhere else like your computer).
Some folks like to wipe internal storage when they flash a ROM, just for general cleanup purposes. But its a personal choice, and not really necessary IMO. And as mentioned doing so will wipe your backups unless you save them somewhere else that isn't going to be wiped.
Thank you so much for clearing that up.
Yes, I was talking about twrp manager. You're right, after I checked the options, all it did was reset and boot up twrp. Pretty useless...
So since I still have all my game data stored, can I just copy it over somewhere to retain where I was at? I'm talking about android/obb data.
How would I go about integrated all my previous data into this current software? Let me know it my question made sense or not
mattprice86 said:
Yes, I was talking about twrp manager. You're right, after I checked the options, all it did was reset and boot up twrp. Pretty useless...
Click to expand...
Click to collapse
I think some folks like to use it to install TWRP. But installing with fastboot is easy, and also important to know how to do if you have issues someday and need to re-install TWRP from a non-booted condition.
So yeah I agree that TWRP Manager is pretty useless.
mattprice86 said:
So since I still have all my game data stored, can I just copy it over somewhere to retain where I was at? I'm talking about android/obb data.
How would I go about integrated all my previous data into this current software? Let me know it my question made sense or not
Click to expand...
Click to collapse
Use the app Titanium Backup to migrate app data when flashing ROMs (also handy to migrate app data to a new phone). And paying the few dollars for the Pro Key and getting the batch backup/restore functions is well worth it if you are flashing ROMs.
Do not use Titanium to migrate any system data to a new ROM, as this will likely cause problems. Just apps and app data. I've had success migrating SMS with Titanium as well. But other things like Settings and Homescreen setup, I usually just do again manually after flashing a new ROM.
As mentioned in my post above, the default save location for Titanium Backup data is the internal storage. So do not wipe internal storage when flashing a ROM, or you will lose your backup data.
Just copying the game files will most likely not work to migrate your game save data.
Thanks for all the help, I really appreciate it.
I used titanium backup and extracted my apps and data from my nandroid backup. Worked pretty well.
The only thing I'm having trouble with now is getting my info like contacts and stuff to sync. It says it's synced, but I'm not seeing it.
I wanted to install HTC backup again and try and restore that info. Would that work?
mattprice86 said:
The only thing I'm having trouble with now is getting my info like contacts and stuff to sync. It says it's synced, but I'm not seeing it.
I wanted to install HTC backup again and try and restore that info. Would that work?
Click to expand...
Click to collapse
I can't say, as I don't use HTC Backup.
I prefer to just have my contacts on my Google (Gmail) account. This is the default on the phone, so unless you changed it, your contacts should all be on the cloud on Gmail (you can login to Gmail on a computer and confirm your contacts are there). Then will automatically restore to the phone when you first setup and enter your Google login and password.
If you've confirmed your contacts are on Gmail, and still not synching, go to Settings>Accounts & sync>Google, go to where Contacts is checked, uncheck it, and then check it again. Sometimes the sync will just get "stuck" and this will clear it up.
One M8 stuck on GPE 5.0.1 ROM boot animation
I foolishly reset factory data using TWRP under Wipe, and when I try to reinstall the GPE 5.0.1 ROM I couldn't find it. Then I try to restore my backed up Sense ROM and I couldn't find it under Restore. Maybe I deleted it and I forgot about it. Help me? I don't have MicroSD to store the GPE ROM which I thought would solve my problem because I thought I may have deleted the GPE ROM .zip file when I reset factory data. Now I am stuck on GPE ROM bootanimation the moving around dots. I need help please someone?
muqrimusa said:
I foolishly reset factory data using TWRP under Wipe, and when I try to reinstall the GPE 5.0.1 ROM I couldn't find it. Then I try to restore my backed up Sense ROM and I couldn't find it under Restore. Maybe I deleted it and I forgot about it. Help me? I don't have MicroSD to store the GPE ROM which I thought would solve my problem because I thought I may have deleted the GPE ROM .zip file when I reset factory data. Now I am stuck on GPE ROM bootanimation the moving around dots.
Click to expand...
Click to collapse
If you did the "default" TWRP factory reset (data, Dalvik, cache) this is not foolish, and is the correct wipe for moving to a new ROM.
You either bypassed the default, and went to "Advanced" and wiped the internal storage; or there is also the occasional instance where internal storage is corrupted by no fault of your own (more common with oldr TWRP versions?).
adb push a ROM to the internal storage (or adb sideload flash) while in recovery.
okay I kind of fixed my One M8. But one problem remains, I can't use my internal storage. My Camera App can't use the internal storage so does all the other apps such as Whatsapp or downloads from Chrome. It's as if my internal storage is not there or somehow malfunctioned or the ROM doesnt support the use of internal storage. But before I got into this problem (I forgot how I got it in the first place as it happened months ago only now I was able to fix my One M8), it worked perfectly fine, the Storage had no problem. But I had problems with Wifi, I thought maybe reflashing the ROM was a good idea to fix this but it didn't instead I can't access my internal storage by File Manager or by PC. If you have any solution please help me. Thanks in advanced.
muqrimusa said:
okay I kind of fixed my One M8. But one problem remains, I can't use my internal storage. My Camera App can't use the internal storage so does all the other apps such as Whatsapp or downloads from Chrome. It's as if my internal storage is not there or somehow malfunctioned or the ROM doesnt support the use of internal storage. But before I got into this problem (I forgot how I got it in the first place as it happened months ago only now I was able to fix my One M8), it worked perfectly fine, the Storage had no problem. But I had problems with Wifi, I thought maybe reflashing the ROM was a good idea to fix this but it didn't instead I can't access my internal storage by File Manager or by PC. If you have any solution please help me. Thanks in advanced.
Click to expand...
Click to collapse
Broken WiFi is usually a symptom of wrong (outdated) firmware for the current ROM.
Internal storage may be corrupted. Try to connect to a computer and format it, or you can try RUU.
Or try to re-flash custom recovery, or update or try a different one (if TWRP, try CWM/Philz or vice versa). Some folks fixed similar internal storage issues by flashing recovery.
I need help again.. I decided to format all my data but I kept my backup in the internal storage.. But after rebooting the phone it works but then I can't download apps from the play store or from chrome.. also I can't transfer files from my pc to my one m8.. But I can take photos (which I think uses internal storage).. Also my guest mode is not working.. Ithought something must be wrong with the internal storage so i wiped it out.. When i rebooted everything is black but when I long press the power button 'power off' shows up.. Something must be wrong.. Oh when connecting to my pc it shows CD Drive instead of HTC_OneM8 like it usually would.. Pls reply even when there's no hope to fix this phone at all..

Categories

Resources