yashsingh1/xdaforums huggingface dataset:
[Android General] Buthmann:
I modified proinfo via notepad++ and changed to 4034E.

I wish it will fix it.

Thanks, I love all your custom roms and this thread is amazing. =)

Cheers
[Android General] kirito9:
You're welcome. Let's see if that works.
[Android General] hectus:
now it seems like i have a issue wiping my phone with twrp, keeps telling my unable to mount /data, and if i factory reset i still see all the old stuff there. Should i attempt to format it? also, should i install the cm13 image from zip, or as image? i tried both but i cant get either to work yet, if i do it as image, i get the option, boot, system and something else wich i dont remember at the moment, what should i do?
[Android General] kirito9:
Format the data partition and install as zip.
[Android General] hectus:
Oki thanks, that worked

Seems im getting there slowly, lol. I downloaded the gapps mini package, but it tells me i dont have enough storage to install it, is there some of the internal storage i havent freed up or something?
[Android General] Buthmann:
It happened to me. I just reinstalled stock rom via spft, setted my device up all again, went to developer options and marked oem unlock.

Did all the adb commands and fastboot, done.
[Android General] kirito9:
It's system space it needs. Use nano gapps. I was there once i understand.
[Android General] Buthmann:
Well , it's me again ... Does anybody know ot-4034E pid ?

Could anybody upload a "proinfo" image for 4034e ?
[Android General] dwl99:
I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery (is TWRP_3.0.0.2_Kirito9@Mod.By_Kevios12_v2 or ctr-6.6-4034 the best one?) but I'm rapidly losing the will to live and would be very interested in any suggestions.

UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM, flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.
[Android General] sipe1:
Bump. Thanks in advance who can help me!
[Android General] hectus:
Hi again

Phone is now up and running and working good, however a couple of questions.

The simcard signal appears to be very low, at a bar or so, but if i go into the phone and compare the db to my other phone, its approx the same. However, the other phone says i got hdspa, the pixi says only hspa. I see i can go under sim card and change some of the baseband settings, but the options are greyed out, any way i can change any of this anyway? and that the signal bar in notification area shows only 1 bar, is that a bug?

Another thing is, incall volume and ringtone volume appears to be lower than it was on stock rom, even tho its turned up full. is there anyway to boost the volume?
[Android General] Charles IV:
also edit build.prop etc, and try to use mobile upgrade tool to see if it recognises your device correctly
[Android General] Buthmann:
After downloading several proinfo images and editing... finally =)

No more signal loss roaming around Rio de Janeiro =)

Thanks =)

It was really a proinfo problem.
[Android General] hectus:
Another thing im noticing is the speaker on the back of the phone aint working, i assume thats why the volume feels lower. Is there anything i can do that? it doesnt work even when playing music.

Thanks again
[Android General] Charles IV:
probably an issue with the rom, have a look at reply's to a different, but recent problem

---------- Post added at 07:14 PM ---------- Previous post was at 07:06 PM ----------

