Database Info

[Q][HELP!] Corrupted cache partition after flashing 5.1 Lollipop

Hi guys,
After flashing LP update 5.1 I`m in trouble with my 32GB Nexus 5
I got the error msg " E: can`t mount / cache " ( the same for system e.t.c). (before I did this I was on Custom ROM with Exposed framework installed.)
So I tryed to re-flash LP factory img (LMY47D) using fastboot command (via ADB SDK platform-tools) manually one by one according guides I found on xda.
I did it many times but the result was still the same - appears just green "android man" with rotating cube (10-15 min) and than it reboots itself and starts over again.
So I tryed to flash older factory image the same way (KTU48P) and I succeed to boot my phone but instead of 32 GB (normally available ~26GB) of my storage space there is only 12GB available now.
I thing there iscorupted partition but don`t know what to do next :crying: - how to restore it or format it ???
When I try to do that via Recovery I cant mount those partitions so I can`t format them...
When I did it via SDK - fastboot erase user data it takes veeery long time with no result
Could you pls help me how to format whole storage space ( all partitions ) and return back to stock rom with full 32GB space available ???
Thanks

Have you tried this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
There is a "32 GB phone now shows 16GB?" section.

shoeseat said:
Have you tried this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
There is a "32 GB phone now shows 16GB?" section.
Click to expand...
Click to collapse
Yes, that was one of the first think I tried.
--> I can`t clear cache & factory reset via stock recovery. Error msg -- "E: Unable to mount `/cache` "
--> Unfortunatelly fastboot erase userdata stucked ( it takes aleady 2 hours it started to erase the data and format the partition ) - do you thing it can freeze or it just can`t mount the data so it`s in loop ?
Any othe idea please , please ?

Have u tried to unmount cache partition from recovery?

shoeseat said:
Have u tried to unmount cache partition from recovery?
Click to expand...
Click to collapse
I can`t unmount it because it`s not mounted ...
When I tried to Wipe cache partition these errors appears :
PHP:
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)

Did you try
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img

joegestes said:
Did you try
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
Click to expand...
Click to collapse
Yes
fastboot erase/flash system was OK, but fastboot erase/flash cache got stucked
So after 2.5 hrs witnout any results I unplug the cord and start over again -- the same results

Maybe this will help
http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
---------- Post added at 09:04 AM ---------- Previous post was at 08:47 AM ----------
basavel said:
Hi guys,
So I tryed to flash older factory image the same way (KTU48P) and I succeed to boot my phone but instead of 32 GB (normally available ~26GB) of my storage space there is only 12GB available now.
Click to expand...
Click to collapse
Did you Wipe data/factory data reset after successful flash?
That will probably fix your 32=16 problem.

I tryed this tutorial :
http://forum.xda-developers.com/showthread.php?t=1284196
Thanks God it`s not "fried".
So I tryed this
Code:
mke2fs /dev/block/mmcblk0p27
(than reboot recovery)
... but still the same result
Than I tried to start over again from stock img flashing so :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
... it got stucked on erasing user data so I had to unplug the cord, restart bootloader
When I re-start the device appears "swireling" dodts (the boot animation) but no step forward, still booting....
When I tried to boot in recovery - dead android with red "!" appeared
Any other ideas what to do esle ?
Should I flash CWM or TWRP rec. instead ??
How this can be fixed ??
PLEASE !!!!:crying::crying::crying:

basavel said:
... it got stucked on erasing user data so I had to unplug the cord, restart bootloader
When I re-start the device appears "swireling" dodts (the boot animation) but no step forward, still booting....
When I tried to boot in recovery - dead android with red "!" appeared
Any other ideas what to do esle ?
Should I flash CWM or TWRP rec. instead ??
How this can be fixed ??
PLEASE !!!!:crying::crying::crying:
Click to expand...
Click to collapse
If you are getting an android sign with a red triangle it is normal for stock recovery.
You must tap volume up/down and the power button all together to get to the recovery menu.
Don't hold them in. Just tap all together at the same time and let go. It takes a couple tries but it works.
You'll then get a menu that will let you wipe data/factory reset.
use volume up/down to scroll to "wipe data/factory reset" then power button to select.
looks something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try it and reply back the result.

