yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Curtis_:
Thank you for the quick answer!

I'll try it tomorrow, and respond with the results...
[Android Q&A, Help & Troubleshooting] alpsayin:
Can we directly go into the Magisk setup without rooting first? [MENTION=3837734]djvinniev77[/MENTION] 's post (#89) how to switch to Magisk from root, ideally i would save myself the time and go from clean ROM. I.e. unlock bootloader, lose data, set-up phone again (minimal), flash jemmini's TWRP, flash Magisk, flash additional SafetyNet things, profit (adaway, greenify, titanium backup).

Another question is has anyone else played around and figured out what triggered SafetyNet in such setup? Also ideally, I don't wanna go through the whole lose-data-setup-apps-again thing only to lose Android Pay and go back to clean ROM.

Also, I must say; I really wasn't expecting this much work on this little(?) brick of a phone, but I'm so thankful to you guys. You've done great work.
[Android Q&A, Help & Troubleshooting] alpsayin:
I'm happy to just have root and android pay. I'll give this a go as soon as possible. Greenify, titanium Backup, adaway, wifi key recovery etc. Still better than nothing. And possibly lucky patcher :)
[Android Q&A, Help & Troubleshooting] sumec100:
Thank you for writing a second step.:good:
[Android Q&A, Help & Troubleshooting] Curtis_:
Sorry that i'm that newbie, but i'm still stucked....

I have only TWRP, and fastboot... How can i install stock rom to this device?

I mean: Wipe does not work because the problem i wrote earlier.

I can go to fastboot, or stay in TWRP - no other choices.

I tried several flashingtools:

- Ulefone official just didn't work. As i read in other forums - it newer worked because of missing checksum.ini

- NeedRom's said that i have to shutdown the phone, set the flashingtool to download mode, and start the phone... But because the phone automatically goes into TWRP it just can't find the phone...

So now, i have a phone that:

- writes at boot that phone is unlocked, and can't be trusted

- TRWP starts with following messages

Updating partition details...

...done

Full SELinux support is present

Data successfully decrypted, new block device '/dev/block/dm-0'

Updating partition details...

...done

Unable to mount storage

Unable to mount /data/media/TRWP/.trwps

MTP Enabled

Failed to mount 'data' (Invalid argument)

I have TWRP 3.1.1. by Jemini...

From this step , i can boot to fastboot, or shutdown the phone, or reboot it...

If i update TRWP trough fastboot

by comment #93 (sorry, i'm still not allowed to post links here),

and then install SuperSu./Magisk from pendrive that should do the trick?

