yashsingh1/xdaforums huggingface dataset:
[Android General] kirito9:
You sure love your colors :silly:. I have a friend that tried to do this and it resulted in a somewhat buggy ROM. The browser wasn't working and the application that manages the SIM card. I'll see what I can do. I would need the stock image of the Pixi 4 (6) however.
[Android General] stryker1968:
Hey dude its not 5054T firmware that im looking for. Its "5045T" firmware.
[Android General] kirito9:
Sorry I made a typo. Here is the link.
[Android General] stryker1968:
I looked the link you gave me dude. Can i flash this to my device 5045T? Coz i have already this firmware but every time i flash this it gives me an error.

---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------

Thanks though.
[Android General] kirito9:
What error do you get?
[Android General] stryker1968:
Wrong format range.
[Android General] Charles IV:
Just to double check, is allow oem unlock ticked in developer options?

And I forget what it is, but there is a fastboot command that tells you if the bootloader is unlocked.

Run fastboot help, but it may be fastboot get unlock ability? - sorry, just realised that is what you ran, ignore that bit

Edit.

Also, I imagine you are on stock ROM, because only stick recovery works. Are you able to try a different ROM?
[Android General] Charles IV:
well, ive finally managed to build for my device without any errors, however twrp gives an error about mounting something as system, and i can't find the file that tells the rom where to mount what as what. I also noticed the phone has many strange partitions such as protect_f and protect_s, and i probably need to include these as well.
[Android General] kirito9:
Any twrp logs? And build what? TWRP or a ROM?
[Android General] Charles IV:
building rom.

The recovery log is a lot longer than what i saw on screen, but it is attached

I think it all starts at about line 716

could it be because the device thinks it's not 4034X, but 4034something-else, so it's rejecting it?
[Android General] Keiko87:
May it work with some "ro.force.uninstall.xxxx=1" & "ro.force.disable.xxx=1 ?? or Prop mods like that ?

Or its possible to put the com.xxx.BBBB to the disabledapplist.xml ?

Btw. Yesss i Love my [/COLORS] :laugh::highfive: You too ? :p

Stock Rom (editable) pw: hamasaki12

All the Apk's of the Rom archived

Your old modfied Pixi 3-4 build.prop

Offtopic: Could this be interesting ?

https://xdaforums.com/android/help/mount-mod-partitions-inside-android-apk-t3610037
[Android General] Anon-E-Mouse:
I've just spent 3+ very frustrating hours trying to get either Miracle Box or Aladdin to connect to the phone. Despite my following the guides directions to the letter, and installing all of the MediaTek VCOM Drivers (both altogether, and one at a time), neither program will connect to the phone regardless of whatever settings are used, and yet adb and fastboot work.

After being asked if I want to unlock the bootloader, you press Vol Up, to unlock, then the phone says it's going to reboot to fastboot mode. Upon reboot I get..

Select Boot Mode

Vol Up to Select, Vol Down to OK

Recovery Mode

Fastboot Mode

Normal Boot

Selection is pointed to Fastboot mode, but none of the buttons worked on the phone, and I had to yank the battery to restart. Upon restart, I get the Android robot with the swirly dodecahedron, and the phone factory resets to 'new'.
[Android General] kirito9:
Can I see the updater-script of the ROM? This is usually found in the META-INF folder. Have you tried CTR recovery? It seems either the updater script has a different path for the /system or the recovery (twrp).
[Android General] kirito9:
Alright, I'll see what I can do with the ROM. The colors bring life :'). What you're trying to do (what you posted in the other thread can be discussed here. It wouldn't be considered off topic as someone else may have ideas about what you're doing.
[Android General] Charles IV:
I'll upload the whole rom for you, and the sources are github.com/Charles-IV and then android_(device/kernel/vendor)_tcl_4034X

