Develop Bugs

AT&T Fusion 2 U8665 Root - General/Q&A

I will be editing this post, and organizing everything, so stay put.
EDIT: I am no longer using my Fusion 2 as my primary phone, but I will still be able to update this thread. If you need any help, just post here, or shoot me a PM.
Links and Guides
Root your Fusion 2
Installing CWM 6
How to install CM7.2
Q&A
Q1.How do I root my phone?
A1.There are several ways to root your phone.
Shagerty's Guide
RoboticBuddy's Guide
Q2.How do I install a Custom Recovery?
A2. User Oct3178 has discovered that the Y201 CWM works with our U8665. Check out his post here, and follow "Installing CWM Recovery":
User Shagerty has made a step-by-step guide for installing CWM.
Oct3178's Post
Shagerty's guide
Q3. Are there any ROMs for my phone?
A3. The post in A2 gives you that answer. You can use Huawei Y200 ROMs for the U8665.
RFE has also dumped a pre-rooted stock ROM.
NEW:Shagerty has developed CM7.2 for this device. Please refer to the links above the Q&A.
Oct3178's Post
RFE's Post
Thanks to RFE, who made rooting the Fusion 2 possible!

RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE

RFE said:
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE
Click to expand...
Click to collapse
If you could, please PM me the Rom, so I can add it to the OP.
Thank you,
-RoboticBuddy

Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.

statussticks said:
Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.
Click to expand...
Click to collapse
I do believe that RFE is working on a custom ROM that removes all the CrapWare that was pre-installed on the phone. Hopefully after that, he will be able to start to build CM for it.
If I could, I would attempt to start building CM for the Fusion 2, but I do not know how to setup a build environment.

Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?

Thanks
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys

still bricked
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!

BOOOYA, well done! Rooted WiFi homephone.. thank you!

Lmao, so rad

statussticks said:
Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?
Click to expand...
Click to collapse
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
ericrazy2000 said:
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys
Click to expand...
Click to collapse
sinco54 said:
BOOOYA, well done! Rooted WiFi homephone.. thank you!
Click to expand...
Click to collapse
gigilie said:
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!
Click to expand...
Click to collapse
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:

RoboticBuddy said:
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:
Click to expand...
Click to collapse
I hope so, i bought this phone at frys for 59.99 on a crazy 1 day sale for no good reason. lol... Its actually a pretty little impressive piece for the price and a custom bare bones aosp/aokp/cm would be the meow meow!!! cool little phone for sure!!

I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..

statussticks said:
I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..
Click to expand...
Click to collapse
A working twrp would be straight drug deala pimp style.. I'm gonna reach out to a couple of devs that may be willing to help out but I don't know, I may have to get him loaded and bribe him with cheap hookers. Also, if you go for it and your phone explodes into puppies then is be willing to help on a 2 device for development.. ill run by frys and see if they are on sale or if I can weasel the sales guy into hookin a sale price up today after I close the store.. stand by sweetie pie.
Sent from my HTC One XL using xda premium

Got Root/Trying to build CWM
sinco54 said:
Lmao, so rad
Click to expand...
Click to collapse
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)

Shagerty said:
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)
Click to expand...
Click to collapse
I'm trying /a friend of mine/ is to get a twrp to function..
Also, these phones were on sale at Fry's again but were 79.99.. I picked 1 more up solely for development.
Sent from my One X using xda premium

Thank you! Rooted my phone without any problems following your instructions!
Probably it is a wrong place to ask such questions, but could you point me to any information how to unlock network on this phone (currently it is locked for AT&T, and can be used with their SIM cards only)?
Thank you!

I'm still looking for that info too...
Sent from my HTC One XL using xda premium

Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup and Root Uninstaller to remove AT&T apps.

Aknodx said:
Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup to remove AT&T apps.
Click to expand...
Click to collapse
Where did you buy the unlocking code?

T999L, failed unlock - now no imei, baseband nor nv_data

