yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Oxynium:
Hello, I have a big problem with this phone...

It was working flawlessly for about a week but today when I disconnected charger from phone, I noticed that Headphones icon is on all the time and phone refuses to play anything from speaker.

And the worst thing is that the screen flickers all the time and phone randomly just blackens screen if that happens.

Anyone encoutered such problem? Is is software/hardware?

Edit: Factory Reset stopped the screen flickering, but phone stays in headphone mode all the time now.

Edit2: Audio reroute app switched on Speakers, headphones icon still up all the time.

Can anyone confirm, is it phone usb failure, or just usb-jack adapter failure? Will new adapter change anything?
[Android Q&A, Help & Troubleshooting] hyegeek:
That sounds like something got damaged in the jack.
[Android Q&A, Help & Troubleshooting] alpsayin:
Anyone tried the ROM released on needrom today?
[Android Q&A, Help & Troubleshooting] jezzabell:
New Rom

S21_GQ3037LF2_Ulefone_V12_2018.5.31.zip

New rom is up on the Ulefone website
[Android Q&A, Help & Troubleshooting] Sebastl:
Translation of the last chinese changelogs

3105: 1. Join Baoxu Screen

2803: Increase the background cleanup whitelist, exempt some communication apps from being cleared by the fast fighter, etc.

0202: Increase the keyboard available in Ukraine

You can view the current version number through 8188, or use the "Product display ID" in 11, 116.
[Android Q&A, Help & Troubleshooting] kaibird:
Hi all,

I have a question I am wondering.....

If I want to switch my root from supersu to magisk, can I flash Magisk directly through TWRP or do I have to reflash the whole stock rom?

Thanks
[Android Q&A, Help & Troubleshooting] Sebastl:
Unlock bootloader, fastboot into tuksoids twrp, use osm0sis unroot and flash magisk. Superuser is working, modules still not really
[Android Q&A, Help & Troubleshooting] TuksOID:
http://ulefone.com/download/armor2.html

About the new version:

Directly see that the rom was fluid, the performance was greatly improved.

Notifications are working.

Sensors are working without delayed loading.

About the upgrade:

I use the letest version of https://spflashtool.com/download/

1. In SP_Flash_Tool leave the option "Download Mode"

2. In SP_Flash_Tool unchecky "recovery", "cache" and "data" (Follow the procedures for flashing the ROM)

3. You will not lose your settings and data if you do not allow the device to start system (read Note 1). Then when the upgrade is finished. Turn on the Smart Phone and keep the vol up pressed to enter the TWRP. If you do not join TWRP, do not let it boot. Immediately press power to turn it off or press power and vol up until device power off and start again, release the power so that enter the TWRP process is repeated. If TWRP is not installed (folow Note 2 procedure).

4. within the TWRP - go to the file manager -> data (scroll down and delete the stock boot backup created by Magisk) This is a prerequisite for magisk being installed again and applying the patch on the recently installed from the new StockROM boot partition.

5. Flash the latest Magisk Framework;

6. Flash the latest openGAPPs Arm64 7.0

Note 1: The boot without the Magisk patch is programmed to format and encrypt the data partition. Therefore, you may lose your data this way too.

Note 2: If TWRP is not installed you can reinstall via the SP Flash Tool. Just put "preloader", twrp renamed to "recovery.img" and "something_with_a_scatter.txt" in a new folder and repeat the same procedure to flash the rom. Return to step 3.

