Flashing First ROM - System Reading as 15 MB !! - Sony Xperia Miro, Tipo (Dual), J, E

Hi everyone,
I have successfully unlocked bootloader and flashed CWM...
now, I have downloaded Xperience CN10 & Gapps Packages to my external sd card.
I have then performed a factory reset in recovery, and formatted System.
After this, I went to flash the ROM .zip from recovery, and it fails staying symlink fails.
When I run "adb shell busybox df -h" to get partition infomation, this is the output:
tmpfs 204.5M 48.0K 204.4M 0% /dev
/dev/block/mmcblk0p12 157.6M 4.3M 153.3M 3% /cache
/dev/block/mmcblk0p17 2.0G 384.0K 2.0G 0% /sdcard
/dev/block/mmcblk1p1 1.8G 1.1G 731.6M 61% /external_sd
/dev/block/mmcblk0p10 15.8M 15.8M 0 100% /system
So why is my system reading as 15.8MB ???

Related

Missing space with new Apps2SD method

I was trying to use the new Apps2SD method by Marcus and I seem to be running into a problem. When I try to remove the unionfs partition through either G-Parted or disk utility I cannot remove/format it.
As far as I'm aware unionfs is NOT supported in G-parted nor in Mac OS. I only have a 1GB FAT32 partition and the other 3GB seem to be lost. I searched the forums and Google but cannot find anything. Does anyone have any suggestions?
im not sure what are you trying to do, but you can repartition removing phone's sd card and plugin it into a computer. If you want to repartition / change partitions with you phone acting as sd card reader connected with usb, you will have to undo unionfs process before trying to repartition / make any changes to sdcard
that last can be acomplished removing /data/init.rc and /data/a2sd.sh and rebooting the phone.
if this doesnt help you, provide more info, like the output of "df" command.
What I'm trying to do is restart Marcus's unionfs Apps2SD by destroying the partitions so I can get a fresh start. I tried deleting the 2 files you told me about but that didn't work. Heres the output of df:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 49356 0 49356 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 92160 60244 31916 65% /system
/dev/block/loop0 492 492 0 100% /system/modules
/dev/block/loop1 3524 3524 0 100% /system/xbin
/dev/block/mtdblock5 91904 23756 68148 26% /data
/dev/block/mtdblock4 30720 1160 29560 4% /cache
/dev/block//vold/179:1
991664 0 991664 0% /sdcard
Thanks!

Error - ROM memory insufficient space

Hi Guys,
I have an Blu Dash 3.5 D170, but i do not have a system android yet... i've got a little problem:
I'm trying to install a backup system.img I got here, but always fails in writing step because the lack of space in /system
when i use adb shell ls -a /system the result is:
Code:
D:\Android\sdk\platform-tools>adb shell
~ # ls -a /system
ls -a /system
. .. lost+found
~ #
other words, there is nothing inside /system...
When i use "busybox df", results is:
Code:
~ # busybox df
busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 80612 48 80564 0% /dev
/dev/block/mtdblock1 225280 148096 77184 66% /system
/dev/block/mtdblock4 179200 1216 177984 1% /data
/dev/block/mmcblk0p1 3850240 118624 3731616 3% /sdcard
/dev/block/mtdblock2 61440 1192 60248 2% /cache
~ #
I can not understand why occupies 66% of the space is has NOTHING within the directory
I tried using the command "fastboot erase system", and the command says that cleared the system, but it does not clear these 66%
what should I do to fix this?

How can i erase block size?

Hi Guys,
I am facing a small problem that will not let me install any Android system on my device.
I have a BLU DASH 3.5 and the problem seems whenever I use the command "busybox df" ... it always returns me:
Code:
~ # busybox df
busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 80612 48 80564 0% /dev
/dev/block/mtdblock1 225280 215936 9344 96% /system
/dev/block/mtdblock4 179200 1152 178048 1% /data
/dev/block/mmcblk0p1 3850240 118560 3731680 3% /sdcard
/dev/block/mtdblock2 61440 1180 60260 2% /cache
My folder /SYSTEM is always full.
I've tried deleting the folder using the "rm" command and it works, the command clears my folder / system, except that when I create the folder again using "mkdir" and remount the partition with the command: "mount -t yaffs2 /dev/block/mtdblock1 /system" the space occupied remains just seen... 96% used.
I tried to:
- delete /system folder
- delete /dev/block/mtdblock1 (also mtdblock2, mtdblock3, mtdblock4, mtdblock5 and mtdblock6) but when devices reboot, everything back as it was before.
- remount in other partition
I dont know what to do
is there any way to clean/wipe/recreate the /system partition?

[Q] Internal SD Card doesn't mount! [i9023]

