Slow performance after flashing cm/formatting userdata. - Sony Xperia M

Hey ,I unlocked xperia m(backed up TA partion) ,I was in a bootloop after that(boot animation) ,then I got to know sony doesn't include stock recovery(so no wipe cache and userdata) ,I quicklly used fastboot instead(fastboot -w) ,it couldn't format userdata and refused to do anything with cache.(the bootanimation bootloop was still there) Then I installed twrp recovery in boot[FOTAKernel can be flashed from fastboot ,which I didn't knew] ,checked /data partion(size: 0MB) and choosed repair/format to ext4 ,it failed so I formatted userdata using terminal. I backed up stock /system ,and flashed cwm+stock kernel and it didn't get pass sony logo ,I then installed twrp+cm12 kernel ,installed cm 12.1 ,and then flashed FOTAKernel twrp. Phone works almost fine ,through now 2d game performance is really choppy(xbox one choppy -sometimes hits 0fps).
The command I used to format /data was "mke2fs -t ext4 -v /dev/block/platform/msm_sdcc.1/by-name/userdata"

Related

[Q] What is wrong with my data partition?

Hello,
I have a HTC wildfire phone. Recently it got stuck in booting screen. I have tried clearing the data (hard factory reset) but no success.
Finally started rooting my mobile. So the core intention is to make the phone in working condition.
I have tried so many ways, referred so many website - have crossed many obstacles but still no success.
Finally there is only one issue which i couldn't solve
Here is my problem:
I couldn't clear/wipe my data partition. It always shows the used memory more than 96%.
When i went to see what is there in my data partition, nothing is there..
Code:
adb shell df -h
shows
Filesystem Size Used Available Use% Mounted on
tmpfs 156.9M 0 156.9M 0% /dev
/dev/block/mtdblock4 40.0M 1.3M 38.7M 3% /cache
/dev/block/mtdblock5 175.1M 167.4M 7.7M 96% /data
and
Code:
/data # du -h
shows
2.0K ./lost+found
4.0k .
My mobile details:
Buzz PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
TOUCH PANEL-SYN3KY_01
RADIO-3.35.20.10
Custom recovery: ClockworkMod Recovery v2.5.01
and I am trying to put cyanogenmod (update-cm-7.1.0.1-buzz-signed)
Custom MTD is not working in my phone as it is not S-off.
All i need is to make my phone working. But installing cyanogenmod is not helping as the data partition is full.
Please anyone help me..
Thanks in advance!!
Try to reinstall clockworkmod recovery and then try to wipe data/factory reset cache,and if you want to install cyanogen 7 you need to root your phone.
It seems you have unlocked your bootloader using HTC Dev? If that is so, try using fastboot to format your /data partition. Then try the entire process of flashing the ROM again.
The command is fastboot erase <partition name>, so here it will be fastboot erase data
ZoRaN85 said:
Try to reinstall clockworkmod recovery and then try to wipe data/factory reset cache,and if you want to install cyanogen 7 you need to root your phone.
Click to expand...
Click to collapse
I have tried reinstalling clockworkmod recovery and have wiped data and cache partition. Still unable to fully wipe data. (still the usage is 96%)
3xeno said:
It seems you have unlocked your bootloader using HTC Dev? If that is so, try using fastboot to format your /data partition. Then try the entire process of flashing the ROM again.
The command is fastboot erase <partition name>, so here it will be fastboot erase data
Click to expand...
Click to collapse
Yes.. But unable to wipe data partition through fastboot. It says "remote: not allowed"
Please help! Thanks in advance!
Please help me.. I am unable to wipe my data partition something went wrong!

[Q] After restart doesnt start

Hi,
About a month I used rom AR and I was aware of her faults (which yesterday revealed that it is not true), that when I restart, phone must be connected to the pc, and start bootloader via fastboot and the Command Promt flash boot.img dissected from ROM. Fortunately ROM, stable, so I followed all the time does not restart.
Yesterday I got a taste for change (and I wanted to get rid of the problem) and I downladed at first 4.4 ROM from xda taktik then 4.3JB and finally cyangen mod 7.2 Problem unfortunately stayed at all the same. When restarting HTC logo flashes and then turns off the display and starts "black" will flash this is over, unless we do the above procedure via the bootloader.
Does anyone an idea how to fix it?
Thnx
Have you format system + data + cache in mount and storage after wipe data cache and dalvik cache? Try this, if not success I think the only way is download the latest ruu and run it. You will be go back to stock. And we can use tools to root and flash custom recovery.
Sent from my Desire HD using Tapatalk
@Pilsner12 what the state of your phone bootloader..?, is that just unlocked with s-on..?, or already s-off..?, and what a custom recovery you used..?
if your phone is just unlocked with still s-on...did you already flashing a boot.img from the rom.zip that you already installed..?
to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?
Pilsner12 said:
to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?
Click to expand...
Click to collapse
so...you mean that you've already/ always flashing boot.img from the rom.zip itself after installing the rom from recovery...and that's mean your phone already can booting normally..right...?, so where's the problem exactly..?
anyway..if the problem you asked is...why you must always do a flashing boot.img manually after installing any new custom rom to boot normally is bacause you're still had s-on flag on your bootloader..that's why bootloader can't give permission to a custom recovery for flashing boot partition..
if you wanna running RUU...then you should be relocked your bootloader first..and that's mean your will return to the stock..so to rooting it again...you must unlocking your bootloader again..
Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..
Pilsner12 said:
Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..
Click to expand...
Click to collapse
maybe you can try it to installing and using a different custom recovery..like 4ext or twrp..
I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..
Pilsner12 said:
I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..
Click to expand...
Click to collapse
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..
JJeamy said:
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..
Click to expand...
Click to collapse
could you please post link, where is .zip file. I found only programs on market or .apk..
Are you booting the boot.img or flashing it? Also, recoveries are not zips, they are imgs.
Pilsner12 said:
could you please post link, where is .zip file. I found only programs on market or .apk..
Click to expand...
Click to collapse
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"
JJeamy said:
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"
Click to expand...
Click to collapse
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Starting recovery on Thu Feb 20 20:57:47 2014
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
7 /system_lib ext3 /dev/block/mmcblk0p28 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
Preparing boot.. 2I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Sat Nov 10 16:53:16 CET 2012
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=SH18KRX02893
ro.baseband=26.14.04.28_M
ro.carrier=HTC-GER
ro.bootloader=2.00.0029
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.8.0"
ext.feature.version_check=yes
ext.build=0
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Backups: include lib: enabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 24h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Irocessing 4EXT Control file...
4EXT Recovery Updater v2.4.6b
Processing..
Mounting sdcard..
I:Backup path: /sdcard/clockworkmod/backup/2014-02-20-00.05.02_CyanogenMod7.2.0ace
I:Backup mode: custom
Calculating space needed..
Space needed to complete: 654 MiB
Free space on your sdcard: 8264 MiB
Backing up boot image...
Including /system/lib
Backing up system_lib...
backup mode: tar
Backing up system...
Writing 4EXT info for filesystem ext4
Backing up data...
Writing 4EXT info for filesystem ext3
Backing up .android_secure...
Backing up cache...
Writing 4EXT info for filesystem ext3
Generating md5 sums...
tar: removing leading '/' from member names
-- Installing: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Finding update package...
I:Update location: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Opening update package...
Installing update...
Installation aborted.
Critical error! Installation aborted!
Canceling pending actions and booting UI
Pilsner12 said:
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Click to expand...
Click to collapse
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?
JJeamy said:
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?
Click to expand...
Click to collapse
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.
Pilsner12 said:
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.
Click to expand...
Click to collapse
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..
JJeamy said:
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..
Click to expand...
Click to collapse
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.
Pilsner12 said:
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.
Click to expand...
Click to collapse
So yesterday I ran RUU and now restart bug is fixed. I am happy for it!
But I have respect from rooting process. Last time it takes me a lot of weeks..
Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD
Bacchione said:
Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD
Click to expand...
Click to collapse
Please help me

[Q] TWRP Error "E:unable to mount data"

Current Problems:
E:unable to mount storage
E:unable to mount data
Stuck at fastboot oem format
The Story:
I factory reset my Xperia M, then I unlocked Bootloader and also flashed TWRP through FastBoot. After that I flashed "Lollipop 5.1 Cyanogenmod 12.1 Official Nightly Build 20150630" through External Memory Card (TWRP). I rebooted my phone, it was stuck on Sony logo for sometime then it again rebooted itself and TWRP was gone and Cyanogenmod's recovery was there. I again flashed TWRP and tried other ROM but then also the same thing happened. So I again flashed TWRP through FastBoot. I searched and tried the following command in Terminal TWRP:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
But I didn't know which folder to select so I selected the directory which was showing all folders, but it said "not enough space to build proposed file system.................". No matter which folder I selected it always showed that error.
Currently I am using the following command through FastBoot:
Code:
fastboot oem format
and it's been stuck there for 1 hour showing 3 dots. Is it working, does it take hours to format?
P.S.: I also tried ADB sideload but the same thing happened - it rebooted and I got Cyanogen Recovery and then again I flashed TWRP.
Please help!!!!!!!!!!!!!!!!!!!!!!!!!

I messed up the /data partition. "Partition table doesn't exist".

Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.
Nixtren said:
Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.
Click to expand...
Click to collapse
try to flash miui v5 or v6 rom via fastboot
unkown rockstar said:
try to flash miui v5 or v6 rom via fastboot
Click to expand...
Click to collapse
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?
Nixtren said:
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?
Click to expand...
Click to collapse
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.
unkown rockstar said:
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.
Click to expand...
Click to collapse
It worked! Thanks, I didn't know there was a separate ROM for fastboot.
Nixtren said:
It worked! Thanks, I didn't know there was a separate ROM for fastboot.
Click to expand...
Click to collapse
glad to know it worked..now follow all steps correctly

[solved] TWRP - could not mount /data and unable to find crypto footer

Hi,
Nice to be here after so much years of reading !
My LG G3s (d722) was fine with Cyanogenmod 13 and encryption enabled. I've made a Titanium backup for my apps (& cie...) on the SD card, and reboot in TWRP 3.0.2-0, enter my password to mount storage, and I've wiped all partitions exept the SD card.
Then I've flashed the CM14 zip file, and get these error in the process :
"could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Unkown error 200 unmount of /data failed; no such volume"
"Failed to mount '/data' (No such device)"
Since then :
- if I reboot into recovery, TWRP doesn't ask me the password to decryp the partition
- if I reboot in CyanogenMod ask me the password, but the tells me :
Decryption unsuccessful
The password you entered is correct but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.​Then it reboot into TWRP
Any ideas ?
How could I mount ext4 partition in TWRP ? Or restore stock recovery ?
Thanks a lot for your advices
resolving !
Hi myself and everyone from another time,
I've resolved this mess by :
- installing LG drivers
- downloading kitkat stock-rom D72210d_00.kdz
- open LG Flash Tool 2014 and load D72210d_00.kdz, and start a CSE Flash
Then stard android 4, root it... etc
Best

Categories

Resources