yashsingh1/xdaforums huggingface dataset:
[Android General] Don DD:
The stock rom is already rooted, you don't need a recovery to install supersu. Just install https://play.google.com/store/apps/details?id=eu.chainfire.supersu

If you still need to instal a recovery, first install https://play.google.com/store/apps/details?id=com.cgollner.flashify

then find a suitable recovery .img file and install it with flashify app.
[Android General] vuckovic_stefan:
Thanks man but after 2016 updates Elephone removed root and broke recovery...

I tried to flash twrp via sp flash tool but nothing happend. Than i tried to flash older stock rom's recovery again nothing. I dont know what they did but its surely broken...

Thanks for your answer, i already tried that and root is not available...
[Android General] jeansilva:
Cameras crash after some time using stock ROM - Please help!

Hi!

I am having problems with the stock ROM for this smartphone. The cameras (rear and/or front) crash all the time after first launch. I've tried to boot up, flashing stock ROMs again (including OTA), wiped cache, used 3rd. party apps, official Google Camera app, etc., but nothing has worked for me.

I am supposing it's not a hardware failure, since the cameras do work for a while - then after some time they crash and start to appear the following pop up message: "Can't connect to the camera".

Tried other custom recovery ROM (Flyme) but the problem remains the same. Also tried to install all other stock ROMs + format the memory through the Flash Tool - again, no success.

Any help/feedback will be highly appreciated.

Thanks!
[Android General] Kenif1983:
DCU rom is excellent. Try that.
[Android General] ruchimes:
I have the same problem right here.

Flashing some roms and no success...

I'll try the dcu rom
[Android General] vuckovic_stefan:
Probably is hardware problem.... Do you have warranty?
[Android General] ruchimes:
I don't think is hardware problem

Work well for a while sometimes, then stop working.

DCU ROM have the same problem to me.
[Android General] vuckovic_stefan:
Aha, i was think it doesnt work at all...

Then wait for android 6, its going out soon, elephone officialy confirmed, they said its going out soon. So then u will see if its going to solve your problem.

I am on latest stock, 28.04.2016 and camera its working fine, also they introduced some other options...
[Android General] ruchimes:
Where can I download that stock ROM 28.04.2016?

the latest I Found is 02.18.2016
[Android General] vuckovic_stefan:
http://4pda.ru/forum/index.php?showtopic=686517&st=1420#

I think that update had malware, so flash this one.

Instructions. Use spflashtool, and use just download mode, never format and download or something like that, remeber don use format :). U have on elephone forum instruction bu ethan.

And use win 7 or xp.

Let me know did u solve problem with camera.

Maybe it is connector on motherboard, did it fell on you?

---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------

https://cloud.mail.ru/public/Dk5Z/bPtSA85dd
[Android General] ruchimes:
I am going to try at night, now I have not a computer

Yes, the mobile have felt sometimes, but then

The camera would not work never, not like it is working now, randomly...

If I open the mobile can I see if it is something with a bad connection?

Thanks a lot
[Android General] vuckovic_stefan:
Yes but i would not reccomend u do that if you are not scillful and you will loose waranty.

I would always go with warranty first...

Let us know if u solved the problem with latest stock rom...
[Android General] ruchimes:
I discovered it is a hardware problem.

When the phone is without the back case, the camera works fine, but when I put the case in his place, something happens like the case presses the camera and don't work...

I'm going to use the warranty or maybe try to make the back case not to press the camera.
[Android General] vuckovic_stefan:
Its good you found what is the problem! Best is to go with warranty...
[Android General] ecklumi:
Hey guys!

I have a question: I would like to be able to turn off and turn on root. (not turning off 4ever) I think my phone is rooted, and I found a seems-like-a-good guide for installing magisk, however the guy uses a different phone, and I don't know, I just want to make sure it will work with mine as well?

Can u help me?

(here is the guide: 3w.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/

hope link works)
[Android General] puzzitta:
Update

Hi guys, I installed the version of 10/31/15 stock rom and would like to install one of 04/28/16, but by me firmware updates from the 2/17/16. I still have not root your phone. Thanks in advance good day
[Android General] puzzitta:
Ora update

Hello guys, I found this on baidu should be official update p6000 pro 4/28/2016

