Database Info

[Guide] All about Caterpillar B15 (CAT Compal B15)

Code:
[B][COLOR="Red"]I don’t take any responsibility if you brick or damage your
device following any of the steps in this guide.
USE AT YOUR OWN RISK. You may violate your warranty!
By following this guide you agree to this conditions![/COLOR][/B]
Index:
POST #1:
I. How to Root / Backup your CAT B15
II. Enable init.d support (only for rooted devices)
III. Swap Phone Storage with SDCard (only for rooted devices)
IV. Entering the service menu
V. Changing the maximum output volume of the headphone output
VI. Enabling A-GPS and EPO
POST #2:
I. How to flash
II. Legend
III. Firmware links
I. Backup and Root:
Method 1: just for ROOT - Works with all version till now (1.041.0):
I recommend doing a FULL backup before rooting. Check method 2 for backup details!
Update your Android to the latest version
Install Framaroot. For more details see this thread.
Method 2
Prerequisites: Update your phone to the latest version. Download all the tools and drivers for the steps below from here.
1. Only for Windows Vista, 7 and 8: Disable driver signature enforcement (allows you to install the unsigned drivers). This is a very important step. Search google for your windows version!
2. On the phone go to Settings->Developer Options and Enable (put a tick on) USB debugging
3. Connect your phone to the PC and wait until the ADB driver installs automatically. If it fails manually install it from device manager->update driver and select the driver from the “ADB_driver” folder.
Then install the drivers from “MT6577 USB VCOM drivers” folder. Windows will tell you that it cannot verify the publisher of the driver. Select Install this driver software anyway on all the dialogs.
4. Execute MTKdroidTools.exe from “Mtk_Android2.4.3\MtkDroidTools”. The device should be detected in about 20 seconds. If it fails go step 1.
Once the phone is detected (picture 1) select Block Maps. Make a screenshot of the Block Maps screen and click on the Create scatter file button. Save the file in a safe place.
5. Execute Flash_tool.exe from “SP_Flash_Tool_v3.1304.0.119” folder.
In the download tab click on the Scatter-loading button and load the scatter file created with MTKdroidTools. Then go to the Read back tab. Delete all the entries if any are present.
The click the add button, this creates a blank entry. Double click on the blank entry. You will be asked where to save the file and then to enter the Start Address and Length select Read Method to be Read Page Only.
You find out the values from the screenshot you made before. I created a Sizes.txt file to help you out with the formatting – CHECK if the sizes and start addresses are the same for you!!!!!!!
It’s recommended to add all the partitions (making a full backup) but you can just add recovery.img and boot.img
Turn off your phone. Unplug it from the computer. Remove the battery. Press Read Back button. Holding the Volume Up and Power button together plug the cable to the phone and computer. Once you see a progress in the SP Flash Tool you can release the buttons.
You will see a green circle the progress is complete (Recovery and Boot read back will take few seconds, full backup will take around an hour). Unplug your phone. Make an archive of the backed up files (zip/rar/7zip) so that the files don’t get modified by mistake.
6. Power on the phone. Connect to PC. Adb should be enabled.
Execute MTKdroidTools.exe from “Mtk_Android2.4.3\MtkDroidTools” and wait for the phone to be recognized, in the root, backup, recovery tab and click “Recovery and Boot” button. Select the boot.img from previous step, you will be asked to make a CWM recovery automatically – choose NO and select the recovery.img from the previous step. If it asks to install created recovery to phone choose NO. Close the program.
7. Power off the phone. Disconnect the cable and remove the battery.
Execute Flash_tool.exe from “SP_Flash_Tool_v3.1304.0.119” folder. In the download tab click on the Scatter-loading button and load the scatter file created in step 4.
Leave the checkboxes on BOOTIMG and RECOVERY. Double click on them and select the modified boot.img and recovery.img (they are located in Mtk_Android2.4.3\MtkDroidTools\recovery). Press the Download button, when a message appears saying that not all images are not loaded correctly press YES.
Holding the Volume Up button and Power button simultaneously plug the USB cable.
After the green circle appears remove the cable.
8. Power on the phone. Connect to PC, Execute MTKdroidTools.exe from “Mtk_Android2.4.3\MtkDroidTools” and wait for the phone to be recognized, in the root, backup, recovery tab the “SuperUser”, “Build.prop” and “Delete china” buttons should be active. Press the “SuperUser” button. Now your phone is rooted.
9. Repeat step 7 but use the files from step 5 (unmodified boot.img and recovery.img).
NOTES: Doing a backup doesn’t violate your warranty. Having a backup is a must. OTA firmware updates checks if some of the system files are modified (build.prop and others take a look at the update-script for details). No not integrate update of system apps to rom (using Titanium backup or similar). If you cannot update OTA the use the backup from step 5 to restore your original firmware.
II. Enable init.d support (only for rooted devices):
Install init.d toggler from Play Store https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler
Note: If someone managed to get init.d support manually please post the steps so I can add it as an alternative method.
III. Swap Phone Storage with SDCard (only for rooted devices):
1. Make a backup (apps, media, contacts)
2. Do a factory reset
3. Using a root explorer (ES File Browser, Root Explorer or other) go to folder /system/etc
edit vold.fstab:
change:
Code:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
to:
Code:
dev_mount sdcard /storage/sdcard1 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard2 /storage/sdcard0 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
edit vold.fstab.nand
change:
Code:
dev_mount sdcard /storage/sdcard0 auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
to
Code:
dev_mount sdcard /storage/sdcard0 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
WARNING: NEVER remove the SDCARD while the phone is running!!!! Never power on the phone without an SDCARD!!!!
IV. Entering the service menu:
Open the dialer (where you dial phone numbers) and enter:
*#*#3646633#*#*
V. Changing the maximum output volume of the headphone output:
1. Enter the service menu (chapter IV. In this guide)
2. Select the Hardware Testing tab and navigate to Audio -> Headset mode
3. Select Level: Level 6 and change the Max Vol. field to the desired value and press the Set button. I recommend a maximum value of 150 (the absolute maximum is 160).
You can also edit the loudspeaker volume (from LoudSpeaker Mode) or the phone volume (from Normal Mode).
VI. Enabling A-GPS and EPO
A) Easy method: Settings -> Location access click on GPS satellites (the text NOT the ON/Off button).
Enable A-GPS/EPO.|
B) Service menu method: Enter service menu -> Location -> Location Based Service
Here you have the AGPS and EPO tabs – use the enable checkboxes

