yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] deinfreund:
The problem is that I can't actually boot into twrp. It's the same on Linux and Windows for me:

user@brieftop /media/user/Subspace/Temp/flashing $ fastboot oem unlock
...
(bootloader) Start unlock flow

OKAY [ 10.610s]
finished. total time: 10.610s
user@brieftop /media/user/Subspace/Temp/flashing $ sudo fastboot flash recovery twrp-3.1.1-0en-20180212-Armor_2\[TuksOID\]/recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (15218 KB)...
OKAY [ 0.444s]
writing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.663s
user@brieftop /media/user/Subspace/Temp/flashing $ sudo fastboot boot twrp-3.1.1-0en-20180212-Armor_2\[TuksOID\]/recovery.img
downloading 'boot.img'...
OKAY [ 0.444s]
booting...
OKAY [ 0.046s]
finished. total time: 0.490s

After executing this and waiting a few seconds, the phone's screen turns off and it reboots continuously. Even though I directly run "fastboot boot" I never see the recovery. From there on I can't seem to do anything but use SP flash tool to revert to stock.
[Android Q&A, Help & Troubleshooting] alpsayin:
Sounds like a joke, but try renaming the img files to "recovery.img" only and try to run the command from the TUKSOID directory itself as below:

And also, try and use a windows dude. As much as I like linux, it's never reliable for these things.

user@brieftop /media/user/Subspace/Temp/flashing $ sudo fastboot flash recovery recovery.img
user@brieftop /media/user/Subspace/Temp/flashing $ sudo fastboot boot recovery.img
[Android Q&A, Help & Troubleshooting] deinfreund:
That's actually what I tried first, after it didn't work I switched to Linux.

D:\Temp\flashing\twrp-3.1.1-0en-20180212-Armor_2[TuksOID]>adb reboot bootloader

D:\Temp\flashing\twrp-3.1.1-0en-20180212-Armor_2[TuksOID]>fastboot flashing unlock
(bootloader) Start unlock flow

OKAY [ 5.332s]
Finished. Total time: 5.333s

D:\Temp\flashing\twrp-3.1.1-0en-20180212-Armor_2[TuksOID]>fastboot flash recovery recovery.img
Sending 'recovery' (15218 KB) OKAY [ 0.459s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 0.695s

D:\Temp\flashing\twrp-3.1.1-0en-20180212-Armor_2[TuksOID]>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.432s]
booting OKAY [ 0.053s]
Finished. Total time: 0.495s

D:\Temp\flashing\twrp-3.1.1-0en-20180212-Armor_2[TuksOID]>bootloop!

I've noticed something else though. I do the flashing unlock via fastboot, then reboot the phone and wait for it to erase, go back into fastboot and flash twrp. Now I still can't use the "fastboot boot" command, but I can reboot the phone just fine without it being bootlooped. I simply can't enter the recovery - whenever I try to boot into recovery it just gives me a black screen and reboots. It's as if the recovery image was corrupt or something, but this happens with both Jemmini's and Tuksoid's.
[Android Q&A, Help & Troubleshooting] Sebastl:
Are you flashing the recovery everytime before trying to boot it ?

If yes, try SP-Flashing stock, and as soon as this works and you ve got your system up and running and the bootloader is unlocked and adb debugging activated and working...

Now reboot into fastboot with "adb reboot bootloader" and then try directly to "fastboot boot recovery.img". I recommend TuksOids one
[Android Q&A, Help & Troubleshooting] deinfreund:
I've factory reset it at least a dozen times now. I've tried your suggestion with both Jemmini's and Tuksoid's twrp. I've tried doing flashing unlock, then reboot, then boot recovery. I've tried just booting recovery directly after unlock. I've tried rebooting after unlock, flashing recovery, rebooting, booting recovery. None of them got the recovery to launch. If I read the previous posts in this thread though, some of these things should've bootlooped my device while they didn't (e.g. flashing recovery then rebooting).

Could it be, that in some way, I have a different device which causes the twrp to not work? Instead of factory resetting, I've tried to reset it to different versions of the factory ROM that I found online. The standard ROM that you can find on the ulefone website is 20180531_s21v57c2k_gq_fp and works just fine. As an alternative I've tried 20171009_s21v57c2k_gq_fp which led to a white screen directly when turning the phone on and no boot. This image should work just fine if I had the same phone as you (it is referenced a few times in this thread as the latest ROM). I've also found another ROM with the date 20180807 which does work just fine but where the twrp recovery doesn't work either. Why is it that the older ROM doesn't work? Could it have something to do with the recovery not working?
[Android Q&A, Help & Troubleshooting] bvm127:
Hi, I've got the same issue on my new armor 2. Any old ROM doesn't work at all and goes to white/black stripes screen and 20180531_s21v57c2k_gq_fp ROM version works perfectly.

