I've been using jt's ICS rom (it's awesome, btw), for a couple of days now and have my phone set up exactly the way I want it. But when I attempt a backup with cwm4_fixed_for_cm7 I get this error:
"Error while generating md5 sum"
Need some help from greater minds than mine
If you had done a search on rootzwiki in the ics thread and discussion thread you would find that this is a known issue.
good day.
here is the fix:
Fix CWM 5.x Nandroid Backup
Let's just say you did what I did today, and did a backup, flashed another ROM, then tried to restore back to the nandroid you just made. Didn't work did it. Come to find out, I wasn't watching the backup, and it fails to generate an MD5 sum. I did a little searching to find out what to do, and I found the following steps (not my work...thanks goes to "desmail" for sharing this).
To fix this is assuming you did not change the folder names and let Clockworkmod create them.*
Code:Checking MD5 sums...
MD5 mismatch!
- Plug your phone to the computer
- Open a Terminal and type:
Code:adb devices
adb shell
# cd /sdcard/clockworkmod/backup/2011-06-29.20.22.53
# rm nandroid.md5 (Probably will fail - for me, the file was never there to begin with...this is fine)
# md5sum *img > nandroid.md5
# exit
****Make sure you change "2011-06-29.20.22.53" to the name of your backup folder*****
- Re-run the restore and everything should be fine.
You will most likely need the Nexus S ADB drivers to accomplish this.
Thanks, droidstyle. I'm getting errors when typing commands into the terminal (you do mean the command prompt, right?), but I will try again later.
azok79 said:
Thanks, droidstyle. I'm getting errors when typing commands into the terminal (you do mean the command prompt, right?), but I will try again later.
Click to expand...
Click to collapse
you need to have adb setup with google drivers or it will not work. Go to cyanogenmod 7 website and look up adb/sdk install guide.
actually jt's v4 release has the nadroid backup issue fixed so I would just flash that...its alot better than v3 imo anyway. I believe its post#875 on pg88, not in the op.
Related
I'm tryin to restore a nandroid backup its giving me a Error : run 'nandroid-mobile.sh restore' via adb! I have to 2 backups and same error for both and also wiped data/cache. Couldn't find much on this error in the search, thanks.
I would like to know this also.
-------------------------------------
Sent via the XDA Tapatalk App
While in recovery mode.
Connect the phone to the pc and run "adb shell". Android sdk must be installed.
Then run the command "nandroid-mobile.sh restore"
The error was pretty much self-explanatory. XD
xstackedx said:
While in recovery mode.
Connect the phone to the pc and run "adb shell". Android sdk must be installed.
Then run the command "nandroid-mobile.sh restore"
The error was pretty much self-explanatory. XD
Click to expand...
Click to collapse
when i do that i get...
Using G1 keyboard, enter a directory name substring and then <CR> to find matches or just <CR> to accept default:
If i try the nandroid restore with that box open, i still get the same error. but i'm not sure if i'm supposed to do anything with the above. just don't want to mess something up as i'm fairly new with this stuff. thanks
Yes the "Using G1 keyboard, enter a directory name substring and then <CR> to find matches or just <CR> to accept default:" was instructions. Then you hit enter on your keyboard, then it allows you to select a rom by typing a number.
thanks i may try that here in a bit... but wandering why the nandroid restore won't work by itself from the recovery or is it supposed to be like that? thanks again.
Edit: I found my problem, i was renaming the first folder inside the nandroid folder on my sd card rather than the second folder to try to keep roms labeled a little better... thanks again for the help.
Just an FYI for anyone else having this problem. From my experience the error is caused by low battery. Every time i get the error i plug it in via usb and it works.
Also what I have found is that if I rename the restore file and put a space in the title, it does that... such as:
BDS-20100513-1708AloysiusV11OC (this one is good)
BDS-20100513-1708Aloysius V11 OC (this one does not work and gives me that error...)
Let me first say that I have read every post I could find on this subject and tried them all with no success. I rooted my Aria using the Ubuntu Live CD so I could use Titanium backup and eventually try different roms. My phone is still using the stock rom. I then installed Titanium backup which reports "your system settings will prevent you from restoring applications. to correct this go to your phone's settings, then in "applications" and tick the "unknown sources" check box."
The unknown sources check box is of course not there because I have not been able to successfully run the code for allowing non-market apps.
From terminal in the Ubuntu Live CD with USB cable connected and set to charge only. I tried and got "remount failed: operation not permitted." at the adb remount step.
Linux Code:
sudo su
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
I downloaded the android-sdk_r07 and extracted it to my C drive. From a Windows command prompt, I changed to the sdk\tools folder. Adb devices sees the phone but adb remount fails with "remount failed: operation not permitted."
Windows Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
I found a post from attn1 that I have not tried that said:
"Put your phone in recovery mode. Go to advanced>mount system and mount data. Follow steps in post #13 (using the windows or linux code above) in cmd screen and you'll be fine." I am not comfortable in trying this approach as there are not enough specific step details and I don't want brick my phone.
I would really appreciate the correct detailed steps to enable non-market apps using the supplied code either from Windows or the Ubuntu Live CD. Thank you in advance.
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
winsettr said:
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
Click to expand...
Click to collapse
Thank you winsettr for your post. It looks like running the commands from recovery did indeed work. Titanium backup no longer reports the "your system settings will prevent you from restoring applications. To correct this go to your phone's settings, then in "applications" error.
However, I expected to see the settings\applications unknown sources check box check box and it is not there. I guess I will have to try side-loading an app to confirm that it will work.
I think that gui option would be part of the rom, a part that AT&T has removed... So yeah, see if side- loading works now.
Sent from my Liberty using XDA App
FYI, I am indeed able to side load now from an .apk copied to the sd card. However, I am not able to install from an internet link. Trying to do so generates a "your phone is not authorized" error message.
Until you get a custom rom running, I wouldn't worry too much. Sounds like you can get any app you want (just download internet apps to sd then install). There may be an additional setting in settings.db but that's beyond my knowledge...
Sent from my Liberty using XDA App
I have a refurbed Eris because my old one had the trackball issue. When I rooted that one I went about the old school ADB way and had s=off. When I got my refurb and got it all activated I went and installed the 1 Click Root and I can't seem to get the engineering bootloader. I tried the steps in jcase's thread, but it didn't do anything but wipe my phone. After that I tried flashing engtools.zip, that flat out did nothing at all.
Basically my question is, how should I go about getting it on there? I have no problem wiping my phone to stock with HTC's RUU package they put out and starting from scratch. Also, is there any way to make the 1 Click Root include the engineering bootloader? Maybe somebody could figure out what the parse error is with jcase's old abandoned work here:
http://forum.xda-developers.com/showthread.php?t=742735&highlight=engineering+bootloader
Scroll down a few replies for the link.
I'm at a loss, so any help is greatly appreciated.
So, here's the deal.
The only thing which prevents somebody from flashing the (HTC) "Root" PB00IMG.ZIP ROM, or ANY OTHER PB00IMG.ZIP ROM OR RUU UTILITY is the "Main Version is Older!" problem. This is the same thing that kept Eris "Leakers" from successfully using the "Root PB00IMG.ZIP" ROM
It turns out that this top-secret "Main Version" number is stored (as a string) in the "misc" partition. (It is also stored in the hidden "misc3" partition, but that's a story for another time). Now, what would happen if you grabbed a copy of your misc partition (using "dump_image" in Amon_RA), hand patched a very old "Main Version number" into the file, and then flashed this hacked "misc.img" back to the misc partition on your phone?
Answer: it would allow you to flash ANY RUU or PB00IMG.ZIP file - including the HTC "Root PB00IMG.ZIP ROM", which installs the 1.49.2000 S-OFF bootloader.
Now, Jcase has already done all of this work for you, except for flashing the resulting "misc.img" to your phone - that's your job.
His original instructions are in this thread:
http://forum.xda-developers.com/showthread.php?t=726885
BUT NOTE! There was/is a typo in the fourth line of his instructions!
The correct sequence is:
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image misc /data/local/misc.img
Note that Jcase could have made these instructions even simpler by noting that there is already a version of flash_image built-in to the Amon_RA recovery, and it suffices to just copy his "misc.img" file to the SD card, fire up Amon_RA, and
Code:
adb flash_image misc /sdcard/misc.img
OK, that's it; the rest is up to you. Don't forget that if you let the HBOOT+(Root)PB00IMG.ZIP flash run all the way through, it installs an old radio , and you will also need to get the Amon_RA recovery back on the phone. (Even though it is the "root" ROM, you can use OneClick to do that). You can avoid both those things if you use the toastcfh "battery pull trick" (documented here, with pictures) at the early part of the HBOOT+PB00IMG.ZIP install.
Don't forget to make a Nandroid backup before you begin.
good luck.
bftb0
PS - I forgot to add the observation that I have tried doing the bootloader install as a flashable .zip method with both of the S-ON bootloaders as a starting point. It worked only for the 1.49.0000 S-ON bootloader, but not for the 1.47.0000 bootloader. I suspect that is why the method you were trying is not working for you. (I used "erisengspl.zip", rather than Jcase's method, but my guess they will both behave the same way - the problem is due to the bootloader version, not the flashing method)
Thanks for all the help, seriously, but literally none of that worked. ADB acted like flash_image wasn't even there. When I tried to install flash_image I got a host of errors. I think I'm gonna start over and try from stock 2.1 and try to root it old school, though I'm not sure any of the guides are relevant anymore.
I'm beginning to think this isn't worth the fighting and wiping and general work.
Thanks again though, that was really detailed and helpful.
dalladubb said:
Thanks for all the help, seriously, but literally none of that worked. ADB acted like flash_image wasn't even there. When I tried to install flash_image I got a host of errors. I think I'm gonna start over and try from stock 2.1 and try to root it old school, though I'm not sure any of the guides are relevant anymore.
I'm beginning to think this isn't worth the fighting and wiping and general work.
Thanks again though, that was really detailed and helpful.
Click to expand...
Click to collapse
It works - I have done it possibly more than 100 times on my phone.
If adb says "flash_image not found", or something like that, it just means that you didn't put that file into the current folder (probably the same folder that adb.exe is in ( either <sdk-directory>/tools or <sdk-directory>/platform-tools )
same deal with "adb push misc.img" ... if a file name is given as an argument to a program launched by the command window (in both Unix and Windows), and it does not start with an explicit path, it is presumed to be in the "current directory".
So, try again, but put the flash_image file and "misc.img" file in the same folder that you are running the adb command from.
If you get an error message in one command, there is no point in running the subsequent command - figure out where your mistakes are before you proceed to the next command.
There are also plenty of opportunities to make a mistake if you are typing things by hand, too - so I recommend cut and paste. (In the Windows command window, there is a pulldown menu from the top bar: Edit -> paste)
bftb0 said:
(In the Windows command window, there is a pulldown menu from the top bar: Edit -> paste)
Click to expand...
Click to collapse
My turn to butt in. If you didn't know already, although you have to go to the pulldown menu for most things, you can actually right-click anywhere in the command window and choose Paste. This was a huge relief to me when I "discovered" it as going to the pulldown menu was a PITA to do very often.
I have been unlocking/rooting since i pre-ordered my G1. I am no way an expert. I just follow GREAT instructions by other users/devs. Anyhow everyone knows how bad the samsung vibrant is b4 a new rom. So i took my girlfriends Samsung Vibrant (tmobile).
my steps
1. downloaded rom manager
2. flashed to the 2.5.1.2
3. downloaded bionix v 1.3.1 (team whiskey)
4. made a backup of the current stock with rom manager (should of used nandroid or titaium)
5. Needed to restore to stock backup i made, cause she needed some contacts, and she doesnt use google sync! "smack, now she does"
6. Restored backup from rom manager! it boots back up and does something weird. i see the lock screen but the signal bar is a blue circle crossed out, and nothing works, it just flips out right there.
So i boot into clockwork (cause i cant do anything in the os) and install the bionx file again. It works great, and the phone rocks once again........but i still need those contacts.
Please please help me.
Does it have something to do with the newer recovery i put on it. ???
I also apologize for asking all this, but i just don't know what i did, so i don't know what to search for on the Forums
Thanks in advance.
M
This may or may not work...
Do you have adb experience?
Be very careful using "dd" command...
1. Boot into CWM Recovery
2. Restore broken backup (don't reboot!)
2.5. Forgot--go to "Mounts and Storage" and mount /data
3. While still in recovery, enter an adb shell
4. In shell, enter "dd if=/data/data/com.android.providers.contacts/databases/contacts.db of=/sdcard/contacts.db"
5. Exit shell (stay in recovery) -- don't know if exiting shell is absolutely necessary, but might as well
6. While still in recovery, flash Bionix from .zip file
7. Before exiting recovery, once again enter adb shell
8. In shell, enter "dd if=/sdcard/contacts.db of=/data/data/com.android.providers.contacts/databases/contacts.db"
9. Reboot and pray lol
Above all else, try this at your own risk...no idea if it will work.
Source: http://hackervisions.org/?p=640
Also, I have no idea why the backup/restore doesn't work. Sorry.
Awesome. Thank You Sir
I have no problem trying this. Just one question
Am i risking a brick with this? i know rooting/unlocking i am at risk. but what is the dd command. by the looks of it, its copying the contacts file ??
Don't think so...but no guarantees lol. You always have the option to wipe /data in recovery, so I don't think potentially messing with one file would result in a brick. Just be sure to triple check the dd command when you enter it.
Will do
Ill let you know. brb
Any luck?
nope
~ # dd if=/data/data/com.android.providers.contacts/databases/contacts.db of=/sd
card/contacts.db
dd if=/data/data/com.android.providers.contacts/databases/contacts.db of=/sd
card/contacts.db
dd: can't open '/data/data/com.android.providers.contacts/databases/contacts.db'
: No such file or directory
~ #
Ok, think I have a possible fix...give me a sec.
thanks for sticking with me through this
im gonna go outside, clear my head.
Thank you Inconceeeivable
Hmmm, yeah that's the wrong contact file...not sure where it would be on your device.
Try this: (be sure to note the extra mount commands)
1. Boot into CWM Recovery
2. Restore broken backup (don't reboot!)
3. While still in recovery, enter an adb shell. Type "mount /dev/block/stl10 /dbdata"
4. Still in shell, enter "dd if=/dbdata/databases/com.android.providers.contacts/contacts2.db of=/sdcard/contacts.db"
5. Exit shell
6. Flash Bionix while still in recovery
7. Reboot Bionix -- let sit for a couple minutes
8. Reboot back into CWM Recovery
9. Enter adb shell, again type "mount /dev/block/stl10 /dbdata"
10.In shell, enter "dd if=/sdcard/contacts.db of=/dbdata/databases/com.android.providers.contacts/contacts2.db"
11. Reboot and pray
EDIT: If step 3 throws an error about /dbdata not existing, replace steps 3 and 4 with the following commands:
"mount /dev/block/stl10 /datadata"
"dd if=/datadata/databases/com.android.providers.contacts/contacts2.db of=/sdcard/contacts.db"
NOTE: If you've upgraded to Bionix-V, Steps 9 and 10 do not change. Still do:
9. Enter adb shell, again type "mount /dev/block/stl10 /dbdata"
10. In shell, enter "dd if=/sdcard/contacts.db of=/dbdata/databases/com.android.providers.contacts/contacts2.db"
I Love You, I Love You, I Love You
You have saved me from so much grief from the girlfriend. I just might get laid tonight!!!
Where do i donate, or ill buy you a beer.....ummm (six pack) if your close, lol
Wow, that worked? Awesome. Don't worry about it, man. Gave me something to do with my free time. Not to mention the fact that the credit for the entire concept goes to the blog linked in the first reply lol.
Not sure if it matters, but you might want to add those contacts to the Google account (I've never moved contacts from the phone to Google...is this possible?) and then rewipe the phone (after confirming the sync of course ). I don't think using "dd" on the contacts2.db would result in any strange behavior (file permissions issue maybe?), but you could be absolutely certain by backing up the contacts, wiping, and resyncing. Again, not sure it if matters though. Either way, glad you got it figured out.
Edit: Wow, I know nothing about how contacts actually work lol. In any case, you may want to somehow (even manually) transfer them to Google and then rewipe the phone.
Yes i thought of the same thing, i hope the contacts can be resaved as google, and not sim or phone !
I know i have this problem with my dads windows 7 phone. Lame.
But im sure google makes it work.
Thanks again man.
I apologize if this has been covered in another thread but I have been doing multiple searches on XDA and in google trying to find a solution but so far no luck. Long time reader of XDA but first time poster.
Details -
I successfully used NVFLASH, loaded Clockworkmod 0.8 and loaded Vega-Ntab gingerbread edition (stable RC1 I believe its called). I have been running this for a month or so with no major issues but I want to test out Vega-Ntab 5.1 and Brilliant Corners. Thinking of going with 5.1 for the hardware acceleration for gaming etc. Oh I also received my new Gtab with bootloader 1.2 and I downgraded that to 1.1 successfully before loading Vega-Ntab gingerbread. I think I can handle loading the new roms etc (may have to switch to 1.2 for Brilliant Corners I believe) but I want to do a full backup before doing so with clockworkmod so I can go back to gingerbread if I decide I liked it the best. But clockworkmod will not do a backup for me. I have tried multiple times and it always freezes/hangs at the same point. On the screen I see
ClockworkMod Recovery v2.5.1.1-bekit-0.8
SD card space free: 9697MB
Backing up boot...
Backing up recovery...
Backing up system... and here it will go no further
I have let it set at that point for hours but nothing changes. I checked the clockworkmod backup folder and it has a folder dated the current date of the backup but the contents is only boot.img and recovery.img and nothing else so I think that confirms it really isnt completing the backup.
I am unsure what the cause or solution to this is. I thought about reloading clockworkmod 0.8 but I don't think I can do this since it's already loaded. I thought about loading a newer version but from what I have read gingerbread and the other 1.1 roms will not work with anything but 0.8. I could just do a melt and repour and just go back to stock level and load 5.1 or Brilliant Corners but then I lose any apps I have loaded. I am not concerned about the majority of them but I have loaded a couple good ones as of late from Amazon that were the free app of the day and I am unsure whether I can "reload" these at a later date without being forced to pay. I have also paid for a couple games but I am assuming I can reload those without issue. I did back up all of the apps I paid for and amazon games that I loaded that I got for free (normally have to pay) with titanium backup. So assuming I can restore these with titanium backup after loading brilliant corners or vegan 5.1 then I guess the only thing that I lose by not being able to do a full backup/restore with clockwork is that if I want to go back to gingerbread then I have to start from scratch for reloading the rom.
So is the problem I am having running the back up successfully a known issue that I just can't seem to find a discussion thread about?
Thanks in advance for any help or advice.
Boot into ClockworkMod Recovery and get me a dmesg output (kernel messages) using adb. See this post for how.
Attach the dmesg.txt to your next post.
thanks for the reply. Unfortunately I am not having any luck getting the dmesg.txt file for you. I downloaded the iso image for Knoppix 6 but when I boot off the disc it starts processing everything but then it gives an error "the file /mnt-system/knoppix/knoppix is broken. then after about 30 secs it gives the following
/sbin/init: line 76: syntax error near unexpected token '/usr/share/fonts/type1/gsfonts/a010013l.pfb'
/sbin/init: line 76: '/URWGothicL-Book (usr/share/fonts/type1/gsfonts/a010013l.pfb);
I will try and download the iso from a different site and burn another disc.
I also tried a different route and loaded SDK manager to get to ADB by that route. I am running windows 7 if that makes a difference. I am not 100% sure when I am supposed to run the adb command line you listed. Do I have my gtab running clockworkmod and then mount USB so it will show up on my pc? Do I have to try and perform a backup and then run the adb command when it freezes? I don't think I can do that because if I navigate away from the mount USB it automatically unmounts it. Anyway adb doesn't appear to be seeing the gtab anyway. When I run the SDK manager it does not find any android devices. If I run the "adb devices" command it comes back with no devices. So I am not sure what basic thing I am missing to get adb or SDK to recognize the gtab.
I apologize for my lack of knowledge on adb. Your first link says if I have adb already set up to run adb shell dmesg > dmesg.txt while in clockworkmod so I am assuming I do this after mounting USB to get the pc to recognize the gtab.
I will try download and burn another iso image from a different location and see if I can boot off a disc. Assuming this time it is successful do I run the ADB command you listed in the second link while the GTab is mounted to USB and recognized by the pc? Hopefully ADB will see it if I can get this to work.
*update* I downloaded the ISO image from a different location. When I went to the folder it was downloaded to I noticed that the first ISO image I downloaded was only approx 100MB in size instead of 700+ mb. So I am re-burning another disc. Hopefully this will allow me to boot properly.
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt) i tried this using the Shell option but it says command not found. If I choose the File Manager option and navigate to where the adb file is that was in your linked zip file it just prompts me to edit/copy/move/rename or delete the file. I am out of time tonight so I will work on it more tomorrow. The good news though is that when I use File Manager the Gtab is listed so it is at least recognized. Now I just need to figure out how to get the dmesg.txt file you request but making some progress... I think
ashton555 said:
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt)
Click to expand...
Click to collapse
Step by step instructions in this post.
thanks a bunch. Those instructions were easy to follow and made sense. I have never used linux before but alot of it reminded me back of my old unix days (terminal commands that is).
Anyway I think I did everything correct and I am now attaching the txt file.
Thanks again for your help and patience with this Linux newbie let me know if I need to provide any additional information.
ashton555 said:
Anyway I think I did everything correct and I am now attaching the txt file.
Click to expand...
Click to collapse
You did indeed. And I can't see any obvious problems with the NAND-flash device, judging from the kernel messages.
Since you've already tried to take backups using CWM before, that action should've created a log file. This file might be useful. Retrieve it. Inside an xterm window on Linux, run:
Code:
hostpc$ [B]sudo ./adb pull /cache/recovery/log recovery.log[/B]
Attach this "recovery.log" file.
Next, try to read, one by one, the NAND flash partitions that CWM usually backs up. Here's an example run on my gTablet:
Code:
hostpc$ [B]sudo ./adb shell[/B] [I]Get into the shell in CWM[/I]
~ # [B]dump_image boot /dev/null[/B]
~ # [B]dump_image recovery /dev/null[/B]
~ # [B]dump_image system /dev/null[/B]
mtd: read error at 0x029a0000 (I/O error)
mtd: read error at 0x02da0000 (I/O error)
~ # [B]dump_image cache /dev/null[/B]
~ #
Type in only the commands in bold.
As you can see, my "system" partition on the NAND flash has errors (and the kernel also report this when it boots), but, the command will not hang. According to the kernel message that you just supplied, you don't have any errors on your onboard NAND flash, so, theoretically, you shouldn't get any errors at all. But, we'll see if the dump_image command hangs when reading system just like CWM does.
And if the dump_image command does hang somewhere, we can see if formatting just that system partition will get it working again. There is a utility on this board which we could use for doing that, though I've never tried it.
I successfully completed the next two tasks. I am attaching the recovery.log file. Note I had an issue copying the .log file to where I could access it in win7 (for some reason I cant attach a file while in linux). I opened it with a word processor and then saved it to my c drive which messed up the formatting. So I opened it in Word to get the formatting correct and saved it as a txt file so thats why the attached file is recovery.txt. Let me know if it messed it up to where its not useable.
On the second task
~ # dump_image boot /dev/null
this worked fine and quick
~ # dump_image recovery /dev/null
this worked fine and quick
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
ashton555 said:
Let me know if it messed it up to where its not useable.
Click to expand...
Click to collapse
The file is just fine... and I can't see any error messages in it.
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
Click to expand...
Click to collapse
This is normal -- "system" partition is ~200MB.
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
Click to expand...
Click to collapse
This also looks like normal behaviour, but, I'm puzzled that the kernel did not report any bad blocks on this partition. Check if this is a transient error:
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same.
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times.
3. Run the "dump_image cache ..." command again.
4. Attempt another full system backup using CWM.
If step 4 fails, we'll see if the writing of the backup to the sdcard is the problem, because the reading seems to be completing without any hangs as of now.
BTW, the most important partitions are all being read fine. The "cache" partition is not that important -- it can be empty (but not corrupt) each time the system boots and only the initial bootup might go a little slower.
And, if, in the end of all this, you can't use CWM at all, you can still make a full system backup using nvflash and a few Unix commands.
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same
....i did the dump 4 times and it always gave the same I/O location
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times
.... I wiped the cache 4 times successsfully
3. Run the "dump_image cache ..." command again.
.... same I/O error location
4. Attempt another full system backup using CWM
.... still freezing at backing up system
So I guess I need to try and do the backup with NVFlash and unix/linux commands? If you have a link on how to do that I will give it a try or I can search for it and see if there is a discussion thread on it.
Thanks again for your help and trying to resolve this
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself? Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
*update* - well I think I am going to be forced to start over anyway. After wiping the cache a couple times and attempting another backup (froze again at backing up system) I now can't get the gtab to boot completely. It is stuck at the flashing vegan ginger edition screen. It flashes for awhile then the screen goes black then it goes back to the flashing screen again. I know you said it would take longer to boot up the first time after wiping the cache but was doing the flash cycling for over an hour which I assume is too long? I tried wiping the cache again and I also wiped the davlik cache as someone suggested in another thread but it is back to being stuck in the flashing screen loop. Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
ashton555 said:
3. Run the "dump_image cache ..." command again.
.... same I/O error location
Click to expand...
Click to collapse
Looks like a permanent I/O error in the cache partition, then. But, I don't understand why it is "system" which is hanging on backup.
4. Attempt another full system backup using CWM
.... still freezing at backing up system
Click to expand...
Click to collapse
Get me the recovery.log.
So I guess I need to try and do the backup with NVFlash and unix/linux commands?
Click to expand...
Click to collapse
I'll think this over during the weekend. In the mean-time, read through this thread. You can safely take a complete backup of your tablet while I do a bit of experimentation on a clockworkmod-like solution. But, I suspect that you may not be able to backup "cache" using nvflash going by the I/O errors. I have errors on my "system" partition and a nvflash backup fails on it, but CWM doesn't have any problems backing up and restoring.
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself?
Click to expand...
Click to collapse
Probably not. But, see this thread. It shows you how to wipe all the partitions on the NAND flash device. We don't need to format the entire NAND flash. We can see if doing a few repeated formats of the "system" and "cache" partitions gets CWM working again, if you're willing to wipe "system"--you will have to load Vegan-Ginger right after this.
Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
Click to expand...
Click to collapse
I haven't used Titanium backup so I can't say how well it works, but, judging from the reports that other users have made, what you're suggesting should work without any problems. User downloaded applications are stored either on /data or on /mnt/sdcard (for apps moved to SD card). Since your SD cards don't seem to be affected, you can go ahead with Titanium backup.
ashton555 said:
Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
Click to expand...
Click to collapse
Yeah, copy the files in CWM, then just do a "wipe data/factory reset" and see if it boot loop goes away.
But, before you do that, gimme a half-hour and I'll send you commands which you can use to save the files in /data and /sdcard. I just have to compile and test a new version of busybox. The tar command already present in CWM doesn't seem to work properly for me.
Attaching the recovery file
I am running the nvflash back up right now.
It successfully did part-1.img through part-11.img with no errors. The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
I looked on my ext SD card and the titanium backup files are there (except for a couple I had forgotten do ....) so I think I am okay for going back to square one if need be.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions. I am assuming that at this point I guess its okay to go ahead and try to load vegan tab 5.1.1 instead of ginger again since I wanted to try out 5.1.1 anyway or if you have any experience with it would you recommend Brilliant Corners instead since its a newer rom. I think I will have to reload the 1.2 bootloader which is okay.
ashton555 said:
Attaching the recovery file
Click to expand...
Click to collapse
No errors in there.
The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
Click to expand...
Click to collapse
I think so. The cache partition isn't that important anyway, so it can be skipped.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions.
Click to expand...
Click to collapse
I would suggest that you copy the Titanium backed-up apps safely away immediately, then format just the system and cache partitions as per that thread. You will need to be in APX mode to use nvflash.
Immediately after the nvflash, (since the system partition is now gone), boot into CWM, then do a factory reset, repartition the internal sdcard, copy the Vegan-5.1.1 update file onto the now clean sdcard through the PC and then flash it. This should give you a clean slate.
Then check if you can do a backup using CWM. If you still can't, then I'll see if a solution can be devised to do partial backups.
And, I have tried neither Vegan* nor Brilliant Corners, so the choice is up to you.
Sorry, my test commands aren't working so I can't send you those commands I promised to back up your /data and /system--I suspect a bad USB cable.