My tail of woe. From what I have read there is nothing that can be done but I thought I would ask anyhow.
I was overseas with an SGH-T999L, and took it to a man in a market to be unlocked. 2 hours later it was useless. The man said it would be OK once it was back in the US, but it wasn't. Obviously he didn't keep backups.
Dialing *#06# gives me "null/null".
I cannot turn on wifi (I slie the switch and it slides right back) but can turn on bluetooth, gps and nfc.
Baseband version is "Unknown"
Build number is JSS15J.T999LUVUBNC1
It appears that he used vRoot to get root.
According to the "odin screen"
CUSTOM BINARY DOWNLOAD: No
CURENT BINARY: Samsung Official
SYSTEM: STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
I used this article from techglobal101.wordpress.com 2013/05/02/how-to-solve-no-service-on-samsung-galaxy-s3/ following the imei already corrupt steps to generate
the text file with the imei in it. However the NV Reader/writer has problems. Firstly *#7284# only gives me a choice of "Modem" or "PDA". However *#0808# does give me more options including "RMNET + DM + MODEM". The bigger problem is that the SPC code of 000000 is not accepted, so NV reader/writer can not access anything.
Looking in the /efs filesystem (using "adb shell" and "su" and "busybox find /efs -size +1000k" ) does not find any files larger than 1MB (I believe the nv_data.bin should be at least 2MB) so no original ".nv_data" file, no "nv_data.bin" nor "nv_data.bak". There are smaller files, for example there is a file /efs/imei/mps_code.dat, 3 bytes long containing TMB. The /efs partition is 13716 blocks in size and is only 33% full (4556 blocks in use).
I can use adb to install and uninstall packages, and copy files.
Things which look interesting to me in the output of "getprop" are (with a valid sim card installed)
[DEVICE_PROVISIONED]: [1]
[gsm.operator.alpha]: []
[gsm.sim,state]: [NOT_READY]
[gsm.sim.unknownready]: [1]
So far I have not done anything else. In particular I have not tried using ODIN to download a stock image, nor have I tried removing the files which are in /efs.
I also have not tried creating a 2MB file of NUL characters called /efs/nv_data.bin in the hope that that would at least advance the solution.
I would be pleased to get any good advice on what to do next. Please assume I know my way around a unix command prompt, but this is my first venture into the world of Android.

First thing, don't mess with the efs. It's not relevant to the issue at hand and sounds to be just fine. Most of the NV Data is stored on different partitions. Don't assume its the same as on other devices like many others seem to advise.
Second, download your stock firmware (NC1)(root66 firmware is ok), flash via Odin on your computer, and factory reset (will wipe internal sd). This often fixes these problems without having to touch the NV data.
Something tells me that whoever you took it to may have tried to flash the 4.1.1 modem to use our free unlock method. If so, that will cause the exact same thing you are experiencing now.
If after that it is still not fixed, PM me and I will try to help get your imei restored. We are not allowed to post information, tools, links or further discuss that here, so if it comes to that, I can only help you via PM.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] /data partition keeps getting corrupted

As the title says, the /data partition keeps getting corrupted on my SGH-i317 (AT&T model). It manifests itself as random lockups and reboots, eventually ending up in a no-boot condition. At this point I boot into Philz recovery and use an adb shell to run e2fsck, which fixes a bunch of things and then I can boot normally. This has happened three times in the last month. The first time it happened I was running CleanROM JB, and at that point I upgraded to dicksteele's DS-NE5v1, so I don't think the ROM is to blame. Any idea what could be doing this and/or how to prevent it? Could it be that the FLASH ram is failing? Is there a way to force an fsck at every boot?

Perhaps I spoke too soon...the phone locked up on me last night while we were both asleep (i.e. I woke up, the phone didn't, so I had to yank the battery). The first thing I did was an e2fsck, and it was clean, which leads me to think that the lockups are causing the corruption instead of the other way around.
A little more history: when I was on CleanROM there were no random lockups or reboots, it was a particular app that caused them when I would run it. I tried to uninstall that app, which caused more lockups/reboots, then becoming reboots just opening the Application Manager or trying to uninstall it with Titanium Backup, eventually ending up in a no-boot scenario. After a couple day's worth of pulling my hair out trying to install various recoveries and flashing new ROMs, I determined that it was a corrupted /data partition, found an article on how to e2fsck it and ended up on DS-NE5v1 (the last ROM I tried in the previous step). At that point I had random lockups/reboots until it eventually went no-boot again after a couple weeks. I've since gone through the same cycle twice, having to run an e2fsck to get it booting again.
Any ideas how to diagnose the random lockups?

I am no longer amused: the thing locked up on me again last night, but rebooted just fine after I yanked the battery. Just now it rebooted while sitting untouched on my desk, then rebooted again and locked up at the animated Samsung logo. The e2fsck said this:
Code:
e2fsck -fy /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 377887 has zero dtime. Fix? yes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 378413 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1433114--1433116) -1509879
Fix? yes
Free blocks count wrong for group #43 (22311, counted=22314).
Fix? yes
Free blocks count wrong for group #46 (11952, counted=11953).
Fix? yes
Free blocks count wrong (1075855, counted=1075859).
Fix? yes
Inode bitmap differences: -377887 -378413
Fix? yes
Free inodes count wrong for group #46 (5787, counted=5789).
Fix? yes
Free inodes count wrong (712361, counted=712363).
Fix? yes
/dev/block/mmcblk0p16: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p16: 24917/737280 files (3.6% non-contiguous), 1871209/2947068
blocks
Has anyone seen this behaviour before in DS-NE5v1 or any other ROM?

Mostlyhrmlss said:
I am no longer amused: the thing locked up on me again last night, but rebooted just fine after I yanked the battery. Just now it rebooted while sitting untouched on my desk, then rebooted again and locked up at the animated Samsung logo. The e2fsck said this:
Code:
e2fsck -fy /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 377887 has zero dtime. Fix? yes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 378413 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1433114--1433116) -1509879
Fix? yes
Free blocks count wrong for group #43 (22311, counted=22314).
Fix? yes
Free blocks count wrong for group #46 (11952, counted=11953).
Fix? yes
Free blocks count wrong (1075855, counted=1075859).
Fix? yes
Inode bitmap differences: -377887 -378413
Fix? yes
Free inodes count wrong for group #46 (5787, counted=5789).
Fix? yes
Free inodes count wrong (712361, counted=712363).
Fix? yes
/dev/block/mmcblk0p16: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p16: 24917/737280 files (3.6% non-contiguous), 1871209/2947068
blocks
Has anyone seen this behaviour before in DS-NE5v1 or any other ROM?
Click to expand...
Click to collapse
More than likely, there is a way to run the command as a script at boot. You can run just about anything as a script at boot using script manager & terminal emulator.
However, have you checked your chip? Some of them had SDS (Sudden Death Syndrome, aka Brick Bug) as I'm sure you're aware. There's an app called eMMC Brickbug Check you can use to check your chip.
Also, when was the last time you formatted data in recovery? Are you getting any errors like UIDs inconsistent or anything?
I don't know much about the e2fsck, but I'm sure if I were to run it right now on my perfectly running phone, it would return similar results. Honestly, IMO, random reboots, crashes, and boot failure sounds like a kernel problem to me. I don't know if you've tried yet, but it might be worth it to try a different kernel.

Without exception, the e2fsck comes back clean when the thing will boot, comes back dirty when it won't, and always boots afterwards. The check needs to be done with the partition unmounted. Since any script would be run from the /system tree, the /data partition would have to be mounted in order to read the script in the first place. Reminds me of something about a chicken and an egg
I formatted the partition when I installed DS-NE5v1, a couple months ago, right before the random problems started.
The eMMC Brickbug came back clean with a sane chip. I did notice that it reported the model as t0lteuc, it is a t0lteatt. Is that anything to be worried about?
The kernel is AGNi 3.0.101-India-v4.2.3_R2-OC-LTE-KitKat. Is there something better?

Mostlyhrmlss said:
Without exception, the e2fsck comes back clean when the thing will boot, comes back dirty when it won't, and always boots afterwards. The check needs to be done with the partition unmounted. Since any script would be run from the /system tree, the /data partition would have to be mounted in order to read the script in the first place. Reminds me of something about a chicken and an egg
I formatted the partition when I installed DS-NE5v1, a couple months ago, right before the random problems started.
The eMMC Brickbug came back clean with a sane chip. I did notice that it reported the model as t0lteuc, it is a t0lteatt. Is that anything to be worried about?
The kernel is AGNi 3.0.101-India-v4.2.3_R2-OC-LTE-KitKat. Is there something better?
Click to expand...
Click to collapse
Well as for agni, 4.23 is kinda old. I know he's since put out 4.24 and 4.25 for our note 2. A new onewith multiroom support was released today so I'll be testing that. To me the most stable versions are 4.24 and 4.25. But if you flash a new kernel be sure to wipe your init.d folder or you will have issues. I do it even when updating the same kernel just to be sure.
As for the build prop I'm not sure what tolteuc is, that is clearly a different country code... but i dont think it's a problem. International would be toltexx and at&t is tolteatt. But that's a rom thing, like mine currently has an s5 build prop so mine says klteatt and kltexx. If you're concerned about it, you can dig into your build prop and the files in your CSC folder. Sometimes these have conflicting information in them which can be a problem (but usually isn't)... sometimes people need to get correct CSC for their country or device and if they're having problems it can help to set the build prop to your original defaults (after making a backup, of course).
Running that command fixes whatever problems your having temporarily. Ok well that's good but you don't want to be running it all the time either. The best way in this case to test your memory & chip without replacing it or running a command constantly would be to Odin back to stock for a little while to see if it's still a problem.
Imo, you can start seeing problems on one rom and despite wiping & wiping, it can still carry over to any subsequent roms you flash. When you see a certain problem consistently, you need to take it back to stock because that's the only way to reset everything back to a clean slate... and if you still have the problem there & then you know it's probably hardware. However, I think it'll resolve whatever is causing these issues and you will be free to flash whatever you want after that. It's worth a try, better than trying to run a script at boot every boot.
This is all just my opinion and what I would do. I just saw that no one had helped you yet and that shouldn't happen here when you have a legitimate concern and you post in the correct section as you did.

I put in AGNi 4.2.8 today, and it crashed within an hour. I see a stock flash in my future...
BTW, perusing the AGNi Control app I found an option for FileSystems Checking on Boot, which is off by default. I don't suppose it could hurt, am going to try it.
Oh, and I really do appreciate the help...was beginning to think I was talking to myself

Mostlyhrmlss said:
I put in AGNi 4.2.8 today, and it crashed within an hour. I see a stock flash in my future...
BTW, perusing the AGNi Control app I found an option for FileSystems Checking on Boot, which is off by default. I don't suppose it could hurt, am going to try it.
Oh, and I really do appreciate the help...was beginning to think I was talking to myself
Click to expand...
Click to collapse
Lol I was surprised no one had helped yet! Yeah try the check file system setting, if you still have issues, try a stock flash. It's always helped me in the past. Too bad the new agni didn't solve it on its own... but hey maybe that check setting will help. I'm sure you'll get it sorted!

I did the stock flash and everything seems good, no crashes for a couple of days now. Thanks for your help!

Mostlyhrmlss said:
I did the stock flash and everything seems good, no crashes for a couple of days now. Thanks for your help!
Click to expand...
Click to collapse
That's excellent news! Glad to hear it!

Stuck in Safe Mode / Decrypt storage

Hi, a little background first. My phone is s-Off, bootloader is unlocked and I have a been running rooted custom roms since day 1 that I had this phone. I always ran good except that 2 months ago it started rebooting for no reason. I change my rom from InsertCoin to LeeDroid thinking that my help but no change. Now, yesterday was phone rebooted in the middle of playing a YouTube video right into safe mode asking for a password to Decrypt storage which I never encrypted.
I found a few threads about it. Here's what I tried:
- wipe user data: tried that with fastboot erase userdata and also fastboot format userdata, both failed.
- I went into TWRP to wipe data, said it ran successfully but it didn't since all my pictures and other personal files.
- I tried restoring a known working backup I had and it failed too
- fastboot oem lock fails
- fastboot rebootruu reboots in a blackscreen (no HTC logo in the background) then completely reboots back in safemode.
Any idea what I should try next?
Thanks a lot

anyone? I really desperate right now :crying:

stoned99 said:
- I went into TWRP to wipe data, said it ran successfully but it didn't since all my pictures and other personal files.
Click to expand...
Click to collapse
This is working correctly. You need to go into the advanced wipe options, and select Internal Storage to wipe that partition.
Try the "Format Data" option, and see if that helps.
stoned99 said:
- fastboot oem lock fails
Click to expand...
Click to collapse
I don't ever recommend doing this on an s-off device (for troubleshooting purposes). It doesn't enable anything that isn't already enabled under s-off (running RUUs is the most common reason); but can leave you stuck unable to do a heck of a lot of things (installing custom recovery, ROMs, etc.).
Does your version have an RUU that you can try?

redpoint73 said:
This is working correctly. You need to go into the advanced wipe options, and select Internal Storage to wipe that partition.
Try the "Format Data" option, and see if that helps.
I don't ever recommend doing this on an s-off device (for troubleshooting purposes). It doesn't enable anything that isn't already enabled under s-off (running RUUs is the most common reason); but can leave you stuck unable to do a heck of a lot of things (installing custom recovery, ROMs, etc.).
Does your version have an RUU that you can try?
Click to expand...
Click to collapse
thanks a lot for the reply. I tried the format option. Typed yes in the field. It said Updating Partitions details.... done. But when I go in the file manager I can see I didn't lose anything. Also if I mount my sdcard (data/media) and delete all the files from my PCs. all the files are being deleted. I rebooted the phone and they are all back.
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something. Tried with the zip file renamed to img file (can't remember the exam name), hboot detected it then asked me if I wanted to update, I select yes by using volume 1, then I saw Update, 1 or 2 second later the phone rebooted in a black screen (not RUU), then rebooted in safe mode again asking to Decrypt Storage.
I tried the info found here http://android-revolution-hd.blogspot.ca/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html but it didn't fix my data partition. Here's the output.
~ # ←[6n/tmp/fsck.ext4 -fn /dev/block/mmcblk0p47
/tmp/fsck.ext4 -fn /dev/block/mmcblk0p47
e2fsck 1.42.9 (28-Dec-2013)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 360574 was part of the orphaned inode list. IGNORED.
Deleted inode 368721 has zero dtime. Fix? no
Inode 426053 was part of the orphaned inode list. IGNORED.
Inode 426055 was part of the orphaned inode list. IGNORED.
Inode 696341 was part of the orphaned inode list. IGNORED.
Inode 712757 was part of the orphaned inode list. IGNORED.
Inode 745473 was part of the orphaned inode list. IGNORED.
Inode 1236999 was part of the orphaned inode list. IGNORED.
Inode 1237006 was part of the orphaned inode list. IGNORED.
Inode 1237021 was part of the orphaned inode list. IGNORED.
Inode 1237022 was part of the orphaned inode list. IGNORED.
Inode 1237036 was part of the orphaned inode list. IGNORED.
Inode 1237043 was part of the orphaned inode list. IGNORED.
Inode 1237046 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1159609--1159624) -(1170414--1170429) -1562594 -(15
65703--1565709) -1704549 -(2531003--2531013) -2743942 -(3047984--3047992) -34477
28 -(4796517--4796523) -6504126 -6504155 -6504168 -6504725
Fix? no
Free blocks count wrong (2592986, counted=2598704).
Fix? no
Inode bitmap differences: -360574 -368721 -426053 -426055 -696341 -712757 -7454
73 -1236999 -1237006 -(1237021--1237022) -1237036 -1237043 -1237046
Fix? no
Directories count wrong for group #52 (27, counted=26).
Fix? no
Free inodes count wrong (1653079, counted=1650912).
Fix? no
/dev/block/mmcblk0p47: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p47: 9897/1662976 files (29.1% non-contiguous), 4058918/665190
4 blocks
Click to expand...
Click to collapse

stoned99 said:
thanks a lot for the reply. I tried the format option. Typed yes in the field. It said Updating Partitions details.... done. But when I go in the file manager I can see I didn't lose anything. Also if I mount my sdcard (data/media) and delete all the files from my PCs. all the files are being deleted. I rebooted the phone and they are all back.
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something. Tried with the zip file renamed to img file (can't remember the exam name), hboot detected it then asked me if I wanted to update, I select yes by using volume 1, then I saw Update, 1 or 2 second later the phone rebooted in a black screen (not RUU), then rebooted in safe mode again asking to Decrypt Storage.
I tried the info found here http://android-revolution-hd.blogspot.ca/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html but it didn't fix my data partition. Here's the output.
Click to expand...
Click to collapse
i would run a full ruu of the dev edition exe in fastboot usb mode and see if that fix the problem

toysoldierq said:
i would run a full ruu of the dev edition exe in fastboot usb mode and see if that fix the problem
Click to expand...
Click to collapse
Thanks. I already tried running the DEV RUU zip file by renaming it to that PXXXIMG.zip without a success. Since fastbootruu doesn't work I can tried it. Regarding the dev edition exe, I can't find it anywhere, only found the zip one. Do you know where I could find it?

stoned99 said:
Thanks. I already tried running the DEV RUU zip file by renaming it to that PXXXIMG.zip without a success. Since fastbootruu doesn't work I can tried it. Regarding the dev edition exe, I can't find it anywhere, only found the zip one. Do you know where I could find it?
Click to expand...
Click to collapse
Right here: http://www.htc.com/us/support/htc-one-m8/news/
But you need to change to the appropriate CID and MID. Plus, if your version's RUU exe didn't work, I don't see how this will be any different.
To be clear, you usually run the RUU in bootloader-fastboot mode, not RUU mode (it will boot to that itself once you run the RUU).
But if you have a fundamental USB connectivity issue, it really doesn't matter, and it still won't run. Try different cables, different USB ports, even another PC.

redpoint73 said:
Right here: http://www.htc.com/us/support/htc-one-m8/news/
But you need to change to the appropriate CID and MID. Plus, if your version's RUU exe didn't work, I don't see how this will be any different.
To be clear, you usually run the RUU in bootloader-fastboot mode, not RUU mode (it will boot to that itself once you run the RUU).
But if you have a fundamental USB connectivity issue, it really doesn't matter, and it still won't run. Try different cables, different USB ports, even another PC.
Click to expand...
Click to collapse
This is not a USB issue. The problem itself seems to be an ext4 corruption issue. When trying to restore my backups, it fails when trying to restore /data/media. I can't delete/format it either. I'll try the RUU exe but doubt it will work. Thanks for the help

stoned99 said:
This is not a USB issue.
Click to expand...
Click to collapse
You said in Post #4:
stoned99 said:
Yes I have a RUU. I ran both using the exe which failed saying it could be an issue with the usb cable or something.
Click to expand...
Click to collapse
I'm not saying the USB connectivity is causing the main Safe Mode/Decrypt Storage issue. But it does seem to be keeping the RUU from running, based on your previous post.
Also, I'm pretty sure I've seen this similar issue posted before (encrypted storage asking for password, when encryption wasn't selected by the user). From what I remember, the format storage option in TWRP (that you already tried) was the solution. But you might just search for those threads, to see if my recollection on the fix is incorrect; or if other fixes were found.

redpoint73 said:
You said in Post #4:
I'm not saying the USB connectivity is causing the main Safe Mode/Decrypt Storage issue. But it does seem to be keeping the RUU from running, based on your previous post.
Also, I'm pretty sure I've seen this similar issue posted before (encrypted storage asking for password, when encryption wasn't selected by the user). From what I remember, the format storage option in TWRP (that you already tried) was the solution. But you might just search for those threads, to see if my recollection on the fix is incorrect; or if other fixes were found.
Click to expand...
Click to collapse
Indeed, I looked at a few posts with that format storage issue and there was basically 2 solutions: 1) format data in TWRP. 2) Repair ext4 filesystem which didn't work either.
PS: Just saw that the link you gave me is for the Sense version, not the Google Edition. That's what I already tried and failed.

stoned99 said:
Indeed, I looked at a few posts with that format storage issue and there was basically 2 solutions: 1) format data in TWRP. 2) Repair ext4 filesystem which didn't work either.
PS: Just saw that the link you gave me is for the Sense version, not the Google Edition. That's what I already tried and failed.
Click to expand...
Click to collapse
You asked for Developer's Edition. Dev Edition and Google Play Edition (GPE) are 2 completely different things. Dev Edition is always Sense.
I've never seen an RUU.exe for GPE.

redpoint73 said:
You asked for Developer's Edition. Dev Edition and Google Play Edition (GPE) are 2 completely different things. Dev Edition is always Sense.
I've never seen an RUU.exe for GPE.
Click to expand...
Click to collapse
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Ok, so I tried that exe already and it didn't work. Any other ideas?

stoned99 said:
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Ok, so I tried that exe already and it didn't work. Any other ideas?
Click to expand...
Click to collapse
do you have teamviewer if so get it and let me help you, message private with the login and password.

stoned99 said:
Oops my bad then. Sorry, probably my bad cold/sinusitis. I'm having a hard time concentrating.
Click to expand...
Click to collapse
Heh, no worries. The last couple weeks have been rough for me (as far as illnesses), as well. And Dev Ed vs. GPE is a fairly common mistake.
Hopefully toysoldierq can help you out. You've tried everything I can think of.

redpoint73 said:
Heh, no worries. The last couple weeks have been rough for me (as far as illnesses), as well. And Dev Ed vs. GPE is a fairly common mistake.
Hopefully toysoldierq can help you out. You've tried everything I can think of.
Click to expand...
Click to collapse
I think he did not do the whole process going back to sense using this 1.54.401.5-W_Splash

toysoldierq said:
I think he did not do the whole process going back to sense using this 1.54.401.5-W_Splash
Click to expand...
Click to collapse
Sorry I'm back now. So what do you think I didn't try? Using the sense exe ruu? I tried it but it failed.
BTW regarding team viewer I'm not sure if that will really help since you won't be able to see my phone. I know how to use adb, fastboot, etc so if you have an idea of what I should try I would sure try it. Thanks a lot

stoned99 said:
Sorry I'm back now. So what do you think I didn't try? Using the sense exe ruu? I tried it but it failed.
BTW regarding team viewer I'm not sure if that will really help since you won't be able to see my phone. I know how to use adb, fastboot, etc so if you have an idea of what I should try I would sure try it. Thanks a lot
Click to expand...
Click to collapse
i have fix m8 phones over teamviewer already son im way ahead of you, if you want me fix the issue let me know or i can tell u what u need to do choice is yours.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset

Ok we can try it over team viewer, give me a few minutes to install it and give you access

stoned99 said:
Ok we can try it over team viewer, give me a few minutes to install it and give you access
Click to expand...
Click to collapse
i gave you the instructions u can try that.

toysoldierq said:
i have fix m8 phones over teamviewer already son im way ahead of you, if you want me fix the issue let me know or i can tell u what u need to do choice is yours.
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
Click to expand...
Click to collapse
Thanks much appreciated.
Would you reboot the phone between each steps? Maybe not because 2 and 3

[GUIDE][XS/XSL]One time re-partitioning for Marshmelow ROM flashing

A Marshmellow based AOSP ROM was recently released by billchen1997. To flash it, re-partitioning of the partition table is required.To do so, following procedure can be used.
Note: This procedure doesn't work with nAOSP 6.0 ROM released by mickybart now, please find the appropriate instructions in ROM thread.
Do make a note of few things though:
Internal storage which can be accessed via PC by selecting "File transfer"option manually after connecting.
Recovery for Me was retained since I had flashed it in fota partition, hence I would recommend flashing recovery in fota partition before hand.
Performing them on PC would be convenient as some calculations are required.
Wiping all partitions before hand is recommended.
Text formatting conventions are used in the code sections to depict different meanings:
Bold : States the commands to be entered on adb.
Italic : States what values, usually which varies user to user, has to be entered at the place.
Underlined : States output shown by a certain command preceding it.
Repeated x/y/z are variables.
As pointed out by @GjorgiDxc, the phone is not directly encrypted. We need to encrypt it manually. To do so, flash only the ROM, without gapps or root, boot into ROM and encrypt the phone. More details can be found here. Encrypting data would make data partition inaccessible in TWRP.
Procedure:
Take backup of Your apps as well as the data from the internal storage (Photos, Music, Video etc) as it will all be wiped.
Boot into TWRP.
Goto mount option and untick all partitions.
On PC, using adb, type out the following commands,
Print the current partition table. Note down the starting cylinder of partition 14, It will be needed further.
Code:
[B]adb shell
fdisk /dev/block/mmcblk0
p[/B]
{
"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"
}
Now delete the sdcard(15) and data(14) partition.
Code:
[B]d
15
d
14[/B]
Create new data partition which uses remaining space.
Code:
[B]n[/B]
[U]First cylinder (xxx-yyyyyy, default xxx): [/U] [I]You have to enter the start cylinder of partition 14 as read in partition table earlier.[/I]
[U]Last cylinder or +size or +sizeM or +sizeK (zzzzz-yyyyyy, default yyyyyy):[/U] [I]Enter the yyyyyy value.[/I]
Print and write the modified partition table. Note down the "Blocks" value of partition 14 here.
Code:
[B]p
w[/B]
Code:
[U]Command (m for help): [/U][B]t[/B]
[U]Partition number (1-14): [/U][B]14[/B]
[U]Hex code (type L to list codes):[/U][B] 83[/B]
One of the two paths can be followed here now. It depends on which filesystem is required for data partition, ext4 or f2fs. For ext4, follow the first subsection and for f2fs, second one.
Now the calculation needs to be done for ext4 file system. From the "Blocks" value of partition 14, subtract 16, since we have to leave 16384 bytes and each block equals 1024 bytes (16*1024=16384).
For Me, the "Blocks" value of partition 14 was 29161464. Hence, my final value was 29161464-16=29161448. Now divide the solution by 4.
Therefore, 29145080/4=7290362. Consider it as final_size. This many blocks will be allocated for the data partition. This needs to be done since the partition needs to be made using blocks size.
Now we format the data partition such that it acquires the space and as well as leaves the trailing 16384 bytes. This creates a data partition with ext4 type, allocation unit as 4096 and size in blocks as final_size.
Code:
[B]mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p14[/B] [I]final_size[/I]
For f2fs file system, simply run the following command, no need of any calculation:
Code:
[B]mkfs.f2fs -r 16384 /dev/block/mmcblk0p14[/B]
Code:
[B]exit
adb push -p pure_aosp_marshmallow_r1.zip /tmp/[/B]
Now on phone, in TWRP, Flash the ROM via install option, and done!
Notes:
First Reboot is long.
If after boot it says encryption failed, let it reset the phone. Then it will work properly.
For root, flashing Update zip of SuperSU from here works.
Wiping data via TWRP menu will allocate the trailing 16384 bytes to it too, so it is not to be done.
For gapps, flash Pico gapps from here. Then after reboot and login, go to Settings, Apps>Settings icon at top right> App permissions. Now in each permission, open the permission, select show system from options and enable the permission for all system apps.
If You get error like "Error retrieving information from sever.[RPC:C:S-7:AEC-7 CDY7-E3OJ-V2TKC]" in Google Play Store and are not able to install any app, then log out and log in again into Your google account via settings.
If You copy a file and want to access it via TWRP, mount data partition and go to /data/media. Although data won't mount if You encrypt Your phone.
Credits to @SystemR89 for his tutorial as base and billchen1997, @mickybart for his instructions and TWRP.
Calculations are not needed now since micybart has modified the TWRP to leave trailing 16384 bytes at end. The TWRP can be found here.

