Develop Bugs

[Q] newer smg files?

I'm now running cm7 rc0 but I've also tried the leaked 2.3.3 versions before which I really liked. Now with the latest 2.3.4 leak there is no downgrade ability after flashing the full sbf. To be able to downgrade you need to flash the fixed sbf and as far as I understand this way you don't get the version 5 smg files of cg31 and cg39.
My questions are; what do these two files do and does it matter what version of smg files this leak is running on (would the full sbf run better than the fixed sbf because of the newer smg files?)

I don't know what the two files do exactly, maybe it is better to use the new file, but the leaked version is too fresh and maybe bugfull. So I think it is not the time to flash the full sbf. Now the main offical version is 2.2.
Sorry for my English.

You can find information about cg31 and cg39 on following thread:
http://forum.xda-developers.com/showthread.php?t=945035

Thanks kapil,
After reading it and googleïng (googeling? ) a bit I found this on the files:
Cg31 is cdt.
"The CDT table (which is located within CG31) determines which NAND parts have to be checked for signatures."
So basically is a list for checking if the sbf is complete and correct?
Cg39 is system.img
"It's the Android file system, which means all the support files that Android needs, the applications, but also the framework, the Dalvik VM, initialization scripts and so on.
Another part of the file system would be the userdata.img which is mostly empty when you compile the framework.
It is not the OS, that would be either a plain zImage or boot.img (and recovery.img for to boot in recovery mode)."
This system.img seems kinda important to me? Does the upgrade to version 5 system.img means a different framework and so on? If so, that means full sbf would run better?

