yashsingh1/xdaforums huggingface dataset:
[Android General] mishurov:
This is a Doogee X5 based ROM. It contains the native kernel and a bit more replaced native libraries than the previous one, so there's a fixed accelerometer, front camera, flashlight, a2dp. However, the FM radio and incorrect mobile signal strength aren't fixed like in the previous one.

I have also a device tree for cm-13.0, but it's a garbage in general, mainly because of a non-working modem, I couldn't fix it despite a copious number of attempts.
[Android General] kirito9:
I think he was talking about the first one ported by Getakgt. The version 2 I linked from you has almost everything working right?
[Android General] mishurov:
Yes, technically speaking, it's the same ROM with extra fixes.
[Android General] kirito9:
Ahh ok. I won't be able to edit the post by the other user tho. Probably made a mistake with the not working list.

Edit: haha it was me who shared it, my bad. Change made.
[Android General] kirito9:
[GUIDE][New Root Method][Replace phhSuperuser with SuperSU]

DISCLAIMER:

Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.

Basic computer skills are required and minimal knowledge about the phone and phone utilities also.

Make sure that whatever you do, you are doing it at your own responsibility.

This guide is for those who would like to remove phh superuser and replace it with SuperSU by Chainfire. I found it on the facebook group and I'm only sharing here in English. Credits to the original creator. This was tested on the Pixi 4-5.

NOTE: You can also use this guide to root your Pixi 4 device. Removing phh's superuser was just an extra step for those who already had root.

Requirements:

Unlocked Bootloader, TWRP, phh's superuser*

unSU Script zip

Chainfire's SuperSU

Steps:

Make a backup with your current system using TWRP

Flash the unSU Script file (if you already rooted with phh's superuser)

Go to TWRP -> Advanced -> Terminal -> Type the follow code: echo "SYSTEMLESS=true" > /data/.supersu

Check to see if the .supersu file is in /data

Install SuperSU from Chainfire

Reboot and profit.

Credits:

Chainfire- SuperSU

osm0sis- unSU Script

Bender1987- Original guide and screenshots!

Luis Mendoza- Original Facebook post
[Android General] Shahriar Rahat:
-----------------------------------------------------

incorrect mobile signal strength means weak signal or anything else????
[Android General] mishurov:
The mobile signal icon in the tray shows always the same level regardless to the real level in dBm in Settings / About phone / Status / SIM status / Signal strength
[Android General] Shahriar Rahat:
-------------------------------------------------

whats about battery life & any other disadvantages.............

I love CM. So wanna try it.

Can i port dogee X5 custom roms for it. I have ported many roms for mtk6582. But here i need to do the same or there are some other things also??

thanks :D
[Android General] mofeck:
gps fix?

Is there any fix for the GPS or will it be in the feature? I can´t wait to flash it. BTW i already installed the superSU you just posted on the fb group, thanks for that. Im going to flash the rom as is, ut cant wait for the gps as its useful sometimes but not indespensable
[Android General] Shahriar Rahat:
Found Some Bugs

-------------------------------------------------

**Bugs found**

1. gesture file not found

2. front flash not working

3. cpu governor can not be changed
[Android General] kirito9:
Thanks, will update the post. What did you use to change the cpu governor?
[Android General] Shahriar Rahat:
the rom owns the cpu governor feature
[Android General] kirito9:
I don't follow.
[Android General] Shahriar Rahat:
i mean CM13 V2 has a cpu governor & i/0 scheduler option in performance in settings. It does not response.............
[Android General] kirito9:
Oh, use Kernel Adiutor app from the playstore.
[Android General] Shahriar Rahat:
Dt2w

Is there any way to get dt2w feature???

& plz help me to find the location of gesture file of cm13

So that i can implement it in this rom. I have some full working

Cm13 rom of same chipset
[Android General] kirito9:
Dt2w has to be enabled in kernel which would mean getting sources and enabling it.

Not sure what gesture file you're talking about.
[Android General] Shahriar Rahat:
in cm13 v2 whenever you will try to enable or disable gesture you will get the message that "Gesture file not found". it is the reason why gestures are not working
[Android General] miguelgamer4:
Help

Good afternoon!

Do you have the TWRP for variant 4034E chip mediatek 6580m ? :eek:

Thanks!!
[Android General] Lucas Ribeiro-BR:
Test for me please

http://xdaforums.com/android/general/dev-alcatel-pixi-4-6-3g-port-cm13-t3509070
[Android General] kirito9:
TWRP for 4034 works for all models.
[Android General] kirito9:
[MENTION=7833711]mishurov[/MENTION] I just found this. You apparently need RIL patches to work with the device tree for the Doogee X5 that MAD team released. That's why RIL doesn't work for you maybe.

http://xdaforums.com/showpost.php?p=68260295&postcount=11
[Android General] habeck.colibretto:
[XPOSED][GRAVITYBOX][PIXI 4 (5) 5010D][STOCK 6.0-01003]

I need (want to) remap hardware navigation keys.

GravityBox is good for this... but it doesnt' work with all keys. I have several phones (Samsungs, LGs, Motorolas and even Chinese UMI Zero) and GravityBox remapping works without a flaw. But on this Alcatel it doesn't.

Only Back and Home remapping works but without long Home. And if I uninstall Google Search than long press for Home key works as well. But it doesn't for Recent key which I don't like. I prefer default action as menu, and long as power button and double as torch. It looks like some kind of system app captures pressings but don't know witch one. I did freeze Onetap Launcher (Titanium Backup can't uninstall it) but it didn't help.

What I can/can't remap:

Back - single, long and double - can :)

Home - single (single tap is unchangeable so can't but doesn't matter) :)

Home - double, long - can :)

Recent - single, double, long - can't :(

I like stock rom, and don't want to change it to buggy CM13 because of this f.... Recent unmappable key!

Does anyone know how to remap this key to my needs?
[Android General] mishurov:
Yes, I've solved the hardware problems by using patched frameworks from xen0n.

https://github.com/xen0n?tab=repositories

Nonetheless, the problem with the incorrect mobile signal in the status bar seems to be somewhere here:

https://github.com/xen0n/android_frameworks_base_mtk
[Android General] kirito9:
This is a problem with the stock ROM. I've had this issue as well. Common problem for Alcatel stock firmwares, not quite as compatible with xposed modules. Idk why Alcatel's stock firmware works like this, isn't stock supposed to be somewhat bugless? :confused:

There is a work around, a new ROM, twp actually are available for the Pixi 4 (4) and (5) models that I will be sharing soon. Xposed works flawless on those ROMs, they are almost completely bugless. Just a few small bugs like led notifications like (on the 4034) etc.
[Android General] kirito9:
The guys here should be able to help you - http://xdaforums.com/showthread.php?t=2274332

Maybe this problem came up before and the correct repo was posted. Fire's github might also have the answer.
[Android General] mishurov:
I'd been looking through Fire's commits in his forks and didn't find anything useful except he inserted a headset icon into the status bar. Thanks for the link to the MTK topic, I'll ask them.
[Android General] habeck.colibretto:
It is bugless (more-less) but harder to modify... :) In GravityBox I can modify almost anything - even tiles but this f... Recent key!

Hmmm... new ROM as workaround... I'll take it if it will be bugless and front flash will be working. :) Do you know ResurrectionRemix (http://www.resurrectionremix.com/). It's really decent ROM based on CM13.0. Very, very customizable and battery friendly - worth to port it. :)
[Android General] kirito9:
Good luck :).
[Android General] kirito9:
Haha yeah that recents key was pissing me off. The ROM is from a Blu Neo X device and GoHD something. Porting would only be possible if there's a similar device with that ROM. RR officially supports Qualcomm devices where as these Pixi devices (most of them) are Mediatek based.
[Android General] Abnerpf:
Hi, I want to know if someone can pass me the pixi ROM STOCK model 4 (3.5) 4017a waxing I need it .. Or any other rom that can serve to unbrick.
[Android General] ghoppa:
Hi all,

I'm gettin crazy with this friend's phone, I just really need to root it but I can't get to fastboot mode.

Model is Pixi 4 (5) 5045x and I'm on linux.

I enabled debug and OEM bootloader unlock in developer options.

I tried powering on with volume down button, adb reboot bootloader, from recovery "reboot to bootloader" but nothing. Phone just restarts with no sign of fastboot, "fastboot devices" gives nothing back. I don't know if I'm missing something or if really fastboot mode is in someway unabled.

Thanks to everyone, damn Alcatel!

Edit: One thing I noticed, on device model in settings it says 5045x, but on recovery mode, the yellow text on top says TCL/5045J/PIXI_4_5_4G.
[Android General] kirito9:
Post you're build.prop.
[Android General] kirito9:
Use the Mobile Upgrade Tool to return the stock.
[Android General] ghoppa:
Sorry kirito, since I still haven't 10 posts yet xda doesn't allow me to send links, and I can't even copy the whole text here (I guess it has some link somewhere inside), so I sent you a PM with the text copied.

Let me know if it's ok.

Thanks a lot!
[Android General] kirito9:
As I suspected, you don't need to unlock your bootloader. I already posted your custom recovery http://xdaforums.com/showpost.php?p=69496572&postcount=498. Just flash it with spft using a scatter created with MTK Droid Tools. Your device is the Alcatel OT Pixi 4-4.5 (4G) MT6735. After flashing the recovery, flash SuperSU to root.
[Android General] ghoppa:
Thanks man! Gonna try that, had a look at those tools this afternoon. Do you know if MTK Droid Tools has a linux version?
[Android General] kirito9:
No, there's no linux version but you can try using wine.
[Android General] ghoppa:
I tried, but it doesn't recognize the phone, I know there are problems with USB under wine, and I can't even install ADB drivers in wine, so that might be the problem too. It's probably easier to borrow a windows PC from someone than to make this work under Linux :eek:.

I'll update you tomorrow on if I manage to achieve something. Thanks again!
[Android General] Martin1307:
Build info ref Pixi 4(4) fastboot problem

more info

Model 4034X

Android version 6.0

Security patch level 5 Aug 2016

Baseband version 6580

KErnel version 3.18.19+

Build number 01002

Boot screen looks like

Android Recovery

TCL/4034D/Pixi4-4

6.0/MRA58K/v3D3S-0

Martin
[Android General] kirito9:
You're welcome, you can always run windows in a VM on linux.
[Android General] habeck.colibretto:
Martin, try to use another computer. I've had the same problem, and I've unlocked bootloader on my second computer. And turn off antivirus.

---------- Post added at 07:50 AM ---------- Previous post was at 07:44 AM ----------

http://www.androidpolice.com/2016/1...-phones-including-blu-devices-sold-in-the-us/ - so remember to clean it from malware. :)

Yea... Pixi is Mediatek... Didn't know that RR supports onlny Qualcomm... :(
[Android General] RiceydDr0id:
Hey all cud I flash supersu.zip threw my PIXI 4s recovery (Stck recovery) To gain root???
[Android General] ghoppa:
Hi kiri,

I'm trying right now, but in MTK droid tools I get the "unknown rom structure message" so I can't get the scatter file.

Hardware : MT6735M

Model : 5045X

Build number : MRA58K release-keys

Build date UTC : 20160726-115533

Android v : 6.0

Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V79.P20, 2016/07/26 19:52

Kernel v : 3.18.19 (int@int-103) (gcc version 4.8 (GCC) ) #1 SMP Sat Jul 2 12:47:48 CST 2016

--->>> Connect to device <<<---

--- ERRORE : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!

--- Struttura della ROM sconosciuta. Il backup NON è possibile!

ATTENZIONE! File /system/recovery-from-boot.p ripristino factory recovery nel caso sia trovato il dispositivo acceso in normal mode!

Message is in italian but I think is understandable... what am I missing?:confused:
[Android General] kirito9:
Your build.prop number says 4034D or 4034X?
[Android General] kirito9:
I tried removing the malware apks but they reappear upon reboot. I removed them from TWRP browser which should remove all files but they reappear after a reboot :confused:.

Technically they support MTK as well as there are unofficial RR ROMs for MTK devices. There are quite a few. I think there was an official RR ROM for mt6580 but they never published it.
[Android General] kirito9:
Stock recovery doesn't allow flashing of unsigned zips. Need to use custom recovery like TWRP.
[Android General] kirito9:
Ahh, Marshmallow...I forgot the tools doesn't support MM. Here's the scatter file from a backup of the 5045D ROM

MT6735_Scatter

You can flash the recovery in SPFT now that you have the scatter.
[Android General] ghoppa:
Kiri you're so kind!

I finally managed to flash recovery, but right after flashing I tried to boot in recovery mode and it didn't. Then I booted to normal system and rebooted again to recovery and it was again the same stock recovery... Gonna try again now :rolleyes:

Edit: tried again, if I try to boot to recovery right after flashing, keeping the volume up button pressed it just reboots again and again, like a bootloop. Then I let it turn on normally again and everything is fine but goes back to stock recovery

Edit 2: On Linux, when I connect the phone turned off to flash it, checking on terminal the attached devices it says "Product: MT65xx Preloader". Shouldn't it be MT67xx?

I'm getting more and more confused

Edit 3: Wait wait wait, sorry, I must be retarded, I thought the recovery was the .img file, but I installed the .zip file instead.

Recovery works now! Flashed ChainfireSU, gonna check now if it worked, let's cross fingers...
[Android General] kirito9:
Strange that you're not able to boot to recovery perhaps different kernel than the 5045D? Backup your recovery and boot partitions with spft and upload them here so I can check.

It can also be a file in your system that's rewriting the stock recovery after reboot but I doubt that.

The preloader name is correct. It's like that for all MTK devices, never really asked why it remains MT65xx tho (good observation).
[Android General] ghoppa:
No Kirito, it's just my fault, I didn't notice that I was flashing the .zip file instead of the .img that was inside it. :silly: Sorry...

Flashing the .img worked and from recovery I flashed SuperSU too (had to flash from sideload, for some reason it wouldn't mount the internal memory) and I just checked that it worked!

I thought this would have been the first time I couldn't manage to root a phone :)

Thanks a lot Kirito, you've been really kind and helpful, and replied fast to everyone! You saved me! :D

Should I make a step by step post for this specific model or would it be useless?

Hurraaaaay! :highfive::victory::fingers-crossed:
[Android General] kirito9:
Haha yeah, I said in the post of the recovery that the zip is not flashable. A guide would be nice so that I add to the first post :).

I can't get the internal memory working for some reason. It's either the external that's mountable or the internal. I decided to go with the external as the internal would probably get wiped.
[Android General] vVxiliVv:
Anyone knows what is the system image partition and how to get reid of it so that we can have mora userspace?
[Android General] ghoppa:
[GUIDE] Root Alcatel OneTouch Pixi 4 (5'') 5045x

So here's the steps I used to root the Alcatel OneTouch Pixi 4 (5'') 5045x

Needed:

MT6735M_Android_scatter.txt - attached

CTR 6.6 Recovery - attached

ChainFire SuperSU - attached

SmartPhone Flash Tool - http://spflashtool.com/

Steps:

0) Copy "SR1-SuperSU-v2.78-SR1-20160915123031.zip" on your SD card for later flashing

1) Start SP Flash Tool and on "Scatter-loading File" select the MT6735M_Android_scatter.txt you downloaded from here

2) White and green lines should appear, control that everything is unticked and tick only the "recovery" line

3) In the "Location" column of the "recovery" line choose "ctr-6.6-5045D-new.img" file. It's INSIDE the zip file here attached, don't flash zip directly!

4) Press "Download" button

5) Turn off your phone, pull off the battery and connect it to the PC USB port

6) Phone should be detected by SPFT, the line at the bottom should become red first and then yellow and in the end a green circle should appear

7) Now recovery should be flashed! Turn on phone on recovery mode (Power button + Volume UP)

8) Flash Chainfire SuperSU either using ADB sideload or from SD

9) REBOOT

Now you should be rooted! :fingers-crossed:

Kirito, let me know if something is wrong in this guide. Thanks again for your help! :good:
[Android General] kirito9:
The system image partition is your /system partition backed up as a .img file. This is if you feel like flashing the system.img via fastboot (fastboot flash system system.img). It really isn't a partition that's necessary to backup as long as you have the system backup already.
[Android General] kirito9:
I don't think there's anything missing. Nice write up. I'll add it to the first post now.
[Android General] MrKartupelis:
My small opinions about 5010(Pixi 4-5inch 3G) to people would think to buy this phone:

Advantages:

+It's one of the cheapest phone runs 6.0 and could be easily owned from local shops.

+5inch is so balanced to use

+back camera takes OK pictures (like sending homework to classmates - readable)

+front flash absolutely helps poor front-cam

+removable back cover+battery

+sd card slot

+has hardware navigation buttons

+does Daily job very well (no lagging while surfing web, even 60fps playing World of tanks blitz in ultra-low settings)

+has twrp & root

+warranty if you buy from local shop

+durable enough to survive half meter drops

+very good mic quality and calls are so clear.

+ok multitasking

Disadvantages:

-Dead-sensitive touch screen (you can't aim in World of tanks thanks to horrible sensitive TFT touch screen.)

-front cam without flash is horrible

-battery will give you max 4-5 hour on web surfing

-very bad DAC

-included charger and headphones are horrible (0.5A) (i use 15$ worth qualcomm 3.0 charger)

-charging times with even QC 3.0 are horrible (6-7 min only charges %2)

-poor view angles on TFT screen

-poor screen scratch durability. (even coin can scratch with little bit pressure)

-poor speakers

-3x slower Daily use speed compared to First generation Moto G

If you need phone from local shop to use temporarly A.S.A.P., buy this phone, you'll be satisfied. But If you have time to wait shipment etc., buy Xiaomi Redmi series, or other chinese brands like TCL's own branded phones with 2GB ram 4G 720p screen with same price.
[Android General] Martin1307:
Hi kirito9,

Not sure what exactly what you mean by 'build.prop'

but i have both numbers.

1. the Android recovery screen (accessed by holding volume up while power up). Says. TCL/4034D/Pixi4-4'

2. The '4034X' comes from 'Settings | About phone'.

So... I'm guessing i have a 4034D - regardless of what the Android OS says.

HOWEVER !!!! :D... I have made progress using another computer (which habeck.colibretto suggested)

It wasn't an instant fix, but it threw light on the problem.....

My problem with fastboot was that NOT ONLY do you need drivers for ADB, but you ALSO need drivers for the FASTBOOT INTERFACE. I guess this is invisible for many people if your PC installs them promptly.

I worked through the problem by booting the phone into fastboot using the volume key etc., and then used Windows Device Manager to explore attached devices and found an Android device called 'Android Bootloader Interface' - which didn't have a driver. I went through an update sequence and all is cool - and fastboot now operates. and I have done the 'unlock' !!!! woohoo!! :D:silly::laugh::victory::good:

I did:

"fastboot flashing unlock"

then

"fastboot continue"

and it is now 'erasing'... and has now booted a few times ,,,, at least 4 - doing 'erasing' each time...

So...

I have used the keystroke boot to get back to fastboot mode, and since I am unlocked, I think i'm in a position to continue rooting my device - as per kirito9 's summaries for this device.

I am sOoo pleased. Thank you all for your help. I expect I will needs some more ! :)

like... all I have got working at the moment is Fastboot and TWRP... so I need to find the instructions for loading other stuff.

cheers

Martin
[Android General] Abnerpf:
The problem is that the Mobile Upgrade Tool It does not detect the phone but the soft if detected ..
[Android General] kirito9:
Glad you succeeded, the instructions for the "other stuff" are on the second post of this thread. Make a full backup for doing anything to your device :good:.

Your build.prop is your device build properties (automatically generated file from ROM building). It can be found in the /system partition.
[Android General] kirito9:
It doesn't detect it? The phone is hard bricked or soft bricked?
[Android General] Abnerpf:
The Phone is softbrick ... esque I formatted it from SPFT ... now I do not know what to do .. I tried it with other ROMs but it gives me error ..
[Android General] kirito9:
If you formatted in SPFT then it's hard bricked, not soft brick. What ROMs have you tried. Do you have the preloader file? Are the ROMs flashing. What errors are you getting?
[Android General] Abnerpf:
Mm as it does not let me flash the roms .. I do not have the preloader so I want to get the ROM
[Android General] kirito9:
Hmm, I haven't seen any stock ROMs for the 4017 that you can use to unbrick. Maybe someone who has this device will upload.
[Android General] Martin1307:
Doh!

Hi Kirito9,

Sadly the unlocking put me in a boot loop doing 'erasing...' and eventually I pulled the battery out - now I have a 'half-brick' (TWRP works ok, but it won't boot a system - it loops on some sort of TWRP screen). so.. no prospect of backing up - since the main system is trashed I think.

I think I need a Rom to be able to turn it back in to a phone.

If I buy another phone (they are v. cheap - main reason i picked it) Can I back up a good phone Before rooting, to create a Rom for the other?

best regards

Martin
[Android General] kirito9:
Hmm, did you try to root with SuperSU? You should be able to use the Mobile Upgrade Tool linked on the second post to get back your stock ROM (Y). If you have any data, back it up with TWRP (data partition only) and you can restore after restoring the firmware.

Does the device loop the TWRP screen over and over?
[Android General] Abnerpf:
I hope so .. please if anyone has got the rom please share it ...
[Android General] Martin1307:
Hi Kirito,

I didnâ€™t get as far as trying to root. - it blew up ...

When I used TWRP to try and boot into System (I think that was the step - the top left button in TWRP - from memory)

TWRP had previously worked ok !! :) - so i'm GUESSING i had killed my ROM. after the unlock and the 'Erasing.... Boot.... Erasing...' loop. and actually trying to boot into the broken Rom is what killed me.

but now it just boot-loops into TWRP. on each boot.

so I can't get back to TWRP to load anything.

Yes, all it does when booting is repeatedly flash up TWRP screen - photo attached (hopefully). Then cycle again through the manufacturer's logo and in to TWRP again.

Mobile Upgrade program tells me I already have the latest version !! so I canâ€™t load a stock rom with the MobileUpgrade program.

I found a stock rom online (hopefully it's real). https://yadi.sk/d/sBhO0_vYuMv2a

Does anyone think I have chance of unbricking?:D

or have i just got a spare battery and a brick in my hands.

:confused:

Martin