To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
{
"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"
}
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Thanks ws waiting fr this frm a long tym
Great Guide keep going on...........
@everyone instead of quoting whole OP ..
you can just type @op
The Droid Master said:
Great Guide keep going on...........
Click to expand...
Click to collapse
Usb diagnostics port change next Too many people fall for that
AMAZING GUIDE.... BLOWN MY MIND OFF !!!! :laugh:
good
Related
What tools can be used to decompress/extract the contents of that ROM correctly?
http://www.gigabytecm.com/Russia/Download.aspx?id=91
The device is Gigabyte GSmart S1205.
Any help is appreciated.
im interested too. the osnbtool seems to recognize the four sections however, it crashes.
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
Sector size : 0x00000800
Extra data bytes : 0x00000008
OS IMAGE found.
Partitions infomation:
**************************************
Part-0 type: BOOT SECTION image
Part-1 type: XIP RAM Image
Part-2 type: IMGFS file system
Part-3 type: legit DOS partition
**************************************
flash.bin.PRE written.
-------------------------------------------------
Sector counters (extra-data) found in source file.
Partition 0 true offset:00003EAC true size:001FA173 Len:000007BE
Partition 1 true offset:00000000 true size:0000C478 Len:00000440
Partition 2 true offset:00000000 true size:00000000 Len:0000CAC0
Partition 3 true offset:00000000 true size:00000000 Len:00011440
Click to expand...
Click to collapse
*** the osnbtool stopped here. and windows caught an exception ****
i also tried to prepare_imgfs the flash.bin (with the ff params or combinations of each: -nosplit -acer -mpx200), the operation seems to have succeed everytime as there are no error messages.
However running viewimgf throws an exception (invalid header) and stops.
any help would be greatly appreciated.
flash.bin is signed?
i found this document
the requirement said something about signing the flash.bin? are all bin files signed before flashing to device?
curious, if this only applies to s1205, then is this the reason why osnbtool or other tools cannot dump the ROM?
any help is greatly appreciated.
Rom extraction - only from spec cable:
1. Pinout special contacts under accu:
From left to right: 1- Gnd, 2- Tx, 3-Rx, next symmetric 4 - Rx, 5 - Tx, 6 - Gnd
{
"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"
}
Connect s1205 with Serial->USB to comp.
2. Flasher:
h..p://4pda.ru/forum/dl/post/1011438/SP_Flash_Tool_v1.1110.00_new_mcp.7z
3. run flasher
2. go to tab "Read back"
3. remove all task button "remove"
4. press button "Add"
5. 2 Click on stroke - select where save dump, press "save", in textbox "Length" - write 0х10000000
6. On tab "baudrate" select speed (std 115200 b/s, can 460?)
7. See in comp manag number of com port of cable and write this number in number port in flasher.
8. Press "Read back" and get rom(1) file without ext.
Do not start memory test in flasher!!! it's destroy you s1205.
If anybody need full dump - h...p://www.multiupload.com/ZBKA138KIN (Russian)
previous link is dead
fullflash reupload
new link:
uploadmirrors.com/download/1FBPRTOE/s1205_fullflash.rar
I found an easy method to unlock the i9003.
To do this you will need an Hexadecimal editor and have root access to your phone.
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (I used WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
Locked
{
"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"
}
Unlocked
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
To check it you can do *#7465625# and verify that Network Lock is [OFF]
I hope it can be useful for you.
after installing a new ROM and unlocking like this could the phone read my SIM card normally ?? (i'm in north africa - Tunisia)
Depends if your phone is region locked. Normally it shouldn't be locked, but some carriers with plans lock the phone
Thanks!! It works fine on my phone.
nice job man.. it works fine
Thanks!
It worked perfectly!
It works. Fantastic solution
Nice Work Man!!
Sent from my GT-I9003 using Tapatalk 2
It works! You are a good man
Man my file has only got 2 lines written.... what can be the problem? Im copying the efs folder in my SDcard, then i choose the called file and it has 32 bytes. only 2 lines written.. Any helps?
i cant ...
the file nv_data.bin.md5 reappears after a reboot
aaaaand nothing happens, a password is required for unlock again
can you help?
Can you upload or give to me your file nv_data.bin??
I try to generate to you a pin unlock code.
This is an experiment, unlock code may be not working.
We try to do, it is only a number PIN to insert.
i made it, thanks
but in 68 stroke
Well! How did you do?
Worked like a charm!! Thanks tons!
Hey fyter, can u help me to unlock the region on i9003.
I bought an i9003 from Africa/Tanzania, but the problem is i cant use it in any other country.
I can use any network in Tanzania, but outside of Tanzania its not showing the network.
Also its not even asking any unlock code.
It seems that the region is locked.....
To do this you will need an Hexadecimal editor and have root access to your phone.
FIRST MAKE A BACKUP OF EFS PARTITION!USE GOOGLE FOR HOW-TO
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (like WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
LOCKED
{
"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"
}
UNLOCKED
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
To check it you can do *#7465625# and verify that Network Lock is [OFF]
I hope it can be useful for you.
I AM NOT RESPONSIBLE IF U SCREW UP UR PHONE....IF U DONT DO THIS CORRECTLY,U WILL SCREW UP UR /EFS PARTITION AND YOU WOULD NOT BE ABLE TO USE NETWORK!!
Hi,
this method doesn't work.
The main problem is that this file doesn't exist in I9001.
This method is similar if it is not the same that the one used for I9000 (I'm not sure if is the same address in the file)
Regards
sugggus said:
Hi,
this method doesn't work.
The main problem is that this file doesn't exist in I9001.
This method is similar if it is not the same that the one used for I9000 (I'm not sure if is the same address in the file)
Regards
Click to expand...
Click to collapse
ok...can u attach your /efs folder and pm me?
i am pretty sure all android phones have these files
which files u dont have?
Yep... file nv_data.bin doesn't exist on 9001. Made search on whole phone.
sh!t happens..........................
ok,so any "similar file"?
Hi Sakindia,
this is what I see:
- .files
.dj550 (folder)
empty
.jck12 (folder)
empty
.ssh01 (folder)
empty
keystr (file)
- lost+found (folder)
empty
Ther are 2 folders, the first one has 3 empty folders and one file (keystr) and the second one is empty.
Any solution for us?
Regards
this is /efs partition,right?strange............
sakindia123 said:
this is /efs partition,right?strange............
Click to expand...
Click to collapse
Hi,
yes, this is the /efs folder.
regards
has anyone tried any app?since this doesnt work,thats the last resort
Hi,confirm that it does not work on my phone.
file nv_data.bin doesn't exist
sakindia123 said:
has anyone tried any app?since this doesnt work,thats the last resort
Click to expand...
Click to collapse
hi sakindia, wise forum people, any alternative?
i have root and i9001XXKP4, european Vodafone lock (Spain).
Have been searching and trying out all the free apps available in the market, incl. sgs2 apps. Nothing works.
SGS unlock complains about a busy box error, but i think it just cant find the i9000 file its looking for.
Having to pay for IMEI unlock feels like a defeat... i'm finding out too late that the i9001 is a bit of an unsupported niche thing, i guess.
Hope someone comes up with something!!! Cheers
sakindia123 said:
To do this you will need an Hexadecimal editor and have root access to your phone.
FIRST MAKE A BACKUP OF EFS PARTITION!USE GOOGLE FOR HOW-TO
Steps:
1. Make a full backup of the /efs folder
2. Get the nv_data.bin file located in /efs
3. Open it with an hexa editor (like WinHex)
4. Go to line 181460 and modify from 01 00 00 00 00 to 00 00 00 00 00
5. Copy the modified nv_data.bin file into /efs
6. Set the appropiate owner user and group doing chown 1001.1001 nv_data.bin
7. Remove the nv_data.bin.md5 file
8. Reboot your phone
9. Enjoy!!
LOCKED
UNLOCKED
ADB commands:
# su
# cd /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
# rm nv_data.bin.md5
# chown 1001.1001 nv_data.bin
# reboot
[...]
Click to expand...
Click to collapse
# cp /sdcard/nv_data.bin /efs/nv_data.bin
Really ???
eBug said:
# cp /sdcard/nv_data.bin /efs/nv_data.bin
Really ???
Click to expand...
Click to collapse
oops...my bad
thanks
...could you be a bit more clear? what is the problem with the instructions? thanks in advance.
senor_coconut said:
...could you be a bit more clear? what is the problem with the instructions? thanks in advance.
Click to expand...
Click to collapse
it doesnt matter really since this method doesnt work.....i9001 doesnt have that file!
Hi,we are awaiting a new method..........
sakindia123 said:
it doesnt matter really since this method doesnt work.....i9001 doesnt have that file!
Click to expand...
Click to collapse
Or we don't see it.
promi said:
Or we don't see it.
Click to expand...
Click to collapse
As u say maybe it`s hidden
Try to root your phone and install ES File Explorer from Market.
Maybe u will find it
I know that root is needed to access /efs.
I just stated that maybe this file is hidden somewhere.
EFS doesn't exist in I9001
The problem is that despsite you are toot and you can navigate through this folder, it seems to be almost empty and the NV_DATA.bin is not found inside.
Regards
I recently installed 4.3 MoKee ROM on my At&t's Atrix 2, System 3. Everything works flawlessly.
I'm a bit concerned about size of data.img partition, It's only 1 GB and BMM didn't allow me a greater size.
Is there any way to resize Data.img partition, to make it capable for more apps to be installed? 1 GB sooner or later will be an insufficient space.
Tnx in advance!
I have the same problem, but with PA. I'd love to see a solution.
Sent from my MB865 using XDA Premium 4 mobile app
iNitrox said:
I recently installed 4.3 MoKee ROM on my At&t's Atrix 2, System 3. Everything works flawlessly.
I'm a bit concerned about size of data.img partition, It's only 1 GB and BMM didn't allow me a greater size.
Is there any way to resize Data.img partition, to make it capable for more apps to be installed? 1 GB sooner or later will be an insufficient space.
Tnx in advance!
Click to expand...
Click to collapse
There is a 2000 mb option when u enter BMM click on it make sure u don't have too many systems coz there won't be enough space in the ROM...
Here is a screen shot .......
{
"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"
}
Doesn't seem to be a problem for me ................
Just see if ur BMM recovery version is the same as mine 0.3.4..........
darth_nihar said:
There is a 2000 mb option when u enter BMM click on it make sure u don't have too many systems coz there won't be enough space in the ROM...
Here is a screen shot .......
Doesn't seem to be a problem for me ................
Just see if ur BMM recovery version is the same as mine 0.3.4..........
Click to expand...
Click to collapse
Thanks darth_nihar!, in my case, when i try to create the 2000 mb partition for data.img, this is shown:
This will take some time
(fat32 don't support sparse file)
-
Allocating disk space to image file..
Then, nothing more happens
I'm using System 3, all system/cache/data partitions are destroyed in System 4, 5, and 6.
System 2 is already 'activated'. BMM is v0.3.4
What I am doing wrong? Please help me!
iNitrox said:
Thanks darth_nihar!, in my case, when i try to create the 2000 mb partition for data.img, this is shown:
This will take some time
(fat32 don't support sparse file)
-
Allocating disk space to image file..
Then, nothing more happens
I'm using System 3, all system/cache/data partitions are destroyed in System 4, 5, and 6.
System 2 is already 'activated'. BMM is v0.3.4
What I am doing wrong? Please help me!
Click to expand...
Click to collapse
Same exact problem. Something I found at least helps conserve space is I moved all the apps that I could to my SD card. This saved me about 500 mb of space, so like half.
Sent from my MB865 using XDA Premium 4 mobile app
CreativeSin said:
Same exact problem. Something I found at least helps conserve space is I moved all the apps that I could to my SD card. This saved me about 500 mb of space, so like half.
Click to expand...
Click to collapse
I think that there must be a solution for our problem,
Maybe we need install an earlier version of BMM,
or install those Roms on System 1 (I tried this but didn't work)
I hope somebody may help us!
Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS
migui0401 said:
Hi Guys! I know this is a question that many of you wondered, if in specs sensation is mentioned with four Gigabytes why we just got one?
I used Z test and search for memory on it, and look a this
I wanna anybody explain me this. Seriously. What are those 2.25 Gigabytes doing there? Nothing, are not sytstem storage, are not cache partition, then, what that? I'd appreciate know it and another question, is there any tool or method to get this space into data partition?
ATTACHED THUMBNAILS
Click to expand...
Click to collapse
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!
ivicask said:
2.25GB is devided by data,system,cache some other minor partitions..That app just sums them up in a stupid way.
Just forget about it, you got what you got and there is no way for you to change it!
Click to expand...
Click to collapse
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.
migui0401 said:
Is not just this app, i've seen it by other ways and that is not just data, sytem and cache partition. There are some others partition that app doesnt show apart of those 128 and 256 megabytes, if that MBs where doing something i would care about but are lost doing nothing.
Click to expand...
Click to collapse
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty
rzr86 said:
if i remember well there is a fastboot command which shows you all partitions and their sizes
some partitions are completely empty
Click to expand...
Click to collapse
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
AFAIK we can't repartition emmc as we want
i think it is impossible
migui0401 said:
Yes, there are some partition lost that would give us some excellent extra space in our phone, the command is df and used in terminal in my phone and this is the result
This a big space lost, accepted or not. There is a proof.
Click to expand...
Click to collapse
There is NO space lost, those are "fake" partitions, just kernel mount points, try running same command when phone is not booted from recovery and it will show you real stats, also regardless of all of this we CANT re-partition Sensations nand even if we wanted...So discussion is pointless.