Database Develop

[INFO] The Atrix sbf thread

Single Binary Format
Hi,
I thought I would start this thread so that all info about sbf utilities and formats specific to the Motorola Atrix could be in one place. (Kenneth Penn's idea) I don't know everything, not a lot, barely anything really, but I will share what I do. Feel free to chime in and correct anything I say.
First off, the software I have found:
Welcome to 2008, Portable SBF Tool / desbf
Motorola android SBF [de]Packer
SBF recalc (waiting for 1.3 edition)
Of these utilities, the one that has done anything worthwhile for me is Desbf. SBF recalc keeps saying wait for version 1.3, and while sbf depacker has been updated for the Atrix, I haven't managed to sucessfully flash anything with it, it has the most promise though and hope for the future.
First, trying these utils is like walking into a shop in chinatown looking to buy a cheeseburger. Where am I? What do I do? How do you say "do something!"?
Desbf, I don't know the history behind this or what it has been used for in the past, it was on a list of google hits for the obscure motorola sbf format. You run it, select a sbf file, and it automatically creates a folder with all the files contained in the sbf extracted. You can delete files and then save an sbf that can be flashed. It has a parse CG button, don't know what it's for. It has been used to flash the Telstra radio onto Att and Bell. I have yet to use it to flash something using RDL3, just the radio using RDL1.
SBF Recalc, shows a lot of information, to use you split the file to a folder to start, do your thing with the files in that folder, and then open the folder to recalc checksum and save an sbf. Only problem is that is doesn't work (yet).
Motorola Android [De]packer is obviously the most in depth util, it shows even more information than SBF recalc. It does do things, not sure what, or if it's my lack of understanding of the format, but I haven't sucessfully done anything with it, it creates files, displays information, but complains about RDL files not being needed for the content, even if you delete all the RDL files.
Speaking of files, here is what I understand about them:
The utilities spit out SMG files, it's a motorola format, not sure of the acronym.
RDL1:
RDL3:
Ram downloader 1 is used for the radio, it is flashed after everything else, changing mode to do so, everything else is flashed using Ram downloader 3. I don't know what happened to RDL2.
CG2 22KB
CG3 512KB, CDT.bin
CG5 is the radio, plus other things apparently. In [De]Packer it's a virtual collection of mbn files, partition.mbn, amas_sec.mbn (the radio), osb1_sec.mbn, cefs.mbn, db1_sec.mbn. I have no idea what they are about. I know they are from CG5 because an sbf with just RDL1, RDL3, and CG5 spits out RDL1, RDL3, and the above without a CG5.
CG42 3072KB mostly zeros, ends at 0xff0
CG44 3072KB Bootloader
CG47 262144 Microboot (Engine and Slot for hashing in microboot priv.c) (ref to rdl1.bin, ptable, CDT.BIN, BCT.bin, PT.bin, EBT.bin, MBR.bin, EBB.bin)
CG50 is 2KB of 0xFF, no content, probably used to clear a partition
CG52 same as above, (sent to mmcblk0p7 to clear misc? -optionally used to pass commands to recovery, it fed with command line for example to flash an update -)
CG53 1014KB begins with SOL: logo.bin (mmcblk0p8)
CG54 2KB of 0xFF (possibly sent to mmcblk0p9, Kernel Panic Data)
CG55 recovery (header, ramdisk, kernel) (mmcblk0p10)
CG56 boot (header, ramdisk (/), kernel) (mmcblk0p11)
CG57 is the system image in ext3 linux format. (mmcblk0p12)
CG58 osh (webtop) system image in ext3 (mmcblk0p13)
CG59 20MB HFS, CDROM (Motorola Helper) (mmcblk0p14)
CG60 2KB of 0xFF (possibly sent to mmcblk0p15 to clear cache image)
CG61 2KB of 0xFF (sent to mmcblk0p16 to clear userdata image, tested)
CG62 preinstall image in ext3 (mmcblk0p17)
This is a work in progress.
New for Gingerbread 2.3.4:
CG39 looks like fs, pds update?
CG42 bootloader
CG47 same as before, just full partition size
CG56 boot logo
CG58 Recovery emmc image (kernel, ramdisk.gz)
CG59 Boot emmc image
CG60 system image APP
CG61 webtop image OSH
CG62 cdrom image motohelper
CG65 preinstall image
Code:
cat /proc/partitions
major minor #blocks name
7 0 7308 loop0
7 1 4190 loop1
179 0 15668736 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 1931264 mmcblk1 (external sd card, 2 GB)
179 33 1930680 mmcblk1p1 (external sd card, 2 GB)
254 0 7308 dm-0
254 1 4189 dm-1
LINKS: (to be integrated)
http://forum.xda-developers.com/show...&postcount=502
http://and-developers.com/partitions:cdt
https://www.droid-developers.org/wiki/BootRecoverySignature
Cheers!

Heres a detailed list of the partitions:
http://forum.xda-developers.com/showpost.php?p=12687720&postcount=502

This is awesome. Thanks for the details.

Thanks,
I am thinking it might be possible to create an sbf from a dump of the partitions on a active phone. It would certainly be nice to have one for Bell. My idea is to replace all the active bits in an sbf file with versions from a dd dump of each partition. [De]Packer could possibly be used to compile a CG5 from all the bits, take that file and use Desbf to create the rest of it.
So if someone with a stock Bell Atrix could run this and post a link back with the resulting 7zip file it would help. Mediafire or some other file hosting service.
backup creator script
What it does is dump all the "other" partitions, not system or data, or webtop, but all the little ones up to 11 and 14
Cheers!

NFHimself said:
Thanks,
I am thinking it might be possible to create an sbf from a dump of the partitions on a active phone. It would certainly be nice to have one for Bell. My idea is to replace all the active bits in an sbf file with versions from a dd dump of each partition. [De]Packer could possibly be used to compile a CG5 from all the bits, take that file and use Desbf to create the rest of it.
So if someone with a stock Bell Atrix could run this and post a link back with the resulting 7zip file it would help. Mediafire or some other file hosting service.
backup creator script
What it does is dump all the "other" partitions, not system or data, or webtop, but all the little ones up to 11 and 14 15 16.
Cheers!
Click to expand...
Click to collapse
That would be a massive development for Bell users.

I have confirmed that removing CG61 causes a flash to not erase your userdata partition.
Cheers!

Great news! Keep us updated.

NFHimself said:
I have confirmed that removing CG61 causes a flash to not erase your userdata partition.
Cheers!
Click to expand...
Click to collapse
hey, how hard do you think it would be to modify the 1.2.6 SBF to also not wipe the user partition? Would it act like the 1.8.3 SBF which preserves all user settings and apps? Conversely, could we modify the 1.8.3 SBF to act like the 1.2.6 SBF by clearing all the settings out and returning completely back to stock? Sorry for all of the questions, but I just found the 1.8.3 SBF very cool, that it let me keep all my settings and apps, and thus cut down on the time I needed to spend on restoring things after the flash.

UncleCemka said:
hey, how hard do you think it would be to modify the 1.2.6 SBF to also not wipe the user partition?
Click to expand...
Click to collapse
Probably as easy as pulling CG61 out, if I recall correctly (pretty easy...)
EDIT: haha I see NFHimself confirmed this... that's the one .8.3 is missing (besides CG51 --ideas?)

That's all I did, selected CG61, hit delete, save in desbf, and run rsdlite.
Only thing about it is that Gingerbreak will still wipe your internal memory so you still have to backup that.

The error in [de]packer, where it says source not found, seems to be limited to cg3.smb, remove that and it compiles the folder.
Cheers!

Update on creating a Bell sbf:
Of the partitions 1-11, and 14, the ones with unique content are 3, 5, 9, 10, 11. Of these, 10 and 11 are straight dumps in the sbf file, the recovery and boot partitions, the partitions 3, 5, and 9 have no direct correlation to a CG that I can see so far.
However, I have managed to go from a Telstra firmware to a stock Bell firmware, just not using a sbf. I simply did a dd of all Bell partitions from sdcard to the phone, leaving mmcblk0p12 for last since it's the system partition. Well most of the partitions, I didn't dd internal memory or data, I just did a data wipe. So, you can go back to stock, you just can't recover from a bricked situation, using this method.
Cheers!

NFHimself said:
Update on creating a Bell sbf:
Of the partitions 1-11, and 14, the ones with unique content are 3, 5, 9, 10, 11. Of these, 10 and 11 are straight dumps in the sbf file, the recovery and boot partitions, the partitions 3, 5, and 9 have no direct correlation to a CG that I can see so far.
However, I have managed to go from a Telstra firmware to a stock Bell firmware, just not using a sbf. I simply did a dd of all Bell partitions from sdcard to the phone, leaving mmcblk0p12 for last since it's the system partition. Well most of the partitions, I didn't dd internal memory or data, I just did a data wipe. So, you can go back to stock, you just can't recover from a bricked situation, using this method.
Cheers!
Click to expand...
Click to collapse
that's great news and I hope that if an update comes out and Bell users aren't necessarily able to update that you might refine this method into an automated process or at least detail it for the rest of the community's benefit.

Wow. Great work NFHimself! That's the only reason I haven't taken Telstra for a spin. There's no going back......yet.
Sent from my rooted and frozen Motorola Olympus.

Well it was literally "dd if=sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1" skipping 12 and continuing on, then doing 12. I did run setprop tcmd.suspend 2 first, and I was rooted, have to pull the battery to reboot since I overwrote the system partition and had no commands in my path, but that's it.
Just would need some online hosting space and do up a simple script, really.
Cheers!

NFHimself said:
Well it was literally "dd if=sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1" skipping 12 and continuing on, then doing 12. I did run setprop tcmd.suspend 2 first, and I was rooted, have to pull the battery to reboot since I overwrote the system partition and had no commands in my path, but that's it.
Just would need some online hosting space and do up a simple script, really.
Cheers!
Click to expand...
Click to collapse
That is really ballsy. I will not write to my mmcblk0p1 because if there is the slightest error I believe I'd have a have a hard brick. All the options seen when holding power + volume-down (or up) can be found in that block device.
But this is not the case for Bell/Telstra?! Fascinating that your devices are different! Where *DOES* your bootloader live?
Actually, I now see that most the Telstra CG img files are signed by two keys, but almost all of the AT&T ones are signed by 3, and the keys differ between the two .sbfs (but are consistent within each.) How very strange. Our CG44s are very similar, but also different (for example do a diff on their strings):
Only in Telstra (1.4.2):
Code:
< UpdateBootBct
< BL size:%d
< MB size:%d
< NvMotBlReSign
< NvMotBctReSign End

I went through each one with hexedit, and nothing really struck me as being the bootloader, in fact, on my archos tablet, the bootloader was not stored in the mtd list at all, it was somewhere else, probably in the SOC somewhere.
Our partition 1 is all 0xFF, no danger there, either it's protected and can't be read or written to, or it really is 0xFF.
Cheers!

Oh, a dump of all the important Bell mtd partitions is available.
Bell_Full_Partition_Backup.tar.gz
Cheers!

Thanks! Yes, I suspect now that the OTA writes the mmcblk0p1 and that this is the location the new bootloader is updated from (on next boot?) and that RSD can simply skip this step and update directly. Just got an mmcblk0p1 from someone who never had an OTA (on ATT) and it is like yours "FF 00 00 00 FF: and then 3.5mb of FFs =) So, you were probably safe to overwrite it!
Will be interesting to confirm once you have your first OTA =) As for "SE" (Secured Engineering?) I don't know the difference to NS yet. Perhaps its related to the bootloader and certificate differences too.

