After renaming backup files with rom manager none of those files I can use
to go to that backup up, not using spaces. Anybody has this problem or
I am doing something wrong.
dito33
A little more info on this, backup is starting and restoring but cant boot after is done, at the end says something ext sd cant be found. I am able to install any rom with no problem but not the back up cuz I renamed it.
dito33
Well clockwork names like this "2010-11-19.22.36.00" that's the name of one of my backups... try renaming to that maby... but I'm not sure how rom manager does it. When I had a nexus one I had same problem when renaming nad backups in its rom manager.
Sent from my SPH-D700 using XDA App
I guess my problem is escalating I tried reg back up that just made and wiped and went back to restore and wont restore of the original backup (not renamed).
Why the backup don't work anyone please make suggestion. Is that upgrade zip file root file in sd causes any problem.
To be more clear restore is doing its job until at the end says finished but the very last line sd ext image something can't be found.
dito33
dito33 said:
I guess my problem is escalating I tried reg back up that just made and wiped and went back to restore and wont restore of the original backup (not renamed).
Why the backup don't work anyone please make suggestion. Is that upgrade zip file root file in sd causes any problem.
To be more clear restore is doing its job until at the end says finished but the very last line sd ext image something can't be found.
dito33
Click to expand...
Click to collapse
I'm pretty sure sd ext is for apps to sd, hope this helps.
I get a MD5 mismatch on nandroid restore, how can i fix that?
as far as I know, you can't do anything about it. the MD5 sum is a checksum calculated once your backup finished.... the fact that there is now a mismatch indicates the file(s) are now somehow different. This is a sign of corruption.
This happened to me quite often when I had an evo... I chalked it up to the ultra cheap SD card I was using... I'm hoping this won't be a problem on the NS.
Anyone know whats causing the following issue?
Recently when I download the latest Nightly's (to flash over current Nightly) and boot into recovery and try to flash the ROM, I get the following:
Code:
Installing Update......
E: Error in /sdcard/cm_vision_full-119.zip
(Status 1)
Installation aborted
Before I proceed with trying to flash the ROM I do clear cache and dalvik cache, I always do this. But lately Ive been getting that error when ever I download the file from the phone's browser (whether it be stock, Miren, etc) or even from computer and transfer it to SD card and try to flash. Sometimes when I download from my computer browser and transer to SD card it works the second time (or if I transfer the first file over again) but when I reboot into the ROM, apps are missing and etc. So it corrupted the install.
Things Ive tried with no success
1. Reformatting SD Card
2. Complete Data Wipe (which allows me to flash the Nightly with nothing previously installed) but when I try to flash a new nightly over the installed one same issue
3. Reinstalling Recovery
4. Downloading rom from either WiFi or Tmobile network
5. Going back to G2 Engineering Hboot
Im at the point where I frustrated with my G2 and want to throw it against a wall. The only way Im able to flash new Nightly's is through wiping the device, which gets tedious.
Bump someone has to have some solution.
is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.
pmcqueen said:
is signature verification enabled in CWM? when you go to install zip from sdcard, make sure you toggle signature verification to OFF. not sure if this is what you're encountering, it almost sounds like a bad sd card too.
Click to expand...
Click to collapse
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.
sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?
boost3d23 said:
Signature verification is always off. I did try to turn it on to see if it made a difference, didn't. Ive pretty much tried everything I could think of.
I did have one issue with the SD card (dont know if it is related or not), when I was trying to copy a file to my SD under Ubuntu, it wouldnt let me saying the SD Card is read-only. I went into Windows and it let me transfer the files, so I dont know.
Click to expand...
Click to collapse
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.
martonikaj said:
sounds like it could be SDcard related because its happening whether you download via the phone or computer. Have you tried wiping and formatting the SDcard and trying agian?
Click to expand...
Click to collapse
Tried wiping and reformatting the card many of times. Most of it through Clockworkmod recovery not through the PC though.
pmcqueen said:
do you have another sd card lying around that you can test with? a malfunctioning sdcard can manifest itself in some pretty wonky ways, including something like what you're describing. that would be my next move in troubleshooting.
seems especially likely since you've already tried downloading the rom different ways and whatnot.
do you have eng hboot? you could try fastboot flashing CWM again just to make sure nothing is going wrong there. I would do it manually via PC10IMG or fastboot flash rather than rom manager... I don't really trust the app to do any of its recovery functions "properly" anymore.
Click to expand...
Click to collapse
I do have another SD card that I could test with, haven't done that yet though. Will try it, wasnt sure if it was SD card related.
Yes I do have eng hboot; I flashed the G2 one then the Desire Z one (using the Virtous rom guide) and finally back to the G2 one. Thought that might of been the reason for the issues but turned out to not be.
And I agree I only use ROM Manager to do backups. Anyway I flashed the Clockworkmod 3.1.0.1 (by blahbl4hblah) through recovery and then went back to the one in rom manager. Havent tried installing it through fastboot. Will try that as well.
Ok I can say its not the SD Card or recovery. I flashed recovery again through fastboot and used a different SD Card. Still throws that error. I made sure to only copy my media to the SD Card and nothing from the previous one to make sure it wasnt some file on there that was causing the issue.
Edit: And here is the worst part. After the install fails and I reboot Im stuck at the HTC logo, so Im forced to wipe and reinstall.
Bump for a possible solution.
Another note. The same file I downloaded (didn't redownload) that throws that error when I try to flash it over a old Nightly, works when I wipe data/factory reset.
Ex. I downloaded Nightly 140 and try to flash it over Nightly 139, it throws that error. Now I wipe data/factory reset and flash that same Nightly 140 (didnt redownload) and flash it, it works.
What the heck is going on. I unrooted and re-rooted my G2 and still have this issue.
Bump still having this issue.
This is the CWM Recovery Error Log
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
52624 inodes, 209715 blocks
10485 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
26 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/52624 files (0.0% non-contiguous), 10771/209715 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Installing: /sdcard/cm_vision_full-145.zip
Finding update package...
I:Update location: /sdcard/cm_vision_full-145.zip
Opening update package...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 435943936
Block size: 4096
Blocks per group: 32768
Inodes per group: 6652
Inode size: 256
Journal blocks: 1663
Label:
Blocks: 106431
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/26608 inodes and 3437/106431 blocks
error: file_write: write: I/O error
E:Error in /sdcard/cm_vision_full-145.zip
(Status 1)
Installation aborted.
Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Have you checked md5 sum of downloads?
Sounds like either card corruption or filesystem corruption.
Tried doing any kind of chkdisk or equivalent on the card?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yeah the MD5 sum of the downloads are okay.
Havent run a chkdisk of the SD card. Will do that. Ive reformatted the SD card and tried a different SD card and still have the same issue.
How do I know if it is a filesystem corruption and anyway to fix that?
Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Hmmm. Have you had any issues with connecting the phone and using as a usb drive? Maybe try copying a large (>250mb) file to the SD from your computer, and then copying back from phone to pc.
The read-only error you mentioned earlier is I think going to be the root cause, somehow. I'm not familiar offhand how the microSD can set RO or RW, but on the normal SD it's a switch.
Maybe something in the microSD card slot is causing errors?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Ran a chkdsk on the SD Card and no issues were found.
No problems connecting the phone to PC and using the usb drive. I tested transfering a 367MB file back and forth and it worked perfectly.
The interesting thing is Im not able to flash the Nightly ()without completely wiping) but Im able to use the same flashing method and flash a kernel perfectly without getting this error.
No clue what in the SD Card slot could cause the issue. The card is seated properly and locked into place.
Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App
Mnementh666 said:
Well... unfortunately, that taps out all my knowledge. Wish I could help more.
My thought on the card slot was just something (dust? Debris?) that got in there and is causing random intermittent r/w errors on the card. Basically like corrupting the file.
Do you download the nightly file through rom manager? Load the zip through same?
If yes... maybe download on pc, transfer to card, boot recovery, install directly.
You've probably tried that, and if so I apologize. I'm @ work and can't read the site, and replying and reading simultaneously isn't possible on tapatalk and I'm grasping at straws :-D
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Nope there was no issue with SD card slot that I could see with the naked eye.
Honestly dont use ROM Manager at all. I either download from the phones browser (stock or Miren) or through my PC and transfer it to the SD; both resulting in the issue.
Here's what I think it is, I think its a issue with the phone's partition/filesystem. The result of switching to the Desire Z Eng Hboot. But Ive went back to the G2 Eng Hboot and stock Hboot, many times. So Im not sure.
Anyway thanks for attempting to help. You gave me some additional stuff to look into.
ive been reading/looking on how to install CWM
Just saw this one on youtube
but havent tried it yet
i dont know if the firmware version matter or not..
any testers??
http://www.youtube.com/watch?v=Gb3V7Oemurg
easy steps right?
I used the same method to install cwm on my phone. It works
Sent from my LT15i using XDA App
just backup my stock rom.
it was running and..
NO sd-ext found, skipping backup of sd-ext
generating md5 sum...
backup complete!
whats the meaning of no sd-extension found?
elnitrox said:
just backup my stock rom.
it was running and..
NO sd-ext found, skipping backup of sd-ext
generating md5 sum...
backup complete!
whats the meaning of no sd-extension found?
Click to expand...
Click to collapse
Not sure about that. Guess , if we use link2sd or other programs to move some programs to sd card , the cwm backsup data relating to those programs else it shows the above message , not sure though .
elnitrox said:
whats the meaning of no sd-extension found?
Click to expand...
Click to collapse
Because CWM is prepared to make full backup phone. Including SD-EXT partition if you had ...
But you do not have, it simply does not backup that part and continuous.
But the backup is OK.
I’m getting “CreateTarFork() process ended with ERROR: 255 Backup Failed” on my BTV-W09 using the greatslon TWRP US version while doing a backup. I’ve tried internal storage and external SD card. Haven’t tried an external USB drive yet though. Flashing SuperSU worked fine with this TWRP, I did get the error about the 3rd modem but this may be because this is a Wi-Fi only device? I’m going to try it again and then try pulling the recovery.log to see if this gives some indication of the failure. Is anyone else receiving this error?
I received this error last night in my data section as I was creating a nandroid backup in my preparation to install the xposed framework. I was backing up to the external SD card and what fixed it for me was to delete the existing TWRP directory and make sure compression was not checked. After that the backup completed successfully. I did receive the 3rd modem error, but like you, I believe that is due to not having a cellular modem (WiFi only). I also received an "unable to unmount system" error at the very end, but I don't think that is any cause for concern.
Thanks for the feedback johe. I checked the recovery logs and the backup was failing on different files each time on the data partition. So I added a larger SD Card and the backups work now. So turns out it was just a space issue. The backups take a lot more space than what I thought originally, presumably for caching.