[MENTION=5515628]kirito9[/MENTION] i am having issues with the kernel you supplied me (https://github.com/kirito96/android_kernel_tcl_pixi4-4/). I am unable to build it by make bootimage at croot, make pixi4_4_defconfig at kernel root, or the scripts provided in kernel root. They all give a similar error similar to 'no rule to make target' and this will include the config file, and even 'clean'

i'm clueless

-edit-

i moved the scripts to ./kernel from the kernel source and edited them to my file structure (im not working in the home directory, but on a separate HDD) and they worked.

This leads me to a question that the contents of ./kernel is usually the root of other kernel structures, and ./boot is not present, or elsewhere, so why is this structure different?
[Android General] hectus:
i thought there was a speaker on the back of the phone, apperently its not. I been trying some volume booster apps but they doesnt seem to work very well, so i was looking for the mixer_path to edit under /system/etc, but apperently its not there on this build. Anyone know where to find it or how to manually edit and boost volume a little?
[Android General] kirito9:
I'll ask a friend who has the Pixi 4 5" to get that for you. Here [MENTION=5691078]ZonaRMR[/MENTION].
[Android General] kirito9:
I think the Viper4android app works but I haven't tested on LP+ android versions. The low signal is a common bug in mt6580 custom ROMs. A user posted the fix in the MT6580 development group. I'll post the fix here once I find it. If an option is greyed out it's probably because the phone doesn't support it or it could be another ROM bug.
[Android General] kirito9:
Probably replacing some audio*.lib files from the stock ROM.
[Android General] kirito9:
Yeah, you had to edit the structure etc because my build environment would be different from every other user. Which branch are you using btw? The test branch is under construction. Use the master branch. I made the ./boot | boot folder there so it would be easier to repack the boot.img without me having to edit it manually. You can completely change the structure as this isn't usually how it is and upload to github the way you would like it.
[Android General] kirito9:
There should be an option in the engineering menu of the phone. I not 100% sure CM works with engineering mode but you can always try. MTK Engineer Mode, download and install it. Go to MTK ENGINEER MODE --> slide over to Hardware Testing --> Audio --> Normal Mode/Headset Mode/LoudSpeaker Mode and edit as desired. Do not increase it to the max setting!
[Android General] hectus:
Hiya, thanks for ur help again. seems cm doesnt have a engineer option, mtk says cant find it or something like that.

do u happen to know where the audio lib is located?
[Android General] kirito9:
If you made a backup of the stock firmware with twrp then you can restore it. Then using a root explorer and go to the root directory then go to system/lib/hw and system/lib.
[Android General] hectus:
Oki thanks, i will give it a try.

Any luck in finding that low signal bug fix?

Thanks again.
[Android General] kirito9:
Edit this line in build.prop - ro.telephony.ril.config=signalstrength.
[Android General] Charles IV:
Thanks, i think I'm using the master branch. I can't use make bootimage in croot right now, so I'll try changing the structure, but if that doesn't work, do you have any idea why it isn't working? I'm trying to make the 'kernel' file.

I managed to make boot.img with your scripts and copying the defconfig from /arch/arm/configs/ to /arm/x86/configs/ which worries me because it makes me think there will be an error later, or it's not the correct kernel
[Android General] paktam13:
Install twrp

This twrp work on 5045T?.

Right?

The installation can follow this link right?

https://xdaforums.com/showpost.php?p=69884357&postcount=672

Last but not least.

How to install​ Xposed on 5045T.

Thanks in advance
[Android General] kirito9:
Yup, it works and get xposed for marshmallow.
[Android General] kirito9:
Why you copied to /arm/x86/configs? Is it because the environment you're building on? The boot.img script would work but I think that's a kernel I compiled before, or it's the kernel getakgt built. The only thin you should edit really is the scripts according to where you have the directories, nothing else.
[Android General] dwl99:
Anyone have any problems getting the GPS to work with CM13? I've run GPS Info Pro and it tells me there is a GPS sensor but it doesn't seem to be able to get a fix.
[Android General] Charles IV:
the reason i copied them is because when i ran the scripts, they ran make, and that looked for configs in /arch/x86/configs, and the makefile was too long to correct. when i moved them it worked.

I'm copying the contents of ./kernel to a new kernel folder, to make the layout the usual layout that you would find, and I'm going to run lunch and make bootimage from croot again so we can have a look at the error

---------- Post added at 06:03 PM ---------- Previous post was at 05:53 PM ----------

heres the pastebin of the log: https://pastebin.com/msiRnG2r

i think it might be an error with TARGET_KERNEL_CONFIG in BoardConfig.mk, so I'll mess about with that, but there's the error

(yippee, 100 posts - but- 99+1=100, not 99. oh well)

-update-

following cm's guide, i had TARGET_KERNEL_CONFIG pointing to the file, including the directory, but i only needed the filename, so i changed it, and i got a different error. will pastebin it

its here: https://pastebin.com/pmSf5htd
[Android General] kirito9:
You can't reconfigure the kernel source structure, that would require modifying a lot of files.

Are you trying to build CM13 ROM along with the kernel? That's what it looks like you're doing. If not then that is not the command to build the kernel. You should build the kernel separately, prebuilt image (zImage-dtb/zImage) works for the building CM13. If TARGET_KERNEL_CONFIG is in the BoardConfig.mk then that means that is what mishurov used. You don't have to use that.
[Android General] Charles IV:
about editing structure, i just moved ./kernel to the root of a new folder and renamed folders (so kernel root is now /kernel/tcl/4034X/ rather than /kernel/tcl/4034X/kernel), so it is now similar to the structures you see on github.

mishurov didn't use TARGET_KERNEL_CONFIG, but i did because the old cm porting guide said to, and when i didn't originally, i got errors, so i added to try and fix them

(this must be my 100th post now)
[Android General] kirito9:
I think you're over thinking this entire thing. Don't use the old CM guide. It's outdated and not exactly for mediatek. There really isn't a guide for mediatek in building ROMs as there is for Qualcomm.

Are you trying to build a kernel or ROM? If kernel, use what is there. If it builds then you can see where the errors were and then modify. If ROM, visit the cyanogenmod for mediatek devices thread and ask there, they're currently working on mt6580 there.
[Android General] Charles IV:
I have noticed a problem with the pixi 4 4" that i didnt notice before. It is randomly rebooting, even in safe mode. While it's not actually random, it's always after a similar amount of time. I went into developer options and then running services. After a reboot, system is taking up about half, and apps a quarter. Every time a watch the system grow, and the apps shrink, until its at about three quarters system, an eighth apps. system continues to grow, apps shrinks to the smallest it can with me still having settings open, before rebooting. The time it takes for it to reboot, with me not using it and screen off is longer. I have reverted everything recent that i have done to it (editing build.prop, auto fstrim) however it continues. I said i hadn't noticed it before, and i hadn't. But it usually sits quietly in a draw without me looking or even checking up on it, so it may have been happening all this time, which would explain the fast battery drain, even with aggressive doze (and almost all apps hibernated with greenify).

TL;DR: pixi 4 4" - system using up all the ram until the phone reboots
[Android General] hectus:
I used es explorer with root acess to edit this, but when i save, and after i restart the phone, the setting is changed again. Any idea why or what to do?
[Android General] kirito9:
Probably doesn't have fill write permissions. You can edit that line before flashing the ROM.
[Android General] kirito9:
Did you try reflashing stock or were you talking about stock?
[Android General] Charles IV:
i suppose there's always that, but i didn't want to go that far

factory reset fixed it
[Android General] bako1980:
Hello to all of you,

I am very new here, i have a question

I have a Alcatel pixi 4 -5 3g. And i just received the message that the update 6.0-01005 is available for download and install.

So i downloaded it and tried to install it, but i get the message after it restarts

""Supported API: 3

Opening update package…

The update.zip is corrupted

Installation aborted.

OTA failed! Please power off the device

to keep it in this state and file a bug

report!""

Can anybody helpt me with this?
[Android General] kirito9:
Do you have a custom recovery installed?
[Android General] bako1980:
What do you mean by custom recovery? What is that?

I have updated my phone succesfully to ***1003 before with no problems.

I have no knowledge about phones and android whatsoever....
[Android General] kirito9:
Probably a corrupted download since you don't know what is a custom recovery.
[Android General] Dizzye96:
External SD Card not detected.

Hi, I installed CM13 ROM for Pixi 4 5010, well everything works fine, amazing.

The only problem is that it don't detect the external card. Well, it actually does, I used AParted app, but it only allowed me to format it as ext4, ext2, fat32, swap etc. I tried all types but nothing worked.

Is there a way to resolve this?

Just to know, the card is detected and works on other devices.

Please help.
[Android General] Buthmann:
[IMG="bug"]http://i.imgur.com/T4VKAh9.png[/IMG]

Hello again. LOL

I'm using cyanogem and it's working great now on my 4034e

Except this YouTube video bug....

It happens in WhatsApp too.

I've reflashed and wiped several times , but i cant get it working.

Any suggestions
[Android General] Zer0Bytes_:
my phone is running on 01003 update theare is 01005 for 5010D i have a update.zip of that update i tried to flash that it gives me a error sooo idk how to install it
[Android General] kirito9:
[KERNEL][MM][3.18.19+]Alcatel Pixi 4 5" 5010[ver 1.0][04.05.2017]

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.

The kernel is based off latest sources from Alcatel sourceforge and should be compatible with all versions of the Pixi 4 5".

Features

None for now ;)