TWRP booting into black screen after "fastboot boot recovery.img" command.

It seems like the latest devices armor2 differ from earlier. I've got ROOT with boot.img patched in Magisk and it works good. Another thing is how to install TWRP at last. All methods discribed are not working on my device.
[Android Q&A, Help & Troubleshooting] Sebastl:
I never really used it except for magisk playing and as potential follow up as soon as my "normal" phone dies. Actually a brand new device.

Last week ago (i guess hehe) it ran out of battery and guess what when i grabbed it yesterday: no charging and no starts anymore ;)
[Android Q&A, Help & Troubleshooting] deinfreund:
Could you describe how exactly you got it rooted? Did you use SPFlashTool to flash the boot.img from #483?
[Android Q&A, Help & Troubleshooting] bvm127:
Yes, boot.img was patched with Magisk on device and flashed with SPFlashTool. That's it.
[Android Q&A, Help & Troubleshooting] dm396:
Serious security problem with armor 2

Hey,

I recently purchased this phone. I kinda hate it, but well I am stuck with it now.

But the problem that I have noticed.... When the phone is locked, if I push the camera button, it goes to camera function (like it is supposed to), but then it is unlocked. No fingerprint, no code, just plain unlocked and fully accessible.

This seems like an absurdly easy way to unlock a phone without a code. has anyone else noticed this problem?

Dipak
[Android Q&A, Help & Troubleshooting] hyegeek:
That is now how things work on mine. What version are you running? I'm on S21_GQ3037LF2_Ulefone_V12_20171009 (according to status on the phone). I did have various security issues with a previous version.
[Android Q&A, Help & Troubleshooting] djvinniev77:
Hey [MENTION=2580755]zagi988[/MENTION], do you have the original zip file for this update or know of a spot aside from needrom to grab it? I got my device back from family member and would like to test out stuff again.

From stock, I flashed the new TWRP and got that going but could not get my previous rom nor your current rom installed back on device. Just gets it to boot back up to TWRP after successful flash. I think I need the original boot.img and I don't have that.

Regardless I would like to see the new rom and how it works well.

Thanks

EDIT: Nevermind, I'm grabbing files from here:

https://www.getdroidtips.com/nougat-firmware-ulefone-armor-2/

Seems to have the latest firmware, surprise surprise!

I may just re-upload these to my MEGA drive when I test everything out.
[Android Q&A, Help & Troubleshooting] enzovic:
Hey djvinniev77

I installed the latest version thanks to your link, and for the first time since I have this phone I wanted to install Term Win Recovery, but after I install it asks for password for decrypting Data partition.

If I reformat Data Partition I get access over it.

But after that silence... It's only trying to boot to recovery

Can't boot into System

How can I work this out?
[Android Q&A, Help & Troubleshooting] djvinniev77:
I had this too. I had to take my device and load the original software using the mediatek flash tool. Once I had the software loaded, reboot into fastboot, loaded twrp recovery, restarted again into twrp, hit cancel on entering password to decrypt. From there the data on device is unreadable and had TWRP perform a wipe (just standard one) - after reboot it was fine.

I didn't do the advanced wipe, just standard one. It seemed to clear the encryption, and everything was fine. Hope it works for you.
[Android Q&A, Help & Troubleshooting] michael205:
proximity sensor

Hi, I have a problem with proximity sensor. When i try to calibrate it doesn't save values.

I tried *#*#3646633#*#* but also no luck in there. Any idea what can be wrong with it ?

When i calibrate it i get min value ~750, and max ~29000.
[Android Q&A, Help & Troubleshooting] alpsayin:
I have 1 or 2 9h screen protectors. Pm me if you're in UK and I'll post them to you for free.
[Android Q&A, Help & Troubleshooting] TuksOID:
You need to patch the boot partition. Then, your system willl boot properly. How to do this?

Memory card with Magisk.

Install Magisk.

Magisk will do the work.

Each time you think about making the Wipe data, you will need to install magisk. Then, previously, run the Magisk uninstaller, so you can reinstall, again, with no problems. You will avoid much work.

Have in mind:

1. that the TWRP I compiled is with disabled data encryption. With TWRP in RU every factory restart will encrypt the userdata partition, and you will lose access through TWRP.

2. that when installing xposed you lose SafetyNet.

3. if you do not run Magisk unintaller before you do Wipe data you will have to flash stock "system.img" and stock "boot.img" with SP_Flash_Tool and run fastboot erase userdata. It's simple, but it's extra work.
[Android Q&A, Help & Troubleshooting] gloschkid:
I am unable to load TWRP after magisk updated to v18

I cannot for the life of me get my Armor 2 to load TWRP after I re-flashed firmware with sp flash tools (because the recent magisk update bricked my phone, however it runs the same version when patched and flashed using flash tools). It has loaded TWRP in the past ,and I do currently have root access via Magisk installed with a patched boot.img. My current kernel is version 4.4.15 tue aug 7 cst 2018 and my current build is S21_GQ3037LF2_Ulefone_V12_20180528. I miss having the pixel launcher and Viper4Android installed. Is it possible my kernel or build number updated on their own?
[Android Q&A, Help & Troubleshooting] TuksOID:
if you have reflashed using the sp flash tool, you should have just marked the system and boot partitions.

but from the symptoms you described, I believe you have performed a complete reflash. so recovery has returned to the stock version.

grab the file "twrp3110en-Armor2_20180212.img" rename to "recovery.img" replace inside the firmware folder and reflash through sp flash tool again. Reflash boot, recovery and system only.

After that, start in download mode, run the "fastboot erase userdata" command (due to the full reflash you've made, you must have already lost all the data.). But even so, to reinforce the care, when executing the command, surely you will lose all your data.

Go to TWRP and redo the entire root process -> busybox -> magisk 16.7.

Remember: always upgrade magisk framework through magisk manager.
[Android Q&A, Help & Troubleshooting] gloschkid:
i will try later on tonight and post back with results. thank you.

---------- Post added at 02:46 AM ---------- Previous post was at 02:10 AM ----------

after doing this i am still unable to boot TWRP trying any method to boot recovery just makes the screen black for about 3 seconds then it reboots it is also bootlooping after doing this i've never had this phone bootloop before. i also have reset the emmc when this originally happened i should have included this in the first post .
[Android Q&A, Help & Troubleshooting] yodonlicenavigator:
ahh, this orange state error is impossibnle to overcome and i will never get twrp to root my phone!
[Android Q&A, Help & Troubleshooting] michael205:
https://xdaforums.com/showpost.php?p=74429860&postcount=68

For some reason after every time that i use "fastboot flashing lock" command my phone gets bricked and i have to use sp flash tool to get it back to life.

What am i doing wrong ?

************

After some time of tring to get it to work i'm unable to unlock bootloader.

Any idea what has just happened and how to fix it ?

Ok, This one i fixed my self. In developers option there is this unlock oem thing. Before i didn't have to unlock it. It just worked....
[Android Q&A, Help & Troubleshooting] michael205:
No one realy knows what's going on ?

P.S.

Does anyone knows if it's possible to port android 7.1.2 to our devices ?

It's not a big leap but would be nice :P
[Android Q&A, Help & Troubleshooting] andre_ggm:
Does anyone know if there is any team willing to update our phone, since this does not happen by the manufacturer?
[Android Q&A, Help & Troubleshooting] michael205:
Doogee y7 plus i very alike armor 2. Is there anyone that can tell me if it's possible to port it to our device ?

https://www.priceboon.com/product/doogee-y7-plus/

https://www.doogee.cc/detail/y-series_y7-plus/147
[Android Q&A, Help & Troubleshooting] michael205:
I need help :/ When i flash stock rom some of the apps are broken. They just stop working right out of the box.

I did format + update to get everything ... stock :)

When i install through twrp any other rom i get bootloop or sometimes i do get to installation screen but usually it break right away.

Any idea what else can be done ?

P.S. I have flashed older rom from 2017 and the same thing happens. When i tried to update rom through Wireless update i get error about certificate or something...

Can someone make whole buckup of their rom in twrp i upload it ? Maybe that would help me with this :/

P.S.2 Ok, when i run applications before any updates come along everything works just fine , but after... crushes many aps, gmail, my bank app and few other that i use. Something with security ?

P.S.3

No hope. I have done everything that i could from this forum. Last option is backup of one of you guys .. I don't know why i didn't make one , never expected that something like this would happen.. :/