http://yiyun.baidu.com/wap/link?sha...843&third=3&dir=/K502T/P6000 pro/大象P6000 pro量 % E4% BA% A7% E7% 89% 88% E6% 9C% AC% 2F2016-4-29 & page = 1 # list / path =% 2FK502T% 2FP6000% 20pro & page = 1

could you tell me how I can update via ota update.?Thanks in advance
[Android General] pamigianleo:
404 error

Hello everyone.

I recently bought this mobile phone (p6000 pro 3gb) and I would like to try the eragon rom.

Unfortunately, the download does not work. 404 error

how can i have this rom.

Thanks for the attention
[Android General] skeleton1911:
Sry. Not available anymore

Gesendet von meinem U_Pro mit Tapatalk
[Android General] pamigianleo:
lineageos 14 MT6753

Hi everybody.

I found this rom - lineage 14 - for MT 6753

https://mega.nz/#!fxU2DZSZ!7_cGcFC2T8qNwJMdZ7cCjA3D8Xb00h9eYqdUf-oRSAM

and I tried to port on the p6000 pro using as a basis the

- lineage-12.1-20180121-UNOFFICIAL-p6000_pro.

Unfortunately with great failure. (I'm not expert).

There is someone who can help me in this project.

The p6000 pro is a good device but not being able to install more modern os is really a big problem.

Thanks in advance
[Android General] awl14:
What is so bad with LineageOS/CM 12.1? In my opinion, it is a much bigger problem not to be able to install Android security updates than using an older Android version as such.

As my above ROM (LineageOS 12.1 [AOSP 5.1.1] for Elephone P6000 Pro (K01TS-A) with 2018-01-05 security patches) has all relevant security patches up to January 2018 (2018-01-05), it is much safer to use than any unpatched Android 6.0 or 7.1 image...

Best regards,

awl14
[Android General] pamigianleo:
Hello.

I'm in agreement with you. security is important.

I tried the rom lineageos 12 and I find it excellent. really a great job done with passion.

but newer OSs have more customization and best battery management.

and then ... you want to put the taste of experimenting, changing, trying ...

What do you say? step to IOS with its chains?

:)
[Android General] awl14:
I say I don't really need any of the features of more recent Android versions. The only possible drawbacks I currently see is when P6000 Pro hardware is too slow for an app (e.g. 3D-games) or an app requires an Android API level of at least 6.0 or higher.

Otherwise I am still fine with my P6000 Pro, now that security (missing patches) is no longer an issue... :)
[Android General] Duron73:
Hello

I installed this rom to be updated with security issues, thanks for all the work done.

Unfortunately I found small problems that I can not solve:

- Each time the phone is rebooted, reset the time and date of the same until it is synchronized with the network or with the sim signal

- the 4g signal is weaker than the original rom

Has anyone else encountered the same problems?

Thank you
[Android General] awl14:
This indeed is a known issue that affects me as well, but unfortunately I have no idea of how to resolve it. On the other hand, I clearly think that this issue is really minor...

Are you 100% sure that you are comparing identical scenarios here? Which version of the stock ROM are you referring to - the latest K01TS-A.A.vA0S.E1.160428 (from which the device and vendor tree binaries have been copied)? I haven't noticed any weak signal issues myself with CM 12.1 - neither with 4G, nor 3G, nor 2G. Note that IMHO, wifi/wireless even works better with CM 12.1 than the stock ROM.

Best regards

awl14
[Android General] Duron73:
So I'm not doing anything wrong with the installation procedure if the "date resets problem" is presented to others, good to know, at least I'm sure I did the installation correctly :)

No, I'm not 100% sure, but in the same places where I used to take the 4g I'm currently taking the 3g +, but then again it's a minor problem, everything else works perfectly.

Thanks again for all the work done!
[Android General] awl14:
Have you checked that 4G is indeed set in the SIM settings?

I think that CM 12.1 determines the defaults for the connection mode differently than the stock ROM: For me, the stock ROM always showed 4G for both SIM cards/slots as default, even though my second SIM card (as well as AFAIK the second SIM slot in the P6000 Pro) supports only 2G. CM 12.1 has a correct default of 2G for my second SIM.

So maybe the default setting for your SIM1 has been set to 3G by CM12.1?
[Android General] Duron73:
From the sim options show 2G-3G and LTE not 4G.

