Database Info

[TOOL]TWRP/AROMA SPFlash | MediaTek

AROMA/TWRP version of SPFlash Tools.
This tool is for MTK devices with a GPT layout - (MT6732, MT6752 and their variants).
With some testing it may be possible to add some some support for the older devices using an MBR.
Requirements:Copy SPFlash contents to /sdcard/SPFlash
Rename *scatter.txt to scatter.txt
Run .zip from TWRP​MTK-64bit_SoCs-v*.zip:During testing there will only be info displayed on screen, nothing should be modified. (Unless otherwise stated)​SPFlash-v*.zip:This will install all .img/.bin in SPFlash folder if partition is large enough​Downloads:GDrive Folder​Changelogs:SPFlash
v10 - Readded internal sd - fixed aroma exit/about screen - (a few cosmetic issues introduced).
v8 - Aroma menus updated
v7 - Create 'flashable' zip from backed up partitions.
v6 - Zipped backups added
v4 - Backup + Install fixed -- Aroma "Quit Installation" stalls
v3 - Backup function added - untested -- backup works / install from v2 broken
v2 - Menu Select Added
v1 - Initial Release
MTK-64bit_SoCs
v8 - attempts to fix unrelated menu/alert
v7 - calculations done quicker
v6 - script rewrite/reorder
v1 - v5: Initial test builds​
Only follow menu Partition Related -> Scatter Information
Other menus/option are broken/dead ends...
Other things in the MTK folder:simg2img/img2simg are arm source compiled binaries to handle sparse files
file/magic were taken from @osm0sis's AIK (I can't seem to get file to compile)
MTKsplit is used to split boot/recovery images into it's individual parts. Normal images will split into 3; 1 = img ANDROID! header, 3 = kernel (zImage) and 5 = ramdisk (ramdisk). MTK images split into 5; 1,3,5 as before with 2 and 4 being additional headers.​
XDA:DevDB Information
TWRP/AROMA SPFlasher, Tool/Utility for all devices (see above for details)
Contributors
HypoTurtle
Source Code: https://drive.google.com/open?id=0B8WPOq9wZyKxfktHVWgxbW9nYmtJd1ZWc2RIM1NXUU5pSXpramg0bVBYYUdyRDhid3hwM3c
Version Information
Status: Testing
Current Stable Version: V8
Stable Release Date: 2015-09-03
Created 2015-09-03
Last Updated 2015-09-03

Current StatusMTK-64bit_SoCs-v8 .zip will output the partitions that it deems are incorrectly sized in the scatter.txt and will also check the .img/.bins in the SPFlash folder and determine what should go where and will determine if the partition is large enough for the respective .img/.bin
SPFlash-v1.zip will flash the entire contents of /sdcard/SPFlash folder
SPFlash-v3.zip allows selection of files /sdcard/SPFlash folder to install and has a backup option​
Improvements NeededFor SPFlash-v2 will add a basic menu select option for what you want to flash...
In future versions will add backup option and partition resize
Will start to look at resize...​

Derivative Work - using scatt and part from #1
ScatterfixGenerating a fixed scatter from a 'broken one'
Code:
[size=1]#!/sbin/sh
ldr=`pwd`
scatterfix(){
scatt \${b} \${c} \${d}
part \${p} \${q} \${r}
scttrbfr=`cat "${scatterloc:-$ldr}/scatter.txt"`
while IFS=" " read -r a b c && read -r d e f <&3; do
if [ $a = $d ]; then
if [[ ! ${b} = "DONT_USE" && ${b} != ${e} ]]; then
scttrafter="${scttrbfr//${b}/${e}}"
scttrbfr=`echo "${scttrafter}"`
fi
if [[ ! ${c} = "DONT_USE" && ${c} != ${f} ]]; then
scttrafter="${scttrbfr//${c}/${f}}"
scttrbfr=`echo "${scttrafter}"`
fi
fi
echo "${scttrbfr}" > ${scatterloc:-$ldr}/scatter-new.txt
done </tmp/scatter 3</tmp/parted-new
}
scatterfix
diff ${scatterloc:-$ldr}/scatter.txt ${scatterloc:-$ldr}/scatter-new.txt[/size]
Problems to fixThe code will change any hex value deemed wrong to a new calculated value - there is a chance that 4 values are the same but only one/two are wrong - to fix will need to add a loop through scatterfix until the scatter-new.txt generated is actually correct.​​Resize Userdata/IntsdMore of a precursor - bugs fixed and maintained by @odigitech
Thread located here​

Some Dev. QuestionsBefore adding the resizing partitions (Firmware Upgrade) option:
1. Is the preloader header custom or generic; and does it change when flashing the proloader?
2. Is there an actual function to the BPLGU/APDB files other than some sort of device/system check?​

