yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] bigrammy:
Who said you were a Numpty :confused:

The custom partition backed up without error and still does so your comments are not really related to this one. :confused:

Sorry if you felt like a Numpty it wasn't my intention to make you feel like one and I was only trying to help you. :rolleyes:

OK SORRY I just re read your OP and noticed you did not specify any partition :eek:

I must of assumed you meant the custom partition because I had just added the option to backup the custom partition :confused:

I had worked for many hours so must of been a bit confused :o

Anyway my apologies :D
[Miscellaneous Android Development] ac0935p:
Hi [MENTION=3924647]bigrammy[/MENTION]

Numpty was my own appellation - poking fun at myself. No accusation was intended...

Your hard work is greatly appreciated.
[Miscellaneous Android Development] bayad:
A new ROM has just made its appearance : Elephone P6000 01 CM12 a1 (http://pan.baidu.com/s/1m6E2U). If a courageous wants to test it... :D
[Miscellaneous Android Development] HypoTurtle:
Has any one restored userdata with SPFlash?

It seems to only want to restore about 600MB, and changing the partition size in the scatter.txt doesn't seem to affect this.
[Miscellaneous Android Development] ac0935p:
Sounds risky, I think the clue is the "A1" part of the name - presumably Alpha 1. Hmmm. But let's not knock it, at least they are still trying stuff out.

Here's the thread for it: http://bbs.elephone.hk/thread-3173-1-1.html#.VQw32o6sVqs

And a comparison video between lollipop, flyme and CM12 all running on P6000:

https://www.youtube.com/watch?v=BA0_IrlWkUw#t=44
[Miscellaneous Android Development] greekfragma:
After some more testing with PhilZ Touch recovery everything works ok. Flashing-Restoring-Backup Data.

One other thing that I need to inform you and it is kind of weird but happy about it.

As soon as I flashed Philz touch recovery, on next reboot the phone was recognized on my Windows 8.1 PC, and also it was mounted correctly as a storage device. So now I am free to move pics and stuff from SD card without the need of adb mounting. :D
[Miscellaneous Android Development] bigrammy:
Hi bro,

Are you on KK Rom or the 5.0Beta :confused:
[Miscellaneous Android Development] greekfragma:
ΚΚ man :)
[Miscellaneous Android Development] bigrammy:
Hi bro,

Sorry for the quick reply but real busy at work :eek:

Last shift day tonight thank goodness :D

Just thinking out loud but I am now thinking we may need a bootstrap / safestrap setup as I can think of no other reason why 4.4.4 kernel would not work :confused:

The HTC ONE M7 I have uses the KK Kernel and works fine on L so It has to be a kernel check by the LK.bin that's blocking the kernel :(

I will have a play around Tomorrow. :fingers-crossed:
[Miscellaneous Android Development] HypoTurtle:
The weird thing is I'm pretty sure I've run Flyme while using the LP lk.bin so it's just blocking the recovery kernel if that's the case.
[Miscellaneous Android Development] Santhosh M:
Could you guys explain the situation you are facing with recovery. Maybe if my help is needed i could do my share if possible.
[Miscellaneous Android Development] HypoTurtle:
Two things:

1. We have a Touch recovery KK kernel (from the Just5 blaster) that won't boot while on the L build (new preloader, lk.bin etc.)

2. We don't have a recovery that can handle the L data encryption.

- I've build TWRP on Omni 5.0 with the changes made above to carliv's recovery device tree (as well as the other cm to omni changes) that build isn't booting for me yet, but at least it compiled - it looks like I'll need to rebase to Omni 5.1 to compile it with 64-bit libraries.

I haven't rewrite the mkmtkbootimg.mk -- so just repacking the booting CWM recovery we have with the compiled ramdisk.
[Miscellaneous Android Development] bigrammy:
Hi HypoTurtle,

Well that may be the case bro :eek:

5.0 Beta3 was pretty well locked down for a Elephone ROM eg: Not rooted no adb which may have been by design rather than error. Now we also have a bootloader fastboot etc which were pretty rare as far as I know for most MTK's :confused:

Hi Santhosh,

Your expertise may well be very helpful bro :D

What Hypoturtle has said below is true but I will try give you a little more detail as we did a lot of testing via PM :eek:

So I will give it bullet points for clarity.

1, We are running Elephones 5.0Beta3 Lollipop ROM which is as described above so we needed a custom recovery.

1. CWM Recovery for the KK 4.4.4 would not boot on this 5.0 ROM

2, We noticed the Boot/Recovery structure had changed again on 5.0 :rolleyes:

5.0 boot/recovery.img structure

base:0x40078000
ramdisk_addr:0x44000000
second_addr:0x40f00000
tags_addr:0x4e000000
page_size:0x800
name:K01Q-E.L.vA00.0
cmdline:bootopt=64S3,32N2,64N2
padding_size:0x800

3, So we repacked CWM Recovery using the new structure but still not boot up :(

4, Repacked CWM Recovery again but swapped the KK kernel for the Lollipop Kernel and It boots no problem :good:

5, So CWM with Lollipop Kernel works but no touch functions and it cannot handle encrypted data The same is true for Philz and [MENTION=5186178]carliv[/MENTION] CTR recovery.

6, So we now we try TWRP KK Kernel No boot :(

7, Repack TWRP using Lollipop Kernel and it boot up but then Force Closes

So providing you disable the enforced encryption the carliv CWM works fine with no backup issues :good:

I Found some mtk compiling tips Here they recon to reduce the compile time by as much as 50% :eek:

Also some tips for unknown board configs (defaults) ;)

EDIT: Well bang goes my theory the lk.bin (Uboot) makes no difference same results as before :(

Its back to the drawing board and some more head scratching for me :laugh:
[Miscellaneous Android Development] HypoTurtle:
[MENTION=5480061]Santhosh M[/MENTION]

This is gonna sound a bit stupid as it's something I noticed week(s) ago but didn't give it too much attention, but the recovery (and/or recovery kernel) is dependent on the boot.img (probably the cmdline/bootopt).

If you flash a custom KK rom you can (or rather will have to) flash a KK recovery.

This means the KK touch kernel and TWRP works with every thing else (bar boot.img) being from a LP SPFlash.

Still need a working recompile for the userdata - best I've come up with (with the help of [MENTION=5480061]Santhosh M[/MENTION]) is a brief flash of an attempted boot with 64-bit recovery compilations. At least now I should be able to test 32-bit compilations. Would be handy to add a backup/restore of recovery partition like the way nvram is backed up.

The LP kernel I'd say at least has CONFIG_COMPAT=y so that it can be used for both 32-bit and 64-bit.

(I have tried to compile the source we have as 64-bit but getting too many errors for me to handle given my inexperience with C/C++ and with MTK kernels.)
[Miscellaneous Android Development] bigrammy:
Hmmm I think you may have hit on something we can at least cross check. :fingers-crossed:

Is anyone one on a KK ROM so we can compare the outputs of the following ???

from adb shell

cat /proc/cmdline

output for 5.0 Lp =

root@k01q_e:/ # cat /proc/cmdline
cat /proc/cmdline
console=tty0 console=ttyMT0,921600n1 root=/dev/ram vmalloc=496M slub_max_order=0 slub_debug=O androidboot.hardware=mt6752 bootop
t=64S3,32N2,64N2 lcm=1-ili9881_hd720_dsi_vdo fps=5397 vram=13172736 printk.disable_uart=1 bootprof.pl_t=3828 bootprof.lk_t=1521
[COLOR="red"]boot_reason=4[/COLOR] androidboot.serialno=0123456789ABCDEF androidboot.bootreason=wdt_by_pass_pwk [COLOR="Red"]gpt=1[/COLOR]
root@k01q_e:/ #
C:\Users\bigrammy\Desktop>

Looking at this it seems it checks the gpt (partition table) which has changed from KK and it maybe it needs all 4 parameters to be correct before booting (boot_reason) like an updater.binary does :confused:

It would be nice to compare without reflashing my ROM :fingers-crossed:
[Miscellaneous Android Development] peschak:
adb shell output

This is the output on KK:

C:\Users\Gero\Downloads\mtk1>adb shell

root@k01q_e:/ # cat /proc/cmdline

cat /proc/cmdline

console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 vmalloc=496M bootopt=64S3,

32S1,32S1 lcm=1-ili9881_hd720_dsi_vdo fps=5411 vram=13631488 printk.disable_uart

=1 bootprof.pl_t=999 bootprof.lk_t=3026 boot_reason=0 androidboot.serialno=01234

56789ABCDEF

root@k01q_e:/ #
[Miscellaneous Android Development] HypoTurtle:
TWRP V2.8.6.0 for LP

32-bit TWRP with KK Touch kernel and L crypto.

Available here

This requires a KK boot.img, but it allows you to backup/install to encrypted userdata partition on Lollipop (untested on KK).

Other than the obvious graphical issues, please report any other issues.

Fixed GUI version

Dev related, the TWRP will compile and boot when compiled as 64-bit, but without a 64-bit Touch kernel it isn't much use.

64-bit available ==> here awaiting a touch recovery

Edit. For Completeness

TWRP - 32bit compiled - 64bit kernel (for use with L).
[Miscellaneous Android Development] bigrammy:
Congratulations bro :highfive:

I will do some testing on Monday when I flash back to stock KK as I have some more testing to do for a friend also :good:

Still at work until then but I will see if I can snatch a little time to play with the 64bit version before Monday. :cool:
[Miscellaneous Android Development] :
EDIT: The 32-bit version doesn't boot? I'm on the 28 March build of Android 5.0.

EDIT 2: You can use https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager to install/flash ROMs through Android. :laugh:

Great work :good:
[Miscellaneous Android Development] xenonism:
It booted for me when I gave Lollipop a shot. Remember you have to flash a KK boot.img as well.
[Miscellaneous Android Development] HypoTurtle:
Think you missed this part: KK boot.img is needed as well. Unsure why exactly at this point I've flashed a few attempts to get it to boot with a L kernel changing the cmdline but getting no where.

I've botched up my build environment a bit (or updating repo broke something), so need to fix that before building again. (the attached 64-bit I think still has the graphical glitches - not sure if I have compiled a fixed one)

I see no reason why OpenRecoveryScript won't work here, adb works fine etc. but as the new 5.0 ROMs (v1 and v1.1) are not encrypted by default the CMW-L is of more use.
[Miscellaneous Android Development] :
Will using the KitKat boot.img affect performance in any way? What's the difference between the 32-bit and 64-bit one?
[Miscellaneous Android Development] HypoTurtle:
You'll have to flash back to 64-bit/L/5.0 boot.img to boot 5.0 - it's just the only way of using touch TWRP atm.

The themes also work fine as well - Material design for example.

All custom ROMs thus far are based on 4.4.4 so the 32-bit Touch TWRP will work fine with them.
[Miscellaneous Android Development] xenonism:
It's not obvious so I'll try to explain the situation here: the 32-bit Lollipop recovery and the KK boot.img are only used once to restore your data after you move from KK to Lollipop. It's the only way to do it.

After that, you need to flash Lollipop's boot.img and the 64-bit CWM recovery (or stock Lollipop recovery). If for whatever reason you don't need to restore anything, you can just ignore all this.
[Miscellaneous Android Development] :
What if I want to install Xposed for Lollipop?
[Miscellaneous Android Development] HypoTurtle:
Xposed doesn't support 64-bit Lollipop; afaik. So no luck there.

And you are only changing the boot.img not system.img:

KK boot.img to boot into 32bit TWRP (with touch)

L boot.img to boot into 64 bit L system

You can flash the boot.img's with recovery/SPFlash/adb/fastboot etc. but if know you need access to recovery while you won't have access to these (a backed up boot.img is probably ideal); then you'd be better off with CWM/Carliv: unless you have encrypted data and would like access to /data and /data/media.
[Miscellaneous Android Development] :
The latest version of Android 5.0 that will ship with the P6000 is out!

http://bbs.elephone.hk/forum.php?mod=viewthread&tid=2443
[Miscellaneous Android Development] ghost45:
Hi Big,

Hello to everybody, I am carefully reading and following all your steps.

Because I'm about to start, I too short, an adventure with the new updates on a lollipop on the zopo phones.

So from what I understand only the TWRP recovery work properly?
[Miscellaneous Android Development] HypoTurtle:
All the recoveries work correctly, the thing is that TWRP is the only recovery that can handle data encryption.

And with the initial Lollipop builds being forceencrypted it was needed to access /data while in recovery; the forceencryption has been retconned by google (performance issues with the nexus'es).

The other issues that may arise are touch support in recovery (needed for TWRP), the P6000 kernel doesn't have touch but the 'clone' - Just5 Blaster - did provide touch in recovery.

And for some reason the recovery kernel needs to be the same arch as the boot kernel - i.e. as the Lollipop kernel will be a 64-bit kernel this will need to be used in recovery as well - which caused an issue here as we only have the 32-bit touch kernel from the Blaster.

The other recoveries work fine (as long as you don't need access to encrypted data), with just a simple kernel switch - and cmdline - from KK to LP

What's the current state recovery-wize for the Zopo?
[Miscellaneous Android Development] bigrammy:
+1

Thanks For the explanation bro I have been at work all day. :highfive:

Is anyone registered on the lenovo forum ?? sevenmax as done a TWRP 2.8.6.0 for the P70 it would be nice if someone good share it for testing purposes :o

Lenovo P70 TWRP v2.8.6.0 Recovery
[Miscellaneous Android Development] HypoTurtle:
Copy here

We have v2.8.6 but the additions - flash .img's look useful - and the default material design theme.

Personally think dark version is better
[Miscellaneous Android Development] bigrammy:
Thanks bro I will take a look shortly....

BTW have you noticed on the mtk cpu app in beta3 version all touch functions seem to be handled by cpu1 and not cpu0 :confused:

I am just trying to check if cpu1 is activated or kept activated during in recovery maybe this could explain things if it's not. :eek:

Maybe the blaster kernel keeps the cpu1 active :confused:

Just a theory so far :laugh:
[Miscellaneous Android Development] HypoTurtle:
Not something I noticed... They've removed that app from the latest ROM, but all 4 cores seem to be scaling equally in kernel toolkit.

Edit. Just pulled the app from the system.img and that seems normal to me, screen untouched just cpu0 is on, with touch the load is shared between cpu0 and cpu1.
[Miscellaneous Android Development] bigrammy:
Yes it seems thats not the problem :(

Back to the drawing board then :laugh:

I will take a look at sevens recovery tomorrow but without a kernel I think we will still be stuck :(

PS: On a side note here is a handy little tool made by umi most functions work for flashing recovery's etc etc maybe you know about it already but here is the link anyway. ;)

HERE I just ordered the Hammer model as I need a tougher phone :D
[Miscellaneous Android Development] Baltyre:
Hi, my P6000 stock rom is a Androida 5.0 Lollipop ROM 20150417.

I try to flash the cwm recovery, but it don't seems to work, there is anything i can do ?
[Miscellaneous Android Development] peschak:
specify please. Stock rom? was the phone delivered with this ROM?

Which program do you use for flashing?

Do you have hatte scatter file if you use SPFT?

Are there any errors shown by flashing program?
[Miscellaneous Android Development] bigrammy:
All these recovery's are for android 4.4.4 KK only as stated in the OP and will not boot on Lollipop 5.0 due to silly Kernel version checks which we can't seem to bypass :mad:

Elephone have not yet managed to fix the touch in recovery mode (Kernel issue) on Android 5.0 Lp so we can not use TWRP which is the only recovery able to handle encrypted data so far anyway and this needs a working touch. :rolleyes:

See [MENTION=4056517]HypoTurtle[/MENTION] thread here for tips and info http://xdaforums.com/android/general/p6000-thread-bug-fixes-faq-info-t3028845
[Miscellaneous Android Development] Baltyre:
Stock rom, i used flashify apk, no error.

If i install a 4.4 rom and reflash the cwm, it will be working ?
[Miscellaneous Android Development] HypoTurtle:
The 5.0 CWM can be found here => https://mega.nz/#!6wJTAR6T!UlNqNd80frBvQ7mUsyrVD9K6EfTrKOmZ50iYZ8I7dF8

That's from #3 on the thread [MENTION=3924647]bigrammy[/MENTION] pointed you to.

If you flash 4.4 then yea if you reflash the cwm from this thread it will work.

After you install just check /system/etc/install-recovery.sh .

If it looks like it's applying a patch then remove it - if it just mentions SuperSU and just calls deamonsu then you can leave it.
[Miscellaneous Android Development] bigrammy:
Port of Lenovo Lemon K3 Note (K50-T5) CWM Recovery

Hi all,

I have just ported a recovery made for the Lenovo Lemon K3 Note (K50-T5) Android v5.0. :fingers-crossed:

I am not 100% sure but I think it has been compiled for 5.0 Lollipop. It seem's to be a [MENTION=4477466]cofface[/MENTION] CWM recovery dual language.

I can't check if it can handle encrypted data or not but you're all welcome to test it out. :good:

The .png's I used are very slightly off center and the text is a little bit big due to the difference in screen size & resolution between the phones.

https://copy.com/hrvQT6IGIgk0QURm

[MENTION=4056517]HypoTurtle[/MENTION]

EDIT: New link added see posts #228 and #229
[Miscellaneous Android Development] HypoTurtle:
Are you sure the wipe nvram should be in there?

As a guess I'd say no on the data encryption - mainly due to metadata not being mounted and TWRP needing it to be; even when data isn't encrypted.
[Miscellaneous Android Development] bigrammy:
Hmmm I never saw that :o

Seems it adds all partitions that's in one of the fastab files :eek:

I will try editing them so those options are removed just not sure which one it reads :eek:

The recovery contains minivold so maybe it will handle encrypted :confused:

I will kill the link and repost when fixed.

Thanks for the feedback :cool:

EDIT: [MENTION=4056517]HypoTurtle[/MENTION] I found the source it uses for the format options it's the /etc/fstab

New link https://copy.com/hrvQT6IGIgk0QURm

If anyone has encrypted data could they please test this recovery and leave some feedback. :good:

Attached some images. :)
[Miscellaneous Android Development] HypoTurtle:
Just thinking out loud in regards to touch, the other thing that the Blaster kernel provides is off-screen gestures. So could the two be related? ie. the top/ bottom/gesture layer is also being used by recovery. [MENTION=3924647]bigrammy[/MENTION] can you confirm off-screen gestures hammer?
[Miscellaneous Android Development] bigrammy:
Hi bro,

Umi Hammer has got working off screen gestures tap to wake etc with exact same touch screen as our p6000.

I have no idea why elephone can not or will not get it working on the p6000 :silly: :silly: :silly:

The P6000 simply does not load/poll the touch screen until you enter the full system environment when this is achieved the touch is then identified and loaded. :(

I cannot find anything that relates to this behavior or its cause it's very frustrating indeed. :D
[Miscellaneous Android Development] HypoTurtle:
Just an addendum/correction "The Elephone compiled kernels do not poll..." as the p6000 does poll touchscreen before system/zygote has started with Just5 kernel; ie not a hardware issue but 100% kernel related.

There are some sources about (lenovo/oppo) that might be useful for adding gesture support, perhaps something there will make recovery touch work, just need to see if ele... will let me look at their kernel source. The only reason I can see for consciously not enabling gestures is perhaps its a bit of a power drain.
[Miscellaneous Android Development] bigrammy:
The HARDWARE is more than capable as proven by the Blaster and Hammer so it's 100% a kernel issue adding gestures and anything else is just a tick option providing we have a nice clean kernel source. :crying:

Why they do not poll or maybe block the touch until full boot is a total mystery to me and seems pointless.....

You may find this informative https://www.kernel.org/doc/Documentation/i2c/instantiating-devices

I did do a quick check of the Lenovo source and some Files and folders are laid out a little differently when comparing our source code against the Lenovo A7000 namely the "mediatek" folder location which seems to contain all the gesture support files among many other mtk options :confused:

Not sure why this is placed differently unless it's a kernel version change ie 4.4.4 v 5.0 :eek:

The Lenovo source does not include our touch screen as an option :crying: so unless some really clever person can merge things we are stuck waiting for elephone again :cowboy:
[Miscellaneous Android Development] HypoTurtle:
Yea i've seen the lenovo source, personally I think the structure pretty much confirms that the 5.0 kernels have been done in house rather than based on source from mediatek.

I was thinking more, this: https://github.com/omnirom/android_kernel_oppo_find5/commit/dc2e72a3f6fa569d0076a696d91c5766ebe4fb5f changing files appropriately
[Miscellaneous Android Development] bigrammy:
:good:
[Miscellaneous Android Development] Penetratore:
a stupid question, but how can I enter CWM ? what is the button combination?

In a custom rom (f.ex on the SGS2) there was in the POWER options the choise to boot to recovery but in the stock 5.0 I dont see it.

Any tips?
[Miscellaneous Android Development] bigrammy:
App method: Use quick reboot from the playstore https://play.google.com/store/apps/details?id=phongit.quickreboot

Button Method: Power off. Then hold Volume UP and long press power button you will get a black screen with small writing use the volume up button to point to recovery press volume down to select it. The phone will then boot to the recovery.
[Miscellaneous Android Development] bigrammy:
Hi bro,

I noticed yet another release of CM12.1 from elephone and the change log says - Enabled touch boost to tune UI performance

Just wondered if you or anyone else has had a chance to check the Kernel to see if this has also enabled touch in recovery :confused:

I am at work tomorrow and have problems with the download just now so if anyone can share the boot.img of this last release I will test it tomorrow evening after work if anyone hasn't already done so.

Regards.
[Miscellaneous Android Development] HypoTurtle:
'Fraud not. Not sure what that 'touch' refers to - either the command/binary or something Volta related perhaps?
[Miscellaneous Android Development] Santhosh M:
Touchboost refers to kernel touch boost coding which is related with hotplugging. ( Like it calculates the touch boost delay time and does load calculations ). Not what is related to our recovery requirement.
[Miscellaneous Android Development] HypoTurtle:
I think [MENTION=3924647]bigrammy[/MENTION]'s thinking was that they've done something with kernel perhaps related to the touchscreen that may have inadvertently fixed the recovery touch.

What I thought it was relating to initially was the frequency control that's built into CM settings - the ROM creates/touch'es a file that the kernel reads from to control frequency/governor etc. - or is there something more to it, as I don't think that's any extra than normal CM stuff.

Edit. Yea - it seems to be just a governor; and I think ties in with Project Butter (not Volta - had those two mixed up a bit) - you touch the screen and the CPU goes to max as fast as it can to keep the UI as smooth as possible.
[Miscellaneous Android Development] bigrammy:
Hi,

Yes thats exactly what I thinking bro.

Ok so they still did not fix it then :crying:

I guess we will have to wait and see if the Just5 Blaster get's an L update but I wont be holding my breath. :laugh: