Everytime I go into BSR and try to flash a rom it says
"Can't chown/mod /system"
(Operation not permitted)
"Failure at line 294"
"set_perm_recursive 0 0 0755 0644"
"System: installation aborted"
What's this mean? Is it fixable or did I screw up my phone totally?
ztotherad said:
Everytime I go into BSR and try to flash a rom it says
"Can't chown/mod /system"
(Operation not permitted)
"Failure at line 294"
"set_perm_recursive 0 0 0755 0644"
"System: installation aborted"
What's this mean? Is it fixable or did I screw up my phone totally?
Click to expand...
Click to collapse
I had the same problem look in the q&a section. I had my original stock 2.3.4 sbf backed up. Found out that the original back up that I have been using for months was the cause. You will need to sbf and then Re root. After you root again make a fresh new back up of stock rom so you have one and then flash your rom of choice. This was my same issue over the last couple of days.
Related
I am running tazz froyo on my droid eris and want to downgrade to 2.1. But i keep getting this error. E: cant chown/mod /system/bin/ip (no such file or directory)
E: failure at line 1016: set_perm 0 3003 06755 system:bin/ip
installation aborted. Please help.
ryan884 said:
I am running tazz froyo on my droid eris and want to downgrade to 2.1. But i keep getting this error. E: cant chown/mod /system/bin/ip (no such file or directory)
E: failure at line 1016: set_perm 0 3003 06755 system:bin/ip
installation aborted. Please help.
Click to expand...
Click to collapse
Maybe you could explain HOW you are trying to downgrade, and whether or not you performed a wipe operation if you are flashing a different ROM.
bftb0 said:
Maybe you could explain HOW you are trying to downgrade, and whether or not you performed a wipe operation if you are flashing a different ROM.
Click to expand...
Click to collapse
I am trying to downgrade via recovery mode. i also tried with rom manger. yes i did perform wipe. And i am running tazz froyo and switching to offacial 2.1
nevermind
nevermind i restored to 1.5
ive rooted my my phone and trying to backup my current rom when i try i just get an error how can i fix it?
Without knowing the error how could one inform you!
ithehappy said:
Without knowing the error how could one inform you!
Click to expand...
Click to collapse
sorry i forgot to add what the error is
E:failed to seek in /cache/update.zip (invalid argument)
E:signature verification failed
Hm, I knew.
Copy the zImage of your rooted kernel to SD card. Then flash it via CWM with the option Flash Kernel. Done.
Regards.
I'm not sure what I'm doing wrong. I keep trying to flash the .zip file but it says it's denied or something like that. I really want to get this ROM working on my Galaxy but I'm not going to flash until I get the recovery saved first. I hope I make sense.
E:failed to seek in /cache/update.zip (invalid argument)
E:signature verification failed
Installation aborted.
ScienceCat said:
E:failed to seek in /cache/update.zip (invalid argument)
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Turn off signature verification in the install zip from sd card menu and try again. It should work once you have done that
Wait, are you trying to use CWM to flash Entropy's CWM release? 'Cause the only release I've seen from him is his Daily Driver release, a version of CWM.
If that IS what you're trying to flash, you need to use Odin or Heimdall.
Extract the zimage file from the .zip. In Heimdall, you'll want to flash that file to the kernel in heimdall, or let Odin flash it wherever it belongs.
when switching through windows inside Recovery or trying to wipe cache i get
E: Can't mount /dev/block/mmcblk0p36
(File exists)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p36
(File exists)
im allways rooted/S-OFF
Recovery is Amon Ra 3.15
Ive tried to reflash the Latest RUU. and itll boot and i can use the stock rom but i usually use custom rom
but flashing the latest RUU didnt solve my problam
I am currently formatting my Internal_Sd and mt Sd card to Fat32 right now
ok im stuck on booting after nandroid restore
someone please help!
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
Also, I've read conflicting info about whether you can restore a nand that was made before updating firmware with an RUU. If any resident experts can comment on this I'd appreciate it as I was going to post a thread asking this.
Did the RUU update yours or was it already running the same firmware?
Also, you were able to boot when on the RUU or no? If yes, you might just flash a ROM fresh rather than restore a nand.
feralicious said:
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
If not, then give a little history on what you had on before your troubles and what you're trying to get back to, etc...
Click to expand...
Click to collapse
i fallowed this http://forum.xda-developers.com/showthread.php?t=1615969&page=3
im not getting the error inside the recovery anymore. im about to try a nandroid restore
Boot was completely successful. everything is fixed
(thread closed)
My Verizon Samsung Galaxy Note II (also known as i605) was Jailbreak by CASUAL yesterday( http://forum.xda-developers.com/showthread.php?t=2118348 ).After I did some wipe at the new TWRP recovery, I sadly found my i605 won't get pass the first screen while booting, and it just stuck there...
Then I tired to restore the stock to I605VRLI3 by Odin, but it still won't pass the first screen...
The saddest thing is when I press vol up+home+power, the TWRP recovery is gone also! It changed back to the original recovery<3e>:crying::crying:,and under a few lines:
-------------------------------------------------------------
E:failed to mount /system (Invalid argument)
can't mount '/system'(Invalid argument)
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Appling Multi-csc...
E:failed to mount /system (Invalid argument)
can't mount '/system'(Invalid argument)
E:failed to mount /data(Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data(Invalid argument)
E:failed to mount /system (Invalid argument)
-------------------------------------------------------------
(Photos attached)
I have tried the VRALJB stock,but Odin is fail whild "NAND Write Start"...it can only pass the I605VRLI3,and failed to boot again...
Can anyone help? I would greatly appreciate...I am so stuck...
Regard!!!
Im thinking you some how damaged your memory. I haven't seen this on an Android device
Yet but back in the day I did this to a good number of razor's. If it won't take a flash at all then
Your memory is probably damaged.
I'm not sure about that because it's still loading the bootloader. You should try to odin it
Back to stock. Try the route 666 root injected stock rom. There is something about that rom
It got me unbroken one time. If it will take that rom then just redo the casual and reinstall your
Twrp. And then put what ever rom you want on it.
If it won't. .. then....
If it was me I would take out the insurance. Then I'd drop it off the roof of my house.
krazzykiller said:
Im thinking you some how damaged your memory. I haven't seen this on an Android device
Yet but back in the day I did this to a good number of razor's. If it won't take a flash at all then
Your memory is probably damaged.
I'm not sure about that because it's still loading the bootloader. You should try to odin it
Back to stock. Try the route 666 root injected stock rom. There is something about that rom
It got me unbroken one time. If it will take that rom then just redo the casual and reinstall your
Twrp. And then put what ever rom you want on it.
If it won't. .. then....
If it was me I would take out the insurance. Then I'd drop it off the roof of my house.
Click to expand...
Click to collapse
Yes insurance fraud always option number 1! Really?
op try two things. First, boot back into recovery and do a factory reset. Second if that didn't work you will need to Odin again and make sure it is successful before proceeding. There is a great guide in development if you need help. I recommend the alternate restore file but full stock would be great to.
The root66 doesn't contain boot loader, recovery, kernel anything so it may not be enough
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Yes insurance fraud always option number 1! Really?
op try two things. First, boot back into recovery and do a factory reset. Second if that didn't work you will need to Odin again and make sure it is successful before proceeding. There is a great guide in development if you need help. I recommend the alternate restore file but full stock would be great to.
The root66 doesn't contain boot loader, recovery, kernel anything so it may not be enough
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I tried the I605VRLI3 stock by odin, it pass,.but it won't help, still fail to boot & stop at the first screen...
I remember one of wipe in the TWRP recovery means fully format the system, include the partition. I think I may made a mistake here...
Is there any ideas about re-partition?
Did you include the sch-i605_16gb.pit file in Odin?
SECTION 1B) At:
http://forum.xda-developers.com/showthread.php?p=1181
Also I used this to preserve bootloader unlocked but if you are that hosed you may need to revert back to the official version then go through root and unlock again using CASUAL.
Sent from my SCH-I605 using Tapatalk 2
samsung sch-i605 wont boot pass verizon logo and when boot into recovery it says
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : unknown
Successfully applied multi-CSC.
E: Failed to mount /data (Invalid argument)
Can't mount '/data' (Invalid argument)
any ideas on how to fix this
E: Failed to mount /data (Invalid argument)
E: Can't mount /data/log/recovery_log.txt
My daughters phone has done the same thing. I have tried everything. I can get Odin to put in the Pit file and stock, but it is completely locked up! I have tried everything.