Database Info

How to dump HTC Kaiser ROM

To dump Kaiser's ROM use itsutils pdocread.exe from itsme:
LIST NAND PARTITIONS
Code:
$ ./pdocread.exe -l
210.38M (0xd260000) FLASHDR
| 3.12M ([COLOR="DarkRed"][B]0x31f000[/B][/COLOR]) Part00
| 3.50M ([COLOR="DarkOrange"][B]0x380000[/B][/COLOR]) Part01
| 69.38M ([COLOR="Olive"][B]0x4560000[/B][/COLOR]) Part02
| 134.38M ([COLOR="Teal"][B]0x8660000[/B][/COLOR]) Part03
STRG handles:
handle e7489c1a134.38M (0x8660000)
handle 474960e6 69.38M (0x4560000)
handle c74b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474960e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
DUMP THEM!
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 [COLOR="DarkRed"][B]0x31f000[/B][/COLOR] Part00.raw
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 [COLOR="DarkOrange"][B]0x380000[/B][/COLOR] Part01.raw
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 [COLOR="Olive"][B]0x4560000[/B][/COLOR] Part02.raw
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 [COLOR="Teal"][B]0x8660000[/B][/COLOR] Part03.raw

and then rebuilding?

Hi, what's the best method (Vista) to upload the orginal HTC rom to a phone? What tool do i search for?

pof said:
To dump Kaiser's ROM use itsutils pdocread.exe from itsme:
Click to expand...
Click to collapse
Thanks for the guide to dump... manage to dump the spanish HTC WM6 ROM, and now i have two questions...
First is easy (i think), what is every partition of the dump? i suppose part03 is the imgfs, but can you give us more information about this?
Second one is do you think can be interesting uploading the dumped ROMs to the wiki (like in the hermes wiki)? If "yes" i can upload the spanish one.
Thanks again for your efforts.

i have followed the links but only downloaded pdocread.cpp
Anyone got pdocread.exe direct link

sparky77 said:
i have followed the links but only downloaded pdocread.cpp
Anyone got pdocread.exe direct link
Click to expand...
Click to collapse
You can download latest version here...
http://www.xs4all.nl/~itsme/projects/xda/tools.html

Think i will leave it untill someone does a site like mrvanx
thanks the only thing i could download "pdocread.cpp". no idea were to go fron here, and don't understand the Wiki (i may leave it to the pro's)
http://nah6.com/~itsme/cvs-xdadevtools/itsutils/src/pdocread.cpp

Thanks a lot!!!
But when i run pdocread.exe an error mag:
"Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked."
I restarted my Kaiser, still the same error...
Anyone could help?

ultimate said:
Thanks a lot!!!
But when i run pdocread.exe an error mag:
"Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart activesync
or maybe your device is application-locked."
I restarted my Kaiser, still the same error...
Anyone could help?
Click to expand...
Click to collapse
ok now
HKLM\Security\Policies\Policies
valuename '00001001' was set to dword:2, change it to dword:1

ok now, I have the
3.12M (0x31f000) Part00
4.38M (0x380000) Part01
73.38M (0x4560000) Part02
129.88M (0x8660000) Part03
From my CHT Hong Kong version Kaiser, how can i flash it to my friend's WWE Kaiser?

ultimate said:
ok now, I have the
3.12M (0x31f000) Part00
4.38M (0x380000) Part01
73.38M (0x4560000) Part02
129.88M (0x8660000) Part03
From my CHT Hong Kong version Kaiser, how can i flash it to my friend's WWE Kaiser?
Click to expand...
Click to collapse
I've uploaded my CHT Chinese version ROM here:
http://www.sendspace.com/file/dc9abe

How do you put the .raw parts together to make a flashable image?
I want to upload t-mobile uk kaiser image.

Harsesis said:
How do you put the .raw parts together to make a flashable image?
I want to upload t-mobile uk kaiser image.
Click to expand...
Click to collapse
For now there is no way to repack the dumpeds ROM, we need to wait and make more research, seems we are near to get the way to do.
You need NBH file and HardSPL/KaiserCustomRUU (thanks to Pof) to flash a Kaiser.
Regards.

T-Mobile UK
210.13M (0xd220000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.50M (0x8780000) Part03
Raw files available online here should anyone want them (62MB).
Russ

Is it possible to use pdocwrite to write back the raw files to your own device?

Deathace said:
T-Mobile UK
210.13M (0xd220000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.50M (0x8780000) Part03
Raw files available online here should anyone want them (62MB).
Russ
Click to expand...
Click to collapse
Strange. On my T-Mob UK...
210.00M (0xd200000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.38M (0x8760000) Part03
Notice the slightly smaller Part03.
Same ROM, same dates. Wierd!
ROM: 1.56.110.4
Date: 01/09/07
Radio: 1.27.12.11
Protocol: 22.45.88.07H

Has anyone figured out how to put the rom back together?
I want to flash my device once I get my rom backed up. I've got the customised cab files for t-mobile uk.
can anyone help?

Dumping my t-mobile NL rom right now.
210.38M (0xd260000) FLASHDR
3.13M (0x31f000) Part00
3.50M (0x380000) Part01
67.25M (0x4340000) Part02
136.50M (0x8880000) Part03
If anyone wants the raw files , please let me know.

On my UK T-Mobile Vario III:
210.25M (0xd240000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.63M (0x87a0000) Part03
Which is really odd...
Recap:
Deathace
210.13M (0xd220000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.50M (0x8780000) Part03
vfrvulcan
210.00M (0xd200000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 68.00M (0x4400000) Part02
| 135.38M (0x8760000) Part03
All using T-Mobile Vario IIIs.

jcespi2005 said:
First is easy (i think), what is every partition of the dump? i suppose part03 is the imgfs, but can you give us more information about this?
Click to expand...
Click to collapse
I'd quite like to know this as well - I'm assuming one of the sections is the SPL. It'd be nice to know which, so I can revert back to the factory SPL if needs be.

[Module] Overclock module project

I'm Building Oc module for s5p and s3c cpus But I'm noop at C language.....
/*
* Author: Useby Ported this module from zdzihu's module
* Adapted from doixanh's X8Undervolt module
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License as published by the
* Free Software Foundation; either version 2 of the License, or (at your
* option) any later version.
*
*/
#include
#include
#include
#include
// defines
#define MODULE_NAME "Useby_oc"
#define MODULE_VER"001"
#define OFS_KALLSYMS_LOOKUP_NAME0xc0251e8c// kallsyms_lookup_name
//for future usage
static struct cpufreq_frequency_table freq_table_666_166MHz[] = {
{0, 1000000},
{1, (1000000)/2},
{2, (1000000)/3},
{3, (1000000)/4},
#ifdef SYSCLK_CHANGE
#ifdef USE_DVFS_AL1_LEVEL
{4, (1000000)/4},
{5, (1000000)/8},
{6, CPUFREQ_TABLE_END},
#else /* USE_DVFS_AL1_LEVEL */
{4, (1000000)/8},
{5, CPUFREQ_TABLE_END},
#endif /* USE_DVFS_AL1_LEVEL */
#else /* SYSCLK_CHANGE */
{4, CPUFREQ_TABLE_END},
#endif /* SYSCLK_CHANGE */
};
static struct cpufreq_policy *policy;
static struct cpufreq_frequency_table *freq_table;
// external variables / functions
typedef unsigned long (*kallsyms_lookup_name_type)(const char *name);
static kallsyms_lookup_name_type kallsyms_lookup_name_dx;
// init module
static int __init useby_oc_init(void)
{
printk(KERN_INFO MODULE_NAME ": module " MODULE_VER " loaded.\n");
// our 'GetProcAddress'
kallsyms_lookup_name_dx = (void*) OFS_KALLSYMS_LOOKUP_NAME;
// look for other offsets
freq_table = (void*) kallsyms_lookup_name_dx("s5p6442_freq_table");
policy = cpufreq_cpu_get(smp_processor_id());
freq_table = cpufreq_frequency_get_table(smp_processor_id());
freq_table[0].frequency = 1000000;
policy->cpuinfo.max_freq = 1000000;
policy->max = 1000000;
printk(KERN_INFO MODULE_NAME ": overclocking applied.\n");
return 0;
}
// exit module - will most likely not be called
static void __exit useby_oc_exit(void)
{
printk(KERN_INFO MODULE_NAME ": module unloaded\n");
}
module_init(useby_oc_init);
module_exit(useby_oc_exit);
MODULE_DESCRIPTION("Overclocking module for SG3");
MODULE_LICENSE("GPL");
When I first load Module Cpu master says It's 1000MHZ
But a Bit later It Says 667...again..
So Developers What about solving this quest? I think module is very useful!
1st picture must be 887 freq but as you see the Source i changed the value....

What is the use of this module...because we already have overclock in our kernels.
Can u please explain
Sent from my GT-I5800 using xda premium

Module is something live device driver that enables various source changing things without flashing new kernel and once someone build oc module and it can be ported to other same based cpu using devices easily also many people want to overclock cpus withoud flashing kernel[I heard many people that their phone became unstable after flashing kernel] and most important I'm more interested in module than kernel.....

That's not the right way to overclock s5p6442 processor.
Changing values in the frequencies table won't overclock the processor. It changes the frequency shown by setcpu but not the processor.
For that, you have to write a new value in APLL like in g3mod : https://github.com/dharamg3/G3MOD/blob/master/Kernel/arch/arm/plat-s5p64xx/clock-ext.c#L197

marcellusbe said:
That's not the right way to overclock s5p6442 processor.
Changing values in the frequencies table won't overclock the processor. It changes the frequency shown by setcpu but not the processor.
For that, you have to write a new value in APLL like in g3mod : https://github.com/dharamg3/G3MOD/blob/master/Kernel/arch/arm/plat-s5p64xx/clock-ext.c#L197
Click to expand...
Click to collapse
After your post I've tested and yeah...that moment was just on setcpu.
But I looked at s5p6442_dvfs.c and i realized that If i change s5p_fclk_set_rate Frequency can be changed without changing clock.c but with just a module
I'm noop that C language so I need mant help.....

useby said:
After your post I've tested and yeah...that moment was just on setcpu.
But I looked at s5p6442_dvfs.c and i realized that If i change s5p_fclk_set_rate Frequency can be changed without changing clock.c but with just a module
I'm noop that C language so I need mant help.....
Click to expand...
Click to collapse
Just flash the fugumod kernel 800MHz. It's not overclocked to crazy speeds and its perfectly stable and it saves you all the hassle of having to modify the kernel yourself.

MicroGeek said:
Just flash the fugumod kernel 800MHz. It's not overclocked to crazy speeds and its perfectly stable and it saves you all the hassle of having to modify the kernel yourself.
Click to expand...
Click to collapse
That's very nice method but purpose i'm making module is not only overclocking my phone i want to learn skill of module making and future i'd like to develop many modules.

useby said:
After your post I've tested and yeah...that moment was just on setcpu.
But I looked at s5p6442_dvfs.c and i realized that If i change s5p_fclk_set_rate Frequency can be changed without changing clock.c but with just a module
I'm noop that C language so I need mant help.....
Click to expand...
Click to collapse
I don't think it will work.
Processor is set at 667Mhz at start... Then, only the dividers in the frequencies table are used :
Code:
/* ARMCLK, D0CLK, P0CLK, D1CLK, P1CLK, APLL_RATIO, D0CLK_RATIO, P0CLK_RATIO, D1CLK_RATIO, P1CLK_RATIO */
static const u32 s5p_cpu_clk_tab_666_166MHz[][10] = {
{667*MHZ, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 0, 0, 1, 0, 1},
{(667*MHZ)/2, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 1, 0, 1, 0, 1},
{(667*MHZ)/3, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 2, 0, 1, 0, 1},
{(667*MHZ)/4, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 3, 0, 1, 0, 1},
#ifdef SYSCLK_CHANGE
#ifdef USE_DVFS_AL1_LEVEL
{(667*MHZ)/4, (166*MHZ)/2, (166*MHZ)/2, 166*MHZ/2, (166*MHZ)/2, 3, 1, 0, 1, 0},
#endif /* USE_DVFS_AL1_LEVEL */
{(667*MHZ)/8, (166*MHZ)/2, (166*MHZ)/2, 166*MHZ/2, (166*MHZ)/2, 7, 1, 0, 1, 0},
#endif /* SYSCLK_CHANGE */
};
so, the APLL ratio is at index 5 (from 0) :
667 / ( 0 + 1) = 667 Mhz
667 / ( 1 + 1) = 333 Mhz
667 / ( 2 + 1) = 222 Mhz
667 / ( 3 + 1) = 166 Mhz
667 / ( 7 + 1) = 83 Mhz
So unless you change the initial frequency of the processor, you won't overclock. That's why in fugumod and g3mod, we have a new table with the right APLL value to overclock the processor (https://github.com/dharamg3/G3MOD/blob/master/Kernel/arch/arm/plat-s5p64xx/clock-ext.c#L59) :
Code:
u32 s5p_cpu_pll_tab[][4] = {
// A P L L M P L L E P L L V P L L
{((1 << 31) | (700 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (650 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (600 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (550 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (500 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (450 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (400 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (350 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (600 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (500 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (400 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (300 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (200 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (83 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
};
only the first value is really usefull (for APLL -> overclock arm processor) :
this one as example :
(1 << 31) | (700 << 16) | (3 << 8) | 1) = 1400 Mhz
(1 << 31) | (600 << 16) | (6 << 8) | 1) = 600 Mhz
....
Then the value is written in the S5P_APLL_CON register
Code:
__raw_writel(0xe10, S5P_APLL_LOCK); // lock time
__raw_writel(s5p_cpu_pll_tab[index][0],S5P_APLL_CON); // new value

marcellusbe said:
I don't think it will work.
Processor is set at 667Mhz at start... Then, only the dividers in the frequencies table are used :
Code:
/* ARMCLK, D0CLK, P0CLK, D1CLK, P1CLK, APLL_RATIO, D0CLK_RATIO, P0CLK_RATIO, D1CLK_RATIO, P1CLK_RATIO */
static const u32 s5p_cpu_clk_tab_666_166MHz[][10] = {
{667*MHZ, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 0, 0, 1, 0, 1},
{(667*MHZ)/2, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 1, 0, 1, 0, 1},
{(667*MHZ)/3, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 2, 0, 1, 0, 1},
{(667*MHZ)/4, 166*MHZ, (166*MHZ)/2, 166*MHZ, (166*MHZ)/2, 3, 0, 1, 0, 1},
#ifdef SYSCLK_CHANGE
#ifdef USE_DVFS_AL1_LEVEL
{(667*MHZ)/4, (166*MHZ)/2, (166*MHZ)/2, 166*MHZ/2, (166*MHZ)/2, 3, 1, 0, 1, 0},
#endif /* USE_DVFS_AL1_LEVEL */
{(667*MHZ)/8, (166*MHZ)/2, (166*MHZ)/2, 166*MHZ/2, (166*MHZ)/2, 7, 1, 0, 1, 0},
#endif /* SYSCLK_CHANGE */
};
so, the APLL ratio is at index 5 (from 0) :
667 / ( 0 + 1) = 667 Mhz
667 / ( 1 + 1) = 333 Mhz
667 / ( 2 + 1) = 222 Mhz
667 / ( 3 + 1) = 166 Mhz
667 / ( 7 + 1) = 83 Mhz
So unless you change the initial frequency of the processor, you won't overclock. That's why in fugumod and g3mod, we have a new table with the right APLL value to overclock the processor (https://github.com/dharamg3/G3MOD/blob/master/Kernel/arch/arm/plat-s5p64xx/clock-ext.c#L59) :
Code:
u32 s5p_cpu_pll_tab[][4] = {
// A P L L M P L L E P L L V P L L
{((1 << 31) | (700 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (650 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (600 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (550 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (500 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (450 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (400 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (350 << 16) | (3 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (600 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (500 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (400 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (300 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (200 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
{((1 << 31) | (83 << 16) | (6 << 8) | 1), ((1 << 31) | (333 << 16) | (3 << 8) | 3), ((1 << 31) | (0x82d << 16) | (1 << 8) | 3), ((1 << 31) | (108 << 16) | (3 << 8) | 3)},
};
only the first value is really usefull (for APLL -> overclock arm processor) :
this one as example :
(1 << 31) | (700 << 16) | (3 << 8) | 1) = 1400 Mhz
(1 << 31) | (600 << 16) | (6 << 8) | 1) = 600 Mhz
....
Then the value is written in the S5P_APLL_CON register
Code:
__raw_writel(0xe10, S5P_APLL_LOCK); // lock time
__raw_writel(s5p_cpu_pll_tab[index][0],S5P_APLL_CON); // new value
Click to expand...
Click to collapse
Thanks that's very thankful information but i don't wanna give up I saw tegra cpu and msm cpu source and it's much easier to change pll value.
I saw the
Code:
unsigned long s5p_fclk_get_rate(void)
{
unsigned long apll_con;
unsigned long clk_div0;
unsigned long ret;
apll_con = __raw_readl(S5P_APLL_CON);
clk_div0 = __raw_readl(S5P_CLK_DIV0);
ret = s5p64xx_get_pll(INIT_XTAL, apll_con, S5P64XX_PLL_APLL);
return (ret / GET_DIV(clk_div0, S5P_CLKDIV0_APLL));
}
I understand it's must to change those three values but i just want to give it a try like g3 and fugu did
I just want to try some more because i'm very interested in modules

Freeze after boot to CM - Possibly a ruined filesystem?

So here's the deal - I was running CM10.1's build on my hand-me-down S-OFF Infuse 4g (T-Mobile). It ran wonderfully, and I loved it. CM10.1 stable was then announced and I figured I'd start over and get this flashed for the last time in a long time. At the same time I figured it was time to do some encryption on the device (which I have found to my dismay to not work). So I went ahead and formatted /data as ext4.
That's when it all started.
So I can flash albinoman's lovely CM10.1 on a system with /data formatted as ext2/3/4 and it does so without complaint - upon boot, however, I get maybe 4-5 seconds of time before the whole thing freezes. Note that I always wipe and clean flash when I do all this.
So I'm sad that ext4 is strangely not working, so I go to format /data back to vfat via mkfs.vfat /dev/block/mmcblk0p23. Same thing. Now it just won't boot and stay there. If I just flip through the desktops then I get about 2-5 seconds of time before the freeze. If I hit the 'menu' button it is always an instafreeze.
Here's my fdisk -l /dev/block/mmcblk0:
Code:
~ # fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2415 MB, 2415919104 bytes
1 heads, 16 sectors/track, 294912 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 4094 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4094 294912 2326544 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 4095 4096 16 5a Unknown
/dev/block/mmcblk0p6 4097 4129 256 73 Unknown
/dev/block/mmcblk0p7 4129 6684 20442+ 0 Empty
/dev/block/mmcblk0p8 6684 6716 256 0 Empty
/dev/block/mmcblk0p9 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p10 6844 6876 256 47 Unknown
/dev/block/mmcblk0p11 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p12 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p13 7260 7264 32 0 Empty
/dev/block/mmcblk0p14 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p15 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p16 8161 8192 256 76 Unknown
/dev/block/mmcblk0p17 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p18 13313 14336 8190+ 74 Unknown
/dev/block/mmcblk0p19 14337 16384 16384 0 Empty
/dev/block/mmcblk0p20 16385 18433 16384 48 Unknown
/dev/block/mmcblk0p21 18433 20480 16383 71 Unknown
/dev/block/mmcblk0p22 20481 122880 819199 83 Linux
/dev/block/mmcblk0p23 122881 275807 1223409 83 Linux
/dev/block/mmcblk0p24 275807 291162 122839 83 Linux
/dev/block/mmcblk0p25 291162 291166 32 90 Unknown
/dev/block/mmcblk0p26 291166 291678 4096 4a Unknown
/dev/block/mmcblk0p27 291678 292190 4096 4b Unknown
/dev/block/mmcblk0p28 292190 294750 20480 19 Unknown
/dev/block/mmcblk0p29 294750 294750 4 0 Empty
/dev/block/mmcblk0p30 294750 294782 256 23 Unknown
/dev/block/mmcblk0p31 294783 294784 16 0 Empty
/dev/block/mmcblk0p32 294785 294912 1022+ 76 Unknown
/dev/block/mmcblk0p33 4095 4096 16 5a Unknown
/dev/block/mmcblk0p34 4097 4129 256 73 Unknown
/dev/block/mmcblk0p35 4129 6684 20442+ 0 Empty
/dev/block/mmcblk0p36 6684 6716 256 0 Empty
/dev/block/mmcblk0p37 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p38 6844 6876 256 47 Unknown
/dev/block/mmcblk0p39 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p40 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p41 7260 7264 32 0 Empty
/dev/block/mmcblk0p42 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p43 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p44 8161 8192 256 76 Unknown
/dev/block/mmcblk0p45 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p46 13313 14336 8190+ 74 Unknown
/dev/block/mmcblk0p47 14337 16384 16384 0 Empty
/dev/block/mmcblk0p48 16385 18433 16384 48 Unknown
/dev/block/mmcblk0p49 18433 20480 16383 71 Unknown
/dev/block/mmcblk0p50 20481 122880 819199 83 Linux
/dev/block/mmcblk0p51 122881 275807 1223409 83 Linux
/dev/block/mmcblk0p52 275807 291162 122839 83 Linux
/dev/block/mmcblk0p53 291162 291166 32 90 Unknown
/dev/block/mmcblk0p54 291166 291678 4096 4a Unknown
/dev/block/mmcblk0p55 291678 292190 4096 4b Unknown
/dev/block/mmcblk0p56 292190 294750 20480 19 Unknown
/dev/block/mmcblk0p57 294750 294750 4 0 Empty
/dev/block/mmcblk0p58 294750 294782 256 23 Unknown
/dev/block/mmcblk0p59 294783 294784 16 0 Empty
/dev/block/mmcblk0p60 294785 294912 1022+ 76 Unknown
Partition table entries are not in disk order
Looks bad! But I didn't touch anything other than /dev/block/mmcblk0p23 (/data) and my external sdcard (which I've put back to vfat). Parted won't print anything, whining that I can't have overlapping partitions:
Code:
Error: Can't have overlapping partitions.
So I am thinking that this is my problem. What I must ask is.... what can I do? Find an RUU and flash the original image via fastboot?
Further, just for my information, all of Android uses ext4 except for sdcards and /data. Is this correct?
Thank you to albinoman for a fantastic ROM and thanks to the wonderful souls that spend time to help out.

I will further state that I do not use gapps, and the md5sum matches correctly.
Is there a log I can look through via TWRP's terminal? A sort of /var/log for android? I couldn't find anything of value.
Here's some output form TWRP's recovery log:
Code:
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p22 | ext4 | 819199 | 255372 | 1 | f |
| data | /dev/block/mmcblk0p23 | ext4 | 1223409 | 38972 | 1 | f |
| boot | /dev/block/mmcblk0p20 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p21 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p24 | ext4 | 122839 | 50452 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 7230468 | 56 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 4 | 4 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | vfat | 500000 | 13 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I've had both 4EXT and TWRP reformat all the partitions many, many times. The only thing I have not tried is reflashing the older rom that I was on (I have very slow internet so I haven't downloaded it yet). But I would really think that it would work the same since it's more or less just a few updated bugs from the latest.
I don't quite know what to do - I don't want to hurt the emmc parts and I have no idea what the purpose of the first few partitions are for - And whether or not they are even the cause of my woes. I wish I could quickly get a logcat/dmesg of what the hell's going on when I boot but I'd have to enable ADB and authenticate with this computer first, something that is most definitely not doable in the small window of time before freezing.
I'm at a loss, and rather worried about the consequences of attempting recovery methods in the rather traditional manner of a desktop.

Okay, I've finally fixed this device. I found an RUU, extracted the rom.zip from the .exe (seeing as I don't use Windows), renamed it to whatever name it needs to autoinstall via the bootloader (PG58.zip?), then had a working phone again. I proceeded to re-unlock the bootloader and install the latest CM10.1, and it all works now.
Strangely enough, the default partition layout does include these overlapping sectors. How bizarre.

RMX2076 edl 9008 Qfil flashing problem

Hello,
I bricked my X50 Pro phone, and now I can only use the edl 9008 mode.
Here below is the problem that I have, flashing with qfil. If anybody can read the flashing log, and tell what is wrong with the edl flashing, please let me know, because I couldn`t find the issue yet. Thank you very much in advance.
2020-07-22 15:12:59.424 Start Download
2020-07-22 15:12:59.424 Program Path:\extract\prog_firehose_ddr5_fwupdate.elf
2020-07-22 15:12:59.424 ***** Working Folder:C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
2020-07-22 15:12:59.582 Binary build date: Apr 27 2018 @ 03:04:33
2020-07-22 15:12:59.582 QSAHARASERVER CALLED LIKE THIS: 'D:\bin\QSaharaServer.ex'Current working dir: C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
2020-07-22 15:12:59.582 Sahara mappings:
2020-07-22 15:12:59.582 2: amss.mbn
2020-07-22 15:12:59.582 6: apps.mbn
2020-07-22 15:12:59.582 8: dsp1.mbn
2020-07-22 15:12:59.582 10: dbl.mbn
2020-07-22 15:12:59.582 11: osbl.mbn
2020-07-22 15:12:59.582 12: dsp2.mbn
2020-07-22 15:12:59.582 16: efs1.mbn
2020-07-22 15:12:59.582 17: efs2.mbn
2020-07-22 15:12:59.582 20: efs3.mbn
2020-07-22 15:12:59.582 21: sbl1.mbn
2020-07-22 15:12:59.582 22: sbl2.mbn
2020-07-22 15:12:59.582 23: rpm.mbn
2020-07-22 15:12:59.582 25: tz.mbn
2020-07-22 15:12:59.582 28: dsp3.mbn
2020-07-22 15:12:59.582 29: acdb.mbn
2020-07-22 15:12:59.582 30: wdt.mbn
2020-07-22 15:12:59.582 31: mba.mbn
2020-07-22 15:12:59.597 13: D:\extract\prog_firehose_ddr5_fwupdate.elf
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597 15:12:59: Requested ID 13, file: "D:\extract\prog_firehose_ddr5_fwupdate.elf"
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597 15:12:59: 675312 bytes transferred in 0.125000 seconds (5.1522MBps)
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597 15:12:59: File transferred successfully
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597
2020-07-22 15:12:59.597 15:12:59: Sahara protocol completed
2020-07-22 15:12:59.597 Sending Programmer Finished
2020-07-22 15:12:59.597 Switch To FireHose
2020-07-22 15:12:59.597 Wait for 3 seconds...
2020-07-22 15:13:02.612 Max Payload Size to Target:49152 Bytes
2020-07-22 15:13:02.612 Device Type:ufs
2020-07-22 15:13:02.612 Platform:8x26
2020-07-22 15:13:02.612 Disable Ack Raw Data Every N Packets
2020-07-22 15:13:02.612 Skip Write:False
2020-07-22 15:13:02.612 Always Validate:False
2020-07-22 15:13:02.612 Use Verbose:False
2020-07-22 15:13:02.612 ***** Working Folder:C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718 Base Version: 18.02.16.18.26
2020-07-22 15:13:02.718 Binary build date: Apr 27 2018 @ 03:04:29
2020-07-22 15:13:02.718 Incremental Build version: 18.04.27.03.04.29
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718 15:13:02: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2020-07-22 15:13:02.718 ************************************************
2020-07-22 15:13:02.718 D:\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=D:\extract --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
2020-07-22 15:13:02.718 ************************************************
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718 15:13:02: INFO: Current working dir (cwd): C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\
2020-07-22 15:13:02.718 15:13:02: INFO: Showing network mappings to allow debugging
2020-07-22 15:13:02.718 15:13:02: INFO:
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718
2020-07-22 15:13:02.718 15:13:02: INFO: Trying to store 'rawprogram0.xml' in string table
2020-07-22 15:13:02.718 15:13:02: INFO: Looking for file 'rawprogram0.xml'
2020-07-22 15:13:02.718 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.718 15:13:02: INFO: Reading through sparse file 'cache.img' and pulling out relevant header information...
2020-07-22 15:13:02.718 15:13:02: INFO: File cache.img is a sparse file, being split up into 7 separate XML tags
2020-07-22 15:13:02.718 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.718 15:13:02: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
2020-07-22 15:13:02.718 15:13:02: INFO: File userdata.img is a sparse file, being split up into 16 separate XML tags
2020-07-22 15:13:02.718 15:13:02: INFO: User wants to talk to port '\\.\COM4'
2020-07-22 15:13:02.733 15:13:02: INFO: Took 0.01600000 seconds to open port
2020-07-22 15:13:02.733 15:13:02: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
2020-07-22 15:13:02.733 15:13:02: INFO: If you don't want this, use --dontsorttags
2020-07-22 15:13:02.733
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'persist.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: cache.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'cache.img'
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'super.img'
2020-07-22 15:13:02.733 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.733 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.733 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.733 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.733 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: userdata.img is a sparse image
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'userdata.img'
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'gpt_main0.bin'
2020-07-22 15:13:02.749 15:13:02: INFO: Looking for file 'gpt_backup0.bin'
2020-07-22 15:13:02.749 15:13:02: INFO:
2020-07-22 15:13:02.765
2020-07-22 15:13:02.765 Total to be tansferd with <program> or <read> is 17.91 GB
2020-07-22 15:13:02.765
2020-07-22 15:13:02.765
2020-07-22 15:13:02.765 15:13:02: INFO: Sending <configure>
2020-07-22 15:13:02.765
2020-07-22 15:13:02.765 15:13:02: INFO: TARGET SAID: 'INFO: Binary build date: Dec 4 2019 @ 19:41:10'
2020-07-22 15:13:02.765
2020-07-22 15:13:02.765 15:13:02: INFO: TARGET SAID: 'INFO: Binary build date: Dec 4 2019 @ 19:41:10
2020-07-22 15:13:02.765 '
2020-07-22 15:13:02.765
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: Chip serial num: 2357875496 (0x8c8a5328)'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: Supported Functions (6):'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: nop'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: configure'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: power'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: firmwarewrite'
2020-07-22 15:14:52.764
2020-07-22 15:14:52.764 15:13:02: INFO: TARGET SAID: 'INFO: getstorageinfo'
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780 15:13:02: INFO: TARGET SAID: 'INFO: End of supported functions 6'
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780 15:13:02: INFO: TARGET SAID: 'INFO: Calling handler for configure'
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780 15:13:02: INFO: TARGET SAID: 'INFO: Storage type set to value UFS'
2020-07-22 15:14:52.780 15:13:02: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
2020-07-22 15:14:52.780 15:13:02: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
2020-07-22 15:14:52.780 15:13:02: INFO: In handleProgram('persist.img')
2020-07-22 15:14:52.780 15:13:02: INFO: Looking for file 'persist.img'
2020-07-22 15:14:52.780 15:13:02: INFO: =======================================================
2020-07-22 15:14:52.780 15:13:02: INFO: {<program> FILE: 'D:\extract\persist.img'}
2020-07-22 15:14:52.780 15:13:02: INFO: {<program> (32.00 MB) 8192 sectors needed at location 8 on LUN 0}
2020-07-22 15:14:52.780 15:13:02: INFO: =======================================================
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780 15:13:02: INFO: TARGET SAID: 'ERROR: Failed to run the last command -1'
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780
2020-07-22 15:14:52.780 _____
2020-07-22 15:14:52.780 | ___|
2020-07-22 15:14:52.780 | |__ _ __ _ __ ___ _ __
2020-07-22 15:14:52.780 | __| '__| '__/ _ \| '__|
2020-07-22 15:14:52.780 | |__| | | | | (_) | |
2020-07-22 15:14:52.780 \____/_| |_| \___/|_|
2020-07-22 15:14:52.780
2020-07-22 15:14:52.795
2020-07-22 15:14:52.795 15:14:52: {ERROR: Could not read from '\\.\COM4', Windows API ReadFile failed! Your device is probably *not* on this port
2020-07-22 15:14:52.795
2020-07-22 15:14:52.795 }
2020-07-22 15:14:52.795
2020-07-22 15:14:52.795 Writing log to 'C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
2020-07-22 15:14:52.795
2020-07-22 15:14:52.795
2020-07-22 15:14:52.795 Log is 'C:\Users\Sven\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
2020-07-22 15:14:52.800
2020-07-22 15:14:52.800 Download Fail:FireHose Fail:FHLoader Failrocess fail
2020-07-22 15:14:52.800 Finish Download

nobody ?

amdtip said:
nobody ?
Click to expand...
Click to collapse
Use this tool to restore phone
https://c.realme.com/in/post-details/1271381271037083648

That tool, does not support edl 9008 mode.

https://youtu.be/z90cQ1whiSE
Can I hope this work with your issue.
Sent from my RMX2071 using Tapatalk

Nekhrun01 said:
https://youtu.be/z90cQ1whiSE
Can I hope this work with your issue.
Sent from my RMX2071 using Tapatalk
Click to expand...
Click to collapse
Thank you for the link, but in my case I need to reflash the phone firmware again, via qfil only in edl mode.

I think my partitions are gone.
How can I reflash them ? I get this message when I trie to read the partitions in qfil
WARNING: Couldn't find the file 'fh_gpt_header_0', returning NULL

gsmmafia.com/realme-x50-pro-rmx2076-flash-file/
Contact these guy but it's a paid service.

Can you solve? Where can you find the ofp Indian extract? Or youre extract? I think you need the 2071 ofp file to restore.
Enviado desde mi RMX2063 mediante Tapatalk

hey similar situation here, did it work?

can't flash because the cellphone is locked in the bootloader

[12:03:55 COM10]:info1:Binary build date: May 9 2017 @ 03:56:22
[12:03:55 COM10]:info1:QSAHARASERVER CALLED LIKE THIS: 'QSaharaServer.ex'Current working dir: D:\MiFlash20200314\MiFlash20200314
[12:03:55 COM10]:info1:Sahara mappings:
[12:03:55 COM10]:info1:2: amss.mbn
[12:03:55 COM10]:info1:6: apps.mbn
[12:03:55 COM10]:info1:8: dsp1.mbn
[12:03:55 COM10]:info1:10: dbl.mbn
[12:03:55 COM10]:info1:11: osbl.mbn
[12:03:55 COM10]:info1:12: dsp2.mbn
[12:03:55 COM10]:info1:16: efs1.mbn
[12:03:55 COM10]:info1:17: efs2.mbn
[12:03:55 COM10]:info1:20: efs3.mbn
[12:03:55 COM10]:info1:21: sbl1.mbn
[12:03:55 COM10]:info1:22: sbl2.mbn
[12:03:55 COM10]:info1:23: rpm.mbn
[12:03:55 COM10]:info1:25: tz.mbn
[12:03:55 COM10]:info1:28: dsp3.mbn
[12:03:55 COM10]:info1:29: acdb.mbn
[12:03:55 COM10]:info1:30: wdt.mbn
[12:03:55 COM10]:info1:31: mba.mbn
[12:03:55 COM10]:info1:13: C:\jasmine_global_images_V11.0.12.0.QDIMIXM_10.0\images\prog_emmc_firehose_Sdm660_ddr.elf
[12:03:55 COM10]:info1:12:03:55: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[12:03:55 COM10]:info1:12:03:55: ERROR: function: sahara_main:924 Sahara protocol error
[12:03:55 COM10]:info1:12:03:55: ERROR: function: main:303 Uploading Image using Sahara protocol failed
[12:03:55 COM10]:flashSuccess False
[12:03:55 COM10]:isFactory False CheckCPUID False
[12:03:55 COM10]:before:flashSuccess is False set IsUpdate:True set IsDone True
[12:03:55 COM10]:after:flashSuccess is False set IsUpdate:false set IsDone true
[12:03:56 COM10]:info1:Base Version: 17.04.27.14.27
[12:03:56 COM10]:info1:Binary build date: May 9 2017 @ 03:56:18
[12:03:56 COM10]:info1:Incremental Build version: 17.05. 9.03.56.18
[12:03:56 COM10]:info1:12:03:55: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
[12:03:56 COM10]:info1:************************************************
[12:03:56 COM10]:info1:fh_loader.exe --port=\\.\devicename --sendxml=rawprogram0.xml --search_path=C:\jasmine_global_images_V11.0.12.0.QDIMIXM_10.0\images --noprompt --showpercentagecomplete --memoryname=emmc --verbose --convertprogram2read
[12:03:56 COM10]:info1:************************************************
[12:03:56 COM10]:info1:12:03:55: INFO: Current working dir (cwd): D:\MiFlash20200314\MiFlash20200314\
[12:03:56 COM10]:info1:12:03:55: INFO: Showing network mappings to allow debugging
[12:03:56 COM10]:info1:12:03:55: INFO:
[12:03:56 COM10]:info1:12:03:55: INFO: Trying to store 'rawprogram0.xml' in string table
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'rawprogram0.xml'
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'system.img'
[12:03:56 COM10]:info1:12:03:55: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
[12:03:56 COM10]:info1:12:03:55: INFO: File system.img is a sparse file, being split up into 28 separate XML tags
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'system.img'
[12:03:56 COM10]:info1:12:03:55: INFO: Reading through sparse file 'system.img' and pulling out relevant header information...
[12:03:56 COM10]:info1:12:03:55: INFO: File system.img is a sparse file, being split up into 28 separate XML tags
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'vendor.img'
[12:03:56 COM10]:info1:12:03:55: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
[12:03:56 COM10]:info1:12:03:55: INFO: File vendor.img is a sparse file, being split up into 14 separate XML tags
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'vendor.img'
[12:03:56 COM10]:info1:12:03:55: INFO: Reading through sparse file 'vendor.img' and pulling out relevant header information...
[12:03:56 COM10]:info1:12:03:55: INFO: File vendor.img is a sparse file, being split up into 14 separate XML tags
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'userdata.img'
[12:03:56 COM10]:info1:12:03:55: INFO: Reading through sparse file 'userdata.img' and pulling out relevant header information...
[12:03:56 COM10]:info1:12:03:55: INFO: File userdata.img is a sparse file, being split up into 13 separate XML tags
[12:03:56 COM10]:info1:12:03:55: INFO: User wants to talk to port '\\.\devicename'
[12:03:56 COM10]:info1:12:03:55: INFO: Took 0.00000000 seconds to open port
[12:03:56 COM10]:info1:12:03:55: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
[12:03:56 COM10]:info1:12:03:55: INFO: If you don't want this, use --dontsorttags
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'storsec.mbn'
[12:03:56 COM10]:info1:12:03:55: INFO: Looking for file 'storsec.mbn'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'rpm.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'rpm.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'hyp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'hyp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'pmic.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'pmic.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'cmnlib.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'cmnlib64.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'cmnlib.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'cmnlib64.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'abl.elf'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'abl.elf'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'devcfg.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'devcfg.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'tz.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'tz.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'mdtpsecapp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'mdtpsecapp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'keymaster.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'keymaster.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'bluetooth.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'xbl.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'xbl.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'dsp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'dsp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'bluetooth.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'mdtp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'mdtp.img'
[12:03:57 COM10]:info1:12:03:55: INFO: Looking for file 'persist.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'modem.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'modem.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'boot.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'boot.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:57 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'system.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:58 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'vendor.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:56: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:57: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:57: INFO: Looking for file 'userdata.img'
[12:03:59 COM10]:info1:12:03:57: INFO: Looking for file 'gpt_main0.bin'
[12:03:59 COM10]:info1:12:03:57: INFO: Looking for file 'gpt_backup0.bin'
[12:03:59 COM10]:info1:12:03:57: INFO:
[12:03:59 COM10]:info1:Total to be tansferd with <program> or <read> is 157.82 GB
[12:03:59 COM10]:info1:12:03:57: INFO: Sending <configure>
[12:03:59 COM10]:info1: _____
[12:03:59 COM10]:info1: | ___|
[12:03:59 COM10]:info1: | |__ _ __ _ __ ___ _ __
[12:03:59 COM10]:info1: | __| '__| '__/ _ \| '__|
[12:03:59 COM10]:info1: | |__| | | | | (_) | |
[12:03:59 COM10]:info1: \____/_| |_| \___/|_|
[12:03:59 COM10]:info1:12:03:57: {ERROR: XML not formed correctly. Expected a < character at loc 0}
[12:03:59 COM10]:info1: _____
[12:03:59 COM10]:info1: | ___|
[12:03:59 COM10]:info1: | |__ _ __ _ __ ___ _ __
[12:03:59 COM10]:info1: | __| '__| '__/ _ \| '__|
[12:03:59 COM10]:info1: | |__| | | | | (_) | |
[12:03:59 COM10]:info1: \____/_| |_| \___/|_|
[12:03:59 COM10]:info1:12:03:57: {ERROR: 3. TAG not found or recognized}
[12:03:59 COM10]:info1: _____
[12:03:59 COM10]:info1: | ___|
[12:03:59 COM10]:info1: | |__ _ __ _ __ ___ _ __
[12:03:59 COM10]:info1: | __| '__| '__/ _ \| '__|
[12:03:59 COM10]:info1: | |__| | | | | (_) | |
[12:03:59 COM10]:info1: \____/_| |_| \___/|_|
[12:03:59 COM10]:info1:12:03:57: {ERROR:
[12:03:59 COM10]:info1: There is a chance your target is in SAHARA mode!!
[12:03:59 COM10]:info1: There is a chance your target is in SAHARA mode!!
[12:03:59 COM10]:info1: There is a chance your target is in SAHARA mode!!
[12:03:59 COM10]:info1:This can mean
[12:03:59 COM10]:info1: 1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
[12:03:59 COM10]:info1: 2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
[12:03:59 COM10]:info1:Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
[12:03:59 COM10]:info1:}
[12:03:59 COM10]:info1:Writing log to 'D:\MiFlash20200314\MiFlash20200314\port_trace.txt', might take a minute
[12:03:59 COM10]:info1:Log is 'D:\MiFlash20200314\MiFlash20200314\port_trace.txt'
[12:03:59 COM10]:begin FlashDone
[12:03:59 COM10]:error:12:03:55: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[12:03:59 COM10]rocess exit.
anybody please help me