[ROM] R11_Max_MT6572_NAND_4.4.2 - Miscellaneous Android Development

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!

Related

[Official] HSG (X5A/X6) & Pandawill G11 rooting/dev thread (SetCPU & Root working!)

[Official] HSG (X5A/X6) & Pandawill G11 rooting/dev thread (SetCPU & Root working!)
Chinese-manufactured devices, with Korean cpu.. The midX5a / midx6 are both Telechips-based tablets. They're very similar to the Augen device, except they have the actual HDMI port, 300M /data, correct /cache size and a 3.5" headphone jack
The Pandawill G11 seems to be a rebranded version of this hardware using the same firmware(s).
Note: There are older versions of this hardware with no HOME/MENU/BACK buttons, running WinCE. These cannot be upgraded to Android as far as we know right now.
TODO / What's not working: (Updated 24/8/2010)
- Add more languages (like Dutch!)
- Cleanup included languages (Georg77cz is working on cz/cs translation.)
- Find out how to increase /data to the full 3.3GB that's available on internal NAND (hexedit LK.ROM?)
- SetCPU (fc's after moving slider) Working! See attachment![/strike]
- Can't seem to enter recovery by hardware buttons Working, connect USB and use Rom Manager to reboot into recovery!
- Unpack tcc_8900mtd files Naobsd figured it out, thanks!
- Unpack system.img Naobsd figured out to patch unyaffs!
- Repack system.img Naobsd released tools for this.
- Unpack boot IMG, figure out base & pagesizes (4096 page size, base 0x40000000)
- Custom recovery - We have Clockworkmod working as of 20-8!
- Can't boot into recovery from ADB - (From firmware #348 this is fixed..)
- Factory defaults (Works in #348 and wipes properly using the recovery reboot.)
What's working: (As of firmware release #348)
- Custom recovery (Clockworkmod)
- Calibration (You must hold the stylus at the spot for some time.)
- Rooted!
- Telechips FWDN firmware recovery (via WinXP/2K)
- Telechips USB host booting method with empty(!) nand
- Rotation with 'RotateD' from market
- YouTube HD (Just push the Evo4G Youtube.apk)
Note there are similar models. Visit the HSG website and note the right side button spacing/placement.
Link: HSG Website
The model this topic is about, has the buttons spaced across the right side.
The other model that is not from HSG appears to be non-available from China sellers right now, or not in production yet for unknown reason. (sensor rumours)
Another third model has popped up, it's basically the same hardware in APAD casing with metal back plate.
I moved this thread over here from Slatedroid since it got filled with non-dev talk, and thier hosting keeps going offline. I hate it when i can't backtrack to my own findings
{
"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"
}
Specs/Facts:
- MIDX6 has on-board rotation sensor, but it's apparently not working in the firmware yet.
- MIDX6 has optional 3G / GPS inside
- MIDX5A is the basic model with no sensor/3G/GPS. (The rest is the same.)
- CPU Runs at 720Mhz stock
- Has HDMI port
- Has a normal 3.5" jack for headphones
- One speaker, and one microphone inside.
- Runs Android 2.1 eclair-update1
- No GPS/3G/Orientation sensor inside
- Linpack score around 4.9 with no mods / clean os.
- Metal top body, plastic bottom
- Mine came with 2x 1300mA battery inside!
- Battery lasts really long, i can run for ~6-7 hours at work with wifi on.
Quick review
I've used the device for about 3 days now with firmware #297, and it's very fast to use & works like a charm. It has a very solid build quality with a metal top on a thick plastic bottom, making it feel like a quality product. Market worked out-of-the-box with no fuss or hacks. Touchscreen is responsive, but resistive. If you want to slide, push down your finger first, then slide (don't hit-and-run or do a driveby with you finger on the screen).
Battery life is pretty damn good. I've been using it for at least 6-7 hours in one go, with wifi while debugging and ADB and such. The screen is nice & bright, and even if it's a resistive screen it works OK. The main reason for an initial slow reaction from the screen, is that the CPU is downclocked to 36Mhz when you are not doing anything. Edit: This is sorted with SetCPU 2.01! After the first wipe/slide it goes up to 720Mhz.(Yes, that's 120 Mhz more than the Augen!)
Note to posters: Please keep this thread clean. If it's not about rooting or dev, do not post it here please. Thank you!
Post reserved for updates:
Root updated (20-11-2010)
Updated One-click root for #348 and lower.
Download here
This also works with the newer revisions of this tablet with g-sensor
Recovery now working! (20-8-2010, requires #348)
See This Topic for working recovery files.
Steps for flashing with FWDN in USB mode (16-08-2010) (Thanks @fun_ & GeorgCZ for testing!)
(more details will follow)
- Figure out your device serial number and /data/softmac. Store it. (easiest to do, is flash same firmware, FWDN shows it)
- Option #1: You are on V7 (@205, #270, #297, #320) ? Use FWDN mode, and just flash it, format entire nand between different versions!
- Option #2: You are on V6 (WINCE) firmware ? Use use the internal switch to set USB host mode. Place tcBoot.rom in fwdnv7 folder
- When going from V6 to V7 firmware, you will need to erase the entire flash with the dropdown box.
- Plug in when asked, the device will boot with the USB boot mode. Then flash your firmware.
- It's almost impossible to kill the device. The CPU will boot in USB host boot mode if you erase the nand completely!
(In)Compatible USB devices (13-08-2010)
- Keyboards
- Mice
- Wifi USB/Keyboard (as long as they are USB HID devices with no drivers)
- CSR Bluetooth: Not working (no driver in kernel)
- UVC webcams: Not working (no driver in kernel)
SAFE MODE boot (12-08-2010)
This is a special mode if you screwed up something and can't get in the OS because of force-closes in an bad-behaving app that you installed..
- Ensure no power is plugged in
- Press the centre of the touchscreen, & keep it pressed.
- Power on the device as normal. Don't let go of the touchscreen..
- You're now in Safe mode! (a message should be in the bottom left corner stating so.)
Exact steps for flashing with FWDN (12-08-2010) (Thanks @fun_!)
- Power off the unit
- Unplug USB
- Plug in the AC adapter
- Firmly touch the touchscreen
- Power on the unit
After a while you'll notice it stays at the boot splash screen, then you can plug in the USB cable and fire up FWDN.
Google maps update failure fix (11-08-2010)
Connect using ADB and issue the following commands:
Code:
adb remount
busybox rm /system/app/Maps.apk
cd /system/bin
sh pm uninstall com.google.android.apps.maps
sync
Now you can install the new Google Maps version from the Market.
(If not, just reboot the device & try again.)
Extract kernel from boot.img (11-08-2010) (Thanks @geoRG77!)
You can extract the contents using split_bootimg.pl (needs linux+perl installation.)
http://android-dls.com/files/linux/split_bootimg.zip
This also works on tcc8900_mtd.img, since boot.img is near the start of this file. Need to DD of some bytes
(Note that system.img and others are also inside this MTD dump, it's for flashing the whole nand area in one go in the FWDN software.)
Modified INF file for ADB driver:
]usb_inf_X5A.zip
How to:
- Enable USB debugging
- Install the driver from my usb_inf_X5A.zip (2k/xp/32 bits)
- Unzip root_setcpu_X5A.zip into C:\rootfiles
- Start a command prompt and do cd /rootfiles, then root.bat
- You should get no errors, and after the reboot, your X5A should be rooted.
- Note, SetCPU does not seem to work properly.
Firmware layout #297 7-10-2010
Here's /proc/mtd output from #297 rom:
Code:
dev: size erasesize name
mtd0: 80000000 00080000 "bootloader"
mtd1: 00a00000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 01400000 00080000 "cache"
mtd5: 13b00000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00a00000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"
mtd9: 00100000 00080000 "tcc"
Firmware layout #348 7-10-2010
Code:
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 12300000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00100000 00080000 "misc"
mtd8: 00100000 00080000 "tcc"
Firmware layout #205 18-10-2010
Code:
mtd0: 80000000 00080000 "bootloader"
mtd1: 00500000 00080000 "boot"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 03200000 00080000 "cache"
mtd5: 12800000 00080000 "userdata"
mtd6: 00100000 00080000 "persist"
mtd7: 00500000 00080000 "recovery"
mtd8: 00100000 00080000 "misc"
Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Firmwares
Below you'll find a fast mirror for the current firmwares:
(Do a Right-click, save as.. these are 7zip compressed, get it at www.7zip.com)
Firmware #205 (0730) - No market, pretty bland rom.
Firmware #297 (0803) - Works stable, has market.
Firmware #348 (0816) - First rom with recovery booting, but no keys work to select options
We don't know how to repack or unpack them yet. LK.rom seems to hold the MTD layout inside. If anyone figures out how to unpack/repack these files, please let us know.
19-8-2010: User fun_ figured out, we need to flash lk.rom as a single file, and then reboot to have new partitions used
Firmware Updating
There are two modes in which you can update the firmware.
The first mode is basic FWDN mode. The second mode with a blank nand is a factory USB host mode boot, that works even if the nand was completely erased by accident, or empty at the production line.
Warning: Each device has a unique serial. Do not select to overwrite it in the 'Tools - Options' menu!!
It is strongly advised to write down your serial after doing a basic FWDN flash, in case of emergency!
Basic FWDN is also outlined in the Chinese document:
http://www.zonko.nl/files/tcc/CBS7001 Android Instructions v1.01.pdf
Use it a basis for upgrading in this mode.
Basic FWDN mode
This is triggered by the following procedure, and the standard way to upgrade these devices:
Tablet side:
- Unplug tablet from the PC!
- Power off the tablet. Insert the power plug (required!)
- Press & hold finger on the touch screen, and then press & hold the powerbutton.
- The tablet powers up, and remains on the splash screen.
PC Side:
- Install the VTC drivers on your PC (tested OK on Win7 & WinXP 32 bit)
- Set up FWDN before plugging in the tablet
- Optional: Browse & add LK.ROM as a single file when coming from another partition layout, flash and reboot the tablet afterwards, then do the steps below. (You can skip this step, if you are staying on the same MTD layout i.e. flashing the same firmware revision you are on.)
- Browse & add the LK.ROM file.
- Browse & add the tcc8900_mtd.img file.
- Ensure no options are selected in the Tools - Options menu or you loose the mac/serial!
- Plug the tablet into USB
- Click the Nand area map and create a FAT partition for the remaining space.
- Yes, thats 'click on the square below the text' where it shows the block See this picture.
- If you're going to a different MTD layout, choose 'low format' in the dropdown.
- Click Start, and patiently wait.
USB Host boot mode
19-8-2010: No longer needed!
Fun_ figured out the LK.ROM holds the partition info. So if you're coming from another layout, simply flash LK.ROM first. The below procedure remains as a service for those that accidently bricked the device.
This mode is triggered when you erase the entire flash by accident, or when you put the switch on the mainboard inside your tablet to the other position.
You will need to add a bootrom to the FWDN folder where the .exe for FWDN resides. You can get that bootrom from here.
In this mode, the tablet will boot when connected by USB to the PC and init the cpu. After that, it can be flashed the same way as above. In this case you'll need to fiddle with the settings under 'Tools - Options' to set back the serial to what it was before the 'accident'.
If you desire, WinCE can be flashed in this way, if you kill the nand using flash_eraseall under Android..
Uninstall Chinese apps (18-08-2010) (thanks to Asure)
Code:
adb pull /system/app/ ./app
adb shell rm /system/app/91pandaspace_v2.3.apk
adb shell rm /system/app/himarket.apk
adb shell rm -r /data/dalvik*
adb shell sync
adb shell reboot
Official Firmware Download Link:
http://www.huashiguang.com/service.html
* * *
naobsd teardown:
http://twitpic.com/2do3a6
* **
I can open up a forum for you at:
Androidtablets.net
For now, it's a thread here
If a couple of you are up for it, that is. XDA is alright for dev talk though.
* * *
I repacked recovery.img earlier before:
http://www.multiupload.com/3N9VPWXS53
I unpacked Asure's boot.img using instructions from here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Then took the Augen Gentouch recovery, unpacked that as well to replace the ramdisk
The stock 297 recovery image is really large (10mb? Augen is 3mb with clockwork) and has a bunch of useless stuff in it.
So Asure, your recovery image didn't boot? I got all excited...
Edit: repacking doesn't work apparently.
I need to get myself one
I tried to repack the recovery.img using all the methods outlined here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
They all produce an image that looks fine in a hex editor at first glance, but fails to boot on a real device (After flashing it with flash_image recovery /sdcard/recovery.img for example)
I'm pretty sure there's a TTL serial port in the device, but i'll need some time to sort that out. I asked Koush for help, perhaps he can see what is wrong with the image.
Root Holding...
I have the model similar to the Apad with the hardware buttons. The Augen root method worked fine and looks to be holding so far, no stability issues or lockups using SetCPU with 120/720 scaling . I can provide some assistance from the "third" model with direction as needed.
My device is actually showing #320. My partition layout is similar to #297.
Latest Firmware update failure
I tried to flash the new firmware from HSG (16-8-2010)
but everytime it failed with this error
[ERROR] The old version(=0x07000002) device can't support 'MTD' fwdn area image.
i followed the same steps when i did the 13-8 update.
Anybody tried to flash it with succes ?
What am i doing wrong this time?
Please read & follow the steps in the second post. Low-format to get the new MTD layout.
Also, please keep this a dev topic. This is not HSG customer support
First, credits to Koush for his amazing recovery, the Android scene would be completely different if it wasn't for you!
Second, i wonder who @google thought it would be a great idea to force a huge download of 4.5GB + apps needed to compile a 13kb mkbootimg.
Anyway, with some files from someone else's kitchen (only 15mb download) i managed to compile mkbootimg with the new --pagesize parameter from Koush.
(This recovery's kernel --base 40000000 and requires --pagesize 1000 to work properly.)
I've updated the second post with the working recovery.
Also the one-click root.bat is back.
Enjoy your weekend!
Recovery is now working thanks to Georg77cz who provided unmissable help with testing this!
Check http://twitter.com/Asure007 for some pics. I'll upload the recovery tomorrow. For now, only confirmed to work on #348 roms! (older roms don't honour adb shell reboot)
So, now that we can do custom roms/updates/zips, does anyone have Dutch strings.xml for Settings.apk and SettingsProvider.apk from a Android 2.1 release ? HSG did not include this language as an option in any of the stuff on the tablet..
Edit: Never mind, i've pulled them off the emulator and added the sections that were missing (HDMI Output selection and such.)
Accessing Flash Mode MID701
I am not sure if you want to track here or in another thread, but I was able to find the right combo to access safe-mode/flashing mode on the 3rd device, MID701 with the #320 firmware.
To access the flashing mode for a MID701 device. After you have prepped your Telechips VTC driver and have FWDN running, do the following in order:
1) Flip the ON/OFF switch to the OFF Position
2) Connect the AC Adapter
3) Connect the USB Cable
4) Press and Hold the Home+Back buttons on the top of the device (both sides of the "rocker" must be depressed)
5) Flip the ON/OFF switch to the ON Position
In a matter of seconds you should get driver/telechips prompts and FWDN will light up. The screen WILL NOT come on in this mode.
After making a few backups and records, I may attempt to install the #348 firmware tomorrow.
I would suggest to ensure you have a working flash to go back to. From tests we did with #320 on HSG x5a the video is not working (white screen). ADB still works and we could flash_image back a #297 kernel(boot.img) into it to get video back & working.
If you really want to try something, try Clockwork Recovery for #320 tablets: http://bit.ly/aA06cY and let me know if it works
I can flash it but it doesn't escape the fact that I can't get to recovery from #320 lol. I will probably wait until the supplier releases the firmware Monday, so I have an absolute recovery path. Will post back with any success.
You can use ADB to get into recovery: adb shell reboot recovery
Or, if you're a windows user, install Droid Explorer, and use the option in the menu.
Or, if you want, install Rom manager from market, or reboot control widget. Plenty of options
Edit: Also, no need to wait for your supplier, i've put #320 here:
http://www.zonko.nl/files/tcc/Haina.android.320.7z
Few new things to report.
- I located a firmware that is #330 from Pandawill that works on my device. The market works, and it appears to have native support for playing xvid files in the gallery which my #320 build could not do, and I am unsure if the #348 builds have the ability.
-It feels a bit snappier than my #320 build.
-The #330 build also responds to the reboot recovery, which results in the Triangle Android update screen we have all seen before.
-Clockwork recovery also works on my device. I can scroll the recovery menu with the "Home" side of the rocker button. Clockwork reports that the back button is enabled, so it should work as well. The problem is the device is programed with the front button as a Sleep button, so it turns the screen on and off at the recovery menu. If I could remap the buttons, I should be in business.
I may dump the MTD image into one of my linux boxes and try to modify the partitioning a bit. Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.
LCD Density
For those who want a bit more screen real estate, you can modify the lcd density in the build.prop. I switched to 161 and it really scales well in some applications like the browser. Other places like the the status bar menus, and some applications, so no honor the new density and will not render scaled. From some translated notes 161, 162, and 180 seem to be the best values for higher density over the default of 240
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 161
adb pull /system/build.prop /directory/to/store/build.prop
edit your build.prop
adb push /directory/to/new/build.prop /system/build.prop
adb reboot
No sleep?
I've got the X5A yesterday and it came loaded with firmware #348. Rooted it last night and it's quite a brilliant little device!
I surfed the net for a bit and left it idle for the entire night last night, and it promptly ate around 40% of the battery. Spare Parts shows that it hasn't been sleeping properly (just like my old Samsung Galaxy) and that Wifi was running the entire time.
I looked on logcat and this line keeps popping up, not sure if it's causing the issue?
V/BatteryService( 937): lwgmUsbOnline
Googled it but nothing seemed to come up...
helfrez said:
Is there an easy way to modify the size of the data partition. The default images only give 256MB for apps, which seems a bit small considering all of the devices have 2/4GB internal memory.
Click to expand...
Click to collapse
As far as i know, the MTD partitioning is done inside LK.ROM.
You can try to change it in a hex editor, and see if that works. I'm not sure if the CRC changes, and it we can even raw hex edit it.. (200+mb for /data is already pretty good..)
Suggested steps:
- Using a hexeditor on lk.rom you can do a search for 'BMPG'
- Around 0x4d350 you should find the mtd table.
- You can see the partition names, and sizes.
- For example, in '#297' LK.ROM, this is at 350Mbytes (00 00 00 D1 00 00 00)
- Try to change to 00 00 00 FF 00 00 00, see what happens
(If this works it's for all TCC related devices, and we can get an even huger /data partition hehehe.)

[DEV][GUIDE][REF] Customize Internal Partition Layout for MTD Devices

See Post #2 for current known stock partition parameters for various devices. Your contributions for missing devices are welcome and appreciated. Cheers!
Introduction
This guide / reference aims to be a complete article on customizing, resizing and/or re-ordering the internal partition layout on most (any?) Android MTD-based device. I have seen many questions around the various forums on how to get more internal data so I thought I'd share my developments. Hopefully this will become a valuable resource for kernel builders/hackers.
The guide is especially valuable (and, in the case of my kernel builds, originally designed for) the Xperia 2011 line, but from what I know it could be applied to nearly any Android device where kernel source/flashing is possible.
I would like to gather stock partition information for various devices and place them into Post #2. If you can at least give me your Partition Info from ATAG (see "Gathering information" section), I can create a reference for all kernel developers. Thank you!
Requirements
Android SDK
Ability to build a kernel (this guide does not teach that)
Ability to flash a kernel (unlocked bootloader, etc)
Bootloader which exposes Partition info via ATAG on startup (see "Gathering information" section)
Device which uses MTD Partition Map (Don't know how to check this, I think most Android devices do anyway)
Warning
As far as I know, following this guide and using precise calculation that you double and triple check before flashing will not result in a hard brick - however I can not guarantee it. Some devices may have "obscure" partition maps or some "protected" sectors for one reason or another, and modifying these *may* result in either a hard-brick (unlikely) or a permanent inability to restore your device to 100% stock (very likely) for warranty and/or DRM purposes. You have been warned. I/we/anyone may not be held accountable for any of these events should they occur, for you are doing this at your own risk and with your own responsibility.
Gathering information
The first thing you'll want to do for the sake of accuracy is to flash to a 100% stock firmware. In the case of Xperia 2011 devices, flash the latest stock FTF for your device.
With the stock firmware now installed, the second thing you will need to do is to flash a custom kernel that is rooted and has busybox installed. In most cases, a CM7/9/10 kernel will do nicely.
Power-off your device. Execute the following command from shell/console, and then press enter:
Code:
adb wait-for-device && adb shell dmesg
After pressing enter, the console will wait at the prompt as intended. Now, power on your device and immediately plug in the USB cable. I assume the ADB drivers are already installed.
Shortly (5-15 seconds) you should see a mass output from the kernel followed by a return to your shell prompt. If you don't, either your kernel or bootloader does not support it. Try a different kernel. If you still don't, then sorry but I think we can't do it for your device.
Scroll right to the top of the dmesg output, you should see something similar to this:
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 2.6.32.9-KRsH ([email protected], Linaro 4.7) (gcc version Linaro 4.6.2 20111004) #8 PREEMPT Thu Oct 25 15:57:27 EST 2012
<4>[ 0.000000] CPU: ARMv7 Processor [511f00f2] revision 2 (ARMv7), cr=10c53c7d
<4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache
<4>[ 0.000000] Machine: zeus
<6>[ 0.000000] Partition (from atag) system -- Offset:2e4 Size:9c4
<6>[ 0.000000] Partition (from atag) userdata -- Offset:ca8 Size:be0
<6>[ 0.000000] Partition (from atag) cache -- Offset:1cb4 Size:32c
<6>[ 0.000000] Partition (from atag) appslog -- Offset:1888 Size:42c
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback
...see those "Partition (from atag)" lines? That's what we need! Copy this information down and move on to the next section.
Additional verification and hidden partitions (optional)
As far as I know, this is only possible with Xperia 2011 devices. If you know of a method for other devices, please let me know.
We can additionally verify the ATAG information and map extra "hidden" partitions such as boot (kernel) by examining the SIN files inside an FTF. I will assume that you know how to use Flashtool already as I won't go into much detail here.
First, we need to enable the development features of Flashtool. In the program folder, open "config.properties" and edit/add the line like so:
Code:
devfeatures=yes
Next, extract your stock FTF bundle with any ol' ZIP extractor, load Flashtool, and select "Tools" > "SIN Editor", and open a particular SIN file that you want to verify/unhide. In this example, we will open system.sin. The "Partition Info" field is what we want. Behold:
Code:
STOCK SIN:
system: 0400000001000080E4020000C4090000
-- --|------||------|
| | | |
type? (elf/yaffs) _/ | | \____ byte-reversed size
| |
unknown ____/ \____________ byte-reversed offset
The second last 8-bytes are the offset and the last 8-bytes are the size. By "byte-reversed" I mean that you read each byte from end to beginning, but not swap the bytes themselves. Thus the size above, reading "C4090000" is actually "000009C4". And as you can see, this matches 100% to our ATAG of 9c4 for system size. Correct sir! Additionally, the offset of "E4020000" > reversed to "000002E4" also matches.
So now, we can open "kernel.sin" and do the same, because we also want to partition "boot" (why not?). In this device (Xperia Play/Xperia Neo L), kernel.sin gives us 03000000220000808002000064000000 which means that the size is 64 and the offset is 280.
Calculations
From the partition info via ATAG, we can now build "stock" mtdparts information to apply to our kernel. Using the example(s) above, we can now build this information:
Code:
system : [email protected]
userdata : [email protected]
cache : [email protected]
appslog : [email protected]
boot : [email protected]
Note the syntax of size@offset. Next, we must convert the hex values to decimal, then multiply by 128 (I do not know if 128 is the same multiplier for all devices, please double check and let me know). This will give us the exact sizes and offsets in kilobytes.
Code:
system : [email protected]
userdata : [email protected]
cache : [email protected]
appslog : [email protected]
boot : [email protected]
Alright, so that is a 100% stock partition map for this device - except we also have the boot (kernel) mapped now too. Here is a (crappy) visual representation of it:
Code:
reserved | boot | /system | /data | appslog | /cache |
first 80MB | 12.5MB | 312.5MB | 380MB | 133.5MB | 101.5MB |
Note: Not to scale :)
You may have noticed that the order we (and ATAG) lists the partitions in does not match the actual order of the partitions. It is quite important to retain the order of the partitions as specified in ATAG, because that's the order they will be mapped in. I.e. system will remain mtdblock0 and cache will remain mtdblock2. Any extra partitions should always go after these defaults.
Formatting for kernel
To specify the mtdparts parameter for the kernel to use is trivial. Doing this will over-ride the ATAG map (from bootloader) and everything in the system - including Recovery - will see your map from the kernel. Search your default config file in your kernel for the value "CONFIG_CMDLINE" and you should find a value like this :
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc"
Using the information we have above about our partition map, we add a new parameter here with "mtdparts=msm_nand:". The syntax is as follows:
Code:
mtdparts=msm_nand:[size]@[offset](name){,[size]@[offset](name)}{...}
Remember that we converted our size and offsets to kilobytes (for better readibility) so we need to specify size unit of k. The new parameter, from our above examples, becomes this:
Code:
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)
Don't forget to retain the order! And so, our full line looks like this:
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)"
NOTE: Depending on your kernel, you may also need to enable the following line in your config:
Code:
CONFIG_MTD_CMDLINE_PARTS=y
And we're all done. If you build your kernel now, you will be able to mount (or at least dd from) the appslog and boot partitions.
Resizing partitions
This is somewhat trivial, the most difficult part is probably over - but this step can be tedious, albeit not very complicated. Anybody with an above average IQ would have already figured this out - we simply change the size of one partition and adjust the offsets of it's following partitions to accommodate for the change. Here is one good example that I use for the MIUI ROM for the Xperia Play and Neo L, compared to the stock examples shown above:
Code:
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)
...and a visual representation of this new map:
Code:
reserved | boot | /system | /data |/cache|
first 80MB | 12.5MB | 280MB | 639MB | 8MB |
Note: Not to scale :)
Hopefully that's enough to make sense. Remember to verify your modified partitions. This can easily be done by adding the size+offset of a partition, giving the offset of the next partition. E.g. in this mod, userdata ends at 1036288 (654848+381440) which matches the offset for the next partition - cache.
Troubleshooting/Recovering from modified partitions
In some cases, your new kernel may not boot. A common issue is that the kernel logo will show, and the device will shortly reboot (kernel bootloop). This can be solved by formatting your partitions with fastboot after flashing the new kernel, usually system and userdata are all that is needed:
Code:
fastboot format system
fastboot format userdata
If you wish to return to a stock partition layout, sometimes flashing a non-modified kernel is not enough. You may get stuck on kernel logo even after formatting system and userdata. In this case, flashing a stock Firmware and setting your phone back to scratch should result in a 100% original device. But if your phone is still bricked, sorry but it's not my fault. You probably did something wrong.
#####
OK, that's the guide done for now. Any questions or suggestions on the guide, please let me know! Also, refer to post #2 for some stock partition map reference.
Finding Stock Partition Info For Your Device
Three methods:
Most reliable - See the section "Gathering info" above to get it from ATAG
Only shows size without offset - do "cat /proc/mtd" from adb shell. Can be used to test if you're on stock partitions or not, or to verify partition is big enough for update ZIP's (with sed/grep).
Xperia 2011 Only - Examine SIN header as outlined above. This method is difficult to determine mtd block order but I'm 99% sure the order is same for all Xperia 2011 devices (system=mtd0, userdata=mtd1, cache=mtd2).
Stock Partition Parameters for Various Devices
Xperia 2011 Range:
Code:
[B]anzu (Arc) (LT15) (HDPI):[/B]
(03) kernel - [email protected] ([email protected]) (unmapped)
(04) system - [email protected] ([email protected])
(05) amss - [email protected] ([email protected]) (unmapped)
(06) amss_fs - [email protected] ([email protected]) (unmapped)
(08) adsp - [email protected] ([email protected]) (unmapped)
(09) userdata - [email protected] ([email protected])
(10) vendor - [email protected] ([email protected])
(0B) fota0 - [email protected] ([email protected]) (unmapped)
(0C) fota1 - [email protected] ([email protected]) (unmapped)
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](appslog),[email protected](amss),[email protected](amss_fs),[email protected](adsp),[email protected](fota0),[email protected](fota1),[email protected](boot)
[B]ayame (Arc S) (LT18) (HDPI):[/B]
(03) kernel - [email protected] ([email protected]) (unmapped)
(04) system - [email protected] ([email protected])
\ this is odd, there is 2048k unallocated between boot and system (SEMC made a mistake?)
(05) amss - [email protected] ([email protected]) (unmapped)
(06) amss_fs - [email protected] ([email protected]) (unmapped)
(08) adsp - [email protected] ([email protected]) (unmapped)
(09) userdata - [email protected] ([email protected])
(10) vendor - none
(0B) fota0 - [email protected] ([email protected]) (unmapped)
(0C) fota1 - [email protected] ([email protected]) (unmapped)
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot),[email protected](amss),[email protected](amss_fs),[email protected](adsp),[email protected](fota0),[email protected](fota1)
[B]haida (Neo V) (MT11) (HDPI):[/B]
[I]Same as ayame (Arc S) (LT18)[/I]
[B]hallon (Neo) (MT15) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
[B]iyokan (Pro) (MK16) (HDPI):[/B]
[I]Same as ayame (Arc S) (LT18)[/I]
[B]mango (Mini Pro) (SK17) (MDPI):[/B]
??
[B]satsuma (Active) (ST17) (MDPI):[/B]
??
[B]smultron (Mini) (ST15) (MDPI):[/B]
??
[B]urushi (Ray) (ST18) (HDPI):[/B]
??
[B]phoenix (Neo L) (MT25) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
[B]zeus/zeusc (Play) (R800) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
R800a (and probably i/at, but not x) has unallocated vendor partition. Needs one-time flash of Vendor-enabled FTF (e.g. phoenix or anzu) to allocate it otherwise the vendor map will present I/O errors.
Reserved again (just in case)
Thanks for the info. You have used the same for MIUI for Neo L and Play and we have good internel memory..
Thanks for sharing
Very nice work mate! (Especially for using ATAGs...)
I just started the related thread:
"[DEV][REF] El Grande Partition Table Reference"
To collect detailed partition info from various devices...
E:V:A said:
Very nice work mate! (Especially for using ATAGs...)
I just started the related thread:
"[DEV][REF] El Grande Partition Table Reference"
To collect detailed partition info from various devices...
Click to expand...
Click to collapse
Heh nice! Yours looks a bit more hardcore than mine, I've never used any of those tools
I started this guide so I can port kernels to various devices for Xperia 2011 range, and also to help other devs appeal the users who crave for more internal partition space. But so far, none of these people seem to have the patience to lend a hand with gathering data
Xperia Arc (anzu - LT15i_4.1.B.0.587_Generic Global World)
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
I've been talking to wedgess about the use of the cache partition... been poking around and he pointed me in your direction... so, here we go! :highfive:
[NUT] said:
Xperia Arc (anzu - LT15i_4.1.B.0.587_Generic Global World)
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
I've been talking to wedgess about the use of the cache partition... been poking around and he pointed me in your direction... so, here we go! :highfive:
Click to expand...
Click to collapse
Awesome, thanks for the partition info. I *hope* to get all Xperia 2011 device info so I can build Turbo Kernel for all. From what I can see, Arc partitions are identical to Play and Neo L. So maybe all Xperia 2011 devices are the same.
Since the cache partition is not an FTF file, it goes after vendor - so offset would be 940544 (kb). The size I am not sure and might vary per device. /proc/mtd (or /proc/partitions) should tell you.
Also, you can remove vendor partition - because all ROM's just mount it to the folder at /system/vendor so any vendor files you need can go into system partition, and then you can remap/reclaim vendor.
CosmicDan said:
Awesome, thanks for the partition info. I *hope* to get all Xperia 2011 device info so I can build Turbo Kernel for all. From what I can see, Arc partitions are identical to Play and Neo L. So maybe all Xperia 2011 devices are the same.
Since the cache partition is not an FTF file, it goes after vendor - so offset would be 940544 (kb). The size I am not sure and might vary per device. /proc/mtd (or /proc/partitions) should tell you.
Also, you can remove vendor partition - because all ROM's just mount it to the folder at /system/vendor so any vendor files you need can go into system partition, and then you can remap/reclaim vendor.
Click to expand...
Click to collapse
Might be different for the Arc S (ayame) ... i'm looking into the official firmware release now to confirm... but as i used a FTF for my LT15i to gain size on my userdata a while back this is what i get from the dmesg ATAG lines...
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
cache 32C @ FA4 103936 @ 512512 101Mb
userdata D20 @ 12D0 430080 @ 616448 420Mb
Seeing cache between system and userdata ... but no vendor partition anymore
I also notice my endpoint at 918Mb of 1000MB (as sony states in their whitepaper: 1GB) that would be inside the phone ... lost space or do you know a reason perhaps?
[NUT] said:
Might be different for the Arc S (ayame) ... i'm looking into the official firmware release now to confirm... but as i used a FTF for my LT15i to gain size on my userdata a while back this is what i get from the dmesg ATAG lines...
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
cache 32C @ FA4 103936 @ 512512 101Mb
userdata D20 @ 12D0 430080 @ 616448 420Mb
Seeing cache between system and userdata ... but no vendor partition anymore
I also notice my endpoint at 918Mb of 1000MB (as sony states in their whitepaper: 1GB) that would be inside the phone ... lost space or do you know a reason perhaps?
Click to expand...
Click to collapse
1GB = 1024MB, not 1000MB
Well on stock zeus/phonex, as the OT shows, boot + system + data + appslog (vendor) + cache = 940MB. Along with the ~80MB of reserved data at the beginning for radio/baseband and such, that comes to 1020MB. I assume the last missing ~4MB of the full 1GB is reserved for remapping bad blocks (i.e. wear-leveling).
That FTF is completely weird, just like the 420MB space mod for some devices is actually dangerous (size of one partition overlaps the offset of another by about 20MB). If you visualize your map you just showed, there is some wasted space after /system map. Anyway, the cache partition on zeus board goes right at the end, after vendor. So yeah the maps are obviously different, however I think the 1020MB NAND size is possibly the same for all msm-7x30/Snapdragon S2 SoC devices (not just Sony).
Could you ensure you have flashed a 100% original/genuine FTF file and get full ATAG information again?
CosmicDan said:
1GB = 1024MB, not 1000MB
Click to expand...
Click to collapse
well... thats open for debate in some way, GB != GiB. For me 1GB should be 1024Mb though ...
CosmicDan said:
Well on stock zeus/phonex, as the OT shows, boot + system + data + appslog (vendor) + cache = 940MB. Along with the ~80MB of reserved data at the beginning for radio/baseband and such, that comes to 1020MB. I assume the last missing ~4MB of the full 1GB is reserved for remapping bad blocks (i.e. wear-leveling).
Click to expand...
Click to collapse
most likely yes... sounds fair atleast...
CosmicDan said:
That FTF is completely weird, just like the 420MB space mod for some devices is actually dangerous (size of one partition overlaps the offset of another by about 20MB). If you visualize your map you just showed, there is some wasted space after /system map. Anyway, the cache partition on zeus board goes right at the end, after vendor. So yeah the maps are obviously different, however I think the 1020MB NAND size is possibly the same for all msm-7x30/Snapdragon S2 SoC devices (not just Sony).
Click to expand...
Click to collapse
i've been playing around with wedgess' kernel:
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata 1258 @ CA8 601088 @ 414720 587Mb
cache 40 @ 1F00 8192 @ 1015808 8Mb
EOD: 1024000 1000Mb
Thats what i am using now, thanks to your guide
{
"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"
}
CosmicDan said:
Could you ensure you have flashed a 100% original/genuine FTF file and get full ATAG information again?
Click to expand...
Click to collapse
Will report back with the defaults from the stock rom later... going to bed now... 7:36am here now... haven't been sleeping yet :silly:
Yeah true, the whole kilobyte/kibibyte thing.... they still display KB/MB instead of KiB/MiB in most things even though they're in 1024 unit (shell listings, file explorer properties, etc.) but storage vendors do use true 1000 units, 32GB SDCard for example... but then the software doesn't so it's stupid and confusing So yeah, most people have not adopted it, thus it's better to assume that all KB/MB/etc measurements are done in powers of 1024 still.... because they're old school
I wonder, in pther Android ROM's is it corrrect? In MIUI/Turbo UI it shows 639MB in Storage (instead of MiB) so I assume even Android OS itself is also "wrong" haha. Titanium Backup is the *only* app I know of that shows sizes in power of 1000.... and that confuses a lot of people.
CosmicDan said:
Yeah true, the whole kilobyte/kibibyte thing.... they still display KB/MB instead of KiB/MiB in most things even though they're in 1024 unit (shell listings, file explorer properties, etc.) but storage vendors do use true 1000 units, 32GB SDCard for example... but then the software doesn't so it's stupid and confusing So yeah, most people have not adopted it, thus it's better to assume that all KB/MB/etc measurements are done in powers of 1024 still.... because they're old school
I wonder, in pther Android ROM's is it corrrect? In MIUI/Turbo UI it shows 639MB in Storage (instead of MiB) so I assume even Android OS itself is also "wrong" haha. Titanium Backup is the *only* app I know of that shows sizes in power of 1000.... and that confuses a lot of people.
Click to expand...
Click to collapse
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
LT15i: anzu
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
cache 330 @ 1CB4 104448 @ 940544 102Mb
EOD: 1044480 1020Mb
LT18i: ayame
system.sin: system C80 @ 2F4 409600 @ 96768 400Mb
cache 360 @ 1CB4 110080 @ 506368 107Mb
userdata.sin: userdata D20 @ 12D0 430080 @ 616448 420Mb
EOD: 1046528 1022Mb
MK16i/a: iyokan
system.sin: system C80 @ 2F4 409600 @ 96768 400Mb
cache 360 @ 1CB4 110080 @ 506368 107Mb
userdata.sin: userdata D20 @ 12D0 430080 @ 616448 420Mb
EOD: 1046528 1022Mb
your welcome
Great thanks. It seems the anzu has 2MB unused... is that your device? If so, do you know how to use dd? Can use dd to dump partition, if its mapped bad it will give I/O error.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Great thanks. It seems the anzu has 2MB unused... is that your device? If so, do you know how to use dd? Can use dd to dump partition, if its mapped bad it will give I/O error.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
Yep, I have the anzu, and I know how to use dd... Will test that some time later would it be possible to dump all of the nand flash?
Sent from my LT15i using xda app-developers app
[NUT] said:
Yep, I have the anzu, and I know how to use dd... Will test that some time later would it be possible to dump all of the nand flash?
Sent from my LT15i using xda app-developers app
Click to expand...
Click to collapse
Sure, should be. Say you wanted to dump entire flash to one image, just add another partition to mtdparts parameter with offset 0 and size of 1020MB (in anzu case). Then you can dd from that new mtdblock device to sdcard. But I think you may get lots of I/o errors on the first 80MB, I am really not sure. Just make sure you don't try to write to it LOL.
Also I think our devices need bs=4096 (4KB) because that is the sector size of our nand chip.
EDIT: Maybe there is some unused space at the end of that first 80MB, I am not sure. Because baseband and adsp firmware is less than 80MB.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Sure, should be. Say you wanted to dump entire flash to one image, just add another partition to mtdparts parameter with offset 0 and size of 1020MB (in anzu case). Then you can dd from that new mtdblock device to sdcard. But I think you may get lots of I/o errors on the first 80MB, I am really not sure. Just make sure you don't try to write to it LOL.
Also I think our devices need bs=4096 (4KB) because that is the sector size of our nand chip.
EDIT: Maybe there is some unused space at the end of that first 80MB, I am not sure. Because baseband and adsp firmware is less than 80MB.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
From what i know from using dd: it does a byte4byte copy, in any sector size you like but in any case it will read what the disk says there is, as long as there is a disk... so the o/i errors should only occur on those parts that are either damaged or non existent...
I'll do a partition as last option in the config_cmdline grabbing the theoretical maximum of 1024Mb and see if it will fly.
As the NAND flash chip has no logic that makes it a disk like entity other then direct access through MTD software logic (hence yaffs2 as filesystem of choice) i strongly doubt it will use the last 2/4Mb in the end as wear leveling buffer...
[NUT] said:
I'll do a partition as last option in the config_cmdline grabbing the theoretical maximum of 1024Mb and see if it will fly.
Click to expand...
Click to collapse
Well... it doesn't ... it craps out on the first sector it seems, but even if i skip the first sector it still doesn't want to go, probably because the partition size was wrong in the first place, but it's strange anyway.
Building a new testkernel with [email protected] which is one less in size, if 0 counts as the first, the last probably didn't exist
EDIT: nope, that one didn't fly either... dunno why, dd isn't very elaborate on it's errors
[NUT] said:
Well... it doesn't ... it craps out on the first sector it seems, but even if i skip the first sector it still doesn't want to go, probably because the partition size was wrong in the first place, but it's strange anyway.
Building a new testkernel with [email protected] which is one less in size, if 0 counts as the first, the last probably didn't exist
EDIT: nope, that one didn't fly either... dunno why, dd isn't very elaborate on it's errors
Click to expand...
Click to collapse
I think that beginning part is "read-protected" in userspace, I'm not sure. I will def. like to try this but my linux machine is awaiting repairs, I want to see if I can write to the amss (SBL) partition. Probably not though
CosmicDan said:
I think that beginning part is "read-protected" in userspace, I'm not sure. I will def. like to try this but my linux machine is awaiting repairs, I want to see if I can write to the amss (SBL) partition. Probably not though
Click to expand...
Click to collapse
I would agree with you, except if I skip the first 92 Mb of the NAND with dd it still doesn't read... maybe the 'read-protection' foils that plan as well... I don't know ...

