Hello Again, I have found a few threads with the same issue but something in the middle is different, this has happened on my Nexus 5 before, and it pissed me off because i never got it resolved.
I want to convert my HTC One M8 ATT to GPE later today, but first i'm on sense with NvROM.
The ROM isn't the issue since it's been working fine for a 2 weeks now, here is the story.
What i did-
Recovery (Wanted to try out CarbonROM)
Flashed LiquidSmooths kernel ontop of Carbon, got "Unfortunately phone has stopped".
Went to recovery again to attempt to flash liquidsmooth only.
E: Unable to mount /data
E: Unable to mount /system
E: Unable to mount /cache
E: Unable to mount /sdcard
E: Wiping /data /system /cache failed!
Now, i rebooted and those errors are non existent i can flash again.
But on LiquidSmooth , The Gallery can not find my Pictures.
The Music app can not find the music anymore.
Whenever i use a File Manager , magically my files are still there.
Anybody got ideas on this one? Thanks.
>Pics related<
Try to connect the phone to a PC, and use Device Manager to format the internal memory. Backup any personal data first, if needed (and if possible).
I've heard that , that causes the eMMc or internal storage to go into Read Only mode?
anyone correct me when i`m totally wrong here.
hasn't this something to do with the so called fused location of your sd-card ?
On my phone the locations of the sdcard is shown different then when i locate them trough recovery or shell.
In android the location is something like: /root/storage/sdcard (internal memory)
the real location in my case was shown in recovery as: /root/storage/emulated/0/
And i think because i had previously installed a cm11 based rom and kernel.
And when i completely wiped my phone for a newly rom, afterwards i still had all my data on my phone, because it didn't wipe the /emulated/0 location.
so all the files are still found with a file manager because the two location i mentioned before are fused. But your apps still has the old location in his settings somewhere..
You can try to do a media rescan so your phone search for new media.... But i believe that is also done when you reboot your phone.
I had that happen to me and I was able to fix it by using the "Format" option in TWRP recovery. That, of course, wipes everything on the device but everything will be mounted correctly and properly again.
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
i4GS said:
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
Click to expand...
Click to collapse
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
sneef said:
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
Click to expand...
Click to collapse
Sorry, but what i did was different, and MIGHT factory reset your internal storage, i can't verify 100%.
You can do two things,
Either flash the RUU
for 4.4.3 STOCK HTC [ATT]
or Flash Google Play edition RUU and revert back to sense which will fix it too.
SENSE: http://forum.xda-developers.com/showthread.php?t=2733523
GPE: http://forum.xda-developers.com/showthread.php?t=2708589
Related
I only loaded a new rom on the incredible successfully once, last summer when the signed 2.2 rom came out early and I couldn't wait for the OTA.
I had this problem crop up that said my storage was full when I had gobs of space left on my internal storage and my sd card. Finally, after I did the factory reset option and still had the storage issue, I decided to try reflashing with a new rom because my phone was becoming unusable. I couldn't install apps, save contacts or even open text messages. My phone wouldn't even sync with Google.
I decided to try flashing with the redemption rom after reading some good things about it.
I managed to load it successfully, but I still had the storage error! argh!
After trying to reformat some things with the ClockworkMod Recovery partition menu, I tried to reload the redemption rom again. Something went wrong.
Now I get messages saying(on the ClockworkMod recovery screen):
_______
E:Can't mount /dev/block/mmcblk0p2
(file exists)
E:Can't mount Cache:recovery/command
E:Can't mount /dev/block/mmcblk0p2
(file exists)
E:Can't mount Cache:recovery/log
E:Can't mount /dev/block/mmcblk0p2
(file exists)
When I choose the option to install the redemption rom off my sd card in the clockworkmod, it fails after giving me similar error messages.
I'm stumped. Can anyone point me towards the right thread to deal with this? I can't boot to install any other software onto my phone. Practically everything I try gives me can't mount error messages.
I was hungry and in a hurry and never made a nandroid backup I HAVE tried reformatting the sd card, but I got no different results from that.
So am I A) totally screwed, B) somewhat screwed, or C) not screwed at all, just an idiot?
Help?
im in the same boat. i have no idea how to fix it. ive tried every fic i can find on google and NOTHING works. someone HALP
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 the site wont let me post a link, but this is what i used. i can now mount data and cache. working on booting now.
Have you tried a different SD card? Your SD card could have failed or become corrupt in some way.
I doubt you are totally messed up. You may need to get a brand new factory ROM (on your new SD Card) and start from there. Just Google it. As for an SD Card, there will be a few on sale Friday.
As for the full memory, I had that same problem, it's a cache issue with the HTC software (HTC Mail, Facebook, Peep and such). Once you get back up and running make sure you root (unrEVOked is working on a work around for the latest mid Nov OTA but there are other ways to root) and get a Cache Cleaner. It's not a permanent fix, but it does work.
Good luck!
Thanks for the response. I have yet to try Barbee's solution, but I did try another SD Card. I reformatted both cards to Fat32 and had the same error message on both. I'm going to go grab my phone and try Barbee's solution next.
it might be that version of CWM recovery is just retarded. what version are you on
I take no credit for this but try this its on Adrynalyne's blog http://adrynalyne.us/
"There have been a few cases where /cache has been corrupting on the DI."
"To fix this, you must be in clockwork recovery.
First, unmount cache from partitions menu.
Then, mount system from the same menu.
adb shell
system/bin/e2fsck -p /dev/block/mmcblk0p2
exit"
That should fix the issue you guys are having.
Thanks Barbee, I was able to unbrick with your solution! Pretty muh all of that was way over my head, but the instructions were clear and they worked. Now I just need to get that Redemption rom to work with the *228 option1 programming on the phone... that doesn't work now lol.
That's easy, go into settings sounds and turn the touch tones to long. This is common in custom roms.
Sent from my ADR6300 using XDA App
what happened was you trashed your internal partitions using cwm partitioner......the method on cyanogen's forum shows how to properly reformat the internal partitions to ext2 and gets you back to having a usable phone.
Glad to hear it helped you. But all the credit goes to the guys in the link post. It was a little over my head too lol. I've used adb before but not for a life or death situation lol
Sent from my ADR6300 using XDA App
I have an Incredible, rooted (and I have issues)... I appear to have repartitioned my internal memory area. Thankfully, the phone is useable, but it's not quite right as some programs don't work properly, the video recorder hangs hard, and I have either corrupt data or areas stomped on by other areas due to incorrect partition information. If certain files get touched, then the phone immediately protects itself by flagging the internal memory as read only. I did find a workaround to the phone automatically going into ReadOnly at boot by simply adding a ".nomedia" file in the root of MP3 (where some corrupt files happen to reside). As long as the system doesn't touch the files, the file system remains R/W.
I stupidly did this to myeself. I did it while using a Partitioning tool (specifically Acronis, making a "secure zone") on my PC while my incredible was charging in the USB port and I accidentally used the wrong drive. It was one of those "oh crap" moments. If I connect the phone to my PC, the internal drive comes up as being unformatted and windows asks if I want to format. Another disk utility (EASEUS) sees the drive, can show how its partitioned, and I can explore within the partitions to see that files exist.
I've been searching for a long while to find someone somewhere who might have info on how to fix the Internal SD partition information, but have yet to find anything. Reflashing the factory ROM, "factory reset", etc. appear to just repopulate the already partitioned areas. The closest thing I have found to my problem is a post called "Challenge to members... Help me fix internal partitions without recovery" on the Incredibleforums elsewhere (can't post external links yet). Unfortunately, trying those solutions doesn't fix the issue. That post deals with /dev/mount/mmcblk0p1 and /dev/mount/mmcblk0p2. My issue appears to be in /dev/mount/mmcblk0p3. Parted doesn't like that one much. I have attached a couple of files that show parted output for all of the drives that get mounted, per /etc/fstab & /etc/recovery.fstab. This was done in ADB while the phone was booted into recovery.
If anyone can point me in the right direction how to properly (and safely) repartition the *internal* areas back to how they should be, I'd really appreciate the help!
Thanks,
Blue
I ran across this:
http://talk.maemo.org/showthread.php?t=15746
.... hope it helps send you in the right direction anyway. Good luck!
Formating instructions i think it would be a better idea to try using the ruu.exe tool to reflash your phone and it should format that partition back and put all the old apps it came with back in proper order. Since the phone is use able right now you could also try a factory reset first if you don't want to try the ruu.exe.
Thanks for the link and tip for RUU.
sfdisk does not appear to be a useable command on my DInc. Is there an Android version/port? Also, that link suggests that the partition should be msdos, but isn't the boot sector type supposed to be ext2/3 or yaffs2 (?) on the DInc?
I have already tried the factory reset as well as reformatting the phone areas using CWM Recovery (3.0.0.8). I also reflashed a factory stock ROM found in the lastest RUU. I also flashed the 2nd to latest ROM from that RUU (2.1). All of these only reformatted and re-installed stock ROM. Unfortunately, doing so only reformats the existing partitions, but does not fix the screwed up partition sizing. As far as I can determine, setting my phone back to S-ON and running the RUU will do nothing different than what I did by placing the stock PB31IMG.zip in the root of my (external) SD card and flashing it from HBOOT.
If the RUU truly repartitions the internal memory, then I'm game to set S-ON and try that. However, all indications are that doing so will be no different than flashing PB31IMG.zip. Is that correct?
Thanks again,
Blue
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
What version of cwm are you using?
Sent From My Optimized HTC Incredibly Dinc
It was the orange, but I upgraded it to see if it would work. uh, oh, as I write this, I fear worse...
Upgrading changed cwm to blue, but still same problems. It is almost as if the data directory has no write permissions.
I got impatient and used the ruu.exe from pvillecomp and now it gets stuck at the red eye droid screen and is on a reboot loop.
I can't get into recovery now, I get the phone icon with the red ! triangle. I figure cwm is gone now, so what, use unrevoked again? This would flash a new recovery, correct? Otherwise, how would I get the zip file onto the sd card now to flash via hboot? Even with a cwm, I imagine I will have the same formatting issues, unless the rom upate utility corrected those.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
Try manually mounting /data before wiping it.
EDIT: Nevermind just read your other post about loosing cw recovery. Are you still s-off?
yeah, I tried every combination of mounting and formatting and it always failed with the same message. I am still S-off, so I imagine from here I can use unrevoked to flash cwm back onto it then I can try to restore from a saved ROM I have on my card. Should I do that?
I could copy the file to flash cwm file to my card instead I guess, but my card would have to be FAT32 I assume.
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
Do you have a ext2/3/4 partition on your sdcard?
cmlusco said:
Do you have a ext2/3/4 partition on your sdcard?
Click to expand...
Click to collapse
By partition, do mean directories? I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I've already tried it before. It did not touch my card but did reset my phone's programming.
The restore function in CWM only touches the internal memory, correct?
evil_elf said:
By partition, do mean directories? If so, yes. I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
Click to expand...
Click to collapse
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
cmlusco said:
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
Click to expand...
Click to collapse
I tried the Factory Reset from HBOOT and also the Wipe Data/Factory Reset from CWM. Occasionally I am getting the 5 vibrations and a black screen when trying to turn off and on; battery pull allows me to boot up into ROM or HBOOT.
CM7 is working now, but the hard button bindings are screwed up along with a bunch of other stuff. CWM is able to restore the system, but fails on data so it makes sense. I can't receive calls either. I was so hoping the ruu would have fixed this...
The card should have no bearing on flashing a ROM? Or am I not understanding this?
Oh, I also tried to restore and format data manually without the card in to no avail. The Wipe Data/Factory Reset formats the data folder without errors but not the manually method of formatting or the restore method.
Could this help? http://forum.xda-developers.com/showthread.php?p=18287267
Just tried this: http://forum.xda-developers.com/showthread.php?t=1006556
Still same error.
To return my phone under warranty to a Verizon store, do I need to make sure that the stock ROM is flashed and the phone is unrooted with S-ON again? I am starting to think this is the route I am heading down and I only have a week left on my warranty.
Very short answer.........YES!!!
A kind soul helping me at http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
*Possible Solution* If still an issue
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Can i get those files?
i dont have a working incredible. can you post a link to the working filesystem.
Thanks.
androidi1 said:
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Click to expand...
Click to collapse
Here try this one http://dinc.does-it.net/Touch_of_Blue/filesystem.zip, im interested to see if this works for you too. It seems quite a few people have been having issues with /data latley.
I get error
Code:
push: filesystem/sys/devices/platform/android_pmem.0/power/wakeup -> /sys/devices/platform/android_pmem.0/power/wakeup
failed to copy 'filesystem/sys/devices/platform/android_pmem.0/power/wakeup' to '/sys/devices/platform/android_pmem.0/power/wakeup': Operation not permitted
i get this error trying to push the filesystem. any workaround?
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.
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.