I tried to clear data/reset to factory and it had a soft brick. Had to restart it using original rom, lost google wallet. Then I got multiview update and after that, I cannot get /system to be in write mode. Its only in read only mode. I tried changing it using adb, tried it using root explorer also but I cannot get it to work. Therefor can't edit build.prop or any files under /system
I been reading all day and can't find a solution to this problem. What am I missing.
I am an idiot, my root was gone. That fixed it.
Related
Well, to my wife's phone anyhow. I had installed CWM recovery and was fixing permissions because I had had a couple of minor issues, but while it was doing its job the battery fell off (duh...) and now I'm getting the infamous error.
I have searched high and low and all I can do -it would seem- is to do a factory reset? Or is there some pearl of wisdom I've missed?
Thanks!
PS Ah yes, forgot to say I've fixed permissions through CWM several times now, problem persists...
Hey... I had this error too..had to factory reset then it was gone
Yeah, that's what I did, too. Somebody should try and make a tool for this issue...
UIDS errors, factory reset and more
I have flashed the 2.3.6 and I started to get some problems of instability with some programs that where crashing, so I reinstalled again the 2.3.6 but I think without removing the roots rights...
From that time I get the famous sentence "Uids .... I'm feeling lucky"
Now most of the programs are not working and crashing, I cannot use the market, I've been trying to factory reset, but I got this error while rebooting after factory reset:
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
E:format_volume: rfs format failed on /dev/block/stl10
E:format_volume: rfs format failed on /dev/block/stl11
data wipe failed
the the phone rebooted, give same sentence "Uids...." and if I try to connect to the pc and try to delete file from the internal SD card it deletes, but when I reboot the mobile the files are always there.
It seems I have not the rights to modify anything on the partition
Anybody has some clue?
I had the same problems and I had to reset the phone to factory settings.
But after that I fixed this I discovered this app Fix Permissions from Stephen (Stericson). I installed this app just in case.
I think it may be fix the problem without CWM or else a factory reset will do.
Larrs said:
I had the same problems and I had to reset the phone to factory settings.
But after that I fixed this I discovered this app Fix Permissions from Stephen (Stericson). I installed this app just in case.
I think it may be fix the problem without CWM or else a factory reset will do.
Click to expand...
Click to collapse
I cannot install anything the market is not working and I cannot copy any file on the internal sdcard.
Exactly I can copy files or even format the partition but when I reboot the device the partition, files, directory are always there like I've done nothing.
Hello lovely android people,
I am a newbie, so im guessing this probably isnt the right place to post this type of question. Please feel free to guide me to the right place.
So the question...
I rooted my galaxy ace2 (gt18160) and install Pimp My Rom app from the market. Did some changes with it and now the phone wont start up, stuck in the bootloop where the logo appears and it does not go anywhere from there.
Ive been researching for solution since yesterday, and found out that I could re-flash the firmware using o2 stock using odin.(although im not quite sure this is a correct solution)
Since there's a possibility of all the data getting deleted, I want to get some files out of the device using ADB pull.
I used adb shell to look for the files I need. At first I could see the sdcard in the root directory / but could not access it without su. After doing su command I can go inside the sdcard directory (where my files are), but it appears to be empty.
ls -l /mnt lists the sdcard with unusual d--------- permission.
Im stuck and dont know how I can grab my files from the sdcard folder.
any suggestion will help.:cyclops:
Thanks
mnt/sdcard is only a symlink to storage/sdcard0 (mount for the internal sdcard) so it does make sense that adb can't cope with that path.
Still, it is impossibibble to delete stuff from either of your sdcards via odin or recovery. Flashing via odin doesn't wipe the data partition either, so as ong as u select the right firmware for our phones, nothing can go wrong really
Thanks for your reply Carpe-Dimi.
after checking /prop.partiitons, it seems that sdcard hasnt been mounted.
The problem now is that there are 18 partitions and I dont know which is the sdcard?
I tried mounting the first mmcblk0. Give me the 'device or resource busy' error.
Excuse my arrogance but I would have liked to find out why I cant access the sdcard or why I cant mount the partitions.
...and thanks again for letting me know that flashing does not wipe the data. :good:
SOLVED!
As Dimi said, flashing does not wipe data partition. But I was able to recover my files in recovery mode as it automatically mounted the mmcblk0p8 partition.
Then installed stock firmware.... tried new jelly bean, then went back to stock as its slow and laggy.
Cheers
i've been breaking my head over this problem for 2 days now, i installed twrp to find out it couldn't make androids because a leftover folder from a deinstalled game prevented it. i tried to remove the folder but failed so i put the phone back to factory settings. now wafter reinstalling everything but the game that prevented it previously it still gives me this error. anyone know how i can get rid of the folder?( see picture)
I cant see how an old folder stops you making backups, it will be an SD card error or a partition error?
You might have to flash back to stock and then bump TWRP again.
As you can read in my op i already tried that also tried rzmoving it with rm -r as su, then i get a I/O error.
How did you restore to stock? The only way to get your desired results is to use cse flash with kdz or use the tot method.
Oh tought it was ok to do it trough pcsuite... Anyway is there a way to solve this trough terminal as well?
Ok so here's an update. I cse flashed a kdz. But the folder is still there, how is thzt even possible?? Any ideas how this can be solved? Could i use twrp to wipe the data partition?
so anyone who knows if i can use tarp to wipe the data partition?
Hi everyone,
I've got a Galaxy Nexus in use since approx. 2 years and update it to the latest CM from time to time. I also flashed Ziyan's beta build (08/06),
but honestly, I dont't think that’s the crux of the matter.
Let me begin with the error pattern:
One day, my Nexus was not in use and only lay on the table, it crashed an rebooted. That happened occasionally, so it seemed like nothing to worry.
Unfortunately the system kept on crashing on every attempt to boot after this or crashed shortly after finishing boot.
This repeated over several hours.
Once in a while, the system managed to stay alive for a few minutes and I was able to browse the settings for example. Doing so, I noticed that it responded normally for about 5 seconds and then froze for 5 seconds alternatingly.
I then tried to flash a backup or rather the latest rom again.
Then it became awkward:
In the beginning I was unable to aquire writing permissions (rw) and only had reading permissions (ro) on my /sdcard. Even adb remount didn't change this.
An attempt to fix permissions in TWRP recovery broke with an error.
I couldn't even access the sideload due to missing write permissions.
Surprisingly, I was able to adb push the rom to /cache partition since I still had rw permissions on /cache and /system and therefore successfully flashed the rom subsequently.
When I checked my permissions again, I regained rw permissions on all partitions.
Trying to reboot my system, it kept on crashing like before, which led me to format the internal memory completely.
According to TWRP the whole memory was deleted completely and I adb pushed an older rom (CM 11) and flashed it.
To my astonishment, I found my phone boot the old rom again, all data was restored and it still crashed like nothing happened to the memory.
I then tried to delete all files manually and flashed the stock rom, even unrooted, all with the same outcome.
After every attempt to change something, Ziyans rom remained on the phone, also the /sdcard data was still there.
What I found noteworthy was the recovery telling me, all the operations completed succesfully everytime and until I restarted the phone, it indeed showed no files remaining after formatting (though, I couldn't change the filesystem).
To put it all in a nutshell:
Memory delete, format or overwrite doesn't work any longer
I am totally out of options and would appreciate suggestions =)
Greetings,
Kosmo$
Yes it is. A way to verify this is to lock the bootloader. If it is unlocked upon rebooting your EMMC is corrupt..
FIX: with adb from computer:
adb shell
su
restorecon -v -R /data/media
possible to fix it from android directly with a terminal emulator. Type:
su
restorecon -v -R /data/media
I'll help if I can
Original post:
The restore worked, but the internal storage is unaccessible (stock samsung rom, tab 8.4)
I can access the files in TWRP though. I tried to "fix permissions" in TWRP, didn't help
Any ideas?
I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..
otyg said:
I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..
Click to expand...
Click to collapse
well, thanks for your answer. back to reinstalling
it's a pain though, I have to re-enter all my accounts, xposed, and all xprivacy settings
CM is good, but I have too many issues with it (wifi bad connection, or it won't come out of sleep mode)
*sigh*
Found the solution, if you have the same problem read the first post