Please upload your phone backups and post links in this thread:
I. Flashing firmware with SP Flash Tool.
Check chapter I of previous post for tools link.
II. Flashing pretty much the same as step 7 of chapter I in first post. You load the scatter file and then load the files if they are not loaded (double click and pointing to the corresponding file).
I strongly recommend to do a full backup of the phone before flashing! (If you don't already have one)
You need to flash the following files: MBR, EBR1, UBOOT, RECOVERY, SEC_RO, LOGO, ANDROID (they must be ticked and correct files shoud be loaded).
DO NOT FLASH: PRELOADER, DSP_BL.
You don't need CACHE and USRDATA (if it's not your own backup)
II. Legend:
EMEA = Europe, the Middle East and Africa (Region Code)
DS = Dual Sim
SS = Single Sim
III. Firmware download links:
EMEA DS.1.041.0 Unrooted (Factory/Virgin/Stock) Thanks to Wedee (TESTED) :
Original link (zip)
Mirror (I have removed the preloader and dsp_bl but haven't tested this backup):
Zippyshare Part1 (7zip)
Zippyshare Part2 (7zip)
EMEA DS.1.041.0 Rooted from my phone (TESTED):
Zippyshare PART 1 (7zip)
Zippyshare PART 2 (7zip)

Reserved 2

Reserved 3

friend, if I modify the "service menu" with a HARD RESET, returns as originally?

cangrejon said:
friend, if I modify the "service menu" with a HARD RESET, returns as originally?
Click to expand...
Click to collapse
Sorry I haven't tested that. I don't want to customize my phone from scratch.
It should be restored but I cannot guarantee that! Write the default values somewhere to be sure!

How do i unroot? I do not able to upgrade anymore

Nice one mate! I for one didn't know about the service menu and I found the headphone volume with high-impedance headphones to be a bit lacking.
One thing to add: improve GPS performance: http://www.gizchina.com/2013/07/23/how-to-fix-poor-gps-on-mediatek-phones/
A-GPS and EPO are disabled by default on some phones -_-
Another thing: you can tweak the camera output to "raw" which apparently gets rid of most compression, and the overzealous noise reductio:
Service menu>camera>raw capture mode: capture mode
Service menu>camera>raw type: pure raw
Currently experimenting with this.
EDIT: camera settings are only honored in the debug camera app.

Could somebody upload EMEA dual sim stock recovery to i.e. dropbox or somewhere else? I am not able to upgrade after root anymore. Tried to flash back original boot and recovery and remover supersu. No lucky :crying:

pubbapubba said:
Could somebody upload EMEA dual sim stock recovery to i.e. dropbox or somewhere else? I am not able to upgrade after root anymore. Tried to flash back original boot and recovery and remover supersu. No lucky :crying:
Click to expand...
Click to collapse
pubbapubba you have modified some system files that's why your phone fails the update checksum progress.
Sorry I don't have a phone without root, but you can update to the latest version (1.041.0) from the second post of this thread (just uploaded minutes ago) but it's ROOTED.
Flash ONLY the following files: BOOTIMG, RECOVERY, ANDROID, UBOOT, LOGO, SEC_RO!!!
Citruspers said:
Nice one mate! I for one didn't know about the service menu and I found the headphone volume with high-impedance headphones to be a bit lacking.
Click to expand...
Click to collapse
Citruspers, I will add the GPS and other tweaks when I have time to properly describe all the options

Thanks for the detailed guide!
When I am running the flash_tool two things happen...
1. My "Read Flag" column is a check box radio with N/A beside it. Not like what your screen shot shows.
2. I can add the starting and length for each item, but the last errors out saying "[Warning] Read back address is adjusted to 512 byte alignment. For the last item "bmtpool" (I have manually typed the values and also cut and pasted your text file entries. My scatter file has the exact same start and length as your guide.
Any idea what I am doing wrong?
EDIT: I tried several times and with changing nothing I now have the Read Flag choices and was able to set page only. I am still getting a Warning on the last item, but the values stuck... am now going to perform the backup and see how it goes.
Ahh... the selecting of the scatter file is the difference. If I load the scatter file first I have no Read Flag choices, if I leave it blank I do. The scatter file changes to EMMC and gets rid of the Read Flag choices.
EDIT: Also just realized I did not upgrade the firmware to 1.41 so am doing that now. (My original CATB15 came with 1.41, this is a replacement brand new out of box and it needed to be upgraded. Will see if that makes any difference.
EDIT: I upgraded firmware and ran it anyway. Was able to root the phone following the steps... Thanks for the guide.. Only thing I saw so far is I would not load the scatter file first in step 5.... as this removes the ability to set the Read Flag choices, although they get overwritten when you do load the scatter file in your screenshot as well.

Wedee said:
Thanks for the detailed guide!
When I am running the flash_tool two things happen...
Click to expand...
Click to collapse
Can you upload the backup you made?

CAT B15 Dual-SIM Stock Firmware 1.041.0 NOT ROOTED
Hi everybody. I have just managed to backup my B15.
The phone is still NOT ROOTED , and the firmware version is EMEA_DS.1.041.0 .
As I am new to this forum, I am not allowed to post external links and the file size is beyond the allowed attachment size.
If someone is interested about the files please contact me.

hello friends, sorry for my bad English, I speak Spanish-
1.- thanks friend, because I was able to root my CAT B15 , all ok :fingers-crossed:
2.- I have my original files : BOOT.IMG , RECOVERY.IMG , if I want to put the factory - VERSION ORIGINAL (not root), as would do?
3.- if in the future tells me that an update is normally update or give me error?.
thanks

tedy_lv said:
Hi everybody. I have just managed to backup my B15.
The phone is still NOT ROOTED , and the firmware version is EMEA_DS.1.041.0 .
As I am new to this forum, I am not allowed to post external links and the file size is beyond the allowed attachment size.
If someone is interested about the files please contact me.
Click to expand...
Click to collapse
Please send the link to my e-mail: mexus(at)abv.bg ( (at) = @) or PM me. I recommend uploading it to zippyshare.com (fast download, upload - you may have to archive it and split the archives - maxiumum upload size is 200MB per file)
cangrejon said:
hello friends, sorry for my bad English, I speak Spanish-
1.- thanks friend, because I was able to root my CAT B15 , all ok :fingers-crossed:
2.- I have my original files : BOOT.IMG , RECOVERY.IMG , if I want to put the factory - VERSION ORIGINAL (not root), as would do?
3.- if in the future tells me that an update is normally update or give me error?.
thanks
Click to expand...
Click to collapse
1. Which method. Famaroot or the tested one?
2. If you want to put the factory version you must have a backup of a factory firmware. I'm waiting for factory (as I call them "virgin" firmwares)
3. You SOULD (not 100% guaranteed) be able to update after root IF you don't modify the build.prop, the framework and library files (in system) and the /system/apps folder. You can add files to system but DO NOT replace, modify system files! Do NOT integrate system app ugrades to system. I'll add the full list of files that SHOULD NOT be modified for the OTA updates to work - when I have time!
EDIT: Unrooted firmware added to second post. It's EMEA DS 1.1041.0. Thanks to Wedee. Please confirm if the firmware works (on DUAL SIM phone It may brick Single Sim)

friend all cat b15 is EMEA???? as if my cat b15 is EMEA?
thanks

cangrejon said:
friend all cat b15 is EMEA???? as if my cat b15 is EMEA?
thanks
Click to expand...
Click to collapse
Go to Settings -> About phone and Check the build number:
If it Says EMEA_DS.1.1041.00 Than its EMEA region, Dual SIM and the version is 1.1041.0.
I don't know what are the other regions? Maybe there is an version for the Americas?

mexusbg said:
Please upload your phone backups and post links in this thread:
I. Flashing firmware with SP Flash Tool.
Check chapter I of previous post for tools link.
II. Flashing pretty much the same as step 7 of chapter I in first post. You load the scatter file and then load the files if they are not loaded (double click and pointing to the corresponding file).
I strongly recommend to do a full backup of the phone before flashing! (If you don't already have one)
You need to flash the following files: MBR, EBR1, UBOOT, RECOVERY, SEC_RO, LOGO, ANDROID (they must be ticked and correct files shoud be loaded).
DO NOT FLASH: PRELOADER, DSP_BL.
You don't need CACHE and USRDATA (if it's not your own backup)
II. Legend:
EMEA = Europe, the Middle East and Africa (Region Code)
DS = Dual Sim
SS = Single Sim
III. Firmware download links:
EMEA DS.1.041.0 Unrooted (Factory/Virgin/Stock) Thanks to Wedee (Untested) Should work. Please confirm!:
Original link (zip)
Mirror (I have removed the preloader and dsp_bl but haven't tested this backup):
Zippyshare Part1 (7zip)
Zippyshare Part2 (7zip)
EMEA DS 1.041 Unrooted (Factory/Virgin/Stock) Thanks to tedy_lv (Untested) Should work. Please confirm!:
Original link Zippyshare (rar)
EMEA DS.1.041.0 Rooted from my phone (TESTED):
Zippyshare PART 1 (7zip)
Zippyshare PART 2 (7zip)
Click to expand...
Click to collapse
someone tested ???
thks

Method 1: just for ROOT (UNTESTED) - PLEASE CONFIRM IF IT WORKS:
I recommend doing a FULL backup before rooting. Check method 2 for backup details!
Install Framaroot. For more details see this thread.
Click to expand...
Click to collapse
Confirmed working for the EU Dualsim version. Installed the APK, chose SuperSU and Boromir method. Rebooted and got root.

Citruspers said:
Confirmed working for the EU Dualsim version. Installed the APK, chose SuperSU and Boromir method. Rebooted and got root.
Click to expand...
Click to collapse
Thank you! Have you check it with root checker from play store?

[GUIDE] Videocon A55 HD Rooting and Recovery related stuff

Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.

Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries

nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...

done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.

nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...

Latest V-Store attached
Attached

nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..

update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?

Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.

nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done

Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,

nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy

How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589

nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...

Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.

For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk

Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:

Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk

Any new updates from Videocon for our A55HD?

File not found
File not found bro

[Recovery][CWM] Custom Recovery for Galaxy Trend S7392

Hello Everybody,
Presenting first custom recovery for Samsung Galaxy Trend S7392. Its a CWM based recovery v6.0.1.5. The package is a ODIN flashable package.
Please try it out and let me know if any issues.
DISCLAIMER : I am not responsible if this bricks your device, or you void your warranty. Try it on your own.
Steps to flash:
1. Download the attachment.
2. Extract it. You will get a .tar.md5 package
3. Start your device into ODIN mode by pressing VolDown + HOME + POWER button on your Galaxy Trend S7392.
4. Run ODIN and connect your device to your PC using USB cable.
5. Browse for the .tar.md5 file from "PDA" section. Select the recently extracted .tar.md5 package.
6. Flash it.

Cant Mount /sdcard/

pratyush369 said:
Cant Mount /sdcard/
Click to expand...
Click to collapse
Lets discuss all that on https://github.com/trivalent/dev/issues, so as not to clutter xda and threads.

Can this mount internal sdcard?

7alvi said:
Can this mount internal sdcard?
Click to expand...
Click to collapse
I haven't checked full functionality apart from Backup, Restore and ZIP installations (from sideload and external sd card). These functions are working well.
It would be very nice if you or someone else can help in making this recovery bug free.

trivalent said:
I haven't checked full functionality apart from Backup, Restore and ZIP installations (from sideload and external sd card). These functions are working well.
It would be very nice if you or someone else can help in making this recovery bug free.
Click to expand...
Click to collapse
Tried ZIp installation,Working great..But factory reset was a trouble.

androidvillage said:
Tried ZIp installation,Working great..But factory reset was a trouble.
Click to expand...
Click to collapse
Agree, but didn't get time to improve over it. Hope to start it soon... Meanwhile, you are free to fork and modify the code as per your requirement. Please update if you get it working fine.

@trivalent the main problem I think is the reset time, once it took 1 hour for. We now have custom ROMs for our device, so wipe data is now more impotent. Try to fix this when you'll got time

@sdeepb
hi buddy
The supersuser 1.65 by jaspreet can be root this device?
i saw in this threadhttp://forum.xda-developers.com/showthread.php?t=2700318
i ll root my kid device its a dual 7392l brasilian variant
best regard, MJ

trivalent said:
Hello Everybody,
Presenting first custom recovery for Samsung Galaxy Trend S7392. Its a CWM based recovery v6.0.1.5. The package is a ODIN flashable package.
Please try it out and let me know if any issues.
DISCLAIMER : I am not responsible if this bricks your device, or you void your warranty. Try it on your own.
Steps to flash:
1. Download the attachment.
2. Extract it. You will get a .tar.md5 package
3. Start your device into ODIN mode by pressing VolDown + HOME + POWER button on your Galaxy Trend S7392.
4. Run ODIN and connect your device to your PC using USB cable.
5. Browse for the .tar.md5 file from "PDA" section. Select the recently extracted .tar.md5 package.
6. Flash it.
Click to expand...
Click to collapse
I need your help i want to compile cm12 for this device . Can you create device tree when you are free

Drain fast please solving my problem
Sent from my GT-S7392 using XDA Free mobile app

[root] Wiko Fever [MT6753]

(Rooting guide at post #5 http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://forum.xda-developers.com/showpost.php?p=63939728&postcount=7)
Hi,
The new flagship from Wiko, the Wiko Fever, it's a great device. :good:
Here my research with it:
- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:
- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***
- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:
You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!

..

Hi,
This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481
Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428
Then the same firmware and rooting procedure will be shareable between both!
Here a great guide for Wiko Fever & Clones:
http://forum.xda-developers.com/android/general/guide-clones-t3421539

Hi,
Here the scatter file for Wiko Fever Lollipop 5.1.
Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).

Rooting GUIDE
Hi,
Good news: Rooting is done! :victory:
Here is the guide for rooting your Wiko Fever:
Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.
1) Unlock bootloader:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Install custom Recovery:
2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://forum.xda-developers.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://forum.xda-developers.com/showpost.php?p=67531723&postcount=217)
2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.
3) Rooting:
3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3.2) Boot in the CWM with “Vol+” and “Power” buttons.
3.3) Install ZIP from external-sd card.
3.4) Reboot and don’t select “fix root”, only “Yes”.
3.5) After boot, start SuperSU and configure it. Root done!
4) Xposed install:
4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://forum.xda-developers.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).
4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).
4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).
4.4) Reboot. The Xposed framework is running.
Enjoy!
Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:
Thank you to all developers & supporters! :highfive:

ChangeLog:
- Beta 3: Fixed ADB shell with root uid.
- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!
Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.​
- Beta 1: Don't use this version, has a bug with SELinux contexts!
- Alpha(1,2,3): Pre-releases.

List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:
- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ
- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ
- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G
In case you need it!
List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):
If you have rooted your device, you can upgrade using these ROMs...
- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP
Probably you want to use these versions!

Hi,
God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!
So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.

this device can support cm12-cm13?

djsolidsnake86 said:
this device can support cm12-cm13?
Click to expand...
Click to collapse
I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!

Verify that the bootloader is unlocked
Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.
manos78 said:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
Click to expand...
Click to collapse
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Thanks again!

hi guys, i followed the guide and all worked also with the last update

cippaciong said:
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Click to expand...
Click to collapse
After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.

Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/

manos78 said:
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Click to expand...
Click to collapse
Unlocked
You have been really helpful, thank you!

oile said:
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
Click to expand...
Click to collapse
Hi,
I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.
Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.
Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:

Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)

oile said:
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
Click to expand...
Click to collapse
In stock Fever ROM:
/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)
Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).
Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).

oile said:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
Click to expand...
Click to collapse
I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.

cippaciong said:
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
Click to expand...
Click to collapse
Hi,
Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.
When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).
For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!

Root with this Upadte_Kinguser.zip modded and get some extras!

Hi!
<<<<<<<The END of low storage>>>>>
I test it in L11 with B370 kit kat factory ROM. From 0.
!!!!Attencion!!!! 3G device users, read pinned post, you need to install SuperSU.zip first than this KingUser.zip to root OR WILL FAIL!!!!
In the step when you will install kinguser.zip change for this one, see the default tutorial here: https://www.facebook.com/groups/huawei.g6.development/permalink/578005512358705/
You need a primary external ext4 partition in sd card with the size you think you need for apps.
To create a primary ext4 partition in sd card with the size you want, you can use mini partition tool (for windows OS ).
http://www.partitionwizard.com/free-partition-manager.html
Need bootloader Unlocked:
https://www.facebook.com/groups/huawei.g6.development/permalink/504332286392695/
Need a custom recovery, i use TWRP for my L11, U models use more CWM, you can find it in G6SKnife.
Must have Windows OS to use G6SKnife:
https://www.facebook.com/groups/huawei.g6.development/permalink/577809609044962/
Than i modded this Kinguser flash zip that:
-Roots
-create a working init.d folder where you can store your scripts that will be executed on boot
-it will install busybox apk ( it need it to install some system tools )
- Rashr to change recoverys with the phone ( only need to have the images in sd card )
- It will automatically send all apps to your external ext4 partiton in sd card IF you have one!!!!
How to do it!!!!??????
READ IT CARFULL:
If you already have apps in phone do backup, use the phone default app for that.
Copy this zip to sd card:
UPDATE-Kinguser-3.4.0-Modded.zip
https://mega.nz/#!rhRknYDJ
Key:
!tnT9KAYOOcuSNm9eq7AcW_PHc2p-C4wjvssNI4IHAMU
Turn off and go to recovery ( TWRP or CWM ) by pressing at same time vol + and power.
Do a factory reset.
Go to install and search the UPDATE-Kinguser-3.4.0-Modded.zip and install it. The phone will reboot.
( A) After settings go to KingUser and open it to check if is ok than go back, open busybox, give root permissions, it will take some time seraching for old files than install it!!!!
( you will need this tools )
Reboot, and is done.
If you start from flash is the same process.
Now your apps go all to sd card.
This video show a flash of B370 and the root with this KingUser.zip:
https://youtu.be/CcFdbS20RrY