For v7 trying to add a backup + make installable zip option:
Have done it with basic dd backups; would prefer to use sparse/simg2img but simgimg can't seem to use zipped .img's; have looked into using dat/sdat2img but that would require getting python to run in recovery (unless I'm mistaken).

Have added the simplistic option as v7...

odigitech said:
@HypoTurtle I have made a modified version of MTKsplit with more human-friendly names, its in my Drive folder, if it's any use.
Click to expand...
Click to collapse
Thanks, I have updated mine to support non-MTK header-ed boot/recovery.imgs -- can't hurt to make it human readable I suppose.
MTKsplit will be used in the next uploaded version (v8) in the form of a simplistic porting tool...
Should be uploaded on Monday/Tuesday

odigitech said:
You made it work for non-MTK also? Nice one, is it on your Drive?
Sent from my thl 2015 using XDA Free mobile app
Click to expand...
Click to collapse
Should be... but I'll update it with the human-readable version now.
It's not vigorously tested; and not as robust as the (un)mkbootimg binaries out there but it seems to do the job.

@HypoTurtle: on my Jiayu s3, the Germans have been working on android 5.1.1 for it and so far it is great. I installed beta 3 and the next day they released beta 4. Rather then getting out the laptop, I thought I'd use your script, so I got the files needed, I got your script and set it up as the instructions. But when I ran the script, it didn't find the system.img file, and didn't give it to me as an option. I verified that the file was there on disk, but I was never given a check box to select it for flashing. Any logs I can send you to try and figure out why?
Sent from my KFTHWI using XDA Premium 4 mobile app

AlexZap said:
@HypoTurtle: on my Jiayu s3, the Germans have been working on android 5.1.1 for it and so far it is great. I installed beta 3 and the next day they released beta 4. Rather then getting out the laptop, I thought I'd use your script, so I got the files needed, I got your script and set it up as the instructions. But when I ran the script, it didn't find the system.img file, and didn't give it to me as an option. I verified that the file was there on disk, but I was never given a check box to select it for flashing. Any logs I can send you to try and figure out why?
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it just the system.img that doesn't appear? And are you using internal or external SD?

HypoTurtle said:
Is it just the system.img that doesn't appear? And are you using internal or external SD?
Click to expand...
Click to collapse
Just system.img, and external_sd
Sent from my KFTHWI using XDA Premium 4 mobile app

AlexZap said:
Just system.img, and external_sd
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you post the scatter; the menu items are just an existence check.
[ if *.img/*.bin from scatter exists in SPFlash folder then you are given the option to flash it ]
(Just noticed that it will stall if you try and install and there are no valid img/bin files present)

HypoTurtle said:
Can you post the scatter; the menu items are just an existence check.
[ if *.img/*.bin from scatter exists in SPFlash folder then you are given the option to flash it ]
(Just noticed that it will stall if you try and install and there are no valid img/bin files present)
Click to expand...
Click to collapse
Screenshot of the folder, and the scatter. I checked it and it looked fine.

AlexZap said:
Screenshot of the folder, and the scatter. I checked it and it looked fine.
Click to expand...
Click to collapse
Ah yes - this problem is caused by the amount of items shown - I have it set to show 3, 5 or 12. It will only show 12 (more than 5) if there are 12 things to flash. From your screenshot you have 7 items to be flashed (trustzone gets flashed twice), so you will miss two items - the second flash of trustzone.bin and system.img.
Hope that makes sense; I can alter it to work with 6+; but you should be able to adjust it to work as described above. the reason I did it this way was that otherwise it would look a bit messy - I suppose I could add a 7 option.

HypoTurtle said:
Ah yes - this problem is caused by the amount of items shown - I have it set to show 3, 5 or 12. It will only show 12 (more than 5) if there are 12 things to flash. From your screenshot you have 7 items to be flashed (trustzone gets flashed twice), so you will miss two items - the second flash of trustzone.bin and system.img.
Hope that makes sense; I can alter it to work with 6+; but you should be able to adjust it to work as described above. the reason I did it this way was that otherwise it would look a bit messy - I suppose I could add a 7 option.
Click to expand...
Click to collapse
Ahhh... Not a. Problem then. I don't really need to flash anything besides system and boot. I just included the rest for completness. I'll take one out and let you know how it goes.
On a side note, any reason for these (3, 5, and 12)? An not just everything that is there?
Sent from my JY-S3 using XDA Premium 4 mobile app

HypoTurtle said:
Some Dev. QuestionsBefore adding the resizing partitions (Firmware Upgrade) option:
Q1. Is the preloader header custom or generic; and does it change when flashing the proloader?
Q2. Is there an actual function to the BPLGU/APDB files other than some sort of device/system check?​
Click to expand...
Click to collapse
A1 - Generic, MTK preloader has been the same since armv7 to armv8. Yes, dd backup copy needs to be clean up of the header & footer, more info then checkout with AlexZap... :good:
A2 - Not all MTK firmware include it, it contains the IMEI refer to here for more info or a single link that explained everything... :good:

AlexZap said:
Ahhh... Not a. Problem then. I don't really need to flash anything besides system and boot. I just included the rest for completness. I'll take one out and let you know how it goes.
On a side note, any reason for these (3, 5, and 12)? An not just everything that is there?
Sent from my JY-S3 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if you missed the edit. It was more for cosmetic reasons - I could have had say 12 files being displayed but if there's only one file to flash you would have a screen with a lot of blank entries. 3, 5 and 12 seemed the most appropriate without going down the route of creating a menu for all possible entries.
3 being typical install (system/boot and perhaps blank cache/userdata to wipe); 5 as 3 but with custom etc.
I figured that anyone with more than 5 flashable items in there would have dumped the entire SPFlash ROM which I calculated as ~12 items.
yuweng said:
A1 - Generic, MTK preloader has been the same since armv7 to armv8. Yes, dd backup copy needs to be clean up of the header & footer, more info then checkout with AlexZap... :good:
A2 - Not all MTK firmware include it, it contains the IMEI refer to here for more info or a single link that explained everything... :good:
Click to expand...
Click to collapse
A2. I don't thing it contains the IMEI - but it is the database that the IMEI is coded against; I'm not aware of any devices (other than the P6000) suggesting that you recode the IMEI on an upgrade from KK to LP so there is probably not an issue here.

i never use it myself, typically MDRT is able to recover it on mine, feedbacks from fellow XDA member is that, that is the only way that they manage to recover IMEI on their MTK...
On 2nd thought, BTW, i'm using intel nowadays :laugh: IMEI & calibration info is at a hidden partition, same as Samsung & Qualcomm devices that reside at /efs partition, how did MTK IMEI survive Factory Reset since it is at /data/nvram, i wonder, never really thought about it...

yuweng said:
i never use it myself, typically MDRT is able to recover it on mine, feedbacks from fellow XDA member is that, that is the only way that they manage to recover IMEI on their MTK...
On 2nd thought, BTW, i'm using intel nowadays :laugh: IMEI & calibration info is at a hidden partition, same as Samsung & Qualcomm devices that reside at /efs partition, how did MTK IMEI survive Factory Reset since it is at /data/nvram, i wonder, never really thought about it...
Click to expand...
Click to collapse
On the 64bits at least it is also on a hidden partition (nvram) - and it just gets copied to /data/nvram or something (ie. its not mounted but it's files are there). The DB files etc are present in /system as well as in the full SPFlash ROM so I guess things like MTKEng and apps like chamelephon use that when setting/'fixing' the IMEI.
What are the file formats used by intel stock ROMS? This tool isn't really MTK dependant - it's GPT partition dependant (with a scatter for validity check- I'll post a bear minimum of what a 'scatter.txt' needs to have).
Anyway v8 added - so that files to flash aren't hidden (max. 12 files).

Hmm, further digging seems MTK IMEI is at /dev/nvram, same thing happening on intel, users just never spell out everything, they use the format/ erase flash/ emmc that wipes out the IMEI partition but never tell...
i think on the X3, its not possible as its NOT an Android image file but proprietary fls file which they got it when they acquire infineon i think...
Manual fastboot/ dd backup/ restore & you'll end up with a brick device, ATM, no custom recoveries that boot on the x3, i haven't figure out how to repack its recovery that has three separate different region that requires three proprietary download file that packs it together into a fls file & only their FlashTool_E2 is able to download it correctly...
Can't really understand infineon/ intel for developing such cheap device but with such high end software tools...

[MTK][TOOL][APP]MTKTransfROM, port your ROM directly from phone!

Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Code:
[B]system/bin/vold [/B] (Copy this file from your device)
[B]system/etc[I]/[/I][/B] (Copy entire directory, replacing existing files)
[B][I]-[/I]system/etc/ [/B] (First delete ROM folder and then copy entire folder)
[B]system/lib/libaudio[I]*[/I][/B] (Copy all files that starts with libaudio...)
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.​

Can you add support for MT6752 devices?

You can add it yourself putting your custom files in the folder I explained in the tutorial

RacerOttavio97 said:
You can add it yourself putting your custom files in the folder I explained in the tutorial
Click to expand...
Click to collapse
Thanks, I will try it and see if it works :fingers-crossed:

I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.

HypoTurtle said:
I was thinking of doing something similar with MT6732/52 devices...
[I'd be doing it from recovery as I have almost zero app making abilities]
Have a look at the MTKsplit file in the MTK folder in my sig. for the boot.img (un)pack - it works fine with the 64bit SoC's boot/recovery images - so not sure about the older ones.
Click to expand...
Click to collapse
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.

RacerOttavio97 said:
Thank you HypoTurtle, but I'm searching a tool that run on android phone itself, like a sh script or a linux binary.
Click to expand...
Click to collapse
MTKsplit can/does run on android itself - thats why I wrote it. It's a sh - primarily using dd to split the boot/recovery. I removed the #! at the top so the same script can be run fron recovery and system (making it default to the shell that calls it - /sbin/sh in recovery and /system/bin/sh in system).
Just tested the MTKsplit against a 6592 recovery.img and it works fine:
Code:
[email protected]_phone:/tmp # ls -la
ls -la
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
[email protected]_phone:/tmp # MTKsplit recovery-6592 unpack
MTKsplit recovery-6592 unpack
Unpacking recovery-6592 - will only take 30 seconds
All Done...
Command line: f30"
Ramdisk unpacked to /tmp/work
[email protected]_phone:/tmp # ls -la
ls -la
-rw------- root root 4265472 2015-10-05 16:24 kernel
-rw------- root root 512 2015-10-05 16:23 kernel_header
-rw------- root root 2048 2015-10-05 16:23 mtk_header
-rw------- root root 1598976 2015-10-05 16:24 ramdisk.cpio.gz
-rw------- root root 512 2015-10-05 16:24 ramdisk_header
-rwx------ root root 5867520 2015-10-05 16:22 recovery-6592.img
drwx------ root root 2015-10-05 16:24 work

Android sdk
Is it necessary to be the port rom is the same android sdk level of my mobile stock rom ?!

RacerOttavio97 said:
Hi guys,
I'm here to explain my new fresh app that I tested on my HTC Desire 310 and it's faboulous. His name is...
MTKTransfROM
*What does it do?
- This app will let you do all the process of porting an MTK ROM to your MTK phone without a PC! You can choose a lot of options and method, like signing ZIP, Fix BootLoop/Stuck at Boot Logo and even READ BOOT.IMG DIRECTLY FROM YOUR PHONE and AUTOMATICALLY ADAPT THE ROM FOR YOUR PARTITION (/dev/block/mmcblk0p*)
*What do I have to do?
-All you have to do is select the ZIP ROM, choose chipset and options and then click "Port ROM for your device!". The default chipsets installed are taken on online forums, like XDA and 4pda.ru (thanks a lot for those guides), but you can build your own chipset method with a simple text editor!
*How can I build my chipset method?
-The chipset structure is like: e.g.
Then save it as "{THE NAME YOU WANT}.txt" in your SDCard under "MTKTransfROM" named folder (e.g. /storage/sdcard0/MTKTransfROM/mt6589.txt)
*Bugs?
Existing bugs TODO:
-During porting, the UI lags. Don't worry, the app is working. If appears Not Responding error, just wait.
-For now, it's only in English.
*Changelog
**1.2
- Discarded zip4j for problems during extraction, using java.util.zip now
- Fixed Exception on some ROM structures
- Added Exit menu voice if activity doesn't terminate
**1.0
- Initial Release
*Credit
-Kellinwood for his ZipSigner class. Thanks a lot.
Now I need help from you community...
As you can see from Play Store screenshots, it has the "Port boot.img" function. However I'm searching a method to unpack and repack MTK boot.img directly from phone. If someone can help me, I will be the most happy man in the world!
As for now, it's the only thing I need to let this app became perfect!
Google Play Store URL: Click here to be redirected (If it says 1.0, is because it's updating or uploading, I'm writing this post while this app is updating).
P.S. Sorry for my English, I'm Italian.
Click to expand...
Click to collapse
playstore-item not found
what ca i do..??

link not work

Infocus m810/m812 custom recovery, unlock, roms (only m810), tweaks.

Infocus M810/T/U thread. (Also wth interesting things for m812 holders.)
Infocus m810 thread on facebook
Note:
All roms on this page are remade to use with Infocus m810 so don't flash on m812. MULTILANGUAGE
Bootloader unlock (m812/m812):
Custom recovery (m810/m812):
SUT flashable images (SUT Factory tool 3.0.8):
SUT 3.1.4 cracked.
Video tutorial SUT flashing on Android 6
ROMS M812(A/I) VN2/PHX:
Android 5.0.2 m812 OFFICAL sut. (Suitable for m810 too) to be used with SUT
cm13 for m812(a) http://forum.xda-developers.com/showpost.php?p=68355126&postcount=1110
ROMS M810(T/I/U):VNA
25/07/16 CM13 beta 2 (release) http://forum.xda-developers.com/showpost.php?p=67901403&postcount=1074
20/03/16 Android 6 custom ROM (ported from m812 ver 617A firmware)
23/02/16 Android 6 custom ROM (ported from m812 ver 6130 firmware)
27/12/15 Android 5.1.1 (internal version 511C(D updated)) (port from m812 ver 511C firmware)
Official Android Kitkat 4.4.2 (VNA-1640-0-00WW-A02)
Older roms
Older ROMs are designed for recovery installation and need some knowledge:
Before the installing of thiose ROMs you must be common with Adb/fastboot driver and installation. working fastboot.exe and adb.exe here
Im the author of this work. So feel free to ask and report.
All you install from here is on your responsibility.
m810.ROM Android 5.0.2: (October 2015) MULTILANGUAGE.
This ROM is full upgrade, so its able to install over Android 4.4.2 ROMS.
How tot install: Russian installation site
1. Put the zip file to sdcard.
2. Connect phone by USB cable. Press and hold volume down+power buttons
(10s), when phone restarts, release power button after vibrating and keep
holding volume down button until FASTBOOT message appear on screen.
3. Download boot recovery https://yadi.sk/d/v_LrtBVdk8pAj and place in fastboot/adb
folder
4. Run in cmd: fastboot boot tw101_recovery_repack_by_titovich.img
5. When recovery booted, Choose firmware UPDATE502_M810_v1.zip and
install.
In the end you should get this error: apply parsed perms lsetfilecon from
/cache to u_object_r:cache_file:s0 failed operation not supported on transport
endpoint set_metadta: some changes failed.
Ignore it. Its issue of recovery.
6 Besides, ROOT and Xposed for 5.0.X framework preinstall can be copied to
sdacard and installed same time after rom installed from boot recovery.
7. Hold power button 10 sec and reboot.
Enjoy.
5.0.2 DOWNLOAD
m810.ROM Android 5.1.1A 08/10/15 The beta version of Lollipop
5.1.1A
ROM from official 511A m812.
Same install instructions as above
Main changes
-Wifi reception better;
-GPS;
-Added buttons config, e-compass, g-sensor calibrations to display menu .
5.1.1 DOWNLOAD.
XPOSED for 5.1.1 . ROOT
Note Xposed from version 5.0 and 5.1 are different!
To flash via SUT:
ODEXED ROM Android 5.1.1B 11/15 The beta version of Lollipop
5.1.1B from official m812 511B update ROM. |For SUT installer. With
unbricking feature.
- ROM designed for odexed files so it contains resized partition for system
(by titovich). means one you install the partition table will remain - 2.5gb for
system. original system parttion is less 2gb. You will be able to install all
m810 roms but I noticed you.
-not for XPLOSED framework. The ROM is full odexed. So don't try Xposed it
will fail;
-minor changes from my side diff to previous ROM;
-fixes from Infocus to battery life.
bugs: haptics not working for hard buttons (to be fixed)
To be installed via SUT utility SUT 3.0.8: DOWNLOAD
-install SUT (drivers will be installed with SUT);
-download zip with nb0 image. Unzip.
-open nb0 image file in SUT.
-Check "Normal Download" and "Erase data".
-Download ignore warning messages.
-Flash will complete in less than 1 min.
5.1.1B for SUT DOWNLOAD LINK2
EOL

Tweaks and enchantments :
M810 service manual
http://forum.xda-developers.com/showpost.php?p=68520451&postcount=1123
Edit boot logo m81X
http://forum.xda-developers.com/showpost.php?p=68956713&postcount=1163
Other party hears the noise durine the phone call
build.prop file
persist.audio.fluence.voicecall=false
Secret codes:
*#*#4636#*#*, *#*#653837#*#*, *#*#76278#*#* Settings.
Note, never tap "USA Band", otherwise you will need to reflash modem part or firmware to make phone back to work.
*#*#873#*#* Upload service
*#*#225#*#* Calendar
*#*#2324636#*#* , *#*#232#*#*, *#*#23273#*#* ,*#*#233#*#*, *#*#231#*#*, *#*#2324678#*#* CDA
*#*#278#*#* CPUDaemon
*#*#324#*#* DebugCfg
*#*#368#*#* Device manager
*#*#3721#*#*, *#*#6721#*#*, *#*#372#*#*, *#*#672#*#*, *#*#4867#*#* High Temperature Monitor
*#*#744#*#*, *#*#628#*#* Mobile Assistant
*#*#787#*#* PackageUsageTool
*#*#227#*#* Pandora Box
*#*#272#*#* Permission Control
*#*#33546#*#* Permission Detection
*#*#793#*#*, *#*#795795#*#* Power Detective
*#*#795#*#* power Monitor
*#*#277#*#*, *#*#3277#*#* Stability Monitor
*#*#28274663#*#* TeleService
Themes pack for 511B/C:
http://forum.xda-developers.com/showpost.php?p=64725810&postcount=429
Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Noise fix. When party on other side is claiming on noise above your voice.
This is typical issue of dual mic QUALCOMM devices on 5+ Androids. Edit built.prop
persist.audio.fluence.voicecall=true change to false
Enable DIAG port for QXDM (QPST). Rooted.
adb shell
su
setprop persist.sys.usb.config diag,serial,mass_storage,adb
Increase speaker volume
http://forum.xda-developers.com/showpost.php?p=64566136&postcount=330
Sound volume mod working on m810
https://www.youtube.com/watch?feature=player_embedded&v=DOo7sT_JIs8
IMEI, Serial number, MEID, MAC, BT changer. Service tool (m810/m812) DANGEROUS!!!
https://drive.google.com/open?id=0B3Wy4Ok3qGszcmZlMDFCbGdwUjQ

I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.

will Infocus m810 get android 5.1???

there is an ota update for m812 to android 5.1 but i am unable to find the file.

My phone its on the way.Im interesting this thread

sknipas said:
I was trying to follow up this conversation on 4pda but i don't speak russian and google translate does a terrible job.
So a couple of questions:
Is this a multilanguage rom?
Does 2g-3g-4g work?
What about wifi?
Thanks.
Click to expand...
Click to collapse
Yes, its Multilanguage.
2g-3g-4g work

sknipas said:
there is an ota update for m812 to android 5.1 but i am unable to find the file.
Click to expand...
Click to collapse
If you find it, pls share, it can be used for further development.

@ heineken78
Thanks for coming here at XDA
I am daily following your good works at 4PDA and I am actually with Titovich's 5.02 rooted and i feel more than satisfied.
I take the opportunity to send you my grateful Thanks.
I will install the new update and let comment as well. I hope and wish the system repartitioning will not give any issue ( I don't like playing with root partition!!).
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards

good work bro. looking for rom based on 5.1 . following this thread

lolo9393 said:
@ heineken78
Question: Was not possible to make the system file as lean as possible , eg removing apk that are unnecessary or available at Playstore for everybody choice in order to avoid this modification.
Regards
Click to expand...
Click to collapse
Stock reserved place in m810 for system partition is ~1,6 gb. Making firmware less, won't bring any changes, unless repartitioning it to lets say 1,1 gb. This operation needs lot of system knowledge from people who will install it.. And profit of changes will be only 500 mb? is nothing.
m812 has partition of 3 gb, that's huge, but suitable for oxdexed roms.
repartition means- you need to change start sectors of emmc in order to set sizes of system, cache. Everything before those partitions remain the same.

Ok, tweak as promised
http://forum.xda-developers.com/showpost.php?p=63576292&postcount=2

Wow,wonderful news... i will test it,downloading...

Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks

@ heineken78
I've just finished the new Rom install. I followed instructions and had no issue . Rebooted via recovery and installed my stuffs.
-Wifi reception is the same as before and always weaker than my other phones. (minus 8 db)
-GPS IS NOT GETTING ANY FIX. 25 SAT in view and no one fixed.
-New Rom is a HUGE bit of improvement and feel more pleasant and very fast.
-DISPLAY is vibrant and very well set. Automatic mode is perfect also at night reading. good
- Battery leak in stand by is impressively low. less 1% full night. very good
THANKS TO THE TEAM BUILDING FOR THIS REALIZATION.
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
[email protected] said:
Hi Guys!
I would like to ask that ROM by titovich, which languages contains?
Thanks
Click to expand...
Click to collapse
Indonesian/Deutch/ENGLISH/Espanol/Filipino/FRENCH/Portugues/VIET/Russian/chinese/ and 2 symbolic i can't know ....sorry may be Hebreu,

lolo9393 said:
Can we suggest next challenge to make unlock the 3G 900Mhz Euro Band N°8 in a practical way?
I care less about the 4G...
---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------
Click to expand...
Click to collapse
Yes Im trying that.
But for now, "adb reboot ftm" to reboot in ftm mode and enable qualcomm diag driver.
Then change nv's as written here and here. Uz mztool to calculate right entry's.

@heineken78
Thanks dude!
Its an official or unofficial translated ROM?
Im just ask the reason of hope, maybe put into some more languages too.
Im get this phone yesterday, it looks really great, but enter the recovery and fastboot mode its terrible.
Do you know TWRP or CWM recovery for this phone?

ilhi, i tried to disable backlight with .rar file you attached and it does work but i
heineken78 said:
TWEAKS:
1. Disable buttons backlight. (pale blue led shine instead). ROOT needed.
Replace system\lib\hw\lights.msm8974.so to get rid of buttons backlight. Instead, PALE blue led will be on.
Don't forget to backup the original file.
Advanced users can control that API /sys/devices/virtual/input/touch/light_led (with echo 0,1)
There is no any other control to disable or enable it.
XPOSED framework can't do anything too
Click to expand...
Click to collapse
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic

a1dahiya said:
ilhi, i tried to disable backlight with .rar file you attached and it does work but i can't adjust screen brightness in settings. Now its full bright and can't switch it low or automatic
Click to expand...
Click to collapse
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.

what should i do please help me
heineken78 said:
Dude, this is patched driver the from the build on first page. Drivers are different on stock502(titovich) so you may have an issue.
Click to expand...
Click to collapse
What should I do, please help me out
---------- Post added at 08:46 AM ---------- Previous post was at 08:38 AM ----------
a1dahiya said:
What should I do, please help me out
Click to expand...
Click to collapse
What drivers to change or any other change of value .....?
I'm on stock lollipop 5.0.2 rooted
I also tried to replace the patched file with original which I copied before replacing but nothing helped

[TOOL] Tingle - Android patcher

Description
File patcher to enable signature spoofing on Android (especially useful for projects like microG).
Success rate is now near 100%.
Download
Tingle (git version)
NOTE: Currently there isn't yet any release, only the git version.
Credits
@moosd (thanks for Needle)
@MaR-V-iN (thanks for the help)
@AnonVendetta (thanks for testing)
@Aaren11 (thanks for testing)
@ChristianTC (thanks for testing)
@_Kosmas_ (thanks for testing)
XDA:DevDB Information
[TOOL] Tingle - Android patcher, Tool/Utility for all devices (see above for details)
Contributors
ale5000
Source Code: https://github.com/ale5000-git/tingle
Version Information
Status: Testing
Created 2016-08-13
Last Updated 2017-11-04

Reserved

Reserved

@ale5000: I got the patch to work, I had to deodex my system APKs and JARs. Then I applied the patch. Everything works so far.
However, on a friend's LG D415 running 5.1.1 SlimROM, it fails. Phone still boots but MicroG says signature spoofing isn't enabled. Will post a log later.
Edit: I meant to say that my friend is running SlimROM v6.0.1 Marshmallow, not v5.1.1 Lollipop.

I also just tested your patch on my Galaxy Tab 2 7.0 (SM-P3113) running SlimROM 5.1.1. The patch works flawlessly. But I had to deodex it too. My friend's phone is already deodexed, not sure why it didn't work on his device.

AnonVendetta said:
My friend's phone is already deodexed, not sure why it didn't work on his device.
Click to expand...
Click to collapse
If you can, please post the original framework.jar so I can make some tests.

Here is his unmodified framework.jar.

I'm running the latest (7/8/2016) version of XenonHD on my LG G3 D855 for the past few days, and whereas I had no problem using needle to patch the build from a few months ago - this latest update throws an error even when using tingle.
I'm fairly certain I've set everything up correctly - I'm using my laptop at the hospital rather than my regular terminal, but I've installed Python 3, linked it in the PATH environmental variables updated Java RTE and made sure that I have working ADB drivers. Needle runs fine, pulls the framework and modifies it, but encounters an error. (I can post screenshots if necessary)
I've attached my unmodified framework.jar to this post, and any help possible would be most appreciated
The ROM is supposedly deodexed, so I haven't tried that yet, to be honest it isn't something I've ever done before or would know where to start with.
View attachment framework.jar
View attachment framework-res.apk

I have found the problem, I need some time to make some tests and trying to fix it.

In the first option FileNotFounError: [WinError 2]
In the second option comes off as all done but framework.jar modified it has the same MD5 that he framework.jar original
I leave the framework.jar, Thank you very much for your time

I'm stupid, I was going to Settings/Applications and mark all permissions and then I was going to
Settings/Privacy and mark all the permissions that were not marked and these permits are Disable app Wi-Fi usage and Disable app cellular usage, he was removing internet access.
I'm stupid.
Sorry.
The only thing that not works is the weather widget from Cyanogenmod 13, everything else works, synchronization contacts, calendar, Chrome and location for cellular it works.
Thanks for the help.

ChristianTC said:
In the first option FileNotFounError: [WinError 2]
Click to expand...
Click to collapse
What does it say if you run manually this?
Code:
adb devices

adb identifies the device as: 4df785271f4440c7
And for disconnect the device of the USB I have to kill process adb.exe from the Task Manager from Windows.

@ChristianTC: Can you please compress all the content of the folder of the patch with included your adb as you use it and put it here so I can try it directly?

ale5000 said:
@ChristianTC: Can you please compress all the content of the folder of the patch with included your adb as you use it and put it here so I can try it directly?
Click to expand...
Click to collapse
Here it is, I have this folder in C:/adb

@AnonVendetta and @Aaren11
You have both the same issue, the framework.jar you have contains 2 dex and the file to patch is inside the first dex but patching it exceed the limit of 64k methods (limit of a single dex) and so it fails, I have added a workaround in my code to move some methods in the second dex (that isn't full) so now it should work but always do a backup before use the patch to be sure.
Please report back if everything works.

@ChristianTC
- For the first option: I was only searching for system wide adb, it never use adb in the folder of the script; in the latest version it search adb also in the tools folder so place it here (after updating Tingle).
- For the second option: This option was added recently and the modified file was only kept in the temp folder, now it is copied to the output folder.
Please report back if everything works.

Tells me that All done but framework.jar modified It has the same MD5 that he framework.jar original.

ChristianTC said:
Tells me that All done but framework.jar modified It has the same MD5 that he framework.jar original.
Click to expand...
Click to collapse
It is really strange.
Try these steps:
1) Please make sure you have the latest version of Tingle (all files and folders, not just patch.py) by clicking "Clone or download" and then "Download ZIP" in the GitHub page.
2) Make sure to extract it in a user writable folder, like Documents; if you extract it under "C:\Program Files" then the patch may not have write permissions to write the file.
3) The patch read the file inside the input folder but write the final file in the output folder so it never overwrite the original file.
4) In case it still do not work open the command prompt with "Run as administrator" and then run the patch from here (it shouldn't really be needed but as last resort it can be tried).
One of the steps should hopefully fix the problem, please report back what happened.

@ale5000: Cancel my request, I caught my now ex-friend trying to steal from me, so I no longer have an incentive to help him with patching his framework.jar. However, if you would still like to provide a technical explanation as to why the patch didn't succeed, then I'd like to hear it anyway.
Sorry for the wasted time.....

[DEV][TOOL][Linux]Android System Extraction and Repack Tool

Introduction
You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).
The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.
Note : Introduction was taken from here : https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952 by @xpirt so thanks to him
So in order to save myself and others who most port Custom & Stock Roms, i decided to use some part of my time to write this script for easy work done.
What this script does :
It basically Unpack and Repack system.new.dat alongside with file_context.bin convertion which is seen in android 7.0/7.1
ITS USAGE:
NOTE
First Clone the repo.
Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
Run "Xtrakt" from it's location in terminal
Copy "file_contexts.bin" from your Rom to "file_context_zone" folder
Use "f" from menu to convert "file_contexts.bin" to text readable "file_contexts"
Copy : system.new.dat, system.transfer.list & file_contexts to "convert-dat" folder.
Use "i" from menu to unpack, which the output will be name as "rom_system" for modifications of apks & files.
Use "y" from menu to repack, which the complete new "system.new.dat", "system.patch.dat" & "system.transfer.list" will be located at "Finish-new.dat" folder
Done !
EXAMPLE:
Again , Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
In your terminal, type the following to start the script:
Code:
git clone https://github.com/iykequame/Android_System_Extraction_and_Repack_Tool.git
mv android_system_extraction_and_repack_tool ~/Desktop/
cd ~/Desktop/android_system_extraction_and_repack_tool/
./Xtrakt
OR
Code:
Double-click the Xtrakt file and choose "Run in Terminal" if your OS supports it.
##ALERT!!!##
sudo is requested in the script.
How To Get It {Tool]
Clone from one of the below ;
From GITHUB :
Code:
git clone https://github.com/iykequame/Android_System_Extractrion_and_Repack_Tool.git
From BITBUCKET :
Code:
git clone https://[email protected]/zac6ix/android_system_extraction_and_repack_tool.git
Or
Download zip
AFH
GIT-RELEASE
Sources :
Android_System_Extraction_and_Repack_Tool
GITHUB
BITBUCKET
Threads :
sdat2img 1.0 - img2sdat 1.2
For file_context.bin conversion by: Pom Kritsada @ MTK THAI Developers.
Credit to :
@xpirt
@SuperR.
-all xda threads which helped
-Android Matrix Development - here
-Nana Yaa for her time.

hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**

Blackball said:
hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**
Click to expand...
Click to collapse
Sorry for the Late reply !
Directories linking has been fix .
You can go ahead and try again

Thanks for sharing!

Don't work
When i press i ..Don't work.say file missing.but i already put all file..Please help meView attachment 4249470

Doesn't do anything with file_context.bin, doesn't even check if file is there.

oreo supported???

I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.

Black_J said:
I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.
Click to expand...
Click to collapse
I see that this thread is not supported.
Anyways, I observed that the tool works for file_contexts.bin but not for other options.
So , I followed the other link in the thread for individual commands and was successful.

Works perfectly on Android Pie! Have to do some tweaks, PM me if anyone wants to make this work for Android Pie.