Based on stock source from Alcatel (OT_5010D_20170407.tar.gz)

Changelog- 04.05.2017

Version 1.0

Fixed Alcatel include tag errors

Initial release

Download

Version 1.0 - MEGA or download from the attachment below.

Installation

Copy the KernelMM-Pixi4_5010.zip to your sdcard or internal.

Boot into your custom recovery mode and make a backup (to be safe).

Go to install/install zip and locate your zip file.

Flash and reboot

Enjoy!

Credit

[MENTION=5691078]ZonaRMR[/MENTION] - Testing,making the flashable zip and screenshots.

Source

https://github.com/kirito96/android_kernel_alcatel_5010
[Android General] kirito9:
Do you still have root and a custom recovery installed?
[Android General] Martin1307:
Probability of compatibility with Pixi 4 4" ??

Hi Kirito,

ref your post [KERNEL][MM][3.18.19+]Alcatel Pixi 4 5" 5010[ver 1.0][04.05.2017]

Cool!

Do you think this is likely to be compatible with the Pixi 4 4" ? ?

I'm happy to give it a try when I get time - just wondering if you think it is a definite 'no no' or if it is worth a shot ?

I'm happy bricking the device to find out, but would like your opinion.

thanks and Best Regards

Martin
[Android General] kirito9:
Definite no no. I'll clean up the Pixi4_4 source and make a flashable zip soon. I'm working on building ROMs for Pixi 4 mt6580 devices now as they are bugless.
[Android General] kirito9:
[KERNEL][MM][3.18.19+]Alcatel Pixi 4 4" 4034[ver 1.2][31.05.2017]

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.