(I'm worried because of this: "After the installation of the recovery, under the condition of resolving the changes in the system, it is necessary to install ROOT, otherwise the system will not boot." )

(I'm working in IT in almost 20 years, and it was a long time ago when i feel myself this stupid :) )

So the question is still similar... How can i install stock rom in this state?
[Android Q&A, Help & Troubleshooting] djvinniev77:
So first you should use the stock ROM and so flash utility to get yourself back to complete stock.

It works much better on Linux as long as you have the latest version of the sp flash utility, or else it will give you some error about incompatible Brom this or that. I found that out the hard way.

If you're on windows, particularly windows 10, there's a driver installation step that you need to do to ensure that the MediaTek vcom drivers work, boot to windows recovery mode, disable driver signing, reboot and install drivers, then try and get it to work.

Regardless, as long as the drivers are installed, the sp flash utility should work, and the way to do it is this.

Load the sp flash utility, load the scatter file for the rom you download for device from either ulefone or needrom, on the sp flash utility, select download and hit the download button so it's "waiting" for device.

At this time, device should be completely powered off, not plugged in to anything. Grab the device, hold the volume up key down, then plug in the device to your PC. You should see the sp flash utility detect the device and the status bar at the bottom fill up red. You can let go of the volume up key, the device details should be noted on the screen on the left side of the sp flash window, and the rom/scatter file will start to flash the files to bring your device back to life.

Hopefully that brings you back to stock to start tweaking again.
[Android Q&A, Help & Troubleshooting] sumec100:
Do not despair. These steps need to be taken slowly and read our practices well. With this phone we are all newcomers that is why we deal here together. In this thread, there are already enough steps for a successful root, and nothing else is working. These steps are taken from other discussions and are only tuned for Armor2. If our instructions are combined with the original instructions you end up failing ( original procedures are universal or intended for other phones ).

Everything you need:

good implements:

1 - correct and functional vcom drivers (for Win or Linux)

2 - correct and functional SPflashtool v5.1728 (for Win or Linux)

3 - installed SDK managere (for Win or Linux)

good files:

1 - original rom from www.ulefone.com S21_GQ3037LF2_Ulefone_V12_20171009.zip

2 - recovery_jemmini_V12_20171009.img

3 - SR1-SuperSU-v2.82-SR1.zip or (Magisk-v14.0.zip and MagiskManager-v5.4.0.apk)

good guides:

1 - the tutorials that are in the discussion from sheet 7 -> . . .

2 - calm nerves and good eyes

Note: who wants to keep the pay store functions, do not root - unless the bootloader is modified, this option will not work. Unlock bootloader reports to the system android that the system is dangerous. Even when TWRP and Magisk can be set unreadable for android, the OEM unlock flag will completely cancel it. As a result, either pay store functions or root, both can not. But even so, thank everyone for the quick creation of the root for this phone, which I consider to be a great success. :good:
[Android Q&A, Help & Troubleshooting] alpsayin:
I guess I must add; something's actually off with that PRO version. I bought and tried to remap the camera button. Button Mapper PRO did not recognise the armor2's camera button. So the method you suggested might be the ONLY way to remap it...

This was some time ago, and I did return the purchase upon failure :/. Has anyone else actually tried the PRO version besides me?
[Android Q&A, Help & Troubleshooting] djvinniev77:
yeah that's true. even with pro you see the camera button section but assigning things to it didn't work as designed, the long press for 5 seconds still launched the camera app no matter what.

what i did definitely broke it though, as key 212 CAMERA is set as a default key layout. When that's no longer assigned as CAMERA but as something else (GRAVE) it works much better.:D
[Android Q&A, Help & Troubleshooting] alpsayin:
Ok, someone please answer me this question. I'll ask very clearly because I'm confused again. Systemless Xposed via Magisk triggers SafetyNet, so we definitely cannot have Xposed and Android Pay; this I understand. But can we have Root via Magisk and Android Pay? So [Android Pay: yes, Root: yes, Xposed:no]-> is this what you guys have or what is possible right now?
[Android Q&A, Help & Troubleshooting] sumec100:
The clear answer is no. Until the bootloader patch is resolved, it is not possible. Magisk has the option of installing such a patch, we do not have the patch. Android must know that it has a bootloader locked, but you can not do the root when the bootloaders are locked. The second solution is to use custom rom, but we do not have it. I do not know how to do it, so ask those who know it. I'm only saying that this is now mutually exclusive. :(

if the bootloader is locked -> Android Pay = yes -> Root = no -> Xposed = no -> . . . = no

if bootloader is unlocked -> Android Pay = no -> Root = yes -> Xposed = yes -> . . . = yes

if the patch bootloader is theoretically -> Android Pay = yes -> Root = yes -> Xposed = yes -> . . . = yes

if the custom rom is theoretically -> Android Pay = yes -> Root = yes -> Xposed = yes -> . . . = yes

we have nothing to verify, therefore theoretically.
[Android Q&A, Help & Troubleshooting] alpsayin:
Well, thanks so much for testing this :). Guess I'll wait a bit. Custom Roms also wouldn't work with android pay, I think the rom signatures have to be signed by Google itself. I was having this problem with one plus one with cyanogenmod or even cyanogen os (special oneplus one release) in fact.
[Android Q&A, Help & Troubleshooting] djvinniev77:
Yes, this is possible. I have set up Magisk and android pay, and there are no triggers that the device is rooted or have any issues. I have added the debit card before and used it to pay. Can definitely validate again. :)
[Android Q&A, Help & Troubleshooting] sumec100:
just a question. change all "key 212 CAMERA" rows in these files?
[Android Q&A, Help & Troubleshooting] djvinniev77:
for me it works. Bootloader unlocked. Magisk installed, Root via Magisk yes, No Xposed. - works.

---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

yup, it's reference 2x in the file, as the developers look like they entered in their own section. either way, I changed on both.
[Android Q&A, Help & Troubleshooting] djvinniev77:
Here's my config files to reference the button inputs
[Android Q&A, Help & Troubleshooting] sumec100:
thank you great work. One more question, in Magisk, when installing modules, quit failed

- Found /data/magisk_merge.img

- Mounting /data/magisk_merge.img to / dev / tmp / magisk_img

! /data/magisk_merge.img mount failed ...

Failed!

what is the error or what I am wrong set up. :(
[Android Q&A, Help & Troubleshooting] Curtis_:
djvinniev77, sumec100 Thank you for the Help!

I tought that my USB drivers are ok, because i could manage my phone trough adb and fastboot commands trough cable... (i could query device status, install trwp etc..)

I was wrong.

As it turned out, every time i connect my PC to a powered off phone, it starts the phone up, and shows a small notification about usb/device problem - witch i did'nt notice until now...(yeah, i know - user error :/ ) In the same time the phone boots up to TRWP - no matter if i press volume up.... If i reboot to fastboot, i can send commands to the phone trough terminal.

I'll continue when i solved that driver problem... Again, Thank you guys! :)
[Android Q&A, Help & Troubleshooting] sumec100:
You are welcome. if you can not install original rom in SPflashtool mode - select Download only -> push Download ( bootloop ), use SPflashtool mode - select Format All + Download -> push Download. The phone completely clears and the settings are new (bootloader is locked and IMEI changed to 111 ..., 222 ...), the phone will normally work. I am describing the IMEI change in the post above. it happened to me, I did not let the phone start up after replacing boot.img. the screen has been illuminated for so long, so I turned it off. :crying: helped only "select Format All + Download" :angel:
[Android Q&A, Help & Troubleshooting] djvinniev77:
really odd you're getting that error when flashing magisk. I didn't see anything like that at all going through the steps I ended up doing, and since TWRP would wipe everything after install because it can't pass the password/encryption, I have no choice but flash the Magisk 14.3 zip file through USB OTG and get properly set up.

It doesn't like to be installed again though, so if you already did Magisk once, from Twrp, then wiped device again and try to reinstall, it won't like it, and you'll be in bootloop.

Good luck man!
[Android Q&A, Help & Troubleshooting] hezig:
my bluetooth gets disconnected all the time. annoying, especially while driving
[Android Q&A, Help & Troubleshooting] djvinniev77:
Yeah it's pretty bad. Seems for me it happens when handling a phone call. It disconnects from Bluetooth and I have to resort to speaker phone or handset.

I stream with a Bluetooth audio device connected to aux in my car, when I play music like Spotify through it the bt doesn't disconnect. Only happens to me on phone calls.
[Android Q&A, Help & Troubleshooting] alpsayin:
Android Pay & Root together working confirmed. [MENTION=5404196]sumec100[/MENTION] I wonder what went wrong in your setup. And thanks so much [MENTION=3837734]djvinniev77[/MENTION] !!! :)
[Android Q&A, Help & Troubleshooting] sumec100:
Yes, you are right, I confirm that it works. :good:

By using Magisk the first time, I did not understand how and what works. :confused:

I found out why Magisk modules can not be installed and also from TWRP. :crying:

Kernels Armor 2 does not support full SuperSU functionality, you can find more information here:

xdaforums.com/showpost.php?p=70492947&postcount=8793

Therefore, systemless root app installation does not work. The standard installation of root apps usually works smoothly, just installing the original xpossed module disables SafetyNet = red, uninstalling original xpossed module turns SafetyNet = green. In both cases, the device remains certified in Google Play. :rolleyes:

Update:

" When Magisk is used: bootloader is unlocked -> Android Pay = yes (or no) -> Root = yes -> Systemless Root app = no -> original Xposed = no (or yes)-> Titanium app and . . . = yes -> edit buttons = yes -> phone certified = yes "

" When only SuperSu is used: bootloader is unlocked -> Android Pay = no -> Root = yes -> Systemless Root app = no -> original Xposed = yes -> Titanium app and . . . = yes -> edit buttons = yes -> phone certified = no "

We have enough combinations just choose :confused: :D
[Android Q&A, Help & Troubleshooting] alpsayin:
Just gonna confirm this. Took me some time to realise what's going on too. Also systemless hosts switch in Magisk setting keeps resetting itself. But Adaway seems to be doing its thing. On another note, lucky patcher complains about lack of busybox but also does its thing.

So from what I understand, even though we have some sort of root, the system partition is still untouched, and even more so; it's untouchable even with TWRP.

Also on another note; Button Mapper asked for root priveleges and I gave it. I also completely uninstalled Zello with Titanium Backup. Button Mapper is behaving much more stable now and hasn't caused any reboots yet.
[Android Q&A, Help & Troubleshooting] djvinniev77:
Yeah it's really strange with this device and what root methods were discovered by it.

While you're at it on modifying buttons, look into editing build.prop and change the longpress camera button from yes to no, so the camera button doesn't invoke the camera app when longpress.

On a different note, I have inquired with the folks at ulefone regarding the bluetooth issue, I definitely have mine disconnecting bluetooth hands free profile when a phone call is initiated or call received. Very annoying. I've logged a bug report and sent it over to them, hopefully that's what they're looking for and have the proper fix for our devices.
[Android Q&A, Help & Troubleshooting] sumec100:
You need to look at magisk log and twrp log, there is that they can not create a "virtual system" where they install systemless app as xposed or terminal and so on. This installed app works as if it were run directly on the system, but nothing changes in /system. It works similar to virtualbox in OS win or linux and so on. This does not work in Armor2.

As far as buttons are concerned, if they are not changed in / system / usr / keylaout, when pressed for a long time (more than 5 seconds), 100% will cause soft reboot even when the button mapper is changed to another function. Yes button mapper works reliably.
[Android Q&A, Help & Troubleshooting] alpsayin:
No reboot but I found this gem after pressing it for 5 seconds ? This is with Zello completely uninstalled but haven't deleted the SOS app left unconfigured. SOS also hasn't caused reboot. Still hasn't changed the config files or anything yet.
[Android Q&A, Help & Troubleshooting] djvinniev77:
i think somewhere in build prop it cites the buttons and maps FUNC1 and FUNC2 as ptt and sos, that's where the hard link is when long press is triggered, although I don't see the direct line, only for the one on camera.

Edit: found the item for PTT.

in build.prop, look for the line:

ro.zello.pressrecorder=yes

change it to

ro.zello.pressrecorder=no

PTT long press function gone!
[Android Q&A, Help & Troubleshooting] djvinniev77:
so I checked on my device, apparently for all devices BT is also enabled for location settings.. .

did a search on fixes for handsfree profile disconnects and found this:

https://forums.lenovo.com/t5/Moto-Z...nnecting-When-Making-Call/td-p/3558469/page/2

essentially on what I assume was an earlier version of android for this device, they may have had issues with BT disconnects when GPS kicks in to scan.

on my device, I went in to settings, location, tap on the 3 dot menu button at top right, select scanning. Disable Bluetooth Scanning.

Tested it with a BT headset and made/received phone calls, disconnect issue gone.

I don't know if it will help others but I would want the people who noted issues with their devices to check this out and see if it makes a difference.
[Android Q&A, Help & Troubleshooting] alpsayin:
What app/method do you use to change the build.prop? Got myself a random build.prop editor app and although it thinks it changed the values, I had no difference in button behaviour(5s PTT -> "please installing PTT app" and 5s camera -> well, camera app).
[Android Q&A, Help & Troubleshooting] djvinniev77:
So I have solid file explorer, when rooted allows you to browse the file system. You can then find the build.prop file under the system folder and from there use any built in text editor. In my case solid file explorer has its own.

ES file Explorer does a similar job. You just want to be able to make the changes on the file, save it and reboot device.
[Android Q&A, Help & Troubleshooting] Curtis_:
[MENTION=3837734]djvinniev77[/MENTION], [MENTION=5404196]sumec100[/MENTION] Thanx for the help!

When i tried to go flash the device with utility from needrom,

- set the SPflash to download

- reboot the device, and press volume up

- the laptop recognised the usb device

- it wrote that usb device has problems

- the phone booted to twrp

- download does not started (The Flash utility does not cared if th device is plugged in or not)

I tried it on several machnies with win10, and win 8.1 with installed, unsigned drivers - from several sources.

After that , i choosed Format All + Download as Sumec mentoined. The flash tool this time wrote that download is in progress!!! Aaand it succesfully flashed the phone!

I' still don't get it. Simple download showed that i have problem with the USB device, but format + download worked well !

Thank you for the patience

I'll go to root the phone and re-bind the buttons in the weekend
[Android Q&A, Help & Troubleshooting] djvinniev77:
Good job!!
[Android Q&A, Help & Troubleshooting] sumec100:
Congratulations. So I wrote it because I also got the phone into a mish-mash state, even if download only was done without error, the phone would not work, so format all. :)
[Android Q&A, Help & Troubleshooting] alpsayin:
Would you believe I found a solution to this on Amazon reviews? :) Install an app called Soundabout and force route audio to whatever device you wish. I still don't have that headphone icon but got music in my headphones and god oh god the sound quality is awful on this thing :D Wonder if it's the cable or the phone...
[Android Q&A, Help & Troubleshooting] djvinniev77:
lol! BT audio doesn't sound bad though.
[Android Q&A, Help & Troubleshooting] alpsayin:
Also, I was checking the settings in build.prop and found this "ro.agui.remove.wallpaper.menu". Set this to "no" to bring back our beloved wallpaper menu. This was annoying me heavily tbh.
[Android Q&A, Help & Troubleshooting] major_n:
my phone has gone unresponsive this morning. I've not tried to root or change anything from stock; any ideas, short of a) let the battery drain or b) open her up and unplug the battery? I can't find any way to reset the device...
[Android Q&A, Help & Troubleshooting] Curtis_:
Long pressing the power button usually do the trick (10-30 sec i don't remember correctly)

If it does not help, you have the other (a,b) options left
[Android Q&A, Help & Troubleshooting] Curtis_:
Camera Black screen

[MENTION=3837734]djvinniev77[/MENTION] , [MENTION=5404196]sumec100[/MENTION] Have you ever experienced black screen after start the camera?

I have done with the following:

- Restore to needrom's ram

- Root with magisk 14.0 (witch is work fine)

- replaced the button binding files with djvinniev's config

After that, i experiencing black screen when i start camera application

- I tried to download 3rd party camera app, shows the same. I tried with barecode scanner, result is still the same.

- I rewrote the button 212 in both files to CAMERA from grave, still the result the same. (props file is untouched)

- tried to install camrea enabler plugin under magisk. It said, that install is ok, but after reboot the plugin was not shown, also didn't find the persist.camera.HAL3.enabled=1 row in props

- I've tried adding persist.camera.HAL3.enabled=1 to props file manually (magisk camera enabler) witch also didn't worked

Have you any ideas how can i get the camera work?

(Should i flash and re-root the device with prev version of magisk?)
[Android Q&A, Help & Troubleshooting] djvinniev77:
I don't think the device works with HAL3, and the magisk I was using is the latest beta btw (14.3)

If you can I would start over and give it a shot with the current rom and beta magisk and see if you can get the same functionality that I did.

Hope it works!
[Android Q&A, Help & Troubleshooting] sfigas:
My armor 2 home button does not work after flashing S21_GQ3037LF2_Ulefone_V12_20171009, only the fingerprint works so I flashed the previus S21_GQ3037LF2_Ulefone_V12_20170926.

My only concern now is that I cannot root the device yet, any info ?
[Android Q&A, Help & Troubleshooting] MystikMan97130:
Hello all. Anyone can send me full method to unlock bootloader and flash TWRP please
[Android Q&A, Help & Troubleshooting] djvinniev77:
You should still be able to unlock boot loader then flash the proper twrp even on an older bundle. When in twrp, ensure you wipe device as the password is not known. Then flash either SuperSU or magisk to root it. All the files can be found from the first post (links to the relevant posts when we figured things out)

---------- Post added at 08:33 PM ---------- Previous post was at 08:21 PM ----------

Assuming you have all the drivers installed on a Windows PC to detect the device in adb and faatboot

Bootloader unlock:

Ensure you're in the device, go to setup, go to about, scroll to the build number and tap 7 times. It should tell you that you're now a developer and developer options are available. Go in there. Ensure OEM bootloader unlock is selected/on

Now reboot your device to fastboot mode

You can do it through command prompt and adb

adb reboot bootloader

Or power off device, reboot by holding volume up and pressing power. It should get into stock recovery (dead android). From here, hold down volume up and power for 2 seconds so you see the menu. Push vol down until you select reboot bootloader and press power to engage.

Once in fastboot mode, in command prompt on PC

fastboot oem unlock

Look at the small print on device screen. Hit vol up to say yes and process OEM unlock

Restart device when complete. It should process a device wipe.

With the unlocked bootloader, you can now use fastboot to flash the proper twrp and SuperSU or magisk - look at the first post to see the links to the relevant posts for these.
[Android Q&A, Help & Troubleshooting] MystikMan97130:
Thanks :D i have root now. I have Xposed too :eek: :D
[Android Q&A, Help & Troubleshooting] MystikMan97130:
Double post for screen :victory:
[Android Q&A, Help & Troubleshooting] djvinniev77:
Cool. You sure safety net passes? That broke for me last time.
[Android Q&A, Help & Troubleshooting] MystikMan97130:
Yes before flash xposed :) xposed can't pass safetynet now