yashsingh1/xdaforums huggingface dataset:
[Android General] jie_gonza:
My device is Alcatel Pixi4 (5) 5045T. The Spft rom that i flash is 5045D. I have no backup on my 5045T. I can't flash spft rom its show me error "Sd_emmc" something like that i dont remember. So, im search on google to find the solution. I found 1, the solution is to untick the "Preloader" section. So, i flash the rom without "Preloader". Flash is succes but when im start my phone it stuck at "PIXI4" logo.

I am already trying Mobile Upgrade Tool by alcatel but mobile upgrade can't find my phone and show me error:crying:

I'm stuck at custom rom:crying:

---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------

My device is Alcatel Pixi4 (5) 5045T. The Spft rom that i flash is 5045D. I have no backup on my 5045T. I can't flash spft rom its show me error "Sd_emmc" something like that i dont remember. So, im search on google to find the solution. I found 1, the solution is to untick the "Preloader" section. So, i flash the rom without "Preloader". Flash is succes but when im start my phone it stuck at "PIXI4" logo.

I am already trying Mobile Upgrade Tool by alcatel but mobile upgrade can't find my phone and show me error:crying:

I'm stuck at custom rom:crying:

---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------

My device is Alcatel Pixi4 (5) 5045T. The Spft rom that i flash is 5045D. I have no backup on my 5045T. I can't flash spft rom its show me error "Sd_emmc" something like that i dont remember. So, im search on google to find the solution. I found 1, the solution is to untick the "Preloader" section. So, i flash the rom without "Preloader". Flash is succes but when im start my phone it stuck at "PIXI4" logo.

I am already trying Mobile Upgrade Tool by alcatel but mobile upgrade can't find my phone and show me error:crying:

I'm stuck at custom rom:crying:
[Android General] jie_gonza:
My device is Alcatel Pixi4 (5) 5045T. The Spft rom that i flash is 5045D. I have no backup on my 5045T. I can't flash spft rom its show me error "Sd_emmc" something like that i dont remember. So, im search on google to find the solution. I found 1, the solution is to untick the "Preloader" section. So, i flash the rom without "Preloader". Flash is succes but when im start my phone it stuck at "PIXI4" logo.

I am already trying Mobile Upgrade Tool by alcatel but mobile upgrade can't find my phone and show me error:crying:

I'm stuck at custom rom:crying:

---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------

My device is Alcatel Pixi4 (5) 5045T. The Spft rom that i flash is 5045D. I have no backup on my 5045T. I can't flash spft rom its show me error "Sd_emmc" something like that i dont remember. So, im search on google to find the solution. I found 1, the solution is to untick the "Preloader" section. So, i flash the rom without "Preloader". Flash is succes but when im start my phone it stuck at "PIXI4" logo.

I am already trying Mobile Upgrade Tool by alcatel but mobile upgrade can't find my phone and show me error:crying:

I'm stuck at custom rom:crying:
[Android General] Charles IV:
whoops! be careful about duplicate posts, but xda is constantly going offline for me right now :confused:

well as long as you're able to boot ...

i noticed mobile upgrade found my device, but said it was on the latest version, and refused to update it or anything.:(

my guess is, if you want to return to stock completely, you'll need to flash an old rom, older than what is officially supported by alcatel for your device.
[Android General] kirito9:
Try adding this line too

ro.multiuser.enable=1

I'm not sure if that's an actual line.
[Android General] kirito9:
Don't I always say make a backup before doing anything? :rolleyes:. TWRP backup is good yes but for these MTK devices, you need to make an SPFT backup as well because of how the Mobile Upgrade Tool works. As [MENTION=7211583]Charles IV[/MENTION] was saying, can you boot to stock recovery and wipe data/factory reset?
[Android General] kirito9:
Quoted the wrong person there :p. Multiple things going on here lol, sorry I forgot about the ROM. You do mean the removing the custpack partition right? Or the ROM you shared which you built.

It's possible to port 3.10.x kernel stock ROMs like what the Pixi 4-4" and 5" has but I haven't got the time to be doing trial and error as I don't have the Pixi 4 6" :'). I can probably look for a guide for you.
[Android General] Charles IV:
Didn't work. :(

I think I've found out what's causing the Bluetooth problem: I deleted audiofx in terminal, and when I clicked on the icon, I got u the same error messages as the Bluetooth one, except the name of the app was changed!

Should probably put this on the other thread, but I just need to find the Bluetooth share app.

