DOWNLOAD MP3 Gratis [SONGR mp3 Engine]

ASALAMUALAIKUM WR WB

SONGR ver 1.9.47.0 by ANDREA MARTINELLI

      Sebelum kita memulai membuka kembali blog ini, perkenankan saya menyampaikan permohonan maaf yang se-tulus-tulus-nya kepada semua rekan-rekan. Apabila ada guratan saya di blog ini yang tidak sopan atau tidak berkenan saya mohon maaf yang se-tulus-tulus-nya. Dan MOHON MAAF LAHIR DAN BATHIN [MINAL AIDIN WAL FAIDZIN]

       Kali ini kita keluar sebentar dari kebiasaan membahas masalah yang terjadi pada berbagai jenis handphone. Yang kita bahas kali ini adalah bagaimana caranya untuk memutar file musik kesukaan secara online dan gratis serta mendownloadnya juga. Tentu akan lebih mudah ketimbang harus keluar masuk situs-situs musik yang ada di jagat maya.

       Adalah sebuah mesin kecil hasil karya kang ANDREA MARTINELLI yang akan saya perkenalkan kepada anda. Sejatinya mesin ini lebih layak disebut sebagai BROWSER MUSIK. Menawarkan berbagai kemudahan dari antar muka tampilan-nya yang sangat mudah difahami. Apa yang anda cari tinggal ketik saja di search bar lalu klik enter maka munculah semuanya. Sebelum anda mendownload mesin ini silakan anda lihat-lihat dulu. Link unduh akan saya berikan pada bagian akhir posting ini.

Gambar berikut adalah tampilan dari SONGR anda

       Untuk mencari musik MP3 kesukaan anda ketik judul lagu atau grup band yang anda inginkan pada search bar. Atau bisa juga dengan meng-klik Search by lyrics dengan prosedur yang sama.

Pada log bagian atas hasil pencarian anda akan ditampilkan. Klik kanan lagu yang anda inginkan kemudian pilih SEARCH. Kemudian akan ditampilkan seluruh lagu yang sama dari berbagai situs yang terdaftar di search engine mesin ini [sayang kita belum dapat meng-ADD situs musik yang kita inginkan].

       Setelah muncul lagu anda pada log bagian bawah, klik kanan lagu tersebut kemudian pilih PLAY untuk mendengarkan sebelum anda putuskan untuk mendownloadnya. Pilih yang paling baik score dan kualitasnya.

Setelah anda pilih PLAY maka WMP atau media player default anda akan memainkan musik anda.

       Bila apa yang anda putar dan dengarkan telah sesuai selera, maka klik kanan file yang sama kemudian pilih DOWNLOAD.

       Simpan dimana saja file MP3 anda yang akan di download, kemudian save dan berikutnya download manager SONGR akan melakukan download lagu anda.

       Nah kini tiba saatnya buat anda yang menginginkan kemudahan untuk mendownloadnya dari LINK ini. Ada 2 versi file SONGR yang disediakan yakni dalam bentuk installer dan portable. Untuk mendownloadnya klik kanan pilihan anda lalu pilih DOWNLOAD. Sebab anda tidak akan menjumpai tombol DOWNLOAD.

Demikianlah kemudahan yang ditawarkan oleh SONGR versi 1.9.47.0 buatan ANDREA MARTINELLI yang cerdas. Semoga mesin browser musik kecil ini bermanfaat buat anda yang meng-gila-i musik.

SEMOGA BERMANFAAT

AKU CUMA SHARING bukan PLAGIAT

wasalamualaikum wr wb

