Develop Bugs

[REF] Partition table on i889.

I was looking for this and could not find it anywhere. So here is what I found
Code:
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
Which translated means:
Code:
Block Device Size Name
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO
/dev/block/mmcblk0p11 268MB TOMBSTONES
/dev/block/mmcblk0p12 1342MB CACHE
/dev/block/mmcblk0p13 1879MB SYSTEM
/dev/block/mmcblk0p14 21.0MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 12.1GB USERDATA

ASK
hey, Do you have stockrom I889?

[Q] Very Broken Note II - partitions, init.d, the works

So, where to start...
I rooted my Samsung Note II, and installed Frosty Jellybean. I was really hoping for the longpress back -> app kill like on cyanogen mod, and started switching roms, till I came across Omega. Not realizing how incompatible it was, I flashed anyway and lost radio. I immediately Odin'd back to stock and got radio back (efs / iemi fine). Then moved on to MyRom. Loved it, it was great, but then noticed duplications on my internal sd card....
the whole /0/ dir for 4.1.2, which at the time I thought was an error on my part from modding.... this is where I take a series of stupid moves
1) formatted the internal sd card with cwm.
2) reflashed odin using the pit file from SGH-t889V from this thread
This significantly hosed my phone, so I spent the weekend trying to understand how I could fix it without paying the warrenty deductible. I did a nandriod restore to a point right before I started modding, and finally got 4.1.1 to come up and not endlessly bootcycle. However, my internal SD card isn't mounting correctly (really at all), and I couldn't figure out how to use the fuse thing to get the vfat partition back and pointed to the right point in /dev/block/mmcblk3p?
So, I've triangled-away, now its a stock piece that
1) has no bluetooth
2) has no radio
3) will not come up as a usb device - the usb doesn't even see its there
-- UNLESS its in download mode, then comes up as a serial device
This leads me to believe that all the instancing scripts / settings that are supposed to run when the device powers on aren't coming up, though the init.d and fstab thingie look right(ish)
So, is this a lost cause - should I just make my claim, or is there some easy Heres-a-raw-dump-of-the-phone thing I have missed, that could get me back up and running?
Thanks,
** UPDATE **
I ran the firmware update through KIES and resolved this.,

So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher

odin restore
RonnieRuff said:
So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher
Click to expand...
Click to collapse
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.

fireupFront said:
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.
Click to expand...
Click to collapse
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium

ktetreault14 said:
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Tried that as well...

if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES

script
rlee008 said:
if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES
Click to expand...
Click to collapse
You're right, I should have run that script then, but now... not so helpful:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/dev/block #
>> no ramdisk <<

wifi
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...

fireupFront said:
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...
Click to expand...
Click to collapse
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...

script
rlee008 said:
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...
Click to expand...
Click to collapse
THe script can't run, /data/media is not writeable
I was able to get parted on the device and got this info:
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
the closest thing to this I've found on the web is here:
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
so it looks like my tombstones are messed up, which makes these logcat msgs make sense
Error kickstart 2029 Requested ID 16, file "/tombstones/qcks/efs1.bin"
39:35.2 Error kickstart 2029 ERROR: function: open_file:80 Unable to open input file /tombstones/

So I re partition ed the tombstone drive and got the vfat back up, but still no radio or bluetooth
Sent from my SGH-T889 using xda app-developers app

[Q] Total Space 10.36GB

While listening to Spotify on my stock N71000 phone (not rooted etc) it locked up. Now it locks up 2 to 5 times a day. I have also noticed My Total Storage Card Space is now 10.36GB. Have restored the phone and still only has the Total 10.36GB with 9.61 Available. My external 64GB card is fine. I have looked at the card on my windows machine with same results.
Any ides?

It is 10.36 from the start.
Try a factory reset.
Sent from my GT-N7100 using xda premium

You won't get full 16 gb from the internal storage..
Everyone has it between 11-10 gb..
Those 5-6 gb as far as I know, they are for system partitions..
Sent from my GT-N7100