Strange thing, after rebooting, Audiofx if back!
[Android General] kirito9:
Taking logs would help figuring out the problem. Catlog or adb logcat on the PC would work.
[Android General] Keiko87:
Currently me using the custpack.img from an modded 8050E which is just about 500mb small instead of over 1gb, than i added lines to the prop to block some jrd.com apps like the facebook_installer and facebook_appmanager which are (100% fake apps) from TCL to keep all permissions & owenership.

Some standard chechjni things and uninstalling of these apps and disabled omacp support, trusted face and findmyphone.

Theaaan deleted in custpack folder all removable apps and some dirty unremovable apps = 300+ mb more space)

Removing all permissions from the TCL_chinese-bastards-virus_infected startup launcher and installed Evie Launcher.

THAAAAAAAAAAAAAAAAAn i did readback my rom with SPFT and done some weird things with pencils in my nose :eek:

But thats just an confusing horrible temporary Soloution, better me sell that SATAN Phone and buy some nice Gameboys :3

---------- Post added at 01:53 ---------- Previous post was at 01:47 ----------

Me uploaded here on xda all Pixi standard apps, happy searching <3
[Android General] jie_gonza:
Yup, i can boot to stock recovery.
[Android General] Charles IV:
I've uploaded a logcat on the cm for mtk thread, but what do you want a logcat of?

---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------

where abouts did you upload them?
[Android General] dashu42332:
Alcatel Pixi 4 (7) 8063

Hi Guys,

I am having Alcatel Pixi 4 (7) WIFI model 8063 chipset MediaTek MT8127. I have the stock backup of ROM. I have try to port recovery CTR 5.7-8050.img. But failed, tab will boot to the recovery and don’t mount. I have limited knowledge about the recovery. I would did help to build recovery for 8063.
[Android General] kirito9:
Boot to it and wipe data/factory reset. Try to reboot again after that.

Also if you're ever going to flash again, do not flash the preloader... Or fornat your device.
[Android General] kirito9:
Not anything specific, just the entire log. As in from device boot up to trying to enable Bluetooth to see what is causing the error.
[Android General] kirito9:
Thanks, was asking for this a while ago. You probably just need to edit the mount points found in etc/recovery.fstab and also ctr.fstab.

If you ported and it boots then I'll make a separate built for the 8063.
[Android General] Charles IV:
well the log on the cm for mtk should suit you ...
[Android General] kirito9:
I'll check it out.
[Android General] dashu42332:
Here you can find my port and snap of recovery give error.
[Android General] Keiko87:
Link is for 8050xxx Pixi 4_4 > 4_6
[Android General] kirito9:
Try this to take the logcat.

adb logcat -v long > name_of_problem.txt

The bug report is a ... bit much. I can't follow anything there.
[Android General] kirito9:
Try the attached zip. Btw it's not flashable.
[Android General] kirito9:
Factory reset? Also next time, use

This :')

for long pieces of information.
[Android General] Charles IV:
yes, thats what i thought when i attempted to have a look at it!

I'm not sure how much of that was code, and how much was pseudo!

So I'll try

adb logcat -v long > bluetoothcrash.txt

???

edit

um, how long is this meant to go on for, it's been going for ages

another edit

i ctrl c'd it, and think i just crashed gist by trying to copy and paste it, but i will zip it up and upload it

more edits

ok, uploaded, beware it is long (because i thought it stopped itself), so ill do another one and stop it after a few seconds of the error message popping up

yet more editing

in the shorter one, i did ~3 seconds normal and the rest (~7 seconds) of the crashes

even more editing

ok, it seems it logs it from, if anything, when i flashed it / wiped data, so it's the last ~10 seconds (line 36858) that i deliberately logged

and it looks like i turned bluetooth on at about 20:20:14
[Android General] dashu42332:
CTR_recovery_20170601-1408.img.zip Still same error " E:can't mount /cache/recovery/command "

Anyway try many port myself and attached is working. But it took huge amount of time to backup(in recovery) and also around 7gb of space in sd card.

Still its not perfect. Recovery don't mount internal sd ,but external sdcard works fine. now it mounts internalsd also.need to restart in recovery to reboot recovery(in carliv menu->reboot recovery)

Then also i have try to flashing SR1-SuperSU-v2.78-SR1-20160915123031.zip eveything goes without error .but cannot get root.

appreciate your assistance
[Android General] Keiko87:
factory reset ??

me modded hours custpack files, i gonna loose everything with factory reset :crying:

thats an answer/advice that would end in an bootloop you know that :o
[Android General] kirito9:
The short one was fine. Here's what I got from the log

[ 06-01 20:20:14.622 29752:29766 E/bt_osi_config ]
config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory

[ 06-01 20:20:14.758 29752:29766 E/bt_vendor ]
vendor_open unable to open libbt-vendor.so: dlopen failed: library "libbt-vendor.so" not found

[ 06-01 20:20:14.770 28368:29050 E/NearbyDirect ]
BackgroundBleScanner: Unexpected action=android.bluetooth.adapter.action.BLE_STATE_CHANGED

[ 06-01 20:20:14.774 28368:29050 I/NearbyDirect ]
MagicPairScanner: BluetoothLeScanner is null, Bluetooth might be off. Enabled=false

Give your friend google a shout and see what he can find ;).
[Android General] kirito9:
I'll just make TWRP for you and make things simpler.
[Android General] kirito9:
Hmm, I heard about that problem before but never found a fix, I thought factory reset would help :p. I'll check again to see if I find anything.
[Android General] Keiko87:
my 8050 is an SPFT Rom -.-

About my "optimizing apps on reboot" issue

just try to have time to simply look on my extracted rom files (read back with My PhoneExplorer)

Some files are missing due to missing ownership hwm whatever...i hope you or anyone finally can help me,

after i did read the conversation between you and charles, it should be a problem for an Pro like you :3

Extracted Pixi4 (6) 3G 8050D
[Android General] kirito9:
Edit made :'). I'll take a look.
[Android General] kirito9:
I just figured out that I can flash TWRP without unlocking the bootloader ;) how nice Alcatel. Thanks for that. I guess you only need to enable OEM unlocking and USB debugging.

NOTE: Only tested on the Pixi 4-4" (MT6580).

Update- June 8th 2016: This method does not work on the Pixi 4-4" (4034X). But it works on the 4034G.

Can anyone else verify this? [MENTION=5691078]ZonaRMR[/MENTION] [MENTION=8142454]Keiko87[/MENTION] [MENTION=4393511]matt4321[/MENTION] [MENTION=7211583]Charles IV[/MENTION]

What I did was fastboot boot twrp (see example below) then I flashed twrp-3.1.0-0-4034.img from TWRP after copying it to the internal storage.

Example:

fastboot boot twrp-3.1.0-0-4034.img

Then rooted with Magisk :D

Steps (copied from here):

(Recommended) Restore your boot image back to stock (flash uninstaller if Magisk is previously installed)

Download the latest Magisk zip file

Reboot to a custom recovery

If you choose to use SuperSU (only support Android 6.0+), flash SuperSU in systemless mode now

Flash Magisk zip

Reboot. Update the stub Magisk Manager to the latest from Play Store APKMirror

Be sure to check out the Magisk forum and hit thanks button for [MENTION=4470081]topjohnwu[/MENTION] ;).
[Android General] drmad:
Hello!

We can do it for the Qualcomm variant (es 9001d) ?
[Android General] kirito9:
I'm not sure, I only tested with MT6580 but I know of another Qualcomm device that Alcatel has that can get it done without unlocking.

The key thing here is having access to fastboot mode and AFAIK, these MSM8909 Alcatel devices have been denied access to it.
[Android General] Charles IV:
Hmm, interesting.

First things, I need to do stuff, so tell me off if I make another post after this!

Second, I think I'll need to read over the steps you took again, because some of it goes against all the 'rules' I had taught myself.

Finally - I remember on my pop c1, I flagged Cwm recovery. This was JB, do no oem option in settings. I had rooted with framaroot, and I couldn't unlock the bootloader, yet I still did it! (Honestly it was so long ago, I can't remember that well)
[Android General] vetooo3001:
plz any news about root acatel 9001D
[Android General] Keiko87:
ee you flashed Twrp only with OEM unlocked via ADB ?

did you done that when phone was on or off ?

normally me root with kingoroot and supersume, which wowrked always just for 1 week after that got problems.

I try the magisk Way, it sounds really like " chains get broken" if it works. thx for that :eek:

Sunday i try that, today, i wanna go swimming, clean my brains dalvik cache ^_O

*pinned to my browser bookmark bar*

EDIT: LoL Kirito just tested the thing above your question to us, replaced the recovery.img from your 8050G SPFT with my 8050D (which runs TWRP) now i have trwrp on my 4 (6) 3G) xD
[Android General] kirito9:
If that's the case then those users of the 4034N won't have to unlock their bootloaders and end up with the brick.
[Android General] kirito9:
The phone was in fastboot mode... to boot the recovery using fastboot boot <recovery.img> then flashing the same recovery permanently.
[Android General] Charles IV:
well, i decided to give flashing twrp a go, with bootloader locked, however i can't reboot into the stock rom!, and i cant flash it with fastboot, or adb sideload!

looks like im going to have to oem unlock and not try it out ...

but i dont want to give up yet ...
[Android General] kirito9:
What does this output?

fastboot getvar all
[Android General] kirito9:
Format the system and data in TWRP. Reboot the recovery then try to flash again, making wipes in the process.
[Android General] kirito9:
What about mobile upgrade or the SPFT backup?
[Android General] Charles IV:
ehe, ehe, ehe

well, i should have made a backup myself, but i got this phone for free, so i live life on the edge, plus there's no time, internal storage's too small, etc.

will try them

also, is there a way to get mobile upgrade tool on linux, it's a pain getting my windows laptop out, and my virtualbox doesn't like usb 3.0 ports, which is all ive got on this pc.
[Android General] kirito9:
SPFT backup doesn't use the internal of the phone to store the ROM_0 file. I lived on the edge as well until I almost couldn't revive my phone :silly:.

Maybe you can try wine

sudo apt-get update

sudo apt-get install wine
[Android General] Charles IV:
wine didn't work, when i tried it before (does it work for anything ???)

Mobile upgrade tool, before, said that i was already on the latest version, and wouldn't do anything, but it may work when there is no os ...

with the spft, can it be flashed in recovery, or do you extract and use fashboot flashall
[Android General] kirito9:
Wine was used on older MTK kernels (<3.4.67).

There are several options you can use. I have a backup of 4034 in TWRP. I can upload that for you or you can get any system.img of 4034X and flash it with either TWRP or fastboot.

SPFT is a tool that flashed the partitions usually in .img format to the device.
[Android General] Charles IV:
can you upload the twrp backup??? thanks

system.img's are generated with my build's i'll try one of those, but what exactly will it do? will i have to flash the rom afterwards, or will it magically start booting?

edit- actually, the img is 700MB, i assume that it may boot now?
[Android General] kirito9:
From the logs, the system is having problems extracting so I figured flashing the system.img would bypass that error. You only need the system.img and boot.img to be flashed for CM13 right? After flashing those, reboot in twrp and wipe data/factory reset and try to boot.
[Android General] kirito9:
The boot.img won't be enough. Change the file system for system to ext2 then change it back to ext4, format, reboot recovery and try to flash again. If that fails then you will have to use SPFT. SPFT is available for linux.
[Android General] Charles IV:
guess what i just did before i saw that ... exactly what you said to do ...

i guess im going to have to try spft ...
[Android General] kirito9:
Clearing cache seems to fix this issue you're having.

What about your extracted files? I've extracted the ROM but what am I supposed to be looking at/for?
[Android General] kirito9:
Only flash the system.img, you can find a backup of the 4034 SPFT ROM in the ROM section.
[Android General] kirito9:
I need your dumchar_info to complete the build or install the diskinfo app from the playstore and send the partitions to me. You'd have to enable the options in the settings to display the mount number.
[Android General] Keiko87:
[/COLOR]

ah no clearing cache not work.

well my issue is that i failed to remove the bloatware ,stop the system to optimize / upgrading apps on every reboot & moving data to 2nd SD.

My build.prop is very much filled with lines i think i dont really need. like ( shared_sdcard=1 & 2sdcard_swap=1, and many ssv & omacp lines also "md_perm_checked=to_upgrade" )

With my build.prop like it is, i am unable to move/link big app data to 2nd Parittion of my SD Card , tried App2SD b4...

