Related
Last week something burnt out in my Streak, it wouldn't turn on, so I needed to send it to get repaired/replaced, as a little data insurance I took a dump of the internal SD card (just using dd in Ubuntu).
Now O2 are replacing my Streak, so I'll have a new one with a different IMEI, etc, and I don't want to open this one (I only opened the other one as it was an emergency). So I'm looking for help on restoring the backup I've taken without opening the phone, and once done, leaving it in a warranty-friendly state.
Obviously the first step is going to be rooting it, but what then? Is it simply a matter of copying all the files? Just thinking that might cause conflicts due to the new IMEI.
so i've got a similar (but reciprocal) problem... i had a malformed update.zip that pooched my internal microsd's system partition and the streak won't boot at all... I have a nandroid backup and i've pulled the internal microsd to find an empty ext filesystem that mounts just fine when I plug it into a linux laptop, but there's not a clear mapping from the system.img that I have and the contents of the accidentally wiped system partition...
SO, two things would fix this....
1. someone could send me a link to their raw 'dd' image of the system partition (~200mb)
2. or, I can keep figuring out how to use 'dd' with the system.img that I have to get the same results as the 'flash_image' tool...
would someone be so kind as to speed me along on this by giving me their system partition dump (1) or quickening my learning curve on (2) so that I can restore with the flash_image formatted nandroid dump of a working system partition???
Please, please....
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
nemith said:
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
Click to expand...
Click to collapse
My Ubuntu image does not mount this partition.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yep-- this is all taken care of in cm9
Update: I don't think you mentioned, but for completeness, there's also the serial file in /rom at devconf/DeviceId that will trigger a rom reformat if it goes missing. there are also some edge conditions that will trigger recovery/flashing such as the presence of certain update.zip files on SD. Also SD boots are treated differently by default, don't increase the boot count, etc. In short, this is very similar to how NookColor works with the added disadvantage of having to deal with, rather than simply ignore or remove, these various "go to recovery' conditions.
I can verify that Bauwks script works and allows internal booting without a bootloop.
Nemith, if you find the time can you add something like this to your CWM recovery.img? I think just adding the /bootdata mount and dd calls to the init.rc file should work. I was going to build my own CWM .img but figured you already had the source code handy.
I'de like to dabble in a CM7 port soon, while CM9 and Ubuntu ports are in-work
Thanks for all your hard work guys!
CWM recovery bootloop
bauwks said:
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
I flashed cm9 alpha 0.2 on my nook tablet using the nook tablet recovery apk. It booted into cyanoboot, however it had an error message that said disc majic error. I noticed I had put the wrong boot image on my sd card from the alpha 0.1. I rebooted 8 times and booted into cwm. Now in cwm I flashed a backup of my tablet. I then made the common mistake of clicking reboot recovery. Then trying to fix the bootloop into cwm recovery while unaware of the sevarity of what I was doing I went into mounts and storage and formated each bootdata, cache, data, emmc, rom, and system. I just restored my backup again and now I know what I need to do. My stock Nook recovery was overwriten when I clicked reboot recovery. Also I formated my rom folder and that might have contained my serial number and info.
I basicaly deleted my partions. while stuck in the cwm boot loop. Can you please send me or send me the link to a step by step way that I can get my nook tablet 16gb stuck in the cwm boot loop back to normal.
I tried using fastboot but I dont know the commands to open it. Also I dont know how to use adb either. I have a 2gig, and a 256 mb micro sd. I have a windows pc. Can you show me step by step how to restore those partions, how to do it on adb or fastboot, or the update zip method. I need help as soon as possible. Thanks.
Its similar to this
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
An image of /factory would be nice as well But less important as we're all (likely) using CM.
edit
Actually disregard this.. I have the nook hd+, but the /bootdata format info will probably be handy for any nook device.
Don't format bootdata or factory!
roustabout said:
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Click to expand...
Click to collapse
pbassjunk said:
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
Click to expand...
Click to collapse
To fix the Recovery Boot Loop caused by invalid/missing BCB and BootCnt in /bootdata, flash Succulent's flashable_fix_bootloop.zip posted at his blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (see under heading "I am stuck in a recovery boot loop?").
An image of /factory would be nice as well But less important as we're all (likely) using CM.
Click to expand...
Click to collapse
/factory contains a backup copy of stock ROM as well as a backup copy of the device data in /rom partition (romdata.zip), the latter includes data that is unique to each Nook (such as MAC address, security certificate, etc.) and hence is not replaceable with a copy from another Nook.
...
Don't format bootdata or factory!
Click to expand...
Click to collapse
Nor /romdata. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info.
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
weasel5i2 said:
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
Click to expand...
Click to collapse
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
tinkering said:
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
Click to expand...
Click to collapse
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
digixmax said:
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
Click to expand...
Click to collapse
Thanks for the link to leapinlar's post. That helps me to understand the problem and fix a bit better. I didn't see the zip that seemed to fit my situation on his post. I did a SD install non-rooted and I see only only emmc fixes on his post. I tried your fix with these steps and I must have done something wrong. Maybe you could point me in the right direction.
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
tinkering said:
...
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
Click to expand...
Click to collapse
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
digixmax said:
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
Click to expand...
Click to collapse
Sorry, I probably should have updated my last post. I was attempting to flash the repair incorrectly. Unfortunately, I have a new problem and have moved my question to the "[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc" thread.
The device would boot from SD. Was running CM10.2 and CWM recovery. The trouble I am having now is that I can't flash anything from the SD in CWM recovery because it wont mount the SD. (See details in thread referenced above.)
Thanks
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.
Hey Guys,
I have always used CWM Rom Manager but now it only bricks the phone when installed. "Encryption Error - Factory Reset", but that does not work, have to use AP Fastboot and reinstall JellyBean. Now that I have it up again, I want a recovery solution besides Titanium Backup that will backup the entire phone, like CWM did. So, I installed SafeStrap. (Rooted with Android 4.1.2)
Now I would like to format the internal SD Card to start fresh, but when I boot to recovery in SafeStrap, Wipe does not format the internal card. The terminal window in the Wipe action shows that it cannot find block device. But, the File Manager in recovery works just fine and the backup seemed successful. When I go to Advanced, Settings, there is one setting that cannot be unchecked. "Use rm -rf instead of Format?" No, I do not want to wipe the existing partition, I want to format the entire internal SD partition, so I do indeed want Format like CWM would do. Is there a way to uncheck this box and how do you do it?
SafeStrap does have a Terminal, use at your own risk. So do I need to Format the internal SD Card by command line? Command line Syntax, please? Since this is a deadly serious operation, I would hope to get an answer and someone to confirm it, if possible. Familiar with Linux so that might help.
Anyone can help, please?
Update:
I checked out the SafeStrap Terminal. It is very, very crude, does not display much information like a Linux shell would. I can enter parted or at least the command echos to the screen, but the print command does not even show the partitions on the block device for the Internal SD Card, /dev/block/mmcblk1p25. There must be a better way...
I think you have to go to the SLOT like the ROM-SLOT-1 to do this.The stock rom slot dosent allow you to format or wipe anything.
Sent from my XT910 using xda app-developers app
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