Index
- Introducion
- Languages
- Changelog
- cm 12 vs cm 13
- microg vs gapps (google-apps)
- Do a proper backup and save your warranty
- Hopefully most simple install (very quick guide)
- SP-Flashtool - the way to flash your phone also when it's dead (and how to connect it)
- TWRP for Cyanogenmod
- No IMEI/Sim-Card? SP-Flashtools again!
- No root? Just a setting-thing!
- BRICKED
- How i've done the Image
- Password and SW for NVRAM.encrypted
- Credits & Links
Introducion
This document has it's recent version @ http://piratepad.net/b15q
Please write new languages to http://piratepad.net/b15q-language, you not have to register!
Add them under languages. Rewriters basicly welcome
File-contents on https://drive.google.com/folderview?
id=0ByDwEzL3kR7iaWJnb1d2dG9VZVk&usp=sharing
The Cat B15Q-Phone is great. At least in hardware, it's ultrarugged. The software is not supportet
and stock-rom is still on Android 4.4.2 what's not changing. Therefore, this old Android-Version
contains security-holes.
A proper cyanogemmod-rom is often whished and i wanted that for my own phone too. In this
instructions, i like to create a "set" from backups over the www and how to controll that phone.
Personaly a main-reason for that thing was to get a rid of the google-apps. I hope, the
"FAQ"/Instructions are usefull and the file-collection doesn't hurt someone ;)
So i'm proud to release the eventualy first port of android 6 and android 5.1 . It‘s ported, so many
thanks to mtkroms.com for doing this.
Cm 13 / android 6 is basicly stable and the first port, but have many errors in logcat /debug.
Cm 12 / android 5.1 is also stable, second port and have nearly no errors.
For further diffrents look into cm 12 vs cm 13
My phone and region is europe, so don't know if it works with us-phones. If not, you could try to
rebuild via steps in last part.
Of course i give no warranty on anything in this software!
Languages
-http://piratepad.net/b15q-da
-http://piratepad.net/b15q-esp
Changelog
V4 (28. Sept 16)
- Rewrite docs.
- Add cyanogenmod 12.1 / android 5.1
- Various changes on cm 13, it‘s base was V2
V3 (18. Sept 16):
Thanks to https://github.com/bgcngm/mtk-tools, , i was able to open boot.img edit ramfs and
rebuild
done
- add files in system from stock, system/vendor/lib/hw, containing blueangel-files (activated in
build.prop)
- edit file_contexts in ramdisk, at bottom from stock-file
- edit uevent.rc to add /dev/gps and similiar (at bottom and from stock)
- removed mtklogger.apk in system, seems to be still active in logcat
- rewrite short guide a little
solves
- gps and basicly agps. lot of errors about gps/mnld/agps in logcat are gone.
- other failures in logcat seems to be solved, but that's more subjective.
V2 (11. Sept 16):
Found out optimations in build.prob. New/changed values:
#ro.sf.lcd_density=320 # original-val from mtk-roms.com
ro.sf.lcd_density=233 # val for b15q
ro.sys.usb.charging.only=no
# USB BICR function, from cm it's yes, in stockrom it's no
ro.sys.usb.bicr=no
+ delete some unused files in zip (from work).
The first line (lcd_density) seems to be the most important to me, cause they restore original device-
screen-resolution. On a installed cm, you basicly just could replace the lines in /system/build.prop .
cm 12 vs cm 13
Cm 12:
- older version
+ fm-radio-app
+ more stable
+ less logcats
Cm 13:
+ newer Version
+ some more features
- less compatible to kernel (which is difficult to recompile proper)
microg vs gapps (google-apps)
My motivation for this images was out of the reason to be more google-free.
On cm 13, users said, gapps is not working.
This is untested for cm 12.
Anyway, there is microg too, a free alternative to the google-stuff. On cm 13, this improves a wide-
defined gps-“fix“ massive.
Do a proper backup and save your warranty
In the next topic, it's about a tool which is able to destroy and to safe – SP-Flashtool.
This means, care about the "Readback"-Tab first, after you can flash your stuff more carefree via the
"Download"-Tab.
This is important!
Often, there is a problem with NVRAM/IMEI. The IMEI-Nr is the hardware-address of your
telephony/gsm-modem. This nr is important for connecting into a phone-network. The IMEI-Nr is
stored into the so-called NVRAM-Image-file/NVRAM-Partition.
To flash a IMEI-Nr, which isn't your's, is may not legal in your country. This is a reason why you
should make your own backup.
The other reason is: If you have hardware-problems and you have to send your Phone to Cat, then
they could read the IMEI written under your battery and compare it to the IMEI in your phone -
when this doesn't match, the phone was modified and waranty is over.
When you have a proper backup of your whole system, you're able to recover everything. They will
never know that a cyanogenmod-system was on your phone, what makes your warranty valid again.
So please: do a Backup or if you don't have, spend some hours to find out how to restore your
original imei. (How to do that exactly will follow - maybe - just ask the web for ;)).
Hopefully most simple install
In short ways for people who don't had problems yet, some short steps:
1. Use SP-Flashtool for flashing TWRP (AND BACKUP! ALSO OF NVRAM!)
2. Boot into TWRP (Vol Up + On @start)
3. Format system and data-partiton in twrp (wipe->advanced wipe)
3. Install the cyanogenmod13.zip-file.
4. Wipe cache and try restart
Factory reset and system-formating is needed!
SP-Flashtool - the way to flash your phone also when it's dead
This part is about the SP-Flashtool-Software:
https://androidmtk.com/smart-phone-flash-tool
Use this tool first, to make a proper backup of your system.
There are some img-files avaible on the Web, often from backups. With the right
ones, you
could recreate the whole system!
The so-called scatter-files will show you the partitions. So you need often one scatter-file and the
right images.
To flash your phone do following:
- remove battery out of the phone and disconnect from computer
- press "download" in SP Flashtool on your Computer
- put the battery first in, then connect with computer.
- have a look inside sp flashtool to see progress until a "finish-window" appears
Well, with this you could restore your original-system - and a little more (read next chapter)
TWRP for Cyanogenmod
There are img-files for the good-known recovery called TWRP on B15Q (search searx.me for "b15q
twrp"). We use this one for extended access.
For installing it, just put the TWRP-File into the recovery-partition in SP Flashtool.
For starting TWRP after installing it, press the volume-key up plus press the
on/off-button and
hold them until the twrp-logo appears.
In the TWRP-Bootloader click "Install", then get the cyanogenmod13.zip-file. After start installing,
take a coffee-break, wipe cache and restart.
No IMEI/Sim-Card? SP-Flashtools again!
If you've lost your IMEI-nr's like me after try several stuff, then reflash all the hidden partitions and
may more.
Just let twrp in
recovery be, for having quick access to twrp again.
IMPORTANT:
Using your own NVRAM-file or reflash your own IMEI-nr with for example SN-Writer or
the
on-the-phone-solution via mtk-engineer-tools. On cyanogenmod, also mtkdroid is tested possible
Just search for that.
It is illegal or at least a grey-zone in law to use another imei than the registered on
the phone.
No root? Just a setting-thing!
When you've a fresh install of cyanogenmod 13, filemanager will crash the first time and
starts
just in safe-mode after. This means, root-mode isn't avaible.
This is valid for all apps using root in this time.
Solution: Settings -> About the phone . There you click about 10x on "Build Number".
This activates
developer-settings, one above "About the phone".
In developer-settings you will find a point "Root-access".
Options for
root-access are adb, apps, adb + apps and none. As regular user i
recommend
you to use apps or none (if root not needed).
BRICKED
I‘ve wrote 2
texts, second is, when you‘ve formated your phone via
sp-flash-tools. The
steps with hidden-scatter-files are may better
ignored, this have to be rewritten a little.
1. go http://spflashtool.com/ and download it for your system. linux 32bit seems to have problems,
windows needs driver, i'm using linux 64bit and it's working good
2. go to the google-drive-repo
3. there's a folder "Recover". Every partition needed is there. download them all.
4. in the folder "used scatter-files", you will find valid scatter files. yours is maybe another, you will
detect that on the later error "mtp table changed".
5. download the hidden-partition-file from scatters (seems to be same as the other version, just
downloadable to device)
6. extract and start spflashtools via ./flash_tool (linux) and go to download-tab
7. choose the hidden-scatter-file
8. in the subpart of the window, partitions will be shown now. click on filename. because of files
have no .bin or ending, you don't will see them. most of them are same named like the partition and
you just could write the name in file. do this for every partition.
9. click the download-button. this brings your computer in the
right mode.
10. latest now, disconnect your phone and remove the battery.
11. put in the battery and connect
12. look into sp-flash-tools if you see the progress-bar
13. do the steps 7 until 12, but with the normal scatter-file and
it's partitions.
14. disconnect, remove battery, insert battery and start it.
15. NVRAM is special, cause it holds the imei-nrs. because of
this it's encrypted by vera-crypt.
link and password is in the
readme or piratepad. but if you don't have it, flash it!
16. don't stay on the wrong IMEI-nr (illegal). flash any kind of
half-working cm on your
device again. then get a windows-computer
and mtkdroidtools. there, you click on the big
IMEI-button, where
you could set your IMEI again. THIS IS NOT POSSIBLE IN STOCK-
ROM
CAUSE OF NON-EXIST ADB!
17.reboot. after you set your IMEI and rechecked it's alright,
you could use sp-flash-tools for
flash system and may data, as well
as recovery to be very stock.
18. enjoy your phone.
Second text,
when whole phone is formated
You basicly kick
your partition-table. This is easy!
Reflash all img-files as explained before. This will create the partitions reconized by system.
Because you've no userdata and cache-img will fail, do the follow:
1. Put system.img
to userdata-partition and bootloader.img to cache-partition
2. Flash that with
all other partitons. Of course flash the system.img also on ANDROiD,
not just userdata (same for the bootimg-partition).
3. After flashing
and may reflash twrp, boot into twrp.
4. Go to wipe,
select data and cache and format it.
5. Mount data, go to advanced -> filemanager and delete /data/media (twrp let this
folder be,
but remember, it's from system.img and because of that
wrong)
5. Install cyanogenmod as usual.
How i've done the Image
Cyanogenmod 12.1: http://pira
Get this image:
http://www.mtkroms.com/2016/08/cyanogenmod-13-for-mt6582.html
Unzip it.
Then replace the files which are descriped on the page:
In /system/lib/
- libMali.so
- hwcomposer.mt6582.so (in my case from subfolder hw/, also replaced
in that subfolder)
- libaudio.primary.default.so
-libcameracustom.so
- libcamalgo.so
- libcamdrv.so
- libfeatureio.so
In /system/bin/ :
- gsm* (all files with the name gsm)
- rild (replace rild from working cm12.1)
In /system/etc/ :
- bluetooth, firmware, wifi (replace entire folder)
In boot.img :
- kernel/zimage (in my case after unpacking called kernel)
I've also copied some files like /system/bin/sdcard and /system/bin/vold .
Then i've copied
some of the stock-apks from /system/app to the new rom. Most-often
mtk-files but also some gsm-stuff. Not 100% shure what's needed,
compare my image with the
original.
Also some folders
like media and etc-files where copied. This was out of "adb logcat"-
researching (what was missing was copied).
In
META-INF/com/google/android/updater-script , the system-partition had to be corrected
(/dev/block/mmcblk0p6 instead of
/dev/block/mmcblk0p5). In other Roms there's
/dev/block/mmcblk0p7
for /data - this has to be /dev/block/mmcblk0p8.
Because of this was
a very tryfull time, i'm not shure about all files and where they
from -
some are of my own phone, some of backups and some of
cyanogenmod 12 from mtkroms.
Btw, mount of a
system.img )for getting stock-rom-files) is simply
mkdir /tmp/mount
mount -o loop
/path/to/system.img /tmp/mount
In the end, make a
zip out of the data again.
https://github.com/bgcngm/mtk-tools
was us
I hope, this let
you reproduce the whole thing - elsewhere just enjoy with existing..
Password and SW for NVRAM.encrypted
It's repeated the x-time - please take care of the IMEI-Nr and use your own as possible.
If you need a valid
NVRAM/IMEI for restructure, there is a valid one at NVRAM.encrypted
Software you need:
https://veracrypt.codeplex.com/
Password: hall0Welt
Credits
Ajit Guraya, Team Roger That (mtkroms.com)
The cyanogenmod-team
The XDA-people's who put backupsfiles online (yes, i should do backups too)
Maybe myself
(Vinzenz Hersche, hersche.github.io / hersche@openmailbox.org)?
...and the austria dude with the unlimited mobile-www-connection for uploading the stuff :p
DZONY220V