The kernel is based off latest sources from Alcatel sourceforge and should be compatible with all versions of the Pixi 4 4".

Features

Based on stock source from Alcatel (OT_4034D_20161023.tar.gz)

Thundersonic Engine

FIOPS, BFQ, CFQ, deadline, noop, zen, and SIO I/O schedulers

Option to disable fsync

Changelog

Version 1.0 (5th March 2017)

Fixed Alcatel include tag errors

Initial release

Version 1.2 (31st March 2017)

Add Thundersonic Engine by varun.chitre

Add FSync and make it toggleable

Add AnyKernel2 support

Add I/O Schedulers

Sio

Fiops

Zen

Add CPU Governors

Smartassv2

ThunderX

Alucard

Download

Version 1.0 - MEGA or download from the attachment below.

Version 1.2 - MEGA | AFH

Installation

Copy the BT**.zip to your sdcard or internal.

Boot into your custom recovery mode and make a backup (to be safe).

Go to install/install zip and locate your zip file.

Flash and reboot

Enjoy!

Source

https://github.com/kirito96/android_kernel_tcl_pixi4-4
[Android General] Martin1307:
Hi Kirito9,

Ok. your intention is music to my ears :D

It is my understanding you are working with Alcatel source (is that correct?) and should(may) include the features like "timed power up" - which was a feature of my phones before I messed with them. (doh!)

May the 4th be with you

Martin
[Android General] kirito9:
Hmm I am indeed working with Alcatel source but I've never heard about that feature before. Do you have a reference link that I can check.
[Android General] Martin1307:
Hi Kirito9

No link, but all 3 of the pixi 4 4 phones I have messed-with had the feature out of the box. It was v cool. I had visions of being able to use the feature for practical jokes and stuff(long story).

I will look for evidence, but I absolutely 100% used the feature for a few tests. The phone would boot from cold at the appropriate time.

ahah! - found some info - See the section "10.4.2 Scheduled power on & off" in the attached (zipped)PDF (i think its attached)

cheers

Martin
[Android General] kirito9:
Hmm, I will also do some checking and see if it was a kernel feature or ROM feature and try to add it.

