I'm trying to install ginger clone r2 on my vibrant. I used ODIN to get back to 2.1 then installed rom manager and CWM. I constantly receive an error during installation of the ROM that reads:
formatting data...
copying files...
E:can't chown/mod /data/app
(operation not permitted)
E:failure at line 70
set_perm 1000 1000 0771 DATA:app
Installation aborted
this error happens with any custom ROM that i try to install.
Any help would be greatly appreciated.
I have to ask the most obvious, are you rooted man?
Did you check the MD5 (doubtful this was the cause)
it is rooted. i just tried the su command and it came back with #. how would i check MD5?
Eugene posted an update I think, see if it helps
You can check your MD5 with a program called hashtab, google it
yeah, hashtab is great:
http://beeblebrox.org/
I googled your error and someone said their issue was not being rooted, had to ask.
i finally got ginger clone to install. after i opened up the terminal and check i decided to give flashing ginger clone another shot and it worked. maybe it had to do with super user permissions or something because i changed those to allow the su command to work which i never did before. thanks for the help guys!
Related
I didn't have this problem before but whenever I try to install either of the Bionix roms now, I get this error message:
"Copying files...
E: Can't mount /dev/block/mmcblkop2
(file exists)
E: Can't Mount DATA
E: Failure at line 373:
copy_dir PACKAGE:data DATA:
Installation Aborted
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please Open ROM Manager to report the issue."
Even odder (is that a word?) is the fact that even though it tells me it didn't install your rom, it still somehow boots into a corrupted version of your original bionix rom, i.e. the gps doesn't work and my quadrant score is mediocre at best. Any ideas? I still love your work, I just wanna find out what the heck is going on, lol.
Any help would be greatly appreciated.
-bobofosho123
p.s. The first time installed the original bionix rom, it didn't have ANY problems, go figure.
Why not ask in his thread opposed to randomly here where its not going to get his attention?
It says a file exists too.
I think i've figured it out actually, i just used ODIN to flash back to the leaked updated rom, and then I re-rooted my phone via my pc, and then simply flashed the Bionix 1.2 rom directly through clockwork mod. Thanks for the help though.
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 get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
ramongarza said:
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
Click to expand...
Click to collapse
could you list what rom you were on and what steps you took to flash cm7.1 please?
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
ramongarza said:
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
Click to expand...
Click to collapse
what recovery did you use to flash cm7?
Clockworkmod then later I tried rom manager. Does that answer your question?
Sent from my SCH-I500 using XDA App
follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1212239
i loaded the Rom thank you so much man!
Got CWM installed, and CM7 installed and running. superuser is there, but doesn't show any apps yet.
I installed titanium Backup and ran it, but get this error:
Sorry, I could not acquire root privileges. This application will *not* work! etc etc..
It mentioned verifying that busybox was installed, so I went to the market and downloaded the one by jrummy16, tried to run it, but it errors out - no root access.
Then I tried the one by stephen - same issue.
superuser v3.0.5 (39) is installed. It auto-updated to that immediately after the first full boot on CM7 with the market installed.
EDIT -
I uninstalled the superuser update, but still have the same issue. Downloaded rootchecker from the market, here is the output:
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
ls: /system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location:
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SCH-I500 device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae
Hello everybody, It's so long since I've done this, I've probably made some fundamental error I know, forgive me.
I have changed to Samsung Galaxy II, but I am giving my old Hero to a family member, I had VillainRom 13 and I was trying to flash the Hero back to stock with 2.1-ruu-root-signed, I did a full wipe and then flashed 2.1, half way through the process I get an error:
Code:
Copying files
E:Can't symlink /system/xbin/flashcp
E:Failure at line 94:
symlink ./busybox SYSTEM:xbin/flashcp
Installation aborted.
Any guidance much appreciated
I should add that I am using RA-hero-v1.7.0.1
*Update* I have now re-installed VR13, seemingly OK, still confused about the failure of 2.1 though
Cheers
Paul
Hi,
You can create a gold card and change the rom.zip to heroimg.zip in the sdcard and then the 2.1 stock should install just fine in the hboot mode.
refer to this link:
_http_blog.up-link.ro/how-to-downgrade-your-htc-hero-rom-so-it-can-be-rooted-goldcard-method/
regards,
Kiran
Hey been on these forums forever since i was installing themes on my hp ipac or htc shadow. Not a noob by any meens. Been flashing android since my G1. Now that thats out of the way im trying to flash a ICS leak to mess with the webtop 3.0. I was coming from a stock/rooted .181...
1. I fastbooted to .181 using the droid razr 1.6 utility.
2. then i root using ICS installer Combo.
3. Next i use the ICS installer Combo to install the .79 leak.
4. allowed rom manager and su user permissions. i get an error that it can not mkdir to /sdcardEXT.. is this a normal error? Either way once the phone reboots it starts install but then gets the ! in the triangle and what i assume, fails and reverts back to .181.... What am i doing wrong iv been at it for like 3 hours and im pulling my hair out trying to figure out what im missing. My battery is at 40%, is that an issue? Assuming not since if i can fastboot to .181 i should be able to install .79
Hopefully this makes sense and thanks for taking a look
I had something similar to this happen to me when downgrading-rooting-upgrading my Transformer Prime. It failed the upgrade OTA part because I had modified the build.prop and that kept it from installing the upgrade and I got the ! triangle. Have you changed anything? Frozen any apps? Changed your build.prop from stock?
There is a directory you can look in for the log file of why it failed the upgrade. I think it is under /cache/recovery directory from root. (you have to be rooted to see it and use a root explorer). Open the log file and see why its failing.
Thanx for the quick reply. if memory serves me right i modified the build prop to mess with the s-voice app. so your saying fastbooting wouldnt restore this? if not i guess il have to figure out how i changed it and change it back before trying this install again
Well, I would have thought fastbooting would bring it to total stock, but I had made a change in my build.prop AFTER I had downgraded I believe. I think I would check that directory if you can /cache/recovery for the log file and see whats causing your failure specifically. Again, you'll need a good root explorer (like "Root Explorer") and make sure you have it do root so you can see the sub directories too. I was using ES Explorer and it was not seeing the /cache/recovery directory, just /cache and using Root Explorer showed me the sub folder.
PS> Changing your build.prop back to what it looked like before the change didn't work for me. I had to get a stock, unmodified build.prop form another user on here for it to work.
PPS> Why are you wanting to install the leak? Its pretty much been all but confirmed its happening OTA very soon.
Ok i checked out the build.prop alot of stuff in there but seems to all be correct.
I checked that log file and at the very bottom i get this.
Finding update package...
I:Update location: /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Have no idea what that means tho... If anyone needs the whole log to help me out let me know
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Shinare said:
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Click to expand...
Click to collapse
Yeah hopefully someone can, i mean with the ota around the corner this is not too big of an issue as long as it doesn't effect the official ota. Thanks for taking the time tho.
Well, the only other thing I can think of thats happened in the past is the wrong "region" file for the phone you are trying to update.
Like you are on US_ENG on your phone and you are trying to flash a WW_ENG or something so its not matching up? *shrug* just a blind guess. Hope someone can help you out.
This may or may not help, but I got that error back in the day flashing a ROM on my D2. In clockwork there was a option to disable and enable signature verification.
Or maybe the zip is messed up?
See the thing is i did this all through the guide in the dev section. i would have posted it there but i didnt have enough posts to post there, im more of a reader than a preacher. i only downloaded the 2 files with the 2 different batch scripts. 1 to fastboot to .181 and 1 to install ICS. Il figure it out eventually, but thanks guys. hopefully someone gets me there sooner.
**fixed it, i ended up using the permissions option in rom manager and also made sure the phone was over 50% and it worked so hopefully this helps soeone eles if they stumble across it.