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
Related
From the head of the recovery partition:
mmcblk1p26 -> sgpt (128 KB) http://www.multiupload.com/CXYCHYS8U7
mmcblk1p25 -> emstorage
mmcblk1p24 -> userdata
mmcblk1p23 -> preinstall
mmcblk1p22 -> cache
mmcblk1p21 -> system
mmcblk1p20 -> kpanic
mmcblk1p19 -> cid (512 KB) http://www.multiupload.com/L5E3SD3TF0
mmcblk1p18 -> misc (512 KB) http://www.multiupload.com/XCWZT4SO7K
mmcblk1p17 -> cdrom (12 MB) http://www.multiupload.com/80C1XQY8Z1
mmcblk1p16 -> recovery (9 MB) http://www.multiupload.com/LLC6606VY0
mmcblk1p15 -> boot (8 MB) http://www.multiupload.com/UOS8RYHF0F
mmcblk1p14 -> bpsw (4 MB) http://www.multiupload.com/HXDG1LNZNV
mmcblk1p13 -> devtree_backup (512 KB) http://www.multiupload.com/G8X9L8OJTA
mmcblk1p12 -> devtree (512 KB) http://www.multiupload.com/DWYL7DT3C4
mmcblk1p11 -> sp (2 MB) http://www.multiupload.com/JUF37ZQN38
mmcblk1p10 -> logo.bin (1 MB) http://www.multiupload.com/ITVROPWGA6
mmcblk1p9 -> lbl_backup (512 KB) http://www.multiupload.com/1Z13IQVBRC
mmcblk1p8 -> lbl (512 KB) http://www.multiupload.com/UCNG7R3KZS
mmcblk1p7 -> pds (4 MB)
mmcblk1p6 -> cdt.bin (512 KB) http://www.multiupload.com/AM49QE6TXY
mmcblk1p5 -> bploader (512 KB) http://www.multiupload.com/PZHOPCRLR7
mmcblk1p4 -> ebr (1 KB) http://www.multiupload.com/ESTER8OYCW
mmcblk1p3 -> mbmbackup (512 KB) http://www.multiupload.com/LD6LTFB4ZE
mmcblk1p2 -> mbm (512 KB) http://www.multiupload.com/3Q8IJCBTL9
mmcblk1p1 -> mbmloader (128 KB) http://www.multiupload.com/MOAYXU14KO
Other:
Cache partition that contains a zip header for an update.zip (from anon on IRC): http://www.mediafire.com/?2uq2yi5jf8fqwjx
"cid.img" is 512Kb of "FF"
"bpsw.img" is 4Mb of "FF"
"cdt.bin.img" contains some Motorola Key "O=Motorola Inc, OU=Motorola PKI, CN=HAB CA 522L"
"bpsw.img" is 128Kb of "FF"
Thanks -- though out of curiosity, why are you posting them in reverse order (mmcblk1p26 to mmcblk1p1)?
psouza4 said:
Thanks -- though out of curiosity, why are you posting them in reverse order (mmcblk1p26 to mmcblk1p1)?
Click to expand...
Click to collapse
That was the order ls listed them on my phone
Hey, make sure no one flash it to their phones. Specially /pds, because it will mess with your IMEI forever.
Sent from my Milestone 2 XDA App
Adam.h.ogle said:
"cid.img" is 512Kb of "FF"
"bpsw.img" is 4Mb of "FF"
"cdt.bin.img" contains some Motorola Key "O=Motorola Inc, OU=Motorola PKI, CN=HAB CA 522L"
"bpsw.img" is 128Kb of "FF"
Click to expand...
Click to collapse
The CDT image is in the correct format but contains extra data?
You are however correct that the bpsw.img and the bploader.img for that matter contain FF because you can't use dd to image them.
The CID image probably should be FF since this is stock (I'm assuming) and doesn't contain data yet.
Adam.h.ogle said:
From the head of the recovery partition:
mmcblk1p26 -> sgpt (128 KB) http://www.multiupload.com/CXYCHYS8U7
mmcblk1p25 -> emstorage
mmcblk1p24 -> userdata
mmcblk1p23 -> preinstall
mmcblk1p22 -> cache
mmcblk1p21 -> system
mmcblk1p20 -> kpanic
mmcblk1p19 -> cid (512 KB)
Click to expand...
Click to collapse
So . . . pardon my ignorance, but why wouldn't you release or post the 25-20 partitions? I could use them right about now!
21, 24, and 25 have user information on them. What do you need exactly? I can hook you up.
rynosaur said:
So . . . pardon my ignorance, but why wouldn't you release or post the 25-20 partitions? I could use them right about now!
Click to expand...
Click to collapse
Userdata is /data, which has personal info.
Emstorage is /sdcard, which isn't needed.
System contains the system partition, which was a) too big to upload, and b) a tainted copy since I had perma-rooted the phone. If anyone has a virgin /system with adb root, upload it and I will add it as a link.
Kpanic is like the sdcard in that it is normally empty.
Preinstall was tainted as I was involved in attempting to root the phone. Like /system, if anyone has a virgin copy, post a link and I will add it.
Sent from my DROID3 using xda premium
Hmmm, ok. I had a problem with /system that was causing a bootloop, but flashing a /system that was posted in the SBF thread on General just made things worse. I wish I could get moto-fastboot to tell me what the sizes of my partitions are so I could have a chance to see which is wrong.
As for /data, i.e., userdata -- how much trouble would it be for someone to pull one that is from a factory-resetted phone. If someone would upload a partition that resuscitates this puppy, I would certainly donate, since that would be cheaper than an Ausrurion deductible (not that they have the D3 yet).
rynosaur said:
Hmmm, ok. I had a problem with /system that was causing a bootloop, but flashing a /system that was posted in the SBF thread on General just made things worse. I wish I could get moto-fastboot to tell me what the sizes of my partitions are so I could have a chance to see which is wrong.
As for /data, i.e., userdata -- how much trouble would it be for someone to pull one that is from a factory-resetted phone. If someone would upload a partition that resuscitates this puppy, I would certainly donate, since that would be cheaper than an Ausrurion deductible (not that they have the D3 yet).
Click to expand...
Click to collapse
Can't you get to recovery mode (Power + X) and do a factory reset?
At least on M1/M2/Droid 2/X we can't get to fastboot mode no matter what we do (just dev phones can do that). Is there any hw/sw difference on the device that enables fastboot or it is a hacked binary from Atrix devs?
Sent from my Milestone 2 XDA App
dangpzanco said:
Can't you get to recovery mode (Power + X) and do a factory reset?
At least on M1/M2/Droid 2/X we can't get to fastboot mode no matter what we do (just dev phones can do that). Is there any hw/sw difference on the device that enables fastboot or it is a hacked binary from Atrix devs?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Milestone 1 and 2 and OG Droid and Droid2 and DX Don't have Fastboot support. It's just not there. Motorola's behind the times. Atrix was the first moto with fastboot, then D3...or the Photon, depending on which timeline you want to accept as cannon....
Anyway, I dunno which came first, am too lazy/pissedthatIbrickedmyD3 to care. I have a warranty replacement coming...told them that I took an OTA update anourd mhgindt, wkoe up and fnuod my Drido3 brekicd.
Yes, I switched around the spelling so those futhermuckers at VZW can't google it and figure out I'm bllusihting them. Plus, you guys can still read it. Gotta love the human brain, eh?
wow, you are paranoid!
In any case, they can't cite you for breach of contract unless your phone shows evidence of rooting. See to that, not scrambling online comments.
Sent from my Transformer TF101 using Tapatalk
nullness said:
The CDT image is in the correct format but contains extra data?
You are however correct that the bpsw.img and the bploader.img for that matter contain FF because you can't use dd to image them.
The CID image probably should be FF since this is stock (I'm assuming) and doesn't contain data yet.
Click to expand...
Click to collapse
Is there any way to get images of bpsw and bploader assuming I'm running temp-adb root? I'd just like to have these if possible with my virgin XT860 system before I start mucking around.
Rick#2 said:
Is there any way to get images of bpsw and bploader assuming I'm running temp-adb root? I'd just like to have these if possible with my virgin XT860 system before I start mucking around.
Click to expand...
Click to collapse
Code:
dd if=/dev/block/mmcblk1p14 of=/sdcard/bpsw
dd if=/dev/block/mmcblk1p5 of=/sdcard/bploader
#pds is also unique for each device, e.g it holds your IMEI.
dd if=/dev/block/pds of=/sdcard/pds
Sent from my Milestone 2 XDA App
Hehe, I know those are the proper p artitions but I don't think we can use dd to dump them, or at least not without any special parameters; all that'll show up is FF (I'm guessing due to the encryption?)
Sent from my XT860 using xda premium
Rick#2 said:
Hehe, I know those are the proper p artitions but I don't think we can use dd to dump them, or at least not without any special parameters; all that'll show up is FF (I'm guessing due to the encryption?)
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Well, on M2/D2 it works fine, we can even flash signed boot.img thru CWM4.X. Is Droid 3 that much encrypted, that you can't even copy a partition? Do you have an organized table of partitions like this one: http://and-developers.com/partitions:cdt?
It shows wich partitions are checked for signature on boot (boot, recovery, cdt.bin...), on 1st boot (e.g system) and not checked (pds, bploader, I think bpsw is signed).
The only way is testing, but don't flash dumped files with dd, it may break something or perma-brick you...
Sent from my Milestone 2 XDA App
Well, got myself into a shenanigan by using moto-fastboot to flash the system.img from the OTA leak on my XT860. (The OTA is meant for a Verizon XT862).
Stunned as I am, I figured I could just moto-fastboot my old dd'd image from mmcblk1p21 but that didn't fix the problem; I was getting the invalid boot screen and was unable to fix it. I guess the image I took wasn't perfect or I should have used certain parameters with the dd command, so this isn't really that great.
Moral of my story, stick with nandroid backups people!
Checking uImage... Invalid Size
During Arch Linux boot...
I've CM9 and webOS 3.0.5, working fine...
Before Arch, I tested Bodhi, and it worked..
I searched about this in moboot, arch linux arm forum... I only found people talking about this problem in android, but it wasn't very conclusive...
I want to test Arch, because is my desktop distro...
Thanks, for all the info I get from this forum!
if your boot doesnt have enough space for a complete boot image, no matter what OS you are trying, it will fail.
Make sure there are no traces of other images (like Bodhi) or your /boot
I've only 4MB of free space on /boot.
I asked in this post if my /boot list files is normal...
There is another thing, when I created the partition for Arch, I had Bodhi... so I did this:
Code:
lvrename /dev/mapper/store-ext3fs /dev/store/arch-root
mkfs.ext3 /dev/store/arch-root
Then, I mounted the new partition and extracted Arch...
dubidu said:
if your boot doesnt have enough space for a complete boot image, no matter what OS you are trying, it will fail.
Make sure there are no traces of other images (like Bodhi) or your /boot
Click to expand...
Click to collapse
Very thanks!
Problem solved and it was very simple. Only today I had time to try to solve this since my post...
Solution: uImage.ArchLinuxARM was corrupted! (download it again)
Before:
Code:
-rw-r--r-- 1 root root 4472832 Feb 5 01:51 uImage.ArchLinuxARM
Now:
Code:
-rw-r--r-- 1 root root 4852245 Feb 12 11:44 uImage.ArchLinuxARM
md5sum is always good in this situations!
Pay attention, when using curl, if there's some error message during download. If there isn't enough space in /boot, curl can't preform correctly, it download but not the integral file...
By request. FYI.
P6800 (3G)
mmcblk0p1 EFS DO NOT TOUCH
mmcblk0p2 BOOTLOADER DO NOT TOUCH
mmcblk0p3 BOOTLOADER DO NOT TOUCH
mmcblk0p4 param
mmcblk0p5 kernel
mmcblk0p6 recovery
mmcblk0p7 cache
mmcblk0p8 modem/radio
mmcblk0p9 system
mmcblk0p10 data
mmcblk0p11 hidden/preload
P6810 (Wi-Fi)
mmcblk0p1 EFS DO NOT TOUCH
mmcblk0p2 BOOTLOADER DO NOT TOUCH
mmcblk0p3 BOOTLOADER DO NOT TOUCH
mmcblk0p4 param
mmcblk0p5 kernel
mmcblk0p6 recovery
mmcblk0p7 cache
mmcblk0p8 system
mmcblk0p9 data
mmcblk0p10 hidden/preload
Thanks Chainfire for your help
You did that what i am wanted to do But this is now much more better cause it is made from a experienced developer!
Cheers
also big thx!
with this i should have been able to get my first 7.7 up again!
hi ldon't know this is the right place to ask my goestion or not anyway because Ithinke my tab problem is belong to the system partition l,am gone ask that please help m e lhave a 7.7 and try to change the rom after that my tab had a reset and it just stuck at the page with the tab's name I just can get into download mod nothing more and in there lcant flash any rom any more it's failed when odin try to write the factory part of rom l have to tell my tab is 6800 and l just find single part rom is there somebody how Can help me or it done and nothing ave gone happen please please please somebody help me
Creating factoryfs.img
The value of factoryfs sizes for P6800/P6810 when creating the image in ext4_utils:
factoryfs.img = 832M
Hmm this is strange. On my P6800 (3G) I also have a 12th partition
mmcblk0p12
Is there any info what this could be?
segelfreak2 said:
Hmm this is strange. On my P6800 (3G) I also have a 12th partition
mmcblk0p12
Is there any info what this could be?
Click to expand...
Click to collapse
Probably extStorage (or sdcard)..
Hello
I have issue with my Tablet when i installed custom rom , Tablet failed to make Wipe Data or Factory reset , ODIN failed even to flash the original ICS Firmware
With CWM i receive 2 errors when wiping Data and Cache
make_extf4fs failed on /dev/block/mmcblk0p10
make_extf4fs failed on /dev/block/mmcblk0p7
I investigated forum and I found that issue can be solved if some one provided me partition table from Working P6800 3G so i can apply it via Adb Shell , so can u please provide me , or if you have any suggestions to solve my issue thanks to tell me , I need to make my tablet alive
biopsin said:
Probably extStorage (or sdcard)..
Click to expand...
Click to collapse
Nope, that is mmcblk1p1; I'm not sure what the extra partition is for. There is an extra partition on the p6810 as well.
this link will have odin and a pit file (i believe the pit file is the partition table?)
http://www.sammobile.com/firmware/?page=3&model=GT-P6800&pcode=TGY&os=1&type=3#
mmcblk0p12 - P6800
Seem mmcblk0p12 points to FOTA or vice versa, at least on P6800 , but what this is I have no clue..
manouver to /dev/block/platform/dw_mmc/by-name to take a peek
partition error
Does anyone know a step by step instruction to re partition the emmc via adb shell?
Take a look in the Note N7000 forum. they have a thread dealing with repartitioning by adb after emmc got corruptes cells
http://forum.xda-developers.com/showthread.php?t=1667886
ddaharu said:
Does anyone know a step by step instruction to re partition the emmc via adb shell?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1862294
this thread also got the info...
As should be well known, using the current CM14.1 OTA update results in a bootloop into recovery.
I was able to get out of bootloop by zeroing the FOTA and MISC partitions. But, turns out, something in there was important. I can no longer connect to WiFi. (I ran a full reset, wiped system + reinstalled, so I'm fairly certain it was my dumb a** wiping the MISC partition without making a backup first. In fairness, I'd just come home from an 18 hour shift, but I should have known better.)
I'm requesting an image of the misc partition from anyone on here with a working LG G4 H811. The phone can be running any ROM, and prior to flashing was ideally running V20P or V20O (the two stock T-Mo MM builds). The resulting raw image should be 16,777,216 bytes. Compressed as a ZIP, it should be around 31 KB.
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
Thanks in advance!
aorbiy said:
As should be well known, using the current CM14.1 OTA update results in a bootloop into recovery.
I was able to get out of bootloop by zeroing the FOTA and MISC partitions. But, turns out, something in there was important. I can no longer connect to WiFi. (I ran a full reset, wiped system + reinstalled, so I'm fairly certain it was my dumb a** wiping the MISC partition without making a backup first. In fairness, I'd just come home from an 18 hour shift, but I should have known better.)
I'm requesting an image of the misc partition from anyone on here with a working LG G4 H811. The phone can be running any ROM, and prior to flashing was ideally running V20P or V20O (the two stock T-Mo MM builds). The resulting raw image should be 16,777,216 bytes. Compressed as a ZIP, it should be around 31 KB.
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
Thanks in advance!
Click to expand...
Click to collapse
you can download it from here
you've been served....
TURBO
And WiFi works. Beautiful.
BTW, I pulled this up in a hex editor, and noticed the lines "recovery --wipe_data".
Do you know if this have any special meaning, like the next OTA I receive (that works) will wipe data? (I don't really care if it will, but could be useful to know.)
Edit: Nevermind, found the answer at http://forum.xda-developers.com/showpost.php?p=54355114&postcount=486
Thanks for the help! Have a beer on me!
aorbiy said:
And WiFi works. Beautiful.
BTW, I pulled this up in a hex editor, and noticed the lines "recovery --wipe_data".
Do you know if this have any special meaning, like the next OTA I receive (that works) will wipe data? (I don't really care if it will, but could be useful to know.)
Edit: Nevermind, found the answer at http://forum.xda-developers.com/showpost.php?p=54355114&postcount=486
Thanks for the help! Have a beer on me!
Click to expand...
Click to collapse
thank you. my pleasure...... please, allow me to be the first to hit thanks on you.....
TURBO
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