yashsingh1/xdaforums huggingface dataset:
[Android General] kirito9:
Pixi 4 ROMs

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.

ROMs

Be careful how you use these SPFT ROMs, they can sometimes cause more problems than solving because of model numbers.

SPFT ROMs- Pixi 4 (3.5) | Pixi 4 (4) 3G (4034G) | Pixi 4 (5) 3G (5010D) | [URL="https://yadi.sk/d/6Vpxfgpz3DgykH"]Pixi 4 (5) 4G (5045D)[/URL] | Pixi 4 (6) (8050G) (8050E) 8050D

TWRP Backups- Pixi 4 (3.5) | Pixi 4 (4) 3G | Pixi 4 (4.5) 4G | Pixi 4 (5) 3G (5010D) | Pixi 4 (5) 4G | Pixi 4 (6)

Stock ROMs- Pixi 4 (3.5) | Pixi 4 (4) 3G | Pixi 4 (5) 4G | Pixi 4 (5) 3G (5010G)| Pixi 4 (5) 4G | Pixi 4 (6)

CyanogenMod 12.1- Pixi 4 (3.5) | Pixi 4 (6)

CyanogenMod 13- Pixi 4 (3.5) | Pixi 4 (4) 3G | Pixi 4 (5) 4G | Pixi 4 (5) 3G, CM13v2*New Build* | Pixi 4 (5) 4G | Pixi 4 (6)

AOSP - Pixi 4 (4) 3G | Pixi 4 (4.5) 4G | Pixi 4 (5) 3G | Pixi 4 (5) 4G | Pixi 4 (6)

Resurrection Remix - Pixi 4 (4) 3G | Pixi 4 (4.5) 4G | Pixi 4 (5) 3G | Pixi 4 (5) 4G | Pixi 4 (6)

Ported Stock ROMs - Pixi 4 (4) 3G | Pixi 4 (4.5) 4G | Pixi 4 (5) 3G | Pixi 4 (5) 4G | Pixi 4 (6)

Mokee - Pixi 4 (4) 3G | Pixi 4 (4.5) 4G | Pixi 4 (5) 3G | Pixi 4 (5) 4G | Pixi 4 (6)

Note: If you do not see your device highlighted, it means the ROM is not there......yet ;).
[Android General] haydent:
Hi, thanks for signing up to provide your feedback. Im guessing your saying it didnt work ? Did you make a rom backup first, can you provide that to us ? If not can you revert, and make one ?
[Android General] vili4u:
Google Play crashed

KingRoot rooted.

First, the System App Managerapp (by flaki)

then it collapsed.

then I worked with System Cleaner ROOT application.

They have been integrated into the updates.

Removed Google Photos, Google Books, and the like. But no system files.

After the mobile phone is restored.

Restart. WiFi connection. Or 3G connection. They.

When checking for updates to Google Play crashes.

And again in the WiFi list.
[Android General] mat584:
Just got a Pixi 4 (4), it works pretty well.

Can't wait to root it.

Subscribing to this thread ;)
[Android General] Junior15mars:
How to root Pixi 4 (4) on marshmallow

I also have the Pixi 4 (4) on marshmallow 6.0 and it is a good smartphone (quadcore 1.3ghz 1g RAM 8g ROM ....) I really want the root :(
[Android General] kevios12:
Now i rooted my tcl alcatel 8050D with kingroot and no restore all works playstore too
[Android General] Paxile2k:
9015w/Pixi4-7_4g-tmo

Is there a stock/rooted/custom rom for this variant? Having a tough time with a boot loop issue after changing the boot animation. Was able to root with kingroot successfully. I got a little to explorative. Was finally able to get into recovery but factory reset did not resolve the issue.

Its an alcatel one touch pop7 lte/4g

Any help would be appreciated.
[Android General] Lucas Ribeiro-BR:
It works in pixi 4 6 8050e?
[Android General] kirito9:
Nope, it won't. This is for MTK devices only. You have a Qualcomm chipset.
[Android General] IrhadTa:
Do someone know if this works with the Alcatel pixi 4 (7") 9003x tablet. Thanks
[Android General] imgo:
Recovery

Have someone got a clean recovery img to alcatel pixi 4 (6) 3g ?

I tried to install that recovery. Img in the top of this topic but it still doesn't work :(
[Android General] Lucas Ribeiro-BR:
CPU Z shows how mtk processor
[Android General] kirito9:
Strange, can you send a screenshot?
[Android General] Lucas Ribeiro-BR:
ok

ok ht tp://i mg ur.c om/a /ajX A0 remove the spaces
[Android General] kirito9:
Ahh, I see now. It's actually MTK but MT6580. The recovery in the first post if for MT6572. If you want a custom recovery or a TWRP recovery. You'll have to compile on your own. Don't forget to say thanks by clicking the button.
[Android General] Lucas Ribeiro-BR:
It works in 8050e?
[Android General] rabsmd:
I tried to root a Pixi 4 4" 4034D.

Reasons, for those interested:

My main goal is to disable/remove com.facebook.appmanager, which sent a few MB of data when I connected to wifi. I'm on a very tight budget for 3G data (only used for "emergency"), so I don't want such waste to happen.

Anyway, it also annoy me that my device communicate "information" to 3rd party. Android 6 permissions should be enough in a general case, but com.facebook.* services are encrusted in the OS...

Then as a bonus, maybe I'll try to customize more things.

What I noticed/tried:

first thing, I tried TCL/Alcatel recovery tool "Mobile Upgrade S 4.5.2 ", which works well

no problem to activate developer mode and USB debug

though on this device also, adb doesn't work in stock recovery boot menu

'fastboot oem unlock' seems to be authorized, but ends on a loop of failure to boot (2x alcatel logo, then an animated android, then reboot). I checked the recovery logs a bit, but it's difficult on the device, so I'm not sure what's wrong. I had to reflash everything with "Mobile Upgrade".

KingRoot app (NewKingrootV4.95_C149_B283_en_release_2016_07_05_105203.apk) fails, 55 people tried. The device was in a boot loop afterward, but a stock recovery "reset data" was enough, no need to reflash everything.

KingRoot exe (KingRootSetup_v3.2.0.1129_105002.exe) fails, 0 (?) people tried
[Android General] dr.mnemonix:
Help.. Please

I've been trying to follow along and use some of this advise to root my tablet with no luck.

Would anyone be so kind as to give me some specific instructions on how to root this device.

I really appreciate it.

If the tone seems like begging it's because I'm at that point.

Thanks!

Here is a pic of my system off cpu z

//imgur . com/a/mDIa9
[Android General] haydent:
please see this earlier post in this thread: http://xdaforums.com/showpost.php?p=68049551&postcount=97

btw i was able to do custom boot loader
[Android General] Heelixx:
Games freezing pixi 4(3.5)

I was wondering if anyone notice this. My phone is about a week old and I'm noticing that every game that I play on it freezes periodically. It's not the laggy type of freezing and there are no skipped frames. It's more like the game pauses then resumes after. Anyone else having this problem?
[Android General] noobfromfar:
Can someone please confirm if the custom recovery for pixi 4 (4) 4034 is working fine ? is backup and restore, flashing supersu mounting system read and write no issue or bug ? I want to edit something in the build.prop but It's the only phone I have as I bricked my pop 2 4.5 and it refuses to updade mobile upgrade q and not charging no fastboot and adb unauthorized and is a qualcomm in qdloader9008 and mmc storage mode is unreachable I can't restore backup , the last time I buy qualcomm devices
[Android General] Heelixx:
Repartition pixi 4(3.5)

Can anyone repartition the internal memory for the pixi?
[Android General] noobfromfar:
Thank you all everything is running fine with pixi 4 4 4034, my pixi 4 4034n is now working with the rom of 4034d from backup and restore and is rooted... Thank you
[Android General] kirito9:
You're welcome.
[Android General] smokerman:
wich TWRP for alcatel pixi 4 6" display?:cool:

the TWRP 3.0.2.0 5010 will work?
[Android General] kirito9:
If your device model number is 5010 then use the 5010 but if it is Pixi 4 (6) then use the Pixi 4 (6) provided by [MENTION=4429374]kevios12[/MENTION]. I will update it in the post.
[Android General] Paxile2k:
Seems a lot of progress has been made on the pixi 4. I must have an offshoot of the p310 with pop 7 lte. There does not seem to be a fastboot option and i cant even find a stock image for the thing. Even then its still a stock recovery. The mobileupdate utility does not exist for this model at all. Curse you T-Mobile and for your locking of the boot loader for the s7 edge.
[Android General] dimspace:
The UK Pixi 4 (6) - 16gb storage/1gb ram is model number 9001x

not overly clear if that model is covered by Kevios's files

as it is, 9001x flatly refuses to boot into fastboot from adb

cant enter fastboot from vol down/power either

can enter the alcatel recovery menu from vol up/power

flatly refuses to go into fastboot though.
[Android General] kirito9:
Probably not mediatek, maybe Qualcomm. I'll check and verify.
[Android General] noobfromfar:
users of 4034n orange rise 31 has complained about bootloop when flashing supersu but not with mine the only problem were failed to root. I think it has secure boot and can't be extracted but when I use boot from 4034d the keyboard is not working
[Android General] smokerman:
I appreciate..must be a cleaner thread and more specific..users are confused...thanks ?

Enviado do meu 2014811 através de Tapatalk
[Android General] kirito9:
Thanks for the advice but I don't have control over that. The TWRP for the Pixi 4 (6) I ported was working but wasn't working for another, so he modified it to work for him.

What do you suggest I do to make it cleaner?
[Android General] JoeTF:
How do I enter fastboot mode?

The Pixi 4 is bootlooping and twrp is showing bunch of red errors and rebooting itself as well.
[Android General] kirito9:
Power off your device, take out the battery then place it back in. Press and hold the volume down + power buttons until you see the Alcatel logo then release the power button. Type fastboot flash recovery recovery.img to flash your stock recovery. That should solve your TWRP problem.

What model of the Pixi 4 do you have?
[Android General] dimspace:
Just looked. Its Qualcomm. MSM8909

Its higher spec than the standard 4 (6) - 16gb storage, 1408 ram
[Android General] DarkShadeX:
I'm wondering, would it be possible to port Cyanogenmod for the 5050D?
[Android General] kevios12:
Its orking i think, can you now flash zips ? From latest mine recovery twrp edit? I think reflash stock rom with update tool and try new twrp or?
[Android General] DarkShadeX:
Nope, i can't do a backup as well, same error as before.

fork error when it tries to dump/backup the system.
[Android General] kirito9:
Do you mean the Pixi 4 (5) ROMs? If so then no.
[Android General] Ridertyy2016:
So,the Alcatel Pixi 4 (5) custom rom and spft rom is only for Alcatel Pixi 4 (5) 5045D?
[Android General] Charles IV:
java 8, boot.img didn't work, flashing stock now.

Should i try and do anything with the Doogee X5 device and vendor tree?
[Android General] kirito9:
There's no need to do anything with those trees as they've already been adapted to the Pixi 4 (5) but if you feel to modify to work with the 4034 then you can do that.

The kernel compiled already? o.O. I'm talking about cloning the kernel tree and getting the zImage-dtb and replacing that in your boot.img. Not flashing any random boot.img.

Use Java 7 to avoid anymore errors.
[Android General] kirito9:
I'm lost. What device do you have? State the model #.
[Android General] Ridertyy2016:
Alcatel Pixi 4 (5) 5045T
[Android General] kirito9:
Ok, I think you're asking if you can use the 5045D ROMs on your 5045T...right? If so yes you can but take a backup first of your 5045T ROM because there's minor differences in the A/D/T versions.
[Android General] Charles IV:
struggling to upload build.prop, so here's a github gist

sorry, i'm confused about

1., what kernel tree, 2., how do i do i replace the zImage-dib and replace that, and why?

finally, is there a way to use java 7 for some build's and java 8 for others? (i need java 8 for grouper). Also, i thought cm13 wanted java 8, not 7. I've stopped the build errors with the LOS instructions for fixing jack.
[Android General] NoahS:
I have the 5'' 4G model.
[Android General] kirito9:
According to the line here, you're using the wrong defconfig and your device is indeed 8GB internal and 1GB ram. That could be why the CM13 ROM doesn't boot when you compile it because of the wrong defconfig.

This kernel tree/source. Compile it separately and you will get a zImage-dtb. Take any working ROM that you can boot into. Get the boot.img of that ROM and unpack it with CarlivImageKitchen. Replace the boot.img-kernel with the compiled zImage-dtb(rename it to boot.img-kernel) and flash the repacked boot.img with TWRP.

I usually use

sudo update-alternatives --config java

to switch java versions. I installed Java 6,7 and 8 so I switch between them to use what I need them for. I build TWRP in CM13 with java 7 and it works fine. So you can probably try that seeing that you have the grouper to work with, just switch the java versions.
[Android General] kirito9:
I believe you're looking for this - https://xdaforums.com/showpost.php?p=72283356&postcount=1741.
[Android General] NoahS:
Yes, thanks!
[Android General] Charles IV:
ok, just quickly before i do anything else, i will try using the other defconfig, however my device most definitely has 0.5 gb ram, 4 gb internal, the stock rom i am using is the one on this thread, and is probably not correctly configured for my exact device, you can see it says the device is 4034X, however my box says 4034X

also on gsmarena under memory,there are 2 options for internal
[Android General] kirito9:
Yes you are correct, hmmm. Try using the other defconfig and see if it'll boot. I don't why Alcatel can't use a better naming convention :eek:.
[Android General] NoahS:
I can not seem to find a custom recovery for the Alcatel Pixi 4 5'' 4G model....
[Android General] kirito9:
Here you go - https://xdaforums.com/showpost.php?p=69884357&postcount=672.
[Android General] Charles IV:
yes, can somebody PLEEEASE tell alcatel to use a better naming system. You get the pixi 4 model, and that's got different models 3.5", 4" etc, and then those have different models!, and then sometimes I'm sure those models have variations that dont even have names!!!

It drives me crazy!
[Android General] kirito9:
It was the same for the Pixi 3 line they had before smh.
[Android General] Charles IV:
ok, so ill try the z image thing, but im going to need a bit of help, so I'll probably edit this post with problems as i run into them as to not flood the thread.

I'll begin downlaoding carliv kitchen etc, and my kernel source is pretty much the same as yours, i just moved /kernel into the root, so this is what im going to do first (plz correct me if im misunderstanding)

cd ./kernel/tcl/4034X
mka clean
export ARCH=arm
export CROSS_COMPILE=/media/charles/HDD/android/4034X/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-
make pixi4_4_defconfig
make

this should mirror the buildkernel.sh you made, and ive used it before

quick question, which tree do you use to build twrp for 4034? is it on androidmediatekrecoverydevelopment?
[Android General] kirito9:
Those commands are correct. I use this tree to build TWRP.
[Android General] Charles IV:
its building now. I saw that tree, and assumed you had built twrp on it, but now only use it for ctr, because the twrp.fstab isn't the correct partitions, or is it for another device?
[Android General] kirito9:
The one for omni is only for twrp. The one I linked you to is for ctr and twrp. What do you mean not correct partitions?
[Android General] Charles IV:
On the CTR fstab, the partitions are Dev/block/m...19 etc, in twrp they are Dev/block.../.../by-name/system

I probably mean mountpoints.

pleaee excuse me. i read back and i think ive done it. now just to flash to my phone
[Android General] kirito9:
Not a pain at all, I understand coming from Nexus with Qualcomm is a bit difficult. We're all here to learn. TWRP and CTR can use both partition naming (blk0p19 or name/system). I haven't updated that repo with the one on my local storage (it uses name/system).

Backing up your current boot.img

Install Flashify and click ACCEPT as well as allow root.

Press the BACKUP/RESTORE tab.

Choose the option to Backup current kernel.

Set the destination to Sdcard or wherever you prefer.

Click on BACK IT UP and that's it.

Copy it to the PC and place it in the CIKA folder.

Rename the file you copied to the PC as boot.img

Using CIKA

Extract the .rar/.zip file you downloaded and place it at the root or anywhere you want.

Go to the folder and open a terminal inside it.

Type inside of the terminal:

"./carliv" or "bash carliv" without quotes

Type the letter B and hit enter.

Type the number 1 to select it and also 1 again to unpack it.

After unpacking, take the compiled zImage-dtb and rename it to boot.img-kernel.

Copy it to your unpacked boot.img folder and replace the current one.

Go back to CIKA and repack using the number 2.

Flash with either TWRP or Flashify to test the compiled zImage-dtb works.

NOTE: You will lose root after flashing the boot.img so you'll have to reroot.

Edit: Just seeing your edit after writing up this nice tut.
[Android General] Charles IV:
[MENTION=5515628]kirito9[/MENTION] it worked!

I'm going to see if it reboots, but otherwise, now what?
[Android General] kirito9:
What do you mean by reboot? If it worked then the problem is building the kernel with the ROM as in the configs in the BoardConfig.mk I'll ask around and see if I can figure it out. I've never done it since I always use prebuilt kernel.
[Android General] Charles IV:
sorry, one of my problems is that the device runs out of ram and reboots - i got this on the cm13 port, and i think its because it thinks it has 1g ram not 0.5g.

i hope my kernel (if i ever boot it) won't have this problem, but i can only assume its because the port was built for 1g ram.

the repacked boot.img boots, but it still runs out of ram.

the main problem is, yes, the fact that the boit.img i build with the rom doesn't work, i assume this was a test to find out where the problem is, but i just wanted to do some side testing.

if you ever find anything, feel free to make a pr (and tell me here if i dont merge it) and I'll probable make you a contributor as it makes things easier and gives you more credit.
[Android General] kirito9:
Ahh, I see now. It made sense to test to see if building with the 512MB config would work. I figured out what else is needed to build the ROM with the kernel and will send another PR when I've figured it out.
[Android General] Charles IV:
Oops, didn't notice that. I've commented on it as I would rather build from source than it prebuilt
[Android General] kirito9:
Merged the other commits?
[Android General] Charles IV:
Sorry, I haven't merged any yet. As soon as you get the build errors fixed, let me know, and I'll merge and build. If you have a device to test it on, I imagine you'll do that, but otherwise, if you can upload something to somewhere for me to test to save time feel free, but don't worry if it's too much hastle.

I will check everything out when I can, which may be a long while, sorry.

All this switching platforms it confusing me!
[Android General] kirito9:
Sure, will do.
[Android General] kirito9:
[MENTION=7211583]Charles IV[/MENTION] I figured out the problem with the build. It was because I had a dirty kernel source which resulted in the error

/home/kirito9/cm13/kernel/alcatel/4034/include/uapi/asm-generic/int-ll64.h:11:29: fatal error: asm/bitsperlong.h: No such file or directory
#include <asm/bitsperlong.h>
^

If you get this, go to the kernel source and export etc etc and run make mrproper. Then it should be able to compile with the ROM.

Edit: See my gist to see the successful build of TWRP with the kernel source.

I'll make a full PR with the changes. You can ignore the other 2 since you haven't merged them.
[Android General] Charles IV:
It's booted!
[Android General] clorrg:
Are the instructions for Alcatel OT Pixi 4-7 3G (9003) applicable to the 8063/wifi only model?

Thanks.
[Android General] kirito9:
Excellent!
[Android General] kirito9:
What chipset is the WiFi model? Do you already have a custom recovery?
[Android General] clorrg:
Thanks for your reply.

Chipset is MediaTek MT8127.

No custom recovery.

Cheers.
[Android General] kirito9:
OK, do you have a backup of your stock recovery? I can make a custom recovery for you.
[Android General] clorrg:
No backups, I've just opened the box of the tablet. I'll try and figure out how to create a stock recovery backup without root, any suggestions?

Thank you kindly for your help!
[Android General] kirito9:
There's an option to use Miracle Box or GSM Aladdin to make a backup without root. Those links are on the first page of this thread under Useful Links.
[Android General] clorrg:
Excellent, thanks for the nudge in the right direction. Will get back to you once that's sorted.
[Android General] Charles IV:
hmm, i was puzzling over the multi user guest problem, although this time i had the sense to allow adb etc before i got locked out

i tried adding

fw.max_users=3
fw.show_multiuserui=1

to build.prop, although this didn't solve the issue, allow me to switch, or show the option in settings.

i also tried

pm list users

in shell, but it returned

Users:
UserInfo{0:eek:wner:13} running

i also tried creating a user with

pm create-user test

, although that returned

Error: couldn't create User.

, even after running 'su'.

maybe the issue isn't that im logged ina s guest, but that still doesn't explain why i can't create users. I'm stumped.

I'm also getting a bluetooth problem, but as they've solved similar problems before over there, I'll probably put it on the cm for mtk thread.

thanks for all your help!

edit:

more hmm:

pm get-max-users

returned

Maximum supported users: 1

, even after

setprop fw.max_users 4

was run.
[Android General] Keiko87:
Wow thx Kirito you still not updated the 8050D stock rom i provided month ago, ..

I make an new Thread and update the list, because the cm12 stuff is bug bug bug'd as hell, why offering non-working cm roms ?... i mean the whole libs are just overwritten with various Pixi libs, unfixable camera for certain Pixi 4xxx > 80xx builds..etc and an worseless build.prop inside th rom :mad:

How about bloatware free Pixi stock roms ?

I have done that at my own stock now, after much research, studying & trial & errors.. remembering that you said once,.. that its impossible to vanish the custpack folder &.IMG..because its a IMPORTANT part of the rom !?

:silly::eek: ofc, chinese NSA Spyware,bloatware mirroring of system files to have full control of pixi users.

humm just block some permissions and disable some system apps and u can delete 98% the whole custpack content, just not the framework stuff, (me) you have to modify yourself. :victory:
[Android General] jie_gonza:
Camera still show red/pink filters:crying: what should i do?

And i have a big problem here, yesterday i tried to flash spft rom but cant included or tick preloader spft will show error. So, i untick the preloader and flash. When my phone boot it stuck at pixi4 logo. Help me please:crying:
[Android General] Charles IV:
I'm not entirely sure of your situation, butcan you wipe cache/dalvik?
[Android General] jie_gonza:
1st, i copy the .lib file from stock rom then i paste it on my phone system .lib file. After that i reboot to recovery to wipe cache/dalvik. When i open camera still show red/pink filters.

Then, i tried to flash spft rom to go back to stock rom but stuck at pixi4 logo
[Android General] Charles IV:
did you wipe the correct partitions before flashing?
[Android General] jie_gonza:
What partition:confused: can you show full instructions?
[Android General] Charles IV:
sorry, im not entirely sure what spft roms are, but i assume the partitions you wipe are just like any other rom. see if [MENTION=5515628]kirito9[/MENTION] has made any guides for your device, but usually you flash dalvik, cache, system and (usually, but back it up if you dont want to loose it) data.

edit-

as to wiping, the other guides tell you what you need to wipe (although i did notice that there wasn't one specifically for the spft rom), did you remember to do that before flashing the spft rom?

i also noticed note 2 in the op, so have a look at it, and i assume coming to spft, you wipe your device, but while actually running it, dont format.

also bear in mind kirito9's note about the spft roms, sometimes causing more problems than solving.