joegestes said:
If you are getting an android sign with a red triangle it is normal for stock recovery.
You must tap volume up/down and the power button all together to get to the recovery menu.
Don't hold them in. Just tap all together at the same time and let go. It takes a couple tries but it works.
You'll then get a menu that will let you wipe data/factory reset.
use volume up/down to scroll to "wipe data/factory reset" then power button to select.
looks something like this
try it and reply back the result.
Click to expand...
Click to collapse
Thanks man, I manage to boot under recovery mode.
After wipe data/factory reset system shows msg:
Code:
-- Wiping data...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
Data wipe complete
So I tried to wipe cache as well and it shows up this:
Code:
-- Wiping cache...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis
(I/O error)
E: failed to mount /cache (invalid argument)
I have no clue how to fix this can you help me pls ??

I would go to fatsboot and try to erase partitions and re flash again. see what happens.
If your data partition fails again we can try adb shell to repair your data partition.

I tried but again got stucked on erasing userdata...
I start research again and search for solution around partitions and I found this ( exactly my problem)
http://androidforums.com/threads/unable-to-mount-cache-while-doing-factory-reset.901188/
and solution for this was posted here on xda
http://forum.xda-developers.com/google-nexus-5/help/lost-cache-partition-fixed-t2949752#post58720690
this link helps me to get back to 32GB storage space (in fact ~ 26GB but doesn`t matter)
[The problem was exactlly the same missing EXT2 partition on cache partition (27)]
But error msg Can`t mount `/cache` still appears So I was not able to flash stock img LP 5.1 but I manage to flash 4.4.4 KTU84Q
It boots us and works like charm, but... ... still can`t mount/erase cache so it`s not fully solved yet but at least I can switch on/off the system now.
Can U pls help me with this mounting / partition problem ???
can it be fixed by stock OTA from KTU84Q to 5.0.1 and than the same to 5.1 ?

I had like 2 years ago similar problem with htc sensation but i fixed it by formating ir with ext2 and the reformated catch with ext4. Try to find something inside sensation forume

basavel said:
I manage to flash 4.4.4 KTU84Q
It boots us and works like charm, but... ... still can`t mount/erase cache so it`s not fully solved yet but at least I can switch on/off the system now.
Click to expand...
Click to collapse
Ok. So you are now successfully running 4.4.4 KTU84Q.
What happens now if you try flashing the stock cache.img of 4.4.4 KTU84Q:
fastboot erase cache
fastboot flash cache cache.img
Also, you could try and see what happens if you flash LP 5.01 lrx22c instead of 5.1 and do factory reset immediately after flash.

Even I manage to boot under KTU84Q the partition is still "lost" - means internal storage is ~26GB thats OK; but the error msg E: Can`t mount /cache bla bla bla still stays.
Actually I have these partitions :
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
So after I run this
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
It formats the cache partition (p27) to ext2 but after install of stock KTU84Q it`s back - UNFORMATED with no possibility to mount
What am I doing wrong ? :crying:

basavel said:
Even I manage to boot under KTU84Q the partition is still "lost" - means internal storage is ~26GB thats OK; but the error msg E: Can`t mount /cache bla bla bla still stays.
Actually I have these partitions :
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
So after I run this
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
It formats the cache partition (p27) to ext2 but after install of stock KTU84Q it`s back - UNFORMATED with no possibility to mount
What am I doing wrong ? :crying:
Click to expand...
Click to collapse
My guess is it needs to be formatted to ext4 not ext2.
KTU84Q probably can not recognize ext2.
Heres what mine looks like.
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
Again it looks like cache should be formatted ext4
Compare line 22 and line 27.
My line22 fsc is not formatted. Yours is formatted ext2
My line 27 cache is formatted ext4. Yours is not.
That is the problem.
Here is the list of partition locations
[/code]
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ #
[/code]

Finally I got to the stage where the ext2 partition stays ( do not disappear) after next flash.
How I did it - format the partition to ext2 than manually flash KTU84Q
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Than let the system update itself to 5.0.1 LRX22C
Now the erroe msg is gone (E: Can`t mount /cache) but agree those messed up partitions must be fixed.
The question is how ?
- should I install TWRP rec. and let it fix it when the cache partition is mountable now ?
- or should it fix it via ADB SHELL ? (and how ? mkfs.ext4 /dev/block/mmcblk0p27 ? )
- and how to erase line 22 in order to have in unformated ?
--- > or should I try to flash custom ROM over this ? - I don`t think so
Could you pls help with this ?
!!!THANKS!!!

basavel said:
Finally I got to the stage where the ext2 partition stays ( do not disappear) after next flash.
How I did it - format the partition to ext2 than manually flash KTU84Q
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Than let the system update itself to 5.0.1 LRX22C
Now the erroe msg is gone (E: Can`t mount /cache) but agree those messed up partitions must be fixed.
The question is how ?
- should I install TWRP rec. and let it fix it when the cache partition is mountable now ?
- or should it fix it via ADB SHELL ? (and how ? mkfs.ext4 /dev/block/mmcblk0p27 ? )
- and how to erase line 22 in order to have in unformated ?
--- > or should I try to flash custom ROM over this ? - I don`t think so
Could you pls help with this ?
!!!THANKS!!!
Click to expand...
Click to collapse
If it was me, the first thing I would do is flash TWRP. Second, make a full backup using TWRP backup function, then save/transfer a copy of that backup to my PC.
That way, moving forward id' have an easy way to restore the device back to it's presently functioning Lollypop state.
After that I might try the ADB shell command from TWRP you mentioned mkfs.ext4 /dev/block/mmcblk0p27 and see if that manages to re formats cache to ext4.
I've never tried this, and don't have much experience with parted, so I cant say if it will work. So proceed at your own risk.
As far as fsc( I think it means file save clean)partition goes. I honestly don't know but Ill try to find out.
Meanwhile, hopefully someone else with some mad partition skillz will chime in.:laugh:

TWRP coruupted all I did before - it tryed to repair broken partitions with f2fs but they are gone now
So I am 2 steps back
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
I can create only ext2 partition thanks to - mkfs.ext2 /dev/block/mmcblk0p27
The same code string with ext4 i.o ext2 is not working
MSG:
~ # mkfs.ext4 /dev/block/mmcblk0p27
mkfs.ext4 /dev/block/mmcblk0p27
/sbin/sh: mkfs.ext4: not found

[HOW TO] Fixing a hardbricked Yuphoria (lettuce) using an external SD card

Read before continue:
http://forum.xda-developers.com/showthread.php?t=1914359
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=3303112
DrGit said:
As I understand it, this only works because the Snapdragon boot ROM (NOT the bootloader, which resides on the eMMC - this is part of the CPU) has a fallback mode which reads the bootloader from an SD card if the eMMC fails.
Click to expand...
Click to collapse
ᴿℓᴚ said:
Check the references below about MSM8960 boot architecture. PBL (Primary Bootloader) Error Handler sequence:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Requirements:
A hardbricked Yuphoria/lettuce (YU5010/YU5010A) - when connected with a PC, it should expose itself as QHUSB_BULK (when no driver is installed)/Qualcomm HS-USB QDLoader 9008 (when appropriate driver is installed).
(Optional) A working Yuphoria/lettuce, if you want to create the recovery image yourself.
A microSD card - contrary to the popular belief, you don't need a 16 GB or bigger one. 1 GB is sufficient.
Win32 Disk Imager (Windows) / dd (*nix).
Information regarding the recovery image:
The partition structure of Yuphoria is as follows:
Code:
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 262145 1024 bytes FFFF fsc
3 262146 262161 8.0 KiB FFFF ssd
4 262162 263185 512.0 KiB FFFF sbl1
5 263186 264209 512.0 KiB 0700 sbl1bak
6 264210 265233 512.0 KiB FFFF rpm
7 265234 266257 512.0 KiB 0700 rpmbak
8 266258 267281 512.0 KiB FFFF tz
9 267282 268305 512.0 KiB 0700 tzbak
10 268306 269329 512.0 KiB FFFF hyp
11 269330 270353 512.0 KiB 0700 hypbak
12 270354 273425 1.5 MiB FFFF modemst1
13 273426 276497 1.5 MiB FFFF modemst2
14 276498 296977 10.0 MiB FFFF splash
15 393216 393279 32.0 KiB FFFF DDR
16 393280 396351 1.5 MiB FFFF fsg
17 396352 396383 16.0 KiB FFFF sec
18 396384 398431 1024.0 KiB FFFF aboot
19 398432 400479 1024.0 KiB 0700 abootbak
20 400480 466015 32.0 MiB FFFF boot
21 466016 531551 32.0 MiB FFFF recovery
22 531552 4725855 2.0 GiB FFFF system
23 4849664 4980735 64.0 MiB FFFF cache
24 4980736 5046271 32.0 MiB FFFF persist
25 5046272 5048319 1024.0 KiB FFFF misc
26 5048320 5049343 512.0 KiB FFFF keystore
27 5049344 5050367 512.0 KiB FFFF config
28 5050368 30785502 12.3 GiB FFFF userdata
From the above table, its evident that dumping the first 200 MB should be enough to include all required partitions, but you can opt for a full dump as well.
To dump, we can use any of the following methods:
Directly to the PC using ADB.
Be rooted, connect to adb shell with root privilege & call dd to dump it in external sdcard.
Without being rooted but on unlocked bootloader, boot to (tethered booted/permanently flashed) TWRP, get shell access in TWRP or via adb shell, call dd to dump it in external sdcard.
For dumping the whole eMMC, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=30535646
For dumping first 200 MB, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=409600
You can directly write to the external sdcard as well:
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
Pre-created eMMC dump:
eMMC backup - Google Drive
drive.google.com
It is created from a bootloader unlocked Yuphoria running cm-12.1-YOG4PAS47N build.
The size of the whole dump is ~14.5 GB.
After compression, the size is ~998 MB. Its compressed using 7-Zip & split into 10 parts.
File hashes (SHA-1) are as follows:
Code:
9ce4d504395e1c64fbb6960c781fc537eb6b04a2 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.001
523287e0c3fb85c5c2ca1004a1b8219585845462 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.002
ad88026b7b723adf2591b622ebdb3051220c69d8 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.003
b0c6396ddae119d85c9135a6ff4e3cf122e5823e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.004
c88b13065babcb7792fd66b877af5f2f4811f710 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.005
bbf88b156bd67d79bd3da64a1b9273d92c1487ee *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.006
99c2be608f8c359caabcd13889828ea1777dde73 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.007
e60acbafd6326d4d000a81128f8195ad0c14342e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.008
895d7db6e961e56ce5c9e541adddfb72815f44c5 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.009
6267aac32bedcff93f4b873a5bce749b85d0ba09 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.010
0c7639808db3480dd06246e952f1f0d363edf6ba *cm-12.1-YOG4PAS47N-lettuce-eMMC.img
Usage:
Download the eMMC dump created by me or make it yourself.
Use Win32 Disk Imager (Windows) / dd (*nix) to write in a microSD card. I've used a 16 GB Class 10 one.
Insert the sdcard into the hardbricked Yuphoria, insert the battery, press Volume Up key & connect it with PC. It should expose itself as a bootloader/fastboot interface.
Flash official Cyanogen OS - you may need to omit the bootloader unlock/re-lock part.
Profit!
Note:
Try at your own risk! If you've any doubt, please contact with the nearest YU service center & ask them for a replacement.
Credit goes to the countless number of people, who risked their devices to find a working method to unbrick it (especially the girlfriend of my friend, who was forced to lend her device for the experiment).
The process is known to many persons out there - earlier I advised some of the Yureka users to try it out, but didn't get any further feedback. Credit goes to @Jimmyz0r for testing the hypothesis on Yureka on his own.
Please provide detailed feedback regarding your success/failure story, so that this tutorial can be enhanced more.

Reserved for future v1.

Reserved for future v2.

@Titokhan,
I tried using first 100MB dump before using full eMMC dump from Yureka but unfortunately I was unable to boot into fastboot, didn't tried 200MB though. I might make one 200MB dump and try it when I get enough time to brick and unbrick my device again.
PS: thanks for the credit m8

Thank You man For the nice Post I just got my phone back , I sucessfully restore my phone from Hell. It was complete Dead , Showing only qualcomm 9008 mode . I followed ur steps And My mobile is working again ... WAITED 4 mOnths for this Post I though i have to put my phone is trash , But it is working now

After Flashing Phone Nothing Boot Up
After follow your steps and download your EMMC data in 16GB 10class SD Card phone is able to connect with pc in fastboot mode and after i download the firmware and flash this with fastboot on my phone it is not booting up ..when i connect my phone to my it nothing show up any..please send me instrucations what can i do for my phone :crying::crying::crying::crying:

@lakhwinderlucky
1. How did you brick the device?
2. Which was original OS - Cyanogen OS or stock Android?
3. Is there any error while flashing via fastboot?

first my phone start restarting automattically and i thought that
there is any problem in firmware and i download the YU Yuphoria firmware and when i flash the downloaded package the phone become completely dead....now i put my phone in trash and crack it with aa big hammer..now i never purchase aa Yu Phone its all bull ****...without any major reason the phone was unexpetdly dead ...and service center is very poor and they refuse for the replacement in the warranty..anyway now i am free to that phone...:laugh::laugh:

Just one question. Does it matters if bootloader is locked or unlocked ? I have a dead Yuphoria with locked bootloader so just want to make sure before trying this revival guide.

Ruvy said:
Just one question. Does it matters if bootloader is locked or unlocked ? I have a dead Yuphoria with locked bootloader so just want to make sure before trying this revival guide.
Click to expand...
Click to collapse
Shouldn't be a problem - please post your feedback.

I have my friend's Yuphoria, due to some problem, I was asked to re-flash the stock rom, I tried to do the same. At that time it was in working condition, successfully entered the fastboot mode, flashed he file, while flashig I saw some message asking me "" volume up to Continue"" or
"" volume down to Cancel"" .. I don't remember the HEAD of the message, and also I don't remember which button I pressed (vol up or vol down). But the phone got bricked and it was never ON back. Now I nneed to try out your procedure.
My doubt is, are all the 3 procedures required to be done to dump the emmc ? If I have a 16GB memory card with class 4, is it OK ?

Rajatmohod said:
Thank You man For the nice Post I just got my phone back , I sucessfully restore my phone from Hell. It was complete Dead , Showing only qualcomm 9008 mode . I followed ur steps And My mobile is working again ... WAITED 4 mOnths for this Post I though i have to put my phone is trash , But it is working now , If anybody has difficulty to restore this phone , Pls Dont bother to call me .. I will help you to Get back your Phone My cell no. is +919975235086
Click to expand...
Click to collapse
Hi bro,
I am trying to reach you on your mobile but you are not picking up the phone. I have downloaded all the 10 zip filrs, made an image file and tried to write to the micro SD card of 16 GB class 10. But I saw about 67 files in my 16gb memory card and can't find the 25+ files as mentioned in the original post. Please guide me...
Sent from my YU5010 using XDA-Developers mobile app

Titokhan said:
Read before continue:
http://forum.xda-developers.com/showthread.php?t=1914359
http://forum.xda-developers.com/showthread.php?t=2136738
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?t=3303112
Requirements:
A hardbricked Yuphoria/lettuce (YU5010/YU5010A) - when connected with a PC, it should expose itself as QHUSB_BULK (when no driver is installed)/Qualcomm HS-USB QDLoader 9008 (when appropriate driver is installed).
(Optional) A working Yuphoria/lettuce, if you want to create the recovery image yourself.
A microSD card - contrary to the popular belief, you don't need a 16 GB or bigger one. 1 GB is sufficient.
Win32 Disk Imager (Windows) / dd (*nix).
Information regarding the recovery image:
The partition structure of Yuphoria is as follows:
Code:
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 262145 1024 bytes FFFF fsc
3 262146 262161 8.0 KiB FFFF ssd
4 262162 263185 512.0 KiB FFFF sbl1
5 263186 264209 512.0 KiB 0700 sbl1bak
6 264210 265233 512.0 KiB FFFF rpm
7 265234 266257 512.0 KiB 0700 rpmbak
8 266258 267281 512.0 KiB FFFF tz
9 267282 268305 512.0 KiB 0700 tzbak
10 268306 269329 512.0 KiB FFFF hyp
11 269330 270353 512.0 KiB 0700 hypbak
12 270354 273425 1.5 MiB FFFF modemst1
13 273426 276497 1.5 MiB FFFF modemst2
14 276498 296977 10.0 MiB FFFF splash
15 393216 393279 32.0 KiB FFFF DDR
16 393280 396351 1.5 MiB FFFF fsg
17 396352 396383 16.0 KiB FFFF sec
18 396384 398431 1024.0 KiB FFFF aboot
19 398432 400479 1024.0 KiB 0700 abootbak
20 400480 466015 32.0 MiB FFFF boot
21 466016 531551 32.0 MiB FFFF recovery
22 531552 4725855 2.0 GiB FFFF system
23 4849664 4980735 64.0 MiB FFFF cache
24 4980736 5046271 32.0 MiB FFFF persist
25 5046272 5048319 1024.0 KiB FFFF misc
26 5048320 5049343 512.0 KiB FFFF keystore
27 5049344 5050367 512.0 KiB FFFF config
28 5050368 30785502 12.3 GiB FFFF userdata
From the above table, its evident that dumping the first 200 MB should be enough to include all required partitions, but you can opt for a full dump as well.
To dump, we can use any of the following methods:
Directly to the PC using ADB.
Be rooted, connect to adb shell with root privilege & call dd to dump it in external sdcard.
Without being rooted but on unlocked bootloader, boot to (tethered booted/permanently flashed) TWRP, get shell access in TWRP or via adb shell, call dd to dump it in external sdcard.
For dumping the whole eMMC, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=512 count=30535646
For dumping first 200 MB, use:
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/backup.img bs=1M count=200
You can directly write to the external sdcard as well:
Code:
dd if=/dev/block/mmcblk0 of=of=/dev/block/mmcblk1 bs=1M count=200
Be very careful working with dd! mmcblk0 is the eMMC and mmcblk1 is the external SD card.
Pre-created eMMC dump:
https://drive.google.com/folderview?id=0B9zZIJPXbMsuaGg2SXFHcW5mbzQ&usp=sharing
It is created from a bootloader unlocked Yuphoria running cm-12.1-YOG4PAS47N build.
The size of the whole dump is ~14.5 GB.
After compression, the size is ~998 MB. Its compressed using 7-Zip & split into 10 parts.
File hashes (SHA-1) are as follows:
Code:
9ce4d504395e1c64fbb6960c781fc537eb6b04a2 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.001
523287e0c3fb85c5c2ca1004a1b8219585845462 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.002
ad88026b7b723adf2591b622ebdb3051220c69d8 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.003
b0c6396ddae119d85c9135a6ff4e3cf122e5823e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.004
c88b13065babcb7792fd66b877af5f2f4811f710 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.005
bbf88b156bd67d79bd3da64a1b9273d92c1487ee *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.006
99c2be608f8c359caabcd13889828ea1777dde73 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.007
e60acbafd6326d4d000a81128f8195ad0c14342e *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.008
895d7db6e961e56ce5c9e541adddfb72815f44c5 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.009
6267aac32bedcff93f4b873a5bce749b85d0ba09 *cm-12.1-YOG4PAS47N-lettuce-eMMC.7z.010
0c7639808db3480dd06246e952f1f0d363edf6ba *cm-12.1-YOG4PAS47N-lettuce-eMMC.img
Usage:
Download the eMMC dump created by me or make it yourself.
Use Win32 Disk Imager (Windows) / dd (*nix) to write in a microSD card. I've used a 16 GB Class 10 one.
Insert the sdcard into the hardbricked Yuphoria, insert the battery, press Volume Up key & connect it with PC. It should expose itself as a bootloader/fastboot interface.
Flash official Cyanogen OS - you may need to omit the bootloader unlock/re-lock part.
Profit!
Note:
Try at your own risk! If you've any doubt, please contact with the nearest YU service center & ask them for a replacement.
Credit goes to the countless number of people, who risked their devices to find a working method to unbrick it (especially the girlfriend of my friend, who was forced to lend her device for the experiment).
The process is known to many persons out there - earlier I advised some of the Yureka users to try it out, but didn't get any further feedback. Credit goes to @Jimmyz0r for testing the hypothesis on Yureka on his own.
Please provide detailed feedback regarding your success/failure story, so that this tutorial can be ehanced more.
Click to expand...
Click to collapse
Dear Mr Titokhan,
I have done the same exercise as was mentioned in post #1 of thsi thread, but nothing has happened. Let me come with my exercise..
* I have downloaded all the 10 files from google drive and made it 1 image file with 7Z
* I have downloaded win32 disk imager and wrote the image to a Samsung 16 GB Class 10 with 48/mbps Memory card
* Inserted this card into the bricked device and pressed volume up and connected the cable to PC for flashing. But nothing came up.
* Tried vol+ and Power button retaining the MC in the device - no use.
* When tried to see the contents of memory card that was written the image file, I could not see anything except 63 mb of free data. (
* When entered the Disk Management I could see number of partitions without any names.
* I have tried with the ROM files, cm-12.1-YOG4PAS47N-lettuce-signed-fastboot-5d674b9b61 and cm-12.0-YNG1TBS2P2-lettuce-signed-fastboot but no use.
I have my friend's Yuphoria, due to some problem, I was asked to re-flash the stock rom, I tried to do the same. At that time it was in working condition, successfully entered the fastboot mode, flashed he file, while flashig I saw some message asking me "" volume up to Continue"" or
"" volume down to Cancel"" .. I don't remember the HEAD of the message, and also I don't remember which button I pressed (vol up or vol down). But the phone got bricked and it was never ON back. Now I need your help.
Note: I have 1 more YU5010 with me and presently using that. Since if it is useful for any type of backup of stock rom, I am just telling you in advance. Please help me with step by step procedure.

@vsrkmurthy
1. Please don't quote the whole first post.
2. Have you matched the hash of the eMMC image after extracting?
3. Windows can't see multi-partitioned removable media; it only shows the first readable partition.
4. After inserting the sdcard, pressing volume up & connecting the device with PC please send me the screenshot of Device Manger.

Titokhan said:
@vsrkmurthy
1. Please don't quote the whole first post.
2. Have you matched the hash of the eMMC image after extracting?
3. Windows can't see multi-partitioned removable media; it only shows the first readable partition.
4. After inserting the sdcard, pressing volume up & connecting the device with PC please send me the screenshot of Device Manger.
Click to expand...
Click to collapse
Thanks for the reply, If you can give me your whatsapp number, I want to send you the screenshots thro' that. Infact, yesterday, Rajat (refer post #5 of this thread) and myself tried a lot by connecting Team Viewer also. But no use. Please give me your contact number so that we can discuss and finalise. else, my number is +919059927728 (whatsapp also).

Bro ; you are a god. Seriously bro ; i went to All shops of NEHRU PLACE; NEW Delhi. They all said ; we can't do it. we(Service centre guys) have to change the motherboard of your YUpHORIA YU5010. and they were asking for ₹3k ;. I literally ordered a new smart phone ; but after reading your post and following each step i got my Yuphoria back. Thank You bro. Hats off to u. Thank You so much bro.

Please give me your contact number
Sent from my 2013023 using XDA-Developers mobile app

eMMc Dump not extracting
Titokhan said:
Shouldn't be a problem - please post your feedback.
Click to expand...
Click to collapse
Hello @Titokhan I have downloaded all the files but they are not extracting i have 16 Gb class 10 samsung card so can you please tell how to only dump necessary files.
Thanks in advance

How did you dump only 100mb?
YuganshT7 said:
Hello @Titokhan I have downloaded all the files but they are not extracting i have 16 Gb class 10 samsung card so can you please tell how to only dump necessary files.
Thanks in advance
Click to expand...
Click to collapse
Jimmyz0r said:
@Titokhan,
I tried using first 100MB dump before using full eMMC dump from Yureka but unfortunately I was unable to boot into fastboot, didn't tried 200MB though. I might make one 200MB dump and try it when I get enough time to brick and unbrick my device again.
PS: thanks for the credit m8
Click to expand...
Click to collapse
Can you tell me how can i Dump only 200mb of eMMc on My SD card . I am on windows

@YuganshT7
Can you please elaborate more? What was the exact error message you got?

GT-P5100 in read only

Hello to all
I am fighting since 2 weeks with a GT-P5100 that seems to be in read only and in boot loop (it shows the CM9 boot animation and then reboot ...). This after a simple update of some apps that seems to have corrupted the sdcard inside ...
I have tried to clear the cache and the user data via the recovery mode, but nothing happen ... (boot in recovery, choose to wipe data/factory reset and wipe cache partition)
To make a long story short:
I am able to boot in recovery and enter as root via adb. Whatever change I do in the filesystem it seems to be done, but when I unmount/mount the fs or reboot I find the same initial situation !
So for example:
a) enter as root, mount /data, delete data content via rm -rf /data/* ... then if I do ls -la /data I see the device empty ... if I unount /data and then mount /data .. all the files are there !!!! :-O
b) enter as root and activate parted ... remove the data partition (for me n. 10) and quit. Run parted again and the partition is still there :-O
c) enter as root and touch a file in any filesystem ... when I ls after I can see the file ... as soon as I reboot, not such file is there
I have tried with ODIN and HEIMDAL (booting in download mode or fastboot mode) also to flash new system.img from stock roms and different recovery.img (currently I have CWM-based recovery v6.0.1.0)... no way. system.img flash does not work, while recovery.img flash say ok, but when I reboot in recovery mode still find always the same partition :-O
It seems somehow that the overall internal disk is in read only and - I do not understand why - when I do changes they are recorded locally, but when I reboot the fs really does not store anything.
BTW, this is my partition table
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 15.2GB 12.9GB ext4 DATAFS
11 15.2GB 15.8GB 537MB ext4 HIDDEN
Any idea ?

ZP980 unbrick/study of partition table

Hi to all, I hope to be posting in the right section...otherwise...punish me plz
It's a long story, so i hope that someone has time and want to put some effort to help me understand what i'm doing wrong.
By the way i work in IT field and have some knowledge about linux (let's say 5 on 10) but not so many on how android really works, but i'm confortable with custom recovery and roms, i'm still using an s4 mini (GT-I9195) with mine android 9 custom rom and i'm super happy with it.
Now that presentation are done , here is the matter.
I've found an old zp980 32GB (NOT the "plus one") that some years ago i've rooted it flashed with recovery and custom rom. all was working, but at some point i started playing with fdisk and parted and i messed up things.
Honestly i don't remember what exactly i was doing, but now the status of the phone is:
System not booting
I can enter into Recovery (custom TWRP by dezmen3 v2.4.4.0)
I can connect to adb into recovery
I cannot flash rom trough recovery due the actual system partition (589 MB)
I cannot flash the original rom trough SP flash tool due "SFT enable dram failed (4032)" error
The partitions actually are (what i can see from recovery):
System (589 MB)
Data (54MB)
Boot (6 MB)
Recovery (6MB)
Cache (4 MB)
uboot(0 MB)
nvram (5 MB)
Free space: 27412 MB
Actually, I've tried to reformat the memory using SP flah tool, but i got the same error "SFT enable dram failed (4032)", all drivers are ok, i can see COM port in deivce manager tried win 10 and even win 7.
SP tool ver. used v5 1720 more updated version tells me that the brick i'm tringo to flash in not supported anymore xD
Here a dump of fdisk -ul /dev/block/mmcblk0 from adb shell
Bash:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 1022 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 26624 47103 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 47104 67583 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 93184 105471 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 134144 1465343 665600 83 Linux
/dev/block/mmcblk0p6 4869120 1022 2145049599+ 83 Linux
if i make a print from parted (pushed with adb) I get:
Error: Can't have a partition outside the disk!
Before i was also having an error saying that there was an extended partition into a logical one (don't ask me how I do it), but i removed it
So, now....what to to to rescue this device?
by the way honestly except for the instinct of "recover things that doesn't work" my main purpose is understand:
What I've messed on the partitions
Why sp flash tool can't reformat/flash the memory (i haven't tried to manually modify it again)

no brave person hat want to help me to brick it in a bad way?
EDIT NEW INFO
i've understtod that the problem was caused by
/dev/block/mmcblk0p1
and
/dev/block/mmcblk0p6
start and end were inverted , them were overflowing.
Now i used fdisk to remove part 1 (the extended), so i've lost also 5 and 6 (system and cache) and i have recreated them using 1 GB for each and using correct sector order.
now SD and try to flash a ....random compatible rom....see u later for info.
Cross your finger for me xD

flash failed it cant mount system and emmc.....
and now
~ # cat /etc/fstab
/cache ext4 rw
/data ext4 rw
/emmc vfat rw
/system ext4 rw
/sdcard vfat rw
/sd-ext auto rw

if someone has a zp980/c2 working can please post me the result of
cat /etc/fstab
from adb shell??
and a fdisk -ul?

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