yashsingh1/xdaforums huggingface dataset:
[Android General] xenonism:
A fellow user from the Just5 Blaster thread kindly shared his backup files with me and I wanted to give that ROM a shot, but so far I have been unable to do so. What I did was take the scatter file from the P6000 stock ROM and replace everything I could with the Blaster files. It didn't work, so I tried keeping the P6000 kernel and preloader, plus a couple other combinations I can't quite remember. :rolleyes:

Should it work, at least in theory? Does anyone have an idea of how it should be done?

These are the Blaster files I got:

boot.img

lk.bin

preloader.bin

preloader-untouched.bin

recovery.img

secro.img

system.img
[Android General] HypoTurtle:
What exactly didn't work? Spflash or it just wouldn't boot? If it is an identical clone then it should work (the only difference seems to be camera related; at least with LP).
[Android General] xenonism:
It's supposed to be an identical clone, yes. SP Flash itself worked fine, but the phone wouldn't boot.
[Android General] HypoTurtle:
Stalled on boot animation?

Do you have adb or anything then?

Custom recovery still boot?

Post/PM the boot.img and I'll see if there's anything obvious.
[Android General] xenonism:
Stalled on boot animation, didn't try adb. About custom recovery... I've never been able to boot into it. It's supposed to be Power + Volume up, right? Any special tricks?

This is quite relevant to me now because I wanted to try the ColorOS port but it crashes as soon as it starts and being able to boot into recovery would be useful to make the phone usable again. :D

boot.img is attached.
[Android General] HypoTurtle:
Yeah; hold volume up and press power will get you into recovery (stock if you haven't changed it).

They have changed it a little with the lk for the LP ROMs, Volume Up and Power now gives a lk menu so you can normal boot, boot to recovery and enter fastboot.
[Android General] xenonism:
We are talking about a powered off phone, right? Power + Volume Up seem to just boot normally.

I managed to get into ColorOS but both Flashify and ROM Manager are unable to reboot to recovery because errors pop up and interrupt the process... :(
[Android General] HypoTurtle:
Regarding the blaster - it seems that it's a P6000 v2 clone (k01q_h rather than k01q_e). You could try the trustzone.bin from the LPv1 http://d-h.st/5Jtx

Yeah Power & VolUP from off, if you see the boot animation you'll need to turn off again. Perhaps the lk from blaster(provided you haven't changed back); doesn't allow booting to recovery.

I haven't tried the ColorOS yet, need to trim it a bit.
[Android General] xenonism:
Thanks for all the info. I'll try the trustzone.bin thing later.

About recovery, my current lk should be the one from stock ROM V8.3, assuming neither the ZOPO nor the ColorOS ROMS overwrite it when installed (which I think is safe to assume). Is V8.3 stock known for not booting to recovery?

About ColorOS, from the little I could see it looks well done, but on my phone it's completely unusable: android.phone, UI and ao.core crash constantly. What do you mean with trim?
[Android General] HypoTurtle:
If you have adb access you can clear data (I've had to a few times as I don't like clearing userdata)

adb shell pm list packages will get you package names

adb shell pm clear [PACKAGE.NAME] will clear the data

I'm on LPv3 which required repartitioning with SPFlash meaning my system partition is ~20MB too small for the ColorOS ROM, so need to remove some stuff; like ringtones so that it installs without erroring.

Haven't heard about v8.3 having problems entering recovery; you can get the v8.4 one on #1 in the second OTA zip (named as uboot.img)
[Android General] xenonism:
The thing is I am at work on a Linux PC and I can't get either adb or SPFT to work... Understood about the trimming. And finally, I am unable to flash or write anything on the phone right now, so I guess I'll just leave it off and fix it when I'm home. I'm supposed to be working anyway. ;)
[Android General] bigrammy:
Flashing this Uboot.img/lk.bin will fix the booting into recovery HERE if your on a KK ROM ;)

Yes v8.3 would not boot to recovery on my version.

Color OS rom is very heavy on system app's and It's knowing what is safe to remove and what's not when I trimmed my attempt too far a lot of things force closed so it's lot of trial and error :D
[Android General] xenonism:
Thanks a lot for the files!

I had never installed Lollipop or resized any partition before I installed ColorOS, should it have worked properly? Is it working for everyone else?

Another weird thing is that after I flashed V8.3 Stock ROM (everything in the scatter file apart from data), I still saw the errors that were plaguing ColorOS and, even more puzzingly, the USB Mass Storage option (from the ZOPO ROM and possibly from ColorOS) was still available and functional. It was lost after a reboot, though. Isn't that weird? :confused:
[Android General] bigrammy:
Hi,

