yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] superdragonpt:
Hi

FYI

These issues are related with

Mediatek's CorePilot

, these builds failed to integrate it. (Don't worry, this is not the only OEM making the same mistaque ... )

Core Pilot (Heterogeneous Multi-Processing Technology) and the way it handles the Cluster Migration groups.

Cheers
[Miscellaneous Android Development] GoJo ^^:
Going crazy with this now, how am i supposed to flash it? I tried flashify, rashr.. When i reboot to recovery, i got the "dead" droid pic, it's a fail! I don't get it.
[Miscellaneous Android Development] xenonism:
Actually...
[Miscellaneous Android Development] schizo99:
No recovery works

Hi all,

I tried the stock recovery but that only gives me the dead droid.

Any other recovery just hangs for a while then reboots the phone.

I tried flashing both using flashify and adb to no avail.

Since I understand that this is what's between me and the latest update any input would be very appreciated.
[Miscellaneous Android Development] bigrammy:
Have you got root and superSU installed??

Which android version are you on???

KK 4.4.4 or Lollipop 5.0

The ones in the OP are for KK only but there are some Lollipop non touch versions.
[Miscellaneous Android Development] andrei80:
Thanks for the great work. Flashed TWRP with Flashify, worked fast and great. I flashed the camera fix by zOrgent hoping it would make it more usable.
[Miscellaneous Android Development] Vixa:
Is there a way to install custom recovery on 5.0 because i'm so confused right now and cant install recovery.
[Miscellaneous Android Development] bigrammy:
Use the flashify app Here or Rashr Here from the playstore and flash THIS RECOVERY HERE ;)
[Miscellaneous Android Development] GoJo ^^:
Can't open your recovery link..

Always quote my messages so I get notified quickly!

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Same goes for the admin link (discussion thread)..!!

Always quote my messages so I get notified quickly!
[Miscellaneous Android Development] bigrammy:
What are you talking about :confused:

Link to the post with the broken links so I check them as I am not a mind reader.

and stop using the ! unless you are shouting at us in which case :mad:
[Miscellaneous Android Development] GoJo ^^:
Shouting on the web consist in writing in caps. Are you ok? Doesn't seem so. I'll keep using punctuation the way I like. The link is showing at the end of your post!!
[Miscellaneous Android Development] bigrammy:
Nothing wrong with me :D

Just gets annoying when people place random comments with no links to what they are talking about and no real explanation :crying:

I have hundreds of posts with links in this and other threads :silly:

So after looking in my crystal ball It comes to me that you mean this post Here :confused:

If it is this post to which you refer then all the links work fine :good:

If your explanation of punctuation is true then why would you use something that has no meaning :silly:

If you don't understand punctuation or it's use then do not use it as it can easily change the entire meaning of what you are saying.

Source

So the way I read your post is that you are shouting at me or demanding.

This is a forum for detailed technical information exchange and not facebook or some live chat site so there is no excuse for sloppy incomplete posts.

You are not a noob so should know better. :fingers-crossed:
[Miscellaneous Android Development] GoJo ^^:
You can see what I was talking about here.

Always quote my messages so I get notified quickly!
[Miscellaneous Android Development] bigrammy:
See how was I to know you were referring to the xda mobile app from your other posts :rolleyes:

Check your app settings so it sends the "Sent from my P6000" or whatever to at least give us a clue :(

I just spent the last hour checking my links THANKS. :crying:

I do not use the xda app so you would need to contact xda about broken links in that.

QA link is Here
[Miscellaneous Android Development] GoJo ^^:
That thing appear at the end of your posts.. So I guess you're the one who put it..?

Always quote my messages so I get notified quickly!
[Miscellaneous Android Development] bigrammy:
No thats auto generated by the forum's Auto Bot not me.

It will appear on all threads with a Q&A when you post in the main thread to remind you to post in the Q&A instead.
[Miscellaneous Android Development] Vixa:
I tried that method but when i flash recovery with these apps i get message that recovery is flashed and i try to reboot the phone in recovery without success, the phone just reboots and hangs for a while and than normally boots, so there is no recovery...
[Miscellaneous Android Development] bigrammy:
No idea mate works for everyone else.

What you describe sounds like you are flashing the wrong version for your ROM :confused:

Again If your on KK 4.4.4 ROM you need to flash the KK 4.4.4 recovery from the OP

If your on LP 5.0 ROM you need to flash the LP 5.0 recovery from the above Post or you could try these also Here in this Post for LP ROM
[Miscellaneous Android Development] bigrammy:
Hi guys,

I just got in from work and see the master has arrived here :D

I will need a little time digest all info and will probably not get time test things evening :( Work is always interfering with my hobby :laugh:

Carliv I did port your mt6595CWM from the zp999 thread :D but I was aware it was not fully functional and did not wish to pester you or declare it in your main thread until I was 100% sure all possible things were fixed. :o

I also ported CTR and TWRP (yuweng helped me with the TWRP port :good: ) while I can get all to boot up just fine I have no touch function on any of them :crying: (15 libminuitwrp.so tried with no sucess :crying: )

I would of liked to use the CTR and it works just no touch and its not easy to navigate with just the hard keys so I had to reverted back to the CWM which is easier. Has anyone reported touch function working on these mt67x2 :confused:

Anyway I will study your posts and try rebuild with your suggestions. I may add to this post as I read the posts more fully.

Just to confirm the mnt folder contains just the folders sdcard which links to external_sd and sdcard1 which links to internel_sd

Thanks to the both of you for the help it's very much appreciated.
[Miscellaneous Android Development] :
:) Iguess you missed some posts from zp999 thread. More exactly this and this. As you see, I fixed everything for their recovery. And in that one made by taiwan101 from my source they used my settings and modds for sdcards. The only thing that is different for your phone I explained it already few posts back.

Cheers!
[Miscellaneous Android Development] bigrammy:
I did not miss any bro Those are the ones I have ported and do use :confused:

I hope you did not misunderstand me carliv so just to be clear my first port was the taiwan101 but after digging around I soon came to realize they had actually used your zp999 recovery so I ditched that one and ported your original ones those exact ones you linked. It is Your CWM thats in this thread :good: and not that taiwan101 version that gave you no credit. :(

The taiwan101 had no touch function and sdcard problem too so I assume that maybe something is different with this SoC or our kernel which is causing the touch functions not to work thats why I asked if anyone has reported a fully working touch version with any mt67x2 to note if it's the Kernel or the SoC :confused:

Like i said I tried 15 different libminuitwrp.so files to try get the TWRP touch functioning but without any joy.

I assume your CTR touch is not just as simple as swapping a lib file bro so thats why I did not come asking you :o

I thought I would try fix all I could myself and only when everything else was working would I ask you about the touch problem. :o

I really do not want to put you through the zp999 experience again bro and thats why I remained quiet and did things for myself :o

I will have some time tomorrow to study your posts about the sdcards in detail and will make it my mission to fix these very minor issues .

I have even been reading your tut on compiling recoverys :eek: :eek: :laugh:

Thanks Again Carliv :angel:
[Miscellaneous Android Development] :
:) I was misunderstading you. But no worry, I'm ok now.

Well, the touch feature is something related only to kernel. And Elephone always had some problems with that in recovery (in many phones the swipe doesn't work). Replacing a "so" module won't make it work. To be able to solve that you need to study the source code for the firmware to see how touch is activated in kernel and ROM. But Elephone never release any source code, so that will be impossible. Probably for now you have to use only the CWM(non-touch) recovery.

I'm curious, if this phone has capacitive buttons on the bottom, do they work in recovery (eg: back for Go Back)?
[Miscellaneous Android Development] bigrammy:
Fixed :victory:

Well 99.9% fixed

Getting the internel_sd to mount to PC is all I can't get to work but maybe we can fix this later. :rolleyes:

All other function work!!

I need [MENTION=5186178]carliv[/MENTION] approval before releasing due to using his slightly modified logo in the port.

Reason: I wanted everyone to know it's his work and it's him we should be thanking. :good:

Let me know if you approve or not carliv I will gladly change things if it's not suitable. :o

All the menu screenshots are HERE

[MENTION=4056517]HypoTurtle[/MENTION] [MENTION=5952124]megthebest[/MENTION] [MENTION=4205141]enr88[/MENTION]
[Miscellaneous Android Development] :
Sure, I don't mind :)

Man, that's a big font! I think it's because of different screen resolution (1080x1920 in zopo).

For your phone the internal sdcard can't be mounted to PC with actual CWM (no emulated sdcard can be). Maybe with philz recovery because he backported the lunfile, to work but I don't know.
[Miscellaneous Android Development] bigrammy:
Thank you carliv :D

Yes font is a little bit large but that suits me because my eyes are not as good as they once were anyway :laugh:

I personally can live quite happily without the mounting of internal_sd card to PC.

Mounting the external_sd to PC works perfect and that's the one I use for my backup's and flashing of update.zip's :good:

All credit goes to you carliv :angel:

Any followers I will update the OP Post #1 shortly with a link and description thanks to all of you.

Regards bigrammy.
[Miscellaneous Android Development] :
Thanks for the coffee :D (I don't drink beer).

Here is a recovery image built for your phone resolution and with an adapted font-size (don't worry your eyes will be fine :laugh: ).

Just copy the /ramdisk/sbin/recovery module from this one to your ported recovery and that's all, no other changes.
[Miscellaneous Android Development] bigrammy:
Your welcome bro you have more than earned it :highfive:

Thanks for the 720x1280 re-compile carliv I will make the necessary change for the adapted font :cool:
[Miscellaneous Android Development] geheimke:
Hi Carliv,

I see you have a recovery made for the MTK6732 is this possible for the ulefone be pro. (1280x780)

Thanks.
[Miscellaneous Android Development] :
Well, not quite. I built a recovery for zopo zp999 at the beginning of the year.

What you see here is a port of that one made by [MENTION=3924647]bigrammy[/MENTION]. I only gave him few hints (check my posts back on this thread).

If you want to do the same for your device, take the one from this post, and read my posts about sdcards from this thread. If your phone has same "layout" it will work and if you have some problems I can give you some hints too.
[Miscellaneous Android Development] ac0935p:
Thanks

a bundle to all involved with this recovery. Being able to easily make a backup of the ROM is clearly vital. Goal achieved. Here's to a touch version - hopefully before too long.

Thanks again...
[Miscellaneous Android Development] bigrammy:
Thanks for your support. :good:

See the OP I have updated it with the Fixed Font version now. :D

:cool:
[Miscellaneous Android Development] ac0935p:
Even more thanks...

That looks even better. Nicely done.
[Miscellaneous Android Development] ac0935p:
OTA Update

For those of you who have installed the custom CWM recovery, you will need to perform the OTA update manually from CWM (or from an app like flashify). The file is downloaded into /storage/sdcard0/adupsfota/update.zip - that's the file you need to flash. Beware in CWM, the sdcards are mounted as sdcard1 --> sdcard and sdcard0 --> sdcard1 - it's a bit confusing, but the file is on one or the other, so a bit of hunting will uncover it.

In CWM do the following:

Install Zip

Install Zip from /storage/sdcard1

The folder is "adupsfota/" - select it. The folder contains update.zip - select it.

The update is applied and the phone reboots. The first boot after the update is very slow as it rebuilds the dalvik cache (I guess).

Flashing this way did not produce any errors, though the zip was corrupt after the first download. A second download and all went well.

I have noticed, too, that this update re-installs the default recovery, so you will need to reflash CWM - if you want to keep using it.

---------- Post added at 02:07 PM ---------- Previous post was at 01:54 PM ----------

More the OTA update. Well it seems that something has changed in the boot up area. Re-flashing CWM after the update doesn't take any more. In flashify, I install the IMG as before. If I choose reboot from flashify it goes into CWM (the first time). If I Reboot Recovery again (e.g. from Rom Tools), the stock recovery seems to be there again.

Maybe the scatter file layout has changed. On a positive note, (volume up + power) together now reboots into recovery.

Weird.
[Miscellaneous Android Development] bigrammy:
Thanks I only just got this update so please do not use the CWM recovery if you have flashed this update!!!!!! If they have indeed changed the partitions then my recovery will flash backup the wrong partitions so please spread the word. Also the spflashtool will also fail It seems like Elephone are deliberately trying to cause problems :mad:
[Miscellaneous Android Development] enr88:
Hi bigrammy, with 01/09/2015 Fw flashed with spflashtool, no ota update avaible.. Then i download from this link http://www.filedropper.com/update_10

Uploaded by an italian guy that download it, but it's unable to flash it from recovery.

I have tried to flash "update.zip" from stock recovery with Error, and now tried with your Carliv with same error (IMG 1) before modifing build.prop ..now got another error when i try to flash (IMG 2)

Spoiler content hidden.
[Miscellaneous Android Development] bigrammy:
Man you guys will flash just about anything :silly:

image 1: The updater.script is telling you the update is not for your version according to your build.prop not sure why you got cm_ (CWM) that seems like a recovery build.prop :confused:

image 2: Probably a corrupt badly edited update.zip.

PS: I think your recovery will be replaced every time you reboot now. :rolleyes:
[Miscellaneous Android Development] ac0935p:
I was on the 2014-12 version, so the flash worked for me. The download does seem prone to corruption the first time I tried it failed as it tried to unzip before running recovery to do the install.

You are right that the recovery gets overwritten every time. It's a pain, but liveable with for the time being. Are you gonna work on an update for CWM - if so is there any information I can provide to assist.
[Miscellaneous Android Development] geheimke:
Hi Carliv,

may i try to update te recovery on http://d-h.st/kAiJ with mobile uncle tools?

Kind regards
[Miscellaneous Android Development] bigrammy:
Hi All,

The update.zip was not for my phone so failed on every level so I am not sure what patches were actually made to those of you who's phones were compatable with the update. :confused:

Anyway I just made a patch.zip which should ensure the recovery does not get changed with each reboot. :D

Make sure you do not select yes to fix root in recovery as you leave Reason is the installed file (install-recovery.sh) it removes runs the daemonsu ;)

Patch attached :good:
[Miscellaneous Android Development] :
You need to port it first; that recovery is for zopo zp999 but with different screen resolution to match this phone here. I built it only for font adjustment.

And MobileUncle works well in up to 4.3 Android versions (according to their website) - I don't know how it'll work in kitkat, and also you need root to try it.

I guess, the safe solution is with spflashtool.

And here a solution for all to not get cwm replaced with stock recovery after OTA:

After OTA install, reboot recovery (in power menu) and when recovery ask about not being rooted choose yes to root, then after recovery boots up again install a SuperSu zip and that's it, you will never get stock recovery again. The reason for that stock recovery install at every boot is a script in /system/etc folder, install_recovery.sh which does exactly that. The rooting solution from cwm will overwrite that script with other content and the supersu zip will make it permanently.
[Miscellaneous Android Development] bigrammy:
Hi carliv,

I lost root once messing with the system and I tried that method and it failed to fix things in this ROM for some reason :confused: On my ROM superuser lives on the custom partition :confused: I am not sure why they rooted it this way but I guess it never gets removed by any sort of script or even flashing a new rom. There is also binary file called recovery-rootcheck in system/data so not sure what that does but it was updated in the ota so I patched it back to the one i know is good.

flashing the latest SU zip fixed my ROM again but flashed the su .apk to system/app it also remade the install-recovery.sh its all a little confusing but I only advise what I know was and is now working on my phone. :laugh: :eek: I think it's this strange rom rather than the CWM thats the problem.

Sorry [MENTION=5186178]carliv[/MENTION] I miss read your post bro that will work too. LOL :laugh: It's been a Hectic few hours :eek:
[Miscellaneous Android Development] :
Or you can flash this boot image and no other operation is needed (I disabled install_recovery.sh service). At least till the next OTA update.
[Miscellaneous Android Development] the1024:
[MENTION=5186178]carliv[/MENTION]

it's like mt6582 and mt6572. basically *72 is cutted *82 (maybe just limited by chip firmware?) and uses scatter and files marked for *82

[MENTION=3924647]bigrammy[/MENTION]

please rebuild recovery with original file_contexts, or add contexts for /custom.

as when i formatting /custom from updater-script i get this error:

or take my repacked recovery
[Miscellaneous Android Development] :
I see... Well I don't think it's a limited firmware (mt6752 is octacore and 6732 quadcore - same for mt6582 quadcore and 6572 dualcore), but you have a point: probably they use same hardware platform (all the other components besides CPU). In this case I might have a solution for the non-working touch in recovery... Let's see... I'll try something this evening.
[Miscellaneous Android Development] the1024:
well, i meant that cpu's also might be the same. (like amd phenom 2-3-4 cores, physically same thing, but limited by chip firmware)

as it cheaper for configure production line for one model and add artificial limitations
[Miscellaneous Android Development] HypoTurtle:
[MENTION=3164405]the1024[/MENTION] [MENTION=5186178]carliv[/MENTION]

The MT6732 and MT6752 are pin compatible (done to speed up development); I think what they've done with the source is just rename the files labelled MT6732 to MT6752 (so that 52 devices don't have 32 names - as those people would be more concerned with having a lower version).

I don't think it would be a stretch to say that MTK has one single large repository for source code; splitting it into separate chipsets from that is likely difficult/messy/time-consuming and that's why they're not GPL compliant.
[Miscellaneous Android Development] bigrammy:
Context amended Thanks. :good:
[Miscellaneous Android Development] bigrammy:
Cool thanks carliv :fingers-crossed:

Yes everything is mt6752 referenced only mt6732 reference is at the end of build.prop

# 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.1419698357
# end fota properties

Thinking aloud Now........

In the update there is a uboot.img I wonder if this may have activated the touch function :confused:

Do you think that Elephone actually listened to my requests :laugh: :laugh: maybe they did :eek:

It would make sense as this was the old school/ may still be current way of activating the screen, sound, buttons etc. I am not sure if it's still applicable on the newer SoC's

A recompile would probably still be needed though :rolleyes:
[Miscellaneous Android Development] :
Well, I received from [MENTION=5480061]Santhosh M[/MENTION] a device tree already made for your phone (he has it too) and I have to make few adjustments and I can build with it. But I need something. Can any of you to post here the result of "adb shell cat /proc/partinfo"?

And just to be sure a stock boot image too (I have one from Santhosh M, but since I saw here that there are some problems with versions I want to make a comparison). Now that I'm thinking I will need a recovery stock too for default.prop, or post here just the default.prop file.

Since he is an experienced developer and has the phone it will be easy for me to work for your phone now.

At the end if this one goes well I can expand it easily to mt6752 (just kernel and names replace).

Thanks!
[Miscellaneous Android Development] bigrammy:
LOL I sent you that fs layout myP6000 check your PM's 29th of Jan

Elephone P6000 mt6732 FS layout.

:laugh:

I will package all you need and PM you the link so keep an eye out for it. :laugh:
[Miscellaneous Android Development] :
Yes, you did sent me that, but guess what part is missing? :)

So, I need only the result of that commnad for /proc/partinfo, to see partitions names and sizes.

Thanks!

I'll add here later two tests (made by porting) to check few things.
[Miscellaneous Android Development] Santhosh M:
partinfo details

Name Start Size
pgpt 0x0000000000000000 0x0000000000080000
proinfo 0x0000000000080000 0x0000000000300000
nvram 0x0000000000380000 0x0000000000500000
protect1 0x0000000000880000 0x0000000000a00000
protect2 0x0000000001280000 0x0000000000a00000
seccfg 0x0000000001c80000 0x0000000000040000
lk 0x0000000001cc0000 0x0000000000060000
boot 0x0000000001d20000 0x0000000001000000
recovery 0x0000000002d20000 0x0000000001000000
secro 0x0000000003d20000 0x0000000000600000
para 0x0000000004320000 0x0000000000080000
logo 0x00000000043a0000 0x0000000000800000
custom 0x0000000004ba0000 0x0000000012c00000
expdb 0x00000000177a0000 0x0000000000a00000
tee1 0x00000000181a0000 0x0000000000500000
tee2 0x00000000186a0000 0x0000000000500000
metadata 0x0000000018ba0000 0x0000000002460000
system 0x000000001b000000 0x0000000052000000
cache 0x000000006d000000 0x0000000007000000
userdata 0x0000000074000000 0x000000032ed80000
flashinfo 0x00000003a2d80000 0x0000000001000000
sgpt 0x00000003a3d80000 0x0000000000080000
[Miscellaneous Android Development] :
Please test these recoveries:

test1

test2

test3

To explain, these are ported from a mt6752 device. Before I start to build I had to set things right, so I want to verify some settings and files.

What I need to be tested: sdcards, wipe cache and factory reset, backup and restore (you can use advanced backup and restore with boot and data for example, if you don't want to do a full test - but has to be an emmc and an ext4 partition), and check if the capacitive buttons are working (touch) for Go Back as example.

Please post results in a list as I did:

test1:

1. ............

2. ...........

3. ...........

4. ...........

and so on.

Thanks.
[Miscellaneous Android Development] Santhosh M:
All the three didn't boot. Logo and restarts back to system :rolleyes:
[Miscellaneous Android Development] :
Ok, let's see what is the problem:

test4

test5

and then we will continue tomorrow.