Develop Bugs

Flash ROM using SPL commands

In the Excalibur forum we are struggling to flash a file to a particular offset in NAND (samsung onedisk flash). The file is 4Mbyte and was dumped with bkondisk (by itsme). Deploying pof's ideas, I have patched Excalibur SPL which bypasses vendor/model and signature checking and raises security level to 0. Using this SPL the flash commands can be used w/o restrictions
A similar patched bootloader exists for Vox S710. That SPL includes same commands as the Excalibur SPL.
The SPL offers 2 commands to interactively flash files from MTTY: ls ("load signed"??) and lnbs ("load new binary signed"??)
Afaik the commands are invoked as:
Code:
lnbs [pathname [StartAddr [Length [SkipOffset ["cp"]]]]]
ls [pathname [StartAddr [Length [SkipOffset ["cp"]]]]]
The question is what format the files must have and how to figure out start address. I found some info in the Hermes Wiki. I also suggested Excalibur various tests:
1. The file test3.nbs in this case has a 0x20 byte header ("R000FF") which includes data blocksize and signature size and flag. But somehow it doesn't like the start address of which I also don't know how to figure it out for the various ROM parts. How was that done for Hermes? (reversing SPL or sniffing USB)
Code:
Cmd>lnbs test3.nbs 500a0000
clean up the image temp buffer at 0x8C080000 Length 0x03900000
MTTYDownloadImage "test3.nbs"
:F=test3.nbs
start download
S
HAddress A0000000h Length 0040034Dh
Start Address out of boundary
checking image header
2. The file test.nb w/o any header, just the 4MB binary file with no modifications
Code:
Cmd>ls test.nb 500a0000
clean up the image temp buffer at 0x8C080000 Length 0x03900000
MTTYDownloadImage "test.nb"
:F=test.nb
start download
S
HAddress A0000000h Length 00400000h
Start Address out of boundary
checking image header
3. The file test2.nbh with a full .nbh header and given type 0x300 (GSM Radio code, although the 4MB file also includes config and simlock data etc.). This was actually the most succesful since it passed mosts tests in the SPL. So it seems a valid file, but it couldn't be confirmed that anything was flashed at all.
Code:
Cmd>lnbs test2.nbh 500a0000
clean up the image temp buffer at 0x8C080000 Length 0x03900000
MTTYDownloadImage "test2.nbh"
:F=test2.nbh
start download
S
HAddress 00000000h Length 0040054Dh
Start Address out of boundary
checking image headerFirst MTTY record empty
Image Download Finish... please check your image
Please reset the device to restart the program!!
DownloadImage success.
Can anyone with more knowledge about this subject please drop some feedback? Thx!
Cheers
JockyW
Edit: I totally forgot about the wdata command which is used by the official RUU. It can not be used interactive from MTTY, but it is possible to use it from self written programs. I think the idea is that only signed .nbh files (which include ROM type information in the header) can use be flashed using this command:
Code:
wdata length checksum
Once all data and the last signature (flag == 2) has been sent to SDRAM and all CRC and sig checks are passed the flashing process starts. The funny thing is that the help text of wdata suggests that also unsigned data can be flashed or be dropped at any memory location. Is this intentional deceiving by HTC ??
Code:
Cmd>wdata
Usage:
wdata [StartAddr Len]
Write data to memory(if write to ROM, need erase first).
StartAddr : Start address of memory.
Len : How many bytes will be written.
Length must not more than 0x10000 bytes(buffer limitation).
Write to RAM: 4 bytes(CRC checksum limitation).
1 byte(in user mode).
Write to ROM: 4 bytes(CRC checksum limitation).
2(16-bit)/4(32-bit) bytes(in user mode).
Write to ROM(16-bit data bus): 32 bytes(writebuffer mode).
Write to ROM(32-bit data bus): 64 bytes(writebuffer mode).
Length must be 4 bytes boundary(CRC checksum) if not in user mode.
After command execute, then send out the data to terminal.
Data format: HTCS(4 bytes)+DATA+checksum(4 bytes, if not in user mode)+HTCE(4 bytes).

while flashing test2.nbh, wlan data doesn't be modified.
jockyw2001's question is very important to find our wi-fi back. plz help us!Thanks!
details about our problem and what we have done can be seen at http://forum.xda-developers.com/showthread.php?t=328690

jockyw2001
You may use method imei-check - they for flash of the area CID have changed address of the flash splash screen - hereinafter they form file nbh (consists only of splash screen) with necessary area CID.

arc said:
jockyw2001
You may use method imei-check - they for flash of the area CID have changed address of the flash splash screen - hereinafter they form file nbh (consists only of splash screen) with necessary area CID.
Click to expand...
Click to collapse
Ah great! You've got a link as well? Thx!

Hi jocky,
interesting thing..
why don;t u try its utils for the above and check..
issue pdcocread -l command and get the header and rom address.
then try with lnbs or ls command to flash back.From whatever I know, lnb and lnbs/ls command can b used when yr device is Super CID.
While flahing ROM, RUU issues set le 1 command and write the ROM using wdata command.You can check these things, with USB monitor

hdubli
The commands lnb and lnbs different -
lnb - load the unsigned code.
lnbs- load signed code -have other structure and headline

hdubli said:
issue pdcocread -l command and get the header and rom address.
then try with lnbs or ls command to flash back.From whatever I know, lnb and lnbs/ls command can b used when yr device is Super CID.
Click to expand...
Click to collapse
hi,
pdocread -l returns:
Code:
>pdocread.exe -l
58.82M (0x3ad1000) DSK1:
| 2.09M (0x217400) Part00
| 3.20M (0x333000) Part01
| 53.53M (0x3586800) Part02
59.31M (0x3b4f000) DSK2:
| 59.06M (0x3b0e800) Part00
...
You mean the values in parantheses?
On excalibur only signed data is accepted by ls or lnbs (dunno the difference between the two. Anyone?).
I disassembled spl and found the startaddress boundary check routine. In it I see the hardcoded nand address boundaries which have no resemblance whatsoever with pdocread.
I'm now checking arc's hint to patch splash screen flashroutine in same way as imei-check does it. I just hope I can use ls and lnbs (with USPL of course), since that would be far more comfortable

jasjam Stuck in boot process

