yashsingh1/xdaforums huggingface dataset:
[Android General] HypoTurtle:
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://xdaforums.com/showthread.php?t=2746861

http://xdaforums.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.​
[Android General] bigrammy:
Very Helpful and concise

Nice one bro :good:

Subscribed :cool:
[Android General] greekfragma:
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 :)
[Android General] xenonism:
Still doesn't work for me on 8.3.
[Android General] rene90:
Nice one, i get my phone in a couple of weeks.
[Android General] Xpresso38:
Hello

and Thanks for all your work ! :victory:

Can you add how save and restore imei ?
[Android General] greekfragma:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
[Android General] xenonism:
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.
[Android General] ludmiloff:
Well, time to get in here, I guess...

[MENTION=3356343]xenonism[/MENTION], 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
[Android General] xenonism:
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. :o

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:

If I try to install the same update with ROM Manager, it also fails in CWM with the following message:

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:

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.
[Android General] HypoTurtle:
[MENTION=6414719]ludmiloff[/MENTION] 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.

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.
[Android General] xenonism:
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. :D
[Android General] ludmiloff:
[MENTION=4056517]HypoTurtle[/MENTION],

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.
[Android General] xenonism:
[MENTION=6414719]ludmiloff[/MENTION], 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. :confused:

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.
[Android General] ludmiloff:
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.
[Android General] bigrammy:
I cant see any CWMLollipop.img there :confused:

They only list two recoverys my P6000CWM3.img with no links or credits of course :mad:

and carliv's CWM_Modd_2.img again no links or credits :mad:

I will be working on the lollipop soon :eek:

I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes. ;)
[Android General] HypoTurtle:
Connect/disconnect is normal: You need to press the Download button, top left in SPFlash before connecting the phone.

Are you sure it's freezing after boot - the runtime (dalvik) will have to be remade after restoring ROM and this could take a while.

For recovery you'll need to flash a 32bit recovery either with SPFlash or fastboot (fastboot flash recovery recovery.img)
[Android General] Xpresso38:
I've retry with spflashtool, and then i've flash with old 4.4 rom.

I think phone was freezing, because gingle at start wasn't play in all :/

P6000 is back with 4.4 and 4G :)

Thanks Again HypoTurtle !
[Android General] GoJo ^^:
Please anyone take 2sec to reply these.. ;)
[Android General] bigrammy:
Home button lights for 5 seconds then goes off unless you touch the back, menu or home softkeys :confused:

Not sure about changing the color as it was not on my list of priority.

Camera fix buy a Pentax or Cannon SLR :laugh:

In normal light conditions the phone camera works fine so you can't fix something that's not really broken :eek:
[Android General] scubascuba3:
Bigrammy, were you able to fix the poor focus?
[Android General] HypoTurtle:
Android 5.0 Modifications

MultiUser Support Reference

Add the following two lines to /system/build.prop and reboot

fw.max_users=3

fw.show_multiuserui=1
​

Cast screen from Quick Settings (Chromecast) Original Tutorial

All steps from fresh flash to Android 5.0

1. Install SuperSU apk (and Chromecast apk)

2. Have terminal access; either:

2.1 Install Terminal Emulator apk

2.2 Ensure you have adb access​

3. Set SELinux to permissive; either:

3.1 Install SELinuxModeChanger apk

3.2 In terminal shell: #setenforce 0​

4. Install a SQLite Manager apk

5. Open Sqlite apk

Open database /data/data/com.google.android.gsf/databases/gservices.db

Select overrides

Select New/Add

Add two entries:

gms:cast:miroring_enabled true

gms:cast:remote_display_enabled true​

6. Force stop 3 apps; Chromecast, Google Servies Framework and Play services; either:

6.1 Settings == Apps == All

6.2 In Terminal shell:

#am force-stop com.google.android.gsf

#am force-stop com.google.android.gms

#am force-stop com.google.android.apps.chromecast.app​

Xposed Framework Dev Thread

Unofficial Xposed for 64bit (5.0 and 5.1)

Download Xposed.zip

Download XposedInstaller apk

Official Xposed thread for updates

GravityBox can't be used, but XBlast can (apart from the KK specific stuff)As of v5.0.8 GravityBox works

Screen Pinning

You need a dedicated overview button to long press:

- get one with Xposed module - GravityBox v5.0.8+

- by activating the navigation bar​

Bootanimation Fix Original Tutorial

Download bootanimation.zip

Copy bootanimation from AOSP/64bit/ in the zip to /system/bin/

