yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] bigrammy:
Well I have no idea how to fix this because I can not be reproduced it on my device. All sim's I have used/tested work for me in the UK :eek:

You need to keep on at Elisa to find a workaround or fix.

I would ask them to give me a no contract sim and ask them to port that sim's details over to your contract account and see if that works. :fingers-crossed:

Other wise bye bye Elisa or bye bye Lumigon :(
[Miscellaneous Android Development] BaltarWithSix:
Issue resolved! The issue was with my network providers contract sim cards with "Mobile-ID" built in. So when I replaced my sim card (3th time!) and asked to give me sim card without "Mobile-ID" - it worked!
[Miscellaneous Android Development] bigrammy:
Glad you got it sorted out in the end :victory:

I am sure other users with the same issue will find this info very useful so thanks for reporting it back :good:

Mobile-ID some Info on this found here.
[Miscellaneous Android Development] chris8189:
[MENTION=3924647]bigrammy[/MENTION] - Ever tried to hunt down the ex devs of Lumigon? LinkedIn search maybe, to see if they may be willing to give up the kernel source code for this lovely device?

EDIT: I have found a couple of people worth contacting:

https://dk.linkedin.com/in/munter

https://dk.linkedin.com/in/ulrik-bech-hald-6aa0644

Chris
[Miscellaneous Android Development] bigrammy:
Good Idea :D

If anyone has a linkedin account maybe they could politely ask them. :fingers-crossed:
[Miscellaneous Android Development] chris8189:
I've sent a connection request to the first guy. I'll keep you informed ;)

Someone out there that was involved with Lumigon will still be holding on to the source code and everything that was developed for these phones. It's not exactly something that would be thrown away.

Chris
[Miscellaneous Android Development] bigrammy:
Thanks :good:

Hopefully they will respond & have the source code laying around on a hard drive some place. :fingers-crossed:

The thing with this SoC is MediaTek stopped supporting it after MM so I doubt there is any official MediaTek N sources which means some of the proprietary blobs will not get updates so your on your own so to speak. :eek:

I noticed one of the guys specializes in driver development so maybe he would of done a better job than MediaTek in updating the driver set anyway :laugh:

Regardless of that the MM source would allow us to bump up to N without too much hassle assuming someone with the necessary skill set was working on the device.

Given the features of this phone and quality of build It would be well worth any time & effort spent on it. :cool: :cool:

I keep meaning to get around to try porting CM13 but always seem to get distracted probably because I am world champion procrastinator :laugh:

Still struggling with the Sony XA (mt6755) to get the new RIL scheme working properly on Lineage 14.1 at the moment and not sure what the missing piece of the puzzle is. I am running out of idea's now and the only real working example I can find using this SoC is for the oukitel k6000 plus by [MENTION=4196889]DerTeufel1980[/MENTION] of Team MAD fame Not only does the RIL work but he managed to bringup 8.0 too. :crying:
[Miscellaneous Android Development] chris8189:
Christian replied;

Hi Christopher,

No unfortunately the Copenhagen office (where I worked) never had the kernel source. As fare as I'm aware only the Chinese partner had access the kernel source. We received binaries from them and build the firmware.

Unfortunately I don't have access the any of it anymore.

Chris
[Miscellaneous Android Development] bigrammy:
Thanks Chris!

That's a real shame :crying:

Good of him to reply though please pass on our thanks. :highfive:

I doubt the "Chinese partner" would respond even if we knew who they were. :rolleyes:
[Miscellaneous Android Development] chris8189:
I have passed on our thanks to Christian for getting back to us. He said he believes the name of the Chinese partner was called HTT, but has a feeling they went bankrupt. Googling them brings up nothing (that I can find).

He said the whole situation is a shame, and if anyone at Lumigon would have had the source code, it would have been him. But of course he didn't. The Chinese company did.

Very pleasant guy who has tried to help us as best he can.

Chris
[Miscellaneous Android Development] bigrammy:
Thanks for feeding back and passing on our gratitude to Christian and yes a nice guy for sure. :good:

HTT rings a bell now with me too and it makes sense that they too went bankrupt hence why we ended up with such a quality device for such a cheap price. :o

I remember some guys saying the T3's were Fakes of the original T3 but that did not stack up as it would of cost far More to produce a Fake T3 of this quality than they were been sold for.

The Quality seems to have been a little sketchy with some saying their device had this issue or another but I doubt the people handling the liquidation had any care or knowledge for quality checking each and every phone before dumping the entire stock of T3's on the market to be sold off.

Guess I got super lucky for a change getting 3 perfect one's :D

Lineage/CM 13 would seem to be a real possibility using the prebuilt kernel and I am surprised nobody has done a build or port so far. :rolleyes:

Real Dev's seem to avoid MediaTek like the plague with no good reason IMHO as there is plenty of official and leaked full source code out there to adjust/build the binaries and lots of official working kernel sources from OEM's like Sony, for example the Sony M5 is a mt6795 SoC the same as this T3.

MediaTek would do well to invest a little cash and appoint a employee full time in assisting dev's openly or unofficially since the decline of Team MAD who no doubt got full time jobs with OEM's due to their awesome work with MediaTek SoC.

Regards bigrammy. :highfive:
[Miscellaneous Android Development] s4goa:
maybe I write a real short thread about how to put Magisk on the T3 without 9 gazillion pages of digressions...

also the earlier note on why this thread is so "short" (relatively) is easy to explain: XDA adopted a hyper-aggressive stance against new users bombarding them with captchas and restrictions. So it is no wonder that people just post elsewhere!

---------- Post added at 15:11 ---------- Previous post was at 14:32 ----------

the Lumigon manual does not say much on gestures in the camera app. besides 2-finger-zoom, does it do any more tricks that no one knows of?

---------- Post added at 15:16 ---------- Previous post was at 15:11 ----------

sorry, I got no nano SIM and prefer SIP VOIPphone actually...
[Miscellaneous Android Development] bigrammy:
Post #2 Titled Rooting and TWRP is as concise as it gets with very little digressions I think :rolleyes:

I started this thread when there was zero info on this device so I gathered all that I could.

I made my own scatter file as no official one was available also there was No TWRP again down to me.

I will be sure NOT to share in future and leave things up to the pro's like you :good:

peace.
[Miscellaneous Android Development] Marioandu:
Hi! I want to buy Lumigon T3. I found ine for 100 usd. But it is possible to have Andorid 8 or 9 or more? Thank you very much!
[Miscellaneous Android Development] chris8189:
Hi. No it isn't possible unfortunately.
[Miscellaneous Android Development] Marioandu:
Hi !Thank you fo r your answer.

I like this phone and i want to buy 1 for 120 usd. Do you think it is still a good phone or it is obsolete?

Thank you very much!
[Miscellaneous Android Development] Marioandu:
Last question.How is the battery for this pfone? How long?

Thank you!
[Miscellaneous Android Development] bigrammy:
Sadly obsolete because there is no official source code for this device so virtually zero chance of any OS updates.

Android 6 is still valid and currently holds a good sized share so will receive support by app developers for a good while yet.

Battery has a pretty small capacity so not great for heavy users eg; gaming and constant social media use.

I used to use mine for calls, texts, check emails, playing Music and some web browsing and the phone would last all day with probably 40% > 50% power left.

Obviously battery life is 100% dependant on the user and really a nonsensical question so the best answer is that the T3 is no better or worse than other devices with a similar sized battery probably.

If you live in the UK I have one New unused T3 for sale. :o
[Miscellaneous Android Development] chris8189:
As [MENTION=3924647]bigrammy[/MENTION] states, there is no official kernel source code for the phone available, and Lumigon no longer exist as a company.

I did the leg work towards the end of last year to get into contact with as many ex-Lumigon employees as I could, through LinkedIn. Every one of them, when I asked about obtaining the kernel source code for the Lumigon T3 all said the same thing. That all of the Android development for Lumigon's phones were outsourced to a company based in China who have also now gone bust themselves. So there really is no way to get it unfortunately. A very disappointing situation for such a nice phone.

Chris
[Miscellaneous Android Development] s4goa:
I like that style telling ppl what not to do then engaginh in lengthy discussions on SPFT.
[Miscellaneous Android Development] s4goa:
run an GUI app as root with mtk-su

OK guys, let's talk mtk-su. You just call it as /data/local/tmp/mtk-su and bang, you are root. Now you can launch the main activity of some GUI app which offers extra functionality as root such as a filemanager like "root-explorer" etc..

In adb shell this can be done with the monkey instruction or other I ways.

- knowledgable people, please elucidate further on this... -

