[Android Q&A, Help & Troubleshooting] TheDrive:
PLEASE CAREFULLY READ WHOLE MESSAGE and OBEY ALL THE PRECAUTIONS!

Please do NOT DO a thing unless you UNDERSTAND all the infos!!!

This was a total problem for a years. Casio/Nec have hidden original FW and loader required to flash the phone with damaged GPT or SBL (SBL level loaders. It's illegal in the context of consumer rights in many countries and violates GNU/GPL Linux/components licenses (independently of the fact the loaders itself are the Qualcomm/OEM proprietary SW, but we couldn't use and develop this particular Linux build w/o them). No FW sources were published. Casio-NEC JSC ****ed up the users and now gone from the market and closed support services/servers just upon closing. It's a shame for these respectable Japanese companies which reputation was clear for the decades. I don't care about any law aspects related to the JSC. Casio and Nec have used their brands to sell these devices and it's a shame for them all. I can't realize why could a web server support and source publishing cost any much for a billion corps. There are the laws in many countries requiring parts supply for a whole time of declared device serve period. Is Casio/Nec device's serve period now is set as 1 year only now? :)

If you have lost some money for an ineffective market policy, should your customers , respond for that?

These phines due to unique 'protected' design, good quality and parts are widely popular around the world far away from the official market places. Who have decided not to officially expand to these markets at the time?

There is good sales potential for a good quality protected phones (especially high branded) at the current time.

Adequate ads activity should provide a small but valuable market share.

Let's back to our problems

Now this, PBL-only bricking (QDloader 9008 only) problem has been partially fixed.

You should read my articles here (in English):

http://androidforums.com/threads/rom-stock-c811-m070-firmware-zip-file-4-1-2.878959/page-3

to understand internal eMMC architecture. Please realize you should try to UNDERSTAND, but not simply think how to quickly FIX your brick! You'll fix nothing unless you will understand what's going on and what's the parts responsible for which state.

Next step, go to the Russian 4dpa.ru forums and read my instructions how to flash loaders and get into the Qualcomm QHSUSB_DLOAD 9006 mode.

http://4pda.ru/forum/index.php?showtopic=497930&view=findpost&p=50105534

Sorry, Russian only for a while. You can translate pages with Google translator.

DO NOT DO a THING YET NOW! Simply READ and THINK!