Does anyone have much experience tinkering around with the PDS.bin file? There's reason to suspect that corruption in the mmcblk0p3 block occurs when the Internal SD is formatted and partitioned erroneously via custom recovery. this could be what causes the bottom of the touchscreen to become unresponsive for the bottom half inch of the screen (causes "ghosting" or misaligned touch response above the impacted area)
Tenfar advised me to properly format and partition mmcblk0p18 with the following command (#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18) which did everything okay, but didn't make an impact unfortunately. Still tinkering around with this buggered AT&T Atrix for the last few weeks. Determined to fix this bish instead of sending it in lol

[Solved] ROM Flashing Problem

Hello, I’m using GT-N7000 (Samsung). Though I haven’t enough knowledge about android nevertheless I flash ROMs frequently. Last time I mistakenly flash “removed_apks_flashable_20140130” when I want to flash a ROM named “Nightmare_DU_4.4.2_20140130_n7000”.
In the above mention ROM, three zip file found
1. Nightmare_DU_4.4.2_20140130_n7000,
2. Slim_AIO_gapps.4.4.2.build.2.x,
3. Removed_apks_flashable_20140130,
Because of hurriedness, I mistakenly flash “removed_apks_flashable_20140130” and my phone did not response even recovery mode wasn’t come up. Then I flash “PhilZ-cwm6-ZCLSE-CHN-4.35.tar.md5” using ‘Odin3 v3.07” and find recovery mode.
Now, when I try to flash a ROM it is aborted due to “modem.bin” and prompt Status7 problem.
Can someone help me regarding this issue?

MosMon said:
Hello, I’m using GT-N7000 (Samsung). Though I haven’t enough knowledge about android nevertheless I flash ROMs frequently. Last time I mistakenly flash “removed_apks_flashable_20140130” when I want to flash a ROM named “Nightmare_DU_4.4.2_20140130_n7000”.
In the above mention ROM, three zip file found
1. Nightmare_DU_4.4.2_20140130_n7000,
2. Slim_AIO_gapps.4.4.2.build.2.x,
3. Removed_apks_flashable_20140130,
Because of hurriedness, I mistakenly flash “removed_apks_flashable_20140130” and my phone did not response even recovery mode wasn’t come up. Then I flash “PhilZ-cwm6-ZCLSE-CHN-4.35.tar.md5” using ‘Odin3 v3.07” and find recovery mode.
Now, when I try to flash a ROM it is aborted due to “modem.bin” and prompt Status7 problem.
Can someone help me regarding this issue?
Click to expand...
Click to collapse
You need to flash Raw kernel in philz recovery, reboot recovery and then flash rom. Google for raw kernel.

treacherous_hawk said:
You need to flash Raw kernel in philz recovery, reboot recovery and then flash rom. Google for raw kernel.
Click to expand...
Click to collapse
Thank treacherous_hawk for your reply first.
I have some raw kernel from "http://forum.xda-developers.com/showthread.php?t=2397000". Please suggest me what version should i flash.

MosMon said:
Thank treacherous_hawk for your reply first.
I have some raw kernel from "http://forum.xda-developers.com/showthread.php?t=2397000". Please suggest me what version should i flash.
Click to expand...
Click to collapse
R4 or R5.

treacherous_hawk said:
R4 or R5.
Click to expand...
Click to collapse
Thanks again.
Please guide me to flash zip file.

Please help me.
Proper guideline is required.

MosMon said:
Please help me.
Proper guideline is required.
Click to expand...
Click to collapse
put the downloaded zip file on your external sd card and boot into philz recovery, go install zip, point to the location where zip is saved and flash, once finished, reboot recovery and then flash the rom along with gapps and SuperSU if necessary.

treacherous_hawk said:
put the downloaded zip file on your external sd card and boot into philz recovery, go install zip, point to the location where zip is saved and flash, once finished, reboot recovery and then flash the rom along with gapps and SuperSU if necessary.
Click to expand...
Click to collapse
After flashing kernel successfully, when reboot recovery is execute then recovery mode is not come up again even I wait for 10mins. Done this several times but same result.

MosMon said:
After flashing kernel successfully, when reboot recovery is execute then recovery mode is not come up again even I wait for 10mins. Done this several times but same result.
Click to expand...
Click to collapse
try the volume up+power+home button combination, hold them till you see the recovery.

treacherous_hawk said:
try the volume up+power+home button combination, hold them till you see the recovery.
Click to expand...
Click to collapse
no luck till 10mins

You may need to flash philz kernel again using odin version.
Sent from my GT-N7000 using Tapatalk 2

MosMon said:
no luck till 10mins
Click to expand...
Click to collapse
WHAT do you see?

Thank to forest1971 and nokiamodeln91 for your reply.
If I flash philz kernel using Odin and without wiping anything like data, delvik, etc in recovery mode, this kernel is stable and I can open recovery mode after switched off but others can not (I tried other kernel as well) . But If I wipe or try to flash a ROM then required to flash Philz kernel again using odin.
When I try to flash a ROM it is aborted due to “modem.bin” and prompt Status7 problem for maximum ROM. After that recovery mode is not enable except well come screen where only fond "Sumsung Galaxy Note GT-N700" with a root symbol. If I press only power button then may be boot-loader goes to a loop and my phone try to boot again and again but failed.
I tried to alive my phone last 5 days but failed to find a solution from XDA. Today I post my problem for your help.

Using Philz recovery flash an older rom like cm 10.2 or 10.1 or a custom touchwiz rom like aryamod.

Still no luck.
HTML:
[QUOTE][I]Error Description:
Installing update....
assert failed: getprop("ro.product.device")=="galaxynote"|| getprop("ro.build.product")=="galaxynote"|| getprop("ro.product.device")=="n7000")|| getprop("ro.butild.product")=="n7000" .............
E: Error in emmc/...............
(Status 7)
Installation aborted.[/I][/QUOTE]
As per forest1971's instruction ([Guide]: Repartition to revive emmc/superbrick G-Note), I scanned my phone and found problem from 3221MB to 4295MB. Now I'm afraid to repartition as forest1971's instruction. I'm worried about Partition No 10, 11 and 12. I found the example as ...
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
In this scenario, what should be mine?
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
Please help....

