I recently tried to switch rom's from vanilladroid to evileris 1.1. When doing so i did a ndroid backup and i wiped the data like it says. This is the error message i'm getting
Code:
Installing update...
Formatting system...
Formatting boot...
Copying files...
E: Can't chown/mod /system/bin (No such file or directory)
E: Failure at line 7:
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
Installation aborted
Doesn't it take you back after that to the system restore? I have had that happen to me and after it aborted, it just took me back to restore and I did a nandroid restore...
I tried to restore and it says error while restoring boot image. Also when booting the recovery image it says E: Can't read MISC (No space left on device).
Dumb question, but did you wipe?
that was a good question... now for a stupid question: can you just reflash the original rom? or does that not work?
droidfreak said:
that was a good question... now for a stupid question: can you just reflash the original rom? or does that not work?
Click to expand...
Click to collapse
that would work. If you still have the backup just wipe data and cache and try restore and that should work otherwise, wipe data and cache and flash rom same steps
No I don't have the backup I can't restore the original flash image file either. It's saying FAILED: remote not allowed whenever I flash trying to use fastboot. Does anyone have the update.zip file with the correct android-info.txt and android-product.txt files? It should work if i'm able to get that.
bump i need it fixed.
Related
I tried updating the Axura Rom on my phone from 2272 to 2290 and now I get this:
-- Installing: SDCARD:/Axura2290VE.zip
Finding update package...
Opening update package...
Installing update...
Formatting SYSTEM:...
Formatting CACHE:...
Formatting DATADATA:...
Formatting DATA:...
Deleting files...
Deleting files...
Deleting files...
Copying files...
Copying files...
Copying files...
Copying files...
E:Can't chown/mod /system/xbin
(No such file or directory)
E:Failure at line 78:
set_perm_recursive 0 2000 0755 0755 0755 SYSTEM:xbin
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockwor
kmod/recovery.log. Please open Rom Manager to re
port the issue.
It gets me into a recovery loop and then I have to Odin back to T-mobile stock
I've done 3 other Axura updates before with no problems, but now...
I later tried to recover back to Axura 2272, I did it's job without throwing any errors at me, but then it goes into a recovery loop.
I've been at this for hours trying to google a solution, or search on the forums and I couldn't find anything...
I'm kind of a noob at this flashing stuff, I've only been doing it for about a month and a half. After waiting for a froyo update, I decided T-mobile and Samsung could suck it, and I got my pretty little self on XDA.
Right now I can only get T-mobile Stock Android to work. I don't want to have to crawl back to that blasphemy! I either want my recovery to work or get onto Axura 2290, after that my phone will be working again. Please help!!
Weird, Can you try other roms?
permissions problem...like not having proper superuser/root ????
It could be a bad download. Atleast i dont see any reason for it to fail coming from fresh odin. Try downloading the file again. Odin>root>try newly downloaded file.
iynfynity said:
Weird, Can you try other roms?
Click to expand...
Click to collapse
I'm about to try Bionix
jmcghee1973 said:
permissions problem...like not having proper superuser/root ????
Click to expand...
Click to collapse
Well if you're asking whether or not I rooted, I used the Galaxy S One Click Root by TGA_Gunman, and I made sure to re root after every Odin. Would trying a different rooting method help at all?
Chip05 said:
I'm about to try Bionix
Well if you're asking whether or not I rooted, I used the Galaxy S One Click Root by TGA_Gunman, and I made sure to re root after every Odin. Would trying a different rooting method help at all?
Click to expand...
Click to collapse
I ve never used it....just sayin it looks as if its a root/permissions problem at this string ...set_perm_recursive 0 2000 0755 0755 0755 SYSTEM:xbin
Dunno ..if your going to ODIN back to stock JFD, I would go ahead and wipe davlik cache, etc while I was there and then reinstall root... might be some peices left behind causing a conflict with permissions to system/xbin
Alex9090 said:
It could be a bad download. Atleast i dont see any reason for it to fail coming from fresh odin. Try downloading the file again. Odin>root>try newly downloaded file.
Click to expand...
Click to collapse
I'm flashing 2272 right now, it appears to be working, and it didn't give me that error. So I guess you were right about it being a bad file. But how come my Clockwork recovery (It was an Axura 2272 recovery) wasn't working?
I have no idea to be honest other than bad download file messed up recovery. I am a noob myself.
I installed the update zip to what I THINK is the internal hardrive. I see a folder that says exteranl but not one that says internal hardrive. But when im in recovery system and i click reinstall packages this pops up
E:failed to open /mt/internal_sd/update.zip (such file or directory)
E: signature verification failed
Installation aborted
How can i fix this
Based Moses said:
I installed the update zip to what I THINK is the internal hardrive. I see a folder that says exteranl but not one that says internal hardrive. But when im in recovery system and i click reinstall packages this pops up
E:failed to open /mt/internal_sd/update.zip (such file or directory)
E: signature verification failed
Installation aborted
How can i fix this
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=849028
get the update.zip from there ??
either get rom manager and flash clockwork then go to recovery and reinstall packages twice or get the update.zip from the link above and reinstall packages twice and that'll take you to clockwork recovery
you sound like you have stock froyo - which means you have the 3E stock recovery.
I suggest following my guide (signature - noobs).
EDIT - ha, just realize Kyle already linked to it, thanks man.
hi, running GB 2.3.3 baseband 2.1.71 build #3.0.1g.0.75
Using flash tool I rooted and installed xrecovery........that went easy.
So I decided to ugrade to wolf 6.0. this is where it got ugly.
I follwed the instructions to back up. Then Factory Reset (Full wipe)
Wipe Cache Partition
Wipe Dalvik Cache
no problems.
however I cannot load the zip I get this
I get the message E:Catnt mount /dev/block/macblk0p1(or /dev/block/mmcblk0)
(device or resource busy)
E:cant mount sdcard:wolf_experia_6.0.0szip
Installation aborted
Now when I try to load the back up I get the same answer.
Someone suggested formatting the SD card so i tried that. Still no go.
So I have tried this numerous times and continuously get the same message.
Any ideas? Thank you
i_rock69 said:
hi, running GB 2.3.3 baseband 2.1.71 build #3.0.1g.0.75
Using flash tool I rooted and installed xrecovery........that went easy.
So I decided to ugrade to wolf 6.0. this is where it got ugly.
I follwed the instructions to back up. Then Factory Reset (Full wipe)
Wipe Cache Partition
Wipe Dalvik Cache
no problems.
however I cannot load the zip I get this
I get the message E:Catnt mount /dev/block/macblk0p1(or /dev/block/mmcblk0)
(device or resource busy)
E:cant mount sdcard:wolf_experia_6.0.0szip
Installation aborted
Now when I try to load the back up I get the same answer.
Someone suggested formatting the SD card so i tried that. Still no go.
So I have tried this numerous times and continuously get the same message.
Any ideas? Thank you
Click to expand...
Click to collapse
so can u use ur phone and is there any OS installed ?? if yes then jus see whether ur USB debugging is on then try turning it off detach ur usb from phone and try goin into xrecovery and flashing the ROM again !!
Hi, the phone works fine, I tried the above and the same results unfortunately.
Hi
Same, exactly same problem here, when trying to install custom rom (Wolf's) from xrecovery.
cant mount sdcard:wolf_experia_6.0.0s.zip
Installation aborted
I read something with xrecovery 0.3 gb but I have it.
Any solutions?
P.S.
After failing istalling custom rom from xrecovery, I can not boot any more to xrecovery. I had to run SEUS to install stock rom from start.
dsencar said:
Hi
Same, exactly same problem here, when trying to install custom rom (Wolf's) from xrecovery.
cant mount sdcard:wolf_experia_6.0.0s.zip
Installation aborted
I read something with xrecovery 0.3 gb but I have it.
Any solutions?
P.S.
After failing istalling custom rom from xrecovery, I can not boot any more to xrecovery. I had to run SEUS to install stock rom from start.
Click to expand...
Click to collapse
You guys can go to zdizhu's page for the latest xRecovery gb fix, and just use root explorer to copy the files in that zip to the corresponding directories.
Do you mean, manualy copy 4 files from xRecovery-0.3_GBradley.zip to bin and sbin directories, overwriting old ones?
chargemon 1kb
charger 36kb to system/bin
and
sh 402kb
xrecovery.tar 1288kb to system/xbin
dsencar said:
Do you mean, manualy copy 4 files from xRecovery-0.3_GBradley.zip to bin and sbin directories, overwriting old ones?
chargemon 1kb
charger 36kb to system/bin
and
sh 402kb
xrecovery.tar 1288kb to system/xbin
Click to expand...
Click to collapse
Yes
Sent from my X10i using XDA App
While trying to restore an old backup of stock 2.3.6 on my Atrix 4g (ATT) from Jokersax CM9, I recieved an error while restoring "/system". This is what showed up:
Rom Manager version 5.0.0.7
August 22, 2012
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM Manager to report the issue.
A bit of background...So, I rooted and unlocked the bootloader of my Atrix 4g about two weeks ago, and everything went fine. I then decided to flash Jokersax CM9 on my Atrix, so I backed up the stock 2.3.6 that I was on at that time. I then used CM9 for the next two weeks, but then decided I wanted to go back to stock, and I received the error. Btw, I used ROM Manager for backups and restore, and had flashed CWM recovery properly. Also, the backups I had created of CM9 earlier wouldn't restore because of the missing MD5 file.
I was curious why it wouldn't restore properly. Is it just a bad backup or is something wrong with my internal sd card? Anyway, what should I do if I want to restore the backup?
Thanks in Advance!
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
No file
ravilov said:
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
Click to expand...
Click to collapse
Actually if I go into /sdcard/clockworkmod, I can't find the recovery.log file. It might have been moved but I don't recall ever messing with the files.
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Md5sum mismatch
stevendeb25 said:
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
If it was Md5sum mismatch, how would I fix it?
Actually I didn't rename the backup and it has no spaces, so I don't know what it would be...
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
I'll definitely try that, I'm not gonna have a chance to do it soon though. I'll get back to you as soon as I do.
Thanks for all the answers anyway!
Did this work? I have had a similar issue with my Atrix, too. I can do an "Advanced Restore" and restore all partitions but /system.
Issue restoring stock rom backup
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.11 (14-Mar-2010)
Setting current mount count to 1
e2fsck 1.41.11 (14-Mar-2010)
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/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20632/327680 blocks
deleted
nvmm_sorensondec.axf
deleted
Protips.apk
deleted
CarDock.odex
deleted
GoogleServicesFramework.odex
deleted
Glam_alert.ogg
deleted
libopencore_player.so
deleted
tar: write error: No space left on device
defaults.xml
deleted
Error while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Atrix4g", "boot", "system", "data", "cache", "sd-ext")
in2slack said:
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Click to expand...
Click to collapse
in2slack, did you try these steps from ravilov? If so, did you get an error?
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
Were you able to find a solution? I'm facing the exact same issue
Same here I installed the AtrICS ROM for a play around after backing up my MIUI ROM. Decided to go back to the MIUI ROM and I get the error when trying to restore. I've got a load of application data that I've lost if I can't get this ROM restored. It seems that the AtrICS ROM, as good as it is, has changed something.
Any thoughts anyone? It seems to be a file system thing? As if the System partion is the wrong type, or not large enough?
I went back from atrICS to epinter by backup today. I had no problems what so ever so it is not an atrICS related issue, my steps were:
1. format /cache
2. format /data
3. format /system
4. format /dalvik-cache
5. recover epinter
have you tried to use format system before recovery? maybe there is some residual file that can't be overwritten...
Thanks for your reply.
I did try formatting System before restoring and still got the same error when restoring.
However, I ignored it and rebooted and I was back at MIUI and able to recover my files
I've the exact same problem.
In the /cache/recovery/last_log, I've found a message:
write error: No space left on device
Click to expand...
Click to collapse
I don't understand why there is no space left on /system... the size of partitions should not change, isn't it?
After checking /system partition size and system backup, I saw that the backup completely fills the partition:
[email protected]:/ # df
Filesystem Size Used Free Blksize
[...]
/system 309M 309M 3K 1024
[...]
Click to expand...
Click to collapse
I faced the same issue
I faced the same issue and would request experienced users to take a look at my log file and advise me
Okay did anyone try anything of this I faces same problem and idk what to do.
Solved - Non conventional method
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Sorry to ressurect the topic, but I can't restore even /system and /data.. gives me error, and MD5 is fine.
Backing up .android_secure...
.
com.trust5.odp-1.asec
com.quoord.tapatalkxda.activity-1.a
com.loudtalks-1.asec
com.whatsapp.wallpaper-1.asec
com.music.download-1.asec
com.facebook.orca-1.asec
me.pou.app-2.asec
com.kiloo.subwaysurf-2.asec
com.davidamado.MetalGearOuterHeaven
Backing up cache...
.
lost+found
dalvik-cache
recovery
last_log
log
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
chmod: /sdcard/clockworkmod/blobs/02c/§☻‼/♀~|♫: No such file or directory
chmod: /sdcard/clockworkmod/blobs/235/∟/☺>☼>♣~: No such file or directory
Backup complete!
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
system.ext4.dup: OK
.android_secure.vfat.dup: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-06-30.03.16.22//data.ex
t4.dup
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Unable to copy file ./backup/processed
data
user
0
idd
etc
bluetooth_bdaddr
wlan_macaddr
light_themes
GNB_DEBUG.txt
backup
processed
Error while restoring /data!
Click to expand...
Click to collapse
Can someone answer that? Thank you!!
I have the same issue
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Can you please post a tutorial? I am experiencing the same issue.
Edit : I've searched the whole internet and some say that i can't restore the system because my cwm backup of the stock system is to large (315 MB to be precise) while the system partition has 320 MB.It look like i need to have more free space, like 10-15MB .Any ideas on how i might to that?
My Atrix 4g has the boot loader unlocked, rooted, is currently running nottachtrix 1.3 with faux 1.3 kernal.
Before flashing nottachtrix I used Clockworkmod Rom Manager to back up the stock rom.
I tried to restore to the stock rom from the app and it failed, the error was "couldn't open directory. no files found" but by this point it had already removed the existing rom. I installed nottachtrix again with out wiping anything and managed to get the phone back working again as before.
I can't restore any of my backups, even new backups made don't work. The error I'm getting is:
"clockworkMod recovery v5.0.2.0
couldn't open directory.
no files found"
The files are still there in the folder /sdcard /clockworkmod/backup the new backups made are also saved to that folder.
From the report.log:
ui_print("ROM Manager Version 5.0.3.1");
ui_print("13 December 2012");
assert(restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.0.3.1
13 December 2012
Checking MD5 sums...
boot.img: OK
cache.ext3.tar: OK
data.ext3.tar: OK
recovery.img: OK
system.ext3.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/Stock_backup/system.ext3.tar
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
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/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20633/327680 blocks
loads of random code then.
write error: No space left on device
libaudioflinger.solibstlport.solibui.solibbluetooth.solibsensortest.solibz.solibnvomxilclient.solibstagefright.solibpanorama_jni.solibnvmm_video.solibopencore_mp4local.solibmedia_jni.solibhwmediarecorder.solibctest.solibCamera_gingerbread.solibjni_nwp.solibext2_profile.solibrs_jni.solibsurfaceflinger.solibflashplayer.solibysshared.solibstagefright_froyo.solibstagefright_honeycomb.solibaudio.solibjni_latinime.solibphotoflow.solibnvddk_aes_user.solibdlnasysjni.solibSR_AudioIn.solibpppd_plugin.solibgui.solibnvodm_imager.solibwebcore.solibreverbwrapper.solibbundlewrapper.solibvisualizer.solibsrec_jni.solibcrypto.solibnvrm_channel.solibRS.soError while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext")
It says "No space left on device" does that mean on the SD Card or the internal storage? There is 1.02 gb available on the internal storage and 3.35 gb on the sdcard how much is required?
Any help would be very much appreciated!
Jonnym
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
demonoid phenomenom said:
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Jonnym said:
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Click to expand...
Click to collapse
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
demonoid phenomenom said:
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Jonnym said:
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Click to expand...
Click to collapse
Thats not a good idea, you risk a hard brick, or need to rsd flash rom again, im not sure about this but there is an adb way to manually flash each partition regardless of restore being corrupt or not but thats too riskiest
Sent from the gray stuff inside my skull