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
Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.
Hello,
I am unable to modify the partition table. I tried parted and gdisk. Both seems working, that means I didnt get any error message. For example I deleted a userdata partition via gdisk a tried to write changes to disk, it finished with success but when I reopened the table, there was the old one.
In addition, system, cache, userdata partitions seems to have 0mb and cant be mounted. In gdisk,fdisk when I view the partition table, these partitions have normal size according to the start and end sector.
I use TWRP 3.0.2-0 , I can go ADB - recovery, sideload. To fastboot. But I cant chcange the recovery, or remove TWRP, when I fastboot flash other recovery on boot, nothing change at all and TWRP boot again.
It seems to me that the phone is read only, but on the other hand I can upload files by adb push cmd.
Do u have any idea what to do?
jirikolar said:
Hello,
I am unable to modify the partition table. I tried parted and gdisk. Both seems working, that means I didnt get any error message. For example I deleted a userdata partition via gdisk a tried to write changes to disk, it finished with success but when I reopened the table, there was the old one.
In addition, system, cache, userdata partitions seems to have 0mb and cant be mounted. In gdisk,fdisk when I view the partition table, these partitions have normal size according to the start and end sector.
I use TWRP 3.0.2-0 , I can go ADB - recovery, sideload. To fastboot. But I cant chcange the recovery, or remove TWRP, when I fastboot flash other recovery on boot, nothing change at all and TWRP boot again.
It seems to me that the phone is read only, but on the other hand I can upload files by adb push cmd.
Do u have any idea what to do?
Click to expand...
Click to collapse
hi.. use aparted app "link https://play.google.com/store/apps/details?id=com.sylkat.AParted" ... for me works perfectly and you can choose a lot of type partitions " but you have to reading message in app when saying that you have to unmount sd card "
olibub said:
hi.. use aparted app "link https://play.google.com/store/apps/details?id=com.sylkat.AParted" ... for me works perfectly and you can choose a lot of type partitions " but you have to reading message in app when saying that you have to unmount sd card "
Click to expand...
Click to collapse
Currently I have no ROM installed because I cant mount userdata and system partition. So I cant use your app.
How do I fix this i decrypted it and now this what do I have to do?
Solution
[/IHi! So are you saying it is mandatory to "unencrypt" (hence format int. storage) in order to be able to install this ROM?
not to flash ROM. You can flash it while encrypted. But it will ask you for a password on first boot. And after that you are ****** because you will lose access to the internal storage, rendering the recovery useless at this moment... however you will still have access to the phone via bootloader. After that, the only way to decrypt will be via fastboot command "fastboot format userdata" (in which you lose all your data).
From my understanding, because of this command you may experience issues with your partition. At least I had a problem: my internal storage was "cut" in half on windows when I connected phone and checked and after booting first time finally thinking everything was solved disk info also reported that I had some 30gb used, with about high 20's gbs free. I was like wtf.
However, luckily, after formatting internal storage via fastboot command you gain access back to your storage, as the encryption (which was blocking you) is gone. This way you can format (yes, again) your storage through recovery (format, not wipe). It corrects the partition and your phone is read as having 64gb of storage again.
Bottomline, as I understand, had I been decrypted from the start ( which means, before flashing the DU ROM) I wouldn't have had any problems at all with booting ROM first time after installing it and gapps, because it wouldn't ask me for a password. So I wouldn't have to fastboot command to format storage, and wouldn't have problems with partition requiring a new format (this time through recovery).
tip: don't forget to check my comments in the previous page. And I advise you to unencrypt before flashing this ROM. There are tutorials on youtube and xda developers forum certainly. Maybe even here. Good luck every one. And I sincerely only recommend rooting your phone and flashing custom roms if you get the basics of a few commands at least on fastboot and know how to backup your stuff before in case something goes very wrong and your recovery goes to ****
edit: you can decrypt and not lose your data if you backup, move backup to pc, and then, after decrypting, move everything back to your phone.
*
So I'm trying to wipe with TWRP because my phone was stuck in a boot loop after installing a module with Magisk. I'm getting error:
mkfs.fat process ended with ERROR: 1
Unable to wipe USB Storage
Unable to wipe /usbstorage
When I go to repair USB storage, it shows 0MB but in the restore tab, it shows internal storage 53878MB (64GB variant).
I have some experience with flashing and rooting but this has never happened to me before. Any help would be great. I'm nervous about it being bricked.
thats just space for OTG. no need to worry.
Also do not forget to mount system, vendor etc. If phone didnt boot up.