That's really a wired place to get issues..UMS? Boot into Philz recovery and connect phone to pc and run adb and use the e2fsck on data partition and format the internal storage using recovery. .. Check if it helps..
Instructions should be in forest's thread.. (great post by him)

Thank you for advise again.
What's your suggestion now?
May I proceed as below table...
10 1174MB 3220MB 2046MB ext4 DATAFS
11 4295MB 15.2GB 11.0GB fat32 UMS
or is there any option for recover bad sector?
One more thing that i want to know. How can i find my present partition information?

Did you use partition scanner by hg42. What is the results?
Sent from my GT-N7000 using Tapatalk 2

Thank you boss for your reply.
Yes I'm using partition scanner and the results are below:
emmc_scan_all_partitions_once.zip ---> Found OK
emmc_scan_all_partitions_infinitely.zip ---> Found OK till 79 times
emmc_find_brick_start.zip ----> Found error on 3221MB
emmc_find_brick_end.zip -----> Found error on 4295MB
emmc_scan_write.zip ----> Not flash yet

MosMon said:
Thank you boss for your reply.
Yes I'm using partition scanner and the results are below:
emmc_scan_all_partitions_once.zip ---> Found OK
emmc_scan_all_partitions_infinitely.zip ---> Found OK till 79 times
emmc_find_brick_start.zip ----> Found error on 3221MB
emmc_find_brick_end.zip -----> Found error on 4295MB
emmc_scan_write.zip ----> Not flash yet
Click to expand...
Click to collapse
The results of the all partition scanner and find brick scanner are not consistent. I still feel your case is probably not a superbrick (unless you have wiped under the dangerous stock ICS kernel). Now I would to try to use gparted to remove ums and recreate it with the same size, with steps as in my Guide.
Let me know how it goes.

