Develop Bugs

eMMC partition table is broken, please post yours

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

Alcatel 960C/ One Touch Authority

Has anyone created a clockworkmod for this? This phone can be rooted, thru two apps, poot, and ministro(Qt). It still has gingerbread 2.3.6, and I need clockworkmod, or the source code, to use clockworkmod's builder. It is the cdma variant of the alcatel 995(which is gsm). can anyone point me in the right direction?

Source Code
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.

reggjoo said:
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
Click to expand...
Click to collapse
how did you get it rooted?

rooting alcatel authority (960c)
squidbutt said:
how did you get it rooted?
Click to expand...
Click to collapse
First make sure you have USB Debugging checked and your allowing instalation of unknown sources
DL these from the play store:
Minstro2
Superuser
DL poot.apk: View attachment poot.zip
Run poot, click yes to download the extra librarys, click "click here to poot" you will need to restart the phone when it prompts. You should be rooted now :good:
You can DL ES File Explorer(from play store) and in the settings check: Root Explorer, Up to Root and Mount File System. Now you can manage all the files on your phone but be careful of what you delete, some of the stock apk's are very hard to recover if you delete them.
Hope this helps

Download superuser first
Download superuser first, you won't be able to run it until the phone's rooted. after it's rooted, it will work. This way, seems to stop a problem, when you go thru the steps to root. Some people had a error. If you plan to open the /data, /system, or dalvik cache, on your computer, install chainfire's adb insecure. These folders don't open without this, on a computer.

I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.

Haven't seen this
aldude999 said:
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Click to expand...
Click to collapse
Hello, I haven't looked into this thread for a while. I see that you have some info for these blocks. that I couldn't get. I tried using root explorer, to look into some files, and they couldn't load, and tried to use too much memory, just to attempt to open, which, my phone said it was low on memory. Hate gingerbread, and kwansi choi( maker of this rom), This phone could easily handle a later os.
The usb ID's, are "Device 007: ID 1bbb:9018" .

USB ID's
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.

reggjoo said:
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
Click to expand...
Click to collapse
I noticed that:
mmcblk0p15
mmcblk0p12
mmcblk0p8
all have the same number of blocks.
The FOTA code shows
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
Click to expand...
Click to collapse
applypatch useage is as follows:
applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Click to expand...
Click to collapse
Apply patch from blk8 to blk15.
So maybe I was mistaken with what I thought was the partition. Blk8 seems to be where fota grabs it's updated partition from?
This shows that blk15 may actually be the recovery partition. Still useless unless the bootloader can be worked on.

Battery terminals
As we know, if the battery is out, the phone will do nothing( unlike my old huawei, it didn't matter). I wondered if that was the reason why, it's so hard to unlock it. I think the bootloader has been set up to not respond to attempts. The bootloader condition treats the phone as if there's no power to it(?) . I found out that the middle terminals, of the battery contacts, will power the phone, if they're connected, but only for a few seconds.
Maybe there's some code that's unknown, or procedure. The phone doesn't respond to fastboot commands, and I can't enable it(function), on it. In the default.prop file, I see that ro.secure, is 1. Whenever I try to change it to 0( in rewritable mode), it never takes. So this is a little info.

reggjoo said:
The bootloader condition treats the phone as if there's no power to it(?)
Click to expand...
Click to collapse
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.

aldude999 said:
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
Click to expand...
Click to collapse
Yes, I think alcatel's a little shady. I use a dual boot pc, and I found out, using the lsusb command, that the usb id's were different, than what the id's were for the supposedly official usb drivers. Sent them a msg, and they said I was wrong( can't be wrong if everything works!). They take no responsibility for their hardware, and I let people know, every chance I get, whenever I see a review of a phone from them. I found out the id's were wrong, when, before I even rooted it, I installed their onetouchmanager, and it couldn't find my phone( what! out the box!). That's not the way you do things.

Bringing 960C Back To Life!!!
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...

thealexday said:
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
Click to expand...
Click to collapse
I still am using my 960c. I wouldn't mind finding the original stock rom or finding out how to upgrade to a newer android version. Currently running version 2.3.6
Too bad I don't know much about modding save for rooting and flashing. I gather there are still some of us here who really like our 960c phones otherwise.