Pls HELP :)
[Android Q&A, Help & Troubleshooting] michael205:
Anyone ?
[Android Q&A, Help & Troubleshooting] zagi988:
With newest Magisk it is possible to install modules again.
[Android Q&A, Help & Troubleshooting] Sebastl:
Thanks for mentioning. Totally forgot about it as the changes happened back in February.

Magisks author dropped the usage of img files via loopback (see commit 1321f097 ) and therefore the faulty kernel implementation doesnt matter anymore.
[Android Q&A, Help & Troubleshooting] zagi988:
Well, mine is kindda history now. Screen stopped working after being in water... I've had it only for a year, gonna see how expensive the repair is and if it's too expensive I'll just buy something else...
[Android Q&A, Help & Troubleshooting] zagi988:
If anyone needs a new front frame, I bought it and it looks like my MBO died so I have no use of it.

Completely new.

https://www.ebay.com/itm/233320104899
[Android Q&A, Help & Troubleshooting] zagi988:
OK, back to this phone. It required update to get it the screen working.

Now I have newest ROM and recovery is not working with it anymore.

Does anyone have any idea how to make recovery to work with newest ROM?
[Android Q&A, Help & Troubleshooting] enzovic:
Hi! Is anyone able to Update this phone to android 9?
[Android Q&A, Help & Troubleshooting] rockcelulares:
hola, tengo el mismo problema

How did you solve it?

---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------

after flashing, the imei stayed in 11111111 ....

any solution? please?
[Android Q&A, Help & Troubleshooting] jamrat:
New Armor 2 phones

It looks like they have disabled the recovery menu on the new phones best I can tell. I can flash TWRP but I can't boot to it. Neither can I boot to the stock recovery. I can get the menu but it wont allow me to select recovery or normal, only fastboot. I tried different roms, but they just tried to burn the screen out. I had to go back to using official Armor 2 tool S21_GQ3037LF2_Ulefone_V12_20180528（2018.08.07）.zip rom.

I really hate the way you can spend hundreds of $$ for a phone and they lock you out like you don't own it.

This is just FYI for anyone buying a new one of these and expecting to root it.
[Android Q&A, Help & Troubleshooting] jordan87:
Hello

Is it possible to use MirrorLink in car wit this phone? My cousin has official software on it and it looks like currently it is not supporting this feature.

Thanks
[Android Q&A, Help & Troubleshooting] michael205:
How fast should data transfer be over wi-fi 5ghz ? I get only 50Mb/s with 300Mb/s internet connetion (my router can transfer up to 900Mb/s over 5GHz)
[Android Q&A, Help & Troubleshooting] alpsayin:
On another note after updating to 20170910 I noticed that I now have some sort of on-body-detection and automatic unlocking going on (I mean bypassing of fingerprint and pattern and everything). Google's on-body-detection is off, and Smart Lock is not even enabled in Trust Agents. I'm not yet sure if it's one of my apps or if it's the ROM. It's really annoying because once I pull it out of my pocket, I push the power button and I find myself turning the phone off rather than on. On another scenario, I find myself tapping all sorts of things on the screen while pulling it out of my pocket because it's already unlocked.

I've got below which has accessibility access:

Microsoft Launcher, Button Mapper, Lastpass, Next Lockscreen, Greenify, Airdroid, More Shortcuts

I've got below as device admins:

Airdroid, button mapper, find my device, greenify, microsoft launcher, more shortcuts, Next lockscreen, OsmAnd, Sleep as android, teamviewer host
[Android Q&A, Help & Troubleshooting] enzovic:
Try uninstalling next Lockscreen.

I have no problem with stock Lockscreen with fingerprint and pin on the latest ROM.
[Android Q&A, Help & Troubleshooting] alpsayin:
Well, this actually started before next lock screen. If anything it's the reason I've put Next. I'll try getting rid of Microsoft launcher to see what happens.
[Android Q&A, Help & Troubleshooting] sumec100:
Reinstall ROM 2017/10/09 via flashtool, if the phone boots OK, skew this procedure to install TWRP, root and xposed: https://xdaforums.com/android/help/doogee-s60-twrp-root-xposed-t3677775/page2 , The Doogee s60 is the HW as Ulefone Armor 2 (except for display 5.2 ", battery 5200mA and rear camera 24Mpx) for this reason" do not use Doogee S60 rom "but only for Armor 2 rom , the Armor 2 recovery is as good as the S60.

