I'm on the latest AOKP Jelly Bean build. Everything was working perfectly fine until I rebooted by phone after a charge. It gets stuck at the Google screen for about 4 or 5 minutes then just goes black. I can get into Clockworkmod, but it's showing a whole bunch of errors every time I try to do anything "E: Can't open cache/recovery/log, E: Can't mount cache/recovery/log". It also will not mount the SD card.
Please help!!!
I had this problem when I first unlocked the bootloader and rooted. Do a search for returning your phone to stock. You only need to do the last step that flashes the system partition. You will lose your data, but your phone should work.
This is the site I used, step 6 only:
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html?m=1
Sent from my Galaxy Nexus using Tapatalk 2
Use Odin http://db.tt/PVsnbLIM
And flash this https://dl.google.com/dl/android/aosp/mysid-imm76k-factory-98d21321.tgz
If you want to attempt to save ur data boot into recovery and with using adb from a PC run
adb pull data/media.. and see if it works. try to mount /data first but I have a feelin its gone
Recovery Options
If you can get into CWM, what happens if you do a wipe of system, data and dalvik then reboot?
If that fails, your next step is to try and reflash a new ROM image, but that could be tricky if you don't already have a ROM image on the sdcard partition on the phone. I don't know how you can copy a new image over to the phone if you can't boot to Android. If anyone knows how to do that, it would be useful to know...
CMW > mounts and storage > mount /data
adb push NAME OF File.zip /sdcard/
unmount /data
I encrypted the device, then decided I wanted it off. I factory reset the phone to remove it and now It's stuck at the Google screen and won't boot.
I tried going into recovery (TWRP) to restore a previous backup but none of my backups are listed. Looked in the file manager and the SD card was blank. I looked in the Mount menu and sure enough, it was unmounted. I tried mounting it, but nothing happens when I touch it. I can't mount the data or SD Card. I can mount and unmount the system and cache just fine though.
The log for TWRP says "E:failed to mount /data (Invalid argument)"
The galaxy nexus toolkit does not recognize the device when using "fastboot devices" or "adb devices" commands.
Anyone have this problem before or know anything that might fix this?
Edit: got it booting again. if anyone's wondering, I used this: http://www.galaxynexusforum.com/for...how-return-stock-using-odin-vzw-lte-only.html
I have a KF1 v6.x (I believe since it was stock). Installed KFU 1.4a. Installed TWRP. Following a post in the [ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1] thread I wiped factory reset then wiped system PRIOR to moving the ROM to the sdcard. Now, there is no OS. I was able to put the ROM.zip on the root of the SD card but when attempting to install it I get "Unable to mount '/data'". I've tried several commands for adb to do partition stuff but didn't get anywhere with that. Not sure if FastBoot is working via KFU due to the following message.
hxxp://imageshack.us/photo/my-images/547/37437819.png/
What's my first step here? I can get into TWRP so hoping this KF isn't totally hosed
Looks like Fastboot is working?
hxxp://imageshack.us/photo/my-images/14/75434412.png/
http://forum.xda-developers.com/showthread.php?t=1949372
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
SUCCESS! :victory: Thanks soupmagnet! Pic of partition table attached showing /data is not mounted. When doing umount cmd received message "can't umount /data: invalid argument" which I guess is good since /data is not mounted in the partition table.
After removing, making, then naming the partion and quitting I received a message: Information: You may need to update /etc/fstab. 2nd pic shows /data correctly mounted.
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
AnotherBrickedDroid said:
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
Click to expand...
Click to collapse
1) It's hard to say really. For the sdcard, I always assumed it was from not "ejecting" it before unmounting, but I think that would be kind of hard to recreate with the data partition. If I were to speculate at this point, I would say it had to do with how certain versions of TWRP format those partitions, but I'm not sure. In either case it's pretty rare for it to happen.
2) From what I understand, you can't. Recovery is unpacked and run from active memory so any changes you make to fstab will be lost every time you reboot. But the filesystem should still be automatically checked every Nth mount.
3) Three guesses? The first two don't count?
Hello friends, i hope you can help me because i ****ed up real bad today... I was in cwm recovery, and press some button that said something like "format for rom" or something like that... Now i dont have any SO installed, no rom on my phone, and it says i have 0mb avalaible. So i flashed the TWRP recovery because im more familiar with it, i have tried sideload but get this error con the cmd window after it gets to 100% * failed to write data 'protocol fault (no status)' *
On the phone i have: E: No valid storage partitions.
Any help please? Already tried adb push rom.zip /data or /sdcard but since i have 0mb for storage on my phone i think any of that will work. I can flash recoverys, but cant move any rom to my phone to flash Help please
Ok it seems that i was able to push the rom.zip to my /system but when i try to flash it, it says:
E: Unable to mount /data
E: Unable to find storage partition to mount to usb
worms45 said:
Ok it seems that i was able to push the rom.zip to my /system but when i try to flash it, it says:
E: Unable to mount /data
E: Unable to find storage partition to mount to usb
Click to expand...
Click to collapse
What carrier are you on?
How does that matter? The phone was originally at&t. I need to format my storage or my /data or something to be able to install the rom
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
kingsmaug said:
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
Click to expand...
Click to collapse
Do you have twrp?
If so which version?
Sent from my XT907 using Tapatalk
Yes. If I remember correctly, its version 2.6.3.0. It used to have boot loader otterx v2.05, but after some failure with KFU, it has FFF v1.4a.
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
kingsmaug said:
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
Click to expand...
Click to collapse
which partition version is selected OtterX or Amazon?
sd_shadow said:
which partition version is selected OtterX or Amazon?
Click to expand...
Click to collapse
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
kingsmaug said:
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
Click to expand...
Click to collapse
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
sd_shadow said:
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
kingsmaug said:
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
Click to expand...
Click to collapse
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
sd_shadow said:
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Well, following that worked. Everything got cleared up, and now I'm loading into the ROM. Thank you!