Also i dont understand why the real build.prop is inside the custpack folder (img) and just linked to /system/ . :(

My wish->

i want debloat my device and in any way move/link big data from apps to my 2nd parition without having trouble. & an Art Award for typing so beauty :D

I thought you could modify some files in etc or xbin or look inside framework-res or hmm ..

Why You ask me ? you are the Virus :p I'm just an WinXP trojaner y_Y

to xda mod: ,, no im not pretending to be female im just using the xda /account~email from my VFX Team Mate <3 Takako-Daishiro Arts (Youtube)
[Android General] kirito9:
So basically you want to remove the custpack partition and increase data partition size?

The real build.prop is in the /custpack partition because this is a custom partition created by Alcatel for their devices. There are ways to remove it and merge the custpack into the system but I haven't quite figured it out as yet.

I'll try from scratch with an unmodified 8050 ROM.
[Android General] Charles IV:
ok, spft is playing up, mobile upgrade tool is saying that im on the latest version (of course no Rom = android 6.0), im honestly not having fun anymore.

i think ill try the twrp backup (can you upload it), and then i'll give up for a while, have a look at things fresh, and solve it :)
[Android General] dashu42332:
please find the partitions of 8063 from diskinfo app.
[Android General] kirito9:
Try this https://www.androidfilehost.com/?fid=745425885120737052
[Android General] kirito9:
I'll begin uploading now. What do you mean playing up?
[Android General] Keiko87:
nah it is ok to delete the cuitspack apps which are useless and stop system re-installing them by "optimizing apps 0 from 204" at booting to system.

yah and to move big data from apps to sdcard. which is problem whenu see my build.prop.

keep an eye on facebook_app_manager, facebook_app_installer & jrd.setupwizard2 in custpack folder and in system apps.

These both make problems

i beg u, i know you have alot to do with charles and others people, but i hope so long time that u concentrate on my issue.

Just debloate in any any way and an simple way to link/move data to SD

:silly::victory::eek::cool::rolleyes::fingers-crossed::highfive::(:D;):cowboy:
[Android General] kirito9:
I'll see what I can do ;).
[Android General] Charles IV:
I'm feeling guilty now xd

where did you upload the twrp backup?

by playing up, i mean it wasn't working. for one, i wasn't entirely sure how to use it (i assume download also flashes to the phone???)

but don't worry, I'll have a proper look at the errors when i come round to looking at it again. But i should take a break.

I am generally driven by this strange force of motivation, and i want to do everything as quickly as possible, but a (hopefully temporarily) broken phone should stop me, or slow me down. I'm doing DofE at the weekend, that should clear my mind (wipe the dalvik cache :silly: ) and i can focus on the real world :victory:

The worry is, my motivation will drive me to fix my phone, so if the twrp backup doesn't work, my motivation might give up
[Android General] dashu42332:
thank you twrp recovery. i have try it,when flashing the recovery using spf tool gives on error without poping up "ok".

Tab boots to twrp recovery ,but cannot be access has tab don't respond to any touch input and key input. i think the recovery size is tab is small and current build of twrp around 10 mb.

As per my previous try flashing, any recovery which is more than 8mb the Spf tool would give same error without pop-up "ok"
[Android General] Keiko87:
Japan needs You !!

​
[Android General] kirito9:
Here's the backup.
[Android General] kirito9:
The max recovery size you can use is 16MB, if twrp is 10MB then it shouldn't be a problem. If touch doesn't work then it could be that your kernel is the problem.....but that shouldn't be the case. I'll build CTR instead.
[Android General] kirito9:
Try this CTR- https://www.androidfilehost.com/?fid=889764386195904689
[Android General] mashroomz99:
No Reception And Not Detected Sim Cards

Guys...Do U Have Any Problem After Flash All These ROM?:(Because Mine Cant Detect Any Sim At All.ROM Works Perfectly:D. Any Solutions?
[Android General] Ruffypp:
will this work on alcatel ot pixi 4 5 4g android 6.0 (5045T),because attachment above for 5045D or X
[Android General] dashu42332:
This recovery works fine. I have tested by backup and restore no problem. But same as pervious recovery this also give error while installing spft. And in the recovery it work with key input only and I think resolution of the recovery is out.

I also try flash SR1-SuperSU-v2.78-SR1-20160915123031.zip but gives error “boot image not found”

Is the boot.img should be edit to get root in marshmallow?

Thank you recovery and time.
[Android General] kirito9:
Yes it will but make a backup before you flash. Please make the backup :(.
[Android General] kirito9:
Do you have fastboot mode? Since you're always getting an error with SPFT and I can't figure out the reason why you're getting the error. You can use fastboot to flash the recovery instead. Or use the existing recovery to flash. There should be an option under advanced to flash images.

Yes I'm now realizing the recovery uses a smaller resolution since it doesn't want to go much out of the phablet range. Is it 600 x 1024 or 1280 x 720. I'm getting those resolutions from different sites.
[Android General] kirito9:
I can build a recovery for you to test but I'm not sure how you would flash it.
[Android General] vetooo3001:
OK please let me try
[Android General] kirito9:
Read below.