Do not try it on Armor 2 that TWRP from BV8000 does not work, the procedure I have put the link upwards also works bootable twrp but does not display any icons so it can not install root and so on. (probably because of the screen resolution). Fixed via flashtool "Format all + Download", the phone remains as new and works smoothly.
[Android Q&A, Help & Troubleshooting] crusht:
Is 5h SOT normal for such a big battery, do you think something is draining it? Is the screen wasting most of it? Maybe put a picture of battery screen and SOT screen? This may be a deal breaker for me.... Thanks.
[Android Q&A, Help & Troubleshooting] frankcilo:
Good smartphone, but battery....
[Android Q&A, Help & Troubleshooting] eazrael:
How long did it take them for an answer? I mailed them on saturday and received on monday the confirmation that the mail was successfully delivered to their mail server. Quite discouraging when it takes 2 days to deliver a mail.

Has anybody else issues with the headphone icon flickering in the status bar? Happens randomly when no headphone is plugged in. Audio is not working at all when this happens.

Small demonstration: https://www.youtube.com/watch?v=0b75aBNPHGg

The difference between V12 and V13 firmware is also weird. I got the V13 firmware on my phone, which is older than the V12 from needrom. Haven't got any update yet.

Battery Life is okay for me, but need to test it a little more. Ran the PCMark battery test and got 10hours with automatic display brightness in a dark room.
[Android Q&A, Help & Troubleshooting] djvinniev77:
Yeah I think it's the chipset... I do have everything turned on and nothing is limited. I don't have another device with the same chipset to check, but vs a device with Snapdragon 625, the sd device is much better on battery vs this one.
[Android Q&A, Help & Troubleshooting] michael205:
In cpu-z i can see cpu load 80 - 100% all the time. In airplane mode 60-70 %.

I don't know what causes that but that's the reason why we get so short battery life :/
[Android Q&A, Help & Troubleshooting] eazrael:
Not sure if I can confirm this.

User 32%, System 20%, IOW 0%, IRQ 0%
User 333 + Nice 2 + Sys 214 + Idle 477 + IOW 0 + IRQ 0 + SIRQ 0 = 1026

PID USER PR NI CPU% S #THR VSS RSS PCY Name
1172 system 20 0 18% S 136 2428708K 135112K fg system_server
356 system 12 -8 12% R 32 552864K 10092K fg /system/bin/surfaceflinger
1363 u0_a55 20 0 12% S 54 1850024K 78104K fg com.google.android.inputmethod.latin
233 root 0 -20 2% S 1 0K 0K fg hps_main
1421 u0_a27 20 0 2% S 50 2868340K 126960K fg com.android.systemui
5742 shell 20 0 1% R 1 9088K 3104K fg top
8 root 20 0 1% S 1 0K 0K fg rcu_sched

Display is off, system ist "idle". 52% CPU.

But honestly I cannot interpret these values. I have no experience with these ARM secondary cores and how this variant of top calculates the load and what the current CPU power states are.
[Android Q&A, Help & Troubleshooting] michael205:
Did you root your device? How ?
[Android Q&A, Help & Troubleshooting] sumec100:
I do not have root, so BV8000 twrp does not work well on Armor 2.
[Android Q&A, Help & Troubleshooting] djvinniev77:
correct, yes unfortunately even by just taking the recovery image as posted for this device, it doesn't boot into recovery. Even if you try and boot recovery temporarily, just doesn't boot.

I've been looking into trying to compile TWRP from source for this device, already unlocked the boot loader (bye bye warranty) and found all the usual things "broken" on it (android pay broke, Netflix doesn't download from play store)

so if anyone has any tips (yes I know I've read this post already https://xdaforums.com/showthread.php?p=32965365#post32965365 - still can't figure it out.. lol)
[Android Q&A, Help & Troubleshooting] KAding:
I am having an issue with NFC on my Armor 2. I am unable to write more than 254 bytes using NFC. I am not sure if this has anything to do with the specific chip or the drivers. If you have the proper NTAG216 chip you can try this out using something like the 'NFC tools' app.

I really have no idea what could be causing this as it works fine on other devices. I'll try to update the ROM to see if that fixes it.
[Android Q&A, Help & Troubleshooting] sumec100:
Hello, how did you get it, both of my sim work normally, thank you for your help.
[Android Q&A, Help & Troubleshooting] tmiland:
Howdy!

Just received an update! :)

See attachement.
[Android Q&A, Help & Troubleshooting] crusht:
Pls let us know if it makes the SOT any better.
[Android Q&A, Help & Troubleshooting] tmiland:
SOT? :confused:
[Android Q&A, Help & Troubleshooting] crusht:
Screen on time