Database Users

[Q] Edit flash.cfg on recovery.img

Sorry, how to change flash.cfg in recovery.img? Recovery end clk pack is for 150Mb of cache. It's possible to chance this value to 135? I have try more rom, and anyone have different cache size on flash.cfg. Thanks

Marchino73 said:
Sorry, how to change flash.cfg in recovery.img? Recovery end clk pack is for 150Mb of cache. It's possible to chance this value to 135? I have try more rom, and anyone have different cache size on flash.cfg. Thanks
Click to expand...
Click to collapse
hi.
To edit flash.cfg download notepad++(google).
Drag.cfg into it and change what you like or require,then save.
Make sure you drag .cfg and not .text .
Flashed from my fingers to your face

But how to extract flash.cfg from recovery.img (for /fastboot)??? Thanks

Marchino73 said:
But how to extract flash.cfg from recovery.img (for /fastboot)??? Thanks
Click to expand...
Click to collapse
Well you have to have a program that can open disk image files and allow you to view them. But I have yet to find one that will let me view the files contained in the disk image file for CWM that just flashed las night cause I was finally successful in converting to cLK. I have tried Undisker 1.6 and WinImage 8.50 but get an error message everytime I try to open the" cLK_recovery_1..3.3_3.0.1.9.img" file. I will keep looking though

I have tried daemon tools for image disk but recovery.img cannot be opened. How to change cache size in fastboot clk installation for other rom?
Sent from my HD2 using XDA App

[NEED HELP] I Need all image files from pinkscreen (Base B526)

Sir, I Need a Internal Image files(From PINK SCREEN) If you have rom used base B526, please upload it sir, i very need that all files,bcoz with old amss from b526 my X5 can be boot normally, can be shutdown normally. Now i'm using OLD (if it corrects, i see in the thread it's image files from B160, i think that's not compatible with B526 Image) before i do update from external sd card, it was a word "Unpacking blablabla" but after changing the amss and the other, it's looks like this http://www.7ayak.com/up/uploads/13425105111.jpg
so please help me sir, without all of you, my x5 can't be turned on like a normal x5, just reboot, reboot, and reboot every 1-3 minutes

Check my mega drive (signature), you should be able to find them.
Sent from my U8800