P6000 General Thread - Bug fixes, FAQ, general info.

Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh M​Various
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 #186​Android 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.ini​KingoRoot 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 different​Charging batteryFlashing a custom recovery should allow you some way to charge the battery​I 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. Confirmed​RIL 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 mode​IMEIIMEI 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 28000​SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5​ROM 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.

MIUI7 Global Stable V.7.5.2.0 OTA for A350

{
"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"
}
Latest OTA from V.7.3.1.0 to V.7.5.2.0​
BLAZING FAST PERFORMANCE​
A ROM by rsbaviskar for Micromax Canvas Knight.​All Rights Reserved.All other trademarks are property of their respective owners.​
Features :
-Based on Android 4.4.2
-Ported from Redmi NOTE 3G Global ( Beta Version )
-Pure MIUI
-Latest Version Es Explorer
-Titanium Backup
-GAPPS included
-Antivirus
-System & Memory Cleaner
-Record FM and Calls
-Privacy Management
-Power Management
-Data Saver Feature
-Block unwanted calls and messages
-Burst and HDR Modes in Camera
-One Handed Mode
-Guest Mode
-Brand New Headphones setting added.
-GOD OF CUSTOMIZATION :angel:
-New MIUI 7 Themes
-Redesigned App Icons
-New Settings Arrangement
-Better Toggle Style
-Notification Blocking in Notification Shade
-Improved System Performance
Read FAQ :
Please don't ask noobish questions, first read the FAQ
MIUI 7.5 Global Stable ROM Fulll Changelog
Messaging
Optimization - Accessibility in Messaging. Buttons for a call back and contact details, voice-over for attachments. (03-15)
Lockscreen, Status Bar, Notification Bar
Fix - Viewing Daily lock screens sometimes led to black screen (02-23)
Fix - Screen lit up multiple times after receiving a notification (03-10)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Delete - (For security reasons) "Forgot password" option for lock screen (03-04)
Delete - Manage guest access to notification shade (03-18)
Music
New - Dragging songs to rearrange playlist order (03-08)
New - Saving current playlist as a new playlist (03-08)
New - Shortcut for recently played songs (03-08)
Backup
Optimization - Mi Mover transfer speed (05-09)
Fix - Interruptions or unsuccessful file transfers in Mi Mover in some cases (03-01)
Fix - "Select app" page in Mi Mover sometimes didn't respond (03-10)
Fix - Errors with transferring files containing "%" in the name (03-10)
Fix - In some cases Mi Mover transfers interrupted and the app didn't respond (03-11)
Fix - In some cases Mi Mover stopped working after the connection was established (03-18)
Weather
New - New white design (04-27)
Permissions Manager
New - A security prompt will appear when an app is installed via USB to prevent unwanted installations (03-08)
Optimization - Preventing apps which have permissions to read notifications from starting automatically (03-16)
Clock / Calculator
New - Long press alarm to select and delete multiple alarms (03-29)
Mi Account
Optimization - Simplified sign-in process and creating Mi Account (04-19)
Cleaner
New - New design for Cleaner (04-27)
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
Security
New - Fingerprint unlock for custom apps (03-15)
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
Optimization - Improved performance for status bar (02-23)
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
Installation Instructions :
Code:
[SIZE="4"]-To Enable & Enjoy Latest Version OTA all you need to be on MIUI 7 ROM v.7.3.1.0 Global Stable.
-Start Recovery Mode. ( Use only PhilzTouch Recovery V3 provided in the given link below )
-Take full NANDROID backup Via recovery of previous or stock ROM .(In case of any problem)
-Then reboot recovery.
-Wipe data or factory reset.
-Wipe cache partition.
-Wipe Dalvik Cache.
-Clean to Install ROM
-Install MIUI 7 GLOBAL V.7.3.1.0 ROM followed by--->Latest OTA V.7.5.2.0--->Sound Enhancement patch.
-do set up your device without inserting SIM nor Connecting to WIFI on 1st boot.
-You Can Flash Dolby zip later on
[/SIZE]
Credits :
worstenbrood - For his Dolby Atmos.
XIAOMI & MIUI -For Providing the ROM.
Dr.Rahul(ME) & My Lovely Brother Dr.Rohan-For Endless Efforts.
DON'T FLASH ANY KERNEL
Note :
-IMPORTANT: FLASH AT YOUR OWN RISK. We are not responsible for any bricked phones or damages caused due to the ROM. You lose
warranty when you root/flash ROMS on your phone.
-BATTERY: Keeping at 100% charged is recommended before flashing.
-BACKUP: Take BACKUP from recovery, useful in case you mess up. Or try Titanium to backup all data and apps.
-Please do not mirror without permission.
-Do not port without permission
-Please read the FAQ first as it might help you.
-Please don't send PM. Ask queries in the thread only.
-Please do not send request to add any app / themes.
-This ROM will be kept as as close to pure MIUI to give a rich experience.
-Please don't ask for when will you update the ROM.
-I won't guarantee anything about my ROM. If you like it keep it otherwise the most simple thing you can do is switch to some other ROM.
DOWNLOAD SECTION​
Download MIUI 7 Global Stable V.7.3.1.0 ROM For V3(Latest) : CLICK HERE
Download MIUI 7 Global Stable OTA from V.7.3.1.0 to V.7.5.2.0 For V3(Latest) : CLICK HERE
Download Philz Touch Recovery for V3 Micromax A350 : CLICK HERE
Download Sound Enhancement Patch : CLICK HERE
Download Dolby Atmos V6.5 : CLICK HERE
Download MIUI 7 Global (Dev) V.5.8.22 ROM For V2(unmerged partition) :CLICK HERE
Download MIUI 7 Global (Dev) V.5.9.25 ROM For V3 : CLICK HERE
Download OTA1 V.5.8.28 :CLICK HERE
Download OTA2 V.5.10.15 : CLICK HERE
Download OTA3 V.5.11.6 : CLICK HERE
Download EBR FOR 4GB APP STORAGE : CLICK HERE
Download EBR FOR 8GB APP STORAGE : CLICK HERE
Download EBR FOR 13GB APP STORAGE : CLICK HERE
Download EBR FOR REVERT TO V2 APP STORAGE : CLICK HERE
Download Philz Touch 6.47.7 KK for V2 Micromax A350 : CLICK HERE
Google Services & Login Error Fix : CLICK HERE
MIUI8 FOR A350 FORUM LINK : CLICK HERE
Hit thanks if you like my work :good:
FAQ : ​
Q1. How to move apps to Internal Storage ?
Ans. Moving apps to Internal storage does not works on MIUI.
Q2. How to Turn ON flash light from Lock Screen ?
Ans.The lock screen on the MIUI V7 had a few extra functions than the standard unlocking and shortcuts. One of them is turning flashlight On directly from the lock screen. For that, while the screen is active but locked, you just need to long press the home button and the torch / flashlight turns on. It would not turn off until you prompt it although the screen would go blank in a few seconds.
Q3.How to Change the look of Multitasking / Recent Menu ?
Ans.By default, when you press the Recent key (the left bottom one), the recent apps show up, and it is just the App icon that is seen. But, you can make it look like the iOS multitasking screen where large thumbnails are shown, with the preview of what is going on in the app. You can change that by pinching out on the empty area in the multitasking screen. Pinching in / out is what changes the look, basically.
Q4.How to Enable or Change Notification Light Color ?
Ans.There is an option that allows you to change the change the notification light as well as turn it off completely. To do that you have to go to Additional Settings section, and tap on notification light. There you would find four option, first would allow you to switch ON or OFF the Pulse Notification light while other options allow you to change colors for notifications, calls, as well as messages. You can choose only 2 colors ( GREEN OR RED ), which will appear in the LED present just below the home button.
Q5.Facebook Messenger pop-up head does not appears , what to do ?
Ans.Go to Security icon on the homscreen > Permissions > Again Permissions > Open Messenger > Enable Display pop-up window.
You can follow the same method for other apps as well which have the feature of pop-up head notification.
Q8.My Screen Orientation takes longer time than usual ?
Ans.Download Advance Tools app, go to sensors ,you will find total 9 sensors with info, keep you device on horizontal & Steady surface & press reset button by selecting individual sensors...​
XDA:DevDB Information
MIUI 7 Global Stable Edition for Micromax A350, ROM for all devices (see above for details)
Contributors
rsbaviskar, rohanbaviskar530, Mr.AK, worstenbrood
Source Code: https://github.com/tpruvot/MT6592-KK-KERNEL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.4.2-V2 with EBR mods available & V3(merged storage)
Based On: MIUI
Version Information
Status: Stable
Current Stable Version: 7.3.1.0 & 7.5.2.0
Stable Release Date: 2016-07-25
Created 2015-09-04
Last Updated 2016-07-27
Great work!!! A flawless ROM!! No bugss found!!!
Note: I flashed it with cmw recovery, took 5 mins to flash, 5 mins to boot, have patience!!! Don't worry it will boot but take time.
Apk not getting updated over play store showing update on WiFi only: goto tool-->download> setting-> click unlimited. .... Done
Thanks again Dr......
@Praful Pradhan Thanks a lot bro for sharing your experience
Dr Rahul,
Many thanks for your efforts! Working flawless since last 2 days.
1) Just curious about the camera MPixel size as the default camera app doesn't show size options by MPixels . The Picture Quality options (High/Standard/Low) works fine.
2) Does both SIM cards work on 3G? (not sure if stock device has both 3G enabled)
3) Slight mis-alignment on slide up/slide down screens like in clock-alarm, Download limit setting type of pages. (can be ignored though)
4) USB Mass storage mode is missing (only Camera and MTP modes) even though this is for un-merged storages
Thanks
Vipin
Great Rom,Even Beter than miui6....REally Awesome Work Buddy...
Thanks AK,will add Screen shot soon
Downgrade to install miui 7
Praful Pradhan said:
Great work!!! A flawless ROM!! No bugss found!!!
Note: I flashed it with cmw recovery, took 5 mins to flash, 5 mins to boot, have patience!!! Don't worry it will boot but take time.
Apk not getting updated over play store showing update on WiFi only: goto tool-->download> setting-> click unlimited. .... Done
Thanks again Dr......
Click to expand...
Click to collapse
Hi Praful,
Need your kind help.
Using Micromax_A350_SW_V6.0_HW_V1.4_231214 rom and am not able to downgrade to v2 in order to activate partitions.
Downloaded Micromax_A350_V2_040614_KitKat but after doing Format all+Download in Smart Phone flash tool the phone doesnt boot.
After above step if flash the rom V6.0 with Format all + Download the phone works.
Is it the error with the V2 rom am i flashing it in a wrong way...
Please help cant wait to use Miui 7 rom.
Thanks in advance
Vaibhav
buntys82 said:
Hi Praful,
Need your kind help.
Using Micromax_A350_SW_V6.0_HW_V1.4_231214 rom and am not able to downgrade to v2 in order to activate partitions.
Downloaded Micromax_A350_V2_040614_KitKat but after doing Format all+Download in Smart Phone flash tool the phone doesnt boot.
After above step if flash the rom V6.0 with Format all + Download the phone works.
Is it the error with the V2 rom am i flashing it in a wrong way...
Please help cant wait to use Miui 7 rom.
Thanks in advance
Vaibhav
Click to expand...
Click to collapse
Silly Mistake Buddy,U Need To select Upgrade Frimware in Sp Flash tools Install OF Format All...
If Any other problems msg me here on whatsapp +919468519959
Mr.Ak said:
Silly Mistake Buddy,U Need To select Upgrade Frimware in Sp Flash tools Install OF Format All...
If Any other problems msg me here on whatsapp +919468519959
Click to expand...
Click to collapse
Imei lost...so no phone working...will surely add you once my starts..
Did Upgrade firmware but the phone wasnt booting..
getting below error..on trying v1 BROM ERROR.
Main error is due to ur using same file again and again of mmx350.
The ROM file u downloaded I.e. zip file... Extract it again... And use it in SP tool as fresh one....or use wiko highway v19 file... Remove sim while flashing.. Restore imei..with the help of mtk tool..
Best of luck
Hits thanks if like...
Sent from my Micromax A350 using XDA Free mobile app
worked very fine in my.
No bugs till now.
The only thing that I found is that miui has a new update that doens't work.
Thanks for this rom!
Yes true updates downloaded but not applied due to phone build issue... As it is not xiomi phone...
Sent from my Micromax A350 using XDA Free mobile app
Error details
Starting recovery on Mon Sep 7 22:59:04 2015
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1080 x 1920)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 21.09.2013 13:16:45
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p5 (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p8 (null) 0
5 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
6 /boot emmc /dev/bootimg (null) 0
7 /recovery emmc /dev/recovery (null) 0
8 /uboot emmc /dev/uboot (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.sys.usb.config=mass_storage
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB9.MP.V1.4
ro.build.version.incremental=37
ro.custom.build.version=S9320_Agua_Infinity_20140304_V10
ro.internal.build.version=S9320_MP_PH_MYP_16_16
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Fri Mar 21 20:49:53 CST 2014
ro.build.date.utc=1395406193
ro.build.type=user
ro.build.user=android
ro.build.host=HTSVR7
ro.build.tags=release-keys
ro.product.model=MyPhone Agua Infinity
ro.product.brand=MyPhone
ro.product.name=MyPhone_Agua_Infinity
ro.product.device=MyPhone_Agua_Infinity
ro.product.board=MyPhone Agua Infinity
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=MyPhone
ro.product.locale.language=en
ro.product.locale.region=PH
ro.wifi.channels=
ro.board.platform=
ro.build.product=MyPhone Agua Infinity
ro.build.description=s9320ae-user 4.2.2 JDQ39 37 release-keys
ro.build.fingerprint=MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys
ro.build.flavor=
ro.build.characteristics=default
ro.mediatek.version.release=ALPS.JB9.MP.V1.4
ro.mediatek.platform=MT6592
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB9.MP
ro.mediatek.version.sdk=1
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
wifi.interface=wlan0
ro.mediatek.wlan.wsc=1
ro.mediatek.wlan.p2p=1
mediatek.wlan.ctia=0
wifi.tethering.interface=ap0
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=300m
dalvik.vm.heapsize=300m
ro.sys.usb.mtp.whql.enable=0
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
ro.sys.usb.bicr=no
ro.sys.usb.charging.only=yes
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
net.tinno.bt.name=S9320
net.change=net.bt.name
persist.lcd.pq.pqparam=30gggggggg
persist.sys.timezone=Asia/Manila
persist.wifi.firmware=1
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=1
ro.sf.lcd_density=180
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
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.mtk.wcn.combo.chipid=-1
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=MTK_CONNSYS_MT6592
mediatek.wlan.module.postfix=_mtk_connsys_mt6592
ril.radiooff.poweroffMD=0
ter.service.enable=0
persist.sys.display.clearMotion=1
persist.clearMotion.fblevel.nrm=255
persist.clearMotion.fblevel.bdr=255
ro.config.ringtone=MyPhone_Online_Pop.ogg
ro.config.notification_sound=MyPhone_Tune.ogg
ro.config.alarm_alert=RingingAlarm.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r3
persist.sys.skin=/system/framework/theme-res-mocha.apk
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.adups.fota.oem=MTK88_92
ro.adups.fota.device=MyPhone Agua Infinity
ro.adups.fota.version=ALPS.JB9.MP.V1.4
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6592
ro.revision=0
ro.emmc=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Signature Check: Enabled
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
-- Installing: /sdcard/downloaded_rom/update.zip
Finding update package...
I:Update location: /sdcard/downloaded_rom/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Updating package '/sdcard/downloaded_rom/update.zip' ...
__bionic_open_tzdata: couldn't find any tzdata when looking for Asia/Manila!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting updater on Mon Sep 7 23:00:28 2015
============= emmc ===============
name: HBG4e
manfid: 0x000090
date: 09/1997
cid: 90014a4842473465040201a2d9349069
csd: d02701320f5903ffffffffef8a4040d3
oemid: 0x014a
erase_size: 524288
preferred_erase_size: 524288
stat: 477 1395 93752 1270 21 23 360 4740 0 3850 6010
============= prop ===============
ro.build.fingerprint=MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys
ro.build.version.release=4.2.2
ro.build.version.incremental=37
ro.build.product=MyPhone Agua Infinity
ro.product.device=MyPhone_Agua_Infinity
ro.product.mod_device=unknown
ro.miui.ui.version.name=unknown
Warning: No file_contextsscript aborted: Package expects build fingerprint of Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.22:user/release-keys or Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.28:user/release-keys; this device has MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/release-keys.
Package expects build fingerprint of Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.22:user/release-keys or Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.4.2/KOT49H/5.8.28:user/release-keys; this device has MyPhone/s9320ae/s9320ae:4.2.2/JDQ39/:user/releasdevice name: /[email protected]
Filesystem volume name: <none>
Last mounted on: /system
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: unsigned_directory_hash
Filesystem features: has_journal ext_attr resize_inode filetype recover extents sparse_super large_file gdt_csum
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem os type: Linux
Inode count: 131072
Block count: 524032
Reserved block count: 0
Free blocks: 339260
Free inodes: 128174
First block: 0
Block size: 4096
Reserved GDT blocks: 127
Blocks per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Mon Sep 7 23:00:28 2015
Last write time: Mon Sep 7 23:00:28 2015
Mount count: 2035
Maximum mount count: 65535
Last checked: Thu Jan 1 00:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 1225 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
E:Error in /sdcard/downloaded_rom/update.zip
(Status 7)
Installation aborted.
My bateri now lives for 2 days! awesome!
Thanks a lot @profetaii,hope u r enjoying MIUI 7.M currently working on some other project ,but also trying to provide latest OTA Update of MIUI 7 V.5.8.28 Soon..as m able to successfully modify OTA files as per device.soon provide screenshots guys
Very very Thanks!!!
rsbaviskar said:
Thanks a lot @profetaii,hope u r enjoying MIUI 7.M currently working on some other project ,but also trying to provide latest OTA Update of MIUI 7 V.5.8.28 Soon..as m able to successfully modify OTA files as per device.soon provide screenshots guys
Click to expand...
Click to collapse
Thanks for your efforts for providing such a great bug Free ROM!!!!
Can you make it with V3 - (merged storage ROM) of MMX350!!!
Best of luck for your efforts!!
Miui7 an tu tu score 31k... Not happy....as 32k was for wiko highway v19!!!
Sent from my Micromax A350 using XDA Free mobile app
can we flash this rom on Micromax gold
Just to update following things for this ROM!!1
Roaming working fine for both the sim!!! - took 5 mins to search network but finally OK
Data in Roaming working Fine !!!
One major issue I'm facing is security apk updates!!!
There is no automatic update!!!
Any one plz help!!

[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing

[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing
Disclaimer
Upon following this guide, you may or may not achieve same results with others. I am not held responsible for anything unexpected that may happen to your device. Do your research first regarding the areas you do not quite understand. Follow at your own risk.​
Prerequisites
Spreadtrum Flash Tool R4.0.0001 (PAC Flashing) or Flashfire (Zip flashing)
SPRD USB Driver (needed for PAC Flashing)
Male to Micro USB Cable (needed for PAC Flashing)
7-Zip
Root with SuperSU (just below, needed for first time Zip flashing)
Packet (*.pac) or Zip ROM (found below)
Rooting
Install and gain root through KingRoot android application.
Restart your phone. (I've encountered a sudden reboot when doing the steps below without this)
Replace KingRoot with SupeSU through this script.
Once the archive is downloaded, extract it. There will be a folder named root where you extract it.
Download and open Terminal Emulator.
Change directory to the root folder that was extracted:
Code:
cd /path/to/root
Then ask for root permissions:
Code:
su
Now run the first script:
Code:
sh level1.sh
Run the second script:
Code:
sh level2.sh
Leave the terminal running and open KingRoot.
Press the button at the upper right corner, and choose general settings.
Scroll down and press uninstall.
Uncheck backup and press OK.
After KingRoot has finished uninstalling, go ahead and uninstall Purify as well.
Go back to the terminal and run the third, last script:
Code:
sh level3.sh
Again leaving the terminal running, install SuperSU and open it.
Let it update the root binary through Normal method, and restart.
Notes:
Currently SuperSU's prompt for applications asking for root permissions does not work, but, changing the setting to "grant" will. Just return it to "deny" afterwards, for security. That's the workaround for now.
Dumping
Before doing anything to your device, it is advised to create a ROM dump/backup beforehand. Also make sure you have a lot of free space on your internal storage.​
Open up terminal and gain root permissions:
Code:
su
Then get the partition details:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
Dump each partition (X) with its name (Y):
Code:
dd =if/dev/block/mmcblk0pX of=/sdcard/Y.img
Do not forget to dump the two bootloaders:
Code:
dd =if/dev/block/mmcblk0boot0 of=/sdcard/splloader.img
Code:
dd =if/dev/block/mmcblk0boot1 of=/sdcard/uboot.img
Flashing
PAC
Extract all the downloaded archives and install the driver (either 32install for 32/86bit or 64install for 64bit OS).
Open the flash tool by double clicking the executable named "ResearchDownload".
Once the flash tool opens, click the single gear button at the top left.
Find and open the PAC ROM.
Press the play button.
Power down the device, hold the volume down button and plug it into the PC.
The flash tool will then recognize the device and start downloading binaries to it.
Once the progress column shows "PASSED", the binary download is finished and the device can now be safely unplugged.
Remove the battery, reinsert, and power the device.
Zip
Gain root if not already done so.
Open Flashfire. (press agree and the other one is up to the user)
Press the red circular button with a plus sign ( + ) on the bottom right, and choose Flash ZIP or OTA.
Find and open the downloaded Zip ROM.
There will be a pop-up for a few settings, leave it as is and press the check icon at the upper right.
Now when the pop-up closes, swipe down and press the Flash button with a lighting icon.
Press OK, and let it flash.
The device will reboot once flashing is finished.
Unbrick Stock PAC ROM
Y541-U02V100R001C567B116
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HUAWEIY541-U02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Mon May 23 22:44:32 CST 2016
ro.build.date.utc=1464014672
ro.build.type=user
ro.build.user=
ro.build.host=a7fcf16085c3
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=HUAWEI Y541-U02
ro.product.brand=HUAWEI
ro.product.name=Y541-U02
ro.product.device=HWY541-U
ro.product.board=Y541-U02
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HUAWEI
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Y541-U02
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Y541-U02-user 4.4.2 HUAWEIY541-U02 135 ota-rel-keys,release-keys
ro.build.fingerprint=HUAWEI/Y541-U02/HWY541-U:4.4.2/HUAWEIY541-U02/C567B116:user/ota-rel-keys,release-keys
ro.build.characteristics=default
ro.zygote.disable_gl_preload=false
# end build properties
#
# from device/ontim/Y541-U02/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=SP7731GEA_V1.0.0
debug.hwui.render_dirty_regions=false
ro.config.hw_showSimName=true
ro.config.hw_hideSimIcon=false
ro.config.coop_stk1comp=com.android.stk1;com.android.stk1.StkLauncherActivity
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=false
persist.ttydev=ttyVUART0
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
persist.modem.w.enable=1
persist.modem.w.nvp=w
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=seth_w
ro.modem.w.snd=1
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
persist.sys.engpc.disable=0
ro.modem.wcn.enable=0
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
camera.disable_zsl_mode=1
ro.digital.fm.support=1
ro.config.ksm.support=true
#supprot storage path change
ro.storagepath.change.support=true
#supprot quickcamera
ro.quickcamera.support=true
#zram config
ro.config.zram.support=true
ro.board_ram_size=mid
# SPRD: add low cost low memory @{
ro.config.low_ram=true
# @}
#if our product not support drm,set as false
drm.service.enabled=true
# hotspot development
ro.hotspot.enabled=1
# this product does not support bt and softap coexist
ro.btwifisoftap.coexist=true
# SPRD: add support hwrotation
ro.sf.hwrotation=0
#SPRD: add support follow sim system config
persist.support.fssc=1
#SPRD: add for cphs
persist.support.oplpnn=true
persist.support.cphsfirst=false
#SPRD: add support virtualnet
persist.support.virtualnet=true
#ontim:add support huawei wlan setting
persist.huawei.wifi.setting=true
#SPRD: add support encrypt
ro.encrypt.devices.support=0
#SPRD: add support vt
persist.sys.support.vt=false
#SPRD: delete baseband version
ro.show.basebandversion=false
#SPRD: mccmnc config path
ro.mccmnc.info.path=/globalinfo/
#for app can install on sd and primary is internal
ro.storage.installonsd=true
# Audio Dump Information for HAL
audio.dump.show.switch=0
hw-k3-burst-supported=1
# adapter for HuaWei PIN(keyguard apk) added by liulibo
ro.config.is_sprd=true
#avoid gallery function:chang voice pic to video.
ro.config.hw_trans_voiceimage=false
#avoid gallery map function
ro.config.support_gallery_map=false
#wifi_country
ro.config.custCountryEnable=ir,sd,sy,kr
# SPRD: DC lowpower
sys.dc.lowpower=true
ro.systemui.flashlight.timeout=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.incremental=C567B116
ro.product.sw.internal.version=Y541-U02V100R001C567B116_user_30323_160523.223910
ro.product.sw.external.version=Y541-U02V100R001C567B116
ro.build.cust.id=Y541-U02V100R001C567B116
ro.versioninfo.delivery=MocorDroid4.4_TShark28_2341A_W15.16.5
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.sprd.modemreset=1
ro.adb.secure=1
persist.sys.sprd.wcnreset=1
ro.xtsdisableverify=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.support.vt=false
sys.usb.gser.count=4
lmk.autocalc=false
persist.sys.data_reserved=100
ro.config.ringtone=Huawei_Tune.ogg
ro.config.ringtone0=Huawei_Tune.ogg
ro.config.ringtone1=Huawei_Tune_Piano.ogg
ro.config.notification_sound=Bongo.ogg
ro.config.alarm_alert=Creamy.ogg
persist.sys.wakeup.enable=0
ro.config.hw_timeformat=true
ro.config.timeformat=24
persist.sys.modem.diag=,none
persist.sys.slog=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r7
ro.build.display.id=Y541-U02V100R001C567B116
ro.config.max_starting_bg=3
ro.com.google.clientidbase=android-huawei
ro.com.google.clientidbase.yt=android-huawei
ro.com.google.clientidbase.am=android-huawei
ro.com.google.clientidbase.gmm=android-huawei
ro.com.google.clientidbase.ms=android-huawei
ro.dual.sim.phone=true
ro.config.hw_coop_no_setting=true
ro.config.remove_subscribe_menu=1
ro.config.hw_coop.ontim=true
ro.config.hw_coop.show_Sun=1
ro.config.app_big_icon_size=90
ro.config.hwcust_drawbgicon=false
ro.config.hw_coop_delay=true
ro.config.hwtheme=1
persist.radio.langu.rule=0
data.icon.onlyconnected=true
persist.sys.certification=103323
ro.config.is_support_my=true
ro.product.hwinternal.version=Y541-U02V100R001C567B116
ro.product.hwinternal.ver.time=160523.223910
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
ro.floatkey.show=false
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Notes:
These ROMs are repacked and tested first before being posted, so if one of these does not work, try another. If none worked, just wait, others will share a new partition dump.
These ROMs do not contain a system, custom and cache dump because these are for unbricking for now. Prerooted full repacks are coming soon.
Stock ZIPs
Notes:
As the device refuses any custom or modified stock binaries, Flashfire is the only way to go to install zips.
These are pre-rooted, deodexed, zipaligned, de-bloated, and of course tested.
None at the moment.
Troubleshooting
If the flash tool fails to download, either the downloaded ROM is incompatible with the device, or the cable is loose.
If the device shows a white screen but the booting sound is heard, try another one.
Support
If anyone happens to have the same device model in fully working condition but seems to be different, kindly make a partition dump of it and PM the link, so it can be processed and uploaded here.​
Credits & Sources
@najoor for the original KingRoot to SuperSU script.
GSM Flashfile Website
@Kingxteam for KingRoot
@Chainfire for SuperSU & Flashfire
Is there any customs available for this device
anil kalyan said:
Is there any customs available for this device
Click to expand...
Click to collapse
As of now, with the bootloader locked, there is none.
In future can we expect the same..........
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
techyzen101 said:
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
Click to expand...
Click to collapse
When can we expect this
Where we are on this Can we expect Lollipop rom anytime
Please provide the lollipop ROM
after flash check download state, last download maybe not complete.
Does anyone have a full file or link .pac file Y541-U02V100R001C567B116 ~ 1.5Gb
Y541-U02V100R001C567B112
I need This version pac file help plz
snmobilecenter said:
after flash check download state, last download maybe not complete.
Click to expand...
Click to collapse
hello can i ask if what can be done when you encouter this error upon power on?
tried flashing with research download and upgrade downgrade tool from spdflashtools.
got it to flash firmware v105. but after flashing, blank screen won't power on. also cannot go to recovery.
tried to flash it again with different version, did not go thru anymore and cannot go through any firmware versions.
stuck at FDL2 failing.
tried android usb drivers and spd /sci drivers still stuck at fdl2
please help.
how to get twrp?

Categories

Resources