yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Yeah guess it out there

Yeah guess you're right.

I just hope they don't patch it up.

Big thanks on your work there by the way ?

And I'll kill the link to my copy.

Everyone can just get it at the thread u mentioned.

By the way. Any idea where to find the kernel source for

These devices? I am trying to get adb and mtp working in twrp
[Android Q&A, Help & Troubleshooting] diplomatic:
[MENTION=9688970]LgPWN'd[/MENTION], great... appreciate it.

I don't think Alcatel has many kernel sources available. If you haven't found them, I wouldn't either. It sounds like adb and mtp should work with the precompiled kernel if you set up your device tree right...

EDIT: Here are some kernel and other sources for the Alcatel 1x: https://github.com/5059d/kernel_5059d_mt6739_tcl
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Ok thanks I'll have to look a little deeper I guess.

Have been using the prebuilt extracted from. Stock

But for whatever reason mtp and adb are broken.

I'll figure it out eventually ?
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Looks like essentially the same hardware.

Only they used Android GO on that one?

I abhor Android GO.

But perhaps with a few changes I can use it for the kernel .

Thanks ?
[Android Q&A, Help & Troubleshooting] LgPWN'd:
So I was thinking about trying to add support for 64bit roms to our device....

My line of thought is that if we can locate a device with same chipset , and a 64bit stock firmware...

I can maybe use the stuff from it's /vendor /lib64 folder to help add support for 64bit A_Only gsi's

on the tetra....

But trying to track down suitable doner-device and firmware is giving me a headache...

So if anyone's interested in that name your suggestions here...

Thanks
[Android Q&A, Help & Troubleshooting] clcombs262:
Talk to [MENTION=4979138]realjo[/MENTION]hngalt on telegram. He's doing a 64 bit bringup for the Moto g6, has 64 bit CPU with 32 bit userspace

Mind you, Motorola publishes kernel source
[Android Q&A, Help & Troubleshooting] LgPWN'd:
well I cloned the repo at https://github.com/5059d/kernel_5059d_mt6739_tcl

and using the prebuilt kernel for that twrp tree in my twrp tree... everything booted fine...

no meltdowns, BUT mtp and adb are still not working...

wtf can't figure this out...

I want adb and mtp in twrp dammit

---------- Post added at 09:27 PM ---------- Previous post was at 09:06 PM ----------

also I'd bet anything made for the alcatel 1x or the alcatel 5059r onetouch idealXTRA will likely work for tetra...
[Android Q&A, Help & Troubleshooting] clcombs262:
Hey did you disappear on us?
[Android Q&A, Help & Troubleshooting] :
nce work guys, getting more going with this phone I see. Nice to be able to flash stuff without Sugar. I was in contact with Diplomatic back in march and april testing his xploit on our device, so I'm famiiliar with it. I'm glad to see he got it working for our device now.
[Android Q&A, Help & Troubleshooting] diplomatic:
[MENTION=5437200]PizzaG[/MENTION], yes, and it could have been done a lot sooner had you gotten back to me ;)
[Android Q&A, Help & Troubleshooting] LgPWN'd:
He's a Champ ?

I'm currently working on a custom kernel that should

Work across several of these mt6739 Alcatel devices

Hope it works out ?
[Android Q&A, Help & Troubleshooting] cthulu_rises:
Hell yeah I did haha been away from internet access for months just got back to civilization. Don't have this phone anymore but willing to help if I can lol
[Android Q&A, Help & Troubleshooting] clcombs262:
I still own it but not my primary device anymore so it's expendable ;)
[Android Q&A, Help & Troubleshooting] LgPWN'd:
There's a button for that ! ^^^^^^^

????????

Well I feel like screaming at Linux again !¿!

I can get the kernel to compile once if I only change

Small things in menuconfig.... But if I try to then make another change I have to scrap everything start over...make fails

for a lot of options / features I want to enable,

Unless I set it up to be a loadable module it causes

Make to fail.

Think I gotta grab more sources, maybe cherrypick some other commits , I want to include drivers for using externalUSB wireless adapters like ralink and atheros. Trying to get the usbgadget features tweaked.

Changed the governor to performance.

Added kexec support and wireless-frame-injection patch .

But progress is painfully slow as I'm having to hand edit and modify makefiles and defconfig.

And kinda just trail / error everything since I'm modifying source from a different device to work on ours...

I took the generic defconfig from /arm64 and the defconfig from this arm kernel.source and merged the two using the commandline ( diff ) and then hand edit that for removing the notations from the diff output ( +/- ) to get it in the correct format.

