System is read only? - Samsung Galaxy Nexus

Hey guys, I'm having a problem with my entire GNex being read-only. I currently can't get the device to boot into Android (after unsuccessfully trying to flash franco's 4.3 kernel to my 4.3 ROM) and am stuck in TWRP 2.6.
There are a couple versions of Paranoid Android on there but when I try to flash one of them, all I get is "Failed" in red font (with no other error message); the only version that I'm able to flash is the most recent 4.3 build, but that doesn't boot past the Google logo.
I've wiped everything multiple times except for Data but that didn't help, and fixing permissions only gives me the "Failed" error again.
I can use adb to pull anything I want from the device, but it refuses to accept any files via the push command, and I get a message saying "failed to copy 'filenamehere.ext' to '/sdcard/filenamehere.ext': Read-only file system".
How do I fix this error? I have adb and fastboot working correctly on Windows 8.

Also, when I try to fix permissions, I get a message in the log that says "E: Unable to chown '/data/app/com.yackovsky.holle" (the name is cut off, but it's the package name for this app: https://play.google.com/store/apps/details?id=com.yackovsky.holler.wht&hl=en , although I doubt the app has anything to do with the problem).
Also tried following the steps from this post http://forum.xda-developers.com/showpost.php?p=22970837&postcount=14 but still got errors about the filesystem being read-only.

Ended up formatting the phone to solve the problem. /thread

Related

adb push fails

Hello there, I've flashed the new Android Revolution 4.3 Rom, and after restoring a TiBu backup, I rebooted.
Since then I'm stuck in recovery, since no Rom will boot, not even the one I had flashed before.
The good news is that I can still get into recovery, the bad news is that I don't seem to be able to do anything from there.
I tried to push the latest 3.96 PA but adb push command fails saying that
Code:
failed to copy 'pa_maguro-3.96-20130813.zip' to '/sdcard/pa_maguro-3.96-20130813.zip': Read-only file system
This has never happened to me before, what can I do?? Any help is very appreciated!
Edit: seems like a full wipe of internal storage fixed everything

[Q] HELP! GPE lollipop OTA Update Error, no apps loading after that

Hello All,
I have GPE version of GPad running Kitkat 4.4 Stock ROM. Last month I have used following link to enable chromecast mirroring. Due to the issues i have uninstalled superuser app and did factory reset. After that all well! I mean no issues with tablet.
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Yesterday I tried to sideload the GPE lollipop update but prompted with following error.
"/system/etc/audio_policy.conf" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
This morning I saw system update notification for Lollipop upgrade and opted to install it, but without any further msg during the system update it prompted with "Error!" After that I did factory reset. When it reboots starts optimizing 48 apps, but it prompts with following sequence of messages:
"Unfortunately sun beam has stopped. "
None of the apps loaded , no access to setting, just empty screen and on screen buttons at the bottom.
I spent quite some time looking around in xda to restore back to factory, none seems to work.
1. Tried flashing original stock .tot file, getting "Download user image is only available in the online environment!!
2. adb sideload, "/system/etc/audio_policy.conf" has unexpected contents
3. To Flash TWRP i am not getting access to setting to enable USB debugging.
Now i cant even put the G Pad in adb as i dont have access to settings to put in USB debug mode. vol down+power puts into bootloader, but cant access to adb commands.
Now I can only access to recovery and do sideload. but i am stuck with "/system/etc/audio_policy.conf" has unexpected contents error. Can someone share kitkat original version of audio_policy.conf? also how i can replace the exiting file as i dont have access to adb?
Greatly appreciate your help to bring back the G Pad.
regards
Raj
You can boot twrp from fastboot and flash either 4.4.4 or 5.0 back onto your tablet. Look at the thread in Android development for more details on flashing the stock images using twrp
Thanks! I was able to get back to kitkat with following method. I was able to flash recovery its now back to complete stock kitkat now.
http://forum.xda-developers.com/lg-...510-gpe-4-4-4-ktu84p-l002-stock-twrp-t2797883
After this I got system update notification to lollipop. Again got "Error!" msg during the install process.
I tried adb side load, got following error!
failed to verify whole-file signature
signature verification failed
installation aborted.
Any thought whats going wrong there?

Mobile Version, Bootloop/Brick, Nandroid FAIL, Factory Flash FAIL, PLEASE HELP!!

HISTORY/CAUSE
Hi, so i was trying to manually install xposed (x80,sdk23).
I was confused at first about which version (arm, arm64, x86). I tried installing x86, it kept failing with 255 errors.
i tried arm(which is the correct one), which kept failing with 1 error. I installed it many times, and i think i once saw a not enough memory error. So i downloaded both arm and x86 xposed uninstallers. It still failed. Notice that after all this i was still able to boot up. I went into recovery and made a nandroid backup . Then i tried installing sdk22, and it showed that it was only for android 5.1. I uninstalled again and tried to boot up, but it was stuck in a bootloop. I booted into recovery, and tried to install the nandroid, but it failed with again 255 errors (only the system part)(does 255 errors again seems suspicious to you?). I tried a factory flash, it failed with unkwown command errors and invalid arguments.
CURRENT PROBLEMS
1. At first, the bootloop showed the 4 animated dots, but now it just goes black after the google logo.
2. The NANDROID backup failed, or more specifically the system restore part with 255 errors.
3. The FACTORY IMAGE flash failed, with invalid argument errors in sending things and unknown errors in rebooting into bootloader.
WORKING THINGS
1. Bootloader works
2. Recovery works
3. ADB & FASTBOOT works
4. The computer even recognises it as a device in recovery and gives me access to the data
DEVICE INFO
Device: Nexus 7 (2013) LTE Version, [deb],[razorg]
Android: Marshmallow 6.0.1 (MMB29Q)[Second to latest]
Bootloader: Flo-4.05
Recovery: TWRP 3.0.0-0
Warranty:Currently None
It's a very comprehensive description, thanks. Please do the following:
- boot TWRP
- connect PC
- run: adb shell dmesg > dmesg.txt
- find 'dmesg.txt' file in your adb folder
- attach it here or upload to http://pastebin.com

Soft bricked Nexus7 can't get through "Can't mount" errors

Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.

RN8 file problems

Hello I have a problem with the files on my device and it is that when trying to install a ROM using TWRP I get that it has failed and a lot of messages saying:
"Error opening: ยด/data/user_de/0/" (Here it puts rare names of symbols and letters) operation not permitted
I already tried to mount the data folder from the recovery and I also tried to install the ROM from ADB commands but it is not possible, this is not the first time that I installed a ROM since I had Pixel Experence and when installing it it did not show me any error and now the Device does not start as it has no ROM and when it turns on it opens the TWRP.
someone could help me with that please.
I'm having problems with TWRP and OrangeFox, permission errors all the time
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU). The steps I took to change the ROM: Formated data (errors started right away) then I did the usual wipes (cache, dalvik...
forum.xda-developers.com

Categories

Resources