yenkoeric said:
While listening to Spotify on my stock N71000 phone (not rooted etc) it locked up. Now it locks up 2 to 5 times a day. I have also noticed My Total Storage Card Space is now 10.36GB. Have restored the phone and still only has the Total 10.36GB with 9.61 Available. My external 64GB card is fine. I have looked at the card on my windows machine with same results.
Any ides?
Click to expand...
Click to collapse
The exact size for user accessible is 11.4GB
Disk /dev/block/mmcblk0: 15.8GB (total storage)
4194kB BOTA0
4194kB BOTA1
21.0MB ext4 EFS
4194kB m9kefs1
4194kB m9kefs2
4194kB m9kefs3
8389kB PARAM
8389kB BOOT
8389kB RECOVERY
92.3MB RADIO
4194kB TOMBSTONES
1434MB ext4 CACHE
2147MB ext4 SYSTEM
587MB ext4 HIDDEN
8389kB OTA
11.4GB ext4 USERDATA (storage left for user)

Unbrick our T989! (need Help with getting a DeBrick.img)

EDIT: we need a T989D user to help us! please if you stumble upon this please read and help us out!
it seems like samsung devices have a new method to unbrick when we get QHSUSB_DLOAD when we plug it into the computer.
http://forum.xda-developers.com/showthread.php?t=2439367 : T999 Galaxy s3 T-mobile
http://forum.xda-developers.com/showthread.php?t=2600869 : I9205 Galaxy mega 6.3
http://forum.xda-developers.com/show....php?t=2624203 : N9005 Galaxy note 3
and it seems like they use the same method but someone has made a debrick.img for their devices specifically, i would love to put up a thread for people for this so we can unbrick our s2's but i dont know how they get their .imgs, i heard that we need someone on a stock rooted rom to be able to make the .img so would anyone be able to show me how to make one of these because i own 3 t989s which i will put one of them to stock if someone can show me how to make the .img.

Trozzul said:
it seems like samsung devices have a new method to unbrick when we get QHSUSB_DLOAD when we plug it into the computer.
http://forum.xda-developers.com/showthread.php?t=2439367 : T999 Galaxy s3 T-mobile
http://forum.xda-developers.com/showthread.php?t=2600869 : I9205 Galaxy mega 6.3
http://forum.xda-developers.com/show....php?t=2624203 : N9005 Galaxy note 3
and it seems like they use the same method but someone has made a debrick.img for their devices specifically, i would love to put up a thread for people for this so we can unbrick our s2's but i dont know how they get their .imgs, i heard that we need someone on a stock rooted rom to be able to make the .img so would anyone be able to show me how to make one of these because i own 3 t989s which i will put one of them to stock if someone can show me how to make the .img.
Click to expand...
Click to collapse
You use clockwork mod recovery on your phone and go to "Install .zip from SD card" then you run the "T999_Partial_Sys_Dump_for_debrick.zip" and that gives you the debrick.img to put to your SD card. Get it from http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 and if you do, please post it! I need a t989 image.. And don't worry about it saying T999, you can rename it to anything. This is just the script that makes the image, its not hardware dependent.. Only the debrick image is that you make.