Color OS , Miui and Lewa etc etc will make lots of changes to your File System due to their framework's and some ports do not do a very good job on the ramdisk of the boot.img so you can be left with many files and folders not belonging to your stock OS :eek:

While some may be beneficial most 99% will not be so If you have strange effects after flashing custom roms I would just use the stock ROM from "Elephone" in SPflashtool and do a Firmware Upgrade. This will clean all partitions.

If you use KK v8.3 for your Firmware Upgrade then before you reboot pull the battery then set SPflashtool to Download untick everything then tick LK.bin and point it to the Uboot.img I gave you and do the same for your stock recovery.img useing any from the OP TWRPv2 or any you like ;)

After flash done! :good:

Pull battery for a minute reinsert it and boot as normal :fingers-crossed:

Everything will be back to normal stock (the orientations sensor may require a recalibration though.)

Then It may also be a idea to clean up your external sdcard too as you will find lots of Color OS Miui etc etc there too. :eek:
[Android General] HypoTurtle:
Yea as bigrammy said, likely something left in /data (local.prop perhaps) or something in /cache or /custom that was still there after the switch back to stock.

[MENTION=3924647]bigrammy[/MENTION] can you just check what you get from running mount. I've just noticed that instead of .../by-name/userdata mine seems to be using /dev/block/dm-0 which is typically the loop mount point used by an app saved on the /sdcard just seems a bit strange but could be due to the encrypted filesystem I suppose.
[Android General] HypoTurtle:
Yea it seems to related to encrypted data - not sure if that's the expected behaviour (I believe it's loop mounted prior to decryption) or not but doesn't seem to be doing much harm.

[MENTION=3924647]bigrammy[/MENTION] I've just got my compiled TWRP to boot - had to look at graphics.c again - there are some graphical issues but it boots - http://d-h.st/oAJ5 - it prompts me for the password, can you check what happens with yours - and if data and /data/media mount correctly (adb works - touch doesn't).

Encryption fixed (default password) I can now backup encrypted data on L

32-bit TWRP V2.8.6.0
[Android General] bayad:
If someone could upload the MIUI Rom to another host because the download stops each time to 89%. :(

Thank you in advance :fingers-crossed:
[Android General] z0rgent:
Here it is: (delete spaces)

h ttps://mega .co.nz/#!VNZBWDKT!CEuC4v4BGNnAZDDblkaYqZce2eRzaEi2RoR08gwQ6uU
[Android General] bayad:
Many thanks z0rgent :good:
[Android General] xenonism:
Thanks guys. I'm gonna do it now. I guess it's time for a proper cleanup after all the mess. :)
[Android General] HypoTurtle:
Android 5.0_01_V1.1 [29/03/15]

System Partition = 2GB

Userdata not encrypted by default

Location fix with both GPS and GLONASS

Restored data (with 32-bit TWRP) works without a problem.

No apparent issue regarding modem.img

As always keep a backup of nvram or restore using one of the numerous methods. #2

Download Links

pan.biadu

mega.co.nz [thanks [MENTION=5593006]z0rgent[/MENTION]]

needrom.com
[Android General] bayad:
Can I flash this with Recovery ? Is it safe ? :confused:
[Android General] HypoTurtle:
They are all SPFlash ROMs so no you can't flash with recovery.

If there is a partition change then you need to flash with SPFlash (stock recovery may be able to repartition but not 100% on that). Also preloader may be different and I believe that can be only flashed with SPFlash.

The TWRP recovery (I'll add a link in previous post) can be used to backup data if you are currently using encrypted data (the data on the betas was encrypted by default - not sure about V1) and can be restored after installing with SPFlash.
[Android General] bayad:
Ok, understood.

Thank you for that clarification :good:
[Android General] taylerdurden:
Why you say this as a change? P6000 has encrypted userdata?
[Android General] HypoTurtle:
The default behaviour for a stock 5.0 ROM is to force data encryption; "forceencrypt=..." in fstab, the betas had forced encryption (data encryption on first boot), not sure about V1, but on V1.1 the encryption is optional like it was on 4.4.4
[Android General] taylerdurden:
I think my phone is not encrypted:
[Android General] HypoTurtle:
Yea, thats unencryted - if it's encrypted the Encrypt phone option is greyed out.

Which ROM; V1?
[Android General] taylerdurden:
Yes, V1
[Android General] HypoTurtle:
Seems that a change was made by google:

https://gigaom.com/2015/03/02/google-backtracks-on-android-5-0-default-encryption/

It might go back to forced with 5.1
[Android General] bayad:
When I try to install this ROM (http://www.needrom.com/download/emui_2-3) by CWM, the error (Status 7 Error) occurs and prevents me from continuing the installation. Do you have a solution please ? :(

Thanks in advance.
[Android General] HypoTurtle:
Look at the updater script and see if there's an assert... line at the top; delete the lines and try again.

Edit. Just downloaded, try deleting the meta-inf/com/android folder
[Android General] bayad:
Thank you for your answer but if I delete this folder and try to install again, is there any risk of brick ?
[Android General] HypoTurtle:
MTK devices are more or less unbrickable. If you've made a backup with CWM you'll be able to go back to CWM and restore, and have SPFlash ROMs available if needed.

There is no risk of brick, but it is a custom ROM and you may need to restore nvram after instaling. The folder I mentioned has some leftover device verification files from the original port device, that may be causing the error 7. The ROM appears to be zipped in what used to an OTA update.zip and thats why those files are there, the scatter.txt is also not needed.
[Android General] killkenny80:
Set imei

i have invalid imei

how can i set imei? please help

tried engmode but it say "AT command is faild to sent"
[Android General] nemo232:
I had same problem with imei. Download Chamelephon prom Google Play and restore it with this app :)
[Android General] bigrammy:
Thanks for this I am sure it will be useful to many people link HERE :good:

I can see it getting pulled due to it's ability to change imei's though so best make a copy for safe keeping ;)
[Android General] bayad:
I did what you asked me, but it did not work. The error status 7 disappeared but the message indicates to me that the installation failed. I do not know where the error may come :confused:
[Android General] HypoTurtle:
Updated #54
[Android General] Xabadou:
Can you tell me how to fix the home button?

I have this problem in some port roms.

Thanks in advance
[Android General] HypoTurtle:
With Flyme it was a problem in /system/usr/keychars and deleting one of them generic I think fixed it, hopefully [MENTION=5593006]z0rgent[/MENTION] can clarify. Also check the dpi, 320 and 280 work fine others seem to turn off the long press = recents.
[Android General] Xabadou:
Ok, I will try change dpi in build.prop.

Thanks!
[Android General] xenonism:
Hi, your ZOPO port is my current favorite ROM for my P6000! :) Are you still working on it?
[Android General] Xabadou:
There is an official Zopo update dated 04/02/2015.

I can re-port the latest version.
[Android General] xenonism:
That would be great! Two things I noticed in your current port are that the BreathLight options don't really work and that there's no auto-brightness settings. Is there any chance your port could come in the form of a full custom ROM instead of an "update", to minimize collisions with the underlying Elephone framework? In any case, thanks again! :)
[Android General] HypoTurtle:
z0rgent's home button fix for MIUI is added to #54 if you want to take a look - if you haven't fixed already.
[Android General] umberto1978:
Hi all, i am trying to port FlyMe OS for my Ulefone Be PRO (same Soc of elephone P6000). Rom boot correctly but when it comes to first configuration (assumed that a wipe data was mandatory, despite the same android version) i stuck with some error, Force closing systemUI and android.phone, from what i understand (consider that the configuration activity start in chinese language for obvious reason, so i am NOT sure what is force closing).

At the moment no adb, so no logcat....

I am trying to port your already ported (for elephone of course) Flyme OS4.2.0.3C V5. Any one knows if those problems are rom related or i am doing something wrong with the port? Thank you in advance for responses.
[Android General] HypoTurtle:
When I attemped a Flyme Port (from the M1 Note mini) I got the android.phone crash; and the only solution for me was to change the number of sims to one in the build.prop also make sure you've wiped /cache and just to be sure I'd wipe/remove the sdcard as some files there can affect thing between different ROMs.
[Android General] scubascuba3:
I've just got the P6000 and Im now struggling getting telephone signal, it was previously fine with my S3 same sim. Anyone know why? is there an issue with call signal?
[Android General] HypoTurtle:
No issues here, you might need to look at APN settings in EngineerMode

Check you're sim here; http://www.willmyphonework.net/ see if there a difference in supported bands.
[Android General] HypoTurtle:
ADB access on Android 5.0

Original Tutorial:

In short need to:

Add MTK subsystem id (0x0e8d) to ~/.android/adb_usb.ini

Add MTK entry to 51-android.rules:

#	MTK

ATTR{idVendor}=="0e8d", ENV{adb_user}="yes"​

On Windows: C:\Users\${Username}\.android\adb_usb.ini

and 51-android.rules is the adb driver android_winusb.inf
[Android General] :
You should update the thread to contain the latest 28 March build of AOSP 5.0.
[Android General] scubascuba3:
The problem seems to be from my lounge I can't make or receive calls or use 3g or 4g data. With my Samsung S3 this wasn't a problem so the conclusion must be that the P6000 isn't as good a quality phone
[Android General] HypoTurtle:
#125 and #3

It's a bit sparse I suppose; not too much to add, ROM is solid just need to remove MMI-Test, they just to add/unhide the OTA app for future updates.

[MENTION=2402280]scubascuba3[/MENTION] did you check your devices on that website? If there's a band missing that would explain it.

You also need to tell the phone which sim you want to have access to 3G/4G the other one can only use 2G/GSM.
[Android General] scubascuba3:
Yes I checked the list Three use 1800 which is fine for P6000. it works for 3G,4G but not 2G. There is a whole list of options to choose, see below, I haven't chosen any as it isn't clear which one is currently being used. I called Three but they had no clue also zero knowledge of the phone. Any ideas?
[Android General] xenonism:
Fair warning: unlike most ROMS, the Lenovo one wipes /data. A backup is probably a good idea. ;)
[Android General] bigrammy:
What's your problem :confused:

I use 3UK and I have no issues at all :good:

You do know that Three is a 3G/4G network only :silly:

2G phones/sims will not work on their network at all. :rolleyes:

I get a stronger signal on my p6000 than I do on my HTC One :D

I assume you have done all the basic stuff

1. factory reset stuff and you have the sim in the correct slot SIM 1 and the correct way around.

2, The sim was/is correctly registered on the 3 network (This can sometimes be a little tricky if its a new sim and it can take upto 15 mins you also need to have data turned on while it registers)

3, You have paid your bill or have credit :laugh:

4, If you are in a dead zone Three have an app that lets you use wifi for calls and texts (Wont work if your rooted though) :good:

Try give us a little more detail if you can so we can narrow down what's going on.

EDIT: Ok I notice from your screenshots you have a good 3G signal on SIM 1 so are you saying that you can Not make or receive any calls or use data eg internet etc even with that signal???

If thats the case then I would say your sim is not registered on the Three Network properly or they are blocking it due to a doggy or duplicated imei number :eek:
[Android General] scubascuba3:
It's the same Three sim I've been using for years so isn't that. Data and calls work in the bedroom, doesn't work in the lounge, this means it isn't a setting issue doesn't it? I'm using "Three in Touch" which is Threes way of receiving calls and texts via WiFi if normal signal is poor. What's the point of a factory reset in this case? it's brand new, I prefer to avoid unless it's likely to help, you have to re set up apps and Internet icons which is a pain.

I mention 2G because it was what was mentioned per the link.

what might be helpful is, if you use Three, under preferred network, 3 UK which option are you using per the screenprints above?
[Android General] bigrammy:
LOL are you for real you're on here because you can't get a signal in your living room :laugh: :laugh: :crying:

You phone is working fine no need to mess with network settings but thanks for wasting our time :rolleyes:
[Android General] scubascuba3:
you are big plonker, added nothing to the problem I had, thanks for nothing, go back to your darkened room.
[Android General] bigrammy:
:laugh: :laugh: my darkened room has a signal :good:
[Android General] bigrammy:
Android 5.0 Betav3

Hi all,

Here is the Android 5.0 Beta v3 stock which I slightly modified to fix some minor issues.

From what I can tell this version is pretty much faultless.

Anyway should anyone wish to try it you can find it here.

Instructions:

Backup Backup!!! :good: :good:

If you are coming from KK 4.4.4 then be sure to use "Firmware Upgrade" mode in Spflashtool. :good:

If you are on Lollipop 5.0 then "Download" should be fine. :good:

After flashing it can take upto 10 mins to fully boot so dont think it's failed please just leave

it alone until it boots which it will !!! :good:

Note: You will not be able to restore any encrypted data if you do then the recovery will not work :(

Please Do Not Post the download link anywhere else or upload it to needrom.com

just simply point people to this post here. I do view other forums guys!!!! :mad:

Change Log:

1 Removed some Chinese apps

2 Comes pre Rooted

3 Fixed adb

4 Disabled Auto data encryption

5 Added CWM custom recovery (None Touch and it will not work if you choose to encrypt data)

6 Added a new boot logo

7 Added a new boot animation

8 Added mini gapp's

Download = 647.8MB from copy.com ;)

Click Here to download

Edit: Any feedback is most welcome on this Rom.

If it's all OK then I will post it on needrom but first I need to be sure there are no glitches.

Glitch: USB/ADB Not mounting on first boot.

Unplug your phone then go to Settings/About phone/ tap on Build number 7 times It should then say "you are a developer"

Now go back to settings/ and find "Developer Options" Toggle USB debugging off and on again then plug it back in.

If it still will not connect switch off the phone pull the battery for a minute reinsert it and reboot.

Reason:

I think maybe a file in userdata or cache doesn't get the permissions on it's first fresh boot so you have to grant it. Once you grant it by toggling USB debugging off and on you will not have any further issues
[Android General] HypoTurtle:
Hope you don't mind; just updating post to V1 / V1.1

Just to show whats changed from the beta versions to the non-beta versions; namely pre-rooted and gapp'ed.
[Android General] bigrammy:
No problem bro mine is just an option for people to try :D

I missed those version so never tried the V1/V1.1 :o

I have been busy with work and trying to workout a way to bypass the recovery/boot kernel checks for the touch recovery to work on 5.0 :eek:

I have no idea why or how this nonsense check is implemented and it would probably need a 5.0 recompile to disable it I think :confused:

On a side note:

I made this little fastboot tool just to save me some typing. :D

It's noobish friendly. :good:

It will most likely work with any Fastboot enabled devices too.

I may add a few more functions later but for now this will do as the bootloader is not very advanced on our phone. :laugh:

Tip:

The Elephone Beta v3 has some quick reboot widgets to boot to bootloader, recovery etc not sure if they are there in the V1/V1.1 :confused:

Hit the thanks button if it helped.

Download Here.

Fastboot Tool
[Android General] scubascuba3:
my second big problem. Two days running now the battery % continues to head to zero even though I have it plugged in and says charging. it got to 12% I removed the battery, replaced and it shoots up to 57%,still there an hour later so probably not correct. Anyone aware of this issue? any solution? I'm moving towards buying a S5 a week in.
[Android General] bigrammy:
It sounds like you have one of buggy rom's :confused:

Just do a "Firmware Upgrade" with one of the Android 5.0 Lp's V1/V1.1 or even my Betav3 from above which I know works fine on 3UK.

After flashing your bat stats and life will improve with time so give it a week before judging.

My phone outlast all my mates S5's so the S5 may not be a good choice :laugh:

PS: Backup your NVRAM first just incase but mine survived the upgrade intact. ;)

Sent from my darkened room :laugh:
[Android General] scubascuba3:
Thanks, firmware upgrade to beta v3 sounds like the best plan then. Basic questions for you, where is splashtool? how should I back up? I'm using tapatalk for this forum and your post above just shows a "spoiler" icon and if I select it it says download but I don't see beta v3 mentioned, maybe when I go to the next stage it will show?
[Android General] bigrammy:
You need a PC for downloading and backups.

SPFlashtool I use is Click Here

See my thread Here and read through the top part of the post and view my video from about 18 mins on. Also view the other two videos posted there for flashing and remember to set as firmware upgrade when you flash. ;)

You can use the start address and size to backup your nvram using scatter file size's from the betav3 as they are the same. :)

Type = EMMC_USER

name = nvram

start = 0x380000 length = 0x500000

All will become clear when you have read and viewed the videos. :fingers-crossed:
[Android General] Xabadou:
Thanks for this Rom, works very fine.

But I have a problem:

My Elephone is not detected in Ubuntu (not usb, not adb).

Kitkat version is detected without problems.

Edit:

On Windows don´t work also.

The phone charges the battery but not have usb connection (Windows & Linux).
[Android General] xenonism:
Do you get anything in dmesg when you switch from Charge Only to MTP?
[Android General] bigrammy:
Sorry bro,

Are you referring to my ROM??

If so unplug your phone then go to Settings/About phone/ tap on Build number 7 times It should then say "you are a developer"

Now go back to settings and find "Developer Options" Toggle USB debugging on off on again then plug it back in.

If it still will not connect switch off the phone pull the battery for a minute reinsert it and reboot. :good:

It's all working for me :confused:

I think maybe a file in userdata or cache doesn't get the permissions on it's first boot so you have to grant it. Once you grant it by toggling USB debugging off and on you will not have any further issues ;)
[Android General] Xabadou:
Thanks, it works.