Thanks for your guide friend. What is difference between this method and your previous method http://forum.xda-developers.com/showthread.php?p=64433804 ? I think your previous method is easier and it's not confusing.
BTW I wiped /data in twrp and I don't have any problem

@Mirhawk so what are you saying Friend? What will be the difference we get than your instruction.will it solve my battery not charching problem.?actually I used mickybarts recovery last time.so was that OK or I have to flash the official twrp to do the job

pejman97 said:
Thanks for your guide friend. What is difference between this method and your previous method http://forum.xda-developers.com/showthread.php?p=64433804 ? I think your previous method is easier and it's not confusing.
BTW I wiped /data in twrp and I don't have any problem
Click to expand...
Click to collapse
The earlier one allocated less space for user. Yeah, I agree, this one is a bit more complicated than previous one, but it is as per some of the instructions provided by billchen1997. Wiping /data with previous process works, but as it wouldn't with this process. I will have to test that if it will work.
nageswarswain said:
@Mirhawk so what are you saying Friend? What will be the difference we get than your instruction.will it solve my battery not charching problem.?actually I used mickybarts recovery last time.so was that OK or I have to flash the official twrp to do the job
Click to expand...
Click to collapse
As said above, it will allocate more usable space for user. Well, modifying of partition should not affect Your offline charging. I used the TWRP by SdtBarbarossa, if it makes any difference.

Why were you saying storage is not accessable via PC? Internal storage shows up fine for me via PC. The only issue I have is with recovery, but there should be a fix to the recovery by mickybart (he is maintaining TWRP) to recognize the new repartitioning, so I can live with that.

GjorgiDxc said:
Why were you saying storage is not accessable via PC? Internal storage shows up fine for me via PC. The only issue I have is with recovery, but there should be a fix to the recovery by mickybart (he is maintaining TWRP) to recognize the new repartitioning, so I can live with that.
Click to expand...
Click to collapse
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Never mind, forgot to select the option for file transfer. Will update that now.

Mirhawk said:
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Click to expand...
Click to collapse
Yes I can. I think after creating partiton14 you should type
t
14
c
I think I did that, but anyway yes i can see the whole 27GB of storage on the computer, and thats how i flash gapps. I flash rom via /tmp and gapps after it boots up. Also maybe you've missed this, but you have to toggle "File tranfer" in the notification shade, the default is "Charging cable" and it doesn't display the internal storage. Pull down notifications, tap on the one bellow USB debugging and select the second option. I'll post some screenshots maybe later, I'm doing some battery testing atm.