[TOOL] imgRePackerRK (RockChip's firmware images unpacker/packer)

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
Version 1.06 Windows & Linux
Supported firmware images (known):
- RK28xx (ChipID=0x00000021);
- RK29xx (ChipID=0x00000050);
- RK30xx (ChipID=0x00000060);
- RK31xx (ChipID=0x00000070);
- RK32xx (ChipID=0x00000080);
- RK33xx (ChipID=0x00000041).
Supported second layer file formats:
- Android boot image;
- RockChip bootloader image;
- gzip/cpio archive file;
- cpio_ascii_new archive file.
- Rockchip resources image;
- Rockchip uboot image file.
Old versions:
View attachment imgRePackerRK_093.zip (7085)
View attachment imgRePackerRK_094.zip (2256)
View attachment imgRePackerRK_095.zip (2539)
View attachment imgRePackerRK_100.zip (2015)
View attachment imgRePackerRK_101.zip (1612)
View attachment imgRePackerRK_102.zip (4051)
View attachment imgRePackerRK_103.zip (2514)
View attachment imgRePackerRK_104.zip (21002)
View attachment imgRePackerRK_105.zip (32858)

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (0.94 Windows & Linux) ready
+ /2nd key added
+ Android boot image support added

imgRePackerRK working very well
Hi,
Thank you for this wonderful piece of software.
I tested it on windows 7 64 with an official image for 97RQ tablet (found on slatedroid)
So this is RK3188 tablet.
I used "imgRePackerRK tablet.img",
then with th system.img in the dump/Image folder, I was able to mount in ubuntu and modify build.prop and modify some apk as well.
Then, i made "imgRePackerRK tablet.img.dump",
and the image was built correctly.
I flashed the img using RKBatchTool V1.6 and....
Works perfectly !
So thank you very much for this tool RedScorpioXDA.
Cheers,
sam

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (0.95 Windows & Linux) ready
+ RockChip bootloader images support added

RedScorpioXDA said:
imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (0.95 Windows & Linux) ready
+ RockChip bootloader images support added
Click to expand...
Click to collapse
Hey, I confirm your tool opens bootloader images for Rockchip images. It works both ways (packing & repacking)
Do you plan to be able to open images that are done with "dd" command ?
e.g. when rooted in android terminal, sending the command:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk.img
Thanks !
Sam

powerpsy said:
Do you plan to be able to open images that are done with "dd" command ?
e.g. when rooted in android terminal, sending the command:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk.img
Click to expand...
Click to collapse
Please provide an example of such image

RedScorpioXDA said:
Please provide an example of such image
Click to expand...
Click to collapse
To get such image, please follow the link here:
http://forum.xda-developers.com/showthread.php?p=31141300
The image seems to be a FAT32-LBA
If I do not specify count / skip parameters, I get an image of 4Go (I will not put here).
Instead I tried quickly to make an image of 1024*4ko (4Mo)
Is it enough or do you ned more ?
++

Hello,
when unpacking a rom for RK3188 tablet, i noticed the backup image is not extracted:
example of the image taken is a VISTURE 10.06.2013 full image (found in pan.baidu.com)
It says: backup (RESERVED) skipped
any explanation to do job ?
Thanks
Code:
imgRePackerRK (version 0.95 windows)
Rockchip firmware batch image unpacker/packer
(c) RedScorpio, Moscow, 2013
[email protected]
==========================[ START ]==========================
--- Firmware unpacking ---
"RKFW" image file detected
Image properties:
Type RockChip batch image (RKFWf)
Version 4.1.1
Date 2013.06.11
Time 15:09:33
ChipID 0x00000070
Code(?) 0x01060000
-- boot.img processing --
-- update.img processing --
Image properties:
Type RockChip update image (RKAF)
Id "007"
Model "V97 HD"
Manufacturer "RK30SDK"
Version 4.1.1
- Files extracting -
Image files count = 10
package-file (package-file) extracted (format: unknown)
bootloader (RK3188Loader(L)_V1.04.bin) extracted (format: RockChip bootloader image)
parameter (parameter) extracted (format: RockChip PARM signed file)
misc (Image/misc.img) extracted (format: unknown)
boot (Image/boot.img) extracted (format: Android boot image)
recovery (Image/recovery.img) extracted (format: Android boot image)
system (Image/system.img) extracted (format: ext3/ext4 image)
backup (RESERVED) skipped
update-script (update-script) extracted (format: unknown)
recover-script (recover-script) extracted (format: unknown)
- rkCRC summ of update.img checking -
Stored rkCRC = 0x70fd48ef
Calculated rkCRC = 0x70fd48ef
- md5 summ checking -
MD5 summ (Z:\xpad\rom\20130610 VISTURE V97 HD FW.img.dump\_img.files\image.md5) saved
Stored MD5 = "b2ff6c1da264fc8a379ad8e79d7adb3d"
Calculated MD5 = "b2ff6c1da264fc8a379ad8e79d7adb3d"
- image.cfg creating -
image.cfg created
==========================[ STOP ]==========================

powerpsy said:
To get such image, please follow the link here:
http://forum.xda-developers.com/showthread.php?p=31141300
Click to expand...
Click to collapse
Unfortunately I have not found images in this discussion. Can you provide a direct link?
powerpsy said:
backup (RESERVED) skipped
Click to expand...
Click to collapse
This means the file is absent in firmware, the partition name is reserved

Unfortunately, I still can't post links due to posts <10.
Firmwares images for RK3188 can be found on slatedroid on N90FHDRK topics.
Hope I can put links in next posts !
And thanks for the explanation. This means there is no recovery partition... But what happends when flashing an image without recovery partition ? the existing is not replaced or it is erased ?
RedScorpioXDA said:
Unfortunately I have not found images in this discussion. Can you provide a direct link?
This means the file is absent in firmware, the partition name is reserved
Click to expand...
Click to collapse

powerpsy said:
And thanks for the explanation. This means there is no recovery partition... But what happends when flashing an image without recovery partition ? the existing is not replaced or it is erased ?
Click to expand...
Click to collapse
This is not so. In your log
powerpsy said:
recovery (Image/recovery.img) extracted (format: Android boot image)
Click to expand...
Click to collapse

Thats cool - molodets bratushka

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (1.00 Windows & Linux) ready
+ gzip/cpio archive file support added
+ cpio_ascii_new archive file support added

Simply works. Thanks RedScorpioXDA!
Perhaps a "root" function on the next version/release?

daeinnor said:
Perhaps a "root" function on the next version/release?
Click to expand...
Click to collapse
What do you mean?

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (1.01 Windows & Linux) ready
+ nongzipped cpio_ascii_new archive file support added (found in Oma's firmware)
+ /skip key added (to support Oma's fw)

imgRePackerRK
RockChip's firmware images (*.img) unpacker/packer
New version (1.02 Windows & Linux) ready
~ "alone" KRNL-signed images unpacking/packing bug fixed

sorry but how to pack system.img again?
first i mounted img file to directory made some modifications but i could not pack the directory again
second i tried to mount img file to a hard drive (dev/sdb1) and did
dd if=/dev/sdb1 of=system.img
but this time system.img file size was long as partition size.. but longer than original system.img
than tried dd with to bs and count parameters but no success.
what is the point to pack system directory to img again?
thanks

nevermind, figured it out.

hey, great tool, thank you so much, but i'm failing to repack the boot.img too (win7 64)
getting error "can't open file "boot.img.dump\package-file", what iam doing wrong?

Can't flash stock firmware, getting many errors

I had flashed Carbon ROM on my Pixel XL, everything was working great. Eventually I was getting tired of the rom, so I decided to go back to the stock rom. I downloaded the stock firmware from google's own site. I tried running the 'flash-all.bat' file and ended up running into some issues. This was a few weeks ago and I don't remember exactly what I did, but I do remember deleting some of the system directories through twrp as per one of the troubleshooting steps I found online.
Now when I try to repair the file systems through twrp I get errors saying that its 'unable to mount storage', and 'failed to mount '/data''.
I also get this error when trying the 'flash-all.bat' file:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 2034413800 bytes
error: update package missing system.img

Nicolas8050 said:
I had flashed Carbon ROM on my Pixel XL, everything was working great. Eventually I was getting tired of the rom, so I decided to go back to the stock rom. I downloaded the stock firmware from google's own site. I tried running the 'flash-all.bat' file and ended up running into some issues. This was a few weeks ago and I don't remember exactly what I did, but I do remember deleting some of the system directories through twrp as per one of the troubleshooting steps I found online.
Now when I try to repair the file systems through twrp I get errors saying that its 'unable to mount storage', and 'failed to mount '/data''.
I also get this error when trying the 'flash-all.bat' file:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 2034413800 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Update your Platform Tools. The latest available is 28.0.1 (September 2018). After you do that - I would re-download the Full system image again - just to be sure you don't have a bad download of the image you are trying to flash. Then, try to flash the full system image again. Good luck!

sb1893 said:
Update your Platform Tools. The latest available is 28.0.1 (September 2018). After you do that - I would re-download the Full system image again - just to be sure you don't have a bad download of the image you are trying to flash. Then, try to flash the full system image again. Good luck!
Click to expand...
Click to collapse
I have the latest platform tools, I downloaded the image again and still the same issues.

sideload it dude!

*Solved* Android 9 update for other Countries.

Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.

Double that. I havent flashed pie too, requesting a little guide how to do it properly to have full stock firmware.

I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely

52.fsc
juandiazmora said:
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
Click to expand...
Click to collapse
Hi, I need help on the flashscript thingie.
Don't have a clue where to get it from.
Thanks in advance.

I'm with Customized CE1 in my H8314 and I'm still in Oreo. It would be possible do this steps with my same firmware without doing wipe? Only deleting the country restricion.
Regards

Why can't we just flash using the downloaded and unpacked firmware from Xperiafirm? Why this need to exclude some specific .ta files and disable final verification checks?

Quarzkopf said:
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Click to expand...
Click to collapse
@Quarzkopf I know this thread is a bit old but I ran into similar "Your device is corrupted..." error when trying to flash US customization to my UK Xperia 1 ii. I was wondering how you got resolved this to a clean flash without this error at the end? Wasn't clear from instructions. Much appreciate your help

Flashing a compiled kernel on S20

Hi,
I've downloaded the latest Android 10 image for the S20, which works great on my phone.
I've then extracted the boot.img from the AP tar, and used unpackbootimg & mkbootimg to pack it right back (without changing anything).
I've made sure all the parts were packed (Including the ramdisk), but after flashing the device always boot to Download Mode with :
dt table header check fail: FDT_ERR_BADMAGIC
DTB LOAD FAIL
I've seen the same error in:
https://forum.xda-developers.com/t/question-building-a-custom-kernel-for-g980f-exynos.4122853/
Where he claims to have solved it by supplying the ramdisk parameter, but I've already did.
Any idea how to solve this?
Thanks!