If anyone try it, please, let your comments!
Thanks

Failure...
Non Root...

Thank you very much persona78 for your continued efforts to help out your fellow G6 users!
I followed your instructions with partial success (see below).
Some notes during this process:
1. To obtain unlock key I had to visit http://www.emui.com/plugin.php?id=unlock&mod=detail The URL you posted does not work anymore and it also seems that the unlocker is only available in Chinese right now, however Google Translate does a good job!
2. To obtain the serial number I dialed *#*#2846579159#*#*, then menu "VeneerInfoQuery", then "OtherQuery", there I found the S/N number and also IMEI (which can also be obtained in settings / about phone)
3. The model I had to enter on the website was "HUAWEI P7 mini", not "HUAWEI G6-L11", corresponding to the text in settings / about phone.
4. I used Linux fastboot to unlock and flash your TWRP2d.img
5. In TWRP I flashed UPDATE-Kinguser-3.4.0-Modded.zip
Root works and the other apps are installed. Busybox installation was successful as well. I did not test with ext4 partition on SD card yet.
Thanks again!

Today I tried the ext4 sdcard feature. It works as expected. Some comments:
1. You do not need a sdcard reader on your PC to change the sdcard partitioning. You can also use the phone itself by connecting via USB and selecting "Mass storage" mode. Then you can use the partitioning tool on the drive (I used gparted on Linux). Note that mass storage mode will also show the "sdcard"/media part of the internal ram as a separate drive but this is not partitionable.
2. Why do you mount both app and app-lib into the same directory? Will there be no name clashes? I would rather suggest you do:
Code:
mount -t ext4 -o rw /dev/block/vold/179:66 /data/sdext4
mkdir -p /data/sdext4/app /data/sdext4/app-lib
mount -o bind /data/sdext4/app /data/app
mount -o bind /data/sdext4/app-kib /data/app-lib
3. In your description of the mod you should mention that it changes the minimum scaling frequency.
4. I suggest you use this Busybox package: https://f-droid.org/repository/browse/?fdfilter=busybox&fdid=ru.meefik.busybox
It is much faster in installation, and 100% free software
Thanks again!