[Q] s3 mini i8190 EFS and GPT corrupt

hi,
i own a galaxy s3 mini i8190 i was trying to flash reovery with heimdall and i used pit to get partition layout i flashed recovery.img on MBR,GPT partition and my phone got hardbricked
because recovery.img in s3 mini should be flashed on kernel2 partition and i flashed it on totally wrong partition after i used jtag to flash it and i unbricked it successfully my phone turned on but my internal memory is corrupted it is showing 0.00b and my phone's efs is also corrupted my s3 mini is in factory mode network is not working i am unable to install any app either from playstore or directly apk because my internal memory is messed up
i think i need to flash GPT.img to repair internal memory layout because it contains layout which is corrupted on my phone then i need efs backup in .img format to exit factory mode and run 3g network please please someone help me
upload GPT.img and EFS.img or if you think this solution is incorrect help me
plz plz plz someone help me i am in a big problem and also my warranty is over plz plz help
give me GPT and efs so i can flash it through heimdall
:crying::crying::crying::crying::crying:

Yor text is to big to read, so I give up of reading it. Anyway take a look here or search on XDA. Good luck with that
P.S: & next time post your questions on Q&A section, thanks.

In efs there's imei. If you don't have a backup i'm afraid it's just gone. You can't use mine
---------- Post added at 06:22 PM ---------- Previous post was at 06:07 PM ----------
AFAIK gpt is read only for s3 mini so i dont think you can flash it. You may just need to repartition with a pit file. This will not solve all of yours problems if efs is corrupted, in that case you have to bring the phone to samsung service to restore your Imei.

