Develop Bugs

[Q] please help - did i brick my phone using exploid method

I followed the “how to root the HTC My touch slide (exploid method) (updated 01.26.11)” to the letter. (theunlokr.com)
Everything worked well until I got into clockworkmod Recovery
I then wipe data/factory reset in recovery mode
Then I installed zip from sd card ( I select slidemeroot2.zip)
After going through the process I get an “installation aborted” message
E: Failure at line 64 symlink busybox SYSTEM:xbin/zcip
(something to that effect. I'm out of town til tomorrow to verify the exact error)
Im very frustrated and afraid I may have bricked the phone
I had to turn the phone off and am scared of turning it back on until I have a fix
Please help

can you get into clockwork recovery???yes you tried to flash the wrong file

xoombie503 said:
can you get into clockwork recovery???yes you tried to flash the wrong file
Click to expand...
Click to collapse
Yeah i believe so.
After removing the battery last night i was able to get back into recovery i think
Will double check tomorrow when i get back home
What do you have in mind and how do i know the correct file to flash?
I'm just scared because it said during the method a few steps earlier: DO NOT REBOOT
I hope that i had past the stage where by rebooting it wont kill the phone

get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works

xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
Thnks so much will do that first thing when i get back in town tomorrow..
By the way this is with the assumption that by plugging my phone onto my computer via usb it will recognize my phone as a drive correct??
o btw im a newby at this, so that i understand correctly, i need to once in recovery cache wipe, then data factory reset before flashing the new room i would download. What is Dalvik cache etc..... is that another option i will see once in recovery?

xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting

pvalery00 said:
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting
Click to expand...
Click to collapse
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock

guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
interresting because the first part of this message is
"no app2sd partition found. Skipping format of /sd-ext.
data wipe complete"
I wonder if this has anything to do with it...
Please let me know

guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?

pvalery00 said:
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?
Click to expand...
Click to collapse
There is a thread in the dev section on how to setup custom mtd partitions. Basically you just assign memory where you want it. If you want stock roms you should assign the normal mtd setup (given in mtd partitions thread). Oh, you'll need s-off though. There is a guide for that too in the dev section. Its actually sticked at the top. Glad i could help
Sent from my T-Mobile myTouch 3G Slide using XDA App

[Q] Can't mount /data

I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?

install a stock rom then re-install cwm 5.0.2.7

Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.

Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.

Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?

Factory reset?
Have you tried doing a factory reset with Kies?

be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...

I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?

Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado

Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$

What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.

Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!

Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.

Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?

That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.

What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?

Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?

I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs

[Q] Ext partition error. Unable to wipe data, install zips and restore backups

Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.

Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2

drixjp said:
Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.
Click to expand...
Click to collapse
Wrong section. Questions don't belong in the General Section. As for your problem, the best solution would be to just flash a stock ftf as mentioned by m1st3r1

m1st3r1 said:
Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app

drixjp said:
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot

m1st3r1 said:
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot
Click to expand...
Click to collapse
Like i said, it's a. 55 rooted with stock Rom. Boot loader unlock alowed: yes. I tryed every kind of fix in cwm already and nothing works.
Something I never tryed is via fastboot. How do I proceed with that?
Sorry, my android life just started yesterday, I don't have much knowledge
EDIT: Ok I solved. Actually it's not like a fix, it's just like putting a silver tape to handle the problem. For some reason I'm able to advance restore system backup via CWM recovery. Every time that I do that, my CWM recovery is fully functional again, i can install mod, rom, etc. But, when I reboot into system again, the problem comes back, but I can still use my android without any problems, I just can't install anything via CWM recovery. So basically, now, every time that I want to install something in recovery, first I need to advanced restore system, and than install the rom, mod or whatever. Than I backup again in case I want to install anything else in the future, to repeat the same procedure with the last backup.
I was just having some problems when I was trying to restore the system with a md5 missing error... something like that. I solved this problem by just creating a file.txt in the backup folder and than renamed it to nandroid.md5. Magically it was fixed.
Sent from my LT26ii using xda app-developers app

Accidentally formatted '/System' in CWM

So I'm not panicking as I know this is most likely recoverable, but I do want to make sure I do this right. I was prepping my galaxy nexus to give to my wife since I got a note 2 and was consequently trying to get it completely wiped. I was trying to clear all the user data and was surprised that it was clearing (I think it was because it's is stored in the /sdcard directory). So, I popped into the mounts and storage section and started formatting . Seriously, I'm not sure what I was thinking here. I only got to the /sdcard and /system before I stopped and reconsidered, but it was too late. Because I had already formatted the /sdcard, I lost my rom and gapps zips.
Anyway, I think all I need to do is hop into adb, transfer the necessary zips to my /sdcard directory, and flash them. Is that correct? Also, of the options on there, what can I format without issue? /system is obviously for the rom itself (or at least mostly), so I'll avoid that in the future. What is the /data and /cache used for?

Yes you are correct about your process. I even there myself about five times now not knowing what I was thinking when I pressed all those buttons hah.
Data is used by android for app caches and the cache is for system and kernel caches. May not be entirely correct but they are safe to clear

Poke_N_PDA said:
So I'm not panicking as I know this is most likely recoverable, but I do want to make sure I do this right. I was prepping my galaxy nexus to give to my wife since I got a note 2 and was consequently trying to get it completely wiped. I was trying to clear all the user data and was surprised that it was clearing (I think it was because it's is stored in the /sdcard directory). So, I popped into the mounts and storage section and started formatting . Seriously, I'm not sure what I was thinking here. I only got to the /sdcard and /system before I stopped and reconsidered, but it was too late. Because I had already formatted the /sdcard, I lost my rom and gapps zips.
Anyway, I think all I need to do is hop into adb, transfer the necessary zips to my /sdcard directory, and flash them. Is that correct? Also, of the options on there, what can I format without issue? /system is obviously for the rom itself (or at least mostly), so I'll avoid that in the future. What is the /data and /cache used for?
Click to expand...
Click to collapse
I actually was trying to format everything to get the GN as clean as possible and ended up deleting everything including my rom that I was going to install(CM10.1). Thankfully recovery was still on there and I just pushed my rom and gapps using adb. I couldn't get the sideload command to work using clockwork so ended up just using the push commands. Make sure to specify the destination folder on your phone with the file name it will be on your phone. I ran around in circles realizing I wasn't specifying the file name in the folder location. Good luck!

[Q] how to upgrade to 4.4 from 4.3 a and backup TA

What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?

theperson333 said:
What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?
Click to expand...
Click to collapse
Also, What is your recommended method of unlocking the bootloader and why?
Please post any answers in a separate thread and link to it, so it can be made a sticky.

I am not responsible if anything goes wrong.
Go to http://xperiafirmware.com/8-firmware/40-sony-xperia-m-c1905, and follow the steps under "Upgrade to latest 4.1.2". This works on locked bootloaders too, and it even works if it is a downgrade, not upgrade.
Stock 4.1.2 is rootable with Framaroot's Gandalf exploit (search for it on XDA), root it. Then you can back up the TA partition, either with the flashtool you have downloaded earlier, or in some manual way. Make absolutely sure it went well before proceeding! I think you have read plenty of warnings if you have asked this question.
Then proceed as usual. Go ask Sony for an unlock key, unlock your phone with fastboot. Download the 4.4 ROM you wish to use, then flash the boot.img of it by
Code:
fastboot flash boot boot.img
. Then boot the phone into recovery mode using
Code:
fastboot reboot
and when it begins to boot, bash the volume up key a few times. Then install your new ROM from recovery.
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Also, this is from experience, I have a C1905, which I prior upgraded with SEUS to 4.3. The procedure I wrote worked on it nevertheless.
Another thing that happened to me is that in the process my /data partition got corrupted. The "internal sdcard" lives at /data/media, and recoveries want to preserve this folder, so when they can't mount it and rescue files from it, they skip it, and the new ROM won't boot because it can't mount the /data partition either. So if you get a bootloop after installing the new ROM, try formatting /data AND the internal storage, there's an option in the recovery to do this.

When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app

theperson333 said:
When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.

thermate said:
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.
Click to expand...
Click to collapse
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?

theperson333 said:
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?
Click to expand...
Click to collapse
As far as I know, flashtool is just a GUI over fastboot when it comes to unlocking the bootloader, so it does exactly the same thing you would do with fastboot. It makes no difference.
What do you mean by "recreating partition with ADB"?

Are there any adb tools or shell tools accessible from adb to recreate partitions?
Sent from my C1905 using XDA Free mobile app