Is setted as LTE.
[Android General] awl14:
Yes, sorry, I meant whether SIM options setting is set to "LTE" for 4G.

Sorry, I have no other ideas then. To the best of my knowledge, the mobile connection in the phone app is handled through the binaries from the device tree, and these have been taken from the most recent 160428 stock ROM...

Best,

awl14
[Android General] Duron73:
Do not worry, I'm still happy to have received an update to the security of the phone, the problems are less than the benefits

thank you
[Android General] Duron73:
An update for those who could have the same problem:

I followed a guide to reset the negotiation from my mobile phone to the network and then try to force the recognition of 4G/LTE ed it worked even if it was not specific to my model.

They are simply basic tips to try.

http://androidflagship.com/17000-fix-lte-not-working-problem-oneplus-one

The first 7 steps were enough to solve and get a rock solid 4G :)

So the problem was not the fault of the rom but it was between my provider and my phone.

Thanks
[Android General] awl14:
Updated to cm12-amami Android Security Bulletin 2018.06.05 :)
[Android General] awl14:
One more time, updated to cm12-amami Android Security Bulletin 2018.09.05 - download location still stays the same :)
[Android General] awl14:
And another update to ASB 2018-12-05 (including some fixes to avoid German O2/E-Plus SIM/network combinations being detected as national roaming).

Download location as before:

LineageOS 12.1 (aka CyanogenMod 12.1) for the Elephone P6000 Pro based on AOSP 5.1.1

Have fun! :)

awl
[Android General] awl14:
As cm12-amami has just been updated to ASB April 2019 security patches, I will also provide a new build for Elephone P6000 Pro to arrive most probably on Good Friday. :)
[Android General] balfek:
I'm glad to hear :)

what will be the base of the new build - cm12 or cm14?
[Android General] awl14:
CM12 (due to the use of cm12-amami, which backports ASB patches through the great initiative of the cm12-amami team): https://xdaforums.com/sony-xperia-z...neageos-12-1-z1c-current-sec-patches-t3614936

I've always found any efforts to port CM14 to the P6000 Pro to suffer from battery drain and other instability issues probably due to incompabilities between its 5.1.1-based device/vendor tree and CM14 binaries...
[Android General] awl14:
Another update of my ROM based on cm12-amami, updating security baseline to ASB 2019-04-05 has just been uploaded.

Download location as before:

LineageOS 12.1 (aka CyanogenMod 12.1) for the Elephone P6000 Pro based on AOSP 5.1.1

Have fun!

awl
[Android General] kaew158:
Is it support WiFi 5.0 GHz (802.11n)?
[Android General] awl14:
Honestly, I'm sorry, but I fear you will have to try this for yourself to definitely find out.

My custom ROM definitely uses the latest binaries from the Elephone device and vendor tree (of the 2016.04.29 ROM), but I fear that there are either different hardware revisions of P6000 Pro, of which some do not support 5G WLAN, or different driver versions, or different country settings, of which at least some clearly some do not (properly or not at all) support 5GHz. IIRC, in theory the official specs say that 5GHz should be supported.

My own phone (of the first series, produced early in June 2015) here in Germany does not support 5GHz with my custom ROM, but it did not support it either with the stock ROM. The same applies to two other P6000 Pro devices that I had access to in previous times here in Germany. (On the other hand, it supports LTE in Germany very well with all needed frequencies.)

If you are currently able to access 5GHz WLAN with the stock ROM (which ROM build date?), I'd encourage you to try with the custom ROM. As you need to install a custom recovery anway during the process, you can very easily restore a backup of the stock ROM if the custom ROM does not fulfill your needs.

Hope this helps & best regards

awl
[Android General] kaew158:
Thank you very much for you advice.
[Android General] Pantantrollo:
Hello, (sorry for my bad English)

First of all, thank you for the work done on this ROM that you are publishing and updating.

Now, the doubts :)

I have installed several ROMs, in addition to this one, I comment to put you in the background

Currently I have the latest official ROM, based on Android 5.1, I ended up going down to this one, because in yours, there are some "little things" that don't work at all.

**1- the app "Cube ACR" gives notice that you will not record (and not record) voip conversations, such as telegram, whatapps, etc, which does work with the last official ROM.

**