Arek NGAJUM IsoIso Ae [The Fully Fuckin' Headache Lion]

Heimdall Frontend Version 1.3.2 All OS

Assalamualaikum WR WB

This will be my last post on August, cause i'm gonna have Great Day Of 1 Syawal 1433 H holidays for the next few days. So all jobs will stop to serv people who need to fix their handsets.

Now I'm gonna talk about Heimdall Frontend Tool version 1.3.2. This tool can do fixing troubles on SAMSUNG Tab. Catch it

The LINKs are on the end of the post below

Heimdall (c) 2010-2011 Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/products/heimdall/

DISCLAIMER:

    This software attempts to flash your Galaxy S device. The very nature of

    flashing is dangerous. As with all flashing software, Heimdall has the

    potential to damage (brick) your device if not used carefully. If you're

    concerned, don't use this software. Flashing ROMs onto your device may also

    void your warranty. Benjamin Dobell and Glass Echidna are not responsible

    for the result of your actions.

These instructions were written for Windows Vista / Server 2008 however the

producedure should be essentially the same for all supported versions of

Windows (XP onwards).

Troubleshooting:

    1. If you get an error as follows:

            The program can't start because MSVCP100.dll is missing from your

            computer.

       This means that you haven't installed the Microsoft Visual C++ 2010

       runtimes. The runtimes can be downloaded from Microsoft's website:

            http://www.microsoft.com/download/en/details.aspx?id=5555

Driver Installation Instructions:

    1. Put your Samsung Galaxy S into download mode and plug it in.

    2. Run zadig.exe included in the Drivers subdirectory.

    3. From the menu chose Options -> List All Devices.

    4. From the USB Device list chose "Samsung USB Composite Device".

    5. Press "Install Driver", click "Yes" to the prompt and if you receive

       a message about being unable to verify the publisher of the driver

       click "Install this driver software anyway".

    6. Done

Driver Uninstallation Instructions:

    1. Put your Samsung Galaxy S into download mode by holding Volume Down + Home + Power.

    2. Plug your phone into your PC.

    3. Open up Device Manager on your PC (Control Panel -> System -> Device Manager).

    4. Under "Libusb (WinUSB) devices" right click on "Samsung USB Composite Device" and chose Properties.

    5. Go to the Driver tab and select Update Driver.

    6. Chose to browse your computer for the driver.

    7. Chose to pick from a list of devices drivers on your computer.

    8. Pick the original Samsung Composite driver, press next and then follow the prompts.

    9. Done

Flashing Heimdall Firmware Package with Heimdall Frontend:

    As of Heimdall Frontend 1.3 there are now two main ways to flash a ROM from

    Heimdall Frontend. The simpler and preferred option is to download a

    Heimdall Firmware Package and follow the following steps.

    1. Fully charge your device (use the wall charger as it's faster).

    2. Open the Heimdall Frontend (heimdall-frontend) executable.

    3. From the "Load Package" tab, under the "Heimdall Firmware Package"

       section click the "Browse" button.

    4. Use the dialogue that appears to navigate to, and select, the Heimdall

       firmware package that you wish to flash.

    5. You will see progress bars appear as the package is decompressed and

       extracted.

       When the package has finished being decompressed you should see

       information about the particular firmware package that has been

       selected.

    6. Verify that your device is listed under "Supported Devices". If it's not

       then STOP immediately! DO NOT flash this firmware to your device!

       Instead search for an appropriate firmware package for your device.

       If you believe there is a mistake and your device is actually

       supported please get in contact with the firmware developer (not Glass

       Echidna!) and ask them to rectify the issue. If the developer provided

       a URL you may be able to contact them by pressing the "Homepage" button.

    7. If you've verified your device is supported you may continue to press

       the "Load / Customise" button.

    8. You should now be looking at the "Flash" tab. If not verify that you did

       in fact push the "Load / Customise" button.

       Generally, you won't NEED or WANT to customise a firmware package! In

       which case you can safely move on to step 9.

       Nonetheless, the "Flash" tab provides you with a means to customise the

       firmware package before flashing it to your device. See "Performing a

       Custom Flash with Heimdall Frontend" for more details.

    9. Put your Galaxy S device into download mode and plug it in to your PC.

       Download mode can be accessed several different ways depending on your

       particular device model. If you're unsure how to do this please search

       online for the appropriate method.

   10. Press the "Start" button.

   11. Heimdall Frontend will display the progress and inform you when the

       flash is complete.

       If something went wrong i.e. your device wasn't detected because it

       wasn't in download mode, then the status section will let you know the

       cause of the problem.

Performing a Custom Flash with Heimdall Frontend:

    This is the advanced means of flashing firmware to your device.

    If you're not an advanced user or a developer, in the event that a Heimdall

    Firmware Package doesn't exist for the particular firmware (or files) that

    you wish to flash, then I strongly recommend you get in touch with developer

    of the firmware (or files) and politely ask them to create a Heimdall

    Firmware Package for you. In doing so then you don't have to worry about

    making mistakes due to inexperience.

    If you're looking to customise an existing Heimdall Firmware Package then

    follow steps 1-8 of "Flashing Heimdall Firmware Package with Heimdall

    Frontend" then start from below with step 5.

    1. Fully charge your device (use the wall charger as it's faster).

    2. Download a decrypted Samsung Galaxy S ROM or a Heimdall Firmware Package

       and extract everything to the one directory.

    3. If the ROM is not a Heimdall Firmware Package it may instead be provided

       as multiple archives (nested or otherwise), extract them all to the same

       location.

       NOTE: If you want to use the CSC then extract it last.

    3. Open the Heimdall Frontend (heimdall-frontend) executable.

    4. Select the "Flash" tab. From the "Flash" tab you're able to completely

       customise a flash. 

    5. Before you can chose which partitions you want to flash with particular

       files you MUST first select a PIT file. To do this click the "Browse"

       button in the "PIT" section. This will open a dialogue allowing you to

       navigate to and select a valid PIT (.pit) file.

       If you do not already have a valid PIT file stored on your computer you

       can download your device's PIT file from the "Utilities" tab.

    6. If a valid PIT file has been selected then "Add" button below the

       "Partitions (Files)" list-box will become enabled. Press this button to

       add a partition to your flash.

    7. When you first add a partition you will see the "Partition Name" and

       "Partition ID" be populated with information. Use the "Partition Name"

       drop down to select which partition you wish to flash. "Partition ID"

       will automatically update and is never directly editable.

    8. You must then select a file to flash to the partition that you just

       specified using the "Browse" button under the "File / Partition". You

       will not be able to flash, create a firmware package or add another

       partition until you have selected a file. However, you're still able to

       press the "Remove" button if you've decided not to flash the partition

       you've just specified.

    9. When you've specified a file name then you'll be able to see the updated

       information in the partition list to the right. You can select any

       partition from this list and customise it as you see fit.

       You can also remove a partition from the list by selecting it and

       clicking the "Remove" button. Removing a partition from the list doesn't

       remove it from your device, it simply means it will not be flashed.

   10. Repeat steps 7-9 as often as needed to specify all the partions/files

       that you wish to flash.

   11. Now you can chose whether you would like to repartition your device as

       well as whether you would like to prevent the device rebooting once a

       flash has been completed. These options can be enabled or disabled by

       toggling the "Repartition" and "No Reboot" check-boxes.

       In the general case you will only need to enable repartition if you wish

       to change the PIT file on your device. Keep in mind that repartitioning

       will wipe your device!

       The "No Reboot" option is rarely required. It's mostly in place so you

       can manually boot straight into recovery mode after a flash (rather than

       booting up normally).

   12. If you've added at least one partition to your flash (and selected a

       file for that partition) then the "Start" button will be enabled. Press

       the "Start" button to begin the flashing process.

       You may notice that the "Create Package" tab becomes available at the

       whenever the "Start" button becomes available. From this tab you're able

       to create a reusable, redistributable Heimdall Firmware Package with the

       files and partitions you just selected. See "How to Create a Heimdall

       Firmware Package" for details.

   13. Heimdall Frontend will display the progress and inform you when the

       flash is complete.

       If something went wrong i.e. your device wasn't detected because it

       wasn't in download mode, then the status section will let you know the

       cause of the problem.

Flashing Firmware from Command Line:

    1. Fully charge your phone (use the wall charger as it's faster).

    2. Download a decrypted Samsung Galaxy S ROM or a Heimdall Firmware Package

       and extract everything to the one directory.

    3. If the ROM is not a Heimdall Firmware Package it may instead be provided

       as multiple archives (nested or otherwise), extract them all to the same

       location.

       NOTE: If you want to use the CSC then extract it last. If you're asked

             to overwrite files then do so.

    4. Put your Galaxy S device into download mode and plug it in..

    5. Open command prompt and navigate to the directory where you installed

       heimdall.

       NOTE: Adding Heimdall to your PATH variable will allow you to run

             Heimdall from any directory.

    6. Type the following to list all the functionality Heimdall supports:

            heimdall help

    7. Use the instructions to manually enter a command with all the files you

       want to flash.

       Here is an example that does a full flash and repartition on a GT-I9000:

            heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin

       NOTE: The above command assumes the files specified are installed in the

             same directory as Heimdall.

    8. Heimdall will display the progress as it flashes so that you know things

       are working as they should.

How to Create a Heimdall Firmware Package:

    Firstly, Heimdall's firmware package format is just a regular TAR archive

    compressed with gzip. The only two real requirements are that a valid

    firmware.xml must be included (refer to Appendix A) and you can only

    include files (no directories, links etc.) As such if you'd like there is

    nothing preventing you from creating Heimdall packages manually. Of course

    Heimdall Frontend provides a simple user interface that takes care of all

    the hard work for you.

    There are two ways in which you can create a firmware package. You can

    create a package from scratch, or you can load an existing package, apply

    modifications and then save the package. Creating a package from scratch

    is the preferred approach, by taking this approach you're far less likely

    to run into file name length limitations. These are not Heimdall's own

    limitation but rather a limitation of the TAR archive format.

    Before you can access Heimdall Frontend's firmware creation functionality

    (available from the "Create Package" tab) you must first specify which

    files will be included in your package, as well as a few flashing options

    i.e. Whether or not users should repartition when flashing. This

    information must be filled out from the "Flash" tab in exactly the same

    fashion you would provide information to flash your device (see "Performing

    a Custom Flash with Heimdall Frontend"). As mentioned above, it's not the

    preferred means, but you're able to load an existing package as a starting

    point for this information.

    Once you've specified the files/partitions you wish to include in your

    firmware package the "Create Package" tab will become available. Clicking

    this tab will display additional information that you can include in your

    package. In order to continue you must fill out all sections except for the

    URLs section, which is optional. The following is a break-down of what all

    these options mean.

    - General Firmware Information: -

        Firmware Name - This is the name of your particular firmware. An

            example would be "Cyanogenmod".

        Firmware Version - This is the version identifier for your package. Any

            valid string will be accepted although a the inclusion of decimal

            point version number is preferred i.e. "7.1". If it makes sense

            then feel free to append a text string like "RC1" or "Beta 1" to

            the decimal point version.

        Platform Name - This is the name of the platform (or operating system)

            that your firmware is based on. In most cases this will simply be

            "Android".

        Platform Version - This is the operating system version that your

            firmware is based on. Again decimal point version numbers are

            preferred over text, i.e. "2.3.4" is preferred over "Gingerbread".

    - Developers -

    URLs (Optional):

        Homepage - Here you can enter your personal URL or a URL particularly

            pertaining to the firmware being packaged. The URL must be well

            formed for it to work. An example of a well formed URL is

            "http://www.glassechidna.com.au/products/heimdall/". It is

            important to include "http://" in order to specify the protocol as

            other protocols such as "ftp://" are equally valid although

            unlikely to be used.

        Donate - Here you can enter a URL that will link users to a page to

            make donations for the effort you've put into developing your

            firmware. Once again the URL must be well formed but there is no

            requirement on how your donation page should work. For instance

            both "http://www.glassechidna.com.au/donate/" and

            "http://forum.xda-developers.com/donatetome.php?u=2710388" are

            equally valid.

    Developer Info:

        Name - Here you can enter in the name of individual team members or a

            team name. Click "Add" and the developer will be added to the list

            on the right. If you make a mistake you can select a developer from

            the list and click "Remove". You can list as many developers as you

            like however visual constraints of the "Load Package" tab means

            only a few names will be visible. Where possible you may want to

            opt for team names over listing individual team members.

    - Supported Devices -

    This section allows you to create a list of devices that are supported by

    your particular firmware. Although Heimdall isn't capable of enforcing this

    we strongly recommend you take this section seriously. If filled out

    correctly you could help save a number of accidental bricks!

    Device Info:

        Manufacturer - This is where you can enter the name of the manufacturer

            for a particular device. For now this will most likely be

            "Samsung".

        Name - This is the human readable name for a particular device.

            "Galaxy S", "Galaxy S II", "Droid Charge", "Vibrant" and

            "Galaxy S (Telstra)" are all valid names. There are a lot of

            possible variations here so be as specific as you think is

            necessary.

        Product Code - This is by far the most important bit of device

            information. Device names tend to be region specific and further

            subject to the whims of telecommunication companies and resellers.

            Product Codes (or product IDs) are designated by manufacturers and

            are generally the definitive means of referring to a particular

            device. Examples are "GT-I9000", "GT-I9100" and "SCH-I897". If

            you're unsure of a particular product code then both Google and

            GSMArena are your friends!

    After filling out all the necessary information the "Build" button will be

    enabled. If it's still disabled then you know you're missing some required

    information. In particular you must specify at least one developer and at

    least one supported device. Pressing the "Build" button will bring up a

    save dialogue where you must chose a file name for your particular package.

    Don't worry about specifying the ".tar.gz" extension Heimdall Frontend will

    take care of this automatically.

    Once you've chosen a file name Heimdall Frontend will begin the process of

    building the firmware package. In doing so a valid firmware.xml file will

    be generated from the information entered. All files will be archived in a

    single TAR file then the TAR archive will be compressed via gzip

    compression. Compression will take a little while but you will see progress

    bars so you know the application hasn't hung. When the progress bars

    disappear you're finished making your package.

    Congratulations! You're now ready to redistribute your firmware package

    online or by any means you see fit.

Appendix A - firmware.xml

The following details a part of the Heimdall Firmware Package format. This

is only relevant to developers or advanced users who wish to create Heimdall

Firmware Packages outside of Heimdall Frontend or in some way integrate support

for the format in their own software.

All Heimdall Firmware Packages must contain a file called firmware.xml. This

file stores flash information and meta-data for the package as well as

information about other files contained within the package.

The format is fairly straight-forward so it won't be explained in great detail.

Nonetheless the following is an example of a valid firmware.xml file.

<?xml version="1.0" encoding="UTF-8"?>

<firmware version="1">

<name>Test Firmware</name>

<version>1.1</version>

<platform>

<name>Android</name>

<version>2.3.4</version>

</platform>

<developers>

<name>Benjamin Dobell</name>

<name>Hedonism Bot</name>

</developers>

<url>http://www.glassechidna.com.au/</url>

<donateurl>http://www.glassechidna.com.au/donate/</donateurl>

<devices>

<device>

<manufacturer>Samsung</manufacturer>

<product>GT-I9000</product>

<name>Galaxy S</name>

</device>

<device>

<manufacturer>Samsung</manufacturer>

<product>GT-I9000T</product>

<name>Galaxy S (Telstra)</name>

</device>

<device>

<manufacturer>Samsung</manufacturer>

<product>GT-I9000M</product>

<name>Vibrant</name>

</device>

</devices>

<pit>Nl3276-I9000 s1_odin_20100512.pit</pit>

<repartition>0</repartition>

<noreboot>0</noreboot>

<files>

<file>

<id>0</id>

<filename>gq3276-boot.bin</filename>

</file>

<file>

<id>24</id>

<filename>Uh3276-cache.rfs</filename>

</file>

<file>

<id>22</id>

<filename>em3276-factoryfs.rfs</filename>

</file>

<file>

<id>11</id>

<filename>fl3276-modem.bin</filename>

</file>

<file>

<id>21</id>

<filename>Xd3276-param.lfs</filename>

</file>

<file>

<id>3</id>

<filename>if3276-Sbl.bin</filename>

</file>

<file>

<id>6</id>

<filename>cr3276-zImage</filename>

</file>

</files>

</firmware>

New lines need not be included and the order in which elements are specified

does not need to match that of the above example.

One and only one <firmware> element must be included. The <firmware> element

must also have a version attribute specified. The version must be parsable as

an integer and indicates what version of the Heimdall Firmware Package

specification the package adheres to.

All data is stored as strings, however a <file>'s <id> element must be parsable

as an integer. The <id> value represents the partition ID (according to the

specified PIT file) that the file should be flashed to.

A <firmware>'s <repartition> and <noreboot> elements must also be parsable as

an integer. However, as they represent boolean values, a value of zero ("0")

means false (or disabled) where as a non-zero value (typically "1") means true

(or enabled).

File names are specified relative to the TAR archive in which firmware.xml and

all other files are to be stored. Heimdall Firmware Packages do not support

directories or links, as such file names should only be a name and not a path.

<url> and <donateurl> are the only optional elements, all other elements must

be included.

Appendix B - Installing Heimdall Suite from Source

    1. Ensure that you have both a version of Visual Studio 2010 with C++

       support and Qt Developer Framework 4.7 (or newer) installed on your

       system.

       A free version (Visual C++ 2010 Express) can be downloaded from

       Microsoft's website:

          http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express

       Qt can also be downloaded freely from Nokia's website:

          http://qt.nokia.com/downloads/

    2. Open Heimdall/msvc2010.sln

    3. From the Solutions Configuration drop-down change from "Debug" to

       "Release".

    4. In the Solution Explorer right-click on the heimdall-frontend project

       and chose "Build".

    5. Depending on how you've installed Qt on your system you may need to copy

       "QtCore4.dll, "QtGui4.dll" and "QtXml4.dll" from your Qt bin/

       sub-directory to Heimdall's Win32/Release sub-directory.

    6. Heimdall Frontend can then be run from Win32/Release or command line can

       be used to run Heimdall (command line) from the same directory.

NO COMMENTS FOR THIS TOOL, SO NO NEED ANY COMMENT HERE. ALL YOU DO IS YOUR OWN RISK!!!

DOWNLOAD HERE

LINK 1

LINK 2

FIRMWARES

wasalamualaikum wr wb

SEE YA NEXT

Arek NGAJUM IsoIso Ae [The Fully Fuckin' Headache Lion]

NOKIA N80 RM-92 Flashing

Asalamualaikum WR WB

       Dalam posting kali ini haribagibagi.blogspot.com dan SuryaJayaPhones menyampaikan selamat hari raya Idul Fitri 1 syawal 1433 Hijriah kepada seluruh umat ISLAM di DUNIA dan INDONESIA pada khususnya.

Mohon maaf lahir dan bathin atas segala kesalahan yang sengaja maupun tak disengaja. Bila terdapat tulisan atau posting yang salah saya mohon maaf yang sebesar-besarnya. MINAL AIDIN WAL FA IDZIN.

Let's go to the troubles happen to NOKIA N80 device

Error detected on device:

• Hang on sending message
• To slow to load the features
• To slow to gathering signal

Step by step to resolve these troubles to your device:

1. Open DCTxBB5 of UFSx Tornado with Original HWK v 2.2.03

2. Change settings on SCENARIO to MANUAL, SPEED to NORMAL [i used to do this in all tasks]

3. Tab BB5, on Files and Settings choose RM-92 PRODUCT, fill on all fields for COR, PPM, UAR   [UserARea]

4. Click CHECK, see the log RESULTS/EVENTS

Executive Path: 

C:\Program Files\SarasSoft\UFS\UFS_DCTxBB5

Please Wait ...

UFxBoot V2.2 (c) SarasSoft 2003. Id: 62 CF 1 10

UFS_USB V2.8 (c) SarasSoft 2007. Cracked

HID: C81733584160007B

HWK: A1.04-PRO1

Features: 00000001

Licence : True

LogFile: .\_!_LOG\Cracked_17122033_00_LOG.txt

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0

APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA

APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

APE 2ND Boot OK

APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0

APE VPP   : Internal

APE KSIG1 : 54965DF2BFA6749422ED197DAD70A03485D35846

DUAL LINE : True

APE ALG Boot OK

PASUBTOC  : PA_SL  

Rebooting Mobile

5. Click INFO, if there is nothing goes wrong you can READ PM

MCU SW  : V 05wk33v29.2 17-05-06 RM-92 (c) Nokia. 

APE Core: V 3.0618.0.2 23-05-2006 RM-92 

APE Var : V 3.0618.0. 2-52 23-05- 2006 RM-92 

Product : Nokia N80-1

Prd.Code: 0535584

Bpr.Code: 0524613

Prod.Sn : SGG659719

HW Vers : 6002

APE HW  : 1

APE Adsp: 256

EM VILMA: 14

EM BETTY: 21

RFIC Ver: 17191719

DSP Vers: pb05w32v32

WLAN Id : 00 16 BC 9F D4 72 

IMEI    : 358814-00-084475-5

SL Serv : SIMLOCK SERVER VERSION 62

SL Conf : 244-07-00000000000

SL Prof : 0000000000000000

SL Count: 00 00 

BLK1= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK2= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK3= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK4= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK5= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK6= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

BLK7= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN 

Provider: Nokia Test;Finland

I have Unlocked the device allready on the first try, it's not work

6. PM reading

Reading PM: 0-511

Id: [1]    20 Record(s)

   Record: 0, 114 byte(s), Ok

   Record: 2, 98 byte(s), Ok

   Record: 4, 110 byte(s), Ok

   Record: 6, 98 byte(s), Ok

   Record: 8, 110 byte(s), Ok

   Record: 13, 98 byte(s), Ok

   Record: 16, 98 byte(s), Ok

   Record: 18, 98 byte(s), Ok

   Record: 20, 98 byte(s), Ok

   Record: 22, 16 byte(s), Ok

   Record: 23, 4 byte(s), Ok

   Record: 24, 84 byte(s), Ok

   Record: 25, 4 byte(s), Ok

   Record: 26, 110 byte(s), Ok

   Record: 28, 98 byte(s), Ok

   Record: 29, 6 byte(s), Ok

   Record: 31, 98 byte(s), Ok

   Record: 33, 36 byte(s), Ok

   Record: 34, 80 byte(s), Ok

   Record: 44, 182 byte(s), Ok

Id: [2]    1 Record(s)

   Record: 0, 360 byte(s), Ok

Id: [3]    0 Record(s)

Id: [4]    9 Record(s)

   Record: 0, 1 byte(s), Ok

   Record: 1, 36 byte(s), Ok

   Record: 2, 44 byte(s), Ok

   Record: 3, 10 byte(s), Ok

   Record: 4, 8 byte(s), Ok

   Record: 5, 8 byte(s), Ok

   Record: 6, 8 byte(s), Ok

   Record: 9, 5 byte(s), Ok

   Record: 16, 4 byte(s), Ok

Id: [7]    0 Record(s)

Id: [8]    7 Record(s)

   Record: 0, 12 byte(s), Ok

   Record: 1, 12 byte(s), Ok

   Record: 2, 0 byte(s), Ok

   Record: 3, 0 byte(s), Ok

   Record: 4, 8 byte(s), Ok

   Record: 6, 4 byte(s), Ok

   Record: 7, 8 byte(s), Ok

Id: [11]   125 Record(s)

   Record: 0, 4 byte(s), Ok

   Record: 1, 4 byte(s), Ok

   Record: 2, 4 byte(s), Ok

   Record: 3, 4 byte(s), Ok

   Record: 4, 1 byte(s), Ok

   Record: 5, 6 byte(s), Ok

   Record: 6, 1 byte(s), Ok

   Record: 7, 2 byte(s), Ok

   Record: 8, 2 byte(s), Ok

   Record: 9, 2 byte(s), Ok

   Record: 10, 2 byte(s), Ok

   Record: 11, 2 byte(s), Ok

   Record: 12, 1 byte(s), Ok

   Record: 13, 1 byte(s), Ok

   Record: 14, 1 byte(s), Ok

   Record: 15, 1 byte(s), Ok

   Record: 16, 1 byte(s), Ok

   Record: 17, 1 byte(s), Ok

   Record: 18, 1 byte(s), Ok

   Record: 19, 2 byte(s), Ok

   Record: 20, 2 byte(s), Ok

   Record: 21, 1 byte(s), Ok

   Record: 22, 1 byte(s), Ok

   Record: 23, 4 byte(s), Ok

   Record: 24, 4 byte(s), Ok

   Record: 25, 2 byte(s), Ok

   Record: 26, 2 byte(s), Ok

   Record: 27, 2 byte(s), Ok

   Record: 28, 2 byte(s), Ok

   Record: 29, 1 byte(s), Ok

   Record: 30, 1 byte(s), Ok

   Record: 31, 1 byte(s), Ok

   Record: 32, 1 byte(s), Ok

   Record: 33, 1 byte(s), Ok

   Record: 34, 1 byte(s), Ok

   Record: 35, 1 byte(s), Ok

   Record: 36, 1 byte(s), Ok

   Record: 37, 1 byte(s), Ok

   Record: 38, 2 byte(s), Ok

   Record: 39, 2 byte(s), Ok

   Record: 40, 2 byte(s), Ok

   Record: 41, 2 byte(s), Ok

   Record: 42, 2 byte(s), Ok

   Record: 43, 4 byte(s), Ok

   Record: 44, 4 byte(s), Ok

   Record: 45, 4 byte(s), Ok

   Record: 46, 1 byte(s), Ok

   Record: 47, 16 byte(s), Ok

   Record: 48, 2 byte(s), Ok

   Record: 49, 2 byte(s), Ok

   Record: 50, 20 byte(s), Ok

   Record: 51, 10 byte(s), Ok

   Record: 52, 2 byte(s), Ok

   Record: 53, 20 byte(s), Ok

   Record: 54, 10 byte(s), Ok

   Record: 55, 1 byte(s), Ok

   Record: 56, 1 byte(s), Ok

   Record: 57, 1 byte(s), Ok

   Record: 58, 1 byte(s), Ok

   Record: 59, 1 byte(s), Ok

   Record: 60, 1 byte(s), Ok

   Record: 61, 1 byte(s), Ok

   Record: 62, 1 byte(s), Ok

   Record: 63, 1 byte(s), Ok

   Record: 64, 1 byte(s), Ok

   Record: 65, 1 byte(s), Ok

   Record: 66, 32 byte(s), Ok

   Record: 67, 32 byte(s), Ok

   Record: 68, 2 byte(s), Ok

   Record: 69, 2 byte(s), Ok

   Record: 70, 2 byte(s), Ok

   Record: 71, 2 byte(s), Ok

   Record: 72, 2 byte(s), Ok

   Record: 73, 2 byte(s), Ok

   Record: 74, 2 byte(s), Ok

   Record: 75, 2 byte(s), Ok

   Record: 76, 2 byte(s), Ok

   Record: 77, 2 byte(s), Ok

   Record: 78, 2 byte(s), Ok

   Record: 79, 2 byte(s), Ok

   Record: 80, 2 byte(s), Ok

   Record: 81, 2 byte(s), Ok

   Record: 82, 2 byte(s), Ok

   Record: 83, 2 byte(s), Ok

   Record: 84, 2 byte(s), Ok

   Record: 85, 2 byte(s), Ok

   Record: 86, 2 byte(s), Ok

   Record: 87, 2 byte(s), Ok

   Record: 88, 2 byte(s), Ok

   Record: 89, 2 byte(s), Ok

   Record: 90, 2 byte(s), Ok

   Record: 91, 2 byte(s), Ok

   Record: 92, 2 byte(s), Ok

   Record: 93, 2 byte(s), Ok

   Record: 94, 2 byte(s), Ok

   Record: 95, 2 byte(s), Ok

   Record: 96, 2 byte(s), Ok

   Record: 97, 2 byte(s), Ok

   Record: 98, 2 byte(s), Ok

   Record: 99, 2 byte(s), Ok

   Record: 100, 2 byte(s), Ok

   Record: 101, 2 byte(s), Ok

   Record: 102, 2 byte(s), Ok

   Record: 103, 2 byte(s), Ok

   Record: 104, 2 byte(s), Ok

   Record: 105, 2 byte(s), Ok

   Record: 106, 2 byte(s), Ok

   Record: 107, 2 byte(s), Ok

   Record: 108, 2 byte(s), Ok

   Record: 109, 2 byte(s), Ok

   Record: 110, 2 byte(s), Ok

   Record: 111, 2 byte(s), Ok

   Record: 112, 2 byte(s), Ok

   Record: 113, 4 byte(s), Ok

   Record: 114, 4 byte(s), Ok

   Record: 115, 1 byte(s), Ok

   Record: 116, 4 byte(s), Ok

   Record: 117, 4 byte(s), Ok

   Record: 118, 4 byte(s), Ok

   Record: 119, 4 byte(s), Ok

   Record: 120, 16 byte(s), Ok

   Record: 121, 4 byte(s), Ok

   Record: 122, 2 byte(s), Ok

   Record: 123, 2 byte(s), Ok

   Record: 124, 1506 byte(s), Ok

Id: [12]   1 Record(s)

   Record: 0, 102 byte(s), Ok

Id: [17]   1 Record(s)

   Record: 0, 4 byte(s), Ok

Id: [21]   0 Record(s)

Id: [26]   2 Record(s)

   Record: 0, 16 byte(s), Ok

   Record: 1, 68 byte(s), Ok

Id: [29]   1 Record(s)

   Record: 2, 6 byte(s), Ok

Id: [31]   0 Record(s)

Id: [35]   0 Record(s)

Id: [43]   0 Record(s)

Id: [44]   1 Record(s)

   Record: 0, 1 byte(s), Ok

Id: [46]   0 Record(s)

Id: [50]   3 Record(s)

   Record: 0, 2 byte(s), Ok

   Record: 1, 26 byte(s), Ok

   Record: 2, 26 byte(s), Ok

Id: [54]   2 Record(s)

   Record: 0, 2 byte(s), Ok

   Record: 2, 24 byte(s), Ok

Id: [88]   1 Record(s)

   Record: 0, 36 byte(s), Ok

Id: [92]   1 Record(s)

   Record: 0, 16 byte(s), Ok

Id: [94]   1 Record(s)

   Record: 0, 40 byte(s), Ok

Id: [95]   2 Record(s)

   Record: 0, 1 byte(s), Ok

   Record: 1, 1 byte(s), Ok

Id: [96]   1 Record(s)

   Record: 0, 24 byte(s), Ok

Id: [107]  6 Record(s)

   Record: 0, 21 byte(s), Ok

   Record: 1, 79 byte(s), Ok

   Record: 2, 79 byte(s), Ok

   Record: 3, 70 byte(s), Ok

   Record: 24, 88 byte(s), Ok

   Record: 25, 132 byte(s), Ok

Id: [112]  0 Record(s)

Id: [117]  10 Record(s)

   Record: 0, 4 byte(s), Ok

   Record: 1, 3 byte(s), Ok

   Record: 2, 6 byte(s), Ok

   Record: 3, 1 byte(s), Ok

   Record: 4, 9 byte(s), Ok

   Record: 5, 10 byte(s), Ok

   Record: 6, 8 byte(s), Ok

   Record: 8, 42 byte(s), Ok

   Record: 13, 3 byte(s), Ok

   Record: 14, 3 byte(s), Ok

Id: [118]  1 Record(s)

   Record: 0, 1 byte(s), Ok

Id: [193]  5 Record(s)

   Record: 2, 8 byte(s), Ok

   Record: 3, 32 byte(s), Ok

   Record: 4, 32 byte(s), Ok

   Record: 8, 228 byte(s), Ok

   Record: 9, 64 byte(s), Ok

Id: [208]  0 Record(s)

Id: [212]  0 Record(s)

Id: [239]  6 Record(s)

   Record: 0, 2 byte(s), Ok

   Record: 1, 2205 byte(s), Ok

   Record: 2, 2205 byte(s), Ok

   Record: 3, 2205 byte(s), Ok

   Record: 4, 2205 byte(s), Ok

   Record: 5, 2205 byte(s), Ok

Id: [291]  0 Record(s)

Id: [307]  0 Record(s)

Id: [308]  4 Record(s)

   Record: 0, 1 byte(s), Ok

   Record: 1, 8192 byte(s), Ok

   Record: 3, 1 byte(s), Ok

   Record: 4, 1 byte(s), Ok

Id: [309]  8 Record(s)

   Record: 0, 4 byte(s), Ok

   Record: 1, 2 byte(s), Ok

   Record: 2, 12 byte(s), Ok

   Record: 4, 12 byte(s), Ok

   Record: 5, 12 byte(s), Ok

   Record: 7, 12 byte(s), Ok

   Record: 8, 12 byte(s), Ok

   Record: 17, 12 byte(s), Ok

Id: [313]  1 Record(s)

   Record: 0, 615 byte(s), Ok

Id: [326]  0 Record(s)

Id: [334]  1 Record(s)

   Record: 0, 1 byte(s), Ok

PM Read Done 221 Record(s), Time: 01:22

7. Then when the PM's read OK what is realy happen to the device???

    Just click VERIFY

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

IMAGE : n80_5.0719.0.2-prd_western_c00_cc.fpsx

CERT_BLK_ERROR at: 0x000C0000, 03

DATA_BLK_ERROR at: 0x000C0400, 03

CERT_BLK_ERROR at: 0x000CC000, 03

CERT_BLK_ERROR at: 0x000CE000, 03

DATA_BLK_ERROR at: 0x000CE180, 03

CERT_BLK_ERROR at: 0x000D0000, 03

CERT_BLK_ERROR at: 0xFFFFFFFF, 03

CERT_BLK_ERROR at: 0x000E0000, 03

DATA_BLK_ERROR at: 0x000E0400, 03

DATA_BLK_ERROR at: 0x000E4400, 03

DATA_BLK_ERROR at: 0x000E8400, 03

DATA_BLK_ERROR at: 0x000EC400, 03

DATA_BLK_ERROR at: 0x000F0400, 03

DATA_BLK_ERROR at: 0x000F4400, 03

DATA_BLK_ERROR at: 0x000F8400, 03

DATA_BLK_ERROR at: 0x000FC400, 03

DATA_BLK_ERROR at: 0x00100400, 03

DATA_BLK_ERROR at: 0x00104400, 03

DATA_BLK_ERROR at: 0x00108400, 03

CERT_BLK_ERROR at: 0x001E0000, 03

DATA_BLK_ERROR at: 0x001E0400, 03

DATA_BLK_ERROR at: 0x001E4400, 03

DATA_BLK_ERROR at: 0x001E8400, 03

CERT_BLK_ERROR at: 0x00200000, 03

DATA_BLK_ERROR at: 0x00200400, 03

DATA_BLK_ERROR at: 0x00204400, 03

DATA_BLK_ERROR at: 0x00208400, 03

DATA_BLK_ERROR at: 0x0020C400, 03

DATA_BLK_ERROR at: 0x00210400, 03

DATA_BLK_ERROR at: 0x00214400, 03

DATA_BLK_ERROR at: 0x00218400, 03

DATA_BLK_ERROR at: 0x0021C400, 03

DATA_BLK_ERROR at: 0x00220400, 03

DATA_BLK_ERROR at: 0x00224400, 03

DATA_BLK_ERROR at: 0x00228400, 03

DATA_BLK_ERROR at: 0x0022C400, 03

DATA_BLK_ERROR at: 0x00230400, 03

DATA_BLK_ERROR at: 0x00234400, 03

DATA_BLK_ERROR at: 0x00238400, 03

DATA_BLK_ERROR at: 0x0023C400, 03

DATA_BLK_ERROR at: 0x00240400, 03

DATA_BLK_ERROR at: 0x00244400, 03

DATA_BLK_ERROR at: 0x00248400, 03

DATA_BLK_ERROR at: 0x0024C400, 03

DATA_BLK_ERROR at: 0x00250400, 03

DATA_BLK_ERROR at: 0x00254400, 03

DATA_BLK_ERROR at: 0x00258400, 03

DATA_BLK_ERROR at: 0x0025C400, 03

DATA_BLK_ERROR at: 0x00260400, 03

DATA_BLK_ERROR at: 0x00264400, 03

DATA_BLK_ERROR at: 0x00268400, 03

DATA_BLK_ERROR at: 0x0026C400, 03

DATA_BLK_ERROR at: 0x00270400, 03

DATA_BLK_ERROR at: 0x00274400, 03

DATA_BLK_ERROR at: 0x00278400, 03

DATA_BLK_ERROR at: 0x0027C400, 03

DATA_BLK_ERROR at: 0x00280400, 03

DATA_BLK_ERROR at: 0x00284400, 03

DATA_BLK_ERROR at: 0x00288400, 03

DATA_BLK_ERROR at: 0x0028C400, 03

DATA_BLK_ERROR at: 0x00290400, 03

DATA_BLK_ERROR at: 0x00294400, 03

DATA_BLK_ERROR at: 0x00298400, 03

DATA_BLK_ERROR at: 0x0029C400, 03

DATA_BLK_ERROR at: 0x002A0400, 03

DATA_BLK_ERROR at: 0x002A4400, 03

DATA_BLK_ERROR at: 0x002A8400, 03

DATA_BLK_ERROR at: 0x002AC400, 03

DATA_BLK_ERROR at: 0x002B0400, 03

DATA_BLK_ERROR at: 0x002B4400, 03

DATA_BLK_ERROR at: 0x002B8400, 03

DATA_BLK_ERROR at: 0x002BC400, 03

DATA_BLK_ERROR at: 0x002C0400, 03

DATA_BLK_ERROR at: 0x002C4400, 03

DATA_BLK_ERROR at: 0x002C8400, 03

DATA_BLK_ERROR at: 0x002CC400, 03

DATA_BLK_ERROR at: 0x002D0400, 03

DATA_BLK_ERROR at: 0x002D4400, 03

DATA_BLK_ERROR at: 0x002D8400, 03

DATA_BLK_ERROR at: 0x002DC400, 03

DATA_BLK_ERROR at: 0x002E0400, 03

DATA_BLK_ERROR at: 0x002E4400, 03

DATA_BLK_ERROR at: 0x002E8400, 03

DATA_BLK_ERROR at: 0x002EC400, 03

DATA_BLK_ERROR at: 0x002F0400, 03

DATA_BLK_ERROR at: 0x002F4400, 03

DATA_BLK_ERROR at: 0x002F8400, 03

DATA_BLK_ERROR at: 0x002FC400, 03

DATA_BLK_ERROR at: 0x00300400, 03

DATA_BLK_ERROR at: 0x00304400, 03

DATA_BLK_ERROR at: 0x00308400, 03

DATA_BLK_ERROR at: 0x0030C400, 03

DATA_BLK_ERROR at: 0x00310400, 03

DATA_BLK_ERROR at: 0x00314400, 03

DATA_BLK_ERROR at: 0x00318400, 03

DATA_BLK_ERROR at: 0x0031C400, 03

DATA_BLK_ERROR at: 0x00320400, 03

DATA_BLK_ERROR at: 0x00324400, 03

DATA_BLK_ERROR at: 0x00328400, 03

DATA_BLK_ERROR at: 0x0032C400, 03

DATA_BLK_ERROR at: 0x00330400, 03

DATA_BLK_ERROR at: 0x00334400, 03

CERT_BLK_ERROR at: 0x003E0000, 03

DATA_BLK_ERROR at: 0x003E0400, 03

DATA_BLK_ERROR at: 0x003E4400, 03

DATA_BLK_ERROR at: 0x003E8400, 03

DATA_BLK_ERROR at: 0x003EC400, 03

DATA_BLK_ERROR at: 0x003F0400, 03

DATA_BLK_ERROR at: 0x003F4400, 03

DATA_BLK_ERROR at: 0x003F8400, 03

DATA_BLK_ERROR at: 0x003FC400, 03

DATA_BLK_ERROR at: 0x00400400, 03

DATA_BLK_ERROR at: 0x00404400, 03

DATA_BLK_ERROR at: 0x00408400, 03

DATA_BLK_ERROR at: 0x0040C400, 03

DATA_BLK_ERROR at: 0x00410400, 03

DATA_BLK_ERROR at: 0x00414400, 03

DATA_BLK_ERROR at: 0x00418400, 03

DATA_BLK_ERROR at: 0x0041C400, 03

DATA_BLK_ERROR at: 0x00420400, 03

DATA_BLK_ERROR at: 0x00424400, 03

DATA_BLK_ERROR at: 0x00428400, 03

DATA_BLK_ERROR at: 0x0042C400, 03

DATA_BLK_ERROR at: 0x00430400, 03

DATA_BLK_ERROR at: 0x00434400, 03

DATA_BLK_ERROR at: 0x00438400, 03

DATA_BLK_ERROR at: 0x0043C400, 03

DATA_BLK_ERROR at: 0x00440400, 03

DATA_BLK_ERROR at: 0x00444400, 03

DATA_BLK_ERROR at: 0x00448400, 03

DATA_BLK_ERROR at: 0x0044C400, 03

DATA_BLK_ERROR at: 0x00450400, 03

DATA_BLK_ERROR at: 0x00454400, 03

DATA_BLK_ERROR at: 0x00458400, 03

DATA_BLK_ERROR at: 0x0045C400, 03

DATA_BLK_ERROR at: 0x00460400, 03

DATA_BLK_ERROR at: 0x00464400, 03

DATA_BLK_ERROR at: 0x00468400, 03

DATA_BLK_ERROR at: 0x0046C400, 03

DATA_BLK_ERROR at: 0x00470400, 03

DATA_BLK_ERROR at: 0x00474400, 03

DATA_BLK_ERROR at: 0x00478400, 03

DATA_BLK_ERROR at: 0x0047C400, 03

DATA_BLK_ERROR at: 0x00480400, 03

DATA_BLK_ERROR at: 0x00484400, 03

DATA_BLK_ERROR at: 0x00488400, 03

DATA_BLK_ERROR at: 0x0048C400, 03

DATA_BLK_ERROR at: 0x00490400, 03

DATA_BLK_ERROR at: 0x00494400, 03

DATA_BLK_ERROR at: 0x00498400, 03

DATA_BLK_ERROR at: 0x0049C400, 03

DATA_BLK_ERROR at: 0x004A0400, 03

DATA_BLK_ERROR at: 0x004A4400, 03

DATA_BLK_ERROR at: 0x004A8400, 03

DATA_BLK_ERROR at: 0x004AC400, 03

DATA_BLK_ERROR at: 0x004B0400, 03

DATA_BLK_ERROR at: 0x004B4400, 03

DATA_BLK_ERROR at: 0x004B8400, 03

DATA_BLK_ERROR at: 0x004BC400, 03

DATA_BLK_ERROR at: 0x004C0400, 03

DATA_BLK_ERROR at: 0x004C4400, 03

DATA_BLK_ERROR at: 0x004C8400, 03

DATA_BLK_ERROR at: 0x004CC400, 03

DATA_BLK_ERROR at: 0x004D0400, 03

DATA_BLK_ERROR at: 0x004D4400, 03

DATA_BLK_ERROR at: 0x004D8400, 03

DATA_BLK_ERROR at: 0x004DC400, 03

DATA_BLK_ERROR at: 0x004E0400, 03

DATA_BLK_ERROR at: 0x004E4400, 03

DATA_BLK_ERROR at: 0x004E8400, 03

DATA_BLK_ERROR at: 0x004EC400, 03

DATA_BLK_ERROR at: 0x004F0400, 03

DATA_BLK_ERROR at: 0x004F4400, 03

DATA_BLK_ERROR at: 0x004F8400, 03

DATA_BLK_ERROR at: 0x004FC400, 03

DATA_BLK_ERROR at: 0x00500400, 03

DATA_BLK_ERROR at: 0x00504400, 03

DATA_BLK_ERROR at: 0x00508400, 03

DATA_BLK_ERROR at: 0x0050C400, 03

DATA_BLK_ERROR at: 0x00510400, 03

DATA_BLK_ERROR at: 0x00514400, 03

DATA_BLK_ERROR at: 0x00518400, 03

DATA_BLK_ERROR at: 0x0051C400, 03

DATA_BLK_ERROR at: 0x00520400, 03

DATA_BLK_ERROR at: 0x00524400, 03

DATA_BLK_ERROR at: 0x00528400, 03

DATA_BLK_ERROR at: 0x0052C400, 03

DATA_BLK_ERROR at: 0x00530400, 03

DATA_BLK_ERROR at: 0x00534400, 03

DATA_BLK_ERROR at: 0x00538400, 03

DATA_BLK_ERROR at: 0x0053C400, 03

DATA_BLK_ERROR at: 0x00540400, 03

DATA_BLK_ERROR at: 0x00544400, 03

DATA_BLK_ERROR at: 0x00548400, 03

DATA_BLK_ERROR at: 0x0054C400, 03

DATA_BLK_ERROR at: 0x00550400, 03

DATA_BLK_ERROR at: 0x00554400, 03

DATA_BLK_ERROR at: 0x00558400, 03

DATA_BLK_ERROR at: 0x0055C400, 03

DATA_BLK_ERROR at: 0x00560400, 03

DATA_BLK_ERROR at: 0x00564400, 03

DATA_BLK_ERROR at: 0x00568400, 03

DATA_BLK_ERROR at: 0x0056C400, 03

DATA_BLK_ERROR at: 0x00570400, 03

DATA_BLK_ERROR at: 0x00574400, 03

DATA_BLK_ERROR at: 0x00578400, 03

DATA_BLK_ERROR at: 0x0057C400, 03

DATA_BLK_ERROR at: 0x00580400, 03

DATA_BLK_ERROR at: 0x00584400, 03

DATA_BLK_ERROR at: 0x00588400, 03

DATA_BLK_ERROR at: 0x0058C400, 03

DATA_BLK_ERROR at: 0x00590400, 03

DATA_BLK_ERROR at: 0x00594400, 03

DATA_BLK_ERROR at: 0x00598400, 03

DATA_BLK_ERROR at: 0x0059C400, 03

DATA_BLK_ERROR at: 0x005A0400, 03

DATA_BLK_ERROR at: 0x005A4400, 03

DATA_BLK_ERROR at: 0x005A8400, 03

DATA_BLK_ERROR at: 0x005AC400, 03

DATA_BLK_ERROR at: 0x005B0400, 03

DATA_BLK_ERROR at: 0x005B4400, 03

DATA_BLK_ERROR at: 0x005B8400, 03

DATA_BLK_ERROR at: 0x005BC400, 03

DATA_BLK_ERROR at: 0x005C0400, 03

DATA_BLK_ERROR at: 0x005C4400, 03

DATA_BLK_ERROR at: 0x005C8400, 03

DATA_BLK_ERROR at: 0x005CC400, 03

DATA_BLK_ERROR at: 0x005D0400, 03

DATA_BLK_ERROR at: 0x005D4400, 03

DATA_BLK_ERROR at: 0x005D8400, 03

DATA_BLK_ERROR at: 0x005DC400, 03

DATA_BLK_ERROR at: 0x005E0400, 03

DATA_BLK_ERROR at: 0x005E4400, 03

DATA_BLK_ERROR at: 0x005E8400, 03

DATA_BLK_ERROR at: 0x005EC400, 03

DATA_BLK_ERROR at: 0x005F0400, 03

DATA_BLK_ERROR at: 0x005F4400, 03

DATA_BLK_ERROR at: 0x005F8400, 03

DATA_BLK_ERROR at: 0x005FC400, 03

DATA_BLK_ERROR at: 0x00600400, 03

DATA_BLK_ERROR at: 0x00604400, 03

DATA_BLK_ERROR at: 0x00608400, 03

DATA_BLK_ERROR at: 0x0060C400, 03

DATA_BLK_ERROR at: 0x00610400, 03

DATA_BLK_ERROR at: 0x00614400, 03

DATA_BLK_ERROR at: 0x00618400, 03

DATA_BLK_ERROR at: 0x0061C400, 03

DATA_BLK_ERROR at: 0x00620400, 03

DATA_BLK_ERROR at: 0x00624400, 03

DATA_BLK_ERROR at: 0x00628400, 03

DATA_BLK_ERROR at: 0x0062C400, 03

DATA_BLK_ERROR at: 0x00630400, 03

DATA_BLK_ERROR at: 0x00634400, 03

DATA_BLK_ERROR at: 0x00638400, 03

DATA_BLK_ERROR at: 0x0063C400, 03

DATA_BLK_ERROR at: 0x00640400, 03

DATA_BLK_ERROR at: 0x00644400, 03

DATA_BLK_ERROR at: 0x00648400, 03

DATA_BLK_ERROR at: 0x0064C400, 03

DATA_BLK_ERROR at: 0x00650400, 03

DATA_BLK_ERROR at: 0x00654400, 03

DATA_BLK_ERROR at: 0x00658400, 03

DATA_BLK_ERROR at: 0x0065C400, 03

DATA_BLK_ERROR at: 0x00660400, 03

DATA_BLK_ERROR at: 0x00664400, 03

DATA_BLK_ERROR at: 0x00668400, 03

DATA_BLK_ERROR at: 0x0066C400, 03

DATA_BLK_ERROR at: 0x00670400, 03

DATA_BLK_ERROR at: 0x00674400, 03

DATA_BLK_ERROR at: 0x00678400, 03

DATA_BLK_ERROR at: 0x0067C400, 03

DATA_BLK_ERROR at: 0x00680400, 03

DATA_BLK_ERROR at: 0x00684400, 03

DATA_BLK_ERROR at: 0x00688400, 03

DATA_BLK_ERROR at: 0x0068C400, 03

DATA_BLK_ERROR at: 0x00690400, 03

DATA_BLK_ERROR at: 0x00694400, 03

DATA_BLK_ERROR at: 0x00698400, 03

DATA_BLK_ERROR at: 0x0069C400, 03

DATA_BLK_ERROR at: 0x006A0400, 03

DATA_BLK_ERROR at: 0x006A4400, 03

DATA_BLK_ERROR at: 0x006A8400, 03

DATA_BLK_ERROR at: 0x006AC400, 03

DATA_BLK_ERROR at: 0x006B0400, 03

DATA_BLK_ERROR at: 0x006B4400, 03

DATA_BLK_ERROR at: 0x006B8400, 03

DATA_BLK_ERROR at: 0x006BC400, 03

DATA_BLK_ERROR at: 0x006C0400, 03

DATA_BLK_ERROR at: 0x006C4400, 03

DATA_BLK_ERROR at: 0x006C8400, 03

DATA_BLK_ERROR at: 0x006CC400, 03

DATA_BLK_ERROR at: 0x006D0400, 03

DATA_BLK_ERROR at: 0x006D4400, 03

DATA_BLK_ERROR at: 0x006D8400, 03

DATA_BLK_ERROR at: 0x006DC400, 03

DATA_BLK_ERROR at: 0x006E0400, 03

DATA_BLK_ERROR at: 0x006E4400, 03

DATA_BLK_ERROR at: 0x006E8400, 03

DATA_BLK_ERROR at: 0x006EC400, 03

DATA_BLK_ERROR at: 0x006F0400, 03

DATA_BLK_ERROR at: 0x006F4400, 03

DATA_BLK_ERROR at: 0x006F8400, 03

DATA_BLK_ERROR at: 0x006FC400, 03

DATA_BLK_ERROR at: 0x00700400, 03

DATA_BLK_ERROR at: 0x00704400, 03

DATA_BLK_ERROR at: 0x00708400, 03

DATA_BLK_ERROR at: 0x0070C400, 03

DATA_BLK_ERROR at: 0x00710400, 03

DATA_BLK_ERROR at: 0x00714400, 03

DATA_BLK_ERROR at: 0x00718400, 03

DATA_BLK_ERROR at: 0x0071C400, 03

DATA_BLK_ERROR at: 0x00720400, 03

DATA_BLK_ERROR at: 0x00724400, 03

DATA_BLK_ERROR at: 0x00728400, 03

DATA_BLK_ERROR at: 0x0072C400, 03

DATA_BLK_ERROR at: 0x00730400, 03

DATA_BLK_ERROR at: 0x00880000, 03

CMT FLASH VERIFY Blocks: 319, Errors: 317, Time: 00:41

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

APE FLASH VERIFY Cannot be Performed for this Product

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

PPM FLASH VERIFY Cannot be Performed for this Product

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

UAR FLASH VERIFY Cannot be Performed for this Product

Verify Completed, Rebooting Mobile

8. What are they mean?? they want to tell you there is something wrong to the device MCU [COR] file(s)

9. Now WRITE FLASH

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

IMAGE : n80_5.0719.0.2-prd_western_c00_cc.fpsx

CMT NOR Erase Area: 0x00080000-00734BCD

CMT NOR Erase Area: 0x00000000-0005FFFF

CMT NOR Erase Area: 0x001E0000-001FFFFF

CMT NOR Erase Area: 0x00880000-00FDFFFF

CMT FLASH ERASE OK, Time: 00:37

Written: 9 Certificate(s)

CMT FLASH WRITE OK, Time: 00:29

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0

APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA

APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

APE 2ND Boot OK

APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0

APE VPP   : Internal

APE KSIG1 : 54965DF2BFA6749422ED197DAD70A03485D35846

DUAL LINE : True

APE ALG Boot OK

IMAGE : n80_5.0719.0.2-prd_western_c00_cc.fpsx

APE NAND Erase Area: 0x00000000-0007FFFF

APE NAND Erase Area: 0x00080000-000FFFFF

APE NAND Erase Area: 0x00100000-0025FFFF

APE NAND Erase Area: 0x003C0000-04C1FFFF

APE FLASH ERASE OK, Time: 00:01

Written: 11 Certificate(s)

APE FLASH WRITE OK, Time: 03:38

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0

APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA

APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

APE 2ND Boot OK

APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0

APE VPP   : Internal

APE KSIG1 : 54965DF2BFA6749422ED197DAD70A03485D35846

DUAL LINE : True

APE ALG Boot OK

IMAGE : N80_userarea_5.0719.0.2-prd.U01

APE NAND Erase Area: 0x04C20000-07D1FFFF

UAR FLASH ERASE OK, Time: 00:00

UAR FLASH WRITE OK, Time: 01:11

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0

APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA

APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

APE 2ND Boot OK

APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0

APE VPP   : Internal

APE KSIG1 : 54965DF2BFA6749422ED197DAD70A03485D35846

DUAL LINE : True

APE ALG Boot OK

IMAGE : N80_rofx_5.0719.0.2-prd.V20

APE NAND Erase Area: 0x03920000-04C1FFFF

PPM FLASH ERASE OK, Time: 00:00

PPM FLASH WRITE OK, Time: 01:04

Flashing Completed, Rebooting Mobile

NOTE: On the case i had to change firmwares to INDONESIAN market by user ordered because it was TAIWAN market device. A good idea to do in one step

10. After flashing completed tick some options on UI OPTIONS then click UI SETTINGS

Set UI Factory Defaults Ok, Time: 00:00

Set Security 12345 ...

Set Security Ok, Time: 00:00

11. After all you can do CHECK and VERIFY again 

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0

APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA

APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

APE 2ND Boot OK

APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0

APE VPP   : Internal

APE KSIG1 : 54965DF2BFA6749422ED197DAD70A03485D35846

DUAL LINE : True

APE ALG Boot OK

PASUBTOC  : PA_SL  

Rebooting Mobile

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1

CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB

CMT FLCNT : 00000000000000000000000000000000000000

CMT MCID0 : FFFF0000-00000000

CMT 2ND Boot OK

CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0

CMT KSIG0 : 54965DF2BFA6749422ED197DAD70A03485D35846

CMT VPP   : Internal

DUAL LINE : True

CMT ALG Boot OK

IMAGE : n80_5.0719.0.2-prd_western_c00_cc.fpsx

CMT FLASH VERIFY Blocks: 319, Errors: 0, Time: 00:29

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

APE FLASH VERIFY Cannot be Performed for this Product

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

PPM FLASH VERIFY Cannot be Performed for this Product

1ST BOOT  : C0,0C [Rm-92] [2.2.0.3]

APE ASICID: 17100708

APE MODE  : 00

APE PUBID : 7C6520A10D15CAFD10A63DADBFCB7EF5CBB774CE

APE HASH  : 49A97E826B93BA20B7ED0B082475C005

APE ROMID : 1DFD66132C872FD4

CMT ASICID: 000000010000022600010006010C192101003000

EM 1 ID   : 00000294

EM 2 ID   : 00000B21

CMT PUBID : 0BE00105668E005481798BBAADD0D0B080FFE3CD

CMT MODE  : 00

CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1

CMT ROMID : 273F6D55DFAAF68F

CMT 1ST Boot OK

UAR FLASH VERIFY Cannot be Performed for this Product

Verify Completed, Rebooting Mobile

12. Now you couldn't found ERROR report anymore on the VERIFY. DISCONNECT

       Turn on your device including the simcard inserted, create a message then send it. Wait a moment and see it goes somewhere...GOOD...GOOD...GOOD...

I hope it could gives you  some example how to fix any problem to the device you handle by software.

Thank you very much for joining to haribagibagi.blogspot.com

wasalamualaikum wr wb

Arek NGAJUM IsoIso Ae [The Fully Fuckin' Headache Lion]