Hi, I've bought a Samsung Galaxy Pocket GT-S5300 and downloaded the italian firmware S5300AILD3 brand Tim. It's composed by one file with extension tar.md5. My question is: is it possible extract the pda, phone, csc, pit and bootloader files from this firmware? If yes, how? Maybe can I use splitfus2?
With winzip i managed to open the file with extension tar.md5, that contains:
Sbl.bin
BcmCP.img
param.lfs
boot.img
system.img
csc.ext4
Unfortunately I can't find them on internet...
Hi, I've bought a Samsung Galaxy Pocket GT-S5300 and downloaded the italian firmware S5300AILD3 brand Tim. It's composed by one file with extension tar.md5. My question is: is it possible extract the pda, phone, csc, pit and bootloader files from this firmware? If yes, how? Maybe can I use splitfus2?
With winzip i managed to open the file with extension tar.md5, that contains:
Sbl.bin
BcmCP.img
param.lfs
boot.img
system.img
csc.ext4
Unfortunately I can't find them on internet...
a last thing: if I select the "Re-partition" and "Update bootloader" options and flash only the file S5300AILD3/S5300TIMLD3/S5300XXLD2/S5300AILD3.tar.md5 with the option PDA of odin, can I do a full flash or would I make a disaster?
marsece said:
Hi, I've bought a Samsung Galaxy Pocket GT-S5300 and downloaded the italian firmware S5300AILD3 brand Tim. It's composed by one file with extension tar.md5. My question is: is it possible extract the pda, phone, csc, pit and bootloader files from this firmware? If yes, how? Maybe can I use splitfus2?
With winzip i managed to open the file with extension tar.md5, that contains:
Sbl.bin
BcmCP.img
param.lfs
boot.img
system.img
csc.ext4
Unfortunately I can't find them on internet...
Click to expand...
Click to collapse
I've checked, SplitFUS2 almost suitable for S5300, but...
It seems, SG Pocket has ext4 fs support and CSC supplied as ext4. SplitFUS2 expecting csc.rfs as the filename, so I modifeied it and uploaded as minor release update SplitFUS v2.01 for Windows/Cygwin version.
Linux comes a bit later...
off topic, but I think Galaxy Toolbox also works on Galaxy Pocket. Could you make and send me a bml15 backup image?
Thank you very much for this version of SplitFUS2
Doky73 said:
off topic, but I think Galaxy Toolbox also works on Galaxy Pocket. Could you make and send me a bml15 backup image?
Click to expand...
Click to collapse
I've installed Galaxy Toolbox, but I can't make the bml15 backup image: when I press SAVE button the program says "bml15 backup saved to /mnt/sdcard/SGYunlock/bml15.img.SAVE", but the folder remains empty. Also, the program can read all the Device Infos, except the "Burnt in model ID" and "IMEI".
marsece said:
I've installed Galaxy Toolbox, but I can't make the bml15 backup image: when I press SAVE button the program says "bml15 backup saved to /mnt/sdcard/SGYunlock/bml15.img.SAVE", but the folder remains empty. Also, the program can read all the Device Infos, except the "Burnt in model ID" and "IMEI".
Click to expand...
Click to collapse
Sad to hear it...
I thought the hardware is almost the same.
Phone rooted, and SDcard was accessible while tested?
Doky73 said:
Sad to hear it...
I thought the hardware is almost the same.
Phone rooted, and SDcard was accessible while tested?
Click to expand...
Click to collapse
Yes, I use "universal root v20" for the root and SuperSu upgrade to version 0.90. RootValidation test says that my phone is complete rootedXP
marsece said:
Yes, I use "universal root v20" for the root and SuperSu upgrade to version 0.90. RootValidation test says that my phone is complete rootedXP
Click to expand...
Click to collapse
ok, I see... Just wanted to be sure, otherwise Galaxy Toolbox also checks root access at start, and exits when no root...
However I'm interested in a version of Galaxy Toolbox for my s5300. If I can do something, please tell me!
marsece said:
However I'm interested in a version of Galaxy Toolbox for my s5300. If I can do something, please tell me!
Click to expand...
Click to collapse
Well, I can't promise anything, but this might help: Download Mobile Odin Lite, and make a dump with. The dump file contains useful info about the partitions
Doky73 said:
Well, I can't promise anything, but this might help: Download Mobile Odin Lite, and make a dump with. The dump file contains useful info about the partitions
Click to expand...
Click to collapse
I sent you a pm message with my mobileodin.txt file
marsece said:
I sent you a pm message with my mobileodin.txt file
Click to expand...
Click to collapse
ok, got it, and examined.
Unfortunately Pocket's partition layout seems quiet different from SGY.
On Galaxy Y the /dev/bml15 partition contains vital data for network locks and bin counter
We have to find similar partition, it might be here somewhere there:
Code:
links:
lrwxrwxrwx root root 2012-06-12 10:00 p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-06-12 10:00 p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-06-12 10:00 p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-06-12 10:00 p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-06-12 10:00 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-06-12 10:00 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-06-12 10:00 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-06-12 10:00 p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-06-12 10:00 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-06-12 10:00 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-06-12 10:00 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-06-12 10:00 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-06-12 10:00 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-06-12 10:00 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-06-12 10:00 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-06-12 10:00 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-06-12 10:00 p1 -> /dev/block/mmcblk1p1
----- partitions -----
major minor #blocks name
179 0 3815424 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 12800 mmcblk0p3
179 4 5120 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 307200 mmcblk0p7
179 8 102400 mmcblk0p8
179 9 1048576 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 2302447 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 256 mmcblk0p13
179 14 256 mmcblk0p14
179 15 1024 mmcblk0p15
259 0 16 mmcblk0p16
179 16 1921024 mmcblk1
179 17 1920955 mmcblk1p1
dumping a suspected partition into file (by dd or cat) and searching for string data like IMEI or carrier identifier might help, but I don't want to instruct it anyone, because it might cause irreversible result.
I've read in Galaxy Ace topics, that dd-ing /dev/bml5 hard bicked the phone (but cat-ing was ok)
So do it on your own risk ;-)
we can exclude
/dev/block/mmcblk0p7 /system
/dev/block/mmcblk0p8 /cache
/dev/block/mmcblk0p9 /data
mmcblk0p3 - suspected modem
mmcblk0p15 has the same size as bml15 ... maybe this is the right one...
If you're brave enough, then try
cat /dev/block/mmcblk0p15 >/sdcard/external_sd/mmcblk0p15.cat_image
(I'm not sure if cat requires busybox or not...)
then examine the file on PC. In hex editor look for IMEI, I'ts maybe at 0x80000...
Interesting post
I was looking for something similar,. but also looking how to flash the firmware
which odin version are u using? thanks
troyaneitor1 said:
Interesting post
I was looking for something similar,. but also looking how to flash the firmware
which odin version are u using? thanks
Click to expand...
Click to collapse
until now I have used odin v1.85 and flashed selecting the entire firmware.tar.md5 under the voice PDA of odin. Another thing: on this forum
http://translate.googleusercontent....=12733&usg=ALkJrhi1SQIo7Y09HFfIyJznTEpoRsz0CQ
I've found these files:
Boot_S5300Xxlc9_Rev04.tar.rar (42.2 KB, 51 views)
Pda_S5300Jplc5_Rev04.tar.part1.rar (50.00 MB, 152 views)
Pda_S5300Jplc5_Rev04.tar.part2.rar (50.00 MB, 200 views)
Pda_S5300Jplc5_Rev04.tar.part3.rar (13.07 MB, 142 views)
GT-S5300-MULTI-CSC-Ojplc5.tar.rar (17.35 MB, 125 views)
Coriemmc_0117.pit.rar (01.01 KB, 33 views)
S5300_Downloader.rar (168.9 KB, 79 views)
I would be interested in download them, but the forum requires a paymentXP...maybe do you know someone that could download them?
Same like u. after opening account it asked to pay
Doky73 said:
mmcblk0p15 has the same size as bml15 ... maybe this is the right one...
If you're brave enough, then try
cat /dev/block/mmcblk0p15 >/sdcard/external_sd/mmcblk0p15.cat_image
(I'm not sure if cat requires busybox or not...)
then examine the file on PC. In hex editor look for IMEI, I'ts maybe at 0x80000...
Click to expand...
Click to collapse
I got the file and send pm. Yes, it contains the IMEI at 0x80000
marsece said:
I've found these files:
Boot_S5300Xxlc9_Rev04.tar.rar (42.2 KB, 51 views)
Pda_S5300Jplc5_Rev04.tar.part1.rar (50.00 MB, 152 views)
Pda_S5300Jplc5_Rev04.tar.part2.rar (50.00 MB, 200 views)
Pda_S5300Jplc5_Rev04.tar.part3.rar (13.07 MB, 142 views)
GT-S5300-MULTI-CSC-Ojplc5.tar.rar (17.35 MB, 125 views)
Coriemmc_0117.pit.rar (01.01 KB, 33 views)
S5300_Downloader.rar (168.9 KB, 79 views)
Click to expand...
Click to collapse
I found a better one free
https://hotfile.com/dl/156305309/e6b7a3d/GT-S5300_PLS_S5300XXLD2_S5300PLSLD1_S5300XXLD2.zip.html
that contains:
BOOT_S5300XXLD2_REV04.tar.md5
DefaultCalDataWithBoot_S5300XXLD2_REV04.tar.md5
GT-S5300-csc-PLSLD1.tar.md5
MODEM_S5300XXLD2_REV04.tar.md5
PDA_S5300XXLD2_REV04.tar.md5
but no pitXP
marsece said:
but no pitXP
Click to expand...
Click to collapse
Theoretically the PIT file is somewhere there on the partitions. On SGY its bml4, which is a 262.144 bytes (a relatively small) partition.
You can check the content of the partitions, the Partition Information Table is one of them, it usually starts with HEX 76 98 34 12
For the moment I found this
76 98 34 12 12 00 00 00 42 72 6f 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 47 41 4e 47 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6d 6d 63 2e 69 6d 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 42 4f 4f 54 00 4c 00 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 42 63 6d 42 6f 6f 74 2e 69 6d 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I've attachted it in a image...maybe could the pit be this?
marsece said:
For the moment I found this
...........
I've attachted it in a image...maybe could the pit be this?
Click to expand...
Click to collapse
Finally I found the coriemmc_0117.pit file on internet...it starts like this but contains more informations; however I tried it on my s5300 in a full flash with odin and all seems to have gone smoothly
Thanks for the info and files
I tried to flash it but i got error message
could u list steps u used to flash files??
thanks
Related
Anybody who know how can help with layout mapping please write here.
Since i don't found Device-specific for GT-S5570 so i made this thread here (CMIIW).
So i've dump bml from the device.
The size each of them is,
Code:
total 502M
-rw-r--r-- 1 root root 218M 2011-03-27 12:41 bml12
-rw-r--r-- 1 root root 189M 2011-03-27 12:40 bml13
-rw-r--r-- 1 root root 29M 2011-03-27 12:39 bml14
-rw-r--r-- 1 root root 25M 2011-03-27 12:40 bml4
-rw-r--r-- 1 root root 9.0M 2011-03-27 12:41 bml5
-rw-r--r-- 1 root root 8.0M 2011-03-27 12:41 bml8
-rw-r--r-- 1 root root 8.0M 2011-03-27 12:41 bml9
-rw-r--r-- 1 root root 6.0M 2011-03-27 12:41 bml11
-rw-r--r-- 1 root root 5.0M 2011-03-27 12:41 bml6
-rw-r--r-- 1 root root 2.0M 2011-03-27 12:41 bml7
-rw-r--r-- 1 root root 1.5M 2011-03-27 12:40 bml1
-rw-r--r-- 1 root root 768K 2011-03-27 12:41 bml10
-rw-r--r-- 1 root root 768K 2011-03-27 12:40 bml3
-rw-r--r-- 1 root root 512K 2011-03-27 12:40 bml2
This is Current Stats :
Code:
BML1 ?
BML2 ?
BML3 ?
BML4 recovery boot ? *contains "recovery" string
BML5 ?
BML6 ?
BML7 recovery boot ? *contains "recovery" string
BML8 Kernel zImage dan initramfs ? *contains arm kernel magic number "2818 016f"
BML9 Kernel zImage dan initramfs ? *contains arm kernel magic number "2818 016f"
BML10 ?
BML12 factoryfs.rfs (/system) *the bigest size
BML13 dbdata.rfs (/dbdata) ? not sure how to test
BML14 cache.rfs (/cache) ? not sure how to test
Hey
I have a S5570L (latin american one) so the BML layout might be different but here's what I've got so far (mind you that my file sizes are different):
Code:
BML1: mibib
BML2: qcsbl
BML3: oemsbl
BML4: amss
BML7: arm11boot
BML8: boot.img
BML9: recovery.img
BML11 is empty (all FFFFFF)
system.rfs is on stl12, userdata.rfs is on stl13 and cache.rfs is on stl14, I also have the efs partition but I can't remember which stl it comes from (I think it's stl5)
That leaves me with six unknown BMLs (5,6,10,12,13,14) and an unknown stl (stl6)
BML10 has some readable code
Code:
COM ON OFF
r.mem=330
console=NULL
fbaddr=0xb8000
RPCCALL
Something to note is that all of those BMLs except 10 begin with the header FSR_STL, I'm thinking that's a filesystem but I don't know what it is.
I'm digging into this 'cause I want to try updating to the european GB but I need a way to backup my phone (particularly the baseband) in order to flash it back with ODIN if the european ROM turns too unstable, borked.
Any help with the BML mapping and my personal query will be greatly appreciated
Akath19 said:
Hey
I have a S5570L (latin american one) so the BML layout might be different but here's what I've got so far (mind you that my file sizes are different):
Code:
BML1: mibib
BML2: qcsbl
BML3: oemsbl
BML4: amss
BML7: arm11boot
BML8: boot.img
BML9: recovery.img
BML11 is empty (all FFFFFF)
system.rfs is on stl12, userdata.rfs is on stl13 and cache.rfs is on stl14, I also have the efs partition but I can't remember which stl it comes from (I think it's stl5)
That leaves me with six unknown BMLs (5,6,10,12,13,14) and an unknown stl (stl6)
BML10 has some readable code
Code:
COM ON OFF
r.mem=330
console=NULL
fbaddr=0xb8000
RPCCALL
Something to note is that all of those BMLs except 10 begin with the header FSR_STL, I'm thinking that's a filesystem but I don't know what it is.
I'm digging into this 'cause I want to try updating to the european GB but I need a way to backup my phone (particularly the baseband) in order to flash it back with ODIN if the european ROM turns too unstable, borked.
Any help with the BML mapping and my personal query will be greatly appreciated
Click to expand...
Click to collapse
Hi, have you guys gotten anywhere with the layout? I have GT-S5570L too and I'm having problems flashing .zip files from ClockworkMod I think it could have something to do with partition layout...
You can get GT-S5570L stock firmwares using CheckFusDownloader (search this forums) just a few days ago Gingerbread has been released for GT-S5570L in Costa Rica and you can even get that version. I have been using it since yesterday and it works great, no connectiviy loss of any kind. For basic backup of system/data there's this nice tool which can be adapted to our phones if we find out the correct partition layout
http://galaxy551.wordpress.com/gearloose/gearloose-backup-manager/
splattx_x said:
Hi, have you guys gotten anywhere with the layout? I have GT-S5570L too and I'm having problems flashing .zip files from ClockworkMod I think it could have something to do with partition layout...
You can get GT-S5570L stock firmwares using CheckFusDownloader (search this forums) just a few days ago Gingerbread has been released for GT-S5570L in Costa Rica and you can even get that version. I have been using it since yesterday and it works great, no connectiviy loss of any kind. For basic backup of system/data there's this nice tool which can be adapted to our phones if we find out the correct partition layout
http://galaxy551.wordpress.com/gearloose/gearloose-backup-manager/
Click to expand...
Click to collapse
What's your problem flashing CWM zips???, 'cause I flashed the Costa Rican ROM you mentioned and had no problem installing either Andro-Id 3.2 or CM7, I also flashed some of my modifications through CWM and had no issues.
Also, CWM does the same kind of backup that gearloose does
From particle.blurringexistence.net
(on Samsung GIO, but I found the same on S5570, apart from STL5 that i do not check...)
Code:
... What you generally see is that BML partitions contain 'static' data (bootloaders, boot / recovery images) and STL partitions contain 'live' filesystem (on android: /system, /data, /cache, /efs, /dbdata)...
On Linux, the kernel exposes both variants of the same device (bml and stl) at the same time through /dev/bmlXX and /dev/stlXX.
BML partition layout:
bml0: contents of the entire flash
bml1: mibib
bml2: qcsbl
bml3: oemsbl
bml4: amss
bml5: block level representation of /dev/stl5 (efs)
bml6: block level representation of /dev/stl6 (empty)
bml7: arm11boot
bml8: boot image
bml9: recovery image
bml10: unknown
bml11: empty (contains only 0xff bytes)
bml12: block level representation of /dev/stl12 (/system)
bml13: block level representation of /dev/stl13 (/data)
bml14: block level representation of /dev/stl14 (/cache)STL partition layout of the Samsung Galaxy Gio GT-S5660:
stl5: /efs
stl6: empty partition (contains only 0xff bytes)
stl12: /system
stl13: /data
stl14: /cache
you can dump this ... I'm studyng how these may be used to make a dump of the device without CWM - that may cause problems on Samsung devices.
I found this in BML0/c
Code:
00081000h: AA 73 EE 55 DB BD 5E E3 03 00 00 00 0E 00 00 00 ªsîUÛ½^ã........
00081010h: 30 3A 4D 49 42 49 42 00 00 00 00 00 00 00 00 00 0:MIBIB.........
00081020h: 00 00 00 00 06 00 00 00 12 10 FF 00 30 3A 51 43 ..........ÿ.0:QC
00081030h: 53 42 4C 00 00 00 00 00 00 00 00 00 06 00 00 00 SBL.............
00081040h: 02 00 00 00 12 10 FF 00 30 3A 4F 45 4D 53 42 4C ......ÿ.0:OEMSBL
00081050h: 31 00 00 00 00 00 00 00 08 00 00 00 03 00 00 00 1...............
00081060h: 12 10 FF 00 30 3A 41 4D 53 53 00 00 00 00 00 00 ..ÿ.0:AMSS......
00081070h: 00 00 00 00 0B 00 00 00 64 00 00 00 12 10 FF 00 ........d.....ÿ.
00081080h: 30 3A 45 46 53 32 00 00 00 00 00 00 00 00 00 00 0:EFS2..........
00081090h: 6F 00 00 00 24 00 00 00 01 11 FF 00 30 3A 4E 56 o...$.....ÿ.0:NV
000810a0h: 42 41 43 4B 55 50 00 00 00 00 00 00 93 00 00 00 BACKUP......“...
000810b0h: 14 00 00 00 01 11 FF 00 30 3A 41 50 50 53 42 4C ......ÿ.0:APPSBL
000810c0h: 00 00 00 00 00 00 00 00 A7 00 00 00 08 00 00 00 ........§.......
000810d0h: 12 10 FF 00 30 3A 41 50 50 53 00 00 00 00 00 00 ..ÿ.0:APPS......
000810e0h: 00 00 00 00 AF 00 00 00 20 00 00 00 12 10 FF 00 ....¯... .....ÿ.
000810f0h: 30 3A 52 45 43 4F 56 45 52 59 00 00 00 00 00 00 0:RECOVERY......
00081100h: CF 00 00 00 20 00 00 00 12 10 FF 00 30 3A 50 41 Ï... .....ÿ.0:PA
00081110h: 52 41 4D 00 00 00 00 00 00 00 00 00 EF 00 00 00 RAM.........ï...
00081120h: 03 00 00 00 12 10 FF 00 30 3A 46 4F 54 41 00 00 ......ÿ.0:FOTA..
00081130h: 00 00 00 00 00 00 00 00 F2 00 00 00 18 00 00 00 ........ò.......
00081140h: 01 10 FF 00 30 3A 53 59 53 41 50 50 53 00 00 00 ..ÿ.0:SYSAPPS...
00081150h: 00 00 00 00 0A 01 00 00 65 03 00 00 01 11 FF 00 ........e.....ÿ.
00081160h: 30 3A 44 41 54 41 00 00 00 00 00 00 00 00 00 00 0:DATA..........
00081170h: 6F 04 00 00 F1 02 00 00 01 11 FF 00 30 3A 43 41 o...ñ.....ÿ.0:CA
00081180h: 43 48 45 00 00 00 00 00 00 00 00 00 60 07 00 00 CHE.........`...
00081190h: 74 00 00 00 01 11 FF 00 FF FF FF FF FF FF FF FF t.....ÿ.ÿÿÿÿÿÿÿÿ
that is
Code:
text Start Lenght Type
MIBIB 00000000 00000600 12 10
QCSBL 00000600 00000200 12 10
OEMSBL 00000800 00000300 12 10
AMSS 00000B00 00006400 12 10
EFS2 00006F00 00002400 01 11
NVBACKUP 00009300 00001400 01 11
APPSBL 0000A700 00000800 12 10
APPS 0000AF00 00002000 12 10
RECOVERY 0000CF00 00002000 12 10
PARAM 0000EF00 00000300 12 10
FOTA 0000F200 00001800 01 10
SYSAPPS 00010A00 00036500 01 11
DATA 00046F00 0002F100 01 11
CACHE 00076000 00007400 01 11
Hi
i have a SGS3 Clone based on MT6575. All the details about it are here .
i have 503MB /data partition
2.09GB /mnt/sdcard partition (it is internal sd card i cannot physically acces it .. its somewhere inside it ..
13.49GB /mnt/sdcard2 which is external sd card 16GB which i have partitioned for link2sd .. and this is the fat32 partition size
and 1.15 GB /data/sdext2 partition which is on external sd card which i created for link2sd it is ext4 partition ..
so the last 2 are the two partitions on my sd card .
i want to Disable altogether the Internal SD Card of 2.09GB (if that doesnt creates any problemm , or if it does creates problem then i want it to be reduced to the minimum) so that all of that space is allocated to /data partition ( or whatever it is which android complains of low disk space .. )
what should i do ?
i have red a thread here but that is with refrence to mt6577 and mine is mt6575 . and i do have its backup obtained through mtkdroid tools and i bricked it once and unbricked it as well .. ( when it was bricked it was total brick it didnt even do anything on inserting the charger)
I am attaching EBR1 EBR2 MBR and scatter file of my device which i obtained through mtkdroid root and tools and the prepared for flash with spf option in mtkdroid tools
and here is the Hex dump of these files which i obtained using ubuntu
[email protected]:~/Desktop/ebr$ hexdump -C -n 64 -s 0x1be MBR
000001be 00 00 00 00 05 00 00 00 20 00 00 00 00 f7 10 00 |........ .......|
000001ce 00 00 00 00 83 00 00 00 20 f7 10 00 00 00 10 00 |........ .......|
000001de 00 00 00 00 83 00 00 00 20 ff 20 00 00 00 10 00 |........ . .....|
000001ee 00 00 00 00 0b 00 00 00 20 07 31 00 ff ff ff ff |........ .1.....|
000001fe
[email protected]:~/Desktop/ebr$ hexdump -C -n 64 -s 0x1be EBR1
000001be 00 00 00 00 83 00 00 00 e0 9e 00 00 00 28 00 00 |.............(..|
000001ce 00 00 00 00 05 00 00 00 e0 ee 00 00 20 00 10 00 |............ ...|
000001de 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001fe
[email protected]:~/Desktop/ebr$ hexdump -C -n 64 -s 0x1be EBR2
000001be 00 00 00 00 83 00 00 00 20 00 00 00 00 00 10 00 |........ .......|
000001ce 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001fe
Click to expand...
Click to collapse
[email protected]:/ # ls -l
ls -l
drwxr-xr-x root root 2013-03-08 14:59 acct
-rw-r--r-- root root 1203 1970-01-01 05:00 advanced_meta_init.project.rc
-rw-r--r-- root root 31482 1970-01-01 05:00 advanced_meta_init.rc
drwxrwx--- system cache 2013-03-08 14:15 cache
dr-x------ root root 2013-03-08 14:59 config
lrwxrwxrwx root root 2013-03-08 14:59 d -> /sys/kernel/debug
drwxrwx--x system system 2013-03-08 14:59 data
-rw-r--r-- root root 177 1970-01-01 05:00 default.prop
drwxr-xr-x root root 2013-03-08 14:59 dev
lrwxrwxrwx root root 1970-01-01 05:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 05:00 [email protected] -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 05:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 05:00 [email protected] -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 05:00 [email protected]_ro -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 05:00 [email protected] -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-08 14:59 etc -> /system/etc
-rwxr-x--- root root 106892 1970-01-01 05:00 init
-rwxr-x--- root root 149 1970-01-01 05:00 init.aee.customer.rc
-rwxr-x--- root root 12077 1970-01-01 05:00 init.factory.rc
-rwxr-x--- root root 2344 1970-01-01 05:00 init.goldfish.rc
-rwxr-x--- root root 3560 1970-01-01 05:00 init.project.rc
-rwxr-x--- root root 26004 1970-01-01 05:00 init.rc
-rwxr-x--- root root 12031 1970-01-01 05:00 init.usb.rc
-rw-r--r-- root root 9148 1970-01-01 05:00 meta_init.rc
drwxrwxr-x root system 2013-03-08 14:59 mnt
dr-xr-xr-x root root 1970-01-01 05:00 proc
lrwxrwxrwx root root 1970-01-01 05:00 res -> /system/res
drwx------ root root 2012-10-10 08:06 root
drwxr-x--- root root 1970-01-01 05:00 sbin
lrwxrwxrwx root root 2013-03-08 14:59 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-03-08 14:59 sys
drwxr-xr-x root root 2013-01-18 15:01 system
-rw-r--r-- root root 272 1970-01-01 05:00 ueventd.goldfish.rc
-rw-r--r-- root root 4388 1970-01-01 05:00 ueventd.rc
lrwxrwxrwx root root 2013-03-08 14:59 vendor -> /system/vendor
Click to expand...
Click to collapse
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0010f720 00100000 "cache"
emmc_p3: 0020ff20 00100000 "usrdata"
emmc_p4: 00310720 004309e0 "fat"
emmc_p5: 00009f00 00002800 "sec_ro"
emmc_p6: 0000ef20 00100000 "android"
Click to expand...
Click to collapse
[email protected]:/ # cat /etc/vold.fstab
cat /etc/vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
## Example of a dual card setup
# dev_mount left_sdcard /mnt/sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host/mmc0
# dev_mount right_sdcard /mnt/sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.2/mmc_host/mmc2
## Example of specifying a specific partition for mounts
# dev_mount sdcard /mnt/sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
Click to expand...
Click to collapse
[email protected]:/ # cat /proc/filesystems
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
yaffs
yaffs2
nodev mtd_inodefs
Click to expand...
Click to collapse
Thanks
Use mini tool partition wizard to do that ... But first make a backup of your data hope that helps ...
Sent from my HTC Explorer A310e
Saumitra Yadav said:
Use mini tool partition wizard to do that ... But first make a backup of your data hope that helps ...
Sent from my HTC Explorer A310e
Click to expand...
Click to collapse
i know i can use minitools to format it as ext4 but then how will the android react to it ? cause its its internal sd card and it mounts it ..
i will prefer the first option i.e. repartition the internal so all sd space is used in /data ...
also have u tried it what was the result .. ?
thanks
khankll said:
i know i can use minitools to format it as ext4 but then how will the android react to it ? cause its its internal sd card and it mounts it ..
i will prefer the first option i.e. repartition the internal so all sd space is used in /data ...
also have u tried it what was the result .. ?
thanks
Click to expand...
Click to collapse
Yea go for the first option ... Nd if you don't want to install a Rom (sense based) then I suggest you to make a fat32 partition
Sent from my HTC Explorer A310e
Please post here the full hexdump of your EBR1 partition so that I can help you.
bgcngm said:
Please post here the full hexdump of your EBR1 partition so that I can help you.
Click to expand...
Click to collapse
how to do that ?
i have posted it in the first post ..
here is some more is it ok >?
[email protected]:~/Desktop/ebr$ hexdump -C EBR1
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001c0 00 00 83 00 00 00 e0 9e 00 00 00 28 00 00 00 00 |...........(....|
000001d0 00 00 05 00 00 00 e0 ee 00 00 20 00 10 00 00 00 |.......... .....|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
Click to expand...
Click to collapse
also i have uploaded those three files .. these are obtained from the set .. first i used mtkdroid root and tools by rua1 to obtain a backup .. then using the same tool i created its spf flashable images .. and these files are those files which are obtained after processing it for flash with spf ..
Okay, then you should change your EBR1 from:
Code:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001c0 00 00 83 00 00 00 e0 9e 00 [COLOR="Red"]00 00 28 00[/COLOR] 00 00 00
000001d0 00 00 [COLOR="red"]05 00 00 00 e0 ee[/COLOR] 00 [COLOR="red"]00 20 00 10[/COLOR] 00 00 00
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
into:
Code:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001c0 00 00 83 00 00 00 e0 9e 00 [COLOR="Red"]ff ff ff ff[/COLOR] 00 00 00
000001d0 00 00 [COLOR="red"]00 00 00 00 00 00[/COLOR] 00 [COLOR="red"]00 00 00 00[/COLOR] 00 00 00
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
In addition, you should also modify vold.fstab so that Android could mount sdcard properly. The following lines should be modified into:
Code:
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
bgcngm said:
Okay, then you should change your EBR1 from:
Code:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001c0 00 00 83 00 00 00 e0 9e 00 [COLOR="Red"]00 00 28 00[/COLOR] 00 00 00
000001d0 00 00 [COLOR="red"]05 00 00 00 e0 ee[/COLOR] 00 [COLOR="red"]00 20 00 10[/COLOR] 00 00 00
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
into:
Code:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001c0 00 00 83 00 00 00 e0 9e 00 [COLOR="Red"]ff ff ff ff[/COLOR] 00 00 00
000001d0 00 00 [COLOR="red"]00 00 00 00 00 00[/COLOR] 00 [COLOR="red"]00 00 00 00[/COLOR] 00 00 00
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
In addition, you should also modify vold.fstab so that Android could mount sdcard properly. The following lines should be modified into:
Code:
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
Click to expand...
Click to collapse
first thanks a lot for your kind help .
second can u share the formula / way how you reverse engineered it ..
now a bit dumb questions .. pardon me for it ..
how to edit EBR1 ?
should i edit it with any hex editor or some specific one ? i checked few hex editors in ubuntu and windows they all disply it in different format then the one which is shown in the above hexdump command output ..
and most importantly what it will do exactly ?
here is what i want it to be ..
i do not want the 2gb /mnt/sdcard partition .. and want to remove it . so the space freed by removing it is then assinged to /data .. so my new /data partition is now
/data should be 503 MB +2.09 GB ( which was earlier used for mnt/sdcard ) .. and i do not want to trick android into treating the external micro sd card or partion /part of it as the internal or /data partition and thereby extremely degrade the r/w speed .. in short i want the external sd card to be irrelevant to above process. is this trick doing it .?
and how to finaly use it for it to effect ?
should i just flash this file EBR1 using SPF and then edit vold.fstab ? and then good to go ? (i have CWMR in this set .. should i also do something in it as well? ) as the thread which mentions this trick for mt6577 is confusing .. though i am trying to decipher that thread .. also i am making the backup using mtkdroid root and tools by rua1
also what are the chances of bricking and recovering it ? i have bricked it few times .. and when it was bricked it was total brick .. no light on pluging charger .. nothing .. on screen no led .. no response to anything .. it seemed its just a fancy brick .. but successfuly unbricked it .. so if it goes into brick .. can i use the nromal unbricking method which i followed above ?
thanks again in millions.
mean while i used winhex editor and edited the file and saved it . then used spf and loaded the scatter file from my backup created with mtk droid root and tools ( and prepared for spf using same tool.. i.e. mtkdroid root and tools by rua1 ) and then unchecked all boxes except ebr1 and specified the path to the modded ebr1 .. then flashed it .. it said ok .. i also had earlier modded the /etc/vold.fstab as above .. and saved it .. and then performed the spf ..
then i rebooted into cwmr and formated /data and /cache and the rebooted .. and got blank black screen .. am i doing something wrong ?
oh i restored it to previous state using the backup i just created before this surgery ...
khankll said:
mean while i used winhex editor and edited the file and saved it . then used spf and loaded the scatter file from my backup created with mtk droid root and tools ( and prepared for spf using same tool.. i.e. mtkdroid root and tools by rua1 ) and then unchecked all boxes except ebr1 and specified the path to the modded ebr1 .. then flashed it .. it said ok .. i also had earlier modded the /etc/vold.fstab as above .. and saved it .. and then performed the spf ..
then i rebooted into cwmr and formated /data and /cache and the rebooted .. and got blank black screen .. am i doing something wrong ?
oh i restored it to previous state using the backup i just created before this surgery ...
Click to expand...
Click to collapse
Did you manage to change the partition sizes?
no all my attempts shown above were un successfull ..
also when i formated the internal sd card with ext2 or 3 or 4 with any tool like minitools.. and the gparted etc and then mounted it android spurted an error of corrupt sd card and wanted to format it .. and it would format it into fat..
anyy help appreciated ..
i would all the space assigned to /mnt/sdcard to be assigned to the /data partition and essientially disable the INTERNAL SD card .. so i can use a big sized external sd card ..
as now all the apps do not see the external sd card . they see the little pesky internal sd card as the only sd card .. . they only see the internal sd card and it is getting filled up and i cannot install more apps ..
or i would even be happy if it is possible to disable the internal sd card (without its space given to /data partition ) so i can use all the external sd card
Mission Impossible
It is not an easy task, for this device, I killed a trying to make this process and still I could not retrieve my device
MauzaoFilho said:
It is not an easy task, for this device, I killed a trying to make this process and still I could not retrieve my device
Click to expand...
Click to collapse
head to this thread for the repair of your dead set.
http://forum.xda-developers.com/showthread.php?t=1943442&page=18
its not that much difficult task . after little tweaking i did managed some success .. doing more work for some more reliable and decent solution.
some work around on the issues were found .. read here
http://forum.xda-developers.com/showthread.php?p=43035540#post43035540
i dealing same problem here
and i did those winhex EBR1, SPF and also end up with blank screen
my gadget always show E (EDGE/2G)
how to enable H /3G?
Hardware : MT6575 (UNIVERSAL5410 is Fake!)
Model : GT-I9500
Build number : JDQ39.I9500ZHUAMDE
Build date UTC : 20130618-102612
Android v : 4.2.2
Baseband v: MAUI.11AMD.W12.22.SP.V17, 2013/05/08 11:12
Kernel v : 3.0.13 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 Tue Jun 18 18:24:15 CST 2013
Hello @ all xda-developers user & team
I have an MTK6582 based phone with internal store size of 0,98GB and phone store of 1,78GB
internal it should be 2.5 GB
is there a way to change the stor size like on the MTK6589??
i search for an easy way like the meteos-mtk6589-rom-edit app / tool
but nothing...
now i read about changing the ebr1 hex, but the example what i found is for mtk6589 and my ebr1 looks a little bit different...
thats how is looks like
000001C0 00 00 83 00 00 00 00 E8 01 00 00 E0 15 00 00 00
000001D0 00 00 83 00 00 00 00 C8 17 00 00 F0 03 00 00 00
000001E0 00 00 83 00 00 00 00 B8 1B 00 00 00 20 00 00 00
000001F0 00 00 05 00 00 00 00 94 01 00 FF FF FF FF 55 AA
if some one could help me I would be very happy
greetings TO
theoverfiend said:
Hello @ all xda-developers user & team
I have an MTK6582 based phone with internal store size of 0,98GB and phone store of 1,78GB
internal it should be 2.5 GB
is there a way to change the stor size like on the MTK6589??
i search for an easy way like the meteos-mtk6589-rom-edit app / tool
but nothing...
now i read about changing the ebr1 hex, but the example what i found is for mtk6589 and my ebr1 looks a little bit different...
thats how is looks like
000001C0 00 00 83 00 00 00 00 E8 01 00 00 E0 15 00 00 00
000001D0 00 00 83 00 00 00 00 C8 17 00 00 F0 03 00 00 00
000001E0 00 00 83 00 00 00 00 B8 1B 00 00 00 20 00 00 00
000001F0 00 00 05 00 00 00 00 94 01 00 FF FF FF FF 55 AA
if some one could help me I would be very happy
greetings TO
Click to expand...
Click to collapse
Hello. I have a THL W100S. The processor is also MTK6582. I made a stupidity, trying to make repartition with meteos-mtk6589 and now my phone is dead
I did not even install CWM
Now I do not know if I can revive it. I tried with SP Flash Tool, but no reaction... Is there any solution to solve this problem?
1. Do a full backup of the current firmware in recovery
2. Install the application, run (on request Root rights answer - YES \ grant)
3. Choose the size of data partition (2.5GB or 2.77GB)
4. Select in the program restarts in recovery
5. Do wipe data
6. Restoring the backup firmware
7. Boot the system
I set 2.77GB, can this be a problem, maybe it was better to choose 2.5GB? After point 5 phone has rebooted and then show only one. This - gifti.me/i/6ylSuEc.gif
theoverfiend said:
Hello @ all xda-developers user & team
I have an MTK6582 based phone with internal store size of 0,98GB and phone store of 1,78GB
internal it should be 2.5 GB
is there a way to change the stor size like on the MTK6589??
i search for an easy way like the meteos-mtk6589-rom-edit app / tool
but nothing...
now i read about changing the ebr1 hex, but the example what i found is for mtk6589 and my ebr1 looks a little bit different...
thats how is looks like
000001C0 00 00 83 00 00 00 00 E8 01 00 00 E0 15 00 00 00
000001D0 00 00 83 00 00 00 00 C8 17 00 00 F0 03 00 00 00
000001E0 00 00 83 00 00 00 00 B8 1B 00 00 00 20 00 00 00
000001F0 00 00 05 00 00 00 00 94 01 00 FF FF FF FF 55 AA
if some one could help me I would be very happy
greetings TO
Click to expand...
Click to collapse
I have the same problem. My phone is a W450 mtk6582.
Many thanks
My phone is an Star W450 to...
@hat3ck
my first try was the meteos-mtk6589 but i have a cwm installed.. ... and the phone didn't boot at least
I fix it by flash all options without preloader
and it's like it was
try to flash again.
greetz TO
theoverfiend said:
My phone is an Star W450 to...
@hat3ck
my first try was the meteos-mtk6589 but i have a cwm installed.. ... and the phone didn't boot at least
I fix it by flash all options without preloader
and it's like it was
try to flash again.
greetz TO
Click to expand...
Click to collapse
Thanks for reply! I tried flashing, but nothing, maybe I don't have the need drivers? Can you make a screenshot of window manage without conected phone? Or how I can verify if my laptop sees the phone...
@hat3ck
try this Tutorial 4 Driver install
(under the red ATTENTION text)
http://forum.xda-developers.com/showthread.php?t=2160490
p.s. whats your home country / language?
Greetz TO
theoverfiend said:
@hat3ck
try this Tutorial 4 Driver install
(under the red ATTENTION text)
http://forum.xda-developers.com/showthread.php?t=2160490
p.s. whats your home country / language?
Greetz TO
Click to expand...
Click to collapse
Thanks, I will try now. Language Romanian, but I can understand and Russian.
okay i dont understand Romanian and Russian. it's like for me. :laugh:
if you run Windows 8 it's a little bit tricky to install the drivers.
Instructions for Win8:
1) Windows Key + X -> Start command prompt (administrator).
2) C: \ Windows \ System32 \ shutdown.exe / r / o
3) Select Troubleshooting
4) Advanced Options
5) Start Settings
6) Restart
7)Disable Driver Signature Enforcement.
Greetz TO
theoverfiend said:
Hello @ all xda-developers user & team
I have an MTK6582 based phone with internal store size of 0,98GB and phone store of 1,78GB
internal it should be 2.5 GB
is there a way to change the stor size like on the MTK6589??
i search for an easy way like the meteos-mtk6589-rom-edit app / tool
but nothing...
now i read about changing the ebr1 hex, but the example what i found is for mtk6589 and my ebr1 looks a little bit different...
thats how is looks like
000001C0 00 00 83 00 00 00 00 E8 01 00 00 E0 15 00 00 00
000001D0 00 00 83 00 00 00 00 C8 17 00 00 F0 03 00 00 00
000001E0 00 00 83 00 00 00 00 B8 1B 00 00 00 20 00 00 00
000001F0 00 00 05 00 00 00 00 94 01 00 FF FF FF FF 55 AA
if some one could help me I would be very happy
greetings TO
Click to expand...
Click to collapse
Hi, you must modify EBR1 and EBR2 like this:
1. EBR1 from:
00 00 83 00 00 00 00 E9 01 00 00 E0 15 00 00 00 00 00 83 00 00 00 00 C9 17 00 00 F0 03 00 00 00 00 00 83 00 00 00 00 B9 1B 00 00 00 20 00 00 00 00 00 05 00 00 00 00 95 01 00 FF FF FF FF 55 AA
to
00 00 83 00 00 00 00 E9 01 00 00 E0 15 00 00 00 00 00 83 00 00 00 00 C9 17 00 00 F0 03 00 00 00 00 00 83 00 00 00 00 B9 1B 00 00 00 50 00 00 00 00 00 05 00 00 00 00 95 01 00 FF FF FF FF 55 AA
2. EBR2 from:
00 00 83 00 00 00 00 24 3A 00 FF 46 C4 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
to
00 00 83 00 00 00 00 24 6A 00 FF 46 C4 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
Flash the files with SPFlashTool. Please make a backup before!! If something go wrong just reflash old EBR1 and EBR2.
Thanks!
mircam said:
Hi, you must modify EBR1 and EBR2 like this:
1. EBR1 from:
00 00 83 00 00 00 00 E9 01 00 00 E0 15 00 00 00 00 00 83 00 00 00 00 C9 17 00 00 F0 03 00 00 00 00 00 83 00 00 00 00 B9 1B 00 00 00 20 00 00 00 00 00 05 00 00 00 00 95 01 00 FF FF FF FF 55 AA
to
00 00 83 00 00 00 00 E9 01 00 00 E0 15 00 00 00 00 00 83 00 00 00 00 C9 17 00 00 F0 03 00 00 00 00 00 83 00 00 00 00 B9 1B 00 00 00 50 00 00 00 00 00 05 00 00 00 00 95 01 00 FF FF FF FF 55 AA
2. EBR2 from:
00 00 83 00 00 00 00 24 3A 00 FF 46 C4 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
to
00 00 83 00 00 00 00 24 6A 00 FF 46 C4 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
Flash the files with SPFlashTool. Please make a backup before!! If something go wrong just reflash old EBR1 and EBR2.
Thanks!
Click to expand...
Click to collapse
so, is it successfull? can you report it and make a n00b tutorial here? thx a lot!
I have a Thl W100S but I can't root it a 100% ! Framaroot says success but after reboot no root access, other software don't root a 100% any suggestions guys? Its the 2nd day I have it latter I will try again, thanks in advance
Sent from my W100 using XDA Premium 4 mobile app
matrix0807 said:
so, is it successfull? can you report it and make a n00b tutorial here? thx a lot!
Click to expand...
Click to collapse
Hi
My ebr1 and ebr2 matches this. I will definintly try this and let you know the result.
My phone is Symphony W128.
Can u root symphony w128
Sent from my Symphony W128 using xda premium
can you post edited files?
Was repartitioning for MTK6582 successful?
Sent from my NOA H42 using Tapatalk
Sargos76 said:
I have a Thl W100S but I can't root it a 100% ! Framaroot says success but after reboot no root access, other software don't root a 100% any suggestions guys? Its the 2nd day I have it latter I will try again, thanks in advance
Sent from my W100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi
try kingroot this version rooted my mtk6582
hey guys i need ur help.i just flashed new firmware android marshmallow 6.0.1 on my D6502 and there was a file called simlock.ta and it just bricked my phone.
1.my phone is working fine but no simcard is valid and my network is completely bricked,
from menu services
bootloader status:unknown
hwconfig:unknown
2.simlock.ta file inside the firmware that i flashed :silly::silly:
Code:
// [SIMLOCK S1]
02
000007DA 0141 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 05 0A 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4F 50
5F 49 44 3D 22 38 35 38 37 22 3B 4F 50 5F 4E 41
4D 45 3D 22 43 75 73 74 6F 6D 69 7A 65 64 20 4D
41 41 22 3B 43 44 41 5F 4E 52 3D 22 31 32 39 31
2D 34 36 37 35 22 3B 52 4F 4F 54 49 4E 47 5F 41
4C 4C 4F 57 45 44 3D 22 31 22 3B 00 00 00 09 00
07 30 30 31 30 31 2D 2A 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 0A 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 00 00 0A 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 02 00 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
3.please avoid telling repeated answers i know all of them .i flashed any firmware from other region but not fixed.i flashed other simlock.ta file from other firmwares but i couldnt find the right simlock.ta and i wanna know what is the correct simlock.ta for my device cause this file inside android 6.0.1 completely reset my network and bootloader status.
4.i was in bootloader unlocked phone but now i cant unlock or relock it when i try to unlock or relock in flashtool or command prompt it says this command is not allowed
5.i can go to flash mode via volume- and power button but my fast boot (volume+ and power button) is not allowed.fastboot damaged and i cant flash any kernel via fastboot or use a recovery mode.
adb mode is not accessible cause no fast boot for my phone.i cant get adb shell from my phone so restoring ta backup is not allowed however i dont have any backup from ta partition.
6.the only solution left that i think it works and that was working for older devices is flashing a simlock.ta on sonyerricson arc,arc s,x10,neo, xperia play or older devices there was a unbrick simlock.ta called "TA brick fix" that we can fix this by flashing but on z2 its not working.please gimme any simlock.ta file that u think it is working for d6502 or tell me a working guide line to fix this issue.
7.i contact my support area but they told me i have to change my main board cause they cant fix it.i know guys there is only problem with simlock.ta only this file damaged my phone and i wanna make the own working simlock.ta back.
8.i am a developer and i know enough about coding and hex editing if u have a deep idea about how simlock.ta hex file works tell me to test it.i dont know what is the right algorithm for simlock.ta on Z2
9.please if u have D6502(L50w)/D6503 Z2 backup ur .ta partition and send it here ill check for solution (Im aware that flashing any other .ta partition from another device can lead me to hard brick,i only want to analyse .ta partitions to find a solution).
.ta partition backup guidehttp://forum.xda-developers.com/showthread.php?t=2292598 :highfive::highfive::fingers-crossed::good:
http://www.4shared.com/zip/aLCY46Xoce/TA-backup-20160423101131.html
Xperia Z2(D6502)
I have same problem with my Xperia U, i have flashed the simlock.ta, after that no network no simcard, bootloader unlock allowed : no
Can't boot to fastboot mode.
Do you find the way fix the problem mind to share with me？
riclim said:
I have same problem with my Xperia U, i have flashed the simlock.ta, after that no network no simcard, bootloader unlock allowed : no
Can't boot to fastboot mode.
Do you find the way fix the problem mind to share with me？
Click to expand...
Click to collapse
No,i contact the sony Co and they said the only way is changing the motherboard with a broken lcd or damaged phone.but still trying to find a way to hack into trim area like 2011 series mobiles
untraceablezing said:
No,i contact the sony Co and they said the only way is changing the motherboard with a broken lcd or damaged phone.but still trying to find a way to hack into trim area like 2011 series mobiles
Click to expand...
Click to collapse
I think this problem hard to hack and fix it, i found the answer is every phone have a unique simlock.ta code, if you didn't back up it, after flash the .ta file, the phone will half brick, don't know how to find back the phone .ta file code, every phone is different
Hi everybody!
Here is my situation:
I have a Xiaomi Redmi Note 4x, snapdragon, 16GB (no unlocked bootloader, no root).
Pictures from my DCMI folder were deleted accidentaly. I would really like to be able to recover them.
But I cannot use tools (PC, or android) to analyze partition for deleted files, unless my phone is root-ed.
And I cannot root the phone unless the bootloader is unlocked, and if I try unlocking the bootloader I lose all data from the phone.
I know some things about smartphones, and I have done some research on my own yesterday.
From what I understand my only option would be to low level backup the internal memory partitions (9GB are left available to the user from the total 16GB).
And then try to recover the pictures from the saved images.
To do that I have to enter EDL Mode using Test Point on the PCB board, then use tools like emmcdl.exe to save the phone partitions.
How can I do this in more detail?
Can anybody confirm that it is indeed possible, and also guide me what to do more precisely, so I can be sure I do not lose any data and still have a try to recover the lost pictures
Would the saved partitions be encrypted?
Backing up user data settings from the phone, using low level, would be very useful for me anyway. so I would be glad to be able to do it, even if I can't recover much of my lost files.
Thanks in advance.
Once data is deleted is impossible to recover on our side u need to send it to lab to recover ur data.. ?
In principle, it should be possible to read out the raw partition images in EDL mode. These guys have done something similar: https://alephsecurity.com/2018/01/22/qualcomm-edl-2/
You can even unlock the bootloader and keep your data, if the Redmi Note 4 still uses the same two bits in the devinfo partition to mark locked/unlocked state.
The big But is: Can you really restore deleted files from a raw ext4 partition, especially once other processes have written to the partition? Because that's what you get.
Please keep me updated what you did and what came out of it. I could not get Alephsecurity's tools to work, but that might be due to Windows driver issues.
The Redmi Note 4 (mido) and Redmi Note 3 (kenzo) still have the bits set at 0x10 and 0x18 in the devinfo partition after unlocking, as described in the alephsecurity blog post. The Redmi Note 5 (whyred) instead has a bit set at 0x90 in an otherwise conspiciously blank partition, so unlocking might work differently there.
Here are the officially unlocked devinfo parititons of a mido, a kenzo, and a whyred:
[email protected]:~/tmp devinfo$ hexdump -C devinfo-mido.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000e0 01 00 00 00 15 53 8a 17 83 99 ce 55 db a2 19 e5 |.....S.....U....|
...
[email protected]:~/tmp devinfo$ hexdump -C devinfo-kenzo.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 01 00 00 00 00 00 00 00 01 00 00 00 01 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000000e0 01 00 00 00 02 00 00 00 57 18 b2 5e 67 10 48 a0 |........W..^g.H.|
...
[email protected]:~/tmp devinfo$ hexdump -C devinfo-whyred.img
00000000 41 4e 44 52 4f 49 44 2d 42 4f 4f 54 21 00 00 00 |ANDROID-BOOT!...|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000090 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00800000
I unlocked officially, installed TWRP/Lineage, booted TWRP, and then I saved the devinfo partition with "adb pull /dev/block/bootdevice/by-name/devinfo devinfo.img".
tijoro said:
The Redmi Note 4 (mido) and Redmi Note 3 (kenzo) still have the bits set at 0x10 and 0x18 in the devinfo partition after unlocking, as described in the alephsecurity blog post. The Redmi Note 5 (whyred) instead has a bit set at 0x90 in an otherwise conspiciously blank partition, so unlocking might work differently there.
Here are the officially unlocked devinfo parititons of a mido, a kenzo, and a whyred:
".
Click to expand...
Click to collapse
Thanks for your replies tijoro.
But I had to recover those files in a day or two, because I had to use my phone, and using it would mean overwriting that info, etc, so I ended up by not recovering them (I don't mind, they weren't that important in the end).
I understand I could have read my user partition in EDL mode, but it would most likely be encrypted data, and MIUI doesn't allow me to set a password (just unlock pattern), so I probably couldn't decrypt it and then try to recover my files.
I didn't check this thread until now since march. I also found that link you gave in your first post, by researching for "edl mode" and unlock
I guess soon I will try and unlock my bootloader with devinfo because unlocking officially would mean losing user data, and I cannot backup many applications user data with MIUI not being rooted.