Also read the discussion on that page and a few on the previous and the next pages. DL files (e.g. FW's, utils), you think could help you later on context. (4PDA reg req'd to DL attachments. It's isn't complicated, but service may ask you to enter a numeric capcha described as numeric-words in Russian. That's the problem for non Russian speakers. Once you get the problem note it ask you a random 4-cipher number. Try to translate somehow or request req'd files to upload here. Look may be these files are already uploaded on the AndroidForums (link above and other topics).

(If the messages/links will some kind shift by the time look for the manual posted on 03.06.2016, 02:28 GMT+3 and around)

Big thanks for the correct and the only working Casio C811 / CA-201L loaders go to the nugiedha [MENTION=5711379]ANDROID[/MENTION]Forums

http://androidforums.com/threads/casio-c811-soft-brick-possible-fix.967172/#post-7136788

Then realize simple thing. Loaders will NOT bring your phone back to the working condition immediately!!!

They will allow you to get the direct access to the eMMC and do WHAT YOU WANT with it. You can partition it as FAT32 UFD and then write your favorite pron there if you want, as you do it with your favorite UFD, but sure, it's simply useless. and stupid. and it will kill the rest of the data on the phone. :)

PLEASE NOTE! Upon an eMMC detection as a mass storage device in your PC, YOU SHOULD NOT OCCASIONALLY CLICK OK ON ANY WINDOWS REQUESTS ASKING TO INITIALIZE A NEW DRIVE/PARTITIONS!!! IT WILL DAMAGE DATA ON THE PHONE! BE CAREFUL!!!

THERE ARE MORE THEN 20 PROPRIETARY PARTITIONS ON THIS MEDIA WINDOWS SYSTEM HAVE NOTHING TO DO WITH!

Important! The first thing you should do is to BACKUP the whole image of the BROKEN phone including partition table (GPT) and all the partitions (intact or damaged) as a one big 16GB whole physical disk image to some partition that have enough free space. Do NOT try to backup to the FAT32 partitions. The maximum single file size there is 4GB.

I.e. DO a FULLFLASH backup, aka eMMC full backup image, etc., independently on the fact FW is broken at the moment!

Use HDD Raw Copy Tool form the HDDGuru forums or similar tools to make a full image backup.

You can use any data recovery / disk editing utils, like R-Studio or DMDE later to extract any data and/or whole partition images from there later. Please note, that after the MSImage loader flashing your original GPT will be replaced with a small GPT built into the loader, independently on fact was it correct or damaged at the moment of the failure.

However there is NO way to avoid this. There is NO any other way out to boot damaged phone from the QDLoader 9008 state (it's PBL mode) except JTAG involving tools. That's why you will not ba able to easily find all the partitions in the broken phone eMMC image. But you can scan the image (e.g. with R-Studio) and find the remaining partitions (except proprietary) on their places unless partition header/data was not damaged upon crash.

Next you have 3 options to recover the phone to the working condition:

1. Find Casio CA-201L or C811 FULL FLASH IMAGE (eMMC USER_PART) image dumped from phone placed in the same DLOAD mode

2. Find same image got using JTAG tools (in fact same as above)

3. Recreate partitions (write correct GPT) and all the partition data manually using parts of your backup and original factory partition images, most of which (for C811 and partially for CA-201L) you can find on the AndroidForums topic.

Option 1 (or 2) is easy to understand and perform. But there are 3 notes on it

1. You should find Full eMMC image for your phone or the one who will dump his phone's image for you

2. All the ID's, i.e. IMEI, MAC's etc and current User Data will move from that image to your phone.

You can make a user data wipe (Hard Reset) to destroy user data and get a 'factory state' phone later.

I do not know a way to patch IMEI/MAC's back to your originals for a while (do not have phone on my hands for experiments),

but sure these ID's are stored on some of the 'unique' partitions, listed in AndroidForums topic and you can find and extract this partition (unless it damaged) from your damaged eMMC image and flash it to the recovered phone. by any method (directly to the eMMC, using FastBoot mode, using ADB/Linux DD commands). It's theory, that I can't revert to the practice for a while.

3. YOU SHOULD NOT TO ASK A MAN, WHO WILL AGREE TO DUMP HIS PHONE IMAGE FOR YOU TO USE MSImage LOADER METHOD TO SWITCH PHONE TO THE QHSUSB_DLOAD 9006 MODE!!! Otherwise he will DAMAGE HIS GPT AND MODEM FW and you BOTH will get 2 NON WORKING phones instead of 1!!!

There are another methods available to switch this phone to the eMMC DLOAD mode while it resides in the working condition (unless SBL is able to load). The first is to hold both VOL keys at the powering up.

Switch phone off, remove and insert battery to be on the safe side, then hold down VOL+VOL- and press Power Key, then connect USB cable. Other options is to hold VOL keys and connect USB cable without Power key or hold keys and connect USB cable without battery. However these options, most probably will bring QDLoader 9008 mode related to the PBL instead of QHSUSB_DLOAD 9006 mode related to the SBL. That's why if your phone have GPT or SBL structures you can't get it into the QHSUSB_DLOAD 9006 mode unless you will flash MSImage (containing GPT and all SBL-related code) using described procedure.

So, please NOTE one more time YOU SHOULD NOT flash MSImage loader to the working phone! You will damage GPT and get phone to the non working condition!

Another way to switch WORKING phone to the QHSUSB_DLOAD 9006 mode id to use software switcher like the ones, that can be found in QPST eMMC Flashing app and QPST Memory Debug app. Search by google for a detailed manuals with screenshots how to do it (switch to DLOAD) with any Qualcomm based phone (You can try with any, but not all the phones will switch because of customizations!)

There are some other methods circulating around how to force particular WORKING Qualcomm based phones switch to DLOAD mode (using ARM native code app / loader or send command to the Debug port of the modem).

Upon the eMMC image creation you should disconnect working phone fro the USB cable and reboot it to switch back to the normal mode., Just hold Power key for a long time or remove and reinsert the battery.

You should reserve 15-20 minutes of time to perform full eMMC backup procedure.

Upon your damaged phone will switch to the QHSUSB_DLOAD 9006 mode using MSImage loader,

you can simply write one's full working phone's eMMC image using HDD Raw Copy Tool.

Just write from Image file to the eMMC device, then disconnect phone, reset it (reinsert battery) and switch it on.

Phone will boot identically to the donor phone. Perform further generic recovery procedures to revert to your phone to the required condition. You may switch is to the DLOAD mode again using 'normal' way and continue to perform eMMC editing, particular partition images writing, patching, etc.

Option 3 (manual image combining without one's working full image) is much more complicated to proceed, but there are almost all the required data can be found around. Get the original GPT (and GPT backup) from the AndroidForums factory images or look for the GPT backup at the end of the eMMC (It's standard. GPT should have a backup copy at the end of media and eMMC holds this backup, look for it). If you will find GPT backup, try to compare it with ones from the factory images from the AndroidForums.

It will clear for you is your previous FW have had same GPT partition structure and find differences in the partition sizes and locations between your old FW and particular Factory FW. This will help you to extract unique and/or any other req'd partition images from your broken full and inject them to the new full, you building up for whole phone flashing. Use DMDE Disk Editor (Free version is absolutely enough, unless you would like to mass recover files from your data partition with it). It will show you all the GPT structures, their sector ranges. It will help you to locate and extract particular partition Upon correct GPT written to the device (or your new image preparation), you can start to write partitions at their dedicated places. Once you have checked (and/or fixed) all the partitions your phone is ready to swich on. In most cases you have great chance to recover without one's full. The only condition all the small 'unique' partitions that is not included to the factory FW images should be NOT damaged. Please note, that many people reported that damaged/incorrect ModemSTx (modem data / NVRAM) erasure on THIS PARTICULAR PHONE will lead to the working partition recreation (assume w/o IMEI loss) and could be used as one of the NVRAM fixation techniques.

So you should have at least be able to extract important ID's (may be a few others) partition(s) and inject them to your new image (or directly to the eMMC).

That's why you should NEVER start to the recovery (eMMC writing) UNLESS YOU HAVE MADE A BACKUP COPY OF THE DAMAGED eMMC IMAGE!

Sure in 99% you will recover your phone whether you will find one's full (simple) or your will be able to rebuild it using factory (others, why not?) images and the part of your broken eMMC contents.

Good Luck!

I'm attaching here the required files. Please be careful!

Some people just DL files and do not copy the description.

The novices can broke their devices trying to do 'something idiotic'.

Please note, that attached GPT images are definitely for factory M070 FW for C811 version.

You can flash it to the any compatible versions (like CA-201L) but I don't know, will it be identical to your old partition scheme, so real unique partition data you could look to find mat be located at another offsets.

Check manually if you can and always make full broken FW eMMC image at first.

Get flesh QPST 2.7.425 here, thanks to drkcobra

http://xdaforums.com/showpost.php?p=59235714&postcount=15

Or look the topic to find later vers (if any)

Direct Link:

http://www.mediafire.com/download/neeapht51ub2333/QPST.WIN.2.7_Installer-00425.1.zip

Important Update:

Casio C811 GPT images were broken due to the Windows decryption utility compilation problem.

File re-uploaded! Please update!