Related
Hello from Mother Russia =)
One user has sold me used Xperia S with an internal memory issue. (He told me the device is okay, arrrgh)
Device is rooted, bootloader is unlocked, firmware is stock, recovery is CWM.
It boots up and working, but memory is read only so I cannot install any software or take a picture or just receive sms...
In CWM I canot mount cache and data, cannot format sdcard, cannot wipe data.
I can only use ADB - pushing and pulling files (so the chip is not fried) and using other utils but all the changes is lost after reboot (or remounting).
I've found the reason - partitions of emmc is not consistent - fdisk -l /dev/block/mmcblk0 p says
Code:
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
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Please help me to restore the memory, any ideas will be valuable.
Or at least please post the results of running the commands
parted /dev/block/mmcblk0 print
fdisk -l /dev/block/mmcblk0
thanks a lot!
Additional info:
parted /dev/block/mmcblk0 print says
Code:
Unable to satisfy all constraints on the partition
mount says
Code:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type vfat (ro,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
cat /etc/fstab says
Code:
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p14 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p15 /sdcard vfat rw
df -a -h says
Code:
Filesystem Size Used Available Use% Mounted on
proc 0 0 0 0% /proc
sys 0 0 0 0% /sys
tmpfs 317.6M 64.0K 317.5M 0% /dev
devpts 0 0 0 0% /dev/pts
/dev/block/mmcblk0p12
1007.9M 562.2M 445.7M 56% /system
/dev/block/mmcblk0p15
25.8G 2.2G 23.6G 8% /sdcard
Basics
Did you try to reflash with with the flashtool? most of the issues are fixed by re flashing the system by flashmode
Make sure you kernel is flashed propely ? use one of xda-developers one e.i http://forum.xda-developers.com/showthread.php?t=2070816
Connect to computer and check attributes ?
Doomlord sd-mount as pendrive- mass storage and format it rememeber to format fat32. push by adb
http://forum.xda-developers.com/showthread.php?t=1744878
factory reset -> setting -> storage clear internal storage
thanks for reply )
marcoplo said:
Basics
Did you try to reflash with with the flashtool? most of the issues are fixed by re flashing the system by flashmode
Make sure you kernel is flashed propely ? use one of xda-developers one e.i http://forum.xda-developers.com/showthread.php?t=2070816
Click to expand...
Click to collapse
No, I did not. The previous owner wrote that he tried and everything looks OK? but after reboot there was no effect.
I will try with last flashtools and kernel you posted.
marcoplo said:
Connect to computer and check attributes ?
Click to expand...
Click to collapse
Hmm, do you mean permissions or what?)
marcoplo said:
Doomlord sd-mount as pendrive- mass storage and format it rememeber to format fat32. push by adb
http://forum.xda-developers.com/showthread.php?t=1744878
Click to expand...
Click to collapse
I cannot install it - adb install says
Code:
adb install SDM.apk
1945 KB/s (575757 bytes in 0.289s)
pkg: /data/local/tmp/SDM.apk
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
and
Code:
adb install -s SDM.apk
failed to copy 'SDM.apk' to '/sdcard/tmp/SDM.apk': I/O error
rm: can't stat '/sdcard/tmp/SDM.apk': I/O error
(the name of apk is correct)
I can push it to root dir or to system but there is no root explorer installed
marcoplo said:
factory reset -> setting -> storage clear internal storage
Click to expand...
Click to collapse
If you did mean the standard option in android settings, it runs OK but has no effect.
You said that Cmw is available is it? so go to advanced mount as a usb storage in clockworkmod try to format by computer !!
if you flash a new kernel and still no difference then I doubt any solution software way fix the problem
Kernel is responsible for the i/o of the mobile phone and managing partitions
From windows explorer, right click-> properties->take the tick out of
read-only box!
I cannot help you anymore since i just don't know !
Sorry
http://forum.xda-developers.com/showthread.php?t=1959445 is not related to the xperia s but it smillar problem to SGS
http://forum.xda-developers.com/showthread.php?t=1849170 this related as well
First thing you should try is repair with Sony PC companion. Relock bootloader then run PC Companion and select repair phone.
@ Raven so what the difference flashing phone with flashtool vs pc companion
try this!
http://developer.sonymobile.com/201...ocked-xperia-smartphones-video-beta-download/
marcoplo said:
@ Raven so what the difference flashing phone with flashtool vs pc companion
Click to expand...
Click to collapse
Well just few days ago I soft bricked my phone. It would show the Sony Logo and after that a memory card-warning type of sign. I tried Flashtool and went to flash a ROM but it got aborted right after starting flashing. My bootloader was unlocked and I panicked I screwed up for good. I tried to relock my bootloader with Flashtool and succeded. I tried again flashing with Flashtool and no-go, again aborted. Then I tried repairing with PC Companion and my phone was saved.
Flashtool is great, I use it all the time, but if you mess something up, your best bet is the PC companion.
mirhl said:
try this!
developer.sonymobile.com/2012/12/06/new-flash-tool-from-sony-for-unlocked-xperia-smartphones-video-beta-download
Click to expand...
Click to collapse
In flashmode the new Sony flasher detects the device correct but after downloading firmware (.A.2.45) an exception occures when writing. Exception has no additional info, just ERROR.
juan_ said:
In flashmode the new Sony flasher detects the device correct but after downloading firmware (.A.2.45) an exception occures when writing. Exception has no additional info, just ERROR.
Click to expand...
Click to collapse
Be sure to relocked your bl before using pc companion, otherwise you will get error in flashing/updating..
Sent from my LT26i using xda premium
marcoplo said:
You said that Cmw is available is it? so go to advanced mount as a usb storage in clockworkmod try to format by computer !!
Click to expand...
Click to collapse
No effect (
marcoplo said:
if you flash a new kernel and still no difference then I doubt any solution software way fix the problem
Kernel is responsible for the i/o of the mobile phone and managing partitions
Click to expand...
Click to collapse
I tried to flash LT26i_1252-0023_6.1.A.2.45_GENERIC-user_CUST_1257-6917_R2G.ftf via FlashTool for SE by Bin4ry and Androxyde (v0.9.10.1) - an error occures: ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Final data verification failed";
With Final data verification option disabled it goes OK but also has no effect +(
marcoplo said:
From windows explorer, right click-> properties->take the tick out of
read-only box!
I cannot help you anymore since i just don't know !
Sorry
Click to expand...
Click to collapse
Thank you for help anyway
marcoplo said:
forum.xda-developers.com/showthread.php?t=1959445 is not related to the xperia s but it smillar problem to SGS
Click to expand...
Click to collapse
Yepp, probably the solution for Samsung is to use Odin flasher and PIT file to restore file tables. But there is no such tools and files for Xperia...
marcoplo said:
forum.xda-developers.com/showthread.php?t=1849170 this related as well
Click to expand...
Click to collapse
I'll try this at last...
jemju_xps-user said:
Be sure to relocked your bl before using pc companion, otherwise you will get error in flashing/updating..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Yepp, thats the point. But i could not relock BL via flashmode and ftf (this thespicygadgematics.com/2012/06/unlock-re-lock-sony-xperia-s-and-u.html way), flashong was OK but the changes has not been applied as usual =(
UPD:
when I do it from fastboot (oem lock) it says
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
No comments
Your emmc partitions are overlapping and you need to fix them.
This will help you
http://gparted.sourceforge.net/h2-fix-msdos-pt.php
Edit:
Just checked partitions are fine as they are
demetris_I said:
Your emmc partitions are overlapping and you need to fix them.
This will help you
http://gparted.sourceforge.net/h2-fix-msdos-pt.php
Edit:
Just checked partitions are fine as they are
Click to expand...
Click to collapse
Emmc partition was not overlapping.I have acro s,that should have similar partition table except for sdcard(mmcblk0p15)
If the bootloader was unlocked try to erase data partition using fastboot
Example:
fastboot erase userdata
Attached partition screen shot from terminal
Sent from my LT26w using Tapatalk 2
So the conservation ends here? Lolz..i thought i can read until it solved..zzzz..
Sent from my LT26ii using XDA Premium HD app
I have that same problem.
juan_ said:
Hello from Mother Russia =)
One user has sold me used Xperia S with an internal memory issue. (He told me the device is okay, arrrgh)
Device is rooted, bootloader is unlocked, firmware is stock, recovery is CWM.
It boots up and working, but memory is read only so I cannot install any software or take a picture or just receive sms...
In CWM I canot mount cache and data, cannot format sdcard, cannot wipe data.
I can only use ADB - pushing and pulling files (so the chip is not fried) and using other utils but all the changes is lost after reboot (or remounting).
I've found the reason - partitions of emmc is not consistent - fdisk -l /dev/block/mmcblk0 p says
Code:
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
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Please help me to restore the memory, any ideas will be valuable.
Or at least please post the results of running the commands
parted /dev/block/mmcblk0 print
fdisk -l /dev/block/mmcblk0
thanks a lot!
Additional info:
parted /dev/block/mmcblk0 print says
Code:
Unable to satisfy all constraints on the partition
mount says
Code:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type vfat (ro,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
cat /etc/fstab says
Code:
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p14 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p15 /sdcard vfat rw
df -a -h says
Code:
Filesystem Size Used Available Use% Mounted on
proc 0 0 0 0% /proc
sys 0 0 0 0% /sys
tmpfs 317.6M 64.0K 317.5M 0% /dev
devpts 0 0 0 0% /dev/pts
/dev/block/mmcblk0p12
1007.9M 562.2M 445.7M 56% /system
/dev/block/mmcblk0p15
25.8G 2.2G 23.6G 8% /sdcard
Click to expand...
Click to collapse
the problem was solved by creating a partition table again .
I rebuild the partition information using adb and twrp.
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
adb shell
umount /sdcard
fdisk /dev/block/blkmmc0
p
d
15
d
14
.......
d
4
n
e
first cylinder 769
last cylinder 954240
n
first cylender 785
last cylinder 800
continues as in the above table
t
4(partiton number)
5(for extendet)
t
7
4b(original partition volume type)
continues to 15
w
install cwm recovery (support for otg, twrp not supported)
install your rom from fat32 usb storage
Komut (yardım için m): t
Disk bölümü numarası (1-6): 6 (6.bölümün türünü değiştirelim)
Onaltılık kod (kod listesi için L tuşlayın): L (Burada disk türünün kodunu istiyor. Kod listesi için L yazdık)
0 Boş 1e Gizli W95 FAT16 80 Eski Minix be Solaris boot
1 FAT12 24 NEC DOS 81 Minix / eski Li bf Solaris
2 XENIX root 39 Plan 9 82 Linux takas / S c1 DRDOS/sec (FAT-
3 XENIX usr 3c Disk Bölümü 83 Linux c4 DRDOS/sec (FAT-
4 FAT16 <32M 40 Venix 80286 84 OS/2 gizli C: a c6 DRDOS/sec (FAT-
5 Ek 41 PPC PReP Önyü 85 Linux ek c7 Syrinx
6 FAT16 42 SFS 86 NTFS bölüm k da DS-olmayan veri
7 HPFS/NTFS 4d QNX4.x 87 NTFS bölüm k db CP/M / CTOS / .
8 AIX 4e QNX4.x 2. böl 88 Linux saltmetin de Dell Uygulamas
9 AIX önyüklene 4f QNX4.x 3. böl 8e Linux LVM df BootIt
a OS/2 Önyüklem 50 OnTrack DM 93 Amoeba e1 DOS erişimi
b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS e4 SpeedStor
e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ee EFI GPT
10 OPUS 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
11 Gizli FAT12 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC
12 Compaq teşhis 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
14 Gizli FAT16 <32 61 SpeedStor a9 NetBSD f4 SpeedStor
16 Gizli FAT16 63 GNU HURD veya S ab Darwin boot f2 DOS ikincil
17 Gizli HPFS/NTFS 64 Novell Netware b7 BSDI ds fd Linux raid otos
18 AST SmartSleep 65 Novell Netware b8 BSDI takas fe LANstep
1b Gizli W95 FAT32 70 DiskSecure Mult bb Önyükleme sih ff BBT
1c Gizli W95 FAT32 75 PC/IX
turkish
Attention! I know there are already some posts about it. If you find it annoying PLEASE ignore this post. Do Not bother to comment. Just Ignore it.
Disclaimer: I'm Not Responsible for Anything. If you wish do it as your own risk.
These things are goning to happen
For the reason of Formating data will be lost - So backup everything to PC
You'll lose google sign in, contacts, messages, social networking etc. - backup before proceed
Things You will Need
Drivers - For Detecting your device properly (Sony Users can use "Flashtool")
ADB - Use mini version. You don't have to install Android SDK for this
USB Cable
CMD - Use "ConEmu" or "Console2" more flexible than cmd. Provides easy copy of text from console
TWRP Recovery - Download it from twrp site
I'm Going to put this assuming you as Novice. So I'll Explain as much as possible
Step 1 -
* Installing flashtool
Download flashtool from the link given above
Install flashtool as usual.
Then from "C:\Flashtool\drivers" install drivers for your phone.
Open Flashtool (Keep it open for this step)
* Phone Detection
After installing drivers - enable "USB debugging" in phone. Connect your phone to pc see if it is detected or not.
If not try doing uninstall & installing flashtool again. If it is not detected yet I shall say "STOP" forget partitioning. Look in the forum for a solution. Fix it and then continue.
If your device detects properly in normal mode then proceed
Turn off phone. Connect USB cable to PC and while pressing volume up button and connect cable to Phone.
A blue light will flash & Driver will install if necessary. In Flashtool window it will show fastboot mode after detecting phone. If not "STOP" try again. Fix it and then continue.
Step 2 - Install mini adb
If you have downloaded mini ADB.exe version install it to root directory of PC for example C:\ADB. Double click to open the .exe when ask for location of install show to C:\ADB
If you have downloaded Mini ADB as .zip/.rar file. Right click on the file> Extract to > C:\ADB
Step 3 - TWRP
Download from the link given above.
Move Downloaded TWRP image such as twrp-3.0.0-0-nozomi.img to ADB folder (C:\ADB)
Rename the file to twrp.img.
(Optional) - also move rom.zip for later use. If you want to install a fresh rom.
Step 4 - Kernel flash
* Flashing Kernel by flashtool
Turn off phone, conncet it to pc while pressing volume + button
open flashtool> flash device (thunder icon)> fastboot> Flash kernel> select twrp-3.0.0-0-nozomi.img
See the flashtool log if it says "OK" then Reboot/start the phone. Otherwise redo this step.
When starting press volume + - button several time it will bring up recovery screen.
* Flashing kernel into Fota Kernel.
You have to Upload the recovery.img into your phone & Flash to do this: Open Command Window by default in windows it is called cmd.
Opening Command window
* By CMD:
Go to ADB folder> Press Shift + Right Mouse button> Open Command window here> it will open a command window
* Using Other console software:
ConEmu or Console2 can't be open this way. You have to use "cd" command to go to adb folder.
In conEmu or console2 write: cd your adb location for example: cd c:\ADB
Now write these in command window-
adb push twrp.img /sdcard/ <<<<---- this will copy twrp.img to your phone sdcard. Remember to change recovery name to twrp.img
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11 <<<<---- this will write twrp to FOTA block of your phone.
** Rebooting phone will bring up recovery screen. In the recovery screen it will ask you whether system should be put into "Read only mode". Don't do that.
** In twrp Go to Mount> deselect System, data, cache, Sdcard and read only system > select again > again Deselect
Before You Procced Any Further Make Sure:
PC can detect your device Normally
PC Can detect device in Fastboot mode
If you really want to do this or not?
Step 5 - Partitioning
[*] Connect USB Cable while in TWRP recovery. (It dosen't matter which screen you are in just Stay in twrp recovery)
[*] Open ADB Folder> Open CMD or ConEmu from there (See Step 4 - opening command window section for this)
Write these command
adb shell <<<<----- it will start ADB
then write
fdisk /dev/block/mmcblk0 <<<<----- It will enable partitioning commands to work
This will bring some info & It will Look Like this:
The number of cylinders for this disk is set to 973824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
**NOTE** " Command (m for help): " will show automatically if you successfuly entered in partitioning mode if not redo steps again.
Now we need to see each block of default partition and detect SDCARD & Internal Storage: Write this-
p <<<<<<----- This will print or show each partition. Command (m for help): already be there just write p for example Command (m for help): p
It will show this:
Code:
[HIDE]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
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help):[/HIDE]
STOPCOPY THESE PARTITIOIN INFO TO A TEXT FILE AND SAVE IT. EVERY PHONE HAS SEPERATE PARTITION SETTING. IF ANYTHING GOES WRONG IT WILL BE NECESSARY TO SEE AND GIVE EXACTLY SAME VALUE TO RECOVER ORIGINAL PARTITION.
Identifying SDCARD & Internal Storage - From the print output we see lots of blocks and lots of data. But We need to know which partition belongs to which.
/dev/block/mmcblk0p14 <<<---- this is the Internal Storage. See the blocks column its like 2 GB (2097152)
/dev/block/mmcblk0p15 <<<---- this is the SDCARD. Blocks look like it's around 27GB and there is also win95 FAT32 type partition.
As we need to increase Internal Storage Size. From where these extra storage will come from? Well, it's from SDCARD. That's why SDCARD & Internal Storage has to be deleted and repartition again. As for delete do this
d <<<<<---- for deleting partition Command (m for help): d
Partition number (1-15): <<<<---- it will ask which partition you want to delete?
15 <<<<<---- First delete mmcblk0p15
then again give
d <<<<<---- for deleting partition Command (m for help): d
Partition number (1-15): 14 <<<<----- Deletes Internal storage partition which is mmcblk0p14
You can give P command to see whether those partition deleted or not
Command (m for help): p
Now creating new partition for Internal storage. Write
n <<<<<----- this is for creating new partition Command (m for help): n
this will show this:
Code:
First cylinder (769-954240, default 769):
To Understand properly look at this table you generated earlier using p command:
Code:
start end
/dev/block/mmcblk0p13 34945 42944
/dev/block/mmcblk0p14 42945 108480
/dev/block/mmcblk0p15 108481 954240
Here mmcblk0p13 started ended at 42944. mmcblk0p14 started at 42945. And mmcblk0p14 ended 108480 just after that mmcblk0p15 started at 108481. Ending is beginning. Quiet easy actually.
So when asked to put first cylinder: you take mmcblk0p13 end value plus 1 write that in first cylinder. for example if End value of mmcblk0p13 is 2 then first cylinder will be 3. if mmcblk0p13 end value is 1000 then first cylinder value will be 1001. if mmcblk0p13 End value is 42900 then first cylinder Value will be 42901. I think that's enough for understanding.
First cylinder (769-954240, default 769): 42945 [<<<<----- in my case mmcblk0p13 end value is 42944 so first cylinder value is 42945 this will not be same for you. press Enter]
Then it will ask for Last Cylinder value: There is three way to put this in kilobyte, in megabyte or in default size but we have to put + sign before size. For example: +100000k or +4000M or +2000000. Easiest one will be using Megabyte. 4000 megabyte is 4 gb, 8000 is 8GB. By default when partitioning system keep some space for recording partition info that's why we never get full size in Memory card, Hard disk, Flash drive etc. This will also be applied here. If you give +4000M command you will get 3.6GB or 3.7GB Something like that. So calculate give some more to keep it even if you want.
Code:
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
I want my internal storage is around 4GB So I Gave
+4192 <<<<----- Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240): +4192
Now The SDCARD Partition. To create This partition we have to give First cylinder value. As we don't know mmcblk0p14 has which Ending cylinder value. We have to generate the partition table and see. So give the P command.
Command (m for help): p <<<<--- shows partition table. Note the END Value of mmcblk0p14. suppose End value is 170875
Give n command
Command (m for help): n <<<<--- new partition for SDCARD or mmcblk0p15. It will ask for first cylinder
First cylinder (769-954240, default 769): <<<<---- put noted Ending value of mmcblk0p14 + 1 here. (170875+1 = 170876) press enter
Now Last cylinder: Just press enter it will take default
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Change partition type for SDCARD by giving these command.
Command (m for help): t <<<--- t for change partition type.
Partition number (1-15): 15 <<<--- It asks which partition to be changed give 15 for SDCARD/mmcblk0p15
Hex code (type L to list codes): c <<<--- FAT32 from win95 for most compatibility give c to choose this. Do not change to any other system type it might not recognized by PC or even your device. Press enter.
Writing all these changing permanently
Command (m for help): w <<<--- give w for write permission. if successful you'll see these message.
Code:
The partition table has been altered.
Calling ioctl() to re-read partition table
**NOTE** if you see something like below line. Partition is not altered or changed. Redo all steps carefully and properly.
Code:
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Step 6 - Formatting Partition.
Your Partition table redefined or resized only. No Formatting has done yet. Your phone do not read memory unless its properly formatted.
If you wish to use stock or stock based rom DO NOT CHANGE PARTITION FORMAT. It will cause problem even brick. Search around forum for more info about this.
Changing Partition format is good for the Upgraded OS version like lolipop 5.0.0 or 5.1.1 or Marshmallow 6.0.0 to work some features. But not always necessary.
Disconnect Phone from pc> Boot into recovery
Code:
TWRP> Wipe> Advance> Format data, cache, system and SDCARD.
If you want to change Format>
Code:
From TWRP>Wipe>Advance>select system or data or cache> change file format> select desiered one> change.
Nice tutorial...but how to push ROM back to phone
payjo73 said:
Nice tutorial...but how to push ROM back to phone
Click to expand...
Click to collapse
If you Mean Stock ROM Use flash tool.
If you mean a zip file of custom rom use adb command:
adb push something.zip /sdcard/
Hey, I have done the exact same procedure and flashed oneofakind ROM. Now my internal SD card seems to be messed up.
Camera app throws error "insert an SD card before using" error & Gallery app throws error "no SD card detected error"
Kindly HELP !!
ps : I already had TWRP installed, had root access & unlocked bootloader. So started from Step 5 with partitioning steps ! I can see the internal storage of 19GB in settings though.
pps : I searched google extensively but most related solutions had external SD card being used so I couldn't reconcile it with my device (Xperia S)
C0D3FR34K said:
Hey, I have done the exact same procedure and flashed oneofakind ROM. Now my internal SD card seems to be messed up.
Camera app throws error "insert an SD card before using" error & Gallery app throws error "no SD card detected error"
Kindly HELP !!
ps : I already had TWRP installed, had root access & unlocked bootloader. So started from Step 5 with partitioning steps ! I can see the internal storage of 19GB in settings though.
pps : I searched google extensively but most related solutions had external SD card being used so I couldn't reconcile it with my device (Xperia S)
Click to expand...
Click to collapse
You need to allow permissions for letting the app access storage in settings of phone.
Mirhawk said:
You need to allow permissions for letting the app access storage in settings of phone.
Click to expand...
Click to collapse
Thanks.
How do i do that ? I never had to do it earlier. I have installed the ROM multiple times in past year.
C0D3FR34K said:
Thanks.
How do i do that ? I never had to do it earlier. I have installed the ROM multiple times in past year.
Click to expand...
Click to collapse
It's in Settings, Apps>Settings icon at top right> App permissions. This error occurs with Marshmellow ROM's as they some new pemission features. You can check out the link in My signature for more related info
Bro i was following this tutorial but i don't know how mobile got disconnected ?.. Now mobile got damaged it can't able to switch on.. Even pc not detecting.. What should I do now.. Please help???
Hi Everyone,
You might have seen my last Guide about Flashing BPaul's 5.0 and 5.1.1
Here's my another Guide for Mickybart's nAOSP 6.0 for ACRO S
Credits:
@mickybart (Developer)
I see people complaining about the Guide available by mickybart is too BIG and Complicated.
Actually it looks Big but it's not!
Hope this Guide HELPS YOU ALL. I made it as simple as I can.
I REQUEST EVERYONE TO PLEASE READ FULL GUIDE
EVEN A GUY WHO KNOWS NOTHING, CAN FOLLOW THIS GUIDE!
(Atleast he/she must have a BRAIN)
Just REMEMBER, for Marshmallow we'll merge /data + /sdcard INTO ONE and change file-system from ext4 to f2fs.
That means, before we were getting 11.2GB of Internal memory AND 2GB for APPS.
Now after Repartition it'll become 13.2GB
NOTE: I'm NOT responsible if you damage your phone while caring out any process. As a NewBie or a N00B can make many silly mistakes. DO AT YOUR OWN RISK
Click to expand...
Click to collapse
We'll cover below major steps:
1. Repartitioning
2. File-System to f2fs
3. Flashing nAOSP 6.0
Pre-Requirities: (Download ALL and Keep in your PC)
Downloads:
nAOSP 6.0 ROM (Download 6.0)
Minimal ADB and Fastboot
OpenGapps ARM-6.0 (Download ARM -> 6.0 -> Mini)
Here We Begin:
First of all BACK-UP everything and save it to PC.
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
----------REPARTITIONING:----------
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk -l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
----------Changing File-Syatem to f2fs----------
Into TWRP:
Wipe
Advanced Wipe
Select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
GO back and do SAME for /cache to change File-System to f2fs
Once it's Done. Just reboot device. JUST REBOOT!
If you see 0MB or any wrong value for data after the reboot, try to format data (Wipe/Format Data).
In Extreme case, convert data to ext4 and convert back to f2fs. It'll hopefully work for you.
DONE!
----------Flashing nAOSP ROM 6.0----------
Copy the Downloaded nAOSP.zip AND OpenGapps.zip in Memory Card
IN TWRP:
Install
Select nAOSP.zip
Add more Zips (IMP)
Select OpenGapps.zip (IMP)
Swipe to Change
(after it's done)
Clear Cache and Dalvic Cache
Reboot
DONE!
(For the first time it can take a long to boot-up. So just don't worry and sit back!)
If you Found Above Post Helpful, There's a Thumbs UP Button Below, Don't Forget To Click It.
Regards,
hitman-xda
hi hitman thanks for your explaination . but im a bit confused about the repartition on the last cylinder. is it need to change 954240 because mine just 400k++
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
adiawie said:
hi hitman thanks for your explaination . but im a bit confused about the repartition on the last cylinder. is it need to change 954240 because mine just 400k++
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Click to expand...
Click to collapse
Please post the whole table?
I can't understand your problem.
hitman-xda said:
Please post the whole table?
I can't understand your problem.
Click to expand...
Click to collapse
im not save the installation table logs . i flashed back to stock rom because internal storage and sd card not detect. maybe i miss something
i'll try flash again later
@Hitman is it your acro works fine with this new rom or unstable?
Hi hitman
My problem is the same as adiawie
Im save the installation table logs :
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
4 heads, 16 sectors/track, 486016 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 477120 15243264 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
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 477120 11796480 c Win95 FAT32 (LBA)
~ #
........
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-477120, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-477120, default 477120): 954240
Value is out of range
.........
Thank you for your help
adiawie said:
im not save the installation table logs . i flashed back to stock rom because internal storage and sd card not detect. maybe i miss something
i'll try flash again later
@Hitman is it your acro works fine with this new rom or unstable?
Click to expand...
Click to collapse
I can't tell anything what went wrong for you, without seeing the table.
Is your stock ROM running well?
And yes my Acro S is running well and almost stable with this ROM.
jamis66 said:
Hi hitman
My problem is the same as adiawie
Im save the installation table logs :
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
4 heads, 16 sectors/track, 486016 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 477120 15243264 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
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 477120 11796480 c Win95 FAT32 (LBA)
~ #
........
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-477120, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-477120, default 477120): 954240
Value is out of range
.........
Thank you for your help
Click to expand...
Click to collapse
Well, I think I can fix you!
USE below values while repartitioning and rest of the procedure is same.
For the FIRST CYLINDER : 42945
For LAST CYLINDER: 477120
Regards,
hitman-xda
hitman-xda said:
I can't tell anything what went wrong for you, without seeing the table.
Is your stock ROM running well?
And yes my Acro S is running well and almost stable with this ROM.
Click to expand...
Click to collapse
yes on stock rom everything run well.
this is the best way to get your partition back.
I tried bpaul 5.1.1 rom but internal storage and sd card still not detect
hitman-xda said:
Well, I think I can fix you!
USE below values while repartitioning and rest of the procedure is same.
For the FIRST CYLINDER : 42945
For LAST CYLINDER: 477120
Regards,
hitman-xda
Click to expand...
Click to collapse
Thanks for the help.
Successfully installed.
Very good work this. nAOSP 6.0 rom
Thank again!
adiawie said:
yes on stock rom everything run well.
this is the best way to get your partition back.
I tried bpaul 5.1.1 rom but internal storage and sd card still not detect
Click to expand...
Click to collapse
Thats nice!
Internal storage and sd card not detected? Do you mean it does not show in any file explorer? Also stock ROM is installed and running successfully?
jamis66 said:
Thanks for the help.
Successfully installed.
Very good work this. nAOSP 6.0 rom
Thank again!
Click to expand...
Click to collapse
That's Good! Enjoy MarshMallow!
hitman-xda said:
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
[/B]
Click to expand...
Click to collapse
Thankyou for this guide Hitman, I am excited to try this on my XAS! I am getting stuck in the early stages of the guide though. I have 2x Acro S running BPaul 5.1.1. I have installed minimal ADB but when I run it the command prompt does not have a '~' symbol. I have tried to connect both phones in fastboot mode by holding the volume up key or also the power key but neither seems to work. I can get a blue light for a few seconds then the phone proceeds to boot to Google logo and battery indicator. I have tried running the first command '~fastboot devices' on both phones but nothing happens, no error message, no attempt or otherwise, it just goes to a new line of the command prompt. I have installed flashtool adb drivers. I am running Windows 10.
Do you have any idea what may be going wrong here?
Thanks!
glenb83 said:
Thankyou for this guide Hitman, I am excited to try this on my XAS! I am getting stuck in the early stages of the guide though. I have 2x Acro S running BPaul 5.1.1. I have installed minimal ADB but when I run it the command prompt does not have a '~' symbol. I have tried to connect both phones in fastboot mode by holding the volume up key or also the power key but neither seems to work. I can get a blue light for a few seconds then the phone proceeds to boot to Google logo and battery indicator. I have tried running the first command '~fastboot devices' on both phones but nothing happens, no error message, no attempt or otherwise, it just goes to a new line of the command prompt. I have installed flashtool adb drivers. I am running Windows 10.
Do you have any idea what may be going wrong here?
Thanks!
Click to expand...
Click to collapse
You don't have to write ' ~ ' symbol. That's not the part of the code.
Blue LED light for few seconds and phone boots! That's means you have to install fastboot drivers to your PC.
If some cases, try connecting USB to different ports of your PC.
You said you're using BPaul's 5.1.1
You should have know this. Still if you don't, check my below link for installing fastboot drivers;
http://forum.xda-developers.com/showpost.php?p=61045126&postcount=4
hitman-xda said:
You don't have to write ' ~ ' symbol. That's not the part of the code.
Blue LED light for few seconds and phone boots! That's means you have to install fastboot drivers to your PC.
If some cases, try connecting USB to different ports of your PC.
You said you're using BPaul's 5.1.1
You should have know this. Still if you don't, check my below link for installing fastboot drivers;
http://forum.xda-developers.com/showpost.php?p=61045126&postcount=4
Click to expand...
Click to collapse
Thanks,
I followed your guide but get the message "Google, Inc (WinUSB) - Install Failed" every time I try. If I look in device manager for the few seconds that the blue light is on I have a device under portable devices with an exclamation that says "S1Boot Fastboot".
It definitely seems to be a driver issue but I can't seem to get it resolved. I have tried pointing the driver directly but it says driver not found.
I will try from another computer in the next day or so.
hitman-xda said:
Thats nice!
Internal storage and sd card not detected? Do you mean it does not show in any file explorer? Also stock ROM is installed and running successfully?
That's Good! Enjoy MarshMallow!
Click to expand...
Click to collapse
now im enjoying MarshMallow.. thanks @mickybart and @hitman-xda
glenb83 said:
Thanks,
I followed your guide but get the message "Google, Inc (WinUSB) - Install Failed" every time I try. If I look in device manager for the few seconds that the blue light is on I have a device under portable devices with an exclamation that says "S1Boot Fastboot".
It definitely seems to be a driver issue but I can't seem to get it resolved. I have tried pointing the driver directly but it says driver not found.
I will try from another computer in the next day or so.
Click to expand...
Click to collapse
Better do it on windows 7/8.
Win10 is crap!
hitman-xda said:
Better do it on windows 7/8.
Win10 is crap!
Click to expand...
Click to collapse
it works for me in win10
@hitman-xda this rom running well on my acro but when connecting to pc internal storage & sd card not detect.
adiawie said:
@hitman-xda this rom running well on my acro but when connecting to pc internal storage & sd card not detect.
Click to expand...
Click to collapse
When you connect your phone to PC, at that time unlock your phone and drop down notification drawer and click on "USB for Charging" then click on "File Transfers".
hitman-xda said:
When you connect your phone to PC, at that time unlock your phone and drop down notification drawer and click on "USB for Charging" then click on "File Transfers".
Click to expand...
Click to collapse
many thanks to u... perfecto
hitman-xda said:
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk-l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
Click to expand...
Click to collapse
Hi Hitman,
I tried on an older Vista machine and I was able to boot to fastboot mode and install recovery, so that is progress! I have come across another problem now though... I have followed the guide and gone to recovery and unticked all mounted partitions, then when I type "adb shell" on the PC with the phone connected I get the error:
"error: device 'null' not found"
Have I missed something here?
Hi,
I am stuck in the bootloop after flashing data.img on Pixel C device.
I have done the following steps and have serached around in 100s of forums before posting this. Please bear with me.
My bootloader is unlocked and I have flashed my boot partition with dragon-boot-encryptable-rooted-01092016-1.img so that the data is not encrypted by default.
I have a freshly booted up (new setup) device with default apps installed. I installed one app so that the /data partition contains something. I am firing all commands as root on Ubuntu 14
I then flashboot into TWRP recovery so that I can access root shell through adb. This is not flashing the TWRP recovery, just booting into it.
#adb reboot bootloader
#fastboot boot twrp-3.0.0-0-dragon-ryu-02112016-1.img
#adb shell
~ # whoami
root
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1420244 20 1420224 0% /dev
tmpfs 1420244 20 1420224 0% /tmp
/dev/block/mmcblk0p6 396744 452 388100 0% /cache
/dev/block/mmcblk0p7 55453060 304032 55132644 1% /data
/dev/block/mmcblk0p7 55453060 304032 55132644 1% /sdcard
Now, I am interested only in taking image backup of my /data partition which is at /dev/block/mmcblk0p7. I confirmed this by:
/dev/block/platform/700b0600.sdhci/by-name # ls -l
...
lrwxrwxrwx 1 root root 20 Oct 16 07:38 UDA -> /dev/block/mmcblk0p7
...
Now, I fire the make_ext4fs command to create the image.
~#umount /sdcard (optional)
~ # make_ext4fs -s -l 55453060K -a data mydata.img /data
SELinux: Loaded file_contexts contexts from /file_contexts.
Creating filesystem with parameters:
Size: 56783933440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13863265
Block groups: 424
Reserved block group size: 1024
Created filesystem with 11/3466624 inodes and 263660/13863265 blocks
mydata.img is created. I do an adb pull on my Ubuntu and fetch the mydata.img and /file_contexts
#adb pull /file_contexts
#adb pull /mydata.img
# du *
20 file_contexts
140888 mydata.img
Now, I convert the mydata.img into raw image file with simg2img.
#./simg2img mydata.img mydata.img.raw
#ls -lrt
-rw-r--r-- 1 root root 17261 Oct 16 13:17 file_contexts
-rw-r--r-- 1 root root 144267780 Oct 16 13:18 mydata.img
-rw-r--r-- 1 root root 56783933440 Oct 16 13:21 mydata.img.raw
Now, I create a directory and mount my raw image into that directory.
#mkdir phonedata
#mount -t ext4 mydata.img.raw phonedata/
I navigate into phonedata and verify the contents. I can see that the app I installed in avaialable under /data/data.
Then, I re-create the image from phonedata mount using make_ext4fs, or I can use the mydata.img fetch by adb pull too.
If I re-create the image, I give file_contexts(fetched) as the -S option to make_ext4fs. One doubt here, if I am re-creating the sparse image, what value should be passed to -l paramtere now?
I got to fastboot and fire these commands.
#fastboot format userdata
#fastboot format data
#fastboot format cache
#fastboot flash data mydata.img { I am confused between data and userdata, which is the correct one. This is mydata.img from adb pull }
#fastboot flash vendor vendor.img { I read in one forum that vendor should be flashed again on a nexus device }
#fastboot reboot
All things take smoothly. When the tab reboot, it shows Google logo, then android flash animation, then it shows 'Android is starting', and then goes back to flash animation. That is, it's stuck in bootloop.
Kindly let me know if there is something with these steps. Or is there is any alternate way to do the same thing. My problem statement is, I need a flashable data.img. I can create TWRP backup and recovery fine, but that's not my requirement.
Thanks!
Edit 1:
I should add, at this point, if I hard boot to fastboot and do a fastboot format userdata followed by fastboot reboot, I am able to boot to device and perform new device setup.
I can also flash system,boot,vendor,recovery and cache.img and perform new device setup normally. This should mean my fastboot/adb are working fine.
Ummmmm
Did you try with smaller sparse image size ?
make_ext4fs -s -l 30000M -a data mydata.img /data
The sparse will grow until max partition size.
Did you play with "img2simg" as well ? (not simg2img)
img2simg mydata.img.raw mydata.img
How to repartition your Xperia s
The old thread is actually easy but many he not understood
So I he posted YouTube links from which you can understand
How to repartition
Here We Begin:
First of all BACK-UP everything and save it to PC.
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
----------REPARTITIONING:----------
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk -l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
----------Changing File-Syatem to f2fs----------
Into TWRP:
Wipe
Advanced Wipe
Select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
GO back and do SAME for /cache to change File-System to f2fs
Once it's Done. Just reboot device. JUST REBOOT!
If you see 0MB or any wrong value for data after the reboot, try to format data (Wipe/Format Data).
In Extreme case, convert data to ext4 and convert back to f2fs. It'll hopefully work for you.
DONE!
YouTube Link https://m.youtube.com/watch?v=ZZqJIY-ITwg
One of a kind rom look https://m.youtube.com/watch?v=lwOxauZBP-Q
Xperia S 6.0.1 look https://m.youtube.com/watch?v=j0_7fZyLf8s
Thanks
He*--have. ...sorry for misspelled words
www.youtube.com/c/Nabeelgm
Subscribe for more
Hi, I've got a question, I asked in other repartition thread too. The question is, will I able to install OneOfAKind 5.1.1 again after this repartitioning ? I've read on one of this threads that it only may work with nAOSP and Im a lil' bit confused now :C
How to revert and leave the internal memory as in the original xperia s?
---------- Post added at 05:39 PM ---------- Previous post was at 04:49 PM ----------
I managed to **** my xperia s in inimaginavis ways
First: I tried to partition my internal memory and disappeared from the mmcblk0p12 to mmcblk0p15
How to fix 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"
}
Second: meu celular entrou em loop ao tentar inciar o Twrp.
So I had the brilliant idea of deleting the Cache, System and Data by Adb...
The loop was solved but ...
Is there a solution or can I use my xperia as paper weight? xD
gmnabeel said:
How to repartition your Xperia s
The old thread is actually easy but many he not understood
So I he posted YouTube links from which you can understand
How to repartition
Here We Begin:
First of all BACK-UP everything and save it to PC.
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
----------REPARTITIONING:----------
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk -l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
----------Changing File-Syatem to f2fs----------
Into TWRP:
Wipe
Advanced Wipe
Select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
GO back and do SAME for /cache to change File-System to f2fs
Once it's Done. Just reboot device. JUST REBOOT!
If you see 0MB or any wrong value for data after the reboot, try to format data (Wipe/Format Data).
In Extreme case, convert data to ext4 and convert back to f2fs. It'll hopefully work for you.
DONE!
YouTube Link https://m.youtube.com/watch?v=ZZqJIY-ITwg
One of a kind rom look https://m.youtube.com/watch?v=lwOxauZBP-Q
Xperia S 6.0.1 look https://m.youtube.com/watch?v=j0_7fZyLf8s
Thanks
Click to expand...
Click to collapse
My device doesnt work anymore, i tried 2 times but when i try to format using TWRP it says:
Failed to mount '/cache' and '/data' (No such device)
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
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Sorry
AnisErrais said:
My device doesnt work anymore, i tried 2 times but when i try to format using TWRP it says:
Failed to mount '/cache' and '/data' (No such device)
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
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Click to expand...
Click to collapse
I just don't have it anymore sorry