If you want to do a clean install, repeat steps 1, 2 and 3. In step 4, within twrp go to Wipe and "Swipe to Factory Reset" (you will not lose the Internal SD (emulated/0) data. But if you follow to "Format Data" or "Advanced Wipe" check dalvik, data and cache and Swipe... You will surely lose everything. Except the contents of the External SDcard. With this you will really have a clean installation. Hehehe

Then follow steps 5 and 6 to finish

It's done.
[Android Q&A, Help & Troubleshooting] Sebastl:
In recent builds magisks author changed the location of the loopback device.

https://xdaforums.com/apps/magisk/grim-fandango-remastered-magisk-t3812662

Anyway, no special method.

Im waiting for a more or less "final" 16.x before i try to play with it again.
[Android Q&A, Help & Troubleshooting] thomas2000:
Biggest problem I had with the phone was the sensitive buttons. It freaked me out, so I tried to fix it. I took off the 3 screws on each side in the metal panel. I took out the buttons and scratched the back of them on a piece of sandpaper, and placed everything back. I think this totally fixes the sensitive button problem. Do not forget this is at your own risk.
[Android Q&A, Help & Troubleshooting] alpsayin:
This update fixed my fingerprint scanner problem that I mentioned previously. Don't see too much performance enhancement though.
[Android Q&A, Help & Troubleshooting] michael205:
This phone should support Vulcan but when I want to play Ark : Survival evolved I can't see world at all. Any solution ? :)
[Android Q&A, Help & Troubleshooting] alpsayin:
Has anyone figured out how to make busybox installation survive reboots? Or alternatively how to make the busybox magisk module work?
[Android Q&A, Help & Troubleshooting] redfateh:
try to change your Dpi in developer options (change smallest width to 441 or lower)
[Android Q&A, Help & Troubleshooting] sumec100:
I use Busybox Pro v6.7.1.0.apk, installed to / system / sbin.

It works without any problems.

---------- Post added at 03:48 PM ---------- Previous post was at 03:26 PM ----------

I have this rom also fixes ( repaired + better ) the camera. :D I have problems with the phone, I recommend this rom works great ( i did not give a new installation I'm lazy to set everything from over again :( )
[Android Q&A, Help & Troubleshooting] Kefir_to_ja:
Samsung camera chip used in Ulefone is capable of very decent results but the photos from the phone are mediocre at best so I'd expect it to be a software (ROM) flaw. Not that I care much, I use DSLRs for my photography but, being curious, let me ask a question: what does it exactly mean that the ROM "fixes the camera"?

I am still using ROM V12_20171009 and never had a slightest issue with the phone. It works flawlessly. I'd maybe upgrade to the latest ROM (again out of curiosity) but frankly speaking all this ROM flashing business is too much of a hassle for me. Besides, they say "when it works don't mess with it".
[Android Q&A, Help & Troubleshooting] sumec100:
Try to reinstall the new rom, the difference is visible. I have three Armor2 phones, two work well (purchased November 2017) and the third most recent (purchased May 2018) were fingerprint problems, photo sharpening, the video failed to create any. The last rom has eliminated all the problems and i did not give a clean installation (retained user data, recovery and reinstall magisk right after the upgrade ROM). I used this rom for all of my Armor2. I recommend using this new rom. :good:
[Android Q&A, Help & Troubleshooting] alpsayin:
Just a little update to folks using Magisk. Magisk Manager's safetynet API is now outdated and says "invalid response". It's actually probably fine. You can use this app to check if it's actually still working. https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

or this one

https://play.google.com/store/apps/details?id=de.guenthers.safetynet
[Android Q&A, Help & Troubleshooting] Kefir_to_ja:
Thank you for the information. Yep, it's tempting but honestly I'm afraid to mess things up and I do not want to loose current data.
[Android Q&A, Help & Troubleshooting] TuksOID:
Why do you need this module through Magisk?

Have you tried the BusyBox Flashable zip version?

I have not yet used it on this device, but you can try.

The Flashable zip of the BusyBox must be installed before the Magisk Framework.

That is, you will need to run the Magisk uninstaller in order to install the BusyBox.

Do your Backups first.

Well, I'm suspicious that Magisk Uninstaller might have caused bootloop on our device. After all, I needed to use it on other occasions, in which I suffered with the dreaded bootloop. Let me know if it happens to you, so we can confirm that.

(Maybe I did not understand what you need. But if you want to make the experience ... Be my guest. :p :D ;))

Note 1: For arm64 install the UNIVERSAL version

Note 2: Magisk framework 16.7 is very stable. Who has not migrated yet, can move on.

Try using the Nokia Camera App.

Search for terms: HMD Global + Camera + App

I'm enjoying the results.

Maybe I'm not as picky as some guys here on Thread. :p :D

I have not checked if this detail is ok in the Magisk Framework 16.7. Because I do not use Google Pay. And, no kind of payment method through SmartPhone.
[Android Q&A, Help & Troubleshooting] kaibird:
Hi

Can I flash this after the newest OTA update?

Thanks
[Android Q&A, Help & Troubleshooting] michael205:
any new about oreo update ? They promised it but never delivered... Next time i will buy doogiee or what ever it's called :P
[Android Q&A, Help & Troubleshooting] alpsayin:
No Oreo update. If anything, they promised no updates will be sent. It's in one of the replies here.

Otherwise yeah go ahead anyways and let us know how they compare. I'm actually quite interested to hear about dooggee's new rugged phone. Ulefone's new rugged phone's CPU compares worse than armor2 in benchmarks so I'm already a bit disappointed. Dooggee's CPU too. I don't know if that's a battery optimization thing or if it's swifter regardless of the benchmarks.
[Android Q&A, Help & Troubleshooting] michael205:
I don't actually remember if it was dogee or some other manufacturer but that device has 3,5mm headphone jack and usb port waterproof without any covers.

I use my phone as a motorcycle navigation and this matters to me.

All the rest isn't all that important. As long as it's durable and works without hiccup I will be ok with it. I have had been using galaxy S3 neo for over 4 years and if not for this "navigation" I'd probably still use it till this day.

I do remember sending Ulefone an email , and yes they said that Oreo is baking.

Not cool Couse it was I think when the Oreo announcement on their page was posted, long a go
[Android Q&A, Help & Troubleshooting] TuksOID:
Yes. After OTA updates.
[Android Q&A, Help & Troubleshooting] alpsayin:
My phone didn't survive the Mediterranean Sea. I'm not sure I'll be buying this phone again. Also, needrom has a new listing.
[Android Q&A, Help & Troubleshooting] TuksOID:
What a tragedy, man! What happened? Tell us more details about what happened.
[Android Q&A, Help & Troubleshooting] alpsayin:
I was in holidays in Turkey. I used the phone in the pool a little bit then went to sea. Didnt do anything extraordinary. I kept checking if it's still working but just as we left the sea i saw the screen come on then turn off. I thought water caused false input and turned the screen off but it never came back on again. When i connect it to charger a red led lights on top but it doesn't really do anything. Doesn't even charge.

Further inspection showed water inside sim/sd storage. I also noticed a break in one of the plastic teeth of sim storage cover (i did drop this thing enough times). My guess is becauss of that the seal didnt hold. Perhaps if the case was stronger, it could've been better.

Sent from my dad's old Iphone 5c lol
[Android Q&A, Help & Troubleshooting] thomas2000:
hi folks,

Lately im experiencing problems with the gmail app. Im not receiving mails until i sync it myself.

EDIT: Read the reviews at the play store on gmail app and a lot of peeps dont get sync working. I removed all updates on the gmail system app and that fixed it.

Running 20171009 as a virgin.

Maybe updating to the latest rom will be helping.

I think its most safely to run twrp first, so i cant brick it anymore. Is that even possible without wiping the device?
[Android Q&A, Help & Troubleshooting] enzovic:
Sorry to hear that. I broke the first version from armor with salt water also. Nothing dramatic, just half of the touchscreen stopped working the second day after going several times with the phone in water. I think the salt solidified inside the edges of the touchscreen and interrupted the electrical contacts.
[Android Q&A, Help & Troubleshooting] alpsayin:
So it may be possible to bring it back to life with a new display? Did you try it with your first?
[Android Q&A, Help & Troubleshooting] armor2222:
Last year I bought an Armor 2 and until a few days ago it worked fine. I drained my battery overnight and now it seems that it is unable to charge. I read that removing the battery, resetting the phone and turning it back on might help but since it is a fixed battery I don't want to risk damaging it. I have left it charge overnight but there is not even the red light showing. Is there anything I can do to revive my phone?

I specifically registered to this forum to ask this question (sorry for that, but there is not a lot of information around besides this topic) I really hope some of you know more

Thanks!
[Android Q&A, Help & Troubleshooting] zagi988:
Can anyone here help me? I'm trying to deodex the ROM since I want xposed but vendor folder is giving me trouble... Anyone knows how to deodex that too?
[Android Q&A, Help & Troubleshooting] GNdroid:
Help needed - Phone bricked

Hey folks,

I'm in trouble, and hope someone here can help me out...

I have an Armor 2, stock ROM and it was rooted with Magisk/TWRP (3.1.1 by Jemmini). (Like described here in the forum.) Sadly I got careless an "allowed" Magisk Manager to update my Magisk to 17.1...

Result is a bootloop now... :(

To make it worse, I CAN boot into twrp, BUT I can NOT decrypt my data, because it always says: "Pattern failed, please try again", even if I give the correct pattern...

So what can I do?

1. Is it possible to go back to the "old" Magisk to get it boot again?

2. If not, is it possible to get TWRP to decrypt my data?

3. If I manage to get my data back, would a complete re-flash help, to make the phone usable again?

4. Anything else, I can try...? ;)

Any help would be greatly appreciated! :fingers-crossed:
[Android Q&A, Help & Troubleshooting] alpsayin:
Start with taking a twrp backup of all the partitions (including data) so you can go back whatever happens. Then get your hands on SP flash tool and flash the stock boot image and see you can boot into your os. Because if you can't decrypt data magisk uninstaller is not gonna help you restore stock boot image. If all fails try this; erase everything (including data) and flash stock ROM. Then follow your own steps to reach the position you were at before 17.1 update (install twrp, install magisk, whatever you've done for enabling/disabling encryption. Then go to twrp and restore only data partition to see if that helps. When all is lost, remember to take Titanium backups into external sd and use some sort of cloud backup for your photos, videos and docs.
[Android Q&A, Help & Troubleshooting] dm396:
Turning off bluetooth scanning did not help me. However, this morning, I grew desperate and turned off wifi. This seems to have cleared the problem. Any thoughts? Anyone else try this?

Dipak
[Android Q&A, Help & Troubleshooting] dm396:
ulefone armor 2 bluetooth audio issues

Hey...I recently received an armor 2, and I think that I have the same problem. I tried turning off bluetooth scanning in locations settings, but that did not help.

What finally seemed to help...turn off wifi. OF course, this is annoying if you need to stream or voice-over-wifi and use bluetooth, but for listening to music while driving, or regular phone calls, seems to work very well now. Please let me know what you think, or if you have found another solution.
[Android Q&A, Help & Troubleshooting] enzovic:
I returned the phone and received money back and with some more money I got this second version. It was only 7 month old...
[Android Q&A, Help & Troubleshooting] GNdroid:
This would be the "worst case scenario"... I'm not sure if it would be possible to decrypt a data partition that was encrypted with a different installation before, because I'm not sure if the encryption-keys are the same.

So I would prefer trying to "repair" TWRP first. I found some information in the interwebs, that it is possible to fix the "can't decrypt" issue with TWRP on other phones, sadly there was no information, if/how this works with the Armor 2, so I hoped, that someone here might have some information about that.
[Android Q&A, Help & Troubleshooting] andre_ggm:
I wonder if there is already an unofficial rom rom 8.1 for our phone, I think its performance in the 7 miserable
[Android Q&A, Help & Troubleshooting] zagi988:
Sooooooooo, after WEEKS of trying and failing I have FINALLY managed to deodex the 31.05.2018. ROM.

Installation goes like this:

1. Download this flashable zip: https://drive.google.com/file/d/1U1OzvBZGfJQ5rCQBV8pj0Iqz9jRMCXsS/

2. Download gapps from https://opengapps.org/ (choose arm64 > 7.0 > pico)

3. Transfer those two zips to phone

4. MAKE BACKUP WITH TWRP

5. Wipe system, cache, dalvik, data

6. Install ROM

7. Install gapps

8. Reboot

Everything should be working. I have not yet tested if all works but I know that it boots and that it connects to the internet and the basic functionality works.

IF you think I should deodex another ROM version (maybe not the latest) - feel free to comment.

This SHOULD make xposed possible, that was the main reason for deodex... we'll see.

---------- Post added at 12:38 AM ---------- Previous post was at 12:18 AM ----------

Now I see that there is an even newer version of the ROM available for download so now that I know how to deodex it and get it working, I will do the same for the newest ROM and put it up for download.
[Android Q&A, Help & Troubleshooting] zagi988:
I have now tried the newest version which has May 2018 security patch and it seems that when deodexed it somehow kills the camera. It starts to record in 15 FPS and does some weird stuttering.

Will try and flash the odexed version just to confirm if deodexing did that.

I've got latest xposed and latest magisk working great on deodexed version of the last ROM, will now try on deodexed version of what I posted here.
[Android Q&A, Help & Troubleshooting] zagi988:
Just to show it off a bit...
[Android Q&A, Help & Troubleshooting] zagi988:
This is the latest ROM with latest security patch, all working, latest Magisk, latest xposed for SDK24 and so on...

Camera is kindda ****ty although it works much better in the low light. Seems like they've added some stabilization to it and I can't seem to find a way to disable it.

Installation goes like this:

1. Download this flashable zip: https://drive.google.com/file/d/1Q7Ii9850w4vjLe9J0RXgsJvL3g5nDt9H/

2. Download gapps from https://opengapps.org/ (choose arm64 > 7.0 > pico)

3. Transfer those two zips to phone

4. MAKE BACKUP WITH TWRP

5. Wipe system, cache, dalvik, data

6. Install ROM

7. Install gapps

8. Reboot

Optional

9. Install Magisk

10. Reboot

11. Install xposed

12. Reboot

13. Enjoy
[Android Q&A, Help & Troubleshooting] Sebastl:
Thanks zagi988. As i wasnt offered the 0818 Update i took the chance and used your deodexed one. Everything working smooth and well so far.

My main reason was to check if maybe a newer kernel would allow Magisk Modules - Sadly the answer is still no ;(
[Android Q&A, Help & Troubleshooting] zagi988:
Really? I have Youtube Vanced installed as a module, systemlessly... Xposed can't work like that but YT Vanced works for instance...

Does the 0818 update have a laggy camera on your phone?
[Android Q&A, Help & Troubleshooting] TuksOID:
Presenting First lineage OS for MT6757 Based Phone Infinix-X603.

https://xdaforums.com/android/development/lineage-os-14-1-infinix-x603-zero-5-t3776621

The kernel of this OS 14.1 lineage can help (even SOC "MT6757" from our device), for those who know how to make a version for our device. Developer has made available the github source for his device tree. If someone is enabled...
[Android Q&A, Help & Troubleshooting] zagi988:
niiiiiice. I was already working on some device trees for Armor 2 but I'm missing RAM to compile it... Have 8 GB need 16 GB.
[Android Q&A, Help & Troubleshooting] enzovic:
What do you think about the new Ulefone Armor 3T?
[Android Q&A, Help & Troubleshooting] Sebastl:
Hey Zagi. Yes, the camera (focus) seems a little slow, thats true.

Regarding loading modules:

I would love to hear that you found a solution, but i doubt it.

The Kernel just doesnt seem to allow to mount/write to the IMG files.

Could you please check your magisk log right at the beginning ?

It should show sth like "couldnt Mount magisk_merge.img to /sbin/core/XY with Permission 13 (denied)"
[Android Q&A, Help & Troubleshooting] deinfreund:
Thank you guys for writing all these guides. Sorry if this is a newbie error, but I managed to get stuck in a boot loop. Here's what I did

I followed this guide https://xdaforums.com/showpost.php?p=74429860&postcount=68

For recovery.img I used recovery_jemmini_V12_20171009.img, provided in #97. I waited for the reboot and then unplugged the USB cable. I did not wait until TWRP started. Instead of actually booting, it just displays the boot screen and

Orange State

Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

It waits 5 seconds, then the screen turns off. About 3-4 seconds later the cycle repeats. If I connect it to my PC (Win 10 x64) it'll show a "USB device malfunctioned message" on every reboot. I've tried installing new VCOM drivers, but still can't recognize the phone with fastboot, adb and spflashtool gets stuck doing nothing.

#112 suggests

None of these buttons seem to have the desired impact. If I keep pressing either volume up or volume up + power, the screen color inverts (black text on white background). It does not show anything except the "Orange mode" boot message detailed above.

How can I get the phone into some kind of recovery/download mode? For Samsung phones I could usually just press the right combination of keys to do so.
[Android Q&A, Help & Troubleshooting] alpsayin:
Button combinations don't work if usb is still plugged in. Even after that, it's a bit annoying to get the timing right.

If all else fails you can use sp flash tool to reflash the entire device. I'm not entirely sure if we have a guide for it in this thread but there's definitely in Ulefone Power 2 thread and it's exactly the same. Just use the right rom either from ulefone website or needrom.
[Android Q&A, Help & Troubleshooting] deinfreund:
I still didn't get any of the button combinations to work. Switching to Linux and following this sp flash tool tutorial allowed me to reset the phone to stock.

I'll have to find another way to install TWRP now, as doing it on Windows using #97 I always get into the bootloop. I'll update this post if when I get it to work.
[Android Q&A, Help & Troubleshooting] alpsayin:
It's a very basic thing that can cause trouble. You need to flash some sort of root (supersu or magisk) immediately after flashing twrp. You need to to flash twrp, and boot twrp and flash root without letting the device try and boot up.