This is turning into quite a learning experience though ?

I still don't have a 64bit kernel that boots ... ☹️

However I did make a 32bit arm kernel that boots.

But I'm not releasing it yet as it's unstable.

And not what I'm trying to build.

I will be building 2 kernels to start.

An arm kernel with extra features (because we can do that)

And an experimental kernel that Im mostly crafting from bits and pieces of other source in an attempt to allow our hardware to support an arm64 GSI....

Afterall we do have a 64bit mt6739 processor.

But I fear the 64bit thing will be a while before it works as we will also need to modify our vendor.img

The one we have doesn't contain the library and shared object files needed for arch/arm64....

As I get these things to work I'll share my releases here along with link to my source on GitHub and continue on to work on the device tree to build a full rom.

But it's all about the kernel....

And that kernel is being a tough one

Since the source base is from Tcl/Alcatel

And oem's seem to almost purposely mess up the file structure and move things around...

Or even hard code commands In Makefile that use the actual path of the source on the developers machine in China or wherever....

I know I'm making progress but it's eating away so much of my time..

And I will not be able to build a complete rom

Until I can buy a decent PC to compile on.

I had to pull 2 of my 2gb ram sticks out this morning...

I guess maybe all this burnt them out.

So down to 4gb ram.

Anyhow. I may let this project sleep for a few days.

I need a break from the screen....

And a double cheeseburger.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
I couldn't leave it alone...

Back at it.

Day 4
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Down the rabbit hole

Wow I'm kinda in over my head.

It's so different from the things I'm used to compileing

And all of these options to enable or disable....

And then soon as I change any options from stock ...

It refuses to make....

Missing dependincys and such...

Streight up pain in my ass.

I've contacted tcl Alcatel and the mother company too

And gotten no where asking for kernel source....

I'm even threatening to take it up In the special court of HongKong if they insist on violation of GPL...

But in the meantime I am trying to make it work with the few source repos I can find for mt6739

If anyone has expertise with kernel building from scratch...

That's whom I need to speak with.

Oh Gawd!!!
[Android Q&A, Help & Troubleshooting] clcombs262:
Our new telegram group is https://t.me/Alcatel_5041c

Come join us!
[Android Q&A, Help & Troubleshooting] LgPWN'd:
UPDATE For Recovery

So today I'll point you to the final release candidates for two better recoveries.

In these you will have adb working out of box in root mode

and they have been built to allow flashing of treble GSI system images.

They both have been tested and reported that all is working correctly.

I also allowed for flashing vendor.img

and lk.img so that it's easier to replace those between different versions.

Pitch Black Recovery

https://xdaforums.com/android/development/unoficial-pitchblack-recovery-alcatel-t3946122

Red-Wolf Recovery

https://xdaforums.com/android/development/red-wolfrecovery-alcatel-tetra-5041c-t3946121

I hope everyone enjoys the new recoveries and it should make switching between GSI flavors much easier.

Cheers!!
[Android Q&A, Help & Troubleshooting] Spades99:
So it took reading through to page 20 to realize I needed the fastboot fix for the latest version. It worked. Was able to unlock the bootloader. However when I flash any recovery via fastboot it never seems to stick. Phone constantly reminds me loader is unlocked but it goes to stocks recovery.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Sorry for late reply

Yeah after fastboot fix you should use any one of the recoverys and restore the vendor from [MENTION=5437200]PizzaG[/MENTION] cricket ROM tut.

Then format data

Then flash a gsi
[Android Q&A, Help & Troubleshooting] Spades99:
Okay I got back to recovery backed up. Restored vendor from pizzas twrp backup. Converted data partition to f2s2 or whatever. Wiped data/user wipe. Installed a gsi (latest RR) and got bootloop. Still had TWRP so was able to restore my backup. Sadly I bought this phone and popped out my sim to make it nano and now have to use it as a daily driver until I can get my sim into something else. I work too much so I'm doing this when I can and always have to start from scratch lol.
[Android Q&A, Help & Troubleshooting] Spades99:
So I couldn't help but tinker a bit.. ended up with the "decryption successful but data corrupt" recovery bootloop... Fixed that by flashing the stock recovery. "Erasing" showed up for 2 seconds and it worked again.

Still can't get GSI's to work, so I dove into getting rid of tethering provisions on rooted stock. If anyone is interested in getting WiFi tethering without 3rd party apps or apns on stock; it's actually a series of old tricks.

Edit your build.prop and add:

net.tethering.noprovisioning=true