Edit: I'll look through the PDF and have a look at what you're talking about.
[Android General] Martin1307:
What's where Rom/Kernel

I'm intrigued. I assume that it's at the same level as the firmware that listens for the power button to power up the phone, but knowing so little about the architecture I'd be keen to understand 'what's where' in Rom and Kernel in the Android universe. - do you have any pointers for where I could go reading?

cheers

Martin
[Android General] kirito9:
Ahh, I see what you mean now. This is a feature of the ROM itself and not the kernel but I'm not 100% sure. I'm still sticking to it being of the ROM itself and not exactly the kernel.
[Android General] kirito9:
Here's a very in depth guide about android building from start to end. This guide is to help understand the android source code which is what I'm hoping you asked for and I provided the correct information heh. Any questions you may have, feel free to ask.
[Android General] Martin1307:
Cool, thanks. I'l do some studying.

I've been thinking on it and (in pseudoengineer speak) there have to be some points of interface from the OS through the power management bits of the Kernel and into the hardware/firmware - such that the clock can 'push the power button' when the 'saved target time' matches the clock time - triggering a wakeup from cold - up through the bootloader.

So this...(going out on a limb) may be the reason the bloody thing doesn;t like being rooted - the hardware/memorymap has some sensitive spots that aren't on other phones -specifically the registers that hold the wakeup times. - but that really is thin in terms of my knowledge (lack of). :-/

all the best
[Android General] kirito9:
That's actually one of the scenarios of how the "timed power on/off" works and I must say well done. I haven't thought so far into it but that can help to pin point where exactly the code is in making that feature work. It'll probably be in the power driver of the kernel. With regards to rooting tho, I'm not too sure that specifically would be the reason as if that was, bypassing that would've been a piece of cake to the senior devs here at XDA. New versions of android are harder to root because of the security features Google keeps adding to prevent modification. They have certain checks in place that would alert the system if you are trying to root or it has installed a modified boot.img. It's all for a good cause but I think the power users would know what they are doing and wouldn't make such a silly mistake.
[Android General] bako1980:
Hi kirito9,

Thank you for your response.

So is this file the same as the update 6.0-01005 ?

I am a nobody at these things so forgive me if it is a stupid question.

Yours,

Barry
[Android General] kirito9:
That file is the stock kernel (what makes the device function) and not an Over the Air(OTA) update. So no, not the same as the 6.0-01005 update.
[Android General] evan5935:
[MENTION=5515628]kirito9[/MENTION] hey been busy and I forgot to respond but I tried the rowhammer apk and wasn't successful in rooting my pop 7 LTE but I also haven't had a computer to use the exploit to its fullest potential. Side question would one be able to install gnuroot, install Linux and gain root from within Linux on the device itself?
[Android General] kirito9:
That idea might actually work, I'm looking at this project KBOX2 (http://kevinboone.net/kbox2.html) and it sounds interesting. The idea of using gnuroot lead me there so thanks. Another possibility of root on android devices.

From the site:
[Android General] evan5935:
[MENTION=5515628]kirito9[/MENTION] I got the idea while looking back at old ps3 jailbreaks and came across geohot's original jailbreak which involved installing Linux on the ps3 to obtain master key to the system, with which he used to create the first CFW and software jailbreak for PS3
[Android General] kirito9:
Good thinking, I'm trying to set it up on my older android device as KBOX2 doesn't support 5.0+. If it works then I'll provide instructions to use KBOX3 for 5.0+ devices.
[Android General] Barbiox Dogg:
[MENTION=5515628]kirito9[/MENTION] Can I use Kingroot to root the Pixi 4 (5) 5010U ?
[Android General] kirito9:
It has been done before by one person so give it a try. You might have to wait until an exploit has been found or the requests made.
[Android General] Barbiox Dogg:
Thanks for the quick reply. Please what's the difference between the 5010G and 5010U ? My phone is the 5010U.
[Android General] kirito9:
More than likely the dual sim feature. Single sim models are usually G/A/X etc while dual sim models are E/D etc. I'm not sure about the "U" tho. This could be single sim. There may be other small differences but I'm not sure of what they are.