**2- When I connect via USB to a PC, to share the connection, it only works, on the PC, or on the phone, but not both at the same time. On the phone I have 2 SIMs from different companies and they don't seem to work in any.

**

****Note, with the original ROM, if they work well. With the last official ROM, after entangling for a while, I get the second SIM (the one that does not support 4G) to work well.

****

****With another ROM, "elephone-p6000-pro-lineage-14-1" (web needrom), and based on android 7.1, they work without problem. This ROM seems to work quite well, except also for the telephone call recorder, Cube ACR, which also does not support voip, (it may in the end have to do with the kernel, and not with the ROM itself, although I do not understand much of it)

Thx, Un Saludo
[Android General] awl14:
Hello,

I never had the requirement myself to record VoIP, so I had not looked into this topic until today.

As this seems to work fine with the stock ROM, as you are describing, and as I am using the kernel source as released by Elephone for the device drivers and all the original hardware-related binaries from the stock ROM, I assume it should be possible to get this to work using one or both of the changes to build.properties as mentioned in several threads on xda and others:

persist.call_recording.enabled=true
persist.call_recording.src=4

The reason why this seems to be disabled in CM builds by default is legal restrictions/regulations in multiple home countries, but the build.prop change is said to allow to override this.

Haven't tried this myself, but I hope you should be able to test it out with my ROM using Magisk and the MagiskHide PropsConfig module immediately (by setting the properties mentioned above as additional custom properties).

I am open to try and set these properties on subsequent builds, but please be warned: It might take a quite while until I find the time to release an updated build - don't expect anything before the Christmas holidays, to be honest... :(

I'm not aware of any issues related to USB connections. Please be much more specific about what you are trying to do over USB: What do you mean by "sharing"? Sharing the internet access of the device to the PC or the other way round (i.e. "tethering" via USB - as opposed to WLAN)?

Again, I am not aware of any issues with regards to the dual SIM functionality. I am using it myself in dual SIM mode, which works fine for me. What are your desired providers for SIM 1 and SIM 2? Can you post a full "getprop" output from a P6000 Pro command line shell ("adb shell getprop")?

I have also checked out that ROM (possibly an earlier build version). If you find that this ROM runs fine for you, feel free to try the above hints (persist.call_recording.enabled) using Magisk with that ROM.

For me, this ROM was not appropriate for daily use due to its battery drain - I assume that it runs too many background tasks that are not working for P6000Pro, but eat up battery life because they wake up in regular intervals just to fail another time... :(

Hope this helps & best regards

awl
[Android General] Pantantrollo:
No problem, there is no hurry :)

As soon as I switch back to this ROM again, I will test the changes you note in the build.properties

Sorry, yes, I meant, as you said, to share via USB the internet connection with the PC (tethering "via USB), in which either the connection only works on the PC, or only the connection works on the mobile, but not at the same time

I will also test the changes you mention above in the build.properties. Personally I have not noticed an excessive consumption of battery with respect to these ROMs based on Android 5.1, I usually disable many services and app starts that I do not use

Thank you very much for the ROM, and for the prompt reply :)
[Android General] awl14:
Can you still be more specific please: Which "general" USB mode is your device in when you see the issue (MTP, PTP, mass storage - I assume it won't work in "loading only"), and do you have "USB debugging" enabled at the same time? When you describe your scenario exactly enough, I may be able to reproduce it... ;)

And do you try to share the phone's mobile internet connection, or its WLAN connection to the target PC that does neither have WLAN nor other net access?

The battery drain I noticed when I tested this ROM was not due to installed apps, but I was referring to "system" services that you can neither see in the "Apps" dialog in Settings, nor activate/deactivate without root access (most are even started during init). You often can use logcat to browse error messages in order to detect these scenarios...

You're welcome, and as stated in the ROM's readme, most of the thanks go to Deepflex and the cm12-amami team - I mainly assembled these two parts into one ROM :)

Regarding changing build.properties in order to try to get VoIP recording to work correctly, please report back here aubout your results when you have found some time to try it out... :)

Best,

awl

---------- Post added at 10:08 PM ---------- Previous post was at 09:58 PM ----------

Ah, and one more thing regarding the USB tethering issue: What operating system and (if on Windows) MTK driver or (if on Linux) kernel version are you using on the PC? I think I have seen official Android docs by Google stating that USB tethering to Apple MacOS is not even expected to work... :confused:

And I just remembered that for quite a while, I had issues on IIRC Ubuntu 16.04, where USB connection was flaky all the time, while at the same time and to the exact same PC (i.e. hardware identical), connection was rock-solid to Windows 10...
[Android General] Pantantrollo:
All the tests have been with the latest version of windows 10 64bits, basically without changes, since they were all done in a couple of days, the 3 ROMs, yours, the last official, and the lineageOS based on 7.1.

In the last two ROMs that I mention, if tethering via USb works well, that is, I have an active connection on the PC as on the smarphone at the same time.

Of course, with USB debuging and MTP enabled :)

No problem, as soon as I change ROM again, I will publish the results of changing those values in build.properties :good:

Un Saludo
[Android General] balfek:
sorry for my lamness...but how to install securty patches?

"P6000_Pro_BuildScripts_cm12.1-deepflex_SecurityPatchLevel-05Dec2018.tar.bz2" - i found this next to custom rom zip....AND there is no instruction about this in the README.TXT....why?

and what is the purpose of this int the custom rom zip: "gapps-config.txt" ???
[Android General] awl14:
Hello balfek,

The answer is simple: You don't/you can't - you can only install the most recent complete ROM image as provided by me. In an ideal world, I would be willing to compile and offer them every month (as long as cm12-amami does offer their security updates). But due to time restrictions in the real world (this is nothing but a hobby) I only find time for doing so sporadically - maybe three times a year.

(Note that this is Android 5.1, so installing security patches on a single patch basis was just not invented...)

So for now, please use my latest build (ASB 2019-04-05), but please stay tuned: Once my Ryzen 9-based new home workstation :D has been fully set up, I plan to provide a current build based on cm12-amami ASB 2019-12-05 release until mid-January... :fingers-crossed:

This is only my personal build script to start the whole build process based on deepflex's work and cm12-amami on my machine - this was intended to see whether there is some interest by other people to also build a ROM on their own - but you are the first one to ask... ;)

The gapps-config.txt provides some default values for the gapps package that provides you with Google standard apps on top of LineageOS/CyanogenMod 12.1. IIRC, if it is present in the current directory when you install a gapps ZIP package, it will automagically be taken into account. You may want to do some research yourself about which apps you do like to install by default, and which you prefer to not be installed, and modify the file accordingly.

Hope this helps, and have a merry Christmas, great holiday season and a happy New Year! :cool:

awl
[Android General] balfek:
hi, happy new year :)

i made as you advice: stock rom, then jemimi recovery, clean install, your rom, gapps5.1, then instantly magisk....

but i have a lot of problem:

1. no deep sleep (max 5-8%) - kernel wakelocks: mainly powermanager, but lot of partial WL and alarms too (eg. from android system, calendar storage...)

2. very fast draining - around 10-12h with 2-3h SOT (and because there is no no deep sleep...)

3. i cant see the 4G, 3G, 2g signs on status bar - just an exclamation mark.. (ok, sometimes, eg !Gsign showed up, when the phone is freezing before self-reboot...but after rebbot there is just again an exclam.mark)

4. i cant delete system apps (ok, i use magisk) with any apk (Link2SD, SDmaid, Root explorer, etc with root permissions) - sometimes they write it out: "failed removing", sometimes suggest it was successful...but after reboot i still see the deleted apps...

5. KErnel adiutor doesn't see "wakelocks"...

6. In the LSpeed apps'log I see this (after when it try to apply aggressive doze or something): "device/kernel doesnt support DOZE"

7. I use Greenify...no affect...no deep sleep

8. sometimes its freezing without any special cause

why dont your kernel support DOZE ? maybe its buggy?

how can i change kernel?

what apps do you use for blocking wakelocks on Lollipop? I couldnt find any apps for this purpose.
[AT&T HTC One (M8)] Siknote:
My rooted M8 was running Venom ROM (S-on) I foolishly tried to install Xposed Framework, messed with some settings and ended up like this. (Yeah, i know, i know) It boots into menu, but recovery just reloads hboot, i dont see bootloader, and theres no OS installed. tried adb but every command yields "device not found". I've tried a couple different toolkits as well. please help. I'm afraid I've bricked it. :mad: