yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] vampirefo:
Sounds great, gives me something to look at, while waiting for phone to arrive.

Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk

---------- Post added at 09:32 PM ---------- Previous post was at 09:16 PM ----------

OK, I did a quick look, it should run my lineageos 14 for blu life max, they appear to be the same hardware.

Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
[Miscellaneous Android Development] mrmazak:
I have started to try and use a different source for porting roms to the Tank Pro.

I needed less modification to get them to boot. But still have trouble with getting IMEI and speaker to work

changed only

1. kernel

2. /system/usr/keylayout

3. /system/vendor/firmware

4. edit line in build prop "qemu.hw.mainkeys=1"

https://xdaforums.com/android/gener...nt-support-t3607222/post72362003#post72362003
[Miscellaneous Android Development] vampirefo:
I have requested kernel Source code for this phone, was told it could take up to 30 business days for code to be uploaded.
[Miscellaneous Android Development] mrmazak:
Hope it is not take that long. I requested also when I received my phone a over a month ago.
[Miscellaneous Android Development] vampirefo:
Here is from Blu.

Hello,

*

Thank you for contacting*BLU Products. We*are happy to help you!

*

We have sent the request to our software department. It will take between 15-30*business*days to have to code added. We recommend re-checking after the time period.*

Should you have any additional questions please contact us at 1-877-602-8762 (Monday-Friday 9:30am-10:30pm EST).

*

Thank you for choosing BLU!
[Miscellaneous Android Development] mrmazak:
Yes October 31, I for got same response.
[Miscellaneous Android Development] mrmazak:
This appears to possibly be a clone hardware device.

http://hammerphones.com/produkty/hammer-energy-2/

Edit:

Phone is close but not full clone.

Touchscreen is different

one of the cameras is different

main speaker is different.

I found this phones stock rom and tried its kernel on the tank, It did not boot.

not that is helps since I find its kernel to not work for us, here is link to the thread (in polish) that has the stock ROM

https://androidforum.cz/myphone-hammer-energy-80923
[Miscellaneous Android Development] vampirefo:
This phone is Android 6 not Android 7, so unlikely the kernel or ROM would work on our tank.
[Miscellaneous Android Development] mrmazak:
Sorry, forgot to mention. The phone is listed as shipped with Android 6 (freeme os 6), and received ota to Android 7 (freeme os 7)
[Miscellaneous Android Development] vampirefo:
So you have the Android 7 kernel and firmware?
[Miscellaneous Android Development] mrmazak:
yes

it is on this link

https://mega.nz/#F!IfIhSKob!ZXBzdQs6Yy-AnLdGPej29g

and attached here is the build.prop

Device info HW shows these two other devices with same Audio hardware/ driver "i2c_tfa9890"

http://deviceinfohw.ru/devices/uplo...rand=brand0&filter=	i2c_tfa9890&submit=Search
[Miscellaneous Android Development] mrmazak:
Followed up with blu again, about sources. I told them it has been over the stated 30 days,

they responded with the following statement

Thank you for contacting BLU Products. We are happy to help you!

Please note a formal request has been placed for the information requested. Please contact us back within 48-72 hours to have an answer regarding this matter. We apologize for any inconvenience.

and on the ftp site there is now a folder for "Tank Xtreme Pro" but the folder is empty right now .
[Miscellaneous Android Development] vampirefo:
It's available now on their ftp server.
[Miscellaneous Android Development] mrmazak:
Right off the bat, I keep getting make errors just trying to "make mrproper"

missing files, missing folders,
[Miscellaneous Android Development] vampirefo:
Maybe, source is incomplete downloading soon.
[Miscellaneous Android Development] mrmazak:
I have gotten past the "make mrproper" errors by back-tracing the errors, and found references to "obj" include lines in 3 make files that point to files that are not in the source. I commented (#) out the lines and got build to start. But again ran into an issue. A missing "lcm-list.o" file. And if I comment that reference out build continues and seemed like it would complete, but failed when build looked for the resulting lcm list that had not been made.

My edits are probably wrong but here is what I have done so far;

1. /drivers/input/fingerprint/Makefile

comment out line #9

"obj-$(CONFIG_MTK_SUNWAVECORP_TEE) += sunwavecorp_tee/"

2. /drivers/misc/mediatek/base/power/Makefile

comment out line #39

"obj-$(CONFIG_MT2701_DCM) += mt2701_dcm/"

3. /drivers/misc/mediatek/Makefile

comment out line #92

"obj-$(CONFIG_MTK_SM100)	+= tc1_interface/vib_drv/"

Those changes allow build to start, still looking at LCM driver build error
[Miscellaneous Android Development] mrmazak:
I have been trying to use the "fq5c_defconfig" based on the build_flavor in stock build.prop.

But I also found those two "almost" clone type devices "Nomu S20" and "myphone Hamer Energy" , both of which also have "fq5c" in there build_flavor. Neither of those kernels boot in the Tank.

So my question is, How to know which defconfig to use?
[Miscellaneous Android Development] vampirefo:
None of them are for tank, you get the information from build.prop

Tank would be fq5c62 it isn't included, nor can one be found in current kernel.

So really the source is useless, Blu uploaded bad source on purpose.
[Miscellaneous Android Development] mrmazak:
I sent Blu an email stating the sources seem to be incomplete.

They responded with generic direction how to connect to ftp server and download.

So unhelpful.
[Miscellaneous Android Development] mrmazak:
I was able to get the kernel to build from there sources now, after one more edit in a source file. (This makes #4)

As of my last post about it, I had to comment out one line in three separate files in order to get "make mrproper" to install sources correctly.

After those changes kernel would start to build but fail at during driver build. I was getting error "LCM_COMPILE_ASSERT=-1" and it gave line numbers for the assert line.

I changed the line from a "0" to "10" and zimage was built.

But it does not boot yet. I beleive it is due to the defconfig in not correct.

file changed

/drivers/misc/mediatek/lcm/mt65xx_lcm_list.c

From line 172

LCM_COMPILE_ASSERT(0 != sizeof(lcm_driver_list) / sizeof(LCM_DRIVER *));

To line 172

LCM_COMPILE_ASSERT(10 != sizeof(lcm_driver_list) / sizeof(LCM_DRIVER *));

Also works if changed to a 1 instead of 10

.

added source repo on github. Hope to get this source to work.

https://github.com/mrmazakblu/Android_Kernel_Blu_Tank_Xtreme_Pro_T0010UU
[Miscellaneous Android Development] vampirefo:
I am able to build Kernel's, but they don't boot cause they aren't for tank, some will compile without any modifications others require defconfig edit.

Example b38_deconfig needed two edits remove 62_gb from line 36 and 180.

Change b3862_gb to b38 and save should build kernel for that device without any other changes.

f5ct_defconfig should build a kernel without any changes.

There are several more that will build, making deconfig changes as described above, but without tank deconfig we won't be able to boot any kernel we build.
[Miscellaneous Android Development] mrmazak:
I had started the same process you say. Found some build, some do not.

I did grep on the config folder looking for "imx219" and "gc2365" The two cameras for tank.

none have the "gc2365"

the "droi6737m_35g_n_defconfig" has the ("imx219" and "gc2355") it builds too. but like your testing , does not boot.

Did not find any that have the touchscreen driver called out "ft5x0x" (from device info HW - app)

I got a response from BLU ,when I told them the source they released was not correct. But it did not help any.

They asked if I had checked before or after they had requested the source and uploaded it. (like really, how could I have checked it before they uploaded it.?)
[Miscellaneous Android Development] mrmazak:
There is a file in "/sys/hwm_info" "hw_module_info"

It lists the LCM driver and camera , touchscreen , etc

I edited one of the droi**_defconfigs to use the correct LCM driver. It built without needing my previous edits in "mt65xx_lcm_list.c".

I feel I am getting closer but still not getting a boot-able kernel.
[Miscellaneous Android Development] mrmazak:
I sent this message to Blu customer support

And they responded with this today.

Hope this goes well.
[Miscellaneous Android Development] mrmazak:
Trying to download rom for "NOMU S10"

phone seems to be near clone.

It has same main camera

same soc

and by the file name it might have same kernel build. (fq5c62....)

http://www.nomu.hk/s10-rom-download/

right now have very poor download speed. And download has failed 2 times. will update when finally find out if the kernel is same
[Miscellaneous Android Development] vampirefo:
i tried this kernel didn't boot on my phone, good luck to you.
[Miscellaneous Android Development] mrmazak:
thanks. I never did get it to download.

But found thread on XDA that has users claiming firmware from "Nomu s10" and "Archos 50 saphir" are interchangeable.

I found the rom for Archos on needrom. The comments there supported the swapping between Nomu and Archos.

its kernel did not boot either.

And I have not found any sources for either of the "near-clones" .
[Miscellaneous Android Development] vampirefo:
I got it to download by adding it to my drive, from my drive it downloaded fast.
[Miscellaneous Android Development] mrmazak:
Blu uploaded a new kernel source today.

I'm still downloading it. To see if it works now.
[Miscellaneous Android Development] vampirefo:
config file is there.

fq5c62_xdnz_f35a_defconfig

trying to compile now
[Miscellaneous Android Development] vampirefo:
I am running built kernel right now, need to do more tests.

T0010UU:/ # cat /proc/version
Linux version 3.18.35 (vampirefo@vampirefo-OptiPlex-760) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Jan 24 21:45:23 EST 2018
T0010UU:/ #
[Miscellaneous Android Development] mrmazak:
ok., good.

I am still having build errors.

I see the new source is in zip format. And I suspected that would be problem , and it is.

There are supposed to be some files with same name one in uppercase one in lowercase. (Example: include/uapi/linux/netfilter/xt_mark.h and. Include/uapi/linux/netfilter/xt_MARK.h)

But new source only has one of them.

This is probably because they repacked with Windows
[Miscellaneous Android Development] vampirefo:
No this is cause they removed the files from source two so it won't build, source one files are intact.

You need both sources run diff -r on the sources that will give you a list of files you need to copy over from source two to source one.

Don't copy any files that have files like you posted, this isn't a mistake, it's how it should be in source one.

(Upcase lowercase, don't mess with these)

Very complicated to build kernel, lots of work to build kernel still alot more work to do.
[Miscellaneous Android Development] vampirefo:
I am looking into compiling Lineage OS 14 for tank, I am trying to find a vendor for mtk android 7, all I have found so far are for android 6 which I already have, I cloned [MENTION=5593584]hyperion70[/MENTION] android_device_leagoo_M8_pro he doesn't have a android_vendor_leagoo_M8_pro, but rezvorck does, which I also cloned, however it's for android 6, so not really helpful, android 7 pulls files from different places than android 6 does.

Does your IMEI return when you use twrp and restore your backup, or is splashtool required?
[Miscellaneous Android Development] mrmazak:
IMEI came back when twrp restored stock rom. Also when I flashed stock rom with twrp. either way. No need for sp flash or s/n writing tools

does 32bit vs 64bit make difference on android_vendor?

because this vendor tree i found earlier but it is cool pad note 3 (64bit)

https://github.com/MediatekAndroidDevelopers/android_vendor_coolpad_note3
[Miscellaneous Android Development] vampirefo:
Thanks, but that is also an Android 6 vendor tree.

A Android 7 tree has firmware and hw files in vendor.

OK, I found one, look at the vendor folder and you will what I am looking for.

https://github.com/vampirefo/android_vendor_motorola_woods
[Miscellaneous Android Development] hyperion70:
Hello!

It seems I have what you need. [MENTION=2472806]vampirefo[/MENTION] check your private messages.
[Miscellaneous Android Development] vampirefo:
Thank you very much.
[Miscellaneous Android Development] mrmazak:
I had sent BLU an email stating the new kernel source they had uploaded didn't work, and explained why I thought so.

Because there was missing and merged files . Original source had some files same name but one was capitol and other lowercase.

They responded today and said they fixed problem and re uploaded fixed "working" sources.

Have not had a chance to see if it's true.

edit:

just had chance to look, and there is

not

a new file uploaded.
[Miscellaneous Android Development] mrmazak:
I have just received a working build of RR for our little tank device.

I only find so far the GPS not working.

Will update the download links.

Hope that this becomes usefull to some.

First post will get updated soon. But for now , here are links.

Resurrection Remix rom

https://www.androidfilehost.com/?fid=11410963190603908218

Patch to fix Bluetooth audio.

https://drive.google.com/open?id=1dS2fa3jRIBhVVjxzO8AX0Y56HeCyqUB7
[Miscellaneous Android Development] mrmazak:
My friend [MENTION=4939713]lopestom[/MENTION] has figured out the gps issue as well. So now GPS is working. It was a simple build.prop line change.

Change

persist.mtk.wcn.combo.chipid=0x0335

to
persist.mtk.wcn.combo.chipid=-1

here this twrp install patch can make the change for you.

Just make sure system is mounted in twrp mount menu

Already patched rom is in Download tab.
[Miscellaneous Android Development] mali843:
help

was wondering if there was a guide to flashing these? i've messed with these before with some success and also almost messed my phone up so a good guide would be greatly appreciated
[Miscellaneous Android Development] mrmazak:
Just came back to this device. Cleaned off the dust and started to use it as my daily. Cause I needed the waterproof rating.

The RR rom I shared earlier is working out nice. The speakerphone does not seem to work, but even on stock rom the speaker phone was not correct.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] laikexpert:
Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4

1.31 GB

letv-x650-7to-twrp3.1-recovery-new

19.4 MB

Update log:

Based on the official 25S unpack optimization, the ROM main streamlined, suitable for like the original friend

Maintain the official input method and store and the necessary procedures

Repair official yellow box problem (mandfx & winter)

Streamline redundant programs and residual files

Modify the kernel to add init.d support

Change kernel selinux status to permissive

Built-in viper sound

Update the busybox component

Add ROOT Privilege Pro, perfect ROOT

Other features of their own experience.

Android version: 6.0.1

Updated on: 2017-05-02

Applicable models: Le Pro3 AI version X650

original link
[LeEco Le Pro3 AI (Model x651) Guides, Development ] laikexpert:
1.) Copy ROM to your phone

2.) install the adb fastboot on the pc

3) Unlocking:

Go to Settings -> About -> Hit Build 7 times

Go to Settings -> Developer Options -> Enable OEM unlocking

Run 'adb reboot bootloader'

Use 'fastboot oem unlock'

4.) Install TWRP via fastboot

5.) Go in TWRP (WIPE - Dalvik/caсhe, Data, и Cache.)

6.) Installing the ROM

7.) The first boot and set your phone.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] vadanorsk:
А русский язык в прошивке есть?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] flixxxua1:
Когда появится Кастом?кто то знает?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] laikexpert:
нет.

в настоящее время ничего, кроме этого.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] flixxxua1:
Who know, where whill been castom ROM to Leeco LEX650
[LeEco Le Pro3 AI (Model x651) Guides, Development ] angelusx85:
Someone has an account here.

bbs.ydss.cn/forum.php?mod=vie...&pe=1&mobile=2

It seems like it's a new rom.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
Its a fake or the author remove the link, anyways the post it's from few months ago
[LeEco Le Pro3 AI (Model x651) Guides, Development ] flixxxua1:
Maybe you give not bad link
[LeEco Le Pro3 AI (Model x651) Guides, Development ] angelusx85:
sorry, I have set myself apart
[LeEco Le Pro3 AI (Model x651) Guides, Development ] raven5867:
can i apply this on my LeEco Pro 3 AI Edition LEX653?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
LeEco Le Pro 3 AI (X650 ) - IMEI Lost

Hello, I need some help.

I got a brand new X650 (4GB/64GB) two days ago and tried TWRP from laikexpert in fastboot mode (not flashed).

This was just to see if it is a suitable candidate for flash. TWRP loaded succesfully, but was completely in chinese and did not respond on touch. MTP with PC worked.

Only choice to get out of this was long press of power-button. Even I did not flash or did anything else, Phone got stucked in first leeco screen.

Stock Recovery was still ok. I tried to perform factory reset but it did not succeed.

Maybe I mistook something with stock recovery but when I checked back later with fastboot of TWRP 3.1 from laikexpert i could see at my PC that all files were gone from phone except an empty TWRP-Folder was there.

After this I tried other older TWRP (LePro3AI_TWRP_3.0.3_recovery) from other post which had standard user interface in english and responded almost normally. I did a backup from what was remained in the phone and copied it to my PC. Afterwards I flashed this TWRP 3.0.3.

Finally I decided to flash "Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4" which succeded in booting system, but now I am without IMEI. Means my phone is perfectly rooted and has somehow custom-ROM, but without IMEI and therefore is useless.

Can somebody help me out ?

fastboot ok

TWRP (LePro3AI_TWRP_3.0.3_recovery)

TWRP backup with unknown status before I flashed new ROM

Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4

no IMEI in phone, only hardcopy of IMEI-label from backside of phone
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
X650 4gb/64gb

The zip-file from the linked thread below restored my phone. IMEI's are back. Phone is operational again but is now EUI 25S CN

(english language is available)

It is not exactly as before, because in fastboot it was named somehow "X650-oversea" before the mess.

Now it is changed to "whole netcom".

"Le Pro3 AI X650 EUI5.9_25S install ROM via Fastboot" the other link from laikexpert

https://xdaforums.com/le-pro3/leeco...e-pro3-ai-x650-eui5-925s-install-rom-t3716920
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
If you can flash by fastboot, you can try to install twrp again and flash magisk for root, if something goes wrong, you can restore the phone again via fastboot.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
I tried already flash of TWRP succesfully afterwards of fastboot restore, but TWRP asks for password and could only be used in read only mode.

Phone has encrypted data partition after fastboot restore with "leecopro3 ai.zip ". I tried "default_password" and also method with setting PIN in restored phone and tried this PIN for TWRP, but without being successful in both cases.

I formatted data partition and reflashed "streamlined Root v4" again, but than again both IMEI are blank.

Would flash of "STOP_Orange+_state+S20.zip" and "no-verity-opt-encrypt.zip" help against blank IMEI in streamlined rom?

Any idea how to continue ?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
X650

Ok, I flashed again the LePro3AI_TWRP_3.0.3_recovery. Due to encrypted data partition I formatted data partition, rebooted into TWRP and put Magisk on the now available data partition.

Flash of Magisk was succesful, reboot also !

Only thing is, that english language was gone due to formatted partition, but meanwhile I know where to touch to come inside the menues.

Magisk was not there and no GSM and no IMEI was available.

Now I am back with leecopro3 ai.zip method.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
you're doing something wrong, try this twrp, works fine for me:

https://mega.nz/#!tfJn2J7B!Ggtdd_pTFA1-JLUERllhpspFrE_NY9CR-f2zcfW_0dc

you must wipe all before flash
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
Thanks for your assistance :)

I flashed it but it is in chinese language which I can not read. In flashed condition screen touch works perfect.

Is it possible to change this TWRP to english ?

If so can you guide me to the menue to set to english?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
youtube:

https://www.youtube.com/watch?v=vxPeYJYsUYU

Mira aquí:

Le Pro3 AI X650 EUI5.9_25S simplificado ROOT V4

P.S.

1.) Desbloquee el gestor de arranque

2.) Instale TWRP a través de fastboot

3.) Vaya a TWRP. Weip: WIPE - Dalvik / cace, Datos y Caché.

4.) Instale el firmware

5.) La primera descarga y configure el teléfono.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
Your linked Youtube video is for classical TWRP which I know well, but please see my screenshot in my previous post. It has completely different user interface and look ;)
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
Its the same Twrp with the theme changed, check this video it's this theme in english, min 2.10:

https://www.youtube.com/watch?v=bbEr3le8Qmc

click in the upper left to change language
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
Ok Thanks again.

I did manage to flash magisk with this TWRP and Stock 25S by comparing english screenshots. But it did not occour in booted phone.

But I did a big mistake afterwards. due to the Orange-State message before boot I flashed "STOP_Orange+_state+S20.zip".

I read that in another post for X620. Now I am in vibration boot loop. I still can access fastboot timewise, but fastboot restore from other post will not start anymore because phone is identified now as s2-plus.

TWRP reflash worked, but did not solve the bootloop problem. Can I uninstall the Stop Orange patch somehow ?

Any idea, or is it all finished now ?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
yes doing again a full wipe and flashing the rom again, but why you try to root a rom that's its already rooted?
[LeEco Le Pro3 AI (Model x651) Guides, Development ] 123Bart:
Phone is completely unresponsive now. If connected to PC it switch intermediately something on and off, but basically it is in deep sleep...

My aim was to root the EUI stock 25S, therefore i tried to flash Magisk. This was not a good idea what I know now.

Your TWRP worked well, but due to my mistake of flash Stop Orange I got fastboot bootloop, the phone type changed and due to this name change fastboot restore was not possible anymore.

Reflash of TWRP in fastboot succeded, but the bootloop persists and Power button with Vol+ did not boot to recovery anymore.

Finally I applied "fastboot boot letv-x650-7to-twrp3.1-recovery-new.img" , what succeded, but this leeds to total brick and completely unresponsive buttons.

My last idea is to wait probably days or weeks for battery drain to get rid of unflashed recovery in fastboot.

If this will work I need to tweak the fastboot restore files to proper respond to my "name changed phone"

To be honest I have only small hope to restore my X650, but I knew the risk.
[LeEco Le Pro3 AI (Model x651) Guides, Development ] Toni Moon:
Try with flashtool, you can unbrick your phone with flashtool and your fastboot image.

Look this thread, and if you restore your phone dont flash it anymore :rolleyes:

https://www.movilesdualsim.com/tema/brickeado-con-luz-roja-en-leeco-le-2-x626-4-64.179674/