Database Info

[Q] 64gb tf700 partitions show up as tmpfs

Hey all, i accidentally formatted the partitions on the tf700. it was unlocked/rooted and i have TWRP installed.
i do not have access to fastboot. i can use adb and adb shell.
i have tried the options 1a & 1b for the prime tf201 unbrick with no luck.
in the terminal if i write the command "df" it shows that the only partition i have is TMPFS, and it is 499732 1K blocks - mounted on /dev
since the card is showing up as TMPFS it is basically a ramdisk and it will be erased on a reboot, so no matter what changes i make, or rom i install it will always be erased.
if i try to mount the /data /system /cache partitions they all return E:Unable to mount '/system' (tw_mount)
( '/system' changes with '/data' and '/cache')
if i go to /dev/block the only things i see are loop0 - loop7 and mmcblk0p3
im thinking that all i need to do is somehow format the internal memory to reinstall a rom and i should be good to go, but i dont know what the partitions need to be, but i could also be way off.
im hoping someone has some insight. i would hate to have a brick

pbcustom98 said:
Hey all, i accidentally formatted the partitions on the tf700. it was unlocked/rooted and i have TWRP installed.
Click to expand...
Click to collapse
How did you do that?
pbcustom98 said:
if i go to /dev/block the only things i see are loop0 - loop7 and mmcblk0p3
Click to expand...
Click to collapse
Looks like your GPT got damaged - this may not be easy to repair (AFAIK the original GPT is nowhere in the Asus firmware download), but as long as you can boot TWRP and use adb, there is hope.
First of all, what does "cat /proc/partitions" say? For comparison, here is my output:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 62087168 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 59976192 mmcblk0p8
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1

_that said:
How did you do that?
Looks like your GPT got damaged - this may not be easy to repair (AFAIK the original GPT is nowhere in the Asus firmware download), but as long as you can boot TWRP and use adb, there is hope.
First of all, what does "cat /proc/partitions" say? For comparison, here is my output:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 62087168 mmcblk0
179 1 786432 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 835584 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 59976192 mmcblk0p8
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Click to expand...
Click to collapse
out of stupidity
cat /proc/partitions shows the following:
# cat /proc/partitions
major minor #blocks name
under it though, there is nothing there

pbcustom98 said:
out of stupidity
Click to expand...
Click to collapse
If you can describe what you did, maybe it is easier to find out what exactly happened.
I assume you don't have an nvflash backup, right?
pbcustom98 said:
under it though, there is nothing there
Click to expand...
Click to collapse
OK. What is the output if you run:
Code:
dmesg|grep mmcblk0
?

_that said:
If you can describe what you did, maybe it is easier to find out what exactly happened.
I assume you don't have an nvflash backup, right?
OK. What is the output if you run:
Code:
dmesg|grep mmcblk0
?
Click to expand...
Click to collapse
I was unlocking the tablet, installing TWRP and then wiping the data, i misread the options and went too far by doing the format data option.
no backup. i do not have access to fastboot/APX now, and i did not create one before.
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this tablet to redo it.
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet

pbcustom98 said:
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
Click to expand...
Click to collapse
Strange, it should at least output the line about detecting the card. Please reboot your tablet into recovery (to restart the kernel log), then do from your computer
Code:
adb shell dmesg > dmesg.txt
and put the resulting file on pastebin or attach it here.

pbcustom98 said:
I was unlocking the tablet, installing TWRP and then wiping the data, i misread the options and went too far by doing the format data option.
no backup. i do not have access to fastboot/APX now, and i did not create one before.
C:\Users\Daniel>adb shell
~ # ←[6ndmesg|grep mmcblk0
dmesg|grep mmcblk0
~ # ←[6n^C
C:\Users\Daniel>
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this talet to redo it.
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet
Click to expand...
Click to collapse
That's odd, format data will not and shouldn't do that. I did this all the time. Do you have the lastest TWRP and was on JB? if you do, go back to "WIPE" option and do the wipe format again. This should reformat with ext4. After that do factory reset, wipe system, internal storage then try to reflash Cleanrom. TWRP may some how corrupted your partition, but not what you did.

_that said:
Strange, it should at least output the line about detecting the card. Please reboot your tablet into recovery (to restart the kernel log), then do from your computer
Code:
adb shell dmesg > dmesg.txt
and put the resulting file on pastebin or attach it here.
Click to expand...
Click to collapse
i cannot post outside links until about 10 posts.
Here is the pastebin attachedView attachment dmesg.txt

pbcustom98 said:
also, the only way i have seen to get the other mmcblk0 partitions to show up (0p3, 0p4 etc) is to run the commands for the tf201 unbrick (option 1a/b)
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Click to expand...
Click to collapse
If the partitions are not already there, then these commands simply create files that are named like the block devices that are missing. Not what you want at all, but harmless.
pbcustom98 said:
i was thinking that all i needed to do was to somehow format the data so the tablet can write to the partition instead of it just acting as a ramdisk. i even tried running fdisk -H 1 /dev/block/mmcblk0 and tried to format the data but i'm not familiar with the partition table of this tablet to redo it.
Click to expand...
Click to collapse
Do not try to to use fdisk, it does not support GPT.
pbcustom98 said:
i have also tried doing those commands above and then running a live usb gparted disk to see if it shows up, but it hasnt worked yet
Click to expand...
Click to collapse
How would you run a live disk on the tablet?
---------- Post added at 05:53 PM ---------- Previous post was at 05:46 PM ----------
pbcustom98 said:
i cannot post outside links until about 10 posts.
Here is the pastebin attachedView attachment 1456337
Click to expand...
Click to collapse
The important part is here:
Code:
<6>[ 9.067211] [mmc]:mmc_read_ext_csd:259 ext_csd.sectors 0x766c000 prod_name HYNIX BOOT_SIZE_MULTI 0x20
<4>[ 9.109988] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 9.116163] mmc0: error -110 whilst initialising MMC card
The recovery kernel cannot initialize the MMC card. So there is no point in trying to run partitioning tools at this time, first you need to gain access to the eMMC. It cannot be completely broken, otherwise it could not boot the recovery.
Next step: find out what error -110 is and how to fix it.
btw, this thread seems to describe the same situation (read the post from MysticMgcn): http://forum.xda-developers.com/showthread.php?t=1917304

_that said:
If the partitions are not already there, then these commands simply create files that are named like the block devices that are missing. Not what you want at all, but harmless.
Do not try to to use fdisk, it does not support GPT.
How would you run a live disk on the tablet?
Click to expand...
Click to collapse
i ran gparted live usb on my laptop and tried connecting the tablet via usb after i had the partitions created.

pbcustom98 said:
i ran gparted live usb on my laptop and tried connecting the tablet via usb after i had the partitions created.
Click to expand...
Click to collapse
I still don't understand - where did you create those partitions? On your laptop?
Anyway, your TF700 is bricked until someone finds out how to make the TWRP kernel initialize the eMMC correctly in your situation. Without that, your internal storage is inaccessible, so any fix attempt at that level will fail.
Unfortunately there is still very little public information how the bootloader interacts with the kernels, so I cannot help you further. You may try asking in the thread I linked in my last post if anyone was able to recover from this.

_that said:
I still don't understand - where did you create those partitions? On your laptop?
Anyway, your TF700 is bricked until someone finds out how to make the TWRP kernel initialize the eMMC correctly in your situation. Without that, your internal storage is inaccessible, so any fix attempt at that level will fail.
Unfortunately there is still very little public information how the bootloader interacts with the kernels, so I cannot help you further. You may try asking in the thread I linked in my last post if anyone was able to recover from this.
Click to expand...
Click to collapse
i ran these two commands via adb shell:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then once i saw them in /dev/block, i rebooted my laptop into gparted hoping that they would show up as a partition i can make changes to, but they didnt.
i will ask in the thread you linked, and thanks for all your help.

Nexus s eMMC dead, or what?

Unlocked Nexus s i9023 stuck on google logo. Tried to wipe cache/ re-flash in recovery...but unable to mount sdcard. "E:Unable to mount /sdcard"
I have tried: Fastboot.. flashing boot and recovery works.
system and userdata ain't
sending 'userdata' (18796 KB)...
OKAY [ 2.511s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 2.539s
On phone screen "Verified EXT4 image!" in red
Odin3 v1.83 with download mode gives write error and on phone screen red txt
KA3...New eMMC Support Fail
Stock android recovery wipe data/factory reset does do nothing.
Sideload...on TWRP recovery.
C:\Users\Jaani\Desktop\adb>adb push rom.zip /sdcard
2788 KB/s (153760279 bytes in 53.839s)
Then try to install zip. Failed, unable to mount storage.
Any ideas?

Lock and unlock bootloader. If still not working then eMMC dead.

smit.sanghavi said:
Lock and unlock bootloader. If still not working then eMMC dead.
Click to expand...
Click to collapse
C:\Users\Jaani\Desktop\adb>fastboot oem lock
...
OKAY [ 0.048s]
finished. total time: 0.051s
C:\Users\Jaani\Desktop\adb>fastboot oem unlock
...
FAILED (remote: Erase Fail)
finished. total time: 21.708s
C:\Users\Jaani\Desktop\adb>fastboot oem unlock
...
FAILED (remote: Erase Fail)
finished. total time: 1.671s

So long eMMC...

smit.sanghavi said:
So long eMMC...
Click to expand...
Click to collapse
Also tried that hairdryer trick, didn't help.

Try a new usb cable! I know it sounds a little tooo easy but I had same problem. I finally found that the cable has to be really snug in fit. I mean real tight that it almost feels like it wont fit. It seems that if there is just a slight bit of play the signal gets pooched somehow and then everything reports dead.
Once you get a cable that fits real well, adb, fastboot and the whole nine yards will work and life will be grand again. It took a while and a few returns to Staples and Best Buy and Future Shop til I found the right one and when i did i bought two spare just becuase and I haven't had any problems since.
I just retired my Nexus S in late November (which was my daily driver since it came out) for a Nexus 5. The S is now running CM11 KK4.4.2 and surprisingly much much smoother than JB but there ain't no looking back after having a N5.
Good luck!

Ezee-E said:
Try a new usb cable! I know it sounds a little tooo easy but I had same problem. I finally found that the cable has to be really snug in fit. I mean real tight that it almost feels like it wont fit. It seems that if there is just a slight bit of play the signal gets pooched somehow and then everything reports dead.
Once you get a cable that fits real well, adb, fastboot and the whole nine yards will work and life will be grand again. It took a while and a few returns to Staples and Best Buy and Future Shop til I found the right one and when i did i bought two spare just becuase and I haven't had any problems since.
I just retired my Nexus S in late November (which was my daily driver since it came out) for a Nexus 5. The S is now running CM11 KK4.4.2 and surprisingly much much smoother than JB but there ain't no looking back after having a N5.
Good luck!
Click to expand...
Click to collapse
Tried 7 different cables. Original Samsung, Nokia, LG's and Kindle. No success. =(

Hi, i have like problem.
I think device has incorrect fstab and partitions configuration.
Nexus S has flash memory chip, parted to some blocks.
Code:
ls /dev/block/platform/s5pc110-onenand
mtdblock0 mtdblock1 mtdblock2 mtdblock3 mtdblock4 mtdblock5 mtdblock6
it is eMMC?
---------- Post added at 07:04 AM ---------- Previous post was at 06:57 AM ----------
markeshov said:
Hi, i have like problem.
I think device has incorrect fstab and partitions configuration.
Nexus S has flash memory chip, parted to some blocks.
Code:
ls /dev/block/platform/s5pc110-onenand
mtdblock0 mtdblock1 mtdblock2 mtdblock3 mtdblock4 mtdblock5 mtdblock6
it is eMMC?
Click to expand...
Click to collapse
jaani8
can you show ouput from your device?
ls /dev/block/platform

markeshov said:
Hi, i have like problem.
I think device has incorrect fstab and partitions configuration.
Nexus S has flash memory chip, parted to some blocks.
Code:
ls /dev/block/platform/s5pc110-onenand
mtdblock0 mtdblock1 mtdblock2 mtdblock3 mtdblock4 mtdblock5 mtdblock6
it is eMMC?
---------- Post added at 07:04 AM ---------- Previous post was at 06:57 AM ----------
jaani8
can you show ouput from your device?
ls /dev/block/platform
Click to expand...
Click to collapse
Seems same. TWRP recovery.
~ # ←[6nls /dev/block/platform
ls /dev/block/platform
s5pc110-onenand
~ # ←[6n
~ # ←[6nls /dev/block/platform/s5pc110-onenand
ls /dev/block/platform/s5pc110-onenand
mtdblock0
mtdblock1
mtdblock2
mtdblock3
mtdblock4
mtdblock5
mtdblock6
/dev/block/platform/s5pc110-onenand # ←[6ncd mtdblock0
cd mtdblock0
/sbin/sh: cd: can't cd to mtdblock0

Up!

jaani8 said:
Unlocked Nexus s i9023 stuck on google logo. Tried to wipe cache/ re-flash in recovery...but unable to mount sdcard. "E:Unable to mount /sdcard"
I have tried: Fastboot.. flashing boot and recovery works.
system and userdata ain't
sending 'userdata' (18796 KB)...
OKAY [ 2.511s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 2.539s
On phone screen "Verified EXT4 image!" in red
Odin3 v1.83 with download mode gives write error and on phone screen red txt
KA3...New eMMC Support Fail
Stock android recovery wipe data/factory reset does do nothing.
Sideload...on TWRP recovery.
C:\Users\Jaani\Desktop\adb>adb push rom.zip /sdcard
2788 KB/s (153760279 bytes in 53.839s)
Then try to install zip. Failed, unable to mount storage.
Any ideas?
Click to expand...
Click to collapse
Try to Relock the Bootloader and then again Unlock it, then try all you did if failed again then eMMc is dead.
There is 1% chance of fixing your phone even by a technisian. Because he needs to pull out the dead eMMc and paste a new one. As nexus devices dont support SD card otherwise you could have flashed your device over SD card. The eMMc on Nexus is pasted one so its very difficult to plug it out sucessfully.
You may need to change the mainboard of your phone if You need the mainboard contact me...
Good Luck

[Q] xt925 Encryption Unsuccessful - cannot flash

So a year or so ago I flashed up to 4.1.2 (FIDO) on the phone and all worked fine.
Now the phone wont boot, all I get is Encryption Unsuccessful screen. I have tried reFlashing FIDO, and Stock 4.0.4 but RSDlite just throws a message saying "FAIL" - I think is due to a Partition problem. I have access to the Boot menu (10.9B), I have tried wiping the Cache and factory reset - Nothing.
Any Ideas how I can fix the partition and re Flash a ROM?

Have a came error too.
is0lde said:
So a year or so ago I flashed up to 4.1.2 (FIDO) on the phone and all worked fine.
Now the phone wont boot, all I get is Encryption Unsuccessful screen. I have tried reFlashing FIDO, and Stock 4.0.4 but RSDlite just throws a message saying "FAIL" - I think is due to a Partition problem. I have access to the Boot menu (10.9B), I have tried wiping the Cache and factory reset - Nothing.
Any Ideas how I can fix the partition and re Flash a ROM?
Click to expand...
Click to collapse
Waiting for an answer too.
---------- Post added at 11:13 AM ---------- Previous post was at 10:48 AM ----------
KisL said:
Waiting for an answer too.
Click to expand...
Click to collapse
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 102400 mmcblk0p1
179 2 1500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 512 mmcblk0p4
179 5 256 mmcblk0p5
179 6 140 mmcblk0p6
179 7 192 mmcblk0p7
179 8 512 mmcblk0p8
179 9 4 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1500 mmcblk0p12
179 13 500 mmcblk0p13
179 14 500 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1632 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 2048 mmcblk0p19
179 20 640 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 8 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 1024 mmcblk0p25
179 26 512 mmcblk0p26
179 27 3072 mmcblk0p27
179 28 128 mmcblk0p28
179 29 4096 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 10240 mmcblk0p32
259 1 8192 mmcblk0p33
259 2 138754 mmcblk0p34
259 3 786432 mmcblk0p35
259 4 1523712 mmcblk0p36
259 5 153600 mmcblk0p37
259 6 12608751 mmcblk0p38
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 421180 48 421132 0% /dev
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
~ # mount /system
mount /system
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,user_xatt
r,barrier=1,data=ordered 0 0
mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument

please help
KisL said:
Waiting for an answer too.
---------- Post added at 11:13 AM ---------- Previous post was at 10:48 AM ----------
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 102400 mmcblk0p1
179 2 1500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 512 mmcblk0p4
179 5 256 mmcblk0p5
179 6 140 mmcblk0p6
179 7 192 mmcblk0p7
179 8 512 mmcblk0p8
179 9 4 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1500 mmcblk0p12
179 13 500 mmcblk0p13
179 14 500 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1632 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 2048 mmcblk0p19
179 20 640 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 8 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 1024 mmcblk0p25
179 26 512 mmcblk0p26
179 27 3072 mmcblk0p27
179 28 128 mmcblk0p28
179 29 4096 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 10240 mmcblk0p32
259 1 8192 mmcblk0p33
259 2 138754 mmcblk0p34
259 3 786432 mmcblk0p35
259 4 1523712 mmcblk0p36
259 5 153600 mmcblk0p37
259 6 12608751 mmcblk0p38
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 421180 48 421132 0% /dev
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
~ # mount /system
mount /system
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,user_xatt
r,barrier=1,data=ordered 0 0
mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
Click to expand...
Click to collapse
Any ideas? In Russia no Motorola service. I read about this problem on another phones. It can be crashed internal storage, but why in ADB i can see partitions? How to format all internal storage and parted it like a stock?

My FIDO XT925 also had this problem suddenly. From what I have found so far I have tried to use the stock recovery (hold vol +/- then power button,white menu will pop up, follow the instructions and select recovery with vol +), to update to Jelly bean but that is not working. I have also tried RSD Lite 6 and the flash process always fails to verify even after I modified the xml file. I'm pretty stuck at this point as well, hoping someone can help.

Bumping this. Just happened to my XT925 a day ago. Was working fine, last thing I noticed was googleservices crashing (with the OK button that was stuck in an infinite loop) so I had to hard-shut it off..
Was rooted since last year, but nothing odd happening recently, seemed totally random.. Also did the above, nothing seems to be working, is it bricked?
Also, any way to recover the internal SD card contents?

Weaponx525 said:
My FIDO XT925 also had this problem suddenly. From what I have found so far I have tried to use the stock recovery (hold vol +/- then power button,white menu will pop up, follow the instructions and select recovery with vol +), to update to Jelly bean but that is not working. I have also tried RSD Lite 6 and the flash process always fails to verify even after I modified the xml file. I'm pretty stuck at this point as well, hoping someone can help.
Click to expand...
Click to collapse
Gloomfrost said:
Bumping this. Just happened to my XT925 a day ago. Was working fine, last thing I noticed was googleservices crashing (with the OK button that was stuck in an infinite loop) so I had to hard-shut it off..
Was rooted since last year, but nothing odd happening recently, seemed totally random.. Also did the above, nothing seems to be working, is it bricked?
Also, any way to recover the internal SD card contents?
Click to expand...
Click to collapse
i dont know if i can help, but partition errors need to be fixed with moto fastboot. no other solution will work.
there are a couple of ways to go about this.
1. get moto fastboot and your stock file (if it doesnt contain a partition file your stuck, some do some dont)
flash each partition manually with mfastboot command starting with the partition file (important you flash the partition file first).
2. grab my "script" from the dev forum. make sure you get the "gpt fix" version. DO NOT USE THE SCRIPT AS IS, IT IS FOR 926 ONLY.
you can either:
A. run your commands from that folder as it already has the required moto fastboot.
or
B. delete all the 926 files from that folder
drop in all of your phones files and edit the "win batch file" file to fix any file name mismatches (you only need to flash the partitions i have listed, dont bother adding any more)
i dont recall if i left the "-w" command in there. that is the data wipe command. remove this line entirely if you want to try and keep data.
not sure if this will help, but if you have partition issues, these are the only ways to fix it.

bweN diorD said:
i dont know if i can help, but partition errors need to be fixed with moto fastboot. no other solution will work.
there are a couple of ways to go about this.
1. get moto fastboot and your stock file (if it doesnt contain a partition file your stuck, some do some dont)
flash each partition manually with mfastboot command starting with the partition file (important you flash the partition file first).
2. grab my "script" from the dev forum. make sure you get the "gpt fix" version. DO NOT USE THE SCRIPT AS IS, IT IS FOR 926 ONLY.
you can either:
A. run your commands from that folder as it already has the required moto fastboot.
or
B. delete all the 926 files from that folder
drop in all of your phones files and edit the "xml" file to fix any file name mismatches (you only need to flash the partitions i have listed, dont bother adding any more)
i dont recall if i left the "-w" command in there. that is the data wipe command. remove this line entirely if you want to try and keep data.
not sure if this will help, but if you have partition issues, these are the only ways to fix it.
Click to expand...
Click to collapse
Thanks, can I run some links by you to make sure I'm using the right stuff?
Moto fastboot: http://forum.xda-developers.com/showthread.php?t=1953948
Stock file: http://sbf.droid-developers.org/phone.php?device=6 - Should I use 4.0.4 or 4.1.2? I was on 4.1.2 OTA.
How do you mean flash each partition manually?
2. http://forum.xda-developers.com/showthread.php?t=2474393, downloading the "GPT error fix - Mirror 1" correct?
Is it step 1 OR step 2? Seems like you said you already have the moto fastboot in your link.. Also, what XT926 files are there to delete?

Gloomfrost said:
Thanks, can I run some links by you to make sure I'm using the right stuff?
Moto fastboot: http://forum.xda-developers.com/showthread.php?t=1953948
Stock file: http://sbf.droid-developers.org/phone.php?device=6 - Should I use 4.0.4 or 4.1.2? I was on 4.1.2 OTA.
How do you mean flash each partition manually?
2. http://forum.xda-developers.com/showthread.php?t=2474393, downloading the "GPT error fix - Mirror 1" correct?
Is it step 1 OR step 2? Seems like you said you already have the moto fastboot in your link.. Also, what XT926 files are there to delete?
Click to expand...
Click to collapse
m fastboot (check)
stock file (you have to use one = to or higher than the one currently installed. so 404 is a no)
flash manually (open a command prompt where you have mfastboot saved, connect your phone in fastboot, also make sure you have all of your stock files in the same dir as mfastboot, flash each partition using the mfastboot command and your correct file name. it would be easier if you look at the win batch file file in my gpt script for the proper commands to send rather than me trying to explain it. you will send the commands exactly as i have them in the batch file only correcting for file names and wait for each to finish, make sure its finished some take a bit of time like system.)
gpt utility (check)
step 1 or 2 (some people are lazy (not you obviously and wont go find mfastboot, so i only mentioned it is in my script for convenience)
what 926 files (just delete everything but the mfastboot.exe and the batch file file. all the other files you wont need or can use.
if you want, i can quickly upload the batch file file so you dont have to dl all that just for one file, and you can get the mfastboot from the other thread you posted.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Gloomfrost said:
Thanks, can I run some links by you to make sure I'm using the right stuff?
Moto fastboot: http://forum.xda-developers.com/showthread.php?t=1953948
Stock file: http://sbf.droid-developers.org/phone.php?device=6 - Should I use 4.0.4 or 4.1.2? I was on 4.1.2 OTA.
How do you mean flash each partition manually?
2. http://forum.xda-developers.com/showthread.php?t=2474393, downloading the "GPT error fix - Mirror 1" correct?
Is it step 1 OR step 2? Seems like you said you already have the moto fastboot in your link.. Also, what XT926 files are there to delete?
Click to expand...
Click to collapse
OMG, i think my head is up my arse.
you dont want the xml file, you want the windows batch file. let me go edit those post grrrrr
---------- Post added at 06:11 PM ---------- Previous post was at 06:05 PM ----------
Gloomfrost said:
Thanks, can I run some links by you to make sure I'm using the right stuff?
Moto fastboot: http://forum.xda-developers.com/showthread.php?t=1953948
Stock file: http://sbf.droid-developers.org/phone.php?device=6 - Should I use 4.0.4 or 4.1.2? I was on 4.1.2 OTA.
How do you mean flash each partition manually?
2. http://forum.xda-developers.com/showthread.php?t=2474393, downloading the "GPT error fix - Mirror 1" correct?
Is it step 1 OR step 2? Seems like you said you already have the moto fastboot in your link.. Also, what XT926 files are there to delete?
Click to expand...
Click to collapse
ok here are the exact commands (just fix your file name as needed)
mfastboot flash partition gpt_main0.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot -w (this can be omitted if you want to try and save data)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot

bweN diorD said:
m fastboot (check)
stock file (you have to use one = to or higher than the one currently installed. so 404 is a no)
flash manually (open a command prompt where you have mfastboot saved, connect your phone in fastboot, also make sure you have all of your stock files in the same dir as mfastboot, flash each partition using the mfastboot command and your correct file name. it would be easier if you look at the win batch file file in my gpt script for the proper commands to send rather than me trying to explain it. you will send the commands exactly as i have them in the batch file only correcting for file names and wait for each to finish, make sure its finished some take a bit of time like system.)
gpt utility (check)
step 1 or 2 (some people are lazy (not you obviously and wont go find mfastboot, so i only mentioned it is in my script for convenience)
what 926 files (just delete everything but the mfastboot.exe and the batch file file. all the other files you wont need or can use.
if you want, i can quickly upload the batch file file so you dont have to dl all that just for one file, and you can get the mfastboot from the other thread you posted.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
OMG, i think my head is up my arse.
you dont want the xml file, you want the windows batch file. let me go edit those post grrrrr
---------- Post added at 06:11 PM ---------- Previous post was at 06:05 PM ----------
ok here are the exact commands (just fix your file name as needed)
mfastboot flash partition gpt_main0.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot -w (this can be omitted if you want to try and save data)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Click to expand...
Click to collapse
Okay thanks. I downloaded your GPT fix, deleted everything inside except mfastboot.exe and the batch file. Then I downloaded the 4.1.2 from sbf and extracted everything inside your utility folder. However, I'm not seeing file extensions.. what's up with that? Like, no bin, no .ext4? I downloaded the Android 4.1.2
Blur_Version.98.21.122002.XT925.RCI.en.CA
I'm going to assume it won't work unless they have file extensions..
Also, if I'll be running mfastboot manually using cmd prompt, why do I need the batch file? --EDIT: Nevermind, you want me to replace what it says with what you wrote here. Gotcha. What do you mean then by 'just fix your file name as needed' - You mean like if the 4.1.2 thing has 'fsg_signed' I should use that in the batch file correct?
Btw sorry, new user limits, have to wait 5 min before edits heh.. =|

Gloomfrost said:
Okay thanks. I downloaded your GPT fix, deleted everything inside except mfastboot.exe and the batch file. Then I downloaded the 4.1.2 from sbf and extracted everything inside your utility folder. However, I'm not seeing file extensions.. what's up with that? Like, no bin, no .ext4? I downloaded the Android 4.1.2
Blur_Version.98.21.122002.XT925.RCI.en.CA
I'm going to assume it won't work unless they have file extensions..
Also, if I'll be running mfastboot manually using cmd prompt, why do I need the batch file?
Click to expand...
Click to collapse
i dont know actually, it might work. you could try going to control panel/folder option/view/hide extensions for known file types and check or uncheck and see if it fixes the issue.
you dont, it was more of a guide assuming you didnt know the sequence and proper commands. but since i posted that, there is no reason if you want to do it manually.
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Gloomfrost said:
Okay thanks. I downloaded your GPT fix, deleted everything inside except mfastboot.exe and the batch file. Then I downloaded the 4.1.2 from sbf and extracted everything inside your utility folder. However, I'm not seeing file extensions.. what's up with that? Like, no bin, no .ext4? I downloaded the Android 4.1.2
Blur_Version.98.21.122002.XT925.RCI.en.CA
I'm going to assume it won't work unless they have file extensions..
Also, if I'll be running mfastboot manually using cmd prompt, why do I need the batch file? --EDIT: Nevermind, you want me to replace what it says with what you wrote here. Gotcha. What do you mean then by 'just fix your file name as needed' - You mean like if the 4.1.2 thing has 'fsg_signed' I should use that in the batch file correct?
Btw sorry, new user limits, have to wait 5 min before edits heh.. =|
Click to expand...
Click to collapse
no problem
yea if you want to use the batch file and have it do everything for you automatically, you likely would need to fix some file names as the ones in your stock file might not match the ones i have.
for instance
our partition file is: mfastboot flash partition gpt_main0.bin
but your file may be called partition.bin so you would have to change that line to
mfastboot flash partition partition.bin

bweN diorD said:
i dont know actually, it might work. you could try going to control panel/folder option/view/hide extensions for known file types and check or uncheck and see if it fixes the issue.
you dont, it was more of a guide assuming you didnt know the sequence and proper commands. but since i posted that, there is no reason if you want to do it manually.
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
no problem
yea if you want to use the batch file and have it do everything for you automatically, you likely would need to fix some file names as the ones in your stock file might not match the ones i have.
for instance
our partition file is: mfastboot flash partition gpt_main0.bin
but your file may be called partition.bin so you would have to change that line to
mfastboot flash partition partition.bin
Click to expand...
Click to collapse
Okay so this is what I have now in the batch file, along with brackets for clarifications:
mfastboot flash partition partition_signed.bin
mfastboot flash system system_signed.img.ext4 (what extension should this have?)
mfastboot flash boot boot_signed.img
mfastboot -w
mfastboot flash modem_signed.bin
mfastboot erase modemst1 (leave this in even though I don't have any files like that in the package?)
mfastboot erase modemst2 (same as above?)
mfastboot flash fsg fsg_signed.mbn
mfastboot reboot
Should I take out all the extensions in the bat since that package file has none, or add them to the files as per above?

Gloomfrost said:
Okay so this is what I have now in the batch file, along with brackets for clarifications:
mfastboot flash partition partition_signed.bin
mfastboot flash system system_signed.img.ext4 (what extension should this have?) dont put an extension if your file states none, i think it will be fine
mfastboot flash boot boot.img
mfastboot -w delete this line if you want to try and save any data, i doubt either option will effect the success or failure of this mission but i would leave it in if you can
mfastboot flash modem NON-HLOS.bin (don't have anything like this in that package - should i remove this line?) doubt the modems were encrypted so delete this line
mfastboot erase modemst1 (left this in) delete this or you may have no modems, only because we arent re-writing them
mfastboot erase modemst2 (left this in) same as above
mfastboot flash fsg fsg_signed.mbn
mfastboot reboot
Should I take out all the extensions since that package file has none? no, just omit any that dont have extensions in your stock file. if we need to drop back and try another route, i would like to know that we tried the file names as you see them.
Click to expand...
Click to collapse
ok im going to go out on a limb here and make some edits above in red

bweN diorD said:
ok im going to go out on a limb here and make some edits above in red
Click to expand...
Click to collapse
Sorry I edited my previous message again - I have modem_signed. Leave that in instead of NON-HLOS?

Gloomfrost said:
Sorry I edited my previous message again - I have modem_signed. Leave that in instead of NON-HLOS?
Click to expand...
Click to collapse
thats kind of a catch 22, yea lets put that in but still remove the erase lines below it as you are writing the same modem.

bweN diorD said:
thats kind of a catch 22, yea lets put that in but still remove the erase lines below it as you are writing the same modem.
Click to expand...
Click to collapse
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.338s
sending 'system' (30720 KB)...
OKAY [ 2.348s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.030s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.544s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.057s
unknown partition 'modem_signed'
error: cannot determine image filename for 'modem_signed'
sending 'fsg' (2849 KB)...
OKAY [ 0.236s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.383s
rebooting...
finished. total time: 0.005s

Gloomfrost said:
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
Click to expand...
Click to collapse
yea, that sucks.
im having the same problem over here.
i made this other user the same updated (not published) script, just because he has a 926, and i can share the script with anyone who needs it. (just to say, i know this is the only method, you are in a bad spot!)
anyways, its the same as you just made with the same results.
have a look to see if maybe one of the simple fixes (not yet confirmed or denied) helped this member.

I really appreciate the efforts here. When I can wrap my head around this I will try as well as post my results. I felt I had hit a brick wall last night and email Motorola Canada for tech support help..
Sent from my SM-N900W8 using Tapatalk

Weaponx525 said:
I really appreciate the efforts here. When I can wrap my head around this I will try as well as post my results. I felt I had hit a brick wall last night and email Motorola Canada for tech support help..
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Keep me posted on this if you don't mind - after maybe 18 hours at this, I'm going to give up
I find it interesting that I managed to unlock my bootloader (even though it still threw a FAILED (remote failure), but going into fastboot DOES say 'Unlocked Status Code: 3'
I also found some chinese forum where people were posting how to do stuff with fastboot oem codes, but if I do fastboot oem anything it just says 'Restricted oem code'. Meh.
Any new phone suggestions? Something that will hopefully last 2 days with battery like this one did.

Gloomfrost said:
Keep me posted on this if you don't mind - after maybe 18 hours at this, I'm going to give up
I find it interesting that I managed to unlock my bootloader (even though it still threw a FAILED (remote failure), but going into fastboot DOES say 'Unlocked Status Code: 3'
I also found some chinese forum where people were posting how to do stuff with fastboot oem codes, but if I do fastboot oem anything it just says 'Restricted oem code'. Meh.
Any new phone suggestions? Something that will hopefully last 2 days with battery like this one did.
Click to expand...
Click to collapse
I am personally trying harder than usual to fix this phone because the battery life is so awesome. It's still a great deal. I hear the Moto X gets pretty great battery life and its cheaper than Nexus 5 right now. Personally I would wait for the Nexus 6, which is rumored to be be built by Motorola.
I am trying to fix this phone for my wife. Personally I am using a Note 3: great big battery and screen but no loyalty to Samsung. If the Nexus 6 pops up I may not be able to resist
---------- Post added at 05:46 AM ---------- Previous post was at 05:39 AM ----------
I'm trying to keep this phone stock. However I am curious if using Fastboot to unlock and installing custom recovery can work with the partition as screwed up as it is. If so maybe with custom recovery we can properly format the partitions. Thoughts?

Weaponx525 said:
I am personally trying harder than usual to fix this phone because the battery life is so awesome. It's still a great deal. I hear the Moto X gets pretty great battery life and its cheaper than Nexus 5 right now. Personally I would wait for the Nexus 6, which is rumored to be be built by Motorola.
I am trying to fix this phone for my wife. Personally I am using a Note 3: great big battery and screen but no loyalty to Samsung. If the Nexus 6 pops up I may not be able to resist
---------- Post added at 05:46 AM ---------- Previous post was at 05:39 AM ----------
I'm trying to keep this phone stock. However I am curious if using Fastboot to unlock and installing custom recovery can work with the partition as screwed up as it is. If so maybe with custom recovery we can properly format the partitions. Thoughts?
Click to expand...
Click to collapse
After everything sane failed (trying to save the userdata, trying to keep stock), I tried flashing random stuff, including sideloading. Nothing worked. Even the 'unlock' like I said threw an error, though the device does say unlocked. If you manage to successfully install custom recovery please post back how.

(Q) fastboot zimage zImage

Hello,
I'm trying flash zImage, but get some erros:
$ fastboot flash zimage zImage
target didn't report max-download-size
sending 'zimage' (4370 KB)...
OKAY [ 0.427s]
writing 'zimage'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.482s
How to solve it?
Tks,
Demiank

demiank said:
Hello,
I'm trying flash zImage, but get some erros:
$ fastboot flash zimage zImage
target didn't report max-download-size
sending 'zimage' (4370 KB)...
OKAY [ 0.427s]
writing 'zimage'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.482s
How to solve it?
Tks,
Demiank
Click to expand...
Click to collapse
Which device is this? Also some theories.
- zimage isn't the name of the actual partition, cd to /dev/block/platform/xxxxx/by-name/ to see your list of partitions
- the image you're flashing doesn't have correct syntax. To fast via flashboot, the syntax is... fastboot flash (partition) (image) . So an example would be fastboot flash recovery twrp.img . You need to remember the file extension such as .img or whatever it is for your image. Also make sure you specify the directory such as fastboot flash recovery C:\Users\xxx\Downloads\twrp.img if you aren't in the current directory.

demiank said:
Hello,
I'm trying flash zImage, but get some erros:
$ fastboot flash zimage zImage
target didn't report max-download-size
sending 'zimage' (4370 KB)...
OKAY [ 0.427s]
writing 'zimage'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.482s
How to solve it?
Tks,
Demiank
Click to expand...
Click to collapse
zImage is a kernel file and it is in the boot.img. you have to unpack your boot.img and replace the existing zImage with new one and repack boot.img again.
Then flash through fastboot mode by "fastboot flash boot boot.img"
So, you want to flash it in boot partition.

The device is LG e615 (2012/2013 device). This don't have a boot partition. I just found a boot.img in cwm backup. The command " fastboot boot zImage" generate a boot.img file.

demiank said:
The device is LG e615 (2012/2013 device). This don't have a boot partition. I just found a boot.img in cwm backup. The command " fastboot boot zImage" generate a boot.img file.
Click to expand...
Click to collapse
$ fastboot boot zImage
creating boot image...
creating boot image - 4478976 bytes
Downloading 'boot.img' OKAY [ 0.416s]
booting OKAY [ 0.159s]
Finished. Total time: 0.650s
Device don't boot and lost fastboot connection;
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 1003 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 28672 mmcblk0p12
179 13 28672 mmcblk0p13
179 14 624640 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 12288 mmcblk0p19
179 20 2823168 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 32 7761920 mmcblk1
179 33 7760896 mmcblk1p1
[email protected]:/ $ ls /
acct
cache
config
d
data
default.prop
dev
etc
fstab.m4ds
init
init.goldfish.rc
init.lge.early.rc
init.lge.rc
init.lge.usb.sh
init.m4ds.rc
init.m4ds.usb.rc
init.qcom.class_core.sh
init.qcom.class_main.sh
init.qcom.rc
init.qcom.ril.path.sh
init.qcom.sh
init.qcom.usb.rc
init.qcom.usb.sh
init.rc
init.target.rc
lgdms.fota.rc
lgdms.fota_update.rc
mnt
mpt
persist
persist-lg
proc
res
root
sbin
sdcard
storage
sys
system
ueventd.goldfish.rc
ueventd.m4ds.rc
ueventd.qcom.rc
ueventd.rc
vendor
[email protected]:/ # cat fstab.m4ds
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#LGE chage partition
#/dev/block/platform/msm_sdcc.3/by-num/p12 /system ext4 ro,barrier=1 wait
#/dev/block/platform/msm_sdcc.3/by-num/p13 /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait
#LGE_CHANGE_S [[email protected]] 20120926:Adding /data partition
/dev/block/platform/msm_sdcc.3/by-num/p14 /system ext4 ro,barrier=1,noatime wait
/dev/block/platform/msm_sdcc.3/by-num/p20 /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc,errors=continue check
Where is my stock zImage or boot.img? How to flash this zImage after compile it following the LG readme.txt:
"2. Kernel Build
- Untar opensource packages of kernel.tar.gz using following command at the android folder
a)$tar xvzf kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make m4-rev11_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot"
Tks for all replies, but i don't understand how to flash my new kernel compiled by me.

Need a repartitioning expert to restore an omitted partition

I think I did some mistakes while trying to reflash a rom on my Sony Xperia S (lt26i).
I was following this guide, the first time it worked but then I decided to ungoogle my phone but it went bad.
[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo
[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo [GUIDE/TUTORIAL/HOWTO] Upgrade Sony Xperia S (Model LT26i codename nozomi) from Android 2.3.7 to Android 8.1 Oreo / nAOSP Rom This detailed step-by-step guide helps you transform...
forum.xda-developers.com
My problem is that I deleted my OS and TWRP can't read the data partition nor mount to Windows.
So now, with djibe89's help (the OP of the guide), I managed to figure out that my data partition is corrupted.
Using the adb shell, like on step 12 of the guide, I went to the partitions and it gave me this
Omitting empty partition (14)
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
~ # fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
The partition 14 should be the data one, that i already merged with the 15 the first time i flashed the rom.
What should I do?

try deleting it and let Android generate new one??

Code:
fastboot erase userdata
fastboot format:ext4 userdata
fastboot reboot
now there's a high chance that your device doesn't support " fastboot format:ext4 userdata "
here's an alternative
fastboot erase userdata <~ never reboot your device after typing this command you would go on infinite bootloop type the next command ...
fastboot reboot recovery <~ if this command does not work and just restarted your device instead of going recovery mode you are now on bootloop ... access recovery mode by pressing combination key instead
via recovery mode do "wipe data / factory reset"
then reboot

ineedroot69 said:
Code:
fastboot erase userdata
fastboot format:ext4 userdata
fastboot reboot
now there's a high chance that your device doesn't support " fastboot format:ext4 userdata "
here's an alternative
fastboot erase userdata <~ never reboot your device after typing this command you would go on infinite bootloop type the next command ...
fastboot reboot recovery <~ if this command does not work and just restarted your device instead of going recovery mode you are now on bootloop ... access recovery mode by pressing combination key instead
via recovery mode do "wipe data / factory reset"
then reboot
Click to expand...
Click to collapse
the first method didn't work because of the format command like you predicted.
then i did the <erase userdata> but i think the <reboot recovery> command isn't available because it returns me the commands list. so i used this command from the list
fastboot reboot-bootloader
Click to expand...
Click to collapse
then unplugged the usb and rebooted on twrp.
now my data partition went back to 0mb (going to wipe -> advanced wipe -> data -> repair or change file system) and i can't even reformat it.
should i re-do the adb procedure to recreate the data partition?

mongolino0 said:
the first method didn't work because of the format command like you predicted.
then i did the <erase userdata> but i think the <reboot recovery> command isn't available because it returns me the commands list. so i used this command from the list
then unplugged the usb and rebooted on twrp.
now my data partition went back to 0mb (going to wipe -> advanced wipe -> data -> repair or change file system) and i can't even reformat it.
should i re-do the adb procedure to recreate the data partition?
Click to expand...
Click to collapse
yes your device won't boot without userdata partition since it got deleted with "fastboot erase userdata" so you need to recreate it by "formatting" it somehow

so i wanted to "recreate" the data partition with adb but now i can't even use adb.
i went to mount on twrp with the phone connected and the cmd still running from 2 hours ago. when I type adb devices I can't find
... is it possible that i did some irreversible mistake?

mongolino0 said:
so i wanted to "recreate" the data partition with adb but now i can't even use adb.
i went to mount on twrp with the phone connected and the cmd still running from 2 hours ago. when I type adb devices I can't find
... is it possible that i did some irreversible mistake?
Click to expand...
Click to collapse
you have TWRP flashed? you can't use it to format data?
also looking at the Sony Xperia S (lt26i) specification it was released back in February 2012 i guess it has serve its purpose for too long it is time for it to retire