Hello. Firstly thanks for a helpful forum you guys have made. It has helped me greatly so far.
My SD card doesn't mount.
How it happened:
I installed ClockworkMod Recovery and CyanogenMod 10 (stable).
Upon reboot, I stupidly encrypted the phone.
After that finished, I flashed Marmite kernel (stable), however this slowed down my phone completely.
To revert back, I re-flashed CyanogenMod.
After this reboot, the SD card could not mount.
Info
Parted /dev/block/mmcblk0
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 1612MB 1074MB ext4 userdata
3 1612MB 15.9GB 14.3GB media
In /dev/block the file list is this;
Code:
mmcblk0 (SD Card)
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
This looks like there are perhaps 6 partitions on my SDcard.
In CyanogenMod 10, df command shows;
Code:
Filesystem Size Used
/dev 198.2M 48K
/storage 198.2M OK
/mnt/secure 198.2M OK
/mnt/asec 198.2M OK
/mnt/obb 198.2M OK
/mnt/fuse 198.2M OK
/cache 469.5M 91.5M
/efs 6.8M 5.6M
/system 503.9M 370.3M
/data 1007.9M 145M
Im stuck in how to get this sorted. Every time I got to mount in CWM is states 'Error mounting /sdcard!'
Is it just possible to delete all the partitions in /dev/block for the SDCard?
[solved]
alfanhui said:
Hello. Firstly thanks for a helpful forum you guys have made. It has helped me greatly so far.
My SD card doesn't mount.
How it happened:
I installed ClockworkMod Recovery and CyanogenMod 10 (stable).
Upon reboot, I stupidly encrypted the phone.
After that finished, I flashed Marmite kernel (stable), however this slowed down my phone completely.
To revert back, I re-flashed CyanogenMod.
After this reboot, the SD card could not mount.
Info
Parted /dev/block/mmcblk0
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 1612MB 1074MB ext4 userdata
3 1612MB 15.9GB 14.3GB media
In /dev/block the file list is this;
Code:
mmcblk0 (SD Card)
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
This looks like there are perhaps 6 partitions on my SDcard.
In CyanogenMod 10, df command shows;
Code:
Filesystem Size Used
/dev 198.2M 48K
/storage 198.2M OK
/mnt/secure 198.2M OK
/mnt/asec 198.2M OK
/mnt/obb 198.2M OK
/mnt/fuse 198.2M OK
/cache 469.5M 91.5M
/efs 6.8M 5.6M
/system 503.9M 370.3M
/data 1007.9M 145M
Im stuck in how to get this sorted. Every time I got to mount in CWM is states 'Error mounting /sdcard!'
Is it just possible to delete all the partitions in /dev/block for the SDCard?
Click to expand...
Click to collapse
I have fixed this issue. These are the steps I took;
Download latest factory image; (https://developers.google.com/android/nexus/images)
Boot into bootloader (power and volume up when phone is switched off)
Connect to PC, and make sure you have the fastboot downloaded from android SDK
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
Once the phone has booted into the stock rom, go into Settings; Backup & Reset; Factory Reset
Reboot phone, and the SD card should now be formatted correctly.
(Then reinstall your favorite Custom firmware! )

TWRP cannot mount /data; nothing 'sticking' using fastboot

Hi all,
hoping on the off-chance someone's still monitoring the Nexus 5 forums here
So decided to dust off the old Nexus 5 (now with extra COVID-19 time on my hands!) to use as a backup device, but having serious issues getting it up and running. I had it rooted years ago, and had no issues installing custom roms.
Now I'm having the following situation:
I cannot flash the factory image using fastboot, nor anything is 'sticking' to the phone when I try to re-flash individual component for the factory image. I've also tried to flash TWRP, but again, it doesn't stick and the only way i can boot into TWRP is by using
Code:
fastboot boot recovery.img
.
However in recovery, the data partition is not mounting and all the tutorials/guides I read about fixing it aren't working (e.g. repairing the partition-- get a 'unable to repair data' error; changing from EX4 to EX2 and back-- get 'failed to mount '/data' error).
Ran the following command in the terminal window in TWRP
Code:
cat /etc/fstab
and got the following output:
Code:
/dev/block/mmcblk0p25 /system ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/mmcblk016 /persist ext 4 rw 0 0
/dev/block/mmcblk0p1 /firmware vfat rw 0 0
/usb-otg vfat rw 0 0
tried using the make_ext4fs command, but again- nothing happens.
Using TWRP 3.3.1-0 by the way
Any ideas? is the phone completely bricked? it's stuck in a bootloop where the google colours come up but freeze within half a second, repeat and continue.
Any advice would be very much appreciated!

Categories

Resources