Ensure correct permissions 755 (rwxr-xr-x)​

SD Card swap

Minor switch in boot.img to switch:

Internal sd(/data/media) with External sd (/mnt/media_rw/sdcard1)

V1 Boot-sdswap.img​

Flash it however you want; rasher, flashify, spflash, fastboot, recovery etc.

Shouldn't need to wipe anything, but you can copy/clear the internal sdcard

Will try and see if something can be implemented with build.prop

Multiuser support is still present​

Recovery Zips

First zip added V1

Install via custom recovery, contains all the above except Xposed.
[Android General] bigrammy:
Elephone fixed it not me. :o

Works perfectly Fine for me.
[Android General] bayad:
CM12 for Elephone P6000 soon !!! :fingers-crossed::D

https://twitter.com/Elephone8/status/590842750288945152
[Android General] HypoTurtle:
Hopefully they've fixed the ril from alpha1.

Of note from the youtube video; this is 5.0.2, other than that can't see any noticable differentiation from AOSP, hopefully softkeys can be turned on and it includes cyanogen recovery.
[Android General] bayad:
Fingers crossed :fingers-crossed:
[Android General] HypoTurtle:
Just5 Blaster Port

Port from Just5 blaster Original Thread

KK port made by [MENTION=5593006]z0rgent[/MENTION] from 4pda - likely made possible due to [MENTION=5172169]NiksSkersts[/MENTION] firmware dump.

[ Mega ]​

To paraphrase z0rgent:

I adapted Just5 Blaster Firmware to P6000.

Works good, very fluent, offscreen gestures works, but frontal camera distorts colors some time​

As it seems the Just5 Blaster seems to be a clone of the P6000 but a different camera component is being used on the front camera; specs wise I believe on blaster front cam is 5MP while it's 2MP on the P6000 (unsure if extrapolation is in play here).
[Android General] bigrammy:
Hi bro,

Have you flashed this ROM??

If so does it report the touch in /proc as the gt9xx_config and gmnode2015????? :confused:

I just wondered if they have used a totally different driver in the kernel.
[Android General] xenonism:
I am using this ROM right now. gt9xx_config and gmnode2015????? are indeed in /proc.

Lock screen gestures work, should tap-to-wake also work?
[Android General] bigrammy:
Ok thanks for that bro :good:

I wonder why no one else except just5 has managed to get everything working with this touch. :laugh:
[Android General] xenonism:
No problem. :) Personally I wouldn't even have thought Just5 had their own developers. :confused:
[Android General] Xabadou:
I tried boot.img from Just5 port to p6000 in my own port of Ulefone be Pro.

The system boot up, but screen gestures not work.

This is my port of Ulefone be Pro, works very smooth and fine, the notification led works also:

https://mega.co.nz/#!yN1EXB5B!KCymmSLyVGqZPoaSas4gxAVlD98ErUYWHN4VHQ8OXKI

Only problem is camera quality, the solution is camera patch form Z0rgent.
[Android General] HypoTurtle:
Can you check the sensors, too. In AnTuTu and with gpsstatus2
[Android General] Xabadou:
Rom Just5 flashed.

All working, but only work a few gestures.

Gps positioning are very very quickly.

Installed whitout wipes and rooted whit supersu v2.46:

http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
[Android General] xenonism:
Were you talking to me? Anyway, GPS Status says there's no compass, AnTuTu agrees. Only in V8.3 it was different.

[MENTION=6199310]Xabadou[/MENTION]: thanks for the port. When you say the notification light works, do you mean it works like in V8.3 or in V8.4 or is there a choice? Also, do you own a Be Pro? If you do, does the compass work?

In general, is it possible that the Be Pro has a working compass while the P6000 doesn't, when they are based on the same SoC and the compass is part of it?
[Android General] Xabadou:
I use P6000 kernel for porting roms, the kernel not support compass.
[Android General] laiding:
This is the new ROM for elephone P6000 CyanogenMod12

You'd better conduct factory reset and wipe cache partition first . Back up your phone before factory reset. If there are some errors during flashing, you can flash official rom first and then try again.

[YOUTUBE]oY7OLZl5ork[/YOUTUBE]
[Android General] xenonism:
Understood.
[Android General] HypoTurtle:
Thanks was more interested in the names - I think initially with V8.3 there was more descriptive text in Antutu than just the "MTK ACCELEROMETER","MTK LIGHT" and "MTK PROXIMITY" that are there now.