Then get into a su terminal app and enter :

settings put global tether_dun_required 0

(Really just in case. I noticed dun was enable in a device management app)

Then delete (or .Bak) the 2 system/app folders with "entitlement" in their name. Forgot specific names because they're long gone. Reboot.

Stock WiFi tethering will no longer kick you off :)
[Android Q&A, Help & Troubleshooting] Spades99:
I have a new phone on the way so I'm going to really start tinkering with this one when it arrives. What ROMs if any are people using on this phone?
[Android Q&A, Help & Troubleshooting] vova2903:
help unlock this device from cricket
[Android Q&A, Help & Troubleshooting] vova2903:
???????no one has any thoughts?:confused::confused::confused::confused:
[Android Q&A, Help & Troubleshooting] tailstwilight:
Where is the Network Unlock ZIP that LgPWN'd was talking about?

Some of us need that ZIP because we can't afford $40 to get an unlock code!
[Android Q&A, Help & Troubleshooting] niishou:
I encountered some troubles following the guide that may help others:

- As stated before, you have to rename "U8M8Y0Y0CT00.mbn" to the current date (by today, it is U8MAB0B0CT00.mbn).

- The right syntax for TWRP to see the backup is "sd:/TWRP/BACKUPS/Your-Device-ID/DATE" (date format is YYYY-MM-DD--HH-MM-SS_Android_O). You may find your ID before doing anything because it's the one showed when you type "adb devices" or "fastboot devices".

- You may find yourself with TWRP asking for a password, to avoid that you should perform a "fastboot format userdata" before rebooting into recovery.

Now I'm running ~CricketROM~ just fine. Sadly stuck with the Network Lock but everything else is running.
[Android Q&A, Help & Troubleshooting] tailstwilight:
I want to use this phone on SoftBank. I need the Network Unlock ZIP as soon as possible. How does the ZIP work, if someone can tell me what bits I need to flip I can unlock my phone and my exchange student friend's phone.

My main is an LG G2 VS980 running AOSP Extended based on Android 8.1
[Android Q&A, Help & Troubleshooting] vova2903:
Do you guys have any thoughts on getting around the operator lock? in the data user 0 file there is info about locking. maybe something needs to be changed there?
[Android Q&A, Help & Troubleshooting] yah2000:
update

I screwed up and installed a tweak from Magisk that shouldn't have and now i can't get past twrp. if anyone has a system.img for this phone that i could reflash , that would be great.
[Android Q&A, Help & Troubleshooting] TeamLeader000:
Bluetooth problems

After getting ~Cricket Rom running almost everything has been working great except for Bluetooth functionality. When using Bluetooth on my car stereo I would receive a bunch of "Bluetooth has stopped" notifications when it tried to move to the next song. This would completely crash anything that was running and freeze up my phone for a couple minutes. After fiddling with different Bluetooth apps to try and fix the problem Bluetooth won't even turn on anymore... Any suggestions would be super helpful since I don't really know what to try next!

Thanks again for the wonderful root instructions, since this is my first rooted phone it took me awhile but the steps were sublime. :D
[Android Q&A, Help & Troubleshooting] Spades99:
Try reflashing the stock recovery.img via fastboot

It's located in the cricket rom zip.
[Android Q&A, Help & Troubleshooting] yah2000:
Thanks

Aight I will try that.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Hey everyone that's asking about network unlocking the tetra,

You will likely never get that from me here, i think it violates forum rules.

feel free to ask about it in my telegram group for alcatel devices....

find new releases of recoveries, info on what we are trying to do to dualboot it, device help/support

and root related questions/answers at my alcatel devices support group

https://t.me/Alcatel_devices_LgPWNd
[Android Q&A, Help & Troubleshooting] niishou:
Hi, got two things to ask. Hoping you can help me.

1.- Has anyone got SP Flash Tool to work? I know it's not a really device-related thing but whatever. I'm using the latest version of SPFT (5.1916) an VCOM USB drivers are installed correctly (phone gets detected as MTK USB Port). The problem is that I get ERROR: STATUS_BROM_CMD_FAIL (0xC0060005) and a blank HINT.

There's not much about the issue online. What I found is that it's related to phone starting too soon and that I need to use another DA file but I tried using MTK_AllInOne_DA and the specific DA file for this phone and it shows the same error with both files. Other possible solution I found is using another SPFL version, tried that too (a lot of them) and it's always the same error.

2.- For those using GSI LOS16 as daily driver, how did you get GApps to work? I tried Open GApps and I did everything Google asks to certify it but it just doesn't work. I tried to use microG too but it gets stuck on the "Just a sec..." screen forever. I've read on the GSI ROM thread to use Magic Gapps from Magisk, has anyone tried that?

Best regards.
[Android Q&A, Help & Troubleshooting] OMGdaCRIT:
MOD EDIT. THIS WILL NOT BE TOLERATED ON XDA.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
MOD EDIT. WE DO NOT RESPOND THIS WAY BECAUSE REMEMBER. YOU CAN GET IN TROUBLE FOR THE RESPONSE AS WELL.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Great Job

I guess I could tone down my response a bit...

But it amazes me that my response gets edit/cut out

And the post before that was flaming/disrespectful

To me gets left there as though not a thing is wrong with it?

Edit

Oh ok there we go ..

MOD EDIT- It takes a moment. We do the best we can. Thank you for your understanding

---------- Post added at 10:07 PM ---------- Previous post was at 09:59 PM ----------

Honestly....

I move that we close the thread here.

The whole point of this was gaining root which we have way more than done.

There will be nothing more to see here.

I'm not releasing anything more in this thread,

And when I do release something new for this device it will have its own thread. [MENTION=9506190]clcombs262[/MENTION] is no longer using the device. [MENTION=5437200]PizzaG[/MENTION] and myself will release what we release in a new thread for it.

In reality this threads kinda outdated and stale at the moment.

And there are even device support groups for this device now....

[MENTION=4392154]apophis9283[/MENTION]

Can we please just close this thread now?

If anything new happens for the 5041C I'll personally create a thread for the new thing at that time.
[Android Q&A, Help & Troubleshooting] nicksalad:
Keep in mind if you have a network unlocked phone (not factory unlocked) and you use Sugar, it will automatically be network locked again. I followed PizzaG's guide and that was the result.

Unlocking the bootloader and flashing Magisk on the other hand works well in most cases. Use Sugar at your own risk.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Sugar mtk for unbrick only

Someone should say that sugar mtk is not needed for this any longer.

U need fastboot fix then use the same steps as any device for unlock bootloader and flash ROMs and recovery

---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------

@Moderator Committee

Can some one please close this thread?
[Android Q&A, Help & Troubleshooting] mark manning:
Sorry but I don’t see a reason to close the thread.
[Android Q&A, Help & Troubleshooting] LgPWN'd:
Sure thing

A reason to close the thread?

How about this.

#1 We got root the threads been completed.

#2 this thread has out dated information at this time.

#3 The OP has moved to a new device and has abandoned this thread.

#4 the old technique using Sugar MTK included with

My associate [MENTION=5437200]PizzaG[/MENTION] 's tutorial is causing people to loose network unlock status of the devices that are unlocked.

#5 if I start the New AIO thread for this device with correct instructions and links to our latest updates of our files ( twrp, pbrp, redwolf, fastboot-fix.zip , magisk-gsi-helper.zip) etc...

My new thread will be marked as a Duplicate to this one...

Now I may be just a (senior member) here but I am the one who helped bust this device open.

I developed the recoveries.

I developed the modz for it.

I'm working on dual boot for it with [MENTION=5437200]PizzaG[/MENTION].
[MENTION=9506190]clcombs262[/MENTION] is the OP and I worked with him outside of xda as I do with [MENTION=5437200]PizzaG[/MENTION] now.
[MENTION=9506190]clcombs262[/MENTION] has moved to a new better device and is no longer participating in development for this device nor in the discussion on this thread.

Users have been complaining to me that they follow the tut by pizzaG and the device gets locked to at&t by sugar MTK. I can Confirm the fact.

And if u really just NEED an excuse to close the thread and edit something, how bout XDA's policy on wares?

PizzaG's tut promotes the use of and distributes (wares) sugarMTK some shady factory tool that TELLS YOU it's sending data about you and your system and your actions to some server in Korea....

And then "fixes" your phone by flashing latest AT&T firmware and locking you to at&t even tho T-Mobile worked fine 30 minutes ago....

So there's more than 5 good reasons to close the thread and remove the links from the pizzaG tut comments.

Now as far as sugarMTK, it is a good tool to have to recover a bricked Tetra and many more models too, but it's not needed to root the Alcatel tetra any longer.

I hope someone in charge sees this and does something about it before it causes 1 more person to (flash) a tetra and lock it back to at&t which doesn't even exist in some places that these users are reporting in from....
[MENTION=3512220]Moderator Committee[/MENTION]
[MENTION=1205214]SacredDeviL666[/MENTION]
[MENTION=4392154]apophis9283[/MENTION]
[Android Q&A, Help & Troubleshooting] mark manning:
You can think whatever you want, the thread isn’t being closed. Other people can and will find it helpful in the future. XDA is a database of information and just because you no longer see a need for a thread doesn’t mean others won’t. We have threads for 10 year old phones that still get posts helping people out.

Please keep to the thread topic.
[Android Q&A, Help & Troubleshooting] Neo:
[MENTION=9688970]LgPWN'd[/MENTION], if you feel the thread needs to be closed, you can send a respectful PM to the OP asking for it to be closed and stating your reason why. If they do not respond or refuse, there is nothing more you can do about it.
[Android Q&A, Help & Troubleshooting] clcombs262:
Well it's a good thing the OP is about to request it be closed
[Android Q&A, Help & Troubleshooting] cthulu_rises:
Root successfully achieved with the magisk patched boot image. Flashed with fastboot/pc
[Android Q&A, Help & Troubleshooting] clcombs262:
Okay. For the TWRP, we're on our own. TWRP has no official support, and TWRP builder has "too many devices in queue"

Haven't tested the root yet, but hopefully will soon.
[Android Q&A, Help & Troubleshooting] ChocolateCowMoo:
Hey guys I did this magisk boot img flash and now I can only get to recovery mode, stuck on secure boot failure. Any help? Nothing seems to take me back to fastboot.
[Android Q&A, Help & Troubleshooting] guyincog:
I've no particular help here, but if you can get to boot you can probably just "fastboot oem unlock" (and follow the prompts on the phone screen). Before this you may need to turn on "OEM unlocking" in the developer options screen. While I've done nothing interesting with mine, I did unlock it. After unlocking the following text appears at boot:

"Orange State

Your device has been unlocked and can't be trusted

Your device will boot in 5 seconds"
[Android Q&A, Help & Troubleshooting] clcombs262:
Did you ensure that bootloader was unlocked?

Also, in an earlier post, the ROM was linked to. Use it if necessary to re flash
[Android Q&A, Help & Troubleshooting] clcombs262:
How did you flash it? I cant get into fastboot
[Android Q&A, Help & Troubleshooting] clcombs262:
How did you get into fastboot? I've tried power+volume up, power+volume down, and adb reboot bootloader
[Android Q&A, Help & Troubleshooting] ChocolateCowMoo:
Yeah unlocking bootloader is where I went wrong... Been a while so I wasn't thinking. But I got to fastboot with adb. I can't remember what I typed from the top of my head but I'll get back to you.

---------- Post added at 11:16 PM ---------- Previous post was at 10:32 PM ----------

I strongly believe it was adb reboot-bootloader
[Android Q&A, Help & Troubleshooting] clcombs262:
Isn't working for me

Here's what I've tried:

adb reboot bootloader (reboot normal)
adb reboot-botloader (safe, not fastboot, mode)
adb reboot fastboot (reboot normal)
adb reboot recovery (goes into recovery, as expected)

I also tried:

volume up+power on (recovery)

volume down+power (looped until i let go, then booted normal)

volume up+volume down+power (no reaction)

Is there something else special I need to do with adb, like unplug immediately after the command is issued or something?
[Android Q&A, Help & Troubleshooting] clcombs262:
The official advice from Alcatel is it isn't possible to get into fastboot. Apparently you guys have achieved it though, so it has to be.
[Android Q&A, Help & Troubleshooting] clcombs262:
I've tried every method i could find to get into fastboot. It is not working.

Unless otherwise stated, I tried each of the following with no result

adb reboot bootloader
adb reboot-bootloader
adb reboot -bootloader
adb reboot fastboot (went into safe mode)
adb reboot recovery (worked as expected to get into recovery, but not fastboot)
Volume + and power (recovery)
Volume - and power

Just to confirm, we are talking About the Alcatel Tetra, Android 8.1, December 5 2018 patch, right?
[Android Q&A, Help & Troubleshooting] guyincog:
I did an "adb reboot bootloader", but I'm on the Sept 5, 2018 patch
[Android Q&A, Help & Troubleshooting] ShortsYoungster:
Any luck fixing your issue? I'm having the exact same one
[Android Q&A, Help & Troubleshooting] guyincog:
Specifically, I have the AT&T version (though I first booted it with a Cricket SIM, and it seems to have set up its internal apps for Cricket).

After an "adb reboot bootloader" it ends up in fastboot, with the screen displaying "=> FASTBOOT mode..."