see also: https://xdaforums.com/android/development/root-lumigon-t3-nonsense-approach-to-t4129959
[Miscellaneous Android Development] bigrammy:
You are confused about everything with only half knowledge about all the steps which points to not fully reading or understanding what your are reading.

This is understandable but cursing op's is not going to win you any friends or get you help....

So chill out and be humble if you don't understand things.

So lets educate you on MTK-SU

So everything is done from your terminal on your PC Linux or Windows.

You set allow usb debugging on your phone.

You connect your phone to the PC via USB cable.

You open your terminal or cmd prompt.

You type adb device and if you get a response like xxserialnumberxx device your good to go.

MTK-SU will only ever get you adb shell running with root privileges. This symbol # denotes when you are root this is also known as a root shell.

When you have root shell you can execute commands and run inbuilt binarys that otherwise you could not.

Where your understanding fails is that you think there is a command that allows a app to be root and do what it wants. :(

Android does not work like that. SuperSU & Magisk are far more complicated than you think.

For me to explain everything regarding these will make this a huge post but since your reading seems limited I will not go into that.

SO if you want to run a app as root like a file manager you MUST root with Magisk or SuperSU.

The easiest way to do that is via TWRP end of story.

You are lucky because you have TWRP thanks to me and thanks to MTK-SU you can now install it without the need of fastboot or SPFlashTool.

Before I continue confirm you understand everything to this point. :fingers-crossed:

.
[Miscellaneous Android Development] s4goa:
mtk-su on the Lumigon

OK, gotcha !

you know, my root experience is with a rooted gingerbread and stuff is kinda easy on those Android 2.3 phones.

but I get what you're saying, I need to follow your TWRP guide which implies complete data erase.

I guess I can do it just last time around, I had no full backup and stopped where the bash shell said it must erase all data.

So if its just a case of following your TWRP guide it seems quite feasible to me.

Thank You for the elucidations! :o
[Miscellaneous Android Development] bigrammy:
Ok to explain further.

The reason for the data wipe in TWRP is because your data is encrypted by default.

I never tried TWRP using encrypted data maybe it will work or maybe not you could just try and see. :confused:

It's Always best practice to start with a clean /data anway in my opinion. :o

Magisk needs to access /data to place some binary files and create folder's which it cannot do if /data is encrypted.

Magisk will patch your boot.img so it does not encrypt your data by default unless you set a Pin or password.

You can follow my original guide or you could use MTK-SU but that will need me to do a tut when I find some time.

If you have any doubts about any part just ask in a clear way giving info or pictures if possible.

Practice booting to recovery using the buttons before you do anything.

This will ensure TWRP does not get overwrote by the OS.

EDIT: You do not need to flash the magisk_patched boot if you boot straight to TWRP as you can simply use the latest Magisk.zip
[Miscellaneous Android Development] s4goa:
TWRP boot

OK cool just am about to finish backing up data n stuff and will go into this thing now. :laugh:
[Miscellaneous Android Development] bigrammy:
Ok good luck and if you get stuck just ask giving as much detail as you can.
[Miscellaneous Android Development] s4goa:
dammit

didn't have it though.

SP FT never finds my USB ports and does absolutely nothing (except logging that it cant find my usb ports tried bot 2.0 and 3.0). in Linux Fedora 32. may run a ubuntu or some stuff like that ?

adb sideload magisk.zip # nothing happens.

so it was all for nought. :silly: so " simply using the latest Magisk.zip" did not pull it off for me.

---------- Post added at 03:06 ---------- Previous post was at 02:37 ----------

fastboot flashing unlock_critical

(bootloader) Start unlock flow

FAILED ()

Finished. Total time: 21.830s

---------- Post added at 03:18 ---------- Previous post was at 03:06 ----------

sweet! now I've got:

orange state

your device has been unlocked and cannot be trusted

device will reboot in 5 seconds

but it never boots fully up. Lumigon is stuck in logo screen forever.

sweet logo! :D
[Miscellaneous Android Development] bigrammy:
:( Where in my instructions did I say do any of that??

You are wasting your own and my time if you don't follow my advice. :crying:

I said if you got stuck just ask :crying:
[Miscellaneous Android Development] s4goa:
orange state ? no biggie

"orange state" is not a big deal though on the Lumigon T3.

Just wait like 20 minutes, the T3 will get over it and boot up without trouble save the "orange state" screen info.

just make sure you don't get into the red state.

orange state will go away after successful flashing (presumably).

But that is the essential hurdle: in most Linuces, SP flashtool will FAIL, Ubuntu may be a possible candidate where it works.

By the way: using UNLOCK BOOTLOADER in the phones's Developer Menu has no effect on ORANGE STATE, as you probably guessed already.

To reiterate: most difficult is to find a Linux distro install where SPFT actually does work. Most GUIDEs do not explicity state it: the phone must be switched OFF while flashing with MTek SPFlashTool for Linux&Win.

#####

to summarize: essentially there is no way around using SPFT (Win/Linux) and flash TWRP with SPFT . While fasttool or some adb shell business can get you root for a sh , you cannot quickly run a GUI "Root Explorer" with just a mtk-su running in a Bourne sh like in Android-gingerbread days.

#####
[Miscellaneous Android Development] bigrammy:
Wow :laugh:

Orange State only happens when you unlock the bootloader. So if you have that message then you unlocked it.

It will then force wipe your data.

It will then overwrite TWRP with the stock recovery if you even managed to flash it.

So you will now have a unlocked bootloader, orange state warning, No TWRP and of course no root maybe even a ROM that won't boot. :rolleyes:

I have fixed SPFlashTool in all the linux distro's I have used as have many others and again it just requires a little effort.

You could of used mtk-su to flash TWRP and then root via Magisk without unlocking the bootloader but again you did not seek advice on how to do that. :crying:
[Miscellaneous Android Development] s4goa:
use mtk-su to flash TWRP

indeed I have no clue how to flash TWRP using mtk-su

"root via Magisk without unlocking the bootloader."

UNLOCKING could mean either of 2 things:

1 . goto ORANGE STATE

2. or just use the option in the the Developer Menu titled "unlock bootloader".

which of those 2 are you referring to?

Like I said, so far Magisk did absolutely nothing for me for the stated reasons, namely, that I cannot flash at all.

in case I get mAid/FWUL to work I could reflash the Lumigon unless more fuqqups happen, that is.

But I'd still be interested: Could you please explain how use mtk-su to flash TWRP ?
[Miscellaneous Android Development] bigrammy:
Neither of those are ever mentioned. You highlighted the wrong word it should be WITHOUT that means NOT Unlocking the bootloader. :crying:

Maybe google translate is not working for you I don't know :confused:

Is your phone still booting up first?

If it's not then mtk-su wont work and you will need SPFlashTool to recover the phone.
[Miscellaneous Android Development] s4goa:
mtk-su

sure, like I said, the orange state is no biggie. Apart from the text lines "orange state ... bla bla" I didnt notice any difference.

SPFT info https://forum.hovatek.com/thread-159.html
[Miscellaneous Android Development] s4goa:
*#*#225#*#* works without SIM but most need SIM which I don’t have.
[Miscellaneous Android Development] s4goa:
mtk-easy-su

https://github.com/JunioJsv/mtk-easy-su

seems like the way forward here. let's see how far I get with it.
[Miscellaneous Android Development] s4goa:
easy su

a lil offtopic since no TWRP involved: http://xdaforums.com/showpost.php?p=83019849&postcount=1

---------- Post added at 23:23 ---------- Previous post was at 22:25 ----------

:confused: "end of story, really? :confused:

In my opinion, your abovestated belief was not borne out by the facts.

flashing / installing TWRP can be MUCH more tedious than just dropping 2 apk’s onto the Lumigon T3, obviously.

The failure / crash rate or SPFT on real life Linuces will easily be clear of 50% . I think using my suggestion for most people is the easiest way to root by far on the Lumigon and many other Mtek-cpu phones.

Of course, SPFT will help in cases where .apk’s can no longer be useful, but it does require significant expediences and introduces numerous points of failure on top of that.

Since Lumigon went bancrupt there will be no OTA updates and the rooting method will stay functional forever hence. :laugh:

Other Mtek customers / phone users might run into a future OTA update which will kill their root-access, in contrast. :crying:

it maybe worthwhile looking into those apk's which can BAK/RESTORE partitions just as TWRP does it, and use those to get TWRP onto the phone.
[Miscellaneous Android Development] bigrammy:
Yes make system mods and see what happens.

Good luck with those various root .apk's that maybe steel others work IDK about that one to be honest.

Unless [MENTION=8132642]diplomatic[/MENTION] the dev of mtk-su sanctioned it or others I wont be using any of them.

Good Luck :good:
[Miscellaneous Android Development] s4goa:
mtk-easy-su

I am not sure whether every MTK phone user can find the time to research for conceivable sanctions given to all applications of mtk-su such as mtk-easy-su . And indeed, mtk-easy-su mentions [MENTION=8132642]diplomatic[/MENTION] prominently, but [MENTION=8132642]diplomatic[/MENTION] seemingly is not listed as a participant at the github. "So what?" is my reply. :confused:

That on top of the research these users will have to do anyway, which often time produced outdated tutorials and what not. btw, I’m not using google-translate as you suggested earlier. :p
[Miscellaneous Android Development] s4goa:
fastboot flash recovery twrpT3.img

adb reboot bootloader

If your asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type this into the command line:

fastboot flash recovery twrp-2.8.x.x-xxx.img

Here modify twrp.img with the name of T3 TWRP recovery .img file from OP #1 obviously.

fastboot reboot

I wonder whether it works on a Lumigon T3 also like they say here: link
[Miscellaneous Android Development] bigrammy:
It should on a unlocked bootloader unless they blocked flashing the recovery partition as some do.
[Miscellaneous Android Development] s4goa:
unlocked bootloader

you keep using the term "unlocked bootloader" but I am unsure whether you actually mean "Orange State" or not. please clarify if it is not too inconvenient. Thanks. :o
[Miscellaneous Android Development] bigrammy:
"Orange State" = unlocked bootloader

bootloader Unlocked is the more accepted term and everyone will understand what your talking about. :laugh:

You don't ask OEM's for a Orange State code you ask for a bootloader Unlock code ;)
[Miscellaneous Android Development] s4goa:
fastboot flash recovery ./T3-TWRP-Final.img

fastboot flash recovery ./T3-TWRP-Final.img

well, you were right! I can successfully use TWRP v3.0.2-2 by bigrammy now.

that is the good news. TWRP works, I can still get into FASTBOOT MODE to flash some boot.img and in TWRP I can mount a USB stick via USB-OTG alright.

Just a little snag: I can no longer boot into Android itself. I always get into TWRP where I must mount READONLY. Then there are many red error message about /data/ mount error and what not. I attached screenies of those onto OTG-stick and attach to a post on XDA here. so now I manually format /data/ from inside TWRP. therefore I get to see the old bootanimation rather than TWRP for a change.

Now the secret is not to wait forever but to powercycle, go into twrp, backup some stuff, and finally BOOT INTO SYSTEM meaning going into actual Android.

Ha! this is all very user-friendly. :laugh: But you should be happy because the stock recovery really is pretty useless and TWRP is much more powerful than stock recovery.

T3 is starting ... Optimizing app 67 of 67 . :cool:
[Miscellaneous Android Development] bigrammy:
OK so your data is encrypted and you mounted system read only so there is not a lot TWRP can do.

Also YOUR TWRP WILL BE GONE after your reboot so you will need to flash it again

When Back In TWRP:

1. So what I would do is go to Menu > Wipe > Advanced Format your userdata (type yes to confirm) This will format everything on your internal_sdcard even Pictures Music etc etc. So ensure you have backed it all up to PC or external_sdcard.

2. When it's done go to the Reboot Menu and choose Recovery (If prompted to install SuperSU just ignore it and choose do not install)

3. When your back in TWRP Swipe to ALLOW TWRP to mount the system.

4. Get the latest Magisk.zip and transfer it to the phone via USB or insert a usb-otg with it already loaded.

5. Now choose Install and select the storage where you put magisk.zip and select it.

6. When it's done just reboot and your done FULLY rooted install any apps you like.

Also when you boot to TWRP again it will still be there and data should be readable Not encrypted unless you set a pin / password of course.

That's What I do but you do what you Like.

PS: IF you would of listened in the first instance and followed the instruction in the OP as the 1000's of people have successfully done already You would be rooted long ago and you would not have the Orange State message So I really hope you have learned a lesson here as No further help or advice from me now you have TWRP installed

..
[Miscellaneous Android Development] alecxs:
lol.. u forgot the [/irony] tag :D
[Miscellaneous Android Development] bigrammy:
Yes I most certainly did! :laugh: :laugh:

I get drawn in just to prove my point sometimes. :crying:
[Miscellaneous Android Development] s4goa:
well, since my method clearly is much quicker, it makes perfect sense to not always follow the advice given. Especially when that is next to infeasible, as here.

had I followed the "advice", I might still be unrooted by now. ;)