I was messing around and disabled voodoo lagfix and wiped bat stats, when it was rebooting I heard the voice say something about re-partitioning and the phone dropped and when I but the battery back in it is stuck at loading screen. I tried to enable voodoo again but it wont work. Didn't find anything on my sd card and when I try to wipe and re-install a rom, I get
E:Can't chown/mod /system/
(operation not permitted)
E:Failure at line 74:
set_perm_recursive 0 0 0755 0644 SYSTEM:
Installation aborted
I can't get it to load. I have never had anything like this happen. Plz help
Something similar happened to me like this. I ended having to odin using eugene's no-brick froyo method.
First of all this is for DEVELOPMENT.
Your QUESTION should have been posted in Q&A or even in GENERAL.
Second, just use ODIN to flash the stock firmware, re-root, reflash Clockwork Recovery then flash your ROM or restore your previous backup.
Sorry... Thanks
I got it working... I had to mount the phone and find the voodoo file and delete it. Then I was able to restore everything back. A few hours of stress...lol Live and learn.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
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.
THIS IS FOR VERIZON SAMSUNG FASCINATE USERS ONLY!
This should not normally be needed...but in my case it was. YOU WILL LOSE ALL DATA. THIS IS NOT A TRIVIAL PROCESS.
If you need to remove Voodoo4, for whatever reason (mine was not booting), this is how you do it:
1. Download original.mbr from here:
http://adrynalyne.us/files/kernels/sgs/original.mbr (right click save as....)
2. Download stock kernel:
http://adrynalyne.us/files/kernels/sgs/stock.zip
2. Boot to cwm (battery pull, and hold up volume while putting it back in and connected to usb), and put original.mbr and stock.zip on your sdcard. Mount as mass storage or adb push them to sdcard.
3. Use adb to restore the mbr:
Code:
cat /sdcard/original.mbr > /dev/block/mmcblk0
4. Use cwm to restore the stock.zip (kernel).
5. Mount dbdata and nuke the contents.
Code:
mkdir /dbdata
Code:
mount -t rfs -o nosuid,nodev,check=no /dev/block/stl10 /dbdata
Code:
rm -f /dbdata/*.*
6. Reboot back to stock recovery.
Wipe data.
7. Apply CWM. Wipe data.
8. Reboot.
Done and done. Nandroid restore back after this, if you wish.
If this doesn't work, take the illogical steps of:
Flash system, kernel and PIT with Odin. Remember, only use pda and pit sections.
Wipe again.
Automatic uninstaller
I am adding the uninstaller again, but it is not perfect.
To use the uninstaller, DO NOT USE ROM MANAGER!
1. Boot clockwork, and apply the uninstaller.
2. Go to the advanced menu and choose reboot recovery.
3. Wipe data from stock recovery. Apply CWM. Wipe data from clockwork.
4. Reboot phone.
Voodoo Uninstaller DI01 ONLY
DJ05/Voodoo5 Instructions
1. Disable voodoo either by adding a disable_lagfix text file or folder to /sdcard/voodoo directory, or by using the RED clockwork recovery for voodoo and going to the voodoo menu. Remember , you can only boot to it via:
adb reboot recovery
quickboot
manually (hold volume+/- and power)
framework modification.
Rom Manager cannot boot it.
2. Once disabled, flash a nonvoodoo kernel.
If red clockworkmod remains, please flash this, then reflash your nonvoodoo kernel of choice.
http://dl.dropbox.com/u/8642620/voodoo5/1129_test_novoodoo_fascinate.zip
Thanks jt1134 for kernel, and pii for bringing the issue to my attention.
http://adrynalyne.us/files/kernels/DI01package3.tar.md5
Flash via PDA in Odin. This will return you COMPLETELY to DI01 stock, bloat and all. You will need to reroot, etc.
IF red clockwork recovery remains, you can Odin this file as well, in PDA.
http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Recovery.tar.md5
thanks for posting this adrynalyne
seems today is don't RTFM day
I thought that was every day
the first link doesnt work
dialect129 said:
the first link doesnt work
Click to expand...
Click to collapse
Right click > Save link as
oh iight thanks ! now i feel better lets get this working hopefully
Gitykins said:
Right click > Save link as
Click to expand...
Click to collapse
Is the wipe necessary?
Can't someone accomplish the same by creating:
/sdcard/Voodoo/disable_lagfix
And then flashing to stock?
Edit:
I guess if someone is restoring a backup, then the wipe is irrelevant.
As the op said, this is for extreme cases. Usually, you should use the disable_lagfix method.
i keep getting a premission denied
adb shell
su
cat /sdcard/original.mbr > /dev/block/mmcblk0
Thanks a million!!!
my phone issnt rooted anymore since i restored it i couldnt get ride of voodoo and it made me have 0 internal storage
so this removes root? can't you just nandroid backup and get root back?
It does *not* remove root.
Update, uninstaller added to first post.
adrynalyne said:
It does *not* remove root.
Update, uninstaller added to first post.
Click to expand...
Click to collapse
Cool beans, thanks adrynalyne!
I tried this method and now after the VZW logo my phone just sits at a black screen with the keys lit up. I can still adb into it, not sure what to try. I've tried reflashing everything using Odin but it didn't help.
automatic or manual method?
Manual method
Go back to stock recovery and do a data wipe.
Then see if it boots.
Careful with that beta auto uninstaller. I lost half of my apps and it's not reading my SD card.
Edit: It finally finished scanning for media, but now my Market downloads are failing, and it took away my Root Explorer. I don't even have the My Files app, so I can't install anything.
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.
Cannot get r/w access with root explorer after install dl30 and using current superuser/root files.
I always had it before, updated all the files, when I go into root explorer it will not change from r/o to r/w. Its upsetting me as it worked before.
easiest fix is to download "Mount /system (rw / ro)" by Beansoft from the market. open it and set it to mount /system as rw on boot, give it root permission, and you're set.
also please remember to post questions (even if they seem development related) in the general section, or in the existing topic for the rom you're using. Thanks.
This didn't work, still cannot get /system to give any type of r/w access. What could be wrong?
Did you have Voodoo installed beforehand?
Don't doublepost!!!
http://forum.xda-developers.com/showthread.php?p=11384883#post11384883
I have the exact same issue. Just talked it over with Adrynalyne.
You are going to have to download an All-In-One Odin Package such as
http://forum.xda-developers.com/showthread.php?t=867648
Then, you're going to have to start over and flash your CWM Recovery from jt
http://forum.xda-developers.com/showthread.php?t=942021
Then you Odin flash the modem of the ROM that you want to install, then you use CWM to flash the ROM that you want to install...
Make sure that you do to not flash using Phone. Use PDA option in Odin.
Apparently, it's a corrupt dbdata partition that is causing it. This can happen occasionally when installing VooDoo... Just another reason to stay away from VooDoo...
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!