I upgraded to WM6 to Schaps_WM6Pro_WWE_4.01_Full.exe after then i tried to go back to
838Pro_HK_ENG_WM6_Upgrade_20070712.zip , the operation stopped on the 20% and
crash Now I just have a 4 color screen showing HERM100 ,IPL-1.04 then HERM100 , SPL-2.03
i have tried to flash more than 12 Rom from wm6 and wm5 with no luck, i have tried to flash
the Radio only ver 1.54 and 1.51 and 1.50 and last 1.47 with no luck all stop and 1%
tried mtty.exe set commend 14 0, 1nb command not available, i think i have Type 2 bricks: Stuck in boot process
mtty output here:
-------------------
Cmd>
Cmd>task 32
CID: Wait interpreter timeout
Level = FF
Cmd>info 2
HTCSF kEØ(HTCE
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x1A900
Partition[3], type=0x4, start=0x1DB00, total=0x1CD00
CE Total Length(with sector info) = 0x3C4D800
CE CheckSum Length(without sector info) = 0x3B60000
Cmd>
-----------------------------------------------------
other info:
Model: jasjam - imate
ROM Before Flash: Schaps_WM6Pro_WWE_4.01
Radio Before Flash: ?
Bootloader Before Flash: 1.04
Flash failed at: 1%
Flashing Radio: 1.54. - 1.51.- 1.47
Bootloader After Failure: 1.04
CID Before Failure Super CID: Yes
CID Corrupt: ??
Radio Corrupt: ??
No GSM Error: Yes
Stuck In Bootloader: ??
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Current Device Status: unusable -cannot boot , can see wm6 green screen before today screen
how can i fix it
many thanks
ehab

Help needed "NO GSM"
Thank you Ehab for bringing this issue, I have the same problem exactly, which happened when I installed Radio 1.54.07.0, which was installed completely, but the JasJam never been able to boot beyond the second splash screen with "No GSM" singe.
I tried the same thing you did and I have the same bad luck!
Heeeeeeeeeeeeeeeelp
Please,
Thank you

Help needed "NO GSM"
I'm wondering why when I do
task 32
I get Level = FF
not Level = 0
as mentioned in the Hermes Upgrade Proplems post
Heeeeeeeeeeeeeeeelp
Please,
Thank you

here is the Solution
My solution for the problem by usnig the SD card method,
get an SD card reader and do the followings:
1- Use your Clean formated SD card (formated as FAT32)
2- find original operating system, extract it with WINRAR, if its not already extracted.
3- When OS extracted, you will have 2 files or more.
4- Look for the file called "RUU_signed.nbh" or similar that ends with ".NBH" (lik "herming.nbh")
5- Copy the "RUU_signed.nbh" file or what ever similar that end with .nbh to the SD card
6- Rename the file to "HERMIMG.nbh"
7- do not use the " " meaning rename it as HERMIMG.nbh
8- Reboot your device to bootloader, (hold Ok button on left side and POWER button at same time and stick with stylus in RESET on bottom).
9- that will start bootloader and in few seconds the falshing will start, it will ask you to confirm flashing on screen by pressing the power button. (screen shot)
10- Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
11- a message will say flashing completed.
12- Do soft reset, volah- device workes.
that worked for me, I hop it will work for you
enjoy

<SOS> - Samsung NAND - KMXEE0A0CM-S600 - Flash Failure !?

Hi There
Diam140 - Olinex:1.93
Used to change ROMs almost everyday - flashoholic. And one bad day a flash failed and after that
Diamond is behaving strangely. Tried 'MTTY'- {task 29} and {task 28} as well. And here is the output
from both:
task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
task 28
Format start
Fill RSVD information for block 288 to 321
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
bad=0x1D20
R:NO bad block reversed for block ID 0x1D20
CorrectNandAddr detect error addr =0x38000000
ERASE FAIL: 0x1D20
W:NO bad block reversed for block ID 0x1D20
Write NAND Faild
Now if the power button is pushed, after 10 minutes device vibrates and comes up with a greyish screen
and after half an hour or so it can be put bootloader. And some times the battery charges with ring
light animation. But flashing any ROM stops at '0%' without any progress and also Hard Reset not
happening - same no progress bar. Checked 'mtty - info 8' and this is what it gave:
info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
OS NOT FOUND !!!
So wanted to change the NAND as above 'samsung_k9k2g08', however Diamond does not use any such chip and
it uses a different combo Nand ROM Memory by the name 'Samsung NAND - KMXEE0A0CM-S600' which is not
possible to change since it is a BGA, atleast with what tools one normally have at home.
Now can someone help reviving the almost bricked Diamond (well some PMs did not do the trick). Any help
is highly appreciated and Thanks in advance

Hi there,
Still stuck with the Device in the same condition. However now this is the output of 'TASK 29 or 28' of late....(given is the end part since it scrolls from the first address)
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FB
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FC
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FD
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FE
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FF
R:NO bad block reversed for block ID 0x7FF
Read sector fail!!!
And also attached the screens for grey screen and HardReset without the progress bar .. can someone help ?

Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
WBR

viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Hi,
Thanks for the response
Yes, tried flashing from bootloader, with no success. Progress bar stops at 0%. And now 'mtty - info 8 and 9' also gives same scrolling output with read error. Any way out ?

viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Was toying with QMAT and bootloader and since the NAND was broken tried 'Write partition to NAND' with 7200A hotfix and after that though the 'task 28 and 29' of mtty were giving the same out of memory errors, the bootloader screen is showing 'DIAM100' instead of 'DIAM140'. Does it give any hope of reviving NAND with some commands either in QMAT or mtty. Well not being a technical person, expecting some engineering inputs/tips.
Thanks in advance.

.... Was just revisiting this thread to see any progress on the query or any solution posted by other members stuck in similar situation, well No Luck... still holding the dead diamond. But then have moved on to a fully customised iPhone 3G 16GB (JB and Unlocked) and may never ever come back to a WinMo and specially an HTC device. Thanks to all those helped directly or indirectly, it was pleasant visiting these pages at 'xda-developers'. Will be visiting these pages to update on the developments in future as well.....

I read your problems. was not to fix this by using J-Tag? me also interested in that topic, I read somewhere that it would be just mentioned J-Tag fix these problems. Sorry but my English is poor.

Hi isaac12,
Glad you are interested in these things, well did not get any tips from the experts of J-Tag. And tried on my own and reported all the results here. Still want to revive the dead diamond, in fact went to the extent of replacing NAND chip but realised it will be a very costly affair and getting the equipment/expertise was also out of question. So it remains dead......

I am in the same situation. I also use flashaolic.

Have a beer, its time to get a new experimental subject.

Help Me Plz..........

I have XDA O2 Orbit ATRE200 HTC INNovation
Tried it 2 flash with Wm6.5 Rom, now it just stucked in bootloader 3 colors showing
IPL 3.04.0001
SPL 1.11.0000
Tried to hard rest but when press send key its shows format failed
after that tried to SD card but wont work just showing checking SD contents but after that enter into bootloader mode nothing happened
tried to use mtty.exe
Cmd>set 32
set 32
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SD clock to 24MHz
***** user area size = 0x3BE00000 Bytes
SDInit---
SDInit OK
g_cKeyCardSecurityLevel = 0
HTCE
but when tried to use commands
Cmd>task 29
task 29
Invalid command : task 29
For a help screen, use command ? or h
Cmd>task 28
task 28
Invalid command : task 28
For a help screen, use command ? or h
Cmd>info 2
info 2
Invalid command : info 2
For a help screen, use command ? or h
etc etc
can any one let me know what i do to get rid from this problem

...
hey, you bricked your device, you need to try and revive it using your original/official/ship rom..
you can find it here:
wiki.xda-developers.com/index.php?pagename=Artemis_Upgrades
when you have your original rom flashed back to the device, do Uspl 1.11.cmon
spl 1.11.0000 checks the size, and failed.. which is why your device is a brick..
spl 1.11.cmon - this means you can flash roms no matter what their size.. its doesnt check it..
(click Uspl 1.11.cmon on my signature to download)

I'm curious if the problem is solved.

i cannot connect my device via activsync so how can i flash it???

How can i put 2 cabs of spl 1.11.cmon in the device? i cannot connect my device via activsync so how can i flash it???

...
cutetaurus, add me to msn messenger..
ill try and help you..
[email protected]

[NooB Guide] Increase Internal Storage of XS/XSL

Attention!​ I know there are already some posts about it. If you find it annoying PLEASE ignore this post. Do Not bother to comment. Just Ignore it.​
Disclaimer: I'm Not Responsible for Anything. If you wish do it as your own risk.​
These things are goning to happen
For the reason of Formating data will be lost - So backup everything to PC
You'll lose google sign in, contacts, messages, social networking etc. - backup before proceed
Things You will Need
Drivers - For Detecting your device properly (Sony Users can use "Flashtool")
ADB - Use mini version. You don't have to install Android SDK for this
USB Cable
CMD - Use "ConEmu" or "Console2" more flexible than cmd. Provides easy copy of text from console
TWRP Recovery - Download it from twrp site
I'm Going to put this assuming you as Novice. So I'll Explain as much as possible
Step 1 -
* Installing flashtool
Download flashtool from the link given above
Install flashtool as usual.
Then from "C:\Flashtool\drivers" install drivers for your phone.
Open Flashtool (Keep it open for this step)
* Phone Detection
After installing drivers - enable "USB debugging" in phone. Connect your phone to pc see if it is detected or not.
If not try doing uninstall & installing flashtool again. If it is not detected yet I shall say "STOP" forget partitioning. Look in the forum for a solution. Fix it and then continue.
If your device detects properly in normal mode then proceed
Turn off phone. Connect USB cable to PC and while pressing volume up button and connect cable to Phone.
A blue light will flash & Driver will install if necessary. In Flashtool window it will show fastboot mode after detecting phone. If not "STOP" try again. Fix it and then continue.
Step 2 - Install mini adb
If you have downloaded mini ADB.exe version install it to root directory of PC for example C:\ADB. Double click to open the .exe when ask for location of install show to C:\ADB
If you have downloaded Mini ADB as .zip/.rar file. Right click on the file> Extract to > C:\ADB
Step 3 - TWRP
Download from the link given above.
Move Downloaded TWRP image such as twrp-3.0.0-0-nozomi.img to ADB folder (C:\ADB)
Rename the file to twrp.img.
(Optional) - also move rom.zip for later use. If you want to install a fresh rom.
Step 4 - Kernel flash
* Flashing Kernel by flashtool
Turn off phone, conncet it to pc while pressing volume + button
open flashtool> flash device (thunder icon)> fastboot> Flash kernel> select twrp-3.0.0-0-nozomi.img
See the flashtool log if it says "OK" then Reboot/start the phone. Otherwise redo this step.
When starting press volume + - button several time it will bring up recovery screen.
* Flashing kernel into Fota Kernel.
You have to Upload the recovery.img into your phone & Flash to do this: Open Command Window by default in windows it is called cmd.
Opening Command window
* By CMD:
Go to ADB folder> Press Shift + Right Mouse button> Open Command window here> it will open a command window
* Using Other console software:
ConEmu or Console2 can't be open this way. You have to use "cd" command to go to adb folder.
In conEmu or console2 write: cd your adb location for example: cd c:\ADB
Now write these in command window-
adb push twrp.img /sdcard/ <<<<---- this will copy twrp.img to your phone sdcard. Remember to change recovery name to twrp.img
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11 <<<<---- this will write twrp to FOTA block of your phone.
** Rebooting phone will bring up recovery screen. In the recovery screen it will ask you whether system should be put into "Read only mode". Don't do that.
** In twrp Go to Mount> deselect System, data, cache, Sdcard and read only system > select again > again Deselect
Before You Procced Any Further Make Sure:
PC can detect your device Normally
PC Can detect device in Fastboot mode
If you really want to do this or not?
Step 5 - Partitioning
[*] Connect USB Cable while in TWRP recovery. (It dosen't matter which screen you are in just Stay in twrp recovery)
[*] Open ADB Folder> Open CMD or ConEmu from there (See Step 4 - opening command window section for this)
Write these command
adb shell <<<<----- it will start ADB
then write
fdisk /dev/block/mmcblk0 <<<<----- It will enable partitioning commands to work
This will bring some info & It will Look Like this:
The number of cylinders for this disk is set to 973824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
**NOTE** " Command (m for help): " will show automatically if you successfuly entered in partitioning mode if not redo steps again.​
Now we need to see each block of default partition and detect SDCARD & Internal Storage: Write this-
p <<<<<<----- This will print or show each partition. Command (m for help): already be there just write p for example Command (m for help): p
It will show this:
Code:
[HIDE]Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help):[/HIDE]
STOP​COPY THESE PARTITIOIN INFO TO A TEXT FILE AND SAVE IT. EVERY PHONE HAS SEPERATE PARTITION SETTING. IF ANYTHING GOES WRONG IT WILL BE NECESSARY TO SEE AND GIVE EXACTLY SAME VALUE TO RECOVER ORIGINAL PARTITION.​
Identifying SDCARD & Internal Storage - From the print output we see lots of blocks and lots of data. But We need to know which partition belongs to which.
/dev/block/mmcblk0p14 <<<---- this is the Internal Storage. See the blocks column its like 2 GB (2097152)
/dev/block/mmcblk0p15 <<<---- this is the SDCARD. Blocks look like it's around 27GB and there is also win95 FAT32 type partition.
As we need to increase Internal Storage Size. From where these extra storage will come from? Well, it's from SDCARD. That's why SDCARD & Internal Storage has to be deleted and repartition again. As for delete do this
d <<<<<---- for deleting partition Command (m for help): d
Partition number (1-15): <<<<---- it will ask which partition you want to delete?
15 <<<<<---- First delete mmcblk0p15
then again give
d <<<<<---- for deleting partition Command (m for help): d
Partition number (1-15): 14 <<<<----- Deletes Internal storage partition which is mmcblk0p14
You can give P command to see whether those partition deleted or not
Command (m for help): p
Now creating new partition for Internal storage. Write
n <<<<<----- this is for creating new partition Command (m for help): n
this will show this:
Code:
First cylinder (769-954240, default 769):
To Understand properly look at this table you generated earlier using p command:
Code:
start end
/dev/block/mmcblk0p13 34945 42944
/dev/block/mmcblk0p14 42945 108480
/dev/block/mmcblk0p15 108481 954240
Here mmcblk0p13 started ended at 42944. mmcblk0p14 started at 42945. And mmcblk0p14 ended 108480 just after that mmcblk0p15 started at 108481. Ending is beginning. Quiet easy actually.
So when asked to put first cylinder: you take mmcblk0p13 end value plus 1 write that in first cylinder. for example if End value of mmcblk0p13 is 2 then first cylinder will be 3. if mmcblk0p13 end value is 1000 then first cylinder value will be 1001. if mmcblk0p13 End value is 42900 then first cylinder Value will be 42901. I think that's enough for understanding.
First cylinder (769-954240, default 769): 42945 [<<<<----- in my case mmcblk0p13 end value is 42944 so first cylinder value is 42945 this will not be same for you. press Enter]
Then it will ask for Last Cylinder value: There is three way to put this in kilobyte, in megabyte or in default size but we have to put + sign before size. For example: +100000k or +4000M or +2000000. Easiest one will be using Megabyte. 4000 megabyte is 4 gb, 8000 is 8GB. By default when partitioning system keep some space for recording partition info that's why we never get full size in Memory card, Hard disk, Flash drive etc. This will also be applied here. If you give +4000M command you will get 3.6GB or 3.7GB Something like that. So calculate give some more to keep it even if you want.
Code:
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
I want my internal storage is around 4GB So I Gave
+4192 <<<<----- Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240): +4192
Now The SDCARD Partition. To create This partition we have to give First cylinder value. As we don't know mmcblk0p14 has which Ending cylinder value. We have to generate the partition table and see. So give the P command.
Command (m for help): p <<<<--- shows partition table. Note the END Value of mmcblk0p14. suppose End value is 170875
Give n command
Command (m for help): n <<<<--- new partition for SDCARD or mmcblk0p15. It will ask for first cylinder
First cylinder (769-954240, default 769): <<<<---- put noted Ending value of mmcblk0p14 + 1 here. (170875+1 = 170876) press enter
Now Last cylinder: Just press enter it will take default
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Change partition type for SDCARD by giving these command.
Command (m for help): t <<<--- t for change partition type.
Partition number (1-15): 15 <<<--- It asks which partition to be changed give 15 for SDCARD/mmcblk0p15
Hex code (type L to list codes): c <<<--- FAT32 from win95 for most compatibility give c to choose this. Do not change to any other system type it might not recognized by PC or even your device. Press enter.
Writing all these changing permanently
Command (m for help): w <<<--- give w for write permission. if successful you'll see these message.
Code:
The partition table has been altered.
Calling ioctl() to re-read partition table
**NOTE** if you see something like below line. Partition is not altered or changed. Redo all steps carefully and properly.
Code:
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Step 6 - Formatting Partition.
Your Partition table redefined or resized only. No Formatting has done yet. Your phone do not read memory unless its properly formatted.
If you wish to use stock or stock based rom DO NOT CHANGE PARTITION FORMAT. It will cause problem even brick. Search around forum for more info about this.
Changing Partition format is good for the Upgraded OS version like lolipop 5.0.0 or 5.1.1 or Marshmallow 6.0.0 to work some features. But not always necessary.
Disconnect Phone from pc> Boot into recovery
Code:
TWRP> Wipe> Advance> Format data, cache, system and SDCARD.
If you want to change Format>
Code:
From TWRP>Wipe>Advance>select system or data or cache> change file format> select desiered one> change.