as i flashed the MBR,GPT partition in heimdall screen shot
by using jtag only MBR master boot record is repaired which unbricked my phone now GPT which was also corrupted along MBR need to be flashed so my partition layout will be corrected and internal sd will work
i also tried pit to flash firmware 4.1.2 with odin but no any change
it is an option in heimdall and i think it can be flashed partition id is 1 so for now i left efs to solve it i am trying to solve internal memory first
i ended up google but found no solution

If you flashed recovery on first partition i think your /efs is ok, because its first sector starts at 10MB from beginning of /dev/block/mmcblk0
recovery images are smaller
You need following images:
Code:
PIT Entry Name filename
00 MBR,GPT
01 MasterTOC
02 PIT goldenxx.pit
03 MD5HDR md5.img
04 STEboot1 STE_boot1.img
05 STEboot2 STE_boot2.img
06 Dnt dnt.ssw
07 reserved
08 CSPSAFS cspsa.img
09 CSPSAFS2 cspsa2.img
I have i8190N so my images can't help you

you have i8190n and its partitiion layout is different for i8190 so these images are so called GB images
also i think if GPT will be corrected the efs will also be fine
does anyone have same model which i have?
plz help me

also when i try to format it in recovery it says
invalid argument failed to mount /data and /efs
and efs and data is not corrupted in mine case my partition layout is corrupted

qasim799 said:
you have i8190n and its partitiion layout is different for i8190 so these images are so called GB images
...
Click to expand...
Click to collapse
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs

piskor said:
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs
Click to expand...
Click to collapse
thank you so much you helped me
you are a good guy:good:

piskor said:
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs
Click to expand...
Click to collapse
any guarantee about theses images I'm afraid to flash them because they are of different model
they will not brick my device?
sure me so i will flash them

qasim799 said:
any guarantee about theses images I'm afraid to flash them because they are of different model
they will not brick my device?
sure me so i will flash them
Click to expand...
Click to collapse
No guarantee, but you can try.
Your phone, as you said is hardbricked, and if you flashed recovery img on first partition, few of them are also overwritten.
You can wait of course for i8190 dump, what i recommend

Any one plz help me
i want images of i8190 only
take a backup of your GPT,MBR.img

still no help i heard about XDA that they help very fastly nut no one is helping me
plz for GOD SAKE help me i am in a big and weird kind of problem

qasim799 said:
still no help i heard about XDA that they help very fastly nut no one is helping me
plz for GOD SAKE help me i am in a big and weird kind of problem
Click to expand...
Click to collapse
But remember, that no one is obligated to help you on XDA I see that many people tried to help you (including me), so if we can't help, what you want more!? Anyway, really hope that someone pops up with a solution for you Have a nice day

I would if I could, but I have a 8910N....

that is what i am saying who trys to help me have different model from me.
i am requesting to those who have gt-i8190
after all it is s3 mini forum
nobody have this phone who has plz help me just take a backup of MBR,GPT.img partition id is 1
it is just a less then 1 MB file which i need to my whole phone

Clostry said:
I would if I could, but I have a 8910N....
Click to expand...
Click to collapse
piskor gave me backup of n model but i am afraid to flash it as it is from a different phone it will hard brick it again .you can see their layout then sure me i can flash them or not and remember the MBR also it matches

no help yet !

To all I8190 users
If somebody want to help to qasim799 please execute this commands from adb or terminal emulatror app on your phone and attach to the post resulting images:
Code:
su
dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mmcblk0p3.img
Resulting image files will be available in root of external storage card
mmcblk0p1.img - image MBR,GPT partition
mmcblk0p2.img - MasterTOC partition
mmcblk0p3.img - PIT partition

Here you go @qasim799, hope that works. Thanks piskor, for the noobish "how to":laugh:

[Q] [HELP] No T599v recovery partition?

Hey guys,
I've been trying to figure out which is the recovery partition (mmcblk0pXX) on my t599v by looking on the internet / on the forum, but I can't find this information.
I also tried to install apps like Partition Table but the recovery partition is not shown.
I've seen on this forum that recovery is on mmcblk0p21 for the t599, but I confirm that it is not the same for the t599v ( this partition being used for something else )
( Actually, I need this to be able to flash .img file ( as recovery.img ) using android terminal emulator, since I have lots of troubles with Odin )
*** I'm using a stock rooted ROM and the stock recovery ( which is working )****
So here i'll need some expert advide! I hope that someone can help me!
Thanks!

I'm one of the earlier members with a T599V and I pulled a recovery.img from the mmcblk0p21 partition. Look at the latter, that's recovery.fstab pulled from the stock recovery image; we all use the same recovery file, so it'd share the same recovery.fstab which would mean it's being flashed to the same partition as the T599, T599N.

Shield Portable 2 X1 Recovery Images

Hello! I've recently just snagged a fully functioning Tegra X1-Powered Nvidia Shield Portable 2 that's rooted. I'm trying to extract the partitions so that I can make backups of the bootloader (to flash with nvflash), system, boot, recovery, etc images for other X1-Powered Shield 2 owners for unbricking purposes, as there aren't any recovery images posted online.
Does anyone know which fastboot/adb commands could achieve this? Here is what the partition scheme looks like but I have no clue which partition is which. Any help with this would be greatly appreciated. Thank you so much!

so i just made an interesting find as to which partition is which
i ran
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
and then ran
cat fstab.loki_e_lte
and now i think i know which partition needs to be extracted for each image. refer to screenshot for context
so it seems
mmcblk0p19 > system.img
mmcblk0p20 > cache.img
mmcblk0p18 > boot.img
mmcblk0p22 > misc.img
mmcblk0p23 > staging.img
mmcblk0p16 > recovery.img

i have extracted the images for recovery but i have not tested these. also currently working on figuring out how to extract the bootloader so i can have a *complete* system recovery for those even without a bootloader; if anyone knows how, i'm all ears.
i do not recommend flashing these on a non-bricked shield but someone with a bricked X1 powered shield feel free to test and let me know how it goes <3 flashing instructions are included in the folder too.
loki_e_lte - Google Drive
drive.google.com