Related
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch CWM Advanced Edition is developed by XDA Recognized Developer Phil3759 now fully supports MediaTek devices . . .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supports Five generations of MediaTek SoC in One-Porting-Tool.
Arm11
Cortex-A9
Cortex-A7
big.LITTLE
Cortex-A53
Video Preview
For full features & functions, refer to Main Thread here . . . :good:
Credits
Phil3759
Michfood
suhas.holla
shoxxy
Last but not least, my Master Shifu Carliv who has taught me how to compile & continuously guiding me to the right direction & also many DEVs that shared & published their findings on the World Wide Web on various subject . . . . . .
Updated Credits - Added support for MTK big.LITTLE & Cortex-A53
Huge Credits to . . .
Russian Master Shifu Javum
Master Shifu Carliv
Huge Thanks to Xpeca1 for confirming all the porting tool features & functions is working correctly on his Cortex-A53 & not forgetting NiksSkersts too . . . :highfive:
This updates has the most beta-tester, never the less, thanks for all their contributions too . . .
XDA:DevDB Information
Easy Magic PhilZ Touch Installer for MediaTek Devices ONLY (Developers ONLY), Tool/Utility for all devices (see above for details)
Contributors
yuweng
Source Code: https://github.com/PhilZ-cwm6/philz_touch_cwm6
Version Information
Status: Stable
Current Stable Version: Final Release 6.59.0
Stable Release Date: 2015-03-09
Created 2014-05-11
Last Updated 2015-04-09
Terms & Conditions of Use
codeworkx said:
DEAR KANGERS
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
Thanks to all contributors!!!
Click to expand...
Click to collapse
As Master Shifu codeworkx says, the same applies here . . .
All i'm asking is for you to give proper credits to me & the DEVs that i mentioned on the porting tool, without them sharing, this porting tool wouldn't have exists !
i have seen many that took my work, got a ported working PhilZ Touch on their MTKs & shared it directly even here on XDA ! while some at other forum threads BUT not a single word mentioning this thread, me or the porting tool or the DEVs that has contributed to this project . . .
Many just make a new thread with the ported PhilZ Touch & shared it with their followers, fooling their followers by not mentioning credits so that their followers thinking that the ported PhilZ Touch is built from source & is their own work, collected all the Thanks & that will make them look cool while some even solicit for Donations !
Anyone can just download this porting tool, run the exe & they will get a ported PhilZ Touch on their MTK, what is so cool about that . . .
Do you know how many hours i have put into this, not mentioned is the time studying & building PhilZ Touch from source, PC hardware upgrading, broadband fee, electricity fee, time to study & building this porting tool exe & i'm sharing this all for FOC & i don't solicit for Donations or Thanks in return, i don't even post my Donate button . . .
If you wanna start a new thread to support specific MTK devices with the ported PhilZ Touch, i have absolutely no problem with that, it will be your responsibility to response & provide support to your followers but pls give proper credits . . .
If you think this porting tool is too complicated & you would wanna start a new thread/ guide/ video or whatever either here or else where, again i have absolutely no problem with that BUT pls pls don't mirror the porting tool. i'm sure you have seen this all the time at XDA here by other DEVs, the logic is very simple, when you mirror the files, there is no way of tracking which version has bugs. Most importantly, i need direct feedback from users & when you mirror the files, your followers will download that version from your link & they complain & feedback to you but you won't be able to fix it so pls put a link direct to this thread so that i can improve on this porting tool.
If you wanna post this porting tool on your blog, website or anything at all, again i have absolutely no problem with that BUT again post a link directly to this thread so that users can always post a bug report here & they will always get the new, bug free porting tool as i will fix it when i receive bug report.
Credits mentioning & redirecting link to original threads won't make you low standard, in fact your followers will be thanking you for sharing with them a great new tool that you found. Credits mentioning & redirecting link to original threads also means that you give respect & honor the original DEVs of the tool, this would also enable feedbacks on new ideas, new features & improvement of that particular tool too.
If you are a company then pls get my permission first or the least you can do is Donate to Phil3759 for a job well done & if you are an end user, you are also encourage to do so too, fyi, i did . . .
Features
Auto mode
- You don't need to know a thing & it'll port a working PhilZ Touch for your MTK & that is why it is called Magic . . .
Manual mode
- Let you choose either to use your boot.img or recovery.img for porting.
- Let you manually choose your device res, MTK fixes, Flip screen/ Flip Touch, different font size & uses all files from your stock recovery when using recovery.img. For boot.img porting, this tool will only use its kernel only. Refer to here for more info . . .
- device resolutions
- flipped screen
UnPack/ RePack mode
- Let you mod whatever you want with option to install it right away to your MTK
Requirement
- Requires Root
- Install adb driver
- Enable USB debugging
- Disable UAC
- Disable driver signature
- Works from Gingerbread to Lollipop but NOT on encrypted data partition on Lollipop but why you enable it back ?
- No need ro.secure=0 to run
recovery.fstab How-to
Preface
As mentioned few times, i don't own all the MTK devices available on the market so a few things might not work on your MTK. So use the UnPack/ RePack mode to edit necessary files typically the init.rc & recovery.fstab.
UnPack other MTK PhilZ Touch by other DEVs & see how they did it.
As mentioned few times, the porting tool now is AIO so go ahead & play with it.
Intro
What is recovery.fstab
The actual require backup partition for MTKs or any android devices are actually ONLY just the boot, cache, data & system partition.
When you encounter any problems such as doesn't boot/ bootloop issues after a new app installation or anything at all, a Wipe Data/ Factory Reset or Restore with ONLY the system & data partition & you'll be able to revert to previous working state in a short while. Thats why its very important to make a backup before modding anything at all !
For bootloop issues with new firmware installation (update.zip) then its best to restore everything. Having said that, if you flash preloader using SP Flash Tool then PhilZ Touch restore would not be able to restore it or for that matter, your device wouldn't even be able to boot at all (brick), thats why it is important to backup your Factory ROM with MTK Droid Root & Tools first.
For latest MTK armv8
Since the latest MTK armv8 is using direct device path, below is possible as i've seen it on msm devices but personally i think it is unnecessary to have those partition backed up as it will take alot of space & typically you only brick the system or data partition but then again, that is entirely up to you on what you wanna backup. Below example is taken from Master Shifu Carliv github, added all various armv8 devices direct device path partition for reference. To find out the actual MTK armv8 partition info on your device, use the command adb shell cat /proc/partinfo & adb shell ls -al /dev/block/platform/mtk-msdc.0/by-name
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type><mnt_flags and options><fs_mgr_flags>
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/nvram /nvram emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/flashinfo /flashinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/expdb /expdb emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/secro /secro ext4 relatime wait,check
/dev/block/platform/mtk-msdc.0/by-name/seccfg /seccfg emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/proinfo /proinfo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/para /para emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/logo /logo emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/tee1 /tee1 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/tee2 /tee2 emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/otp /otp emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/lk /lk emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,noatime wait
/dev/block/platform/mtk-msdc.0/by-name/preload /preload ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 relatime wait,check
/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 relatime wait,check
/devices/mtk-msdc.0/11240000.MSDC1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
To manually make a SP Flash Tool backup of your MTK armv8 Factory ROM then refer to here & you can also use the following empty cache secro userdata since a Factory Reset/ Wipe Data will wipe data partition anyway.
Updates
Refer to here & here for custom partition backup/ restore on armv8 Thanks to Katinatez . . . :good:
Refer to this the only lead shared by BachMinuetInG . . . :good:
Aroma File Manager
It is a known problem that aromafm will not to work properly on flip-screen, this is not a PhilZ Touch problem as it has never been updated for almost a year.
Flip Screen/ Flip Touch/ Font size
It is a known problem that MTK manufacturer uses non-standard design & uses different Flip Screen/ Non-Flip LCD with different combinations of Flip/ Non-Flip Touch Screen on various Portrait & especially Landscape Android devices.
There is absolutely no way that the porting tool could detect whether your MTK's Touch is FlipX or FlipY or SwapXY so i build all possible combinations into the porting tool -> Manual-mode -> Try all combinations one at a time until one that works for your device.
Typical Flip Screen device then choose either Flip Screen Only or Flip Screen FlipX-FlipY. For Landscape devices (tabs), typically is SwapXY FlipY.
As said, i don't own all MTK devices so i donno which font size is suitable for your device so again, you'll need to play around with the different selection. Below are available fonts as demonstrated on my 480x854 res . . .
Bug report <- No support if you don't attach it to your post.
Please always attach recovery.log & log.txt from the porting tool or i'll be giving the wrong advice based on assumption & that might brick your device !
How to obtain recovery log
adb pull /tmp/recovery.log -> Attach to your post
At PhilZ Touch -> Advanced Functions -> Report Error -> Copy log from /sdcard/clockworkmod/philz_recovery.log -> Attach to your post
If you don't see me replying means either the answer is already at this thread so start reading every page, its not like there are 100 over pages, as of 18 March 2015, there are only 14 pages . . .
The 2nd reason you don't see me replying is i donno the answer then head up to PhilZ Touch development thread & get help from Phil3759 directly . . .
Questions & Answers
Q : Your tool doesn't work.
A : Its already explained at the OP, pls read EVERYTHING at Page 1 !
Q : I can't get adb to work on my PC.
A : Then get one of your device forum DEV to look at this porting tool.
Q : I have a MTK model xxx SoC YYY, does your porting tool support it.
A : The title already said it, for all MediaTek Devices ONLY
Q : I have a MTK but i'm afraid the porting tool would brick my device.
A : Then don't use it ! Its for Developers ONLY !
Q : OP said DO NOT USE IT ON LOCKED BOOTLOADER but the link doesn't say much for MTK devices.
A : There isn't any guide to identify locked bootloader on MTKs, generally you'll have to flash the recovery.img to find out whether it bricks ! However, farenheith has confirmed by flashing back the original stock 3e recovery.img & his locked bootloader MTK Motorola boots back !
To check your bootloader
Code:
adb reboot-bootloader [COLOR="Blue"]or[/COLOR] adb reboot bootloader [COLOR="blue"]or[/COLOR] adb reboot fastboot
fastboot getvar all
Code:
(bootloader) unlocked: NO
To unlock it, use below command.
Code:
fastboot oem unlock
Source
As explained BRANDED at the OP, UNBRANDED MTKs are generally MTKs directly from China, have unlock bootloaders.
Updates
MTK armv7/ armv8 LP refer to this workaround, make sure to unlock your bootloader first !
List of supported MTK devices . . .
Installation
Installation How-to
Where is the Downloads . . .
WARNING
Even though wrong installation of custom recovery normally will bricks the recovery only however it is better to be safe than sorry.
PhilZ Touch is packed with many features so typically it will work on MTK devices with above 6Mb recovery partition however you can try your luck.
Tested working perfectly on my legacy MTK device, MT6573 & MT6577.
Make a Factory ROM backup first with MTK Droid Tools. My old guide here.
Install Flashify & make another backup of your current recovery first & also the boot.img too
Extract, double-click PhilZ Setup & follow the on-screen for instructions.
YOUR TOOL DOESN'T WORK . . .
i've seen this at many threads & also mentioned this many times at my other threads, most frequent reply is it doesn't work, you have given nothing at all to figure out what went wrong . . .
Please list out as many info as possible then it'll be easier to trouble-shoot & read EVERYTHING before hands-on, fyi, tested working on XP to Win10 Technical Preview . . .
What OS you are using on the PC & your MTK...
Did you disable UAC & Anti-Virus
Did you execute the porting tool at C: drive if you're using XP else then at your Desktop
Did you try Run as Administrator
Could it be some other software that you installed that interfere with the porting tool then uninstall it
Did you try it on other PC with other version OS or even different USB port
Try uninstall all previous adb driver -> Device Manager -> View -> Show hidden devices -> uninstall all ADB Interface/ Android device -> reboot -> re-install. Refer to screenshot -> View attachment 3018860
Did you try latest google ADB driver while for XP try this one
Known problems on MTK devices
Known problems on MTK devices
E: failed to mount /cache
Mostly older intermediate MediaTek devices such as MT6589, MT6572 that comes with only 6Mb recovery partition, most probably won't work. However, it works on my legacy MT6573, MT6577 because its kernel is much smaller. There has been feedback from fellow xda members that some latter MediaTek devices comes with 7Mb & 8Mb. Latest MT6592 has a recovery partition of more than 8Mb.
PhilZ Touch does not support ubifs
PhilZ Touch does not support MTK Alcatel devices with /custpack partition. Added support at beta version
Haven't identify latest voldmanaged mount points for Internal SD that uses /storage/usbdisk voldmanaged=usbdisk:auto so it won't mount Internal SD on such layouts. Thanks to adhamamar for sharing the solution. :good:
In the past, there has been reports that Touch doesn't work at recovery on some MTK devices, try using different releases of kernels from your device. Recovery is independent so GB, ICS or JB kernel will work provided they are from your device.
Thanks to shoxxy for the tip, flip screen works on PhilZ Touch with added Flip screen flag. However, it has a small glitches that is the screen will flashes & flip upside down when using the virtual keys. Since Touch is fully working either don't use the virtual keys or just disable it permanently. PhilZ Settings -> GUI Preferences -> Toggle Virtual Keys
Updates
Fixed flip screen flickering, Thanks to Teamwin updated flip screen codes . . . :good:
# Even though the MTK SoC is designed by MediaTek but the one that produces it is hundreds if not thousands of factories so some might use other combinations to boot up the recovery. It is a known problem that some MTK doesn't wanna boot up PhilZ Touch the normal way so try Popey900 technique. Standard procedure : Take out the battery, wait a while, put it back, hold Volume Up or Down, don't let go then press the Power button until it boots up PhilZ Touch #
Do not try this on lock bootloader MTK devices as there has been confirmed cases that it will brick it, refer to here for more info.
---------------------------------------
This tool will auto-install Aroma FileManager & it is a known problem on some MTK devices that Aroma FileManager refuses to start & complains about E:Can't make /tmp/update_binary -> Installation aborted . . .
On Flip screen MTK device, Aromafm will always be flipped & the answer is here
Work around - Built-in to porting tool
Use the Auto mode first & it will auto make a backup of your current recovery.
Pull out the USB cable & use the Manual mode, copy recovery.img from BackUp-MTK-Recovery folder to Stock & it will ask you to plug-in the USB to PC.
Now open Stock/recovery/rmdisk/init.rc with Notepad++ & add the line as below & save it.
Plug-in USB cable to PC, press OK, select your device res & it'll auto install it.
Code:
mkdir /emmc
mkdir /system
mkdir /data
mkdir /cache
[COLOR="blue"][B]mkdir /tmp[/B][/COLOR] [COLOR="Red"]<- add this line to init.rc[/COLOR]
mount tmpfs tmpfs /tmp
chown root shell /tmp
chmod 0775 /tmp
Aroma FileManager shall work now.
---------------------------------------
On my friend's old ICS 4.0.4 MT6577 with 480x854 res, ported PhilZ Touch doesn't boot & later i found out its something to do with the kernel not supporting PhilZ res more than 320x480.
Work around - Built-in to porting tool
At Windows Explorer -> Show Hidden Files & Folders -> MTK_PhilZ -> bin -> extract out 240x320_bg.png from res.7z, rename it to stitch.png
Plug-in the USB cable & use the manual mode, select your device res & it will ask whether you have flipped screen.
Copy & paste extracted 240x320 stitch.png to Stock/recovery/rmdisk/res/images folder to replace it & answer the flipped screen question
At PhilZ Settings -> GUI Preferences -> Change Background -> Reset Koush Background
Trouble-shooting
Trouble-shooting the mount USB storage
Huge credits to suhas.holla, the fstab v2 AKA unified fstab has been demystified for MTK devices & mount both sdcard at PhilZ Touch is working perfecty now. . . :laugh:
i don't own every MediaTek devices out there so most probably some will not mount USB storage for both of the storage while at recovery b'cos of different voldmanaged path.
Updates - Built-in to porting tool
Refer to below on how to identify it & correct this problem.
Open a new Notepad & save the below to MTK_PhilZ folder for unpack/ repack of ported PhilZ Touch recovery.img.
MTK_unpack.bat
Code:
@echo off
cd %~dp0
chcp 1251
if (%1)==() (
echo Select image
goto end
)
setlocal enabledelayedexpansion
COLOR 0A
mode con:cols=65 lines=31
bin\sfk166.exe hexfind %1 -pat -bin /88168858/ -case >bin\offset.txt
bin\sfk166.exe hexfind %1 -pat -bin /FFFFFFFF1F8B08/ -case >>bin\offset.txt
bin\sfk166.exe find bin\offset.txt -pat offset>bin\off2.txt
bin\sfk166.exe replace bin\off2.txt -binary /20/0A/ -yes
if exist %~N1 rd /s /q %~N1 >nul
set /A N=0
:loop
FOR /F %%G IN (bin\off2.txt) DO (
if !N!==1 (
set /A ofs1=%%G
set /A N+=1
)
if !N!==3 (
set /A ofs2=%%G
set /A N+=1
)
if !N!==5 (
set /A ofs3=%%G+4
set /A N+=1
)
if `%%G` EQU `offset` (
set /A N+=1
)
)
FOR %%i IN (%1) DO ( set /A boot_size=%%~Zi )
echo.
echo - size of %1 %boot_size% byte
echo - kernel offset - %ofs1%
echo - ram_header offset - %ofs2%
echo - ram_disk offset - %ofs3%
echo.
del bin\offset.txt
del bin\off2.txt
md %~N1
echo - extracting kernel_header...
bin\sfk166.exe partcopy %1 -fromto 0x0 %ofs1% %~N1\kernel_header -yes
echo - extracting kernel...
bin\sfk166.exe partcopy %1 -fromto %ofs1% %ofs2% %~N1\kernel -yes
echo - extracting ram_header...
bin\sfk166.exe partcopy %1 -fromto %ofs2% %ofs3% %~N1\ram_header -yes
echo - extracting ram_disk...
bin\sfk166.exe partcopy %1 -fromto %ofs3% %boot_size% %~N1\ram_disk.gz -yes
echo - unpack ram_disk.gz...
bin\7za.exe -tgzip x -y %~N1\ram_disk.gz -o%~N1 >nul
echo - unpack ram_disk.cpio...
md %~N1\rmdisk
cd %~N1
cd rmdisk
%~dp0bin\cpio.exe -i <../ram_disk
cd ..
cd ..
copy %1 %~N1
echo.
echo - Done ^^!
echo.
pause
:end
MTK_pack.bat
Code:
@echo off
cd %~dp0
chcp 1251
if (%1)==() (
echo Select folder
goto end
)
setlocal enabledelayedexpansion
COLOR 0A
mode con:cols=60 lines=39
set pt=%~N1%~X1
echo %pt%
copy %pt%\ram_header %~N1\new_ram_with_header >nul
cd %pt%
%~dp0bin\chmod og=xr rmdisk
cd rmdisk
echo - pack rmdisk to cpio...
%~dp0bin\find . | %~dp0bin\cpio.exe -o -H newc -F ../new_ram_disk.cpio >nul
move ..\ram_disk ..\ram_disk_old >nul
copy ..\new_ram_disk.cpio ..\ram_disk
echo - pack rmdisk to gzip...
%~dp0bin\gzip -n -f ../ram_disk
echo - add header...
%~dp0bin\dd if=../ram_disk.gz >> ../new_ram_with_header
FOR %%i IN (../ram_disk.gz) DO ( set /A size=%%~Zi )
echo - new ramdisk %size% byte
%~dp0bin\sfk166 hex %size% -digits=8 >../../size.txt
FOR %%i IN (../../size.txt) DO ( set /A size=%%~Zi )
%~dp0bin\sfk166 split 1 ../../size.txt ../../1 >nul
FOR /F %%i IN (../../1.part7) DO (set a1=%%i)
FOR /F %%i IN (../../1.part8) DO (set a2=%%i)
FOR /F %%i IN (../../1.part5) DO (set a3=%%i)
FOR /F %%i IN (../../1.part6) DO (set a4=%%i)
FOR /F %%i IN (../../1.part3) DO (set a5=%%i)
FOR /F %%i IN (../../1.part4) DO (set a6=%%i)
FOR /F %%i IN (../../1.part1) DO (set a7=%%i)
FOR /F %%i IN (../../1.part2) DO (set a8=%%i)
echo %a7%%a8%>size.txt
echo %a5%%a6%>>size.txt
echo %a3%%a4%>>size.txt
echo %a1%%a2%>>size.txt
echo - add new size in header 0x%a1%%a2% 0x%a3%%a4% 0x%a5%%a6% 0x%a7%%a8%
%~dp0bin\sfk166.exe echo %a1%%a2% %a3%%a4% %a5%%a6% %a7%%a8% +hextobin ../../tmp1.dat
%~dp0bin\sfk166.exe partcopy ../../tmp1.dat 0 4 ../new_ram_with_header 4 -yes>nul
echo - make image...
%~dp0bin\mkbootimg.exe --kernel ../kernel --ramdisk ../new_ram_with_header -o ../new_image.img
del size.txt >nul
copy ..\new_image.img %~dp0\new_image.img
move ..\ram_disk_old ..\ram_disk >nul
cd ..
cd ..
del size.txt >nul
del tmp1.dat>nul
del 1.part*>nul
echo.
echo - Done ^^!
echo.
pause
:end
Just Drag&Drop ported PhilZ Touch recovery.img to MTK_unpack.bat to unpack it & Drag&Drop unpack recovery folder to MTK_pack.bat to repack it back. Disable UAC first.
Or you can also download the original Boot/Recovery repack utils for WINDOWS to unpack/ repack the ported PhilZ Touch recovery. Basically it operates exactly the same except for this porting tool, it is using the standalone 7za.exe instead of 7z.exe that requires the 7z.dll to operate.
Huge Credits to Russian Master Shifu Michfood for sharing his unpack/ repack MTK boot/ recovery algorithm or this porting tool would not have exists & you will have do all this on a NIX box . . . :laugh:
recovery.fstab for MT65xx
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
# For MT6577
/devices/platform/mtk-sd.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0:[COLOR="blue"][B][SIZE="4"]6[/SIZE][/B][/COLOR]
/devices/platform/mtk-sd.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
Code:
# For MT65[B]xx[/B]
[COLOR="Blue"]/devices/platform/mtk-msdc.0/mmc_host/mmc0[/COLOR] auto auto defaults voldmanaged=sdcard0:[COLOR="blue"][B][SIZE="4"]6[/SIZE][/B][/COLOR]
[COLOR="blue"]/devices/platform/mtk-msdc.1/mmc_host/mmc1[/COLOR] auto auto defaults voldmanaged=sdcard1:auto
To identify your MTK voldmanaged path for sdcard -> adb shell find /sys -name mmc0. You don't need to include the first path /sys so it should start with /devices
To identify your internal sdcard partition no. -> adb shell cat /proc/dumchar_info & look at fat partition block /dev/block/mmcblk0p6 & update it accordingly . . .
Update it to fstab.${ro.hardware} too.
The correct way to check ${ro.hardware} -> adb shell getprop ro.hardware -> mt6577 then it should be rename to fstab.mt6577
------------------------------------------------
Updates - Built-in to porting tool
Some MTK don't use fat mount points for Internal sdcard then this tool will fail to identify it & ported PhilZ Touch will not boot/ bootloop . . .
Code:
/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0: [COLOR="Red"]<- Empty[/COLOR]
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
Solution - Put a # at the beginning of that line or just delete it & it'll boot . . .
Code:
[B][SIZE="3"][COLOR="Blue"]#[/COLOR][/SIZE][/B]/devices/platform/mtk-msdc.0/mmc_host/mmc0 auto auto defaults voldmanaged=sdcard0: [COLOR="Red"]<- Empty[/COLOR]
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
------------------------------------------------
To identify USB voldmanaged mount points for Internal SD -> adb shell su -c "ls -R" > c:\users\YOUR USER NAME\desktop\usb.txt
Look for anything usb in it & try it at the fstab.${ro.hardware} & also update it to recovery.fstab too. Both must be identical or it will not work.
An example below, confirmed by shoxxy that can be view at PhilZ Touch -> Install Zip but doesn't mount it at mount USB storage.
Code:
/devices/platform/mt_usb/usb1 auto auto defaults voldmanaged=usbdisk:auto
Also look for various example here on voldmanaged for USB storage & hopefully someone will get it working one day.
if yours is a /data/media device then it would not work . . .
Refer to here credits to RD chrmhoffmann
As mentioned many times, i don't own all MTK devices out there so some features might not work. To fix it & to learn more about modding recovery refer to my Master Shifu thread here & here . . . :good:
When everything fails then try your hands on building one yourself with the optional build flags here for your MTK . . .
This is awesome man....
Yeah...Finally a support thread of philz touch for mediatek devices ...Great initiative by master @yuweng for bringing simple tool to install philz touch on many mediatek devices
Sent from my A250 using Tapatalk
Hi there. Does it work with the Jiayu G5S ?
Is there a simple guide?
Gesendet von meinem JY-G5S mit Tapatalk
Bro, everything is already stated clearly at post #1 to 5, make backup x3, double-click PhilZ.exe & follow on-screen instructions, that's the guide . . .
manual porting ?
SIR Thanks a lot for creating the tool :good:
BTW I tried on my mt6577 in both the ways but it says recovery.img is too large and it is aborting
my question is How to do manual porting for this recovery as we did for carliv touch recovery ( i tried to merge the A9,7z with my ramdisk but it didnt worked)
so pls assist me Sir :crying:
Updates - Built-in to porting tool
Temporary work around is to use the same technique at post #3 most bottom . . . When ask whether you have flipped screen, that is the time to delete the files. Binary files at Stock/recovery/rmdisk/sbin as listed below are safe to be deleted to save some space. List below starts with less critical to critical & i have absolutely no idea what will happened in the long run but definitely it'll boots.
Most of them are utilities for formatting the sdcard while at recovery. Try one at a time starting with Item 1, if still it complains about oversize then delete 1+2 , 1+2+3 & so on until it auto-install . . . :fingers-crossed:
Parted
sdparted
fb2png
mount.exfat
adbd
e2fsck & tune2fs
Updates
You can also try tinypng.com the tips from EnerJon to resize all images at Stock\recovery\rmdisk\res\images to a much smaller size that might just be enough for it to boot PhilZ Touch on your MTK . . . :fingers-crossed:
--------------------------------
Refer to updates of the updates here . . . :good:
hi Bro
thanks for sharing this TUT
but, i can't see download ling of Philz.exe
can give me Download Link ?
thanks ...
Little problem
Hi
First, thank you for porting Philz cwm recovery to our mediatek devices.
I have a zte blade q mini rooted with framaroot but when i want to use your tool, it says ro.secure=1 so no way to port recovery for me.
Any idea or workaround ?
Thank you
ladalgigi
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
You have to go on the top of OP, you can see Discussion and Download tab...
Update info . . .
i3ooter said:
but, i can't see download ling of Philz.exe . . . can give me Download Link ?
Click to expand...
Click to collapse
ladalgigi said:
ro.secure=1 so no way to port recovery for me. Any idea or workaround ?
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
You have to go on the top of OP, you can see Discussion and Download tab...
Click to expand...
Click to collapse
i donno why so many cannot see the Downloads, updated info here . . .
For ro.secure=1 solution is also at the same post & since you already gain root, refer to here . . . :good:
My experience is that you'll have to EXIT MTK Droid Tools first then start the PhilZ.exe or both will be conflicting using the adb shell at the same time . . .
Updates
To others facing the same problem & still you cannot make ro.secure=0 then follow the guide here on how to upload your boot.img & let MTK Droid Tools automatically make the boot.img to ro.secure=0 for you . . . :good: You can also let MTK Droid Tools automatically make & install CWM for you first then use PhilZ.exe to updates it to PhilZ Touch . . . :laugh:
WARNING
Be careful, wrong steps & you'll end up with a soft-brick MTK . . . Make a Factory ROM backup first, read & continue reading then only hands on !
Hi yuweng,
I have root shell right.
but the program says I need root shell.
what can I do?
see my attached file
Then i guess you have no choice but to upload your boot.img & make it ro.secure=0 then . . . :laugh: Or try the manual mode if you have your stock recovery.img with you . . . :fingers-crossed:
Hi !
I tried the manual mode an put my recovery.img in the right folder.
But it gets the same error.
How i can make my boot.img to ro.secure=0 ?
Hi all.
Now i have a Boot.img with ro.secure=0 (Thank you to hanuma)
Now i have the next Problem.
After installing, (Congratulation now you have PhilZ.... Boot into recovery? Yes or No)
And he cant't boot into the recovery.
Only Bootlogo.
Phil's CWM, supports MTK for some time now, i got some issues last time i checked (source built)
Can you please check, if the backup / Restore of boot.img / system are done correctly ?
Regards
Popey900 said:
And he cant't boot into the recovery.
Click to expand...
Click to collapse
In the past, users feedback the same for my other porting tool & then they manually installed it & it works . . . Ported recovery.img is at PhilZ folder.
If still it doesn't boot then upload your stock recovery.img here & i'll have a look at it . . . :fingers-crossed:
superdragonpt said:
Can you please check, if the backup / Restore of boot.img / system are done correctly ?
Click to expand...
Click to collapse
Hey, and i though you followed the news back at the CTR thread then you would've know this . . . :laugh:
CWM/ PhilZ Touch never boots on MTK since last year on the release of cm10.2 & cm11 b'cos we are not using fstab v2 . . .
And just got PhilZ Touch fully supported on MTK devices, Phil3759 just a few days ago announces retirement & releases all the close source to the world . . .
Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh MVarious
Latin Paradise(拉丁乐园)(Elephone) on Baidu
P6000 Folder
OTA Updates - direct from elephone
--- both are 404 now ---
12282014 to 31012015
01092015 to 31012015
Other threads and useful sites:
http://forum.xda-developers.com/android/general/elephone-p6000-mtk6732-64-bit-4g-5-2g-t2957425
SP Flash Thread - P6000
4pda thread - translated top post is fairly concise
Check your Mobile Network/Carrier
Please use the other threads/Q&A and the thanks button - to minimise duplicate posts reporting the same issues.
I'd like this thread to be used mainly for bug fixes, tips and tricks. If someone reports a similar problem/fix/bug click the thanks button if you'd like to agree.
Bugs
Android 5.0 'Official' Release
Update Official (V3.3)
Some modifications: #186
Android 5.0 Beta
12-02-15 ROM available on needrom.com
Hardware buttons don't work
Battery doesn't draw charge
Ril related memory leak
No ADB
Android 4.4.4 (V8.4)
Notification light - not breathing when charging
OTG only works with self-powered devices
Battery seems to jump from 100% to ~90% Soon after removing from charger
Screen jumps several pixels (30) on slow scrolling. Android 4.4.4 (V8.3) bugs not present in V8.4Data encryption results in a stalled boot/softbrick
FAQ/Fixes
1. Notification light is not working in V8.4 as it was in V8.3
Try Light Manager from the play store or gravity box (xposed module)
2. Does OTG work?
It seems to work only with a powered USB hub - I've only been able to check a powered external hard-drive which wouldn't connect
3. How do you fix the screen jump issue?
There are several options here:
From @the1024 / zOrgent we have two options 1. Using a chinese tool - and 2. Using a .bat
From elephone we have TpUpgrade.apk (appears to only work with V8.4)
From lidmiloff we have P6000 Bugfixer.apk
4. How do you restore a Stock ROM?
Download a SPFlash ROM from #1; you will need to install MediaTek USB VCOM drivers (if they aren't automatically installed); On the download page select the scatter from the ROM folder; and the page should populate with the various .img's and .bins; if it doesn't then double click on the entry and locate it manually (also useful if you wan to change boot/recovery with SPFlash). Hit download; remove the battery from the phone and connect it to the PC (you can connect the battery again). The connection will be fairly instantaneous (there may be a driver install the first time it's connected); if it doesn't connect then unplug/replug.
More details from @bigrammy found here
5. Battery jump from 100% to 90%.
Haven't really noticed this too much - download an app like Battery Monitor Widget, add widget (Battery monitor widget gauge => Content => Central value => Battery => Battery Current (mA)) which will show you the battery drain/draw and charge until the draw is close to; if not +0mA
6. Is there any touch recovery?
As of now (pre-5.0) there is no touch recovery. The recovery thread on #1 contains various recoveries - most of which boot but none have touch - this seems to be a kernel issue.
Touch recoveries can be found here. These are built for KK.
7. What about Custom ROMs?
Potential Port devices (MT6732/MT6752) and their ROMS
As there are no official sources released; for MT6732 or P6000 then custom ROMs are a no-go for now. Porting ROMs from other devices running on MT6732 (and MT6752); i.e. Ulefone Be Pro for example is theoretically possible but there doesn't appear to be any custom ROMs on these chips that offer anything different than the stock/AOSP(almost) that we have already. As other devices get released possibly running MIUI or ColorOS then Custom ROMs may be possible.
FlymeOS
8. How do you take a screenshot?
Natively pressing Volume down and power together for 1 second will take a screenshot - it may take a while to get used to - if volume mixer appears then they were too slow and need to wait for it to disappear. Over adb/terminal you can make use of screencap and screen record
9. How do you back up EVERYTHING(except preloader)?
In SPFlash Tools => readback from 0x00 to 0x3a3e000000
This is a fairly quick way to make sure you have a copy of all the partitions on the device; it will create a 14GB+ file containing all the partitions. You will need to break this block up (manually for the moment) into it's constituent parts if you want to use it to restore - using a Hex-editor (HxD for example) and a copy of the matching /proc/partinfo file and/or scatter.txt
The essential partitions to backup for a fully running device are - boot, (recovery), system, (cache) and data which can all be backed up using a custom recovery. The one other partition needed is nvram - this can be backed up with SPFlash (look at /proc/partinfo) or with dd commands. The nvram partition will only be needed to be restored if you Format All with SPFlash. If you don't have a backup you can restore/recreate the IMEI files that it contains.
10. How do you backup/restore IMEI?
Several options here:
1. MTKDroid
2. Backup NVFLASH partition via readback in SPFlash Tools (look at the scatter.txt) to restore you need to modify the scatter.txt to give the nvflash a file_name: and change it from is_Download: false to is_Download: true
3. From elephone there's a IMEI coding tool
4. Keep a copy of the /data/nvram folder
5. Create new imei files to add to nvram folder/partition with imei.exe
6. Chamelephon app from the play store
7. MTK Engineering Mode
11. Adb access with 5.0 Beta ROMs
1. Use KingoRoot
2. Add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
12. Any Stock Camera fixes?
For KK-4.4.4 from @z0rgent at 4pda
FAQ/Fixes Continued
Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below
5.0 Modifications #186Android 5.0 Beta1 Beta2 Beta3
To gain adb access
Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
Linux: ~/.android/adb_usb.ini
Windows: C:/Users/${Username}/.android/adb_usb.iniKingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.
Root
For root install SuperSU v2.11+
Confirmation
Custom Recovery
Recovery from @carliv - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).
Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)
This recovery seems to only work when the Lollipop Beta ROM is installed.
Gapps
64-bit gapps made for the Nexus 9.
My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.
Mirrored copy of the version I'm using.
(OP's thread has updated them and removed the previous version)
Busybox
64-bit busybox installation
Removing encrypted data (temporarily)
In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19
This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img
Android 5.0 Beta Breakdown
Screenshots to come later.
Entering LKVOL UP and POWER (this no longer enters recovery)
From lk menu: entering fastboot mode and normal boot works.
Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything differentCharging batteryFlashing a custom recovery should allow you some way to charge the batteryI haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. ConfirmedRIL Memory leakThere seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode
I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane modeIMEIIMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.Antutu Scores64-bit Antutu Scores are around 28000
32-bit Scores are around 27000
Data-encrypted 4.4.4 Antutu scores are also around 28000SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5ROM is not rooted; does not have gapps installed and data is encrypted.
TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).
Android L kernel config
Annotated /system/build.prop
Stripped top of build.prop (build properties) due to size
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK2.MP13.V1.27
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/k01q_e/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196608
wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp #### adding ,massstorage to this gives an additional USB option but it apears to still mount as a media device (MTP) adding ,mass_storage will let you mount the microsd card
# USB BICR function
ro.sys.usb.bicr=no #### changing to yes will allow you to mount /system/mobile_toolkit/iAmCdRom.iso to PC via USB ####
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.4
ro.com.google.clientidbase=alps-k01q_e-{country}
ro.com.google.clientidbase.ms=alps-k01q_e-{country}
ro.com.google.clientidbase.yt=alps-k01q_e-{country}
ro.com.google.clientidbase.am=alps-k01q_e-{country}
ro.com.google.clientidbase.gmm=alps-k01q_e-{country}
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so #### Charnging this to libart.so appears to have no effect ####
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin fota properties
ro.fota.platform=MTK6732_KK
ro.fota.type=phone
ro.fota.oem=new-bund6732_KK
ro.fota.device=k01q_e
ro.fota.version=eng.jenkins.1422677980
# end fota properties
ro.sf.lcd_density=190
#### Stock value I believe is 320; changing to >190 switches the device to phablet mode; this spoofs the screen size to be 7.73 inches (CPU-Z) enabling tablet apps in the apps store after clearing play store app data ####
qemu.hw.mainkeys=0
#### This enables softkeys ####
Annotated /custom/customprop/custom.prop
ro.product.model=Elephone P6000
ro.product.name=Elephone P6000
ro.product.brand=elephone
ro.product.manufacturer=elephone
ro.bt.name=P6000
ro.wifi.name=P6000
ro.notification.breath=yes #### This seems to not be working with V8.4 ####
ro.build.display.id=ALPS.KK2.MP13.V1.27
ro.internal.build.version=K01Q-E.ELEPHONE.vR83.E4.150109
ro.custom.build.version=Elephone_P6000_V8.4_20150109
ro.fota.device=Elephone_P6000
ro.fota.version=Elephone_P6000_V8.4_20150109202612
MTK Engineering Mode
*#*#3646633#*#* (*#*#ENGMODE#*#*)
What can be done in engineering mode
General non-specific guide
Backlight
Hardware ===> LCM ===> LCM Cycle ===> add a value between 5 and 55 ===> Hit Set.
(On L at least this value will jump to value in the millions/billions; unsure if this has any implications)
Audio
http://forum.xda-developers.com/showthread.php?t=2746861
http://forum.xda-developers.com/showthread.php?t=2248396
GPS
http://www.cnx-software.com/2013/11...ps-lock-on-mediatek-mt65xx-based-smartphones/
Orientation / GSensor
Hardware Testing ===> Sensor ===> Sensor Calibration ===> GSensor Calibration ===> Do Calibration (20% tolerance)
IMEI Restore
Command should be AT +...
Xposed Installer (or WSM Tools)
I've had no problems with any xposed modules.
You will get a warning regarding AliyunOS -
this issue is reported due to the presence of /system/framework/*.jar.jex files.
You can ignore/move/remove these *.jar.jex files without it causing any (noticable) issue.
I haven't decompiled any apps so I don't know if. jex files are used elsewhere within the ROM (in place of .jar),
so can't comment on whether the stock ROM is indeed an Aliyun OS.
I would advise backing them up so that any future OTA can complete 100%.
Any issues identified with xposed modules will be reported here.
Very Helpful and concise
Nice one bro :good:
Subscribed
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
greekfragma said:
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
Click to expand...
Click to collapse
Still doesn't work for me on 8.3.
Nice one, i get my phone in a couple of weeks.
Hello
and Thanks for all your work ! :victory:
Can you add how save and restore imei ?
xenonism said:
Still doesn't work for me on 8.3.
Click to expand...
Click to collapse
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
greekfragma said:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
Click to expand...
Click to collapse
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
xenonism said:
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
Click to expand...
Click to collapse
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again. There must be something messed up in your device. I really believe the config is independent of ROM. The secret is very simple, you must start with new version letter and at offset 184 set correct checksum. How to calculate checksum:
//cal checksum
byte checksum;
for(i=0; i<chip_cfg_len; i++) {
checksum += file_config;
}
file_config[chip_cfg_len] = (~checksum) + 1;
Where chip_cfg_len = 184
Then write the checksum and write 0x01 at offset 185.
I believe you already know where are the theshsold values - at offset 16 and 17.
If you wish, I could send you my hand crafted config, which I was an inspiration for my apk.
Good luck
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
I have a fully functionalV8.3_20141228 ROM running and carliv's CWM from the 7th of February installed. The phone offers me the OTA update and it downloads a ~23 MB update. When I agree to install it, the phone reboots to CWM and the update fails with the following messages:
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can't mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Click to expand...
Click to collapse
If I try to install the same update with ROM Manager, it also fails in CWM with the following message:
-- Installing: [FILENAME SHOWS HERE]
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
But when I reboot the phone, I get the "Android is upgrading...] Screen, saying it's optimizing 124 apps. I believe no actual update takes place, though.
And here's what I'd consider the relevant portion of the recovery.log file:
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Click to expand...
Click to collapse
If I try to install the full 20150109 ROM with ROM Manager, it also fails in CWM, without displaying any meaningful messages in recovery. I also get the "Android is upgrading screen here".
The errors in recovery.log are the same as above.
I guess I could install the full ROM via SP Flash Tool, right?
Also... I have a couple of questions to ask, can I feel free to do it in this thread? Some might be trivial for most.
ludmiloff said:
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again.
Click to expand...
Click to collapse
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img...
Is there any difference in the 4pda.ru ROMs and the ones on needrom.com?
Also found a fix for the backlight in Android L - in engineering mode - not sure if it will do anything useful in 4.4.4 (lower the minimum brightness?).
MTK Engineering Mode => Hardware => LCM => LCM Cycle => value between 5 and 55.
xenonism said:
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
Click to expand...
Click to collapse
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
HypoTurtle said:
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
Click to expand...
Click to collapse
Ok, thanks a lot. I will edit my post right now. The thing is... I haven't used an Android phone in 4 years and I did a lot of my tinkering on my P6000 while working or late at night so.. things got a bit messy.
@HypoTurtle,
My app does not require busybox. It simply run some commands in the shell, though.
In fact It is my first experience with android programming and I just followed some examples found here and there. I also wanted to make a Kotlin based app, but then I decided to continue with plain old java. The app might not a perfect one. Hope it worked for many of elephone owners
---------- Post added at 08:05 AM ---------- Previous post was at 07:41 AM ----------
@xenonism, you should try a clean ROM with sp flash tool. It is a bit tricky, I have tried one from needrom and as the author suggested, I did not check the preloader mark. Then my phone ended totally bricked. The ROM from 4pda worked for me. Today I'm going to reflash it again and investigate why my app does not work on it.
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
xenonism said:
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
Click to expand...
Click to collapse
Same I did just few minutes ago. Won't install updates and will try to make my app working on this ROM.
BTW. Russian method write a very different format to file /process/gmnodexxxxxxx where xxxxxxx is build date. I'm pretty sure if I could change the file with correct checksum and version letter it should work too.
Anyway, my intent was to fix the scroll after I applied the elephone apk. For sure the Russian method with correct version letter and checksum would work too and it is still the best flow now for phones with very stock ROM. I already explained how to calculate the checksum.
HypoTurtle said:
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img..
Click to expand...
Click to collapse
I cant see any CWMLollipop.img there
They only list two recoverys my P6000CWM3.img with no links or credits of course
and carliv's CWM_Modd_2.img again no links or credits
I will be working on the lollipop soon
I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes.
Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (https://www.youtube.com/watch?v=d9ekjWaUHYU)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (https://youtu.be/B0cGRY4vwy0).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,
reserved
Hi,
First post updated with multiboot v1.0 released.
Please watch this video https://www.youtube.com/watch?v=B0cGRY4vwy0 and read carefully first post before using multiboot.
Philippe,
Ok...i'll try
Sent from my SM-A9100 using Tapatalk
Twrp nandroid
how to backup or restore twrp backup?
Thanks for the Multiboot option on Android
:good: Excellent option for trying out ROM without affecting the Usage ROM.
Tried out and it woks.
Thanks a lot Phil for providing this option.
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Is there a way to have my actual storage for every rom?
nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
TW roms dont need gapps
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
buick1356 said:
how to backup or restore twrp backup?
Click to expand...
Click to collapse
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
nalbantoglu.mehmet said:
First, Thank you for multiboot twrp.
Second, i m using rr rom and install multiboot twrp then install second rom angelo but i cant install gapps. Error 12.
Click to expand...
Click to collapse
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
DontBrickYourPhone said:
Is there a way to have my actual storage for every rom?
Click to expand...
Click to collapse
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,
Phil_Suz said:
You can simply copy all the ROM folder (internal card/multiboot/roms) with your PC on another drive.
Maybe a next version will include nandroid backup for those without computer.
I did not notice any trouble installing 6.0 gapps (pico) with AngeloA7 rom.
Inside a multibooted rom, I already mentionned it on first post : If you want to access your real internal sdcard, look at /multiboot/intsdcard ( need a file explorer with root permission I guess)
Inside TWRP, when set to a ROM, your real storage is accessible in /sdcard2.
Philippe,
Click to expand...
Click to collapse
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?
DontBrickYourPhone said:
Thanks I noticed but I was wondering if I can have my data on that Rom as well, or is that not possible since they get sepereated?
Click to expand...
Click to collapse
Unfortunately no, I don't think that it could be possible with the way I separated the roms.
Philippe,
Backup and restore
Please add backup and restore options in multiboot for second ,.....roms
Can u write steps of how to do this ???
Pls
mehal123 said:
Can u write steps of how to do this ???
Pls
Click to expand...
Click to collapse
Please view the video post for the same purpose. if you still have a clarification, I will be glad to support.
well I've notice after adding ROM internal storage is just 8GB ,well is this default for TWRP? or there is option to choose exact space taken by each ROM?
check picture:
HTML:
https://ibb.co/inAtW5
Phil_Suz said:
Hi all,
Here you will find modded TWRP recovery file with multiboot feature for Galaxy Note 3 Exynos (ha3g).
With it, you can have multiple ROMs on your device, test new roms without touching your principal rom, etc...
The method used is based on kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827) with a lot of adaptations to make it work on our device (different kernel patches and usersapce program).
Generic demo of booting multiple roms from internal and external storages (
)
Here is a simple video to show basically how to create and install a ROM. It shows also how to upgrade the rom with another zip after installation (
).
Very important recommendations before using multiboot :
BACKUP all your data first !
Please watch and follow video.
Use only if you have at least 5.5G available on your internal sdcard.
Installation :
Download here : https://www.androidfilehost.com/?fid=673368273298984528
Install zip in recovery mode
Informations :
- Your principal ROM is not affected at all by ROMS installed with multiboot
- Each ROM created sit in a subdirectory of your card : (Internal Storage)/multiboot/roms/NAME_OF_ROM
# ls -al /data/media/0/multiboot/roms/
drwxrwxrwx 2 root root 4096 Sep 8 03:32 Angelo-A7
drwxrwxrwx 2 root root 4096 Sep 9 00:10 DILSHAD-V10UX
drwxrwxrwx 2 root root 4096 Sep 8 02:05 Lineage14.1
drwxrwxrwx 2 root root 4096 Sep 8 03:33 RR-N-v5.8.4
drwxrwxrwx 2 root root 4096 Sep 8 02:21 aicp_ha3g_n-12.1
- Each ROM directory contains 5 image files (boot, system, data, cache and modem) with fixed size for the moment
# ls -al /data/media/0/multiboot/roms/Lineage14.1
-rw------- 1 root root 20971520 Sep 6 19:45 mmcblk0p13_modem.img
-rw------- 1 root root 329252864 Sep 8 21:10 mmcblk0p19_cache.img
-rw------- 1 root root 2554331136 Sep 7 05:59 mmcblk0p20_system.img
-rw------- 1 root root 3221225472 Sep 8 21:10 mmcblk0p21_data.img
-rw------- 1 root root 8388608 Sep 6 20:13 mmcblk0p9_boot.img
- Image files system, data and cache are sparsed so dont necessarely take all their size
# du -sh /data/media/0/multiboot/roms/Lineage14.1/
1.4G /data/media/0/multiboot/roms/Lineage14.1/
- Because android installation method with system.new.dat failed on external sdcard with vfat FS, I disabled option to install ROMs on external sdcard.
- You can copy /sdcard/multiboot/roms/NAME_OF_ROM to external/multiboot/roms/NAME_OF_ROM, il you want to boot ROM from external storage (only sdcard vfat supported). Copy can be done diretly from your PC with copy/paste of the folder.
- All kernels tested are working fine, except Aurora kernel which seems to work but takes long time to load (~1 minute). I recommend another kernel if you want to boot quickly.
- If you want to access your real internal sdcard, look at /multiboot/intsdcard
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : https://twrp.me/
jcadduono : TWRP porting developper - https://forum.xda-developers.com/ga...elopment/recovery-official-twrp-ha3g-t3406899
All ROMs developpers
Version Information
Status: Stable
Current Stable Version: V1.0
Stable Release Date: 2017-09-09
Created 2017-09-09
Last Updated 2017-09-09
Philippe,
Click to expand...
Click to collapse
I tried and installed 3 different roms . It is working perfectly.
The minus points which i noted are,
we dont have enough internal space in the secondary roms(We have only 2 gb per rom)
If i restart the phone the original rom will be replaced the secondary roms ( without booting it via twrp)
Principal ROM
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.
notagamer said:
Sorry if I missed it in the OP.
How to get back to the original (primary/principal) rom which is parent to multiboot folder? set rom only shows the newly created roms.
Click to expand...
Click to collapse
Just restart or clear cache it will automatically revert to primary rom.
Can I give a working link to download !?
ROM build is now up links are at the bottom,
This is for the HS_Q6_MB_V1.0 revision board,
ZMA_12_MB_V1.0 revision boards see the last post on thread for a working incomplete modded firmware.
Personally rebuilt stock OS installed on the R11 max china phone firmware with all mods done by myself apart from the optional modified boot.img
------------------------DISCLAIMER------------------------
Flash this Firmware at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware.
______________________________________
R11 MAX DEVICE INFO
______________________________________
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
ROM ispre-rooted with SU & Busy Box binaries which will remain after factory reset.
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
INT RAM: 128KB SDRAM
EXT RAM: 512MB DRAM
NAND: (4GB + 4096MB) [HYNIX] - H9DA4GH4JJAMCR_4EM
Boot Style: NAND BOOT
Size: 0×20000000 [0.500GB]
BlockSize: 2048 SpareSize: 64 BMT blocks: 80
_____________________________________
REMOVED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• SU Binary pre installed to system, will remain even after factory reset.
• BUSY BOX 1.28 binary pre installed to system, will remain even after factory reset.
• Nova Launcher as new stock launcher
• Opera mini browser (fast with inbuilt DL manager
• Google Calander
• Gmail
• Google wallpaper picker
• FOTO gallery 3.3
• Open Camera
• MTK Video Wallpapers
• Vivo Wallpapers
• Bubbles Live Wallpaper
• JRD Music Player
• JRD File Manager
• JRD Calculator
• updated exchange2
• JRD Secure container
• JRD FOTA & services
• JRD plugger
• Gmail
• MTK Sim Engineering mode
• Updated music FX
• CDS info.apk
• AVG mobile antivirus PRO* 365 day subscription free free from me
• JRD video player
• JRD video favourites
• JRD media container
• JRD Facelock
• Mobile Log
• Modem log
• Alcatel one touch manager agaent (wifi data sync)
• VIVO Boot Animation
• VIVO Shutdown Animation
• VIVO Boot Tone
• VIVO Shutdown Tone
• Updated Boot Logo
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build prop edited to display as VIVO R11 max
• Other .prop edits
• Updated to Release Keys (was test keys)
• updated libs for Jrd app support
• updated framework for Jrd app support
• updates -res for Jrd app support
• a few JRD -res and libs interswapped from alactel 4027A 4.4.2 EMMC with 3.4.67 Kernel also for use of some JRD features
• root set to function without the need for Su manager app binaries can run themselves.
• changed format of FAT from yaffs_img to normal_rom in scatter for use of the 37.8mb usb partition to be also used for for system storage aswell,
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
• added mount points to system for better SD card support and to mount as internal device storage when SD card is inserted.
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
•integrated framework2 into /system/framework/ as was completely absent, NOTE you cannot remove framework2 or any of its components you will break the system
Everything added or replaced came from the followimg devices.
•ZTE luna MT6572 EmmC
•Alcatel 4027 MT6572 EmmC
•Alcatel 5050 MT6575 EmmC
•HTC 310 MT6572 EmmC
•Samsung S7 Exynos8890
------------STORAGE CAPACITY--------------
storage free space is as follows without an SD card inserted before and after flash of new firmware
BEFORE
/data 20mb
/system 9.0kb
/usb storage 37.8mb (not usable)
AFTER
/DATA 62.9mb
/SYSTEM 25.2mb
/USB STORAGE 37.8mb (usable)
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
as these R11 max only come with a 512mb NAND chip with OS installed there is only 62.9mb Data storage after flash of my firmware,using the modified boot.img this allows you to use the devices SD card as the devices ROM & internal storage, info on my device with 15GB SD card,
/DATA 12.9GB
/SYSTEM 25.2MB
/USB storage 37.8MB
/internal storage 1.02GB
This has not been implemented into the build due to firmware size when pulling,
If you wish to use the modifed Boot.img and SD card you MUST partition the SD card BEFORE flashing the firmware if you wish to use the boot.img which is OPTIONAL rom will work fine without it,
partition your SD card as follows with 2 partitions
•PRIMARY partition - FAT32
•PRIMARY partition - EXT4
You should name your EXT4 partition that you made as "mmcblk0p2".
To flash with modified boot.img follow steps above for SD card, and steps below for flashing.
NOTE
if you use the boot.img you will need to reconfigure NOVA launchers looks in the Nova settings once flashed everything else is fine
WORKING
• everything is working unless stateded below
NOT WORKING
• VIVO wallpapers (not showing need to rubuild framework-res to set default as vivo)
• FaceLock (due to root installed secure container wont run, unroot and it should)
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
Open SP flash tool, and open the scatter.file and change flash method to download only and click download, plug the device in while switched off and the device will flash,
DO NOT USE "format all + download" unless you have a backup of your firmware and security partition or you WILL lose your imei.
________________________________________
LINKS
________________________________________
SP FLASH TOOL :
https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip
FIRMWARE DOWNLOAD:
https://drive.google.com/file/d/1mK3lnvqSzvtMajyWm1S1YplfQvPlgcgY/view?usp=drivesdk
MODIFIED BOOT IMG :
https://drive.google.com/file/d/1IRwW4SY-mcRfRrFLYw45CpKacmoRRRW3/view?usp=drivesdk
all credits go to Luca Roggero for building this boot .img to allow SD card to be used as system & rom storage.
_______________________________________
☆☆EDIT☆☆
You must change the storage to SD card and "let the system decide" in preferences on initial fieat boot or you will get a soft reboot when installing any app for the first time it can be changed back after if wanted
Also all other MT6572 nand devices that are not an R11 max chinaphone flash only the android file in firmware first with download only to see if will boot (give it 5 or so minutes) and dont forget to take a partition information table backup to change to your addessses in the scatter of this firmware if no boot do a full flash with download only option again allow 5 minutes to boot dont forget to change addresses and lengths also to match your partition info.
Take a firmware backup also, NCK_MTK dongle can obtain the PIT info, backup your firmware and userdata also and has a variety of other usefull finctions such as formatting & network unlocking & imei and baseband backups aswell
Attention all users of R11 max,
New build will be up in a week maximum, Google play is functional, and has been completely rebuilt, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.
New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041
Ti ringrazio
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
metrovinz said:
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
Click to expand...
Click to collapse
?? English please
Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also
I'm seeking ROM for my R11-1 device which is similar to R11 max.
I'm seeking ROM for my R11-1 device which is similar to R11 max.
The big difference between my R11-1 device and R11 max is the partition size for system.img.
R11-1 is 360MiB and R11 max is 310MiB.
I got some info of R11-1, but now it's bricked. I flashed wrong ROM..
Thank you for reading and I'm happy if you could help me.
______________________________________
R11-1 DEVICE INFO
______________________________________
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ df
Filesystem Size Used Free Blksize
/dev 238.2M 128.0K 238.1M 4096
/sys/fs/cgroup 238.2M 12.0K 238.2M 4096
/mnt/secure 238.2M 0.0K 238.2M 4096
/mnt/asec 238.2M 0.0K 238.2M 4096
/mnt/obb 238.2M 0.0K 238.2M 4096
/system 320.0M 235.7M 84.3M 4096
/data 80.5M 68.4M 12.1M 4096
/.cache 7.0M 772.0K 6.2M 4096
/fat 20.0M 2.6M 17.4M 4096
/protect_f 1.5M 784.0K 752.0K 4096
/protect_s 1.5M 780.0K 756.0K 4096
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 17.8M 352.0K 17.5M 4096
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
7 1 18304 loop1
253 0 393216 zram0
31 0 512 mtdblock0
31 1 1024 mtdblock1
31 2 1536 mtdblock2
31 3 1536 mtdblock3
31 4 1536 mtdblock4
31 5 128 mtdblock5
31 6 384 mtdblock6
31 7 6144 mtdblock7
31 8 6144 mtdblock8
31 9 256 mtdblock9
31 10 384 mtdblock10
31 11 1024 mtdblock11
31 12 2048 mtdblock12
31 13 20480 mtdblock13
31 14 368640 mtdblock14
31 15 7168 mtdblock15
31 16 94848 mtdblock16
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/dev/block $ cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "preloader"
mtd1: 00100000 00020000 "pro_info"
mtd2: 00180000 00020000 "nvram"
mtd3: 00180000 00020000 "protect_f"
mtd4: 00180000 00020000 "protect_s"
mtd5: 00020000 00020000 "seccnfg"
mtd6: 00060000 00020000 "uboot"
mtd7: 00600000 00020000 "boot"
mtd8: 00600000 00020000 "recovery"
mtd9: 00040000 00020000 "secstatic"
mtd10: 00060000 00020000 "misc"
mtd11: 00100000 00020000 "logo"
mtd12: 00200000 00020000 "expdb"
mtd13: 01400000 00020000 "fat"
mtd14: 16800000 00020000 "system"
mtd15: 00700000 00020000 "cache"
mtd16: 05ca0000 00020000 "userdata"
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP7.Band1.2.5.V1.3-2018-10-09_12-33
ro.build.version.incremental=eng.daiweiping.1539059404
ro.custom.build.version=DW_MT6580_ZM9_FWVGAJ_CXT_RJ151_P113_R10_hhx_ZHX_FL_V1.0_20181009
ro.build.version.sdk=19
ro.defwidth2=480
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2018年 10月 09日 星期二 12:33:14 CST
ro.build.date.utc=1539059594
ro.build.type=user
ro.build.user=daiweiping
ro.flash=yes
ro.build.host=user
ro.build.tags=test-keys
ro.product.model=R10
ro.product.name=R10
ro.product.device=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.board=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.brand=alps
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl-user 4.4.2 KOT49H eng.daiweiping.1539059404 test-keys
ro.build.fingerprint=alps/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl:4.4.2/KOT49H/1539059404:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.launcher=com.shly.theme.s6
dw.control.2d=true
ro.sversion=8200
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP7.Band1.2.5.V1.3
ro.mediatek.platform=MT6572
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=MAIN2.1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.operator.optr=CUST
ro.kernel.zio=38,108,105,16
persist.sys.timezone = Asia/Dubai
ro.camera.front.sizeindex=0
ro.camera.back.sizeindex=0
persist.sys.sign_3g_4g=3
persist.sys.frontcamera=800W
persist.sys.backcamera=1600W
ro.defwidth=960
ro.defwidth2=960
isWallpaperSlide=true
bluetooth.HostName = X21
persist.sys.resolution=1920x1080
persist.sys.fingerprint2=true
persist.sys.hidenavigation=true
persist.sys.isshowrealrom=1
persist.sys.isshowrealram=1
factory_code=*#66*#
engineering_code=*#*#3646633#*#*
imei_code=*#0623#
hideSwitch_code=*#0011#
isshowUSB=false
ishotseatAllAppsRank=true
ro.product.name=R10
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=mediatek.wlan.module.postfix=_
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Hey mate,
Youve got the R10
In which i dont have one of those unfortunately, when you flashed the wrong firmware did you flash PRELOADER, UBOOT & BOOT ?
if so youve deffo messed it up,
Im assuming you didnt take a firmware backup first either ? If you did flash it back with SP flash tool if you didnt then i wont be able to help you i dont think unless by some miracle they both use the exact same kernel, either way i have 3 R11 firmwares
2 are ubifs NAND firmwares for the R11 max & the 3rd is an ext4 eMMC for R11 im happy to upload the UBOOT, PRELOADER & BOOT files from all 3 to see if you can get some life back into the device as they are all made from the same chinese manufacturer.
If you can get the device to at least turn on to the boot screen then after flash then the files are good you can then flash the ANDROID, CACHE & USRDATA from my firmwares here on xda and it should come back to life as i have tested this on the R11 EMMC i flashed my UBIFS system.img to the device & worked no problem,
system size also does not matter as long as the ANDROID file is not bigger than your system partition so that should also be fine,
You should never ever flash another devices preloader, uboot or boot.img as the kernels are compiled differently on each device in most cases,
If you cant get any power to the device to flash then take the backing off and take all the screws out take the backing off and look for a series of 4 -6 gold circular points.
These are called test points plug the device in and start the flash on pc then touch all the points with your finger you should now hear the VCOM connect to the device and flash the files youve loaded into SP
#edit ive just looked at your partition info you have the exact same layout as the R11 MAX ubifs models i have so ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
[email protected] said:
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
Click to expand...
Click to collapse
Hey mate,
No worries at all,
For future references on your mtk devices it is always advisable to take a firmware backup using SP Flash tool you can do this by entering the readback menu or by using MTK nck dongle there is a free version in which works quite well which outputs the pulled files directly into there segregated partitions eg preloader, uboot, boot, secro,usrdata,system,cache files aswell as generating a scatter ready to be loaded into SP flash tool great program i use it all the time,
Anyhow give me 5-10mins & ill upload both of my variations of the R11 boot preloaders & uboot as youll need to flash them all to get rid of the other ones both have diff kernels as i mentioned so give them both a try and see how you go,
Let me know if they dont work also as i can ask a few people to see if maybe they have one they can pull a backup from.
#edit my google drive isnt working ill upload as soon as it is
Hey mate google drives back up now heres the links for preloader, uboot, & boot
R11 max ubifs ZMA_12_MB
https://drive.google.com/file/d/1kW34rLGyWGcUT04i3ThXGMM703frVHPr/view?usp=drivesdk
R11 max ubifs HS_Q6_MB
https://drive.google.com/file/d/1tTZjnGN5jQQ2lIl_4FmqPtyuoXsH1dJm/view?usp=drivesdk
See how they go
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
[email protected] said:
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
Click to expand...
Click to collapse
Hey mate,
Your device isnt R10 yours is R11 ZMA Variant ive confirmed this by looking at the pics youve provided,
The logo will look like that due to either 2 things the firmware or logo is still on the device,
1 either the logo is to small or to big for the device causing the lines, or 2 the firmware you flashed is using a diff LCD driver,
Give me a bit when i get home from work ill upload a full firmware for the ZMA_12_MB variant for you, its not the best but once ive finished on the R11_HS_Q6_MB firmware ill be doing the ZMA_12_MB after, the firmware ill be uplaoding is somewhat modified however,
Also did you know that there a storage fix available for these R11, all it requires is a modified boot.img which im happy to do now i know the zma12 kernel is your model for sure, & a decent class 10 sd card with an ext4 partition on it, ive already got a modified boot.img for the hsq6 variant i made a 14GB ext4 partition now data is 14GB instead of 20MB lol no lag at all or anything due to the sd being class10
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
[email protected] said:
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
Click to expand...
Click to collapse
Hey mate sorry i couldnt get the firmware up for you last night having troubles with PC being slow reinstalling windows on it now and ill get the FW up for you as soon as its booted up as its all stored on my 2TB external HD
Hey mate wow didnt realise it been 3 days will have the firmware up for you today some time 100% been doing some modifications to it as i didnt realise how crap the OS was still, ive also modified a stock boot.img aswell as a modifed storage boot.img with CM sources and im just about finished making the OS look a bit better, still gonna look bad as it was a quick job but it will be alot better than what it was before until i get around to properly building the firmware for the zma variant,
Ill update this post with the link soon as its uploaded sorry again for the wait mate
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
[email protected] said:
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
Click to expand...
Click to collapse
Hey mate,
Link will be up soon for you firmwares uplaoding to google drive still needs work but ive redone quite a bit considering what it used to look like youll see anyhow, some of the stuff ive done is modded the camera app & gallery app to run on 4.4, modded system to run cyanogenmod trebuchet launcher, redone the settings & dropdown and also built a setupwiz for it aswell which you will see,
I will finish it up after im done with the HS_Q6 variant, if theres anything majorly wrong with calls or anything etc let me know and ill get it sorted,
I cant test the ril as these are 2G network handsets, Australia dosent have 2G network anymore but it should be all good i know what im doing
## EDIT ##
Link for firmware is here,
https://drive.google.com/file/d/1Ix-k9Myjt1Mc9Rs36wQgRHXuQtU58Pwg/view?usp=drivesdk
Theres a readme id strongly suggest to read it before flashing as theyre are some extra files i have added, also the flash layout is very diff from normal MTK firmwares for 6572 as ive modifed most partitions already just never got around to the theming side of things on the zma variants
Anyhow let me know how you go
Hello Matty1993,
Thank you for your great works.
I flashed R11_Max_ZMA_12_MB_1.0_GT18_MT6572_NAND+UBIFS_20190322.
Then when I power on,the boot screen is shown with google logo 'G'.
But after that,it seems like to be freezing.
When I connect my device to my linux pc,my device is recognized as USB device.
[201999.116029] usb 1-4: new high-speed USB device number 7 using ehci-pci
[201999.248871] usb 1-4: New USB device found, idVendor=0bb4, idProduct=0001
[201999.248878] usb 1-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[201999.248883] usb 1-4: Product: MT65xx Android Phone
[201999.248887] usb 1-4: Manufacturer: MediaTek
[201999.248891] usb 1-4: SerialNumber: 0123456789ABCDEF
[201999.249986] usb-storage 1-4:1.0: USB Mass Storage device detected
[201999.254160] scsi host6: usb-storage 1-4:1.0
[202000.252799] scsi 6:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.253292] scsi 6:0:0:1: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.258682] sd 6:0:0:0: Attached scsi generic sg2 type 0
[202000.261076] sd 6:0:0:1: Attached scsi generic sg3 type 0
[202000.262946] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[202000.265932] sd 6:0:0:1: [sdc] Attached SCSI removable disk
OPPO RECOVERY Ver 1.0 seems to be working good!
However there are vertical stripes and flickling a little,I can select menu like wipe data etc.
I took pictures below.
I'm very very happy if your custom_boot_storage_modified_zma_12_mb_1.0.img could work on my device!
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Xiaomi 12 lite 5G
Installation:
1. fastboot devices
2. fastboot flash boot twrp-3.7.0_12-0-taoyao.img
3. if you were using magisk, reflash it now
Source tree: https://github.com/erwinabs/device_xiaomi_taoyao-twrp
Send me a beer: Paypal
Telegram group: https://t.me/hetdahwin
Download: https://sourceforge.net/projects/win-abs/files/taoyao/Recovery/
reserved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Devices Changelogs:
- Initial Build
Knows Bugs:
- Vibrator
Whats Work ?
- Decryption
- Adb
- MTP
- Backup
- Restore
Hello, thank-you for this developpement.
This is an error i receive : (touch screen not working)
Code:
11-20 15:50:34.562 0 0 E ueventd : firmware: could not find firmware for aw8622x_haptic.bin
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /etc/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /odm/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /vendor/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /firmware/image/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /vendor/firmware_mnt/image/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.563 0 0 I ueventd : loading /devices/platform/soc/a84000.i2c/i2c-3/3-005a/firmware/aw8622x_haptic.bin took 0ms
yzena said:
Hello, thank-you for this developpement.
This is an error i receive : (touch screen not working)
Code:
11-20 15:50:34.562 0 0 E ueventd : firmware: could not find firmware for aw8622x_haptic.bin
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /etc/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /odm/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /vendor/firmware/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /firmware/image/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.562 0 0 E ueventd : firmware: attempted /vendor/firmware_mnt/image/aw8622x_haptic.bin, open failed: No such file or directory
11-20 15:50:34.563 0 0 I ueventd : loading /devices/platform/soc/a84000.i2c/i2c-3/3-005a/firmware/aw8622x_haptic.bin took 0ms
Click to expand...
Click to collapse
Test build
- Vibrator
https://we.tl/t-fjVwIKoC4l
Hello, Still not working properly, I will try to find an error code as soon as i can.
yzena said:
Hello, Still not working properly, I will try to find an error code as soon as i can.
Click to expand...
Click to collapse
Impossible move to telegram?, Also send full logcat - TG link deleted
Edit Moderation : Contrary to Forum Rule #5 regarding social media links - TG link deleted - Sib64 - Moderator
awesome! hopefully this will encourage others to create ROMs for 12 Lite. thank you.
twister26 said:
awesome! hopefully this will encourage others to create ROMs for 12 Lite. thank you.
Click to expand...
Click to collapse
You need request device https://forum.xda-developers.com/t/new-device-forum-requests.1660354/page-1260#post-87765015
Erwin Abs said:
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Xiaomi 12 lite 5G
Installation:
1. fastboot boot twrp-3.7.0_12-0-taoyao.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Send me a beer: Paypal
Telegram group: https://t.me/hetdahwin
Download: https://sourceforge.net/projects/win-abs/files/taoyao/Recovery/
Click to expand...
Click to collapse
can you send device trees please ? i need some base to do 12T pro dt
New Build
Changelog:
- Fix Touch issue random users ( MIUI V13.0.5.0.SLIMIXM )
- Updata Prebuilt V13.0.5.0.SLIMIXM
the bug remains with the vibrator, when I add the vibrator touch delay, so I guess I don't add it doesn't really matter either
Download: https://sourceforge.net/projects/win-abs/files/taoyao/Recovery/twrp-3.7.0_12-1-taoyao.img/download
Test Build
Download:
Erwin Abs said:
Test Build TWRP For Miui A13
Download: https://we.tl/t-VuQOMecruB
Click to expand...
Click to collapse
New Build
Changelog:
- Add Support MIUI A13
Download: Sourceforge
1.Does not mount partitions.
2.After an unsuccessful firmware, the touch does not work