Trying to work on pulling image from my BLU Studio C 5+5 LTE and creating a recovery.img
It will be specifically for-
An UPDATE (5/17/16)-
I have tried several different techniques to get an imaged flashed but I am running into roadblocks.
#1 Technique - Flash the entire device using factory tools.
Several of the various tools require 8909_msimage.mbn
When I try to build the file with
emmcswdownload -f "C:\Program Files (x86)\Qualcomm\QPST\bin\8909_msimage.mbn" -x "C:\Users\jtourvil\Desktop\BLU\My Blu Recovery\rawprogram0.xml" -s 5G -g 64M -p "C:\Users\jtourvil\Desktop\BLU\My Blu Recovery\";
the tool errors out and dies on me. Anyone have ideas? I have tried playing around with the s and g parameters but haven't had luck getting a file output. I am confident of my rawprogram0.xml file as it matches up with the partition structure I manually mapped out using gdisk.
#2 Technique- Build OTA update file to fix key system files
The file requires having the correct signature dependent upon a set of test keys. I get the following error-
-- Install /sdcard/myupdate-signed.zip..
Finding update package...
I:Update location: /sideload/package.zip
Opening update package...
I:read key e=65537 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1537 bytes; signature 1519 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
I:Saving locale "en_US"
I read the following guide-http://jhshi.me/2013/12/02/how-to-create-and-sign-ota-package/
As I understand it, having the correct keys is dependent on having testkeys for your build. I have the build environment setup. The testkeys will be built when you compile the device. Not sure quite how to proceed. as this is a slightly custom build and not mainline like many of the AOSP builds are for Nexus devices, etc. I have the kernel source from Blu but that alone is not enough from everything that I know. (Someone tell me I'm wrong!!!)
#3 Technique- Create Bootable SD Card
Problem- because of the locked bootloader you can't even fastboot a modified kernel. Issuing ./fastboot <"kernel"> <"ramdisk"> results in the system reading the image and trying to download it to the device. It fails because of the locked bootloader issue.
Not sure how to proceed on this one.
At this point I think I am tapped out on ideas. I have learned a LOT about how this device works and have made a lot of notes on what does and doesn't work. I have tons of notes and a full backup of the device (raw images of all partitions created using DD) but I can't get anything to write an image back to the device. Maybe there is a Dev who would be kind enough to take pity on me and see if they can help me cross the finish line on any of this?