Lord Zog said:
You use clockwork mod recovery on your phone and "Install .zip from SD card" then you run the "T999_Partial_Sys_Dump_for_debrick.zip" and that gives you the debrick.img to put to your SD card. Get it from http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 and if you do, please post it! I need a t989 image.. And don't worry about it saying T999, you can rename it to anything. This is just the script that makes the image, its not hardware dependent.. Only the debrick image is that you make.
Click to expand...
Click to collapse
alright cool dude i have been told that this file makes the debrick.img i just didnt know if it would work with the s2 but it looks like other people clarified that i should be able to do that when i get home. i might run into a problem though, my S2 has a stuck power button and when i go into cwm it taps on random things and im afraid it will screw me and somehow brick it (i might just factory reset so there's nothing but it could still hit one of the wrong options) , i need to find a way to get CWM touch on it but i have made a thread and nobody has helped me D: do you think From rom manager i can hit the "Install rom from SD card" option and use it on the Debrick file?

alright made a debrick.img and tried the method for the s3 and it didnt work maybe i did it wrong, heres there .img (im not on a rooted stock, is that the reason why?) mediafires being dumb and couldnt upload there: http://d-h.st/KUD sorry about Anonymous uploader i couldn't find the registration page.

Trozzul said:
alright cool dude i have been told that this file makes the debrick.img i just didnt know if it would work with the s2 but it looks like other people clarified that i should be able to do that when i get home. i might run into a problem though, my S2 has a stuck power button and when i go into cwm it taps on random things and im afraid it will screw me and somehow brick it (i might just factory reset so there's nothing but it could still hit one of the wrong options) , i need to find a way to get CWM touch on it but i have made a thread and nobody has helped me D: do you think From rom manager i can hit the "Install rom from SD card" option and use it on the Debrick file?
Click to expand...
Click to collapse
I think in ROM manager it won't mount the partitions correctly, but I'll try it on this end with the file you posted.
Nope. Doesn't work. I'll look at the image in Linux and see whats in the partitions.
OK. So, it should look like this...
# parted /dev/sdb print
Model: Generic Ultra HS-SD/MMC (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB userdata
16 14.8GB 14.8GB 8389kB persist
17 14.8GB 15.7GB 881MB cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
OUR's looks like this..
#parted /dev/sdd print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdd: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
This looks more MS-DOS that Linux file system.. I made it in Windows using the app everyone refers to. I'll do it now in Linux.
update: Still shows what we got. Try to do it again but in CWM.

Lord Zog said:
I think in ROM manager it won't mount the partitions correctly, but I'll try it on this end with the file you posted.
Nope. Doesn't work. I'll look at the image in Linux and see whats in the partitions.
OK. So, it should look like this...
# parted /dev/sdb print
Model: Generic Ultra HS-SD/MMC (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB userdata
16 14.8GB 14.8GB 8389kB persist
17 14.8GB 15.7GB 881MB cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
OUR's looks like this..
#parted /dev/sdd print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdd: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
This looks more MS-DOS that Linux file system.. I made it in Windows using the app everyone refers to. I'll do it now in Linux.
update: Still shows what we got. Try to do it again but in CWM.
Click to expand...
Click to collapse
sooo what should i do then? should i go back to stock reroot it and redo the flashing?

Trozzul said:
sooo what should i do then? should i go back to stock reroot it and redo the flashing?
Click to expand...
Click to collapse
Yeah, but from clockwork mod recovery, and rooted stock, like UVLE1.

Lord Zog said:
Yeah, but from clockwork mod recovery, and rooted stock, like UVLE1.
Click to expand...
Click to collapse
Would this be what you want me to be on? http://forum.xda-developers.com/showthread.php?t=1668502 and that .img was from CWM

Trozzul said:
Would this be what you want me to be on? http://forum.xda-developers.com/showthread.php?t=1668502 and that .img was from CWM
Click to expand...
Click to collapse
No, use uvle1 ICS
http://stockroms.net/file/GalaxyS2/SGH-T989/ICS/SGH-T989_UVLE1_ICS.zip
scroll to the bottom and hit play and use the captcha and get stock ICS.
And that was from CWM? Were you rooted? The file structure looks a lot different.. Maybe the script is extracting from the wrong partition, but I thought the T989 and T989D used /dev/block/mmcblk0 also. Sadly, I don't have another T989(D) to check

Lord Zog said:
No, use uvle1 ICS
http://stockroms.net/file/GalaxyS2/SGH-T989/ICS/SGH-T989_UVLE1_ICS.zip
scroll to the bottom and hit play and use the captcha and get stock ICS.
And that was from CWM? Were you rooted? The file structure looks a lot different.. Maybe the script is extracting from the wrong partition, but I thought the T989 and T989D used /dev/block/mmcblk0 also. Sadly, I don't have another T989(D) to check
Click to expand...
Click to collapse
yeah CWM and rooted. and i heard that we shouldnt flash the stock UVLE1 ics stock because it was bricking other peoples phones?

Trozzul said:
yeah CWM and rooted. and i heard that we shouldnt flash the stock UVLE1 ics stock because it was bricking other peoples phones?
Click to expand...
Click to collapse
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device

Lord Zog said:
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device
Click to expand...
Click to collapse
yeah im on CM 10.2 still, i forgot i still needed to get back to stock, also so when i bricked my other T989 does it matter what rom it was on before? or if it was on stock? so i came from Aokp before, for us to unbrick it does the bricked phone needed to be on stock before? what do you think exactly this .img file does? im thinking it runs the drivers from the SD card?

Lord Zog said:
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device
Click to expand...
Click to collapse
alright flashed that file in odin, heres the Debrick.img From rooted stock also on CWM like last time

Trozzul said:
alright flashed that file in odin, heres the Debrick.img From rooted stock also on CWM like last time
Click to expand...
Click to collapse
hmm. Still doesn't work.. Without having a physical phone to play with, its hard to do it this way.
[email protected]:/home/zog/Downloads# dd if=debrick.img of=/dev/sdg
262144+0 records in
262144+0 records out
134217728 bytes (134 MB) copied, 35.458 s, 3.8 MB/s
[email protected]:/home/zog/Downloads# parted /dev/sdg print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdg: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical

Lord Zog said:
hmm. Still doesn't work.. Without having a physical phone to play with, its hard to do it this way.
[email protected]:/home/zog/Downloads# dd if=debrick.img of=/dev/sdg
262144+0 records in
262144+0 records out
134217728 bytes (134 MB) copied, 35.458 s, 3.8 MB/s
[email protected]:/home/zog/Downloads# parted /dev/sdg print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdg: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
Click to expand...
Click to collapse
Well what else can I do?

Trozzul said:
Well what else can I do?
Click to expand...
Click to collapse
We need to figure out the partition structure and find the right one with the .PIT file, and try to create a proper 8660_msimage.mbn or debrick.img creation.

Oh yeah, try to install BusyBox while rooted, and then try it again. I'm still trying to find partition info. So far I have found aboot, amss, boot, cache, mdm, recovery, rpm, sbl2, sbl3, system, tomb, and tz. I'm missing a few and proper flags and such
Also, in play store, when you get BusyBox, also get Android terminal emulator. Then once those 2 things are installed, run BusyBox and use smart install. Once that's done, you can try to do into Android Terminal Emulator and type
su <enter> It'll ask for SuperUser access, allow it. then
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128 <enter>
When I say <enter>, I mean press enter. Try that.

Okay. We're going a different route. Get this https://mega.co.nz/#!TEthlJYY!cq8cwm3c_ilvZVrGEa9TezmOpIkHbaTgYdctr3bxAl8 Its' from http://forum.xda-developers.com/showthread.php?t=2136738
Unzip it all to its own folder, say, Backup989
Run python-2.7.3, let it install to default folder
attach the phone
then run backup.bat
It will make another folder in this folder we're in called "Backup" Once this is done, you should have 8 or so files, compress them in WinZip or WinRAR and upload that.
Files in folder should be
aboot.mbn
pitfile.pit
partition0.bin
rpm.mbn
smd_hdr.mbn
sbl1.mbn
sbl2.mbn
sbl3.mbn
and maybe 1 more, compress them all into one file and upload to me.
DO NOT run the debrick file in that archive, that IS NOT for our phones and the sectors for writing are probably NOT the same as ours and will overwrite something else that could be important. (EFS/IMEI/ANYTHING!) Only run BACKUP.BAT

Got it. Made a debrick.img manually. Its not perfect and consists of a few messy hacks. I'll fix this up and send you one to try once I look at it and the partitioning in HS-USB 9008 and HS-USB-9006 state. This was a 9008 state, then it was switched to a 9006 state and had 7 partitions. I'll post more in a bit once I get this thing fully running.

Ok, I still need partition info. After flashing in Odin, it seems to not want to boot. I can get in and out of ODIN, but the partition info is bad. I can't enter recovery, nor boot past the boot logo, not the animation, just logo. SAMSUNG, and the one that says TMOBILE S2.. I still need you to do the backup to get proper .PIT file and partition0.bin to fix MBR and the PIT partition at b0p11. But send all the backup files it makes just incase one of mine is bad. Had to use another source for SBL1.MBN...
UPDATE: Ok. After messing more things and tinkering, I can boot. I can't go to recovery tho, but ODIN works and I want to make sure my partition isn't screwed up and that why I can't get recovery. But we got boot! I'm excited. This things been dead for 3 months, and never bothered to try till now.
We need a user with a T989D to do the same as the partition table IS different. Using a PIT from a 989 and ODIN Fail's on the modem/baseband MBN file from a T989D ROM, but using a T989 ROM flashes fine, but then doesn't boot. So, we need partition info from BOTH devices, PIT File, and partition0.mbn/.bin from a T989 and a T989D MBR, as well as the other files (sbl1-3, etc) Then we can properly make 2 debrick.img files, one for T989 and one for T989D as I am using a T989D but using modified SBL1-3 files and ABOOT to get this going.
As you can see from the screenshot, my build is T998DTLUMC4, but my baseband is T989UVMC6. One is telus, one is T-Mobile.

Galaxy ace 2 Deleted Partitions

Good day fellow xda-developers!
I am currently have a problem with my galaxy ace 2 ( GT-I8160). My brother by accident and through Odin erased some partition files! He ticked Nand erased all and since then the mobile shows the first screen writting Samsung Galaxy Ace 2 GT-I8160 and then reboots.
More specific:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found..
I:Cannot load volume /misc
I:Can't partition non mmcblk device: /devices/sd i2/mmc_host/mmc0/mmc0
I have tried many Official roms by sammobile but no luck, i tried from here an official rom given with PDA,CSC and pit but still nothing.
I have even tried to flash through CWM many custom roms but still nothing. Some off them showed to be done correctly but still then it showed the first screen and then restarted.
Has anyone any idea how to fix it? Can someone provide me with a CWM back up to try to flash it?

@matlowpap, you PMed me:
matlowpap said:
Do you have any CWM back up to send me to try flash through there? I want to see if it will flash the missing partitions..
Click to expand...
Click to collapse
Not sure if flashing CWM backup will help here, since even flashing an official ROM didn't help. Probably your best bet is to try recovering deleted partitions via parted. Have you tried to repart internal sdcard via CWM ReParted? If no, then first connect the phone to PC via adb and run:
Code:
parted /dev/block/mmcblk0
print
If even this is not working, it's likely to be a hardware fault. Otherwise this command will print partition list. Compare output with this one
Code:
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB 1049kB PIT
6 1573kB 3146kB 1573kB CSPSA FS
7 4194kB 14.7MB 10.5MB ext4 EFS
2 14.7MB 31.5MB 16.8MB ext4 Modem FS
14 32.5MB 34.6MB 2097kB SBL
16 34.6MB 36.7MB 2097kB SBL_2
1 36.7MB 53.5MB 16.8MB PARAM
12 53.5MB 55.6MB 2097kB IPL Modem
13 55.6MB 72.4MB 16.8MB Modem
15 72.4MB 89.1MB 16.8MB Kernel
17 89.1MB 106MB 16.8MB ext4 Kernel2
3 106MB 726MB 620MB ext4 SYSTEM
5 726MB 1972MB 1246MB ext4 DATAFS
4 1972MB 1982MB 10.0MB ext4 CACHEFS
9 1982MB 2602MB 620MB ext4 HIDDEN
8 2602MB 2702MB 100MB fat32 UMS
11 2702MB 3949MB 1247MB
to find out what partitions to restore. Note that CWM reparted doesn't touch any of "vital" partitions, and will recreate only System, data, cache and UMS. If some other partitions are missing, you have to create them via parted utility.
P.s. Be sure to read that topic in link above before flashing anything.

ChronoMonochrome said:
@matlowpap, you PMed me:
Not sure if flashing CWM backup will help here, since even flashing an official ROM didn't help. Probably your best bet is to try recovering deleted partitions via parted. Have you tried to repart internal sdcard via CWM ReParted? If no, then first connect the phone to PC via adb and run:
Code:
parted /dev/block/mmcblk0
print
If even this is not working, it's likely to be a hardware fault. Otherwise this command will print partition list. Compare output with this one
Code:
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB 1049kB PIT
6 1573kB 3146kB 1573kB CSPSA FS
7 4194kB 14.7MB 10.5MB ext4 EFS
2 14.7MB 31.5MB 16.8MB ext4 Modem FS
14 32.5MB 34.6MB 2097kB SBL
16 34.6MB 36.7MB 2097kB SBL_2
1 36.7MB 53.5MB 16.8MB PARAM
12 53.5MB 55.6MB 2097kB IPL Modem
13 55.6MB 72.4MB 16.8MB Modem
15 72.4MB 89.1MB 16.8MB Kernel
17 89.1MB 106MB 16.8MB ext4 Kernel2
3 106MB 726MB 620MB ext4 SYSTEM
5 726MB 1972MB 1246MB ext4 DATAFS
4 1972MB 1982MB 10.0MB ext4 CACHEFS
9 1982MB 2602MB 620MB ext4 HIDDEN
8 2602MB 2702MB 100MB fat32 UMS
11 2702MB 3949MB 1247MB
to find out what partitions to restore. Note that CWM reparted doesn't touch any of "vital" partitions, and will recreate only System, data, cache and UMS. If some other partitions are missing, you have to create them via parted utility.
P.s. Be sure to read that topic in link above before flashing anything.
Click to expand...
Click to collapse
I will try as soon as I can your method but please can you upload a CWM back up too.
I want to be sure that it is not working.

matlowpap said:
I will try as soon as I can your method but please can you upload a CWM back up too.
I want to be sure that it is not working.
Click to expand...
Click to collapse
I don't have neither enough internet traffic to upload nand backup nor high enough upload speed. Of course you can ask someone else to upload CWM backup, but it would be senseless, as restoring nand backup won't create those deleted partitions.