Blefish said:
Check my mega drive (signature), you should be able to find them.
Sent from my U8800
Click to expand...
Click to collapse
Ya sir i have download it before. But it didn't work sir, changing the amss and other files still got reboot automatically (in 1-5 mins my X5 will get autoreboot)
I have do partition before about 1GB SD and 1.4GB APP, but i need to install a stock rom, never get completed, always get at 1/2 and failed (no words says 'update blablalba'
When i install a stock partition, never successfull. hmm, after i click emmc unlock boot for my friend l7 , my phone turns like that sir . vie my thread before for details . i have go to huawei centre, but they ask me to pay Rp.2.000.000 for changing the engine inside (WTF! I Have buy it only Rp.1.600.000) :crying:
i see my x5 partition via minitool partition wizard , see that picture sir, are my X5 internal partition was bad or it's okay ?

Blefish said:
Check my mega drive (signature), you should be able to find them.
Sent from my U8800
Click to expand...
Click to collapse
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.

Blefish, i've downloaded B526 Image files from your mega, but i think its not correct amss.mbn for B526, it size same as i downloaded before (23,5mb) before i replacing the amss, my amss original size upper than 23mb and my phone never get reboot automatically

rqmok said:
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.
Click to expand...
Click to collapse
Sir, i think my phone always get auto reboot its not causing by the partition. first time i got the problem in my other thread is my x5 working like normal but my x5 can;t detect a simcard, and now it can (i'm not fixing it, just maybe it has fixed by itself ) . but my stupid i do change the amss.mbn , before i got amss.mbn size is more than 23,5mb sir
So, the problem may causing my phone auto reboot is need to change the correct amss from the base B526
If someone can't upload the amss, i need to unpack update.app based on B526 and find the amss.mbn . but i don't know how to

rqmok said:
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.
Click to expand...
Click to collapse
Under cust/image, there is also cust_data folder. This is not really used in the 2.3 I believe, but it contains some carrier specific bits to Android. Not really necessary though.
VickySullivan said:
Blefish, i've downloaded B526 Image files from your mega, but i think its not correct amss.mbn for B526, it size same as i downloaded before (23,5mb) before i replacing the amss, my amss original size upper than 23mb and my phone never get reboot automatically
Click to expand...
Click to collapse
The B528, B526 all use the B522 amss if I am not mistaken, so there is no difference.

Blefish said:
Under cust/image, there is also cust_data folder. This is not really used in the 2.3 I believe, but it contains some carrier specific bits to Android. Not really necessary though.
The B528, B526 all use the B522 amss if I am not mistaken, so there is no difference.
Click to expand...
Click to collapse
Maybe
*Update
Now i repartitioning the system again with minitool partition wizard
- Ext 3 (system ) : 220mB
- Ext 3 (app) : 700mB+
- U8800-MMC (SD Internal) : 1.9gB
But when i trying to install stock rom, it always fails
I have more fun with my x5 since my x5 goes like a crazy phone
*It's same as before, gets auto reboot.
*I Have changed the Date and Time, but after my phone auto reboot IT'S DATE BACK AGAIN TO JAUNARY 1980 and TIME BACK TO THE 07:00 AGAIN , WHEN I NOT CHANGE IT, THE TIME WILL WORK ONLY ON 07:00 AND UO, Whats wrong with my phone sir>?
Always restart and restart. did u know what is the problem sir ?>

ATIV S ROM Extraction / Analysis

Current progress:
Partitions extracted from SMD (.wp8 & .csc)
Tool to extract SMD
NTFS extracted
Decompiled Diagnosis
Decrypted Diagnosis codes
TODO:
Tool to extract NTFS

Funny how the ATIV S is the most underrated device and most unknown and yet, in the xda-developers community, work for the ATIV S is done the most because it isn't that hard.

Simply because Ativ S looks like business device. Not like kiddy colorful Nokia's or HTC (jesus 8X fail). HTC Mozart that was a gooood phone and I thought that HTC would release something similiar to it. But not, they've released these ****ty two-colored devices for kids. Microsoft is trying to aim WP to business users but how it can be done if they could only buy one phone (Samsung Ativ S)?
Additionally im also interested in this Samsung device and waiting for interop or full unlock. WP7 without file manager is UNUSABLE for me, same WP8. I'll buy WP8 phone when Samsung custom rom will be made. Im PHP and Game Developer and I offer my support anytime when You need it.
And big thanks to developer of Unique File Manager if is he reading this - GOOD JOB!
Regards

I've mounted it in Windows. Chkdsk repaired it into some sort of garbage

extract ?
-W_O_L_F- said:
I've successfully extracted all partitions from Italian ROM. Most of those are RAW, one FAT12, one FAT16 and two NTFS. FAT partitions mount just fine (on Linux), but NTFS not. There are 4096 byte header before NTFS signature. If I cut off those bytes Linux detects NTFS, but says it's broken (no $MFT). No recovery tool can repair it. Are WP8 NTFS partitions special? How can I unpack it?
P.S. Partition start in ROM and in GPT is the same.
P.S.S I can upload Data partition to an file hosting. It's 94 MB large.
Click to expand...
Click to collapse
hi ...
i have the GT-I8750 XXBME1_R_signed.wp8 ROM file
can you please tell me HOW did you extract this file ???
many thanks in advance
M

megasounds said:
hi ...
i have the GT-I8750 XXBME1_R_signed.wp8 ROM file
can you please tell me HOW did you extract this file ???
many thanks in advance
M
Click to expand...
Click to collapse
I have a tool for extracting. I'll post it here on first week of September, cuz I have to fix some minor bugs in it.

is the bootloader unlocked? have you guys figure a way around secureboot?

No

Hmm this thread doesn't seem to do anything with ROM hacking. I would rename it to ATIV S ROM Extraction / Analysis.

snickler said:
Hmm this thread doesn't seem to do anything with ROM hacking. I would rename it to ATIV S ROM Extraction / Analysis.
Click to expand...
Click to collapse
You're right. It's a better name.

Data partition
It's hard to belive but attached archive contains 90+ MB NTFS partition image. May be someone can mount it. The sad thing is that it's huge, about 13 GB. So you need much free space on your HDD.
I can't mount it, case I only have 3 GB free on my tablet.

13 GB? What methods did you use to parse and separate the partitions from the .wp8 file?

snickler said:
13 GB? What methods did you use to parse and separate the partitions from the .wp8 file?
Click to expand...
Click to collapse
File in the archive is what I've extracted from .wp8 file. It's image of the beginning of partition called "Data". "Data" is ~13 GB big but free space isn't included in .wp8.
I analyzed .smd files from wp7 Samsung devices. .csc and .wp8 are smd too. So, a tool I wrote to extract smd can extract csc and wp8. As I said it has some minor bugs.
Usage: smd-tool /u <file> [<folder>]

I think the ROM file is just a some repack form of FFU file.
The NTFS partition is compressed, you can grab full FFU part from the ROM and use imgmount tool to extract.

reker said:
I think the ROM file is just a some repack form of FFU file.
The NTFS partition is compressed, you can grab full FFU part from the ROM and use imgmount tool to extract.
Click to expand...
Click to collapse
AFAIK, FFU is Nokia's format. And this ROM is for Samsung. FAT partitions are not compressed, so are NTFS. Or you talking about internal NTFS compression feature? It's easy to check. If image contains any text data it's not compressed.
UPDATE: I found text info (part of xml) in the image, so it's really uncompressed.

FFU is reference Microsoft format.

OK extracted
ok i extract the files from the wp7 file
now i see a lot of *.bin files
question
how can i mount/uncompress/edit these files ???
many thanks in advance
m

ultrashot said:
FFU is reference Microsoft format.
Click to expand...
Click to collapse
I attached SMD header. Is it similar to FFU?
megasounds said:
ok i extract the files from the wp7 file
now i see a lot of *.bin files
question
how can i mount/uncompress/edit these files ???
many thanks in advance
m
Click to expand...
Click to collapse
With a hexeditor!
Did you read the opening post?
Data.bin contains NTFS. Dig.

question
hi there
yes i extracted the files from the *.wp8 file
my question
can i edit some files and REpack all the files to a new *.wp8 file ?
i saw an option to /p pack all the data but i cannot make this working
is it possible to make an example line how to PACK all the new data into a new *.wp8 file ???
many thanks in advance
M

Still no luck
I've downloaded FFU for Nokia and extracted MainOS NTFS image. It mounts just fine. What's the matter with Samsung's one?
P.S. FFU and SMD are totally different.

How to open stock .img files?

I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?

Teracotta said:
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Click to expand...
Click to collapse
It depends on the image, boot, recovery, system etc and what you want to do with it?

ashyx said:
It depends on the image, boot, recovery, system etc and what you want to do with it?
Click to expand...
Click to collapse
I figured out the issue.
The earlier firmwares list the files as .img, but they are in fact .img.ext4 files. I renamed them, then converted them to proper .imgs and it worked.
Thanks you for giving a response.

How to fix "PMT changed for the ROM, it must be downloaded"

While trying to modify my KW88 Pro watch to run AsteroidOS I took the advice of the program and clicked "Format All + Download" without fully understanding what it does. It deletes all partitions. The install then failed with some random errors but I had a brick. I managed to recover it with KW88 Pro firmware (KW88Pro_V1.5_NHH_B_20190114) I found on discourse.fullandroidwatch.com (don't know how legit it is but at least it works now).
While this guide is how to fix the "PMT changed for the ROM, it must be downloaded" error, the above is relevant. You must find firmware for your watch that has the default partition layout if you did not take a backup before formatting or if you don't know the partition layout. In a nutshell you get the PMT error when the partition layout of the scatter file does not match the partition layout of the device, and the stock firmware + scatter file is needed as a reference point. My error:
https://imgur.com/aFZKfOo
Let's compare the start addresses of those 3 partitions to the stock firmware:
https://imgur.com/rV3XBt2
Boot and Logo partitions are the same, but User Data starts at a different address.
If we compare the contents of both the scatter files we see the same thing:
https://imgur.com/OYw10d3
https://imgur.com/DNQ1Ztw
In a nutshell what you need to do is clone the partition layout (start address variables + offset variable) into the new scatter file, but maintain all other variables of the scatter file. It should also be mentioned that there are other partitions in the scatter file that I had from AsteroidOS that did not match the physical layout of the firmware I used, and even though I was not flashing them I still had to edit the scatter file.
Afterwards using these settings I flashed successfully:
https://imgur.com/TdVRDEV
I also want to note that the End Addresses will not match even with the correct partition layout because different firmware has different sizes on disk, despite the space allocated for the partitions. In theory if you want you could reclaim unused space by tweaking the original scatter file and then the custom scatter file, but it may also impact your future updates if the partition is too small.
Hope I made someone's day easier, best of luck

Can you explain the getting the partition start and offset address part?
Because I think im going to brick my phone really soon if I can't make this auto-generated scatter I got from internet work to flash my phone back to stock rom.
The scatter itself already has some bugs with userdata partition (Too large)

kutiz21 said:
Can you explain the getting the partition start and offset address part?
Because I think im going to brick my phone really soon if I can't make this auto-generated scatter I got from internet work to flash my phone back to stock rom.
The scatter itself already has some bugs with userdata partition (Too large)
Click to expand...
Click to collapse
Sure thing. The scatter file which is for stock firmware vs. the file for new firmware will not allocate the space on disk based on what partitions are actually, physically on it. The new scatter file for custom firmware will be for what the devs had on their device, but not what you actually have on yours (different hardware versions, android releases, w.e.). What you need to do is take the existing partitions of your device, the start addresses for them, add the size of that partition to get the end address and using that information supply that data to the new scatter file. You COULD in theory also change the partition sizes but that is more prone to error so I did not recommend that. So what I did would visually look like this, the | are partition start / end markers
Original scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxx|
vs new scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxx|
vs the patched scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx....................||xxxxxxxxxxxxxxxxxxxxxxx....................................................||xxxxxxxxxx........|
Tl;Dr An offset is basically a way of saying address + data/space (until next segment at next address).

Intersting
printf() said:
Sure thing. The scatter file which is for stock firmware vs. the file for new firmware will not allocate the space on disk based on what partitions are actually, physically on it. The new scatter file for custom firmware will be for what the devs had on their device, but not what you actually have on yours (different hardware versions, android releases, w.e.). What you need to do is take the existing partitions of your device, the start addresses for them, add the size of that partition to get the end address and using that information supply that data to the new scatter file. You COULD in theory also change the partition sizes but that is more prone to error so I did not recommend that. So what I did would visually look like this, the | are partition start / end markers
Original scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxx|
vs new scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxx|
vs the patched scatter file:
|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx....................||xxxxxxxxxxxxxxxxxxxxxxx....................................................||xxxxxxxxxx........|
Tl;Dr An offset is basically a way of saying address + data/space (until next segment at next address).
Click to expand...
Click to collapse
I used Smartphone flash tool version 3 and 5 and I have managed to use my own image to flash numerous phones, encrypted with a key or with no keys (Auth file).
Usually, I would use Google's method of flashing back rom that is using a zip file contains bunch of flashable system images and let fastboot app itself flash it.
I dumped my images using dd tool and img2simg (Full blown raw ext4 file, not sparsed.)
Because fastboot likes sparse images rather than raw ones and flashable sparse images can be easily flashed with SP tool normally (It can make phones bootable but will more likely making phone unbootable most of the time)
I do aware that I need to adjust the address thing. But normally, using the start address based on the scatter. SP app can automatically calculates how large the image and it can prevents you from flashing because it is too large.
But this particular phone won't flash even if it is the stock rom. Which dumped and got its scatter file generated by some sketchy "miracle box".
My best guess is that the scatter file was tied to specific emmc chip and it is not for my phone's emmc so there might be some difference there.
Because when I use the REAL flash scatter file from actual OEM (In this case, Nokia 1, European Variant). It can make my APAC counterpart can be flashed normally, even with my custom sparsed or raw image (These 2 variants were kinda different, technically.)
I would like to point out that newer SP flash tool app tends to hate to co-operate with scatter scripts so that could be a reason (I used older build of version 5 and it only gets the userdata bug, but it does lags the app when the bug "PMT changed for the ROM, it must be downloaded" show up. Because it was a bug and it hadn't fixed in that build, which is fixed in the latest build of SP app when I attempt to flash)
And flashing extracted "stock" rom from flash tool and flash it back over fastboot tool tends to break system OTA and make my phone on bootloop (I highly doubted it was the raw image thing, because of the free space it can allocated. I flashed it raw back then I think because i don't know what happened yet, keep in mind that stock rom images shipped for SP flash tool were most likely in raw state, not compressed like sparse images)
And SP flash tool also hates raw dd images too (too big?????)
So like. What do I need to fix the script? What program that can calculate the exact offset for it? I still be able to flash the stock rom with fastboot fine. But for "unforeseen consequences" that makes it unbootable, I still need it.
Say the scatter is not reliable or doesn't exist. How do I use the readback function and then use some aged apps like MTK droid tool to generate actual offsets and possibly generates scatter for me (Most likely will not work because my phone's Android is too new for it). I used to work with Android 4.2.2 so it's really easy back then.

kutiz21 said:
So like. What do I need to fix the script? What program that can calculate the exact offset for it? I still be able to flash the stock rom with fastboot fine. But for "unforeseen consequences" that makes it unbootable, I still need it.
Say the scatter is not reliable or doesn't exist. How do I use the readback function and then use some aged apps like MTK droid tool to generate actual offsets and possibly generates scatter for me (Most likely will not work because my phone's Android is too new for it). I used to work with Android 4.2.2 so it's really easy back then.
Click to expand...
Click to collapse
I'm not sure how to get the data when no original scatter file exists, I was fortunate enough to find a reference for my stock OS. The other scatter file was for AsteroidOS. I think the easiest way to explain what I did would be to share the scatter files. Effectively start address + partition size should not be larger than the start address of the next partition.
Stock scatter file:
https://pastebin.com/tfFDCPfT
Original AsteroidOS scatter file:
https://pastebin.com/0z7DtL9u
Patched AsteroidOS scatter file:
https://pastebin.com/iiYZTzBt
Take note that in my original post screenshots, AstreroidOS was only flashing 3 partitions (corresponding to the is_download: true/false field of the scatter file). That told me that those were the partitions / boundaries that need to match, the other partitions were irrelevant (for the purpose of flashing anyway). AsteroidOS itself is contained inside the userdata partition, effectively leaving other ~20 partitions as "lower layers" or unused.

printf() said:
I'm not sure how to get the data when no original scatter file exists, I was fortunate enough to find a reference for my stock OS. The other scatter file was for AsteroidOS. I think the easiest way to explain what I did would be to share the scatter files. Effectively start address + partition size should not be larger than the start address of the next partition.
Stock scatter file:
https://pastebin.com/tfFDCPfT
Original AsteroidOS scatter file:
https://pastebin.com/0z7DtL9u
Patched AsteroidOS scatter file:
https://pastebin.com/iiYZTzBt
Take note that in my original post screenshots, AstreroidOS was only flashing 3 partitions (corresponding to the is_download: true/false field of the scatter file). That told me that those were the partitions / boundaries that need to match, the other partitions were irrelevant (for the purpose of flashing anyway). AsteroidOS itself is contained inside the userdata partition, effectively leaving other ~20 partitions as "lower layers" or unused.
Click to expand...
Click to collapse
So my insights were true. It does automatically calculates the free space of a partition to whether allow you to flash or not. But I tried fiddling with it and it doesn't work. I might try to individually comment out those partitions as unflashable and try it out.
One more thing is that I used to had this error. But it will be gone when I explicitly referencing SP flash tool the preloader partition image (flashing it or not doesn't matter) alongside with all of my custom images but they must be fully loaded in the app.
You will not be able to flash if it can't fully loaded all partitions that has the property "is_download: true". Maybe that should allow me to do the flash.
Any more thoughts on " boundary_check and is_reserved"? Because I used to poke with these and managed to flash my other phone successfully.
I don't have the phone to test right now but more food for thought I guess.
Cheers!

kutiz21 said:
Any more thoughts on " boundary_check and is_reserved"? Because I used to poke with these and managed to flash my other phone successfully.
I don't have the phone to test right now but more food for thought I guess.
Cheers!
Click to expand...
Click to collapse
Not sure what is_reserved does, but boundary_check probably validates the scatter file vs. the layout on the disk. If you don't do the check though you are risking overwriting a partition which might be needed for the lower layer functionality - keystore, firmware, etc.