Hey, I was able to make changes to the Heimdall repository to easily gain access to flashing with Linux to the Galaxy Camera. This is important because this is the only way to get a PIT file unless Samsung themselves make changes and issue a new pit.
Here is the PIT for the Samsung Galaxy Camera. http://forum.xda-developers.com/attachment.php?attachmentid=1487728&stc=1&d=1353110552
Here is the partition table:
Code:
Entry Count: 17
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: camera.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5423104
Partition Block Count: 737280
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 6160384
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6176768
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: -
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/code/heimdall/Heimdall/heimdall$
I wanted to log this here for others to use.
To reproduce the changes to Heimdall for the Galaxy Camera, you simply need to "git clone" the heimdall repo located here: https://github.com/Benjamin-Dobell/Heimdall
Then find the line that says kPIDGalaxyS2 in /Heimdall/heimdall/source/BridgeManager.h:
Code:
kPidGalaxyS = 0x6601,
[B]kPidGalaxyS2 = 0x685d,[/B]
kPidDroidCharge = 0x68C3
Then make Heimdall as usual. It's able to pull the Partition Information Table easily.
... And root achieved under Linux. I spoke to Chainfire about CF AutoRoot. He requested a recovery.img. He then posted the binary here. http://download.chainfire.eu/283/CF-Root/CF-Auto-Root/CF-Auto-Root-gd1-ekgc100.zip
I extracted all files from that binary, built heimdall as above and was able to flash. Heimdall will be built for this device soon. I've submitted a ticket.
Code:
[email protected]:~/Desktop/heimdall$ /usr/local/bin/heimdall flash --cache ./cache.img --recovery ./recovery.img
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading CACHE
100%
CACHE upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/Desktop/heimdall$ adb shell
[email protected]:/ $ su
[email protected]:/ #
AdamOutler said:
Here is the partition table:
Click to expand...
Click to collapse
How did you get that?
I'll be posting the table (based on this) in my partition table thread. But it would be better to obtain the output of the standard partition commands...
Actually that list above, makes little sense. Where are the mount points and "block size" is probably not a block size etc... I'd much rather see the output from these commands...
EDIT:
BTW. Have you managed to rip this thing apart yet? I'd love to see some internal pictures...
Hey Adam thanks for this but one question, should I use this pit file with heimdall or with odin, in both cases which firmware gave you this pit partitioning( on the mexican sgs sometimes different firmwares had different pit)
thanks!
I set up a job to analyze PIT files over at http://jenkins.CASUAL-Dev.com and you can analyze PIT files with more accuracy there.
This is my own breed of Print-Pit.
Code:
PIT Name: Mx
Entry Count: 17
File Type: COM_TAR2
--- Entry #0 ---
ID: 80 Partition Name: BOOTLOADER
Filename: sboot.bin param: md5
Block Size: 1734 (887.8kB)
Block range: 0 - 1733 (hex 0x0 - 0x6c5)
PartType: 2 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOOTLOADER partition, identified as partition number 80, is 887.8kB in size. It carries a Basic format and Bootloader data type. The partition resides on the AP EMMC. It identifies itself to Odin as sboot.bin param: md5.
--- Entry #1 ---
ID: 81 Partition Name: TZSW
Filename: tz.img param: md5
Block Size: 312 (159.7kB)
Block range: 1734 - 2045 (hex 0x6c6 - 0x7fd)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The TZSW partition, identified as partition number 81, is 159.7kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as tz.img param: md5.
--- Entry #2 ---
ID: 70 Partition Name: PIT
Filename: camera.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 70, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as camera.pit.
--- Entry #3 ---
ID: 71 Partition Name: MD5HDR
Filename: md5.img param: in.md5
Block Size: 2048 (1.0MB)
Block range: 50 - 2097 (hex 0x32 - 0x831)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MD5HDR partition, identified as partition number 71, is 1.0MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as md5.img param: in.md5.
--- Entry #4 ---
ID: 1 Partition Name: BOTA0
Filename: -
Block Size: 8192 (4.2MB)
Block range: 8192 - 16383 (hex 0x2000 - 0x3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOTA0 partition, identified as partition number 1, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #5 ---
ID: 2 Partition Name: BOTA1
Filename: -
Block Size: 8192 (4.2MB)
Block range: 16384 - 24575 (hex 0x4000 - 0x5fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOTA1 partition, identified as partition number 2, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #6 ---
ID: 3 Partition Name: EFS
Filename: efs.img param: md5
Block Size: 40960 (21.0MB)
Block range: 24576 - 65535 (hex 0x6000 - 0xffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 3, is 21.0MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as efs.img param: md5.
--- Entry #7 ---
ID: 4 Partition Name: PARAM
Filename: param.bin param: md5
Block Size: 16384 (8.4MB)
Block range: 65536 - 81919 (hex 0x10000 - 0x13fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 4, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as param.bin param: md5.
--- Entry #8 ---
ID: 5 Partition Name: BOOT
Filename: boot.img param: md5
Block Size: 16384 (8.4MB)
Block range: 81920 - 98303 (hex 0x14000 - 0x17fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOOT partition, identified as partition number 5, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as boot.img param: md5.
--- Entry #9 ---
ID: 6 Partition Name: RECOVERY
Filename: recovery.img param: md5
Block Size: 16384 (8.4MB)
Block range: 98304 - 114687 (hex 0x18000 - 0x1bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 6, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as recovery.img param: md5.
--- Entry #10 ---
ID: 7 Partition Name: RADIO
Filename: modem.bin param: md5
Block Size: 65536 (33.6MB)
Block range: 114688 - 180223 (hex 0x1c000 - 0x2bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RADIO partition, identified as partition number 7, is 33.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as modem.bin param: md5.
--- Entry #11 ---
ID: 8 Partition Name: CACHE
Filename: cache.img param: md5
Block Size: 2097152 (1.1GB)
Block range: 180224 - 2277375 (hex 0x2c000 - 0x22bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 8, is 1.1GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as cache.img param: md5.
--- Entry #12 ---
ID: 9 Partition Name: SYSTEM
Filename: system.img param: md5
Block Size: 3145728 (1.6GB)
Block range: 2277376 - 5423103 (hex 0x22c000 - 0x52bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SYSTEM partition, identified as partition number 9, is 1.6GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as system.img param: md5.
--- Entry #13 ---
ID: 10 Partition Name: HIDDEN
Filename: hidden.img param: md5
Block Size: 737280 (377.5MB)
Block range: 5423104 - 6160383 (hex 0x52c000 - 0x5dffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The HIDDEN partition, identified as partition number 10, is 377.5MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as hidden.img param: md5.
--- Entry #14 ---
ID: 11 Partition Name: OTA
Filename: -
Block Size: 16384 (8.4MB)
Block range: 6160384 - 6176767 (hex 0x5e0000 - 0x5e3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The OTA partition, identified as partition number 11, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #15 ---
ID: 12 Partition Name: TDATA param: TA
Filename: - param: erdata.img param: md5
Block Size: 409600 (209.7MB)
Block range: 6176768 - 6586367 (hex 0x5e4000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: param: emained
The TDATA param: TA partition, identified as partition number 12, is 209.7MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC.
--- Entry #16 ---
ID: 13 Partition Name: USERDATA
Filename: userdata.img
Block Size: 0 (0B)
Block range: 6586368 - 6586367 (hex 0x648000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: remained
The USERDATA partition, identified as partition number 13, is 0B in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as userdata.img. The partition will expand to fill the remainder of the EMMC.
Here's the PIT file: http://d-h.st/3B3
Here's the link where you can analyze a PIT: http://jenkins.casual-dev.com/job/Analyze PIT File/build?delay=0sec
This is for the Freescale IMX6Q tablet (Zenithink C-94). This really is a good tablet that never got a chance. Originally came out with ICS 4.0 on it. Freescale released the source for Jelly Bean 4.3. I have built a rom from that source (and a AOSPA+ rom) , but the problem is with Zenithink. There are the proprietary blobs patched to the "boot.img" and "uImage_update". I need these blobs to get the tablet to initialize, but Zenithink hides behind a wall of silence. I have requested the source for the u-boot and boot.img, but have gotten squat. I have tried to pressure them by reporting a GPL violation here: [email protected] and so far nothing. I have been left with reverse engineering this.
The "uImage_update" is essentially a uImage by what I can tell. On this tablet this writes to partition mmcblk08; basically a pre-file system that is up and running at initialization. The kicker is this is what I pulled off that:
Linux rev 1.0 ext4 filesystem data, UUID=80720123-59a2-fc56-b69d-aaf1e69ad9ae, volume name "vender" (extents) (large files)
This is a dev/zero section on that partition; meaning it overwrites the data from the first initramfs with zeros. Try to go into an adb shell:
Code:
cat /dev/zero
and you'll see what I mean; you get nothing shown. I have extracted the initramfs from this uImage_update and this is what it looks like:
http://www.mediafire.com/download/6e30ctaz6ydn58t/initramfs_uImage.zip
This is very different from what I have seen. I then extracted and decompressed the .gzip data file out of the uImage_update and named it "update". I then typed:
Code:
binwalk update > update.walk
to get this:
Code:
DECIMAL HEX DESCRIPTION
-------------------------------------------------------------------------------------------------------
185916 0x2D63C ASCII cpio archive (SVR4 with no CRC), file name: "system"
186036 0x2D6B4 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib"
186160 0x2D730 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libc.so"
468472 0x725F8 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2_e2p.so"
487080 0x76EA8 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libusbhost.so"
496836 0x794C4 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libcutils.so"
560808 0x88EA8 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2_uuid.so"
570612 0x8B4F4 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext4_utils.so"
622588 0x97FFC ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/liblog.so"
636540 0x9B67C ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libstdc++.so"
642124 0x9CC4C ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libz.so"
738176 0xB4380 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2fs.so"
843628 0xCDF6C ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2_blkid.so"
872304 0xD4F70 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2_com_err.so"
882096 0xD75B0 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libm.so"
969572 0xECB64 ASCII cpio archive (SVR4 with no CRC), file name: "system/lib/libext2_profile.so"
983680 0xF0280 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin"
983804 0xF02FC ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/toolbox"
1091336 0x10A708 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/ext4fixup"
1097032 0x10BD48 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/setup_fs"
1102812 0x10D3DC ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/newfs_msdos"
1210348 0x1277EC ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/linker"
1250068 0x131314 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/sh"
1402156 0x15652C ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/ext2simg"
1412060 0x158BDC ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/mke2fs"
1447104 0x1614C0 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/mkdosfs"
1554636 0x17B8CC ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/make_ext4fs"
1560344 0x17CF18 ASCII cpio archive (SVR4 with no CRC), file name: "system/bin/logcat"
1574488 0x180658 ASCII cpio archive (SVR4 with no CRC), file name: "sbin"
1574604 0x1806CC ASCII cpio archive (SVR4 with no CRC), file name: "sbin/test.sh"
1577204 0x1810F4 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh_1"
1579444 0x1819B4 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh_2"
1581776 0x1822D0 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/ueventd"
1680556 0x19A4AC ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh2"
1684784 0x19B530 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh"
1689836 0x19C8EC ASCII cpio archive (SVR4 with no CRC), file name: "sbin/ts_calibrator"
1748816 0x1AAF50 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/busybox"
3383044 0x339F04 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/sh"
3535128 0x35F118 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh_5"
3540032 0x360440 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/recovery"
3818032 0x3A4230 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh3"
3821452 0x3A4F8C ASCII cpio archive (SVR4 with no CRC), file name: "sbin/adbd"
3964160 0x3C7D00 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh_v0.1"
3968736 0x3C8EE0 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/mkext2.sh"
3971392 0x3C9940 ASCII cpio archive (SVR4 with no CRC), file name: "sbin/product_tool.sh_v0.2"
3974620 0x3CA5DC ASCII cpio archive (SVR4 with no CRC), file name: "ueventd.freescale.rc"
3977084 0x3CAF7C ASCII cpio archive (SVR4 with no CRC), file name: "sys"
3977200 0x3CAFF0 ASCII cpio archive (SVR4 with no CRC), file name: "tmp"
3977316 0x3CB064 ASCII cpio archive (SVR4 with no CRC), file name: "ueventd.goldfish.rc"
3977720 0x3CB1F8 ASCII cpio archive (SVR4 with no CRC), file name: "res"
3977836 0x3CB26C ASCII cpio archive (SVR4 with no CRC), file name: "res/images"
3977960 0x3CB2E8 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing.png"
4003368 0x3D1628 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate01.png"
4004188 0x3D195C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/progress_fill.png"
4004732 0x3D1B7C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate03.png"
4005540 0x3D1EA4 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay07.png"
4015756 0x3D468C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay02.png"
4025900 0x3D6E2C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate04.png"
4026712 0x3D7158 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_error.png"
4046156 0x3DBD4C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay04.png"
4056128 0x3DE440 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay05.png"
4066144 0x3E0B60 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate05.png"
4066972 0x3E0E9C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay03.png"
4076908 0x3E356C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate02.png"
4077740 0x3E38AC ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay06.png"
4087836 0x3E601C ASCII cpio archive (SVR4 with no CRC), file name: "res/images/progress_empty.png"
4088096 0x3E6120 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/indeterminate06.png"
4088916 0x3E6454 ASCII cpio archive (SVR4 with no CRC), file name: "res/images/icon_installing_overlay01.png"
4099164 0x3E8C5C ASCII cpio archive (SVR4 with no CRC), file name: "res/keys"
4100692 0x3E9254 ASCII cpio archive (SVR4 with no CRC), file name: "ueventd.rc"
4104644 0x3EA1C4 ASCII cpio archive (SVR4 with no CRC), file name: "data"
4104760 0x3EA238 ASCII cpio archive (SVR4 with no CRC), file name: "init"
4203532 0x40240C ASCII cpio archive (SVR4 with no CRC), file name: "init.rc"
4205208 0x402A98 ASCII cpio archive (SVR4 with no CRC), file name: "proc"
4205324 0x402B0C ASCII cpio archive (SVR4 with no CRC), file name: "default.prop"
4206964 0x403174 ASCII cpio archive (SVR4 with no CRC), file name: "etc"
4207080 0x4031E8 ASCII cpio archive (SVR4 with no CRC), file name: "etc/recovery.fstab"
4207564 0x4033CC ASCII cpio archive (SVR4 with no CRC), file name: "dev"
4207680 0x403440 ASCII cpio archive (SVR4 with no CRC), file name: "mkext2.sh"
4210328 0x403E98 ASCII cpio archive (SVR4 with no CRC), file name: "TRAILER!!!"
10454976 0x9F87C0 Linux kernel version "3.0.35 ([email protected]) (gcc version 4.4.3 (GCC) ) #258 SMP PRersion 4.4.3 (GCC) ) #258 SMP PREEMPT Mon Nov 19 18:58:49 CST 2REEMPT Mon Nov 19 18:58:49 CST 20122012"
10468824 0x9FBDD8 LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 50331648 bytes
10470224 0x9FC350 gzip compressed data, from Unix, NULL date: Wed Dec 31 17:00:00 1969, max compression
10489368 0xA00E18 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 50331648 bytes
10546214 0xA0EC26 LZMA compressed data, properties: 0x02, dictionary size: 33554432 bytes, uncompressed size: 133128 bytes
10596880 0xA1B210 LZMA compressed data, properties: 0x48, dictionary size: 33554432 bytes, uncompressed size: 50331648 bytes
10597168 0xA1B330 LZMA compressed data, properties: 0x03, dictionary size: 16777216 bytes, uncompressed size: 67108864 bytes
10615161 0xA1F979 LZMA compressed data, properties: 0x75, dictionary size: 1048576 bytes, uncompressed size: 262144 bytes
10615197 0xA1F99D LZMA compressed data, properties: 0x6E, dictionary size: 1048576 bytes, uncompressed size: 262144 bytes
10615233 0xA1F9C1 LZMA compressed data, properties: 0x64, dictionary size: 1048576 bytes, uncompressed size: 262144 bytes
10625784 0xA222F8 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 167772160 bytes
10678417 0xA2F091 LZMA compressed data, properties: 0x02, dictionary size: 1048576 bytes, uncompressed size: 50593792 bytes
10698516 0xA33F14 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 92372993 bytes
10698732 0xA33FEC LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 25231361 bytes
10698828 0xA3404C LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 16842753 bytes
10698900 0xA34094 LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 25296897 bytes
10699044 0xA34124 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 151060737 bytes
10699116 0xA3416C LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 92340481 bytes
10699188 0xA341B4 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 151060737 bytes
10699260 0xA341FC LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 92340481 bytes
10706088 0xA35CA8 LZMA compressed data, properties: 0x0A, dictionary size: 33554432 bytes, uncompressed size: 33554434 bytes
10713427 0xA37953 LZMA compressed data, properties: 0xC0, dictionary size: 65536 bytes, uncompressed size: 1 bytes
10735476 0xA3CF74 LZMA compressed data, properties: 0x02, dictionary size: 33554432 bytes, uncompressed size: 234881024 bytes
11474468 0xAF1624 ASCII cpio archive (SVR4 with no CRC), file name: "oop (skipped) already calibrated this CPU"
12398841 0xBD30F9 LZMA compressed data, properties: 0x04, dictionary size: 65536 bytes, uncompressed size: 98304000 bytes
12430328 0xBDABF8 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 4 bytes
12430373 0xBDAC25 LZMA compressed data, properties: 0x02, dictionary size: 65536 bytes, uncompressed size: 1179648 bytes
12460472 0xBE21B8 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 50331648 bytes
12466532 0xBE3964 LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 33554432 bytes
12473624 0xBE5518 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 50331648 bytes
12474072 0xBE56D8 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 50331648 bytes
12513680 0xBEF190 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 1 bytes
12544155 0xBF689B LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2057732 bytes
12544175 0xBF68AF LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2049025 bytes
12544195 0xBF68C3 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2050048 bytes
12544215 0xBF68D7 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2032640 bytes
12544235 0xBF68EB LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2049281 bytes
12544255 0xBF68FF LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2049537 bytes
12544275 0xBF6913 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2049792 bytes
12544295 0xBF6927 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 1847574 bytes
12544315 0xBF693B LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 1843222 bytes
12544435 0xBF69B3 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12722196 bytes
12544475 0xBF69DB LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12722198 bytes
12544695 0xBF6AB7 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 66070 bytes
12544895 0xBF6B7F LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15679511 bytes
12544915 0xBF6B93 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526989 bytes
12544935 0xBF6BA7 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526990 bytes
12544955 0xBF6BBB LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526913 bytes
12544975 0xBF6BCF LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526922 bytes
12544995 0xBF6BE3 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526849 bytes
12545015 0xBF6BF7 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526850 bytes
12545035 0xBF6C0B LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526851 bytes
12545055 0xBF6C1F LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 12526852 bytes
12545075 0xBF6C33 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2105360 bytes
12545535 0xBF6DFF LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2126102 bytes
12545555 0xBF6E13 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2126614 bytes
12545575 0xBF6E27 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2122518 bytes
12545595 0xBF6E3B LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 2126103 bytes
12545635 0xBF6E63 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675410 bytes
12545655 0xBF6E77 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675411 bytes
12545675 0xBF6E8B LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675412 bytes
12545695 0xBF6E9F LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675413 bytes
12545715 0xBF6EB3 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675414 bytes
12545735 0xBF6EC7 LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15679510 bytes
12545755 0xBF6EDB LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15675415 bytes
12545775 0xBF6EEF LZMA compressed data, properties: 0x01, dictionary size: 65536 bytes, uncompressed size: 15679511 bytes
12554493 0xBF90FD LZMA compressed data, properties: 0x02, dictionary size: 1048576 bytes, uncompressed size: 1073741824 bytes
12554517 0xBF9115 LZMA compressed data, properties: 0x02, dictionary size: 1048576 bytes, uncompressed size: 1073741824 bytes
12554589 0xBF915D LZMA compressed data, properties: 0x02, dictionary size: 2097152 bytes, uncompressed size: 1073741824 bytes
12554613 0xBF9175 LZMA compressed data, properties: 0x02, dictionary size: 2097152 bytes, uncompressed size: 1073741824 bytes
12554685 0xBF91BD LZMA compressed data, properties: 0x02, dictionary size: 4194304 bytes, uncompressed size: 1073741824 bytes
12554709 0xBF91D5 LZMA compressed data, properties: 0x02, dictionary size: 4194304 bytes, uncompressed size: 1073741824 bytes
12554781 0xBF921D LZMA compressed data, properties: 0x02, dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
12554805 0xBF9235 LZMA compressed data, properties: 0x02, dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
12554829 0xBF924D LZMA compressed data, properties: 0x02, dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
12554949 0xBF92C5 LZMA compressed data, properties: 0x02, dictionary size: 16777216 bytes, uncompressed size: 1073741824 bytes
12560849 0xBFA9D1 LZMA compressed data, properties: 0x13, dictionary size: 65536 bytes, uncompressed size: 7340032 bytes
12568984 0xBFC998 LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 2 bytes
12569104 0xBFCA10 LZMA compressed data, properties: 0x09, dictionary size: 131072 bytes, uncompressed size: 2 bytes
12569124 0xBFCA24 LZMA compressed data, properties: 0x0A, dictionary size: 131072 bytes, uncompressed size: 2 bytes
12573615 0xBFDBAF LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12573635 0xBFDBC3 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12573655 0xBFDBD7 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12573675 0xBFDBEB LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12573695 0xBFDBFF LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12573715 0xBFDC13 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 896 bytes
12580217 0xBFF579 LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 49276 bytes
12605245 0xC0573D LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12605429 0xC057F5 LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12605613 0xC058AD LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12605797 0xC05965 LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12606165 0xC05AD5 LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12606809 0xC05D59 LZMA compressed data, properties: 0x01, dictionary size: 131072 bytes, uncompressed size: 196608 bytes
12631676 0xC0BE7C LZMA compressed data, properties: 0x01, dictionary size: 33554432 bytes, uncompressed size: 456912 bytes
12636813 0xC0D28D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12636901 0xC0D2E5 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12636989 0xC0D33D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637077 0xC0D395 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637165 0xC0D3ED LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637253 0xC0D445 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637341 0xC0D49D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637429 0xC0D4F5 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637457 0xC0D511 LZMA compressed data, properties: 0x01, dictionary size: 8388608 bytes, uncompressed size: 2097152 bytes
12637501 0xC0D53D LZMA compressed data, properties: 0x01, dictionary size: 8388608 bytes, uncompressed size: 2097152 bytes
12637517 0xC0D54D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637605 0xC0D5A5 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637693 0xC0D5FD LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637781 0xC0D655 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637869 0xC0D6AD LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12637957 0xC0D705 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638045 0xC0D75D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638133 0xC0D7B5 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638221 0xC0D80D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638309 0xC0D865 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638397 0xC0D8BD LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638485 0xC0D915 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638573 0xC0D96D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638661 0xC0D9C5 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638749 0xC0DA1D LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638837 0xC0DA75 LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12638925 0xC0DACD LZMA compressed data, properties: 0x04, dictionary size: 262144 bytes, uncompressed size: 65536 bytes
12640200 0xC0DFC8 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 654311424 bytes
12640232 0xC0DFE8 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 654311424 bytes
12640264 0xC0E008 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 704643072 bytes
12640296 0xC0E028 LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 704643072 bytes
12646716 0xC0F93C LZMA compressed data, properties: 0x01, dictionary size: 16777216 bytes, uncompressed size: 50331648 bytes
12661391 0xC1328F LZMA compressed data, properties: 0xC0, dictionary size: 524288 bytes, uncompressed size: 720896 bytes
12675172 0xC16864 LZMA compressed data, properties: 0x02, dictionary size: 33554432 bytes, uncompressed size: 134217728 bytes
This, as you can see, shows the cpio, kernel, gzip, and LZMA files. The .gzip here is the configuration file for the kernel. I did the same with the uImage I built, from the freescale ICS source. This was done so I could compare the to images to isolate the extra files from Zenithink. Then I compared the ICS source to the JB 4.3 source I built to see the changes from ISC to JB. The kernels are essentially the same. I know that threre will be a difference between the builds (ICS=GCC 4.4.3 and JB=GCC 4.6). I extracted these extra (.LZMA) files (binaries) from the original uImage_update to put into the JB uImage.
Next, was the boot.img to boot up the device. I have extracted the initramfs from that:
http://www.mediafire.com/download/5yj8mq7lw2grtlm/initramfs_boot.zip
As one can see, this is very different form the uImage_update. I followed the process as I did with above and I extracted the extra (.LZMA) files (binaries) from the original boot.img to put into the JB boot.img. So now you have a little history traveling down this rabbit hole, My question is:
How do I put these .LZMA files into the JB uImage (to be built and named "uImage_update") and JB boot.img? I do know it comes down to the uImage_update and boot.img to get this to work. I've tried updating the "initramfs" to match the way it is in JB, for both these images, but that did not work. I know someone here can help with this. Please help. Any and all help would be greatly appreciated.
Thanks,
Hello All,
I bought Motorola G52 PAU70015IN (India) 6|128 variant on 22nd December 2022 via Flipkart. Here I will some guides and general info for Motorola G52
Specifications
Spoiler
169 grams lightweight
6.6in 90Hz FHD+ pOLED display
33w fast charging support with charger included in box
4G with Carrier Aggregation Support
Stereo Speakers with Dolby Atmos support, Secondary Noise Cancellation Mic
50MP main camera + 8 MP Ultrawide + 2MP Macro at back and 16MP front
Side mounted finger-print scanner, NFC support, IP52 rated
HDR10 and Widevine L1 support
UFS(2.1?) storage(uMCP)
Snapdragon 680 SM6225(Khaje)
5000 mAh with Type-C port
Android 12 and can be upgraded to 13
See all detailed specifications at https://www.motorola.in/smartphone-motorola-moto-g52/p and https://www.xda-developers.com/moto...lay-snapdragon-680-soc-and-a-5000mah-battery/
Software Info
Spoiler
Codename: rhode
Bootloader Unlockable (read this before doing)
Near to Stock Android 12 and upgradable to Android 13
Firmware: https://mirrors.lolinet.com/firmware/motorola/rhode/official/
Spoiler: Applications
List of Stock Moto Apps that can be available in Play Store
Moto Widget
Interactive Wallpapers
Device Help
Moto Gametime
FM Radio
Moto App
Moto Camera 3
Camera Tuner 4
Moto Camera Content 3
Moto Tour
Moto Actions
Moto Display
Moto Power Touch
Moto Face Unlock
Screenshot Editor
Moto AI Services
Moto Update Services
Moto Feedback
Recorder
Camera Desktop Settings
Easy Prefix
Moto Notifications
Guides by G52 Community
http://rentry.co/g52g_m or http://rentry.org/g52g_m
Guides by @sd_shadow
Spoiler
Unlocking Bootloader
Rooting with Magisk
Flashing Firmware
Flashing and Unbricking
Bootloader Unlock & Flashing
Spoiler
Warning: Don't unlock bootloader if you don't know how to correctly lock bootloader, since locking bootloader seems like scary thing in Moto because if you fail to restore Stock fully and relock bootloader, you can't able to flash anything with the available free flashing tools and resources. So proceed with care.
Also Widevine will become L3 from L1.
Unlike Google, Xiaomi, OnePlus, Realme bootloader unlocking in Motorola mobiles will VOID WARRANTY
See official guide at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Legal Terms at https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/89425
Spoiler: Flashing
This device comes with Virtual A/B Partition Scheme. This means most of the partitions are doubled with _a and _b suffixes like boot_a and boot_b.
Some development links
Spoiler
Causes of Hard Brick
Locking Bootloader
Moto G60
Moto G100
Changing slots
Moto G7 Power
Bad flashing
Motorola Nexus 6
Because of downgrading
Moto G7 Plus (seems like downgrade in oem_locked)
Because of downgrading and locking
Moto G60
Moto G60 another guy
Moto G30
Because of downgrading and OTA updating
Moto Z Play
Moto Z Play (another)
Moto X Pure (SD Card Method)
Locking bootloader with custom images or other region stock roms
Moto Razr 5G
Moto G 5G Plus, xda
Moto G10
Moto G40
Misc Unbrick guides
Moto G6 Plus
Moto G5 Unbrick(SD Card Method)
Note:- Since our device uses UFS, SD Card Method will not work in devices with UFS. So only blankflash method is remaining.
Building blank flashes
Build blank flash yourself
Reddit Guide
Generating singleimage.bin (old disk image format)
HemanthJabalpuri said:
Hello All,
I bought Motorola G52(India) 6|128 variant on 22nd December 2022 via Flipkart. Here I will some guides and general info for Motorola G52
Specifications
169 grams lightweight
6.6in 90Hz FHD+ pOLED display
33w fast charging support with charger included in box
Stereo Speakers with Dolby Atmos support
50MP main camera + 8 MP Ultrawide + 2MP Macro at back and 16MP front
NFC support, IP52 rated
UFS storage(uMCP)
Snapdragon 680
5000 mAh with Type-C port
Android 12 and can be upgraded to 13
See all detailed specifications at https://www.xda-developers.com/moto...lay-snapdragon-680-soc-and-a-5000mah-battery/
Click to expand...
Click to collapse
Hello and good morning, @HemanthJabalpuri
Please read the sub-title of the forum you've originally posted in:
Miscellaneous Android Development
For ROMs, kernels, tools and scripts only (devices that do not have a forum on XDA)
forum.xda-developers.com
I've moved the thread to General Topics but also deleted the two posts that you called "Reserved". Such placeholder posts are only accepted for developers in their own development thread.
Regards
Oswald Boelcke
Senior Moderator
Partition Info of Moto G52.
Since G52 uses UFS it is divided into Logical UNits(LUNs). It has 6 LUNs.
Spoiler
LUN 0 - /dev/bloc/by-name/sda
Spoiler
Code:
:/ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 4096 sectors, 16.0 MiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): EF690DA0-C557-D70D-D98A-2DB36D02AA99
Partition table holds up to 3 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 4090
Partitions will be aligned on 32-sector boundaries
Total free space is 1781 sectors (7.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 32 2079 8.0 MiB FFFF hw
2 2080 2335 1024.0 KiB A01A ddr
3 2336 4090 6.9 MiB FFFF last_parti0
LUN 1 - /dev/bloc/by-name/sdb
Spoiler
Code:
:/ # sgdisk --print /dev/block/sdb
Disk /dev/block/sdb: 2048 sectors, 8.0 MiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): B4445DF1-19FF-620B-E822-98B3F9488AA5
Partition table holds up to 3 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 2042
Partitions will be aligned on 32-sector boundaries
Total free space is 693 sectors (2.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 32 1311 5.0 MiB A012 xbl_a
2 1312 1375 256.0 KiB FFFF xbl_config_a
3 1376 2042 2.6 MiB FFFF last_parti2
LUN 2 - /dev/bloc/by-name/sdc
Spoiler
Code:
:/ # sgdisk --print /dev/block/sdc
Disk /dev/block/sdc: 2048 sectors, 8.0 MiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): F0179B06-DF74-8244-33FA-4766C3717289
Partition table holds up to 3 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 2042
Partitions will be aligned on 32-sector boundaries
Total free space is 693 sectors (2.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 32 1311 5.0 MiB A012 xbl_b
2 1312 1375 256.0 KiB FFFF xbl_config_b
3 1376 2042 2.6 MiB FFFF last_parti3
LUN 3 - /dev/bloc/by-name/sdd
Spoiler
Code:
:/ # sgdisk --print /dev/block/sdd
Disk /dev/block/sdd: 241664 sectors, 944.0 MiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): D63153E7-E4F9-BE40-6F55-F0BF0FB7AE54
Partition table holds up to 23 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 241658
Partitions will be aligned on 4-sector boundaries
Total free space is 100545 sectors (392.8 MiB)
Number Start (sector) End (sector) Size Code Name
1 32 1055 4.0 MiB A016 tz_a
2 1056 1183 512.0 KiB A018 rpm_a
3 1184 1311 512.0 KiB A017 hyp_a
4 1312 1439 512.0 KiB FFFF cmnlib_a
5 1440 1567 512.0 KiB FFFF cmnlib64_a
6 1568 1695 512.0 KiB FFFF keymaster_a
7 1696 1759 256.0 KiB FFFF prov_a
8 1760 2015 1024.0 KiB FFFF abl_a
9 2016 2527 2.0 MiB FFFF uefisecapp_a
10 2528 2559 128.0 KiB FFFF devcfg_a
11 2560 2579 80.0 KiB FFFF qupfw_a
12 2580 2611 128.0 KiB FFFF storsec_a
13 2612 48691 180.0 MiB 0700 modem_a
14 48692 48947 1024.0 KiB FFFF bluetooth_a
15 48948 65331 64.0 MiB FFFF dsp_a
16 65332 89907 96.0 MiB A036 boot_a
17 89908 96051 24.0 MiB FFFF dtbo_a
18 96064 120639 96.0 MiB FFFF vendor_boot_a
19 120640 124735 16.0 MiB FFFF logo_a
20 124736 124751 64.0 KiB FFFF vbmeta_a
21 124752 124767 64.0 KiB FFFF vbmeta_system_a
22 124768 141151 64.0 MiB A02A fsg_a
23 141152 241658 392.6 MiB FFFF last_parti4
LUN 4 - /dev/bloc/by-name/sde
Spoiler
Code:
:/ # sgdisk --print /dev/block/sde
Disk /dev/block/sde: 30746624 sectors, 117.3 GiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): AFB60E86-7175-40A3-5246-E51DDBC51F11
Partition table holds up to 27 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 30746618
Partitions will be aligned on 1-sector boundaries
Total free space is 142 sectors (568.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 32 33 8.0 KiB A02C ssd
2 64 8255 32.0 MiB A026 persist
3 8256 10303 8.0 MiB A026 prodpersist
4 10304 10559 1024.0 KiB A01F misc
5 10560 10687 512.0 KiB FFFF frp
6 10688 10815 512.0 KiB FFFF utags
7 10816 10943 512.0 KiB FFFF utagsBackup
8 10944 10975 128.0 KiB FFFF cid
9 10976 15071 16.0 MiB FFFF metadata
10 15072 17119 8.0 MiB FFFF kpan
11 17120 19167 8.0 MiB FFFF sp
12 19168 23263 16.0 MiB FFFF carrier
13 23264 23903 2.5 MiB A027 modemst1
14 23904 24543 2.5 MiB A028 modemst2
15 24544 24575 128.0 KiB A029 fsc
16 24576 24583 32.0 KiB FFFF dhob
17 24608 24671 256.0 KiB A023 msadp
18 24672 24672 4.0 KiB A021 devinfo
19 24673 26720 8.0 MiB FFFF logfs
20 26721 26784 256.0 KiB A022 apdp
21 26816 28863 8.0 MiB FFFF spunvm
22 28864 28864 4.0 KiB A040 limits
23 28865 28992 512.0 KiB FFFF uefivarstore
24 29024 29055 128.0 KiB FFFF pad3
25 29056 1880447 7.1 GiB FFFF super
26 1880448 1880575 512.0 KiB FFFF pad4
27 1880576 30746618 110.1 GiB A03A userdata
LUN 5 - /dev/bloc/by-name/sdf
Spoiler
Code:
:/ # sgdisk --print /dev/block/sdf
Disk /dev/block/sdf: 241664 sectors, 944.0 MiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): C440EC50-E0CD-DA85-FFB5-BC7D26D3D860
Partition table holds up to 23 entries
Main partition table begins at sector 2 and ends at sector 2
First usable sector is 6, last usable sector is 241658
Partitions will be aligned on 4-sector boundaries
Total free space is 100545 sectors (392.8 MiB)
Number Start (sector) End (sector) Size Code Name
1 32 1055 4.0 MiB FFFF tz_b
2 1056 1183 512.0 KiB FFFF rpm_b
3 1184 1311 512.0 KiB FFFF hyp_b
4 1312 1439 512.0 KiB FFFF cmnlib_b
5 1440 1567 512.0 KiB FFFF cmnlib64_b
6 1568 1695 512.0 KiB FFFF keymaster_b
7 1696 1759 256.0 KiB FFFF prov_b
8 1760 2015 1024.0 KiB FFFF abl_b
9 2016 2527 2.0 MiB FFFF uefisecapp_b
10 2528 2559 128.0 KiB FFFF devcfg_b
11 2560 2579 80.0 KiB FFFF qupfw_b
12 2580 2611 128.0 KiB FFFF storsec_b
13 2612 48691 180.0 MiB FFFF modem_b
14 48692 48947 1024.0 KiB FFFF bluetooth_b
15 48948 65331 64.0 MiB FFFF dsp_b
16 65332 89907 96.0 MiB FFFF boot_b
17 89908 96051 24.0 MiB FFFF dtbo_b
18 96064 120639 96.0 MiB FFFF vendor_boot_b
19 120640 124735 16.0 MiB FFFF logo_b
20 124736 124751 64.0 KiB FFFF vbmeta_b
21 124752 124767 64.0 KiB FFFF vbmeta_system_b
22 124768 141151 64.0 MiB FFFF fsg_b
23 141152 241658 392.6 MiB FFFF last_parti5
We can use sgdisk --info=<part_num> disk command get partition information
Spoiler
Code:
:/ # sgdisk --info=1 /dev/block/sda
Partition GUID code: B2D77EC0-8957-11E5-AF63-FEFF819CDC9F (Unknown)
Partition unique GUID: 6025B0D2-2210-068C-B204-B5C0B7B3789E
First sector: 32 (at 128.0 KiB)
Last sector: 2079 (at 8.1 MiB)
Partition size: 2048 sectors (8.0 MiB)
Attribute flags: 1000000000000020
Partition name: 'hw'
Since this is a Virtual A/B device, here is the Super partition scheme
Spoiler
Before Update or When we flash stock ROM manually from fastboot
Code:
:/ # lpdump -a
Current slot: _a
Slot 0:
Metadata version: 10.2
Metadata size: 1000 bytes
Metadata max size: 65536 bytes
Metadata slot count: 3
Header flags: virtual_ab_device
Partition table:
------------------------
Name: product_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 5895927 linear super 2048
------------------------
Name: product_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: system_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1746159 linear super 5898240
------------------------
Name: system_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
0 .. 76175 linear super 7645184
------------------------
Name: system_ext_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1858519 linear super 7723008
------------------------
Name: system_ext_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: vendor_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1513143 linear super 9582592
------------------------
Name: vendor_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Super partition layout:
------------------------
super: 2048 .. 5897976: product_a (5895928 sectors)
super: 5898240 .. 7644400: system_a (1746160 sectors)
super: 7645184 .. 7721360: system_b (76176 sectors)
super: 7723008 .. 9581528: system_ext_a (1858520 sectors)
super: 9582592 .. 11095736: vendor_a (1513144 sectors)
------------------------
Block device table:
------------------------
Partition name: super
First sector: 2048
Size: 7583301632 bytes
Flags: none
------------------------
Group table:
------------------------
Name: default
Maximum size: 0 bytes
Flags: none
------------------------
Name: mot_dp_group_a
Maximum size: 7579107328 bytes
Flags: none
------------------------
Name: mot_dp_group_b
Maximum size: 7579107328 bytes
Flags: none
------------------------
Slot 1:
Metadata version: 10.2
Metadata size: 1000 bytes
Metadata max size: 65536 bytes
Metadata slot count: 3
Header flags: virtual_ab_device
Partition table:
------------------------
Name: product_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 5895927 linear super 2048
------------------------
Name: product_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: system_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1746159 linear super 5898240
------------------------
Name: system_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
0 .. 76175 linear super 7645184
------------------------
Name: system_ext_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1858519 linear super 7723008
------------------------
Name: system_ext_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: vendor_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1513143 linear super 9582592
------------------------
Name: vendor_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Super partition layout:
------------------------
super: 2048 .. 5897976: product_a (5895928 sectors)
super: 5898240 .. 7644400: system_a (1746160 sectors)
super: 7645184 .. 7721360: system_b (76176 sectors)
super: 7723008 .. 9581528: system_ext_a (1858520 sectors)
super: 9582592 .. 11095736: vendor_a (1513144 sectors)
------------------------
Block device table:
------------------------
Partition name: super
First sector: 2048
Size: 7583301632 bytes
Flags: none
------------------------
Group table:
------------------------
Name: default
Maximum size: 0 bytes
Flags: none
------------------------
Name: mot_dp_group_a
Maximum size: 7579107328 bytes
Flags: none
------------------------
Name: mot_dp_group_b
Maximum size: 7579107328 bytes
Flags: none
------------------------
:/ #
After update
Code:
:/ # lpdump -a
Current slot: _b
Slot 0:
Metadata version: 10.2
Metadata size: 1000 bytes
Metadata max size: 65536 bytes
Metadata slot count: 3
Header flags: virtual_ab_device
Partition table:
------------------------
Name: product_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 5895991 linear super 2048
------------------------
Name: product_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: system_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1746231 linear super 5898240
------------------------
Name: system_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
0 .. 76199 linear super 7645184
------------------------
Name: system_ext_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1853231 linear super 7723008
------------------------
Name: system_ext_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Name: vendor_a
Group: mot_dp_group_a
Attributes: readonly
Extents:
0 .. 1513143 linear super 9576448
------------------------
Name: vendor_b
Group: mot_dp_group_b
Attributes: readonly
Extents:
------------------------
Super partition layout:
------------------------
super: 2048 .. 5898040: product_a (5895992 sectors)
super: 5898240 .. 7644472: system_a (1746232 sectors)
super: 7645184 .. 7721384: system_b (76200 sectors)
super: 7723008 .. 9576240: system_ext_a (1853232 sectors)
super: 9576448 .. 11089592: vendor_a (1513144 sectors)
------------------------
Block device table:
------------------------
Partition name: super
First sector: 2048
Size: 7583301632 bytes
Flags: none
------------------------
Group table:
------------------------
Name: default
Maximum size: 0 bytes
Flags: none
------------------------
Name: mot_dp_group_a
Maximum size: 7579107328 bytes
Flags: none
------------------------
Name: mot_dp_group_b
Maximum size: 7579107328 bytes
Flags: none
------------------------
Slot 1:
Metadata version: 10.2
Metadata size: 1096 bytes
Metadata max size: 65536 bytes
Metadata slot count: 3
Header flags: virtual_ab_device
Partition table:
------------------------
Name: product_b
Group: mot_dp_group_b
Attributes: readonly,updated
Extents:
0 .. 5895991 linear super 2048
------------------------
Name: system_b
Group: mot_dp_group_b
Attributes: readonly,updated
Extents:
0 .. 1746607 linear super 5898240
------------------------
Name: system_ext_b
Group: mot_dp_group_b
Attributes: readonly,updated
Extents:
0 .. 1853311 linear super 7723008
------------------------
Name: vendor_b
Group: mot_dp_group_b
Attributes: readonly,updated
Extents:
0 .. 1513055 linear super 9576448
------------------------
Name: product_b-cow
Group: cow
Attributes: none
Extents:
0 .. 77823 linear super 7645184
77824 .. 122783 linear super 11089920
------------------------
Name: system_b-cow
Group: cow
Attributes: none
Extents:
0 .. 1474551 linear super 11134976
------------------------
Name: system_ext_b-cow
Group: cow
Attributes: none
Extents:
0 .. 586103 linear super 12609536
------------------------
Name: vendor_b-cow
Group: cow
Attributes: none
Extents:
0 .. 1296951 linear super 13196288
------------------------
Super partition layout:
------------------------
super: 2048 .. 5898040: product_b (5895992 sectors)
super: 5898240 .. 7644848: system_b (1746608 sectors)
super: 7645184 .. 7723008: product_b-cow (77824 sectors)
super: 7723008 .. 9576320: system_ext_b (1853312 sectors)
super: 9576448 .. 11089504: vendor_b (1513056 sectors)
super: 11089920 .. 11134880: product_b-cow (44960 sectors)
super: 11134976 .. 12609528: system_b-cow (1474552 sectors)
super: 12609536 .. 13195640: system_ext_b-cow (586104 sectors)
super: 13196288 .. 14493240: vendor_b-cow (1296952 sectors)
------------------------
Block device table:
------------------------
Partition name: super
First sector: 2048
Size: 7583301632 bytes
Flags: none
------------------------
Group table:
------------------------
Name: default
Maximum size: 0 bytes
Flags: none
------------------------
Name: mot_dp_group_b
Maximum size: 7579107328 bytes
Flags: none
------------------------
Name: cow
Maximum size: 0 bytes
Flags: none
------------------------
:/ #
Ref:-
- https://forum.xda-developers.com/t/motorola-moto-g-partitions-explained.3418644/
- https://forum.xda-developers.com/t/...ails-about-luns-and-partition-scheme.4123335/
I am working on making TWRP for Moto G52, for now ROM Flashing is not tested Since Custom ROMs are not available as of this writing.
Present Uses of this TWRP
- Grab logs if GSI fails to boot
- Flash recovery only flashable zips like GApps(used for vanilla GSIs)
I tested flashing NikGApps core for Android 13(from here) when I am on phh AOSP Android 13(from here). Magisk.apk flashing also working.
TWRP Tree at https://github.com/HemanthJabalpuri/twrp_motorola_rhode
Download at https://github.com/HemanthJabalpuri/twrp_motorola_rhode/releases/
I am using prebuilt kernel but here are kernel sources https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-S1SR32.38-87-2
Version infos:- Screenshots attached
Build NumberSecurity PatchS1SR32.38-14-21st March 2022S1SR32.38-251st March 2022S1SR32.38-40-21st April 2022S1SR32.38-87-21st June 2022S1SR32.38-1121st July 2022S1SR32.38-124-31st August 2022S1SR32.38-1321st September 2022S1SRS32.38-132-31st November 2022S1SRS32.38-132-51st January 2023S1SRS32.38-132-81st March 2023S1SRS32.38-132-111st May 2023
OTA Updating with Keeping Root(Magisk)
Put stock boot.img of present installed stock rom version in Internal Storage and flash it using Termux
Code:
su
dd if=/sdcard/boot.img of=/dev/block/by-name/boot$(getprop ro.boot.slot_suffix)
Let OTA download and install but Don't reboot after completion
Go to Magisk -> Install -> Install to Inactive Slot (After OTA) -> OK -> LET'S GO
Now you can reboot and Magisk will be there in updated Android
If you updated without following above procedure and if full stock ROM zip is not available, then you can dump boot partition using adb pull /dev/block/by-name/boot_(current-slot) when in TWRP and patch that boot.img using Magisk and flash
Ref:- this
Was looking for info about this device, thanks!
Hey, thanks for your work. Did you flash the aosp with twrp? Can you give brief instructions here?
dellwit said:
Hey, thanks for your work. Did you flash the aosp with twrp? Can you give brief instructions here?
Click to expand...
Click to collapse
I tried phhusson's Android 13 AOSP GSI and it worked fine. We don't need TWRP to flash any GSI.
Instructions to flash GSI in our device are available at https://github.com/phhusson/treble_experimentations/wiki/Moto-G52
Thanks
HemanthJabalpuri
HemanthJabalpuri said:
Version infos:- Screenshots attached
Build NumberSecurity PatchS1SR32.38-14-21st March 2022S1SR32.38-251st March 2022S1SR32.38-40-21st April 2022S1SR32.38-87-21st June 2022S1SR32.38-1121st July 2022S1SR32.38-124-31st August 2022S1SR32.38-1321st September 2022S1SRS32.38-132-31st November 2022S1SRS32.38-132-51st January 2023
Click to expand...
Click to collapse
On my Moto G52, I don't see the Google Play System update details under Security (OS is on Jan'23 security patch). Under About device, Google Play System shows as being on March 2022 update, which is a year old.
Any ideas why? I haven't logged into my Google account on the device, if that makes any difference.
GCam improves the quality of selfies remarkably well. Selfies look like they have been shot using some premium phone.
Do you have configuration files for GCam for Moto G52? There is a slight reddish tint with Google AWB ON and greenish tint with Google AWB OFF. The tint increases in intensity under sunlight.
TheMystic said:
On my Moto G52, I don't see the Google Play System update details under Security (OS is on Jan'23 security patch). Under About device, Google Play System shows as being on March 2022 update, which is a year old.
Any ideas why? I haven't logged into my Google account on the device, if that makes any difference.
Click to expand...
Click to collapse
Maybe that's the issue(you are not logged in)
GCam improves the quality of selfies remarkably well. Selfies look like they have been shot using some premium phone.
Do you have configuration files for GCam for Moto G52? There is a slight reddish tint with Google AWB ON and greenish tint with Google AWB OFF. The tint increases in intensity under sunlight.
Click to expand...
Click to collapse
Sorry, I use stock one only. In Telegram(Search 'Moto G52') there are some configs available. Since I don't use any of them, I can't post them here.
Thanks
HemanthJabalpuri
HemanthJabalpuri said:
Maybe that's the issue(you are not logged in)
Click to expand...
Click to collapse
That's quite strange. What has my logging in got to do with the security update.
HemanthJabalpuri said:
Sorry, I use stock one only. In Telegram(Search 'Moto G52') there are some configs available. Since I don't use any of them, I can't post them here.
Click to expand...
Click to collapse
You should try GCam from BSG. You'll see a huge improvement with it (mainly on selfies) over the stock camera app.
@TheMystic
seems like there are GCam configs available at our community guide in rentry.
Guides by G52 Community
http://rentry.co/g52g_m or http://rentry.org/g52g_m
HemanthJabalpuri said:
I tried phhusson's Android 13 AOSP GSI and it worked fine. We don't need TWRP to flash any GSI.
Instructions to flash GSI in our device are available at https://github.com/phhusson/treble_experimentations/wiki/Moto-G52
Thanks
HemanthJabalpuri
Click to expand...
Click to collapse
hello i hope you will respond, so i want to know if gsi version is at least stable like stock version on moto g52, i want to switch on gsi and i want to use the phone as daily driver and if its worth it.
IgorFTW said:
hello i hope you will respond, so i want to know if gsi version is at least stable like stock version on moto g52, i want to switch on gsi and i want to use the phone as daily driver and if its worth it.
Click to expand...
Click to collapse
Hello, I am a Stock ROM user. Currently using rooted S1SRS32.38-132-3(Nov SPL) (just for Call Recording, nothing else).
I tested only few things in GSI. Like calling, fingerprint, internet connection etc., that too for 1 or 2 days only. I don't play games or use apps that has heavy impact on RAM usage and performance.
So, I can't tell you if you can use a GSI for daily usage purpose. My purpose of testing that GSI is just to tell other Moto G52 users that we can able to "use" custom stuff in the form of GSI.
Thanks
HemanthJabalpuri
HemanthJabalpuri said:
Hello, I am a Stock ROM user. Currently using rooted S1SRS32.38-132-3(Nov SPL) (just for Call Recording, nothing else).
I tested only few things in GSI. Like calling, fingerprint, internet connection etc., that too for 1 or 2 days only. I don't play games or use apps that has heavy impact on RAM usage and performance.
So, I can't tell you if you can use a GSI for daily usage purpose. My purpose of testing that GSI is just to tell other Moto G52 users that we can able to "use" custom stuff in the form of GSI.
Thanks
HemanthJabalpuri
Click to expand...
Click to collapse
but i can install gsi directly from dsu loader and then relock the bootloader? im asking this because i use google pay and its a deal breaker for me.
IgorFTW said:
but i can install gsi directly from dsu loader and then relock the bootloader? im asking this because i use google pay and its a deal breaker for me.
Click to expand...
Click to collapse
You already unlocked bootloader?
Either case, carefully read the warnings of locking the bootloader in 1st post of this thread.
I don't know about DSU, but GPay(in India) is working fine with unlocked bootloader and rooted with Magisk. But many UPI applications(like BHIM and YONO SBI) are not working. So it's better to stay away from these things if your device bootloader is locked.
Thanks
HemanthJabalpuri
HemanthJabalpuri said:
You already unlocked bootloader?
Either case, carefully read the warnings of locking the bootloader in 1st post of this thread.
I don't know about DSU, but GPay(in India) is working fine with unlocked bootloader and rooted with Magisk. But many UPI applications(like BHIM and YONO SBI) are not working. So it's better to stay away from these things if your device bootloader is locked.
Thanks
HemanthJabalpuri
Click to expand...
Click to collapse
no i didnt unlocked the bootloader, im just doing research now, i want a pure google experience without motorola forks . i want to install it without unlocking bootloader, it can be done?
IgorFTW said:
no i didnt unlocked the bootloader, im just doing research now, i want a pure google experience without motorola forks . i want to install it without unlocking bootloader, it can be done?
Click to expand...
Click to collapse
Sorry, I don't about DSU. Without unlocking bootloader, you have to live with Moto Stock ROM.
HemanthJabalpuri said:
Sorry, I don't about DSU. Without unlocking bootloader, you have to live with Moto Stock ROM.
Click to expand...
Click to collapse
but i can relock it back without damages? in europe gpay didnt work with unlocked bootloader
sorry for that repetitive questions...