Ulefone Armor 3W/3WT

ultramad said:

Thanks, I have tried the arm 64ab gsi rom from havoc but that just got stuck on the boot logo. Maybe I missed a step somewhere? I'll have another go at it tonight

Click to expand...

Click to collapse

I would try just reflashing the stock rom and trying again. It eliminates the "bug" i found that just doesn't let any rom boot at all until you reflash stock and makes sure you didn't miss any step as you do them again from the start.


By the way... in case anyone finds that the camera lens shakes and snaps while trying to focus i think it is not hardware related but something wrong with the stock camera app. In my case every other app from snapchat or telegram to open camera or anything else never once had that issue while the stock camera sometimes does.

Thanks.

So flash stock with sp tools on download only, run through the stock setup, flash twrp, format data then flash havoc through twrp, flash magisk and reboot?

ultramad said:

Thanks.

So flash stock with sp tools on download only, run through the stock setup, flash twrp, format data then flash havoc through twrp, flash magisk and reboot?

Click to expand...

Click to collapse

You might have to do flashing unlock again in fastboot... not too sure myself because my current win10 install for some reason won't work with anything fastboot it just constantly plays the usb connect sound but from what i remember it might relock it after you flash with sp tools. I posted somewhere early in this thread the process that worked for me so you could try doing that after reflashing to stock.

I have tried the method you posted but still get stuck on the boot logo... also when flashing the rom it only goes to the boot logo if I install magisk otherwise it goes straight back into twrp.

Any ideas?

ultramad said:

I have tried the method you posted but still get stuck on the boot logo... also when flashing the rom it only goes to the boot logo if I install magisk otherwise it goes straight back into twrp.

Any ideas?

Click to expand...

Click to collapse

You can try flashing it with A only rom and letting it bootloop (a only will bootloop either way) and then force shutdown and back into twrp to flash AB. I do remember trying that once but if that doesn't work then i have no idea. Maybe something broke in new roms so you could try flashing one from early 2020 (back when i last tried) because i can not test it myself due to my windows install breaking fastboot but i highly doubt that or someone else would also say something about it not working anymore. Im afraid this phone is just very glitchy sometimes and you have to randomly poke it and try things until it suddenly works...

Just flashed Havoc-OS-v3.1-20200121-ARM64AB-GSI from stock by formatting data (not wiping) then reboot to recovery and wipe system and both caches and then installing the img to system and flashing no encryption zip which ended with an error and then magisk which flashed fine. It does indeed bootloop. I then rebooted to twrp again and wiped everything except sdcard and flashed an old build i had left over on my sdcard which was v3.0 20191215 arm64 ab unofficial and that booted right up. Latest lineage also works which tells me the havoc dev broke something.

EDIT: Also installed pixel experience now which seems to work great.

Thanks a lot for your help. Have got the latest havoc os 3.0 an running with magisk and opengapps pico now

Hows the battery life on the custom roms?

I haven't noticed any better battery life on havoc os 3.0 but performance seems slightly improved

ultramad said:

I haven't noticed any better battery life on havoc os 3.0 but performance seems slightly improved

Click to expand...

Click to collapse

As long as it's not worse. I'd hate to take the time to flash another OS only to find out it's buggy. So you're happy?

Yes I'm happy with it, battery isn't any worse. Only problem I have is videos glitch and don't play on Facebook, I notice there is a newer version of 3.1 out so will flash that later today and see if it boots up.

Instruments not working

Hello. I have a question about ulefone armor 3wt. I bought it and it seems that all instruments not working. Compass, bubble level, protractor, plumb bob, proximity sensor .... It is hardware or software? I reset to factory but still the same.

ultramad said:

I haven't noticed any better battery life on havoc os 3.0 but performance seems slightly improved

Click to expand...

Click to collapse

ultramad said:

Yes I'm happy with it, battery isn't any worse. Only problem I have is videos glitch and don't play on Facebook, I notice there is a newer version of 3.1 out so will flash that later today and see if it boots up.

Click to expand...

Click to collapse

Cool let me know how it goes.

Hello everyone. I also had this problem of brightness / proximity sensor with my device. then following the tip of some users in this topic I installed "havoc os" believing that it would solve this problem. but not. the luminosity / proximity sensor keeps stopping the same in the rom stock. when i installed i made all the wipes on twrp but i noticed that it does not erase everything, it still leaves something from the rom stock, like for example the kernel, nvram, and i believe that the drive that controls the luminosity / proximity sensor. I think it's because of the AB partition. it looks like twrp wipes only on partition a and these sensor control files should stay on b. so I believe that any custom rom that installs will not do any good to solve this problem of these sensors, because the rom will always get the drive information from the rom stock that is in partition b

has anyone been successful in the issue of the luminosity / proximity sensors problem?

Hi there, here a newby and his phone

Hi there everybody.

After 2 years using the Armor 2, I doubted long whether I should buy the 3T or the newer 3WT model and allthough I finally choosed the 3WT because of the price difference, I now reckon that I maybe should have rather bought the 3T. Android 8.1, at least on the Armor 2 is solid, logic and Ulefone has through several updates solved the few glitches and hitches its build had when released.

So far, my 3WT works fine, but the system build feels like shabby, sloppy.... and android 9 is not much older than a year, maybe two and it seems to me that it's been some sort of middlestage before android 10.

Unfamiliarities and personal opinions about Android 9 aside, here are some of the funny things this phone does, which I cannot blame other than the OS-build for:
-It mainly refuses to connect to my 5Ghz-Wi-Fi. Sometimes it does, mainly it doesn't... When casually connected, the connection is solid, though, but it mainly shows my 5Ghz network as -disabled-
-It un-deactivates Duo and YouTube apps, which I don't need nor want and cannot unninstall, but deactivate. Nevermind. The system activates them and updates them despite I have disabled all the automatic updates.
-It turns location (which I normally have turned off and I only turn on when needed) on both soft and hard reboot. But it doesn't do it consistently. It mostly turns it on, but once every blue moon, it doesn't.
-Once you activate the walkie talkie, there is no human way to get the notification out of there.
-It rolls back on reboot some defaults to the initial apps. eg: Instead of messages, I use QKSMS. Sometimes, after a reboot, it changes by its own will to set messages as the default app to handle my sms... etc.
-It blocks the developer options all by itself on reboot!!!
-It repeatedly asks for the same freaking updates, even if I installed them a couple days ago.... It feels as it resetted itself to factory settings when it reboots... but, again, not constantly, not consistently, only when it pleases to, without warning. The apps seem to keep the settings I have chosen, but not the freaking OS.

So, my options, after one month of daily usage are the following:

-Send the crap back to china and order the 3WT with android 8.1
-Try to compile my own custom ROM based on Android 8.1 specifically build for this model.
-Try to hack and adapt the stock Rom for the 3WT to this specific model, based on either Android 9 or 10 (which I haven't used yet).
-Try to find a custom rom that either or both solves all the glitches and hitches or allows downgrading to android 8.1, which so far seems the most solid, well thought and functional iteration of Android.
-Lay on the floor in fetal position, roll and suck my thumb.

The worse of all that is that when I can consider myself an over-the-average user of Linux, I am not a developer and I am a complete ignorant when it comes to Android.

I think I'll start trying to learn how to unblock the bootloader and try to get rid of the unwanted system apps.

Any hints, tips, or experience other than the previously referred in the prior pages?

Thank you all for all the patience.
Paul

EDIT: My OS compilation number as shown in the system info: Armor_3WT_RF1_EEA_V01
If I try to update the system, it says that the system is updated and I get following version number: Armor_3WT_RF1_EEA_V01_20191017-1743

no tools for Linux??

Hi. I'm trying to fiddle on my 3wt, but I cannot find rooting flashing or driver tools for doing it from Linux or, in the worst case, Mac.

I got rid of Windows long ago and I wouldn't like to start looking back.

Thank you for all help
P

New ROM

Hi all, it seems that new stock ROM version is available here: https://drive.google.com/drive/folders/1PounIRufNQtS2OhdSO5dlKSy3EGaDfkc (archive file name GQ3060RF2_AGS62_Ulefone_EEA_20200116_V04 (Eu).zip).
I'm just curious if somebody tried this already and if so - does it solve the proximity and light sensor issue?

Clight75 said:

Hi all, it seems that new stock ROM version is available here: https://drive.google.com/drive/folders/1PounIRufNQtS2OhdSO5dlKSy3EGaDfkc (archive file name GQ3060RF2_AGS62_Ulefone_EEA_20200116_V04 (Eu).zip).
I'm just curious if somebody tried this already and if so - does it solve the proximity and light sensor issue?

Click to expand...

Click to collapse

That's for 3W. For 3WT there is version V05 here: https://drive.google.com/drive/folders/1uJgVHnm6OXQXYKYw0vXRDcC40oCB9TK8

I have bought 3WT a few days ago, and went immediately for a root (I can't live without root, it's like water ).
It took me a whole day, but I managed to root the phone (bricking it somewhere along the way, but recovered), but due to some problems I ended up with red text overlay. I couldn't find a way to get rid of it, so I flashed Lineage OS, and now almost everything works fine. I even managed to install xposed, and Gravity Box is a great thing. The things that don't work fine are:
1. No walkie-talkie app.
2. In-call volume cannot be changed. This one is strange - the volume is quite fine, but I cannot change it, and it won't be fine when get to talk on a busy street. I tried alternative dialers, but they worked the same. Whatsapp calls work fine - I can change the volume there.
3. The sounds are too loud. Even when ring and notification volume is at the lowest setting above zero, they are too loud in the night. I kind of solved it by reducing volume of my sound files I use for ring and notifications. And I managed to increase steps for media volume, but I cannot find a way to increase steps for notification volume too.

It would be much appreciated it someone knew how to solve these issues. I'm thinking about flashing some other rom based on android 9, or maybe 8.1 even. I tried Resurrection Remix, but it was looping back to TWRP. Maybe I will try again.
I'm also thinking about flashing back the original firmware, to get the walkie-talkie functionality. But I would have to find a way to remove the red texts. Does anyone knows how to do it?

The bootloader unlock worked this way for me (on Windows, but I think it will work on Linux too - the ADB and fastboot are available there, right?
1. Enable developer menu (Settings, Information, tap Build number 8-9 times).
2. Enable “OEM Unlock” option and USB Debugging in Developer options.
3. Connect the phone to USB, run a console on PC, navigate to the ADB/fastboot installation dir.
4. In the console type:
adb reboot bootloader
5. The phone will reboot in bootloader mode, then type:
fastboot flashing unlock
(the usually recommended fastboot oem unlock didn't work for me).
The phone may show a question with tiny, barely readable font, if you are sure you want to unlock. You have to use the volume and power keys to confirm.
After confirmation, it's done - you are unlocked.
6. Then you can flash twrp with:
fastboot flash recovery twrp-recovery.img
7. IMPORTANT: If you reboot the phone after flashing TWRP, the original software will restore the original recovery.
To keep twrp, you have to do this immediately after flashing twrp:
- turn off the phone by long-pressing power,
- still keeping power pressed, press volume up,
- release power for a quick moment, and press it again (still keeping volume up pressed),
- when the phone logo shows on the screen, release both power and volume up.
- in twrp format data partition, reboot, flash DisableForceEncryption/magisk/OS, etc.

I'm not sure if I remember the procedure details correctly (do everything on your own responsibility, as usual), but it should work.