GjorgiDxc said:
Yes I can. I think after creating partiton14 you should type
t
14
c
I think I did that, but anyway yes i can see the whole 27GB of storage on the computer, and thats how i flash gapps. I flash rom via /tmp and gapps after it boots up. Also maybe you've missed this, but you have to toggle "File tranfer" in the notification shade, the default is "Charging cable" and it doesn't display the internal storage. Pull down notifications, tap on the one bellow USB debugging and select the second option. I'll post some screenshots maybe later, I'm doing some battery testing atm.
Click to expand...
Click to collapse
Yeah, thanks, the notification doesn't show up on lock screen.
I don't think there is any need to type "c" after creating partition, since it converts the partition to fat32 and it is not needed here.

Mirhawk said:
Yeah, thanks, the notification doesn't show up on lock screen.
I don't think there is any need to type "c" after creating partition, since it converts the partition to fat32 and it is not needed here.
Click to expand...
Click to collapse
I never knew that, still no issues with doing that
So you've missed the notification? You're able to see storage now right?

@Mirhawk try this if it works.connect device to PC.then select file transfer.then goto settings developer option and turn off the USB debugging.it worked for me

Mirhawk said:
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Never mind, forgot to select the option for file transfer. Will update that now.
Click to expand...
Click to collapse
I'm able to access all 27GB in my device and PC. I did everything exactly like you instruction http://forum.xda-developers.com/showpost.php?p=64433804&postcount=1487 till item 4, then I went to wipe menu in twrp and ticked /data partition then pressed on "Repair or change file system" then pressed on resize, then it changed and shows all 27GB then I choose EXT4 then wiped all partitions on my device by twrp, then I did rest of your instruction

Screenshots
 @Mirhawk

GjorgiDxc said:
I never knew that, still no issues with doing that
So you've missed the notification? You're able to see storage now right?
Click to expand...
Click to collapse
nageswarswain said:
@Mirhawk try this if it works.connect device to PC.then select file transfer.then goto settings developer option and turn off the USB debugging.it worked for me
Click to expand...
Click to collapse
Yup, it works for Me, just had to unlock the screen to get notification.
pejman97 said:
I'm able to access all 27GB in my device and PC. I did everything exactly like you instruction http://forum.xda-developers.com/showpost.php?p=64433804&postcount=1487 till item 4, then I went to wipe menu in twrp and ticked /data partition then pressed on "Repair or change file system" then pressed on resize, then it changed and shows all 27GB then I choose EXT4 then wiped all partitions on my device by twrp, then I did rest of your instruction
Click to expand...
Click to collapse
Yeah, it would work that way since the 16384 bytes are left outside the data partition end border in the older procedure. Here, we leave the 16384 bytes inside the end boundary of the data partition. My screenshots after following this procedure with size are attached.

Mirhawk said:
Yup, it works for Me, just had to unlock the screen to get notification.
Yeah, it would work that way since the 16384 bytes are left outside the data partition end border in the older procedure. Here, we leave the 16384 bytes inside the end boundary of the data partition. My screenshots after following this procedure with size are attached.
Click to expand...
Click to collapse
We both did the same but why I lost about 1GB rather than you?

pejman97 said:
We both did the same but why I lost about 1GB rather than you?
Click to expand...
Click to collapse
In the previous method, more than 16384 bytes are left out. There 16384 cylinders*bytes_per_cylinder are left out. Hence there is a difference in size.

Mirhawk said:
In the previous method, more than 16384 bytes are left out. There 16384 cylinders*bytes_per_cylinder are left out. Hence there is a difference in size.
Click to expand...
Click to collapse
Thanks for your instructions it's clear at the the beginning. Now there is no way to use old p15 in this rom until doing like this to use all storage size. That's clear now. So, can I leave about 1G as mmcblk0p15 with vfat system just to flash an update and gapps in the future? Cause all data partition will be wiped if we reset the device.

Can anyone help me? When I try adb in PC, i receive this message: device not found.
I have the phone with TWRP and connected by Usb to the PC.
In the past, i increased the partition for lollipop without problems.
What am i doing bad??
Update:
If I connect the phone with lollipop instead TWRP i can access to the phone without problems. Adb found my de vice attached.

hi, thanks for the detailed instructions. is there any way (command) fo format as f2fs instead of ext4?

jgilalonso666 said:
Can anyone help me? When I try adb in PC, i receive this message: device not found.
I have the phone with TWRP and connected by Usb to the PC.
In the past, i increased the partition for lollipop without problems.
What am i doing bad??
Click to expand...
Click to collapse
Just connect your device to PC and open command. Write (adb devices) if the device doesn't detect while youre device is connected to PC go to advance menu in twrp and open side load and swipe then press cancel then your device should be detected by this command (adb devices)

Ok. I'm gonna try. Thanks