I don't think the ecompass is part of the SoC, it would be a separate module on the board.

No great loss - only really useful if your stationary - but would've been handy for orienteering/mountaineering etc.

There is a teardown on youtube by geekbuying: [YOUTUBE]watch?v=pl3M4TugnNk[/YOUTUBE]

but they don't appear to have taken any [hi-res] pictures so can't identify components.
[Android General] xenonism:
By memory, I think it was always "MTK ACCELEROMETER" and so on in AnTuTu. I agree we can easily live without the compass, I would just find it a bit annoying if the hardware were there but Elephone had no software support for it (see Smart Wake gestures or Mass Storage and the mess with the notification light).
[Android General] HypoTurtle:
CM12.1 RC1 - ROM Available

ROM indirectly from Elephone

Hosted on pan.baidu and a [MEGA_Mirror] from [MENTION=5593006]z0rgent[/MENTION]

Have only tested a dirty flash; just SPFlashed system.img and boot.img over 5.0_V3.3 (other files are identical) - resulting in FC's.

Will test with wiped data to see if this solves the FC'ing.

The zipped folder is named the same as the Offical 5.0 [K01Q-H.L.vR30.E3.150417] but the included ROM is CM12.1
​

This is likely an alpha, preview, whatever you want to call it build, although it is labeled as release candidate 1; and if the youtube video is anything to go by - and this is the same ROM then sim/ril appears to be working correctly.

Update

ROM starts correctly after clearing data; and as expected not too much works.

1. Only 1 Sim is detected - but IMEI is invalid and I haven't been able to restore yet

2. There is a 250MB out of space warning

This has been noted on other CM12.1 ROMs but the fix (deleting /system/media/bootanimation.zip) doesn't seem to fix the problem.

This may be causing the issue of ART (dalvik-cache) not being correctly generated​

3. Can't side load apps (adb install ...)

if the cause of this is an issue with /data (permissions perhaps) then this may also explain the issue above.​

4. Most other things driver-wise isn't working

Wi-fi and bluetooth can't be switched on

Brightness level, Auto-rotate, Notification light/LED all don't work

Can't check gps (would need to sideload)
​

So definitely a test build (was compiled as test-keys) but looks promising if they can get the drivers to work correctly; to me it appears to be the bare CM build that just needs MTKified.
[Android General] :
So its the official, not yet released Cyanogenmod from Elephone?

Good Job Elephone in that case.
[Android General] xenonism:
Thanks, as always. Forgive my ignorance... FC's?
[Android General] HypoTurtle:
Force Closed... essentially when you get the screen spammed with com.${something} has stopped working toasts. They're often fixed by clearing app data when moving from one rom to another (as opposed to wiping /data).

Have updated previous post.
[Android General] xenonism:
Got it, thanks. I understand Force Closed but I didn't catch the acronym.
[Android General] cheeze.keyk:
i saw cm12.1 on youtube for this device. is good for daily use? :confused:
[Android General] nemo232:
No, i only found CM12 but sim doesn't work yet :(
[Android General] HypoTurtle:
#205

There is likely some way to get the sim to work; but I couldn't get it to - and it gave me IMEI trouble when flashing back to 5.0 so not advised.
[Android General] bayad:
Another version of CM 12.1 Rom here : http://pan.baidu.com/s/1ntzaYPr#path=%2FP6000%2FCM12.1_0504

If someone can try it ;)
[Android General] Xabadou:
This is my beta port from Huawei g629-EMUI 3.0.

Rom is multilang and rooted, but not have Gapps.

Principal bug is camera: don´t work.

Any help is apreciated.

¡Thanks!

https://mega.co.nz/#!DEUjSTKZ!jqK2ZENfRJuuwjqY4jYYrpPVTChH9qpNqNNStI4w8TM
[Android General] HypoTurtle:
First Android 5.0 Custom ROM

ROM is based on VibeUI v2.5 [5.0] ported from the Lenovo K50–T5

Available on mega via needrom

It is posted by mystory - but I don't think is the porter - will try to locate original forum/post

[MENTION=6199310]Xabadou[/MENTION] can you claim credit for the previous EMUI build - v2.3? (currently accredited to mystory)

Additionally - there is an Ele* Flash apk on the companys' pan.bauiu storage

It's not fully functional - but it shows what they're planning - with the above VibeUI ROM seemingly among the available downloadable ROMs. They really need to add one line of credit for the original porter in my opinion - or even half a line - it will still be uncluttered; and be a nice nod to the community at large.
[Android General] Xabadou:
Base rom is this:

http://www.needrom.com/download/ascend-g629-ul00

Port is build by me whith Archikitchen.

Boot.img is from Mystory EMUI 2.3.
[Android General] bayad:
Is this a stable ROM ? Is everything working ? :confused:
[Android General] HypoTurtle:
As it's a 5.0 ROM - I'll compare it to Official AOSP 5.0 - which personally is very stable - when appropriate.

Just installed:

Only two languages - Chinese and English.

Default keyboard is a hybrid chinese/english - it's fine, bit might need replaced

Didn't lose IMEI - installing over AOSP 5.0

Gapps need to be installed on top - I haven't attempted an install yet - Gapps install fine

Not sure if superuser is installed - it should be according to the zip - I have root but I needed to do it manually - probably just a problem with my recovery though

Not working.

Flashlight in QuickSettings - in AOSP QS flashlight is done in a hacky way (I believe it's normal and achieved similarly on other devices) where the camera is activated and flash turned on without the camera UI - so perhaps this issue is due to the lenovo camera app that's included as stock.

Currently restoring data - will report if I notice anything else.

EDIT

External SDCard

Support for installing to sdcard and moving apps to external storage seems to be included by default.
[Android General] bayad:
Thank you for your answer but one more question ;) : do i need to wipe everything (wipe data, cache, dalvik cache) when I'll flash it or i can install it over 5.0 without wiping ?
[Android General] HypoTurtle:
I had to wipe data for a different reason - but had a fairly recent adb backup.ab to restore.

You should be fine just wiping dalvik and cache.
[Android General] bayad:
Another P6000 CM12.1 Rom here : http://pan.baidu.com/s/1ntzaYPr#path=%2FP6000%2FCM12.1_0504. :D

It's a RC3 release from 20150510.
[Android General] cheeze.keyk:
is it stable? and good as daily driver?
[Android General] bayad:
I don't know because I can not install it until our dear developers have not tried themselves to see if it is stable enough for everyday use :)
[Android General] Huk1:
Sound problem

Hello,

I received my new Elephone P6000 android 5.0 but I have problem. I dont have any sound from speaker I tried with earphones it is the same. I cant hear any ring or any song. I have done Factory reset no success. Please help me
[Android General] ferreinf:
Try flashing it using flashtool or rollback to kitkat, could be hardware issue

Enviado do meu Elephone P5000
[Android General] HypoTurtle:
Have a look in Engineer Mode (*#*#ENGMODE#*#*) - and see if the sound level is set properly - failing that it sounds hardware related
[Android General] Huk1:
Thanks but I have tried already and all audio configurations seem to be properly set. Unfortunately it sounds to be hardware issue :(
[Android General] Destrobg:
One day I found my phone with empty battery - zero percent (3.6V was at that time). I plugged it to be charged but there was no identification that the battery was charging. After I while I removed the battery for a bit longer and after that I plugged it again and the Elephone logo has appeared (it was charging). So far so good but when I turned on the telephone it stopped charging. I read in elephone's forum that some guys have similar problem and after reflashing with the original rom everything should be ok. But I don't have such luck. I have reflashed it with the original rom (8.3 and 8.4) several times but without any success. Just after I formatted everything and flashed it I was able to get the phone charging when is on. I was happy but after a while it stopped charging again. Meanwhile lduring all this processes I can't connect the phone to the computer via USB so the menu with Media, Photo, Debbuging, Charging to appear (I think that somehow the two problems are connected). I hope here someone can help me because this phone drive me crazy :(
[Android General] bayad:
Two more Custom Roms for Elephone P6000 :D

ELEPHONE p6000 VIBE 2.5 MULTILANG UPDATE 150522 (Android 5 Lollipop)

Thread :

- http://bbs.elephone.hk/thread-4730-1-1.html#.VV9XHagnWv0

Download Link:

- https://mega.co.nz/#!6ZAC1SSa!7C6uJweCE5FkSCyhCJeZ_oFlpUQN2PjMj70XpN-QyXU

ELEPHONE P6000 ULEFONE UI 150522 (Android 5 Lollipop)

Thread :

- http://bbs.elephone.hk/thread-4733-1-1.html#.VV9XIKgnWv0

Download Link:

- https://mega.co.nz/#!CRByTKIZ!yQ-iEUauYJdn9FerYrvEyl88KdkzryYGQvvoSTdJxDc

All thanks go to Mystory. Congratulations to him :)