[6039y] **GUIDE** Repartitioning of the internal memory

Here it is as I promised.
This phone (the model with one sim card) is sold as a device with 8GB internal memory. In fact the memory chip inside is 16GB, so we can increase the available internal space.
PLEASE READ CAREFULLY AND IF SOMETHING IS NOT CLEAR DO NOT HESITATE TO ASK.
*** The data on your device will be untouched after this operation. But again please read carefully! ***
*** A good practice is always to make a backup of everything which will be changed. I do it and I've made a backup of the entire internal memory of the device before the start of the operation which is described below. ***
*** At the end of the post there is a link to a ZIP file which can be flashed through TWRP in order to perform the procedure automatically. Also includes a check for the size of the EMMC (as there are devices on which the resizing cannot be performed...their chip is smaller).***
1. You can go to this thread and to say Thanks! @meghd00t as his static build of gdisk is used in the recovery below.
2. What is needed:
- A different TWRP Recovery with gdisk inside. It can be downloaded from here twrp-2.8.7.0-idol3-6039y-with-gdisk.img - md5sum: 66b3f82a3e2e1afe14627b3b900a9319
- (Optional) An SD card for backup of the original GPT partition layout.
- Patience and careful reading.
- The Windows users probably need the drivers from this post, for access to the device in recovery mode.
3. How to do it (the output used below is from the terminal window from which I've done this operation on my device):
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3-6039y-with-gdisk.img
- go to the device
Code:
adb shell
- unmount all partitions of the internal memory
Code:
~ # umount /cache
~ # umount /sdcard
~ # umount /and-sec
- ensure that there are no mounted partitions from mmcblk0. The output from the mount command should looks like this:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=713016k,nr_inodes=157853,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=713016k,nr_inodes=157853)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
- start gdisk
Code:
~ # gdisk /dev/block/mmcblk0
all partitions can be listed by pressing 'p' but we are interested by the last two:
Code:
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
and their information which will be shown by pressing 'i' and entering the partition number:
Code:
Command (? for help): i
Partition number (1-38): 37
Partition GUID code: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335 (Unknown)
Partition unique GUID: BDD7FA27-93D4-40BC-B266-313E074E0E87
First sector: 5000400 (at 2.4 GiB)
Last sector: 15269853 (at 7.3 GiB)
Partition size: 10269454 sectors (4.9 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdata'
Command (? for help): i
Partition number (1-38): 38
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: BD12CF41-10E7-BBF7-D096-5553B89882E7
First sector: 15269854 (at 7.3 GiB)
Last sector: 30535646 (at 14.6 GiB)
Partition size: 15265793 sectors (7.3 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdatabak'
The information which is needed from the above output is Partition GUID code, First sector, Last sector and Partition name. You can write these somewhere (if your values are different from the above) from where can be pasted easily later (alternatively you can use the scrollback function of the terminal ).
- if you have an SD card make a backup of the partitions layout (in case that something goes wrong):
Code:
Command (? for help): b
Enter backup filename to save: /external_sd/gpt_partitions_table.backup
The operation has completed successfully.
- delete partitions 37 and 38:
Code:
Command (? for help): d
Partition number (1-38): 38
Command (? for help): d
Partition number (1-37): 37
- create a new partition 37, bigger in size with the same (as before) Partition GUID code, and the same (as before) start sector:
Code:
Command (? for help): n
Partition number (37-40, default 37): 37
First sector (34-30535646, default = 5000400) or {+-}size{KMGTP}: 5000400
Last sector (5000400-30535646, default = 30535646) or {+-}size{KMGTP}: 30535546
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
Changed type of partition to 'Unknown'
The difference here is in the last sector of the partition 30535546.
- create a new partition 38 with same Partition GUID code, but with different First sector:
Code:
Command (? for help): n
Partition number (38-40, default 38): 38
First sector (34-30535646, default = 34) or {+-}size{KMGTP}: 30535547
Information: Moved requested sector from 30535547 to 30535548 in
order to align on 2-sector boundaries.
Use 'l' on the experts' menu to adjust alignment
Last sector (30535548-30535646, default = 30535646) or {+-}size{KMGTP}: 30535646
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
Changed type of partition to 'Microsoft basic data'
Please note that here in the output after 'n' the default first sector is 34, so you explicitly must enter the value!!! As can be seen I've entered the next available sector (after partition 37) 305355547 but it has been corrected automatically to 30535548. So you can use directly 30535548 as a start sector. The last sector is at the end of the memory 30535646.
- write the names of the new partitions:
Code:
Command (? for help): c
Partition number (1-38): 37
Enter name: userdata
Command (? for help): c
Partition number (1-38): 38
Enter name: userdatabak
- if you list the partitions again (with 'p') the end of the table should looks like this:
Code:
37 5000400 30535546 12.2 GiB FFFF userdata
38 30535548 30535646 49.5 KiB 0700 userdatabak
- now it is safe to write the changes by pressing 'w':
Code:
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
The operation has completed successfully.
- resize the file system:
Code:
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... hmm ... let's run it:
Code:
~ # e2fsck -f /dev/block/mmcblk0p37
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 12519/321280 files (5.8% non-contiguous), 678615/1283425 blocks
~ # resize2fs -p /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p37' first.
... well the resize2fs have some checks and refuses to resize the file system therefore we must force the execution:
Code:
~ # resize2fs -fp /dev/block/mmcblk0p37
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /dev/block/mmcblk0p37 to 3191893 (4k) blocks.
The filesystem on /dev/block/mmcblk0p37 is now 3191893 blocks long.
The device now can be rebooted and its internal memory will be almost 12GB which compared to its previous size is a very nice upgrade. Screenshots before and after the repartitioning can be seen here.
Update (19.09.2015): This is a link to a flashabable zip which can be used from the TWRP to automate the process. Can be used with any TWRP recovery for 6039.
md5sum: c3f685310283bdc00cee5412fa33259c

Just tried it, and it worked like a charm. Thank you very much!

Wow ! Kudos to meghd00t and petrov.0. I just ordered this phone as a backup, waiting for my beloved Xperia Z1 Compact to be saved from watering (medium rain during less than 10min, so long Sony waterproof phones...). Can't wait to receive it and play with this extra storage !! Thank you :victory:

Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!

evilinheaven said:
Here i'am, crazy thinking that if the 6039y(Single chip, SDcard and 8Gb) come with 8Gb worth of wasted money, that the 6039j dual chip and 16Gb non-SDCard version may very well come with a SDCard reader hardware worth of wasted money.
It would be like just changing the Chip Support slot thing or whatever...
Can someone support my craziness and post a picture of thi "where the chip stays" of the SDCard reader version of this phone??
Thanks a lot!!
Click to expand...
Click to collapse
Well ... I like crazy things. But is impossible just to add a chip.
The thread itself is for other things. I don't want more reminders from the moderators. So please use the general section next time.
Thank you in advance.

Here is the complete partition list for 8Gb single sim variant:
Code:
Disk /dev/block/mmcblk0: 30535680 sectors, 14.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 40 entries
First usable sector is 34, last usable sector is 30535646
Partitions will be aligned on 2-sector boundaries
Total free space is 256464 sectors (125.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 265215 1.5 MiB FFFF tunning
3 265216 267263 1024.0 KiB FFFF traceability
4 267264 267265 1024 bytes FFFF fsc
5 267266 267281 8.0 KiB FFFF ssd
6 267282 268305 512.0 KiB FFFF sbl1
7 268306 269329 512.0 KiB 0700 sbl1bak
8 269330 270353 512.0 KiB FFFF rpm
9 270354 271377 512.0 KiB 0700 rpmbak
10 271378 272401 512.0 KiB FFFF tz
11 272402 273425 512.0 KiB 0700 tzbak
12 273426 274449 512.0 KiB FFFF hyp
13 274450 275473 512.0 KiB 0700 hypbak
14 275474 278545 1.5 MiB FFFF modemst1
15 278546 281617 1.5 MiB FFFF modemst2
16 281618 283665 1024.0 KiB FFFF simlock
17 283666 286737 1.5 MiB FFFF efsdata
18 393216 393279 32.0 KiB FFFF DDR
19 393280 396351 1.5 MiB FFFF fsg
20 396352 396383 16.0 KiB FFFF sec
21 396384 398431 1024.0 KiB FFFF aboot
22 398432 400479 1024.0 KiB 0700 abootbak
23 400480 466015 32.0 MiB FFFF boot
24 466016 531551 32.0 MiB FFFF recovery
25 531552 4306427 1.8 GiB FFFF system
26 4325376 4390911 32.0 MiB FFFF persist
27 4390912 4407295 8.0 MiB FFFF splash
28 4407296 4448255 20.0 MiB 0700 tctpersist
29 4448256 4468735 10.0 MiB 0700 hdcp
30 4468736 4468751 8.0 KiB FFFF fota
31 4468752 4993039 256.0 MiB FFFF cache
32 4993040 4995087 1024.0 KiB FFFF misc
33 4995088 4996111 512.0 KiB FFFF keystore
34 4996112 4996175 32.0 KiB FFFF config
35 4996176 4996303 64.0 KiB FFFF oem
36 4996304 5000399 2.0 MiB FFFF FactoryRP
37 5000400 15269853 4.9 GiB FFFF userdata
38 15269854 30535646 7.3 GiB 0700 userdatabak
Maybe someone can post the list for 16Gb dual sim variant?

Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitions have the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.

rioachim said:
Ok, I bit the bullet and resized the "userdata" partition. Only that I did not create the smaller #38 partition, I did not see any reason to do it (if any update tries to store something inside it, will fail anyway; this partition does not look special, all *bak partitionshave the same GUID). Plus there isn't any "userdatabak" partition on 16Gb models. Instead I made partition #37 up to the latest available sector (30535646). The phone is working just fine.
Click to expand...
Click to collapse
OK. But don't be fulled by the GUID. Most of the bak partitions contain data which is equivalent to the data in the primary ones (aboot, rpm, sbl1 etc.). The data is patched in both partitions with the same patch during an upgrade.

Script to repartition "internal memory"
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99

google99 said:
Hello petrov.0, all
Is it possible to create a shell for all thoses commands ?
In this case if partitions are lost (upgrade, patchs....) we could apply it easily.
And nice discovered.
Regards
Google99
Click to expand...
Click to collapse
No it is not:
Code:
GPT fdisk (aka gdisk) is a text-mode menu-driven program for creation and manipulation of partition tables.

Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!

Romagnolo1973 said:
Hi petrov.0 great news and thanks.
Just a doubt, a friend of mine will receive Idol 3 4,7" 8 GB tomorrow, he can made OTA update (that I think are available for security reasons as "stagefright" and another I know Alcatel get users a way to set SD as main memory) and then use your guide to expand memory t 16 Gb or for this operation is better been in a fresh unchained device not updated?
Because in this second option device become 16 Gb Rom but will be afected by stagefright and for the rest of his life
Thanks!
Click to expand...
Click to collapse
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).

petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk

Rorshan said:
By the way is there any hope (other than getting Alcatel to push an update to put fastboot commands back in, cause is anyone that optimistic?) for people who have indeed updated to recover those?
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
If you find a way to root the device after the update then may be there is a hope.

petrov.0 said:
It shouldn't be updated. The official updates for 6039 removes the fastboot commands therefore you will not be able to do the repartitioning nor to root the device. Give me the update file and will modify it in a way which will preserve the commands (there is a risk for a broken device after it though ... I wish to try such modification first on my phone, but unfortunately I still do not have official update for it with which to test).
Click to expand...
Click to collapse
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.

Romagnolo1973 said:
Understood the problem is new update that remove some action from fastboot needed for repartioning. Idol 3 was received and he resize rom from 8 to 16 with no issue with your guide, after that he made OTA update and they are working perfectly, no issue with the new partitioning size and device is working well.
Click to expand...
Click to collapse
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.

petrov.0 said:
Not some but all fastboot commands are removed. Glad to see that you have made it though. The OTA update however is a mistake. Now you can't get root access nor the fastboot commands are available.
Click to expand...
Click to collapse
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.

Romagnolo1973 said:
Yes, it was risky but probably he is not interested in root, I only inform you that new partitioning with OTA is still there, I think is a goodnews and a base to start, now the perfect situation is if Alcatel made a future OTA as soon as possible with fastboot perfectly working.
Click to expand...
Click to collapse
There is nothing wrong with the fastboot commands prior the update. I have doubts that they will be returned. Thanks for the info though (despite that I already know this by looking in the update files). I can't live without root access however therefore there is no option to loose it.

I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)

Rorshan said:
I'm kinda confused here. Are all the steps done from a terminal on the computer or is some of that to be typed inside the TWRP terminal? Because as soon as I boot TWRP with gdisk I get a device not found from typing adb shell. I'm pretty sure I have all the drivers mentioned in the linked post (and even more too). Any kind soul to explain how stupid I am being (because I know that's the solution in the end, I'm a fool)
Click to expand...
Click to collapse
Everything after adb shell must be done directly on the device. The VID & PID of the device are different in the recovery and you don't have the necessary drivers. Try to install the drivers mentioned in the first post (- The Windows users probably need the drivers from this post, for access to the device in recovery mode).

[GUIDE][ACRO S] nAOSP 6.0 Full Flashing Guide. ULTIMATE N00B GUIDE! (ROM+Repartition)

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?

mmcblk 14 missing (data)

Hello,
Today i tried to put a custom rom on my Sony Xperia Acro S. After a lot of problems with the flashing(windows 10 blocks everything) i got it rooted and in fastboot.
After that i repartioned it, if followed this guide: https://forum.xda-developers.com/xperia-s/acro-s-development/guide-naosp-6-0-flashing-guide-ultimate-t3334055
I did everything it said and at the end I didn't got an error while the thread said it had to, so i waited a while and then rebooted it.
I don't know if the problem came from that but after that i couldn't format or change filesystems. The phone constantly says: Erimary block device '/dev/block/mmcblk0p14' for mount point '/data' is not present!
After that a few more lines follow with unable to mount and error change and so on. So basically it says that mmcblk0p14 is missing. After that i did some research in adb and i found out that the partitions look completely different from the start situation. After that i tried to just install the rom, this worked until at the end i got an error and with the reboot after that the phone got stuck in a bootloop, after removing the sd it worked normal again. My question now is, how can i recover the storage or place mmcblk0p14 back or can i just go back to my normal android or is this gone now?
Start
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
4 heads, 16 sectors/track, 477120 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)
~ #
Click to expand...
Click to collapse
End
~ # fdisk -l /dev/block/mmcblk0
Omitting empty partition (14)
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
4 heads, 16 sectors/track, 477120 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
~ #
Click to expand...
Click to collapse

Re open adb shell just like you did for partitioning then: (aafter every command press enter)
fdisk /dev/block/mmcblk0
n
42945
108480
t
14
83
write w
after this write: fdisk -l /dev/block/mmcblk0
the output at part 14 should be like this:
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux if yes ok, REBOOT, IF NOT OK:
reboot the phone, go to twrp again and restart adb shell, retype the command fdisk -l /dev/block/mmcblk0 and see if there is a 14 partition then,
again
n
108481
477120
t
15
NOW, I'M NOT SURE, when it asks for hex code type L and search for win32/fat32 code and write it.
and write w
after every w you should see smt like the partition table has been altered.
Restart the phone, and in twrp format data you should be ok, NOT FOR FLASHING NAOSP, IF YOU WANT TO FLASH NAOSP:
fdisk /dev/block/mmcblk0
n
42945
477120
t
14
83
write w

Thank you for your reply. I tried it but after i typed 42945 it asks for another letter while you instruct that i have to use 108480, it doesn't accept this number.
But anyway i gave up on repartitioning. I found out how to go back to stock android and i maybe will try later again but i need to be reachable right now.
Anyway thanks for your reply