Nice tutorial...but how to push ROM back to phone

payjo73 said:
Nice tutorial...but how to push ROM back to phone
Click to expand...
Click to collapse
If you Mean Stock ROM Use flash tool.
If you mean a zip file of custom rom use adb command:
adb push something.zip /sdcard/

Hey, I have done the exact same procedure and flashed oneofakind ROM. Now my internal SD card seems to be messed up.
Camera app throws error "insert an SD card before using" error & Gallery app throws error "no SD card detected error"
Kindly HELP !!
ps : I already had TWRP installed, had root access & unlocked bootloader. So started from Step 5 with partitioning steps ! I can see the internal storage of 19GB in settings though.
pps : I searched google extensively but most related solutions had external SD card being used so I couldn't reconcile it with my device (Xperia S)

C0D3FR34K said:
Hey, I have done the exact same procedure and flashed oneofakind ROM. Now my internal SD card seems to be messed up.
Camera app throws error "insert an SD card before using" error & Gallery app throws error "no SD card detected error"
Kindly HELP !!
ps : I already had TWRP installed, had root access & unlocked bootloader. So started from Step 5 with partitioning steps ! I can see the internal storage of 19GB in settings though.
pps : I searched google extensively but most related solutions had external SD card being used so I couldn't reconcile it with my device (Xperia S)
Click to expand...
Click to collapse
You need to allow permissions for letting the app access storage in settings of phone.

Mirhawk said:
You need to allow permissions for letting the app access storage in settings of phone.
Click to expand...
Click to collapse
Thanks.
How do i do that ? I never had to do it earlier. I have installed the ROM multiple times in past year.

C0D3FR34K said:
Thanks.
How do i do that ? I never had to do it earlier. I have installed the ROM multiple times in past year.
Click to expand...
Click to collapse
It's in Settings, Apps>Settings icon at top right> App permissions. This error occurs with Marshmellow ROM's as they some new pemission features. You can check out the link in My signature for more related info

Bro i was following this tutorial but i don't know how mobile got disconnected ?.. Now mobile got damaged it can't able to switch on.. Even pc not detecting.. What should I do now.. Please help???