adb push fails - Samsung Galaxy Nexus

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

Related

SOLVED - "Can't falsh zip file"

I just wanted to throw this out there in the event someone else experiences what I did. I searched the forums and didn't find much out there.
I was trying to flash a new ROM with 3.0 kernal. I went through the routine. Backed up current (reloaded 1.1) ROM. Wiped Factory Rest|Cache|Dalvic Cache and System. When I tried to flash the new ROM I received a message E: cannot open zip file. The KF was stuck/frozen in TWRP so I did a hard shutdown and booted back into recovery. Tried to install the zip again and the same message appeared. Rebooted to recovery again and then mounted USB and put on a few other zip's I had. Each returning the same message that the zip couldn't be opened. I knew I couldn't have had bum downloads of all these ROM's. I restored to my Reloaded 1.1 and rebooted into recovery and this time I wiped everything but System. Installed new ROM without error.
I'm not sure what happened here but it appears that it didn't like when I wiped System. Hope this helps anyone who may find themselves in a similar situation.

System is read only?

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

GNEX keep rebooting. Flashed with stock rom but still use old rom.

Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
I have same problem. When i turn on my phone there is a google screen and then "X" screen. After 30 seconds it reboots again and again. I tried everything that i found on xda forum. Pls help !
ariffisariff said:
Hi,
My GNEX is keep rebooting. I tried flash with stock rom or other custom rom and it is said in the CWM recovery that I have successfully flashed but then when reboot, it keeps using old rom. I already check the emmc block and i fsck some block which got problem and it is success. But then, after reboot, it still using old rom.
Behavior:
1) Keep rebooting to old rom although already flashed with stock rom, delete dalvik cache and so on.
2) When in adb shell, i tried push some custom rom in the /sdcard in my GNEX, it is transferred successfully. But when I reboot, the file i transferred gone and left old file. I already do rm -rf to /sdcard and check the /sdcard is empty. But when reboot, /sdcard is back to having old file.
3) My behavior is becoming stress with the issue.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
DR3W5K1 said:
This is the behavior that happens when your emmc dies. It gets stuck in a read only mode.
I'm sorry to inform you that nothing will fix it. It is DEAD!
If you check the forums you will find dozens of threads exactly like yours.
Even though flash storage lasts a lot longer than mechanical storage. It is not immortal.
Click to expand...
Click to collapse
Erk.... No wonder sometimes when in fastboot mode, when flashing the userdata.img, it will failed with "Read Only Mode" error.
:crying::crying::crying:
But, thanks bro for your information.

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Trouble installing stock ROM due to multiple '0' folders !HELP!

I am having a lot of trouble restoring my GSM Galaxy Nexus to it's former glory. I installed CM12 and CWM recovery earlier but CM12 suddenly stopped working. My phone started rebooting over and over so I decided it was to time to flash the stock ROM.
I flashed the stock ROM with WugFresh's root toolkit. And it worked fine besides the fact that writing the system.img took 30 mins, which is very unusual. I rebooted my device and CM12 showed up again... ?!. I tried flashing it by hand with ADB but no luck either. CM12 was still there.
I've been busy 3 days now and suddenly realized that CM12 created new root folders after a factory reset which I did multiple times. So for example, my sdcard contains one root with a folder, named 0, that contains the files on my phone before the factory reset. The problem is that this folders contains the system and CM12 ROM too. So I have like four 0 folders, and the 'deepest' one contains the system and ROM.
Assuming that if you flash a stock ROM, it will install in the root of my SD-card, but doesn't boot because it didn't overwrite the CM12 ROM in the deepest '0' directory [​IMG]. If only CM12 was working, I could manualy delete all the unnecessary 0 folders... I really have no idea how to continue from now on and I really need your help [​IMG]
Edit: I tried: adb shell rm -r /sdcard/0 and it is gone but if I reboot Recovery and look into my folders everything is there again...
epilogue:
Maybe the fact that system.img took 30 minutes to write has something to do with all those 0 folders [​IMG]
I tried flashing multiple recovery's to my device but they only show up if I open them via ADB. Otherwise CWMR shows up again because that one is actually installed in the 'correct' (read:incorrect) folder.
With Skipsoft roolkit I actually received an error while writing userdata.img. It said: remote: write fail. I thought this was due the multiple installation folders and the toolkit not knowing where to place/flash the ROM.
So I need to remove all the 0 folders and place the OS back in the sdcard's root, or I have to somehow tell android to place the stock ROM in the same directory as CM12, or I need to somehow wipe the complete sdcard so I can install a new recovery and flash the stock ROM... I have no idea how however.
Thanks in advance!

Categories

Resources