(may take a while - too large for xda, and dont have upload access for android file host
[Android General] kirito9:
Alrighty. You built the kernel with the ROM?
[Android General] kirito9:
The miracle box/gsm backup is tricky and sometimes requires a new PC to work. I'll let you follow another guide that would get you the same images from a scatter file (attached below). Follow this guide to make a backup of the boot.img and recovery.img or the entire ROM using SPFT.
[Android General] Charles IV:
yes, and im waiting for android file host upload access, meanwhile, i will try to upload to xda again, and then crack open the zip to get META-INF
[Android General] kirito9:
You might have to open a new thread with dev db access to upload such a large file. I think it would be easier to unpack the ROM and get the META-INF folder, compress and upload.
[Android General] Charles IV:
here is meta inf
[Android General] InfernoShark:
I came across something in my user guide that says, "This device is unlockable" and to check TranFone's website for info. Is there more than one type of unlocking? Haven't checked the website though. :\
[Android General] kirito9:
They're probably talking about SIM unlocking. Unlocking in android generally refers to SIM.
[Android General] kirito9:
Did you test the ROM with CTR recovery? Also try flashing the ported CM13 and get the twrp log and attach it here as well. META-INF seems to be fine. Another thing, in the TWRP menu under Mount, what does it say for system?
[Android General] Charles IV:
I'll check when I get home, and try CTR probably at weekend, when you say 'ported cm13', do you mean the one uploaded on this thread, so I try mine and the one here?

CTR makes sense to try, as it's possible cm doesn't like twrp.

Actually, on your lineage OS 14 test, which I forked, I forget what, but it was something like a flag in boardconfig, target_ota_assert_device, and it was set to a list of 4034 models, could I be missing this, shall I try adding the model I want, the twrp model, and the stock ROM model? (I'll see if I can find the flag)
[Android General] Keiko87:
Mount & Mod Partitions inside Android-System Apk itself ?! /w Screenshot

Just found this inside my Android-System Apk.. dunno if its just an information xml or the TRUE thing :victory: :confused:

=======Attached the .xml file below=======​

[IMG="Mount & Mod Partitions inside Android-System Apk itself ?!"]http://abload.de/img/mountpartitionsinsidebijvc.jpg[/IMG]
[Android General] Charles IV:
ok, twrp calls it System. Will edit this post with my progress. Currently downloading ctr and cm13

I've attached the log for the port.

about ctr recovery, it can't find a zip on internal storage, and when i try sideload, adb devices returns ??...?? no permisions and adb sideload with the normal zip returns cant read <zip name>, and with the ota zip, returns insufficient permissions. Going to flash twrp back.

tried flashing my own again, with twrp 3.1.0, and it says this package is for device 4034,htct5...,Pixi4-4; this device is 4034

Im rebuilding with target_ota_assert_device, and I'll see how that goes

And I've just found, in by device.mk:

TARGET_OTA_ASSERT_DEVICE := 4034X,hct6580_weg_c_m,Pixi4-4

I'll remove this and stick with the one in BoardCOnfig that I commited
[Android General] Itachi879:
Vodafone VFD 1100

Hi. I have the TCL VFD 1100 that has the same hardware as the TCL Alcatel Pixi 4 (7) 9003. I want to know if this will work if I flash it on my phone.

Thanks
[Android General] ludia2210:
pixi 4(7)

Hello,

founded stock rom for SP Flash tool,maybe!!! :D

https://lahuria.com/2017/05/alcatel-9003x-official-firmware-mt6580-android-6-0/

Rom not tested!!!Explore and test it on your own risk.

And can someone to tell how convert Sp flashtol ROM_ backup file in normal flashable rom for flashtool.

Tryed with mtk droid tool,but cant convert.
[Android General] kirito9:
There's no SD Card to install the ported CM13 from? I'm still not able to get CTR to detect both storages, I made it to detect external by default.

The TARGET_OTA** searches for the model # string from the recovery, so if you build the recovery with /alcatel/4034 then the ROM would look for the 4034 match. You can either update TARGET_OTA** with the name you build the twrp image or ignore it altogether.

Did you flash the CM13 port with ctr or twrp? It seems according to the log that the mount point that works is

/dev/block/mmcblk0p19

and not

/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/system

. This also goes back to the recovery.The recovery.fstab found in the ramdisk probably uses the first method of detecting the mount point. Try comparing both recovery.fstab from the twrp you're using verses the fstab file in your source.
[Android General] kirito9:
It probably will as there have been cases in the past where Vodafone phones were clones of the Pixi from Alcatel. Make a backup before trying this however.
[Android General] kirito9:
Seems legit. Concerning the converting of the ROM_0 file. There's a Russian tool that I know of that I used before but the program itself is in Russian. If I can replicate the process with an MT6580 ROM file then I'll make a guide and post it here.
[Android General] ludia2210:
Link please,i speaking Russian:D
[Android General] kirito9:
Here you go - WWR MTK. If it works maybe you can create a guide for us :).
[Android General] Charles IV:
Thanks,

Ok, I've found device/tcl/4034X/rootdir/recovery.fstab

Where would I find the TWRP one?

Edit:

Sorry, the quote things were messed up.

I flashed the port with TWRP.

I did have an external SD card, but removed it for my raspberry pi zero. I wondered if stock and CTR recovery wanted a zip called update.zip

I also didn't realise when I was trying to

have to go, will update this later
[Android General] kirito9:
Decompiling the framework-res.apk from the system would give you what you're looking for and yes, it's possible to change the values you see there, like mount internal as external etc.
[Android General] kirito9:
If your BoardConfig.mk is set up to compile twrp by having the flags defined then it would tell you where the twrp fstab is. If not just look for twrp.fstab or edit the recovery fstab.
[Android General] Charles IV:
I'm not building twrp, so I'll edit recovery. Fstab

are there any other paths I need to add/edit?

Edit:

Have a look at this: https://github.com/Charles-IV/android_device_tcl_4034X/blob/cm-13.0/rootdir/recovery.fstab

Will I need to change all of the paths?
[Android General] kirito9:
Yeah change them like how I defined it before from

/dev/block/platform/mtk-msdc.0/by-name/system

to

/dev/block/mmcblk0p19

To find the list of the partitions bu number you can use an app called disk info from the play store.
[Android General] Charles IV:
OK, i was just looking at the recovery.fstab i pulled from the ported cm13, and found that the locations are in the same as the current recovery.fstab file in my source.

I'll install an OS and download that app, so would i change the '19' in 'mmcblk0p19'?

Actually, in the fstab i pulled, it shows:

/dev/block/mmcblk0p3 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p4 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p15 /mobile_info ext4 rw 0 0
/dev/block/mmcblk0p17 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p19 /system ext4 rw 0 0
/dev/block/mmcblk0p20 /cache ext4 rw 0 0
/dev/block/mmcblk0p21 /data ext4 rw 0 0
/dev/block/dm-0 /external_sd ext4 rw 0 0
/usbotg auto rw 0 0

(couldn't uplaod fstab file to xda)

Shall i use this?, the only problem is some are missing, so I'll have to use the app

EDIT:

found the rest of the partitions in the log, apart from the 'vold-managed volumes' (bottom two in source). There were many partition details in the log, that aren't in recovery.fstab in my source, do i need to add them?
[Android General] kirito9:
Yeah, add them as well. If it's already defined as "mmcblk0p19", there's no need to change it. If you found the other partitions in the log then the app isn't necessary. It's useful for finding out information about partitions tho.
[Android General] Charles IV:
I'm not sure though, it's things like 'proinfo', 'para', and 'lk', that I've never seen before.

edit:

and another thing, when i build, i notice it says its using prebuilt recovery and boot img's from BOOTABLE_IMAGES, apart from when i only build bootimage or recoveryimage, so i dont know whether the kernel and recovery in the rom are old ones from before i changed it to 4034 device. I couldn't find bootable images, are they just what's made during the build process?

Edit:

Great.

Can you have a look at this folder, and see what other files you think needs editing. I think ueventd.mt6580.rc might, but can you see. I should have expected this.
[Android General] kirito9:
The ROM doesn't necessarily use them but up to you really if you want to add them or not. The fstab.mt6580 file (if in your rootdir) has all these partitions so it should be fine to leave them out.

Where would it get the prebuilt img's from to use? Unless you didn't run a make clean before starting a new build. I think your kernel source isn't configured properly in the BoardConfig.mk so I'll check and make a PR.

Boot.img and recovery.img are made when making a full build so like I said before unless you didn't run make clean before starting a new build.
[Android General] Charles IV:
thanks.

To add to my most recent edit, I've just seen fstab.mt6580

As soon as i have recovered from my mental seizure, i guess all off these need to be edited. yipee
[Android General] kirito9:
No problem, no rush :). About building the ROM with your kernel, since I don't know how you have it in the CM13 source. Edit the code below to match what you have.

TARGET_KERNEL_SOURCE := kernel/tp-link/tp701a
TARGET_KERNEL_CONFIG := hq6735_65u_b1p_l1_defconfig

So it may be something like

TARGET_KERNEL_SOURCE := kernel/tct/4034X
TARGET_KERNEL_CONFIG := pixi4_4_defconfig

I think there's more but for now update with that. I'll be back with a PR once you add your correct path.
[Android General] Charles IV:
Thanks, the 5010D device tree didn't have either, and it threw me off, and i only added the config

all done now

edit:

I've begun going through fstab.mt6580, and I've noticed a few things

On line 20 and 21:

/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/lk /bootloader emmc defaults defaults
/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/para /misc emmc defaults defaults

in the recovery log, there aren't partitions names /bootloader or /misc, but there are /lk and /para, so i get that the path is the one for lk and para, however do i change /bootloader to /lk etc. or not? Or doesn't it matter, and i can change them if wanted, in which case i wont, because i understand /bootloader and /misc!
[Android General] kirito9:
Those (/bootloader and /misc) are just the name used to identify the partitions. The /lk and /para and the mount points.

Example:

#device fstype #mount point
/boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot
/system ext4 /dev/block/platform/mtk-msdc.0/by-name/system
/bootloader emmc /dev/block/platform/mtk-msdc.0/by-name/lk
/misc emmc /dev/block/platform/mtk-msdc.0/by-name/para
[Android General] Charles IV:
ok, so the lines should be:

/dev/block/mmcblk0p6 /bootloader emmc defaults defaults
/dev/block/mmcblk0p5 /misc emmc defaults defaults

rather than what they were before
[Android General] kirito9:
Yup, just like that.
[Android General] triforcebih:
Hello people

I have an old Pixi 4 (4) 4034D which now also has FRP activated and I screwed up and can't get rid of it the normal way. I can't even activate Developer Options by tapping the build number... so can't really do anything without OEM Unlock not even flash custom rec or a rom. Can anyone help? Maybe a scatter file would help my case? All the links on that russian forum are sadly dead now.
[Android General] kraolesage:
info

please i need custom firmware to Alcatel One Touch POP 7 LTE 9015B
[Android General] kirito9:
The problem isn't that the links are dead, you just do not have an account. Here you go Alcatel 40340 01004 RU.
[Android General] kirito9:
There is no custom firmware available.

Also wrong thread.
[Android General] itsfeelipe:
Did you fix the the bug in the frontal camera ??
[Android General] kraolesage:
info

Ok but How to unlock the alcatel one touch pop 7 LTE
[Android General] Charles IV:
If the bootloader is unlockable,

fastboot oem unlock

or

fastboot flashing unlock

using adb and fastboot should unlock the bootloader, just like in the guides for other devices.
[Android General] kirito9:
It's another one of those Alcatel devices with an MSM8909 chip which might not have the option to even boot to the fastboot mode. I don't know why Alcatel or carriers hide the fastboot mode for those devices :rolleyes:.
[Android General] Charles IV:
ahh, i remember on my pop c1, i could boot into fastboot by using adb, but then, when i ran fastboot oem unlock, or fastboot flashing unlock, the command worked, but nothing appeared on screen.
[Android General] kraolesage:
info

By the way the alcatel OT POP7 LTE is blocked mobile operator (SIM LOCKED) TMobile and I want to make it universal. Is this possible by a flash? And if so then I could have the explanations step by step with the list of prerequisites. thank you
[Android General] Charles IV:
If you just want to unlock the operator, i assume that flashing a custom rom would do it, but otherwise, alcatels or tmobiles website may have something on it, or google holds many solutions.

I've never done it, so I'm not sure
[Android General] kirito9:
I was gonna ask about that but I wasn't sure if you still had the C1 or not. These MT6572 devices has the fastboot mode but they don't use it :confused:. I don't know what Alcatel was doing. I have a Pop C2 and I also tried it, nothing works :D.
[Android General] kraolesage:
info

Since yesterday I search on google but that paid solutions lol but hey I will try a flash with a Original rom I downloaded. What tool to use for the flash apart from the root I have to do with kingroot
[Android General] CVAngelo:
I unlock phones for a living (at least it's one of the services I offer). You cannot SIM unlock a device by flashing a ROM! You need to use an unlock device called a "box". They are sold online typically for a couple hundred dollars. So you would not buy one just to unlock 1 phone. You'd only use a box for commercial purposes.

Otherwise, you can simply pay the operator or any of the numerous online unlock services for the unlock code.
[Android General] Charles IV:
I think I bricked mine (I was rooted, I forgot I hadn't unlocked the bootloader, because I couldn't, and so determined to upgrade to kk!) But I gave it to friend because he said he d could fix it, don't know what he did to it!

Anyway, my current phone doesn't have have a bootloader or recovery, apart from a screen giving you the option to factory reset, kingroot won't work on m, and I have sworn never too buy Alcatel or LG again! Only Nexus (or pixel if that lives up to the Nexus name!)
[Android General] kirito9:
TWRP 3.1.1-0 for Alcatel Pixi 4 (7) 3G- Update

This recovery was ported by [MENTION=8022358]ludia2210[/MENTION]. There was an MTP bug which was also fixed by him :D.

What's new in 3.1.1-0:

Backups will now include adopted storage keys (Dees_Troy)

Fixed an adb restore issue (bigbiff)

Fixed rebooting when no OS is present (Dees_Troy)

Fixed line wrapping in the GUI terminal (_that)

Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2

Download : Drive

If you need the download link mirrored be sure to ask.
[Android General] kirito9:
Ahh these devices don't die that easily. It was probably a softbrick and your friend probably knew what to do to recover it. Now there's a stable KK available for it, you probably tested the unstable KK from before? That LG Leon is getting to you isn't it :silly:, MSM8909 as well?
[Android General] Charles IV:
I'm really annoyed now you've said that ..., Whether her likes to admit or not, I know more than him on this level. If it was soft bricked, I wouldn't be able to recover it, as I can't unlock the bootloader, and wiping didn't help. Anyway, it doesn't matter now, he claims that he smashed it against a wall, and that I was with him.
[Android General] kirito9:
Hmm maybe it was hard bricked then? Still would be able to restore, even a corrupted eMMC (which prevents flashing) won't prevent this from dying.

He probably didn't have the patience to unbrick as it takes various methods if one doesn't work. Guess that's the end of that.
[Android General] Charles IV:
I was looking at the 4034-n-test repo which you committed to, and i noticed that all the fstab files, including the twrp one, were in the

/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/system

format, and i wondered if you hadn't changed them, or if it was just my device that needed the other format.
[Android General] kirito9:
That repo was to be deleted lol, I was trying to build on the CM14/LOS14 base to see if TWRP would still boot but I never finished compiling as I ran into some dependency issue. rock12345 forked it before I could delete it so it's still out there. Ignore that repo all together as it isn't tested. The format for the /dev/block/* which is mmcblk0p** still applies from before.
[Android General] Charles IV:
ok, thanks, i think I'll still use it as a base for los14 once I've got cm13 working

---------- Post added at 07:48 PM ---------- Previous post was at 07:40 PM ----------

what else do you think there is to do?
[Android General] kirito9:
Just checked another tree, don't think there's anything else.
[Android General] Charles IV:
can you check the recent commits i made about the mountpoint partition things, there are a few I'm not sure about, but do they look ok?

building again now
[Android General] mrblankslate1138:
[/COLOR]Hey, I've had some rooting experience and use of Linux; I'm trying to root my Alcatel PIXI-4_4TF / model-A466T / Hardware(MRA58K) /Android 6 Marshmallow, and I cannot figure out what one of those links up there to choose to root my phone with. I tried one and the TWRP flashed successfully via ADB, but now I cannot boot into any recovery at all, it just boots up normally, which hindered my flashing of the SuperSU. Any help would be appreciated.
[Android General] Charles IV:
Somebody else had problems booting into recovery with a different model, you might have to scroll back a few pages, but have you tried the suggestions there?
[Android General] Charles IV:
Success! ... Well not really. Sorry for getting you excited. [MENTION=5515628]kirito9[/MENTION] late last night I flashed the new build to my device, however things didn't seem right from the start. In the visible on screen log, I saw (if I can remember correctly)

detected filesystem ext4 for /dev/block/m(thingy)19
detected filesystem ext4 for /dev/block/m(thingy)19

Obviously the thingy bits it that system partition, I just can't remember it.

It stayed on this for a long time, and then I thing l think the flash completed, and after wiping cache and dalvik, installing twrp app, I rebooted. After a while the Alcatel boot screen came up. And it stayed on that. Cm boot animation never came up.

Another thing I've noticed, I'm on the latest twrp that you uploaded, but it takes ages to wipe cache etc. This maybe because I haven't yet successfully flashed an OS since upgrading twrp, but I don't know.

It's progress, but I think it's not flashing everything.