yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] schroedingersdog:
Hi all,

Yep - I can confirm that turning off VoLTE makes for a BIG difference in battery life.

(A positive difference... ;) )

Cheers, Thomas
[Device Reviews and Information] schroedingersdog:
Rooting?

Hi Armor community, does someone know if the phone can be rooted using the MTK Droid Tools? I mean not "in theory" but in real life... :D. Has someone tried that and can confirm this?

Before you ask, yes: I tried to root mine, but the tools seem to not work correctly in my windows vm on linux. And I don't have a native windoze machine at hand right now. Was wondering if someone could confirm that it works ...or confirm that it won't work at least.

(Bootloader unlocked, developer options/usb debug active)

Cheers, Thomas
[Device Reviews and Information] megthebest:
is necessary to have stock rom from ulefone.. and after we will be able to build a TWRP to use for backup and root..
[Device Reviews and Information] MCGN:
i tried KingoRoot (rooted my Cubot S500) but no root for Armor.

the phone is clean and works fine... i dont need root necessarily.

But another question: Is it possible to configure the hardware-Home-button for screen-off?

Actually we can use it as screen-on and (whren using the phone) for the home-screen. whren in home-screen and click another one and the screen will go off... thats would be nice. ;)

Michael
[Device Reviews and Information] dannorth:
Received a new Armor yesterday, and turned it on to find the display is badly garbled. Any suggestions? Purchased from Gearbest which is shut down for the Chinese New Year at the moment, so no support there until Feb 2, probably.

https://www.youtube.com/watch?v=zMCYvcMtKi4

**Update: Gave it a little "percussive maintenance" on my desk; gentle love tap of the bottom back of the phone against the desk and POOF - screen is clear. For now. Clearly a hardware issue / loose connection.
[Device Reviews and Information] gocom:
looks like Feb. 10 we can get stock rom.. See http://forum.ulefone.com/thread-834-1-1.html
[Device Reviews and Information] arsalanksa:
I was selected 3 Rugged smartphones. Ulefone Armor, Blackview BV6000, and AGM A8. I checked the reviews and comparison. I saw many bad customers comments regarding the quality of camera, battery life and lower display resolution, therefore I ordered AGM A8 because of 5 Inch HD display, Android 7.0, 13MP HD camera, real huge battery capacity, and cheaper in term of price.

I believe that AGM A8 is the best value for money and looking forward to receiving my unit soon.
[Device Reviews and Information] beeker666:
Stock Rom Ulefone Armor

Link for Armor download Page:

ulefone.com/download/armor.html

and 2 Links for two versions of Armor Stock Rom

drive.google.com/drive/folders/0B8NC4kBpjQhYa3BDeGZ1QVhoajQ

drive.google.com/drive/folders/0B8NC4kBpjQhYV2RIdWhnblNYT3c

sorry for my english

To make TWRP please
[Device Reviews and Information] megthebest:
i will work on the TWRP soon
[Device Reviews and Information] beeker666:
thanks
[Device Reviews and Information] megthebest:
Warning: if you came from ROM 1 rev 1.0.6 and you flash 1.0.7 your Magnetometer, Gyro and Accelerometer don't work anymore .. so stay with 1.0.6 rom !

Here're TWRP checked and full working for Rom 1 and Rom 2:

TWRP 3.0.2-1 for ROM1 20161209

https://mega.nz/#!2AE1yAQZ!Jr3u9uEalaejW4zSyWhqB6Kvz65wqFCUknHMg_90igs

TWRP 3.0.2-1 for ROM2 20161214 (3.0)

https://mega.nz/#!KZclBZga!5Jn6av2VF0AapKomCOvMm43ahpRDSPTuR-h71OTqJsg

The two TWRP are not interchangeable.

Use scatter MT6753_Android_ScatterTWRP inside archives to Flash TWRP and MT6753_Android_Scatter to flash Stock Revovery if you need (both provided).

When Enter in TWRP at boot (Device OFF, Power and VOL+ same time, choose Recovery with Vol- and wait ) please flash supersu.zip to have Root and no issue with BootLoop

Enjoy and i appreciate thanks if i help you!

Regards
[Device Reviews and Information] schroedingersdog:
[MENTION=5952124]megthebest[/MENTION] Thanks a lot!

I have rooted my Armor successfully, using the stuff at needrom.

I also left some hints at Ulefone forum for escaping bootloop in case one has problems... and that it is generally a good idea to FIRST PUT SUPERSU ON THE SD CARD before installing and rebooting to TWRP. ;)

Others: With root, we can at least finally use apps like PhoneProfilesPlus, FasterGPS, Titanium BackupRoot, ... however, if you ever used Cyanogenmod, you will still feel lost in matters of tweaks and customzation. Hopefully someone will be working on a Cyanogen port that supports the phone and SOS hardkeys. :)

Cheers, Thomas
[Device Reviews and Information] uzairrizwan007:
battery charging problem

My experience is very bad, what they said what I got, can’t believe. I am here to warn you to not believe what they are showing you because it have very low screen resolution, bad camera quality, battery capacity is not actual, very slow charging and dropping charge very fast, not all sensors worked, poor sound quality and no after sale support. Now a day i am using AGM A8 and I am very satisfied with performance and quality of everything.
[Device Reviews and Information] megthebest:
Stop spamming in this thread only to advertise your device. Write in the correct thread of your device and there you can make it your idol.
[Device Reviews and Information] zonatar:
I rooted my ulefone and installed xposed + gravity box, i change the sos key to use it as the power button and more and more fuction!

Now i really enjoy my new phone!
[Device Reviews and Information] MCGN:
Big Thanks, working fine!

Michael
[Device Reviews and Information] jarknar:
GPS

Does the rooting actually help with the bad GPS Signal ? Can the apps with root access do more to improve the Signal than regular apps ?
[Device Reviews and Information] maback:
Can anyone test if this phone passes safetynet before it is rooted? I've tried everything and cannot get Android Pay to work, but I've already rooted.
[Device Reviews and Information] 1248:
Deleted

---------- Post added at 05:13 AM ---------- Previous post was at 05:06 AM ----------

Try GPS Locker.

It won't improve weak signal problems but it locks the GPS up much faster initially and when exiting a tunnel in a car and improves navigation programs (Waze, etc).
[Device Reviews and Information] Ridbark:
Hello,

I am trying to update the software with version 2 to install TWRP and SuperSu.

I download drivers and flash tool from Ulefone website, I install drivers, connect my phone (which is off). Windows 7 show me a new device (with a port COMx, where x is a number), but 1 second after, this new device disapear to show me a device called "USB MTP", not recognized by my Windows 7 ... And the flash tool doesn't show any device to flash ...

Can you tell me how to flash my device with version 1 or 2, to flash after the TWRP ??

Ridbark
[Device Reviews and Information] PatrickFutch:
Battery issue

First, thanks to everyone on here smart enough to help us simple folks root, install recovery and everything else. I'm very grateful. To the battery issues and the guy accused of spam, I have a battery issue with mine as well (multiple apps showing the size as 1000mAh instead of the advertised 3500mAh). I like almost everything about this device, so I'm hoping mine is just a defect and I can return it for another. But if any one can please check if theirs is the same small size? When I asked Ulephone in an email, they responded with "it will show bigger in few days". That didnt give me a lot of hope.
[Device Reviews and Information] megthebest:
what App said doesn't matter..

App are not able to check correctly battery capacity.

only USB power meter like this can be used to have reliable results:
[Device Reviews and Information] PatrickFutch:
mAh usb

That's a useful tool. Have you, or anyone on the thread tried it?
[Device Reviews and Information] megthebest:
yes, many times.. on the Armor battery, i have measured a capacity around 3100mAh ..lower than specs, but enough for a full day of work..

Unfrtunately Mediatek devices are poor managed in terms of battery drain and cpu balance in deep sleep, so the battery last less than qalcomm cpu..
[Device Reviews and Information] bertrandchan:
root feedback

Hello,

I have rooted the ulefone Armor with some difficulties.

The only twrp rom which worked is the needrom custom rom 'TWRP Recovery 3.0.3-0' developed by hanuma50.

Neither the xda roms and other needrom roms worked with me. The phone stucked on 'ulefone' picture and didn't catch the next step.

I am not keen enough to explain in detail what happened when I rooted the phone, it is just a feedback.

I noted another difficulty to sync the 'contact' app with an sync app 'davdroid'.

I never got this kind of problem before with other chinese phones (homtom, huawei ...).

I resolved the problem with another specific 'card dav sync' sync app cardDAV-Sync.

The DAVDROID app is ok for the calendar.

I bought this phone as it seems strong, after I dropped my 2 last phones !

Except these problems, it is a plesant and very fast phone for my common use.
[Device Reviews and Information] maback:
Anyone have a flashable zip for TWRP of the latest update from Ulefone?
[Device Reviews and Information] HMME:
hi there,

i need the update (GQ3268AH_Ulefone_V1.0.9_20170406) as a zip to.

is it possible?

michael
[Device Reviews and Information] bootsplash:
I have it installed on my armor by wifi automated process... where is the zip file on the internal memory i cant find it?
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
Hi,

Apologies in advance if I'm covering old ground.

I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.

the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.

I've tried different roms, different usb ports and different versions of activesync all with the same result.

Any help on this would be great and hopefully I haven't 'bricked' the unit.

Cheers

Duncan
[MDA III, XDA III, PDA2k, 9090 ROM Development] kerio:
Do you have PH20A2 or PH20B device?

mtty utility can be found using search button:)
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
It's a PH20B.

I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.

A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.

Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.

Cheers Duncan
[MDA III, XDA III, PDA2k, 9090 ROM Development] meehaa:
try reflashing
[MDA III, XDA III, PDA2k, 9090 ROM Development] kerio:
You should know how to use search - however here is the link

http://xdaforums.com/showthread.php?t=348030&highlight=mtty

(Is that hard to put "mtty" in the search field and set BA section only?:( )
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
Further update:

Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.

Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....

I have used the wiki and the search funstion and I seem to be the first with this situation.

Soft Reset - Nothing

Hard Reset - Nothing

Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.

I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.

I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.

Any help would be great..... please??
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
[off topic]

no need for apologies...

we started once like you... some are far worse...

knowing one part and boasting with air on their heads...

since you managed to explain yourself on your first post.

knowing what to search (E.G. MTTY 1.42.rar)

you definitely searched the forum before you posted AND

you stated that the links are not working... that proves it.

we are the one who is sorry because some others think

that they are high and mighty, it sometimes blurs the opinion making.

i dont like opinionated people because i admit that am one too...:D sometimes...

but that doesnt mean i hate them...;)

[on-topic]

you never told us what happened when you tried the mtty procedure.

is your last post the result of your mtty experience?

please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
SilverSamurai,

Thanks for the quick response.

After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.

I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.

Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).

USB>set 14 0

HTCST ÚÈÒHTCEUSB>task 28

DOC_format_HW+

DOCInfoTableinitHW+

Binary0:dwSize=80000

BINFS0:dwSize=0

FAT0:dwSize=1000000

FAT1:dwSize=2BA0000

All:dwSize=3C20000

USB>task 0

USB>

It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.

I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.

I think that's about it. If you need any more info let me know.

Many thanks

Duncan.
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
let's relist the things you did.

since i dont want to experiment with my sole BA...

i tried to search for solution...

and with some of my computer instincts i came up with this suggestion...

try this command before "task 28"

"task 7 0" <-- this is the "Do flash ROM lock/unlock" command

"task 2a" <-- fix bad blocks on MFG bootloader and Storage

then try to reflash your BA.

my sources one | two

although it's not BA but i think mtty commands are generic.

it's worth a try.
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
SS,

Still no joy, it's exactly as it was before.

Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://xdaforums.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.

I think I may have got it beyond the point of return.

I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
awww... im sorry to hear that.

but dont lose hope.

i'll try to read some more and search for solutions.

and i hope someone with the same problem as

yours that had their BA fixed comes to the foreground.

[off topic]

hmm... come to think of it... we're both Marvel SuperVillains ;)
[MDA III, XDA III, PDA2k, 9090 ROM Development] anilkaparthi:
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)

2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)

kill two processes rapimgr.exe and wcescomm.exe

3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.

4. Run mtty (from downloaded) Choose WCEUSBSH001

5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.

6. type "task 28" to get your device formatted

7. type "task 0" to ask your device reboot

8. take the device out of the cradle, and manually reset it if it does not do that already.
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
i think he did all of those already,

that's why i posted this in response to his mtty experience.

wouldnt hurt to try it again though. :D
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
A bit more info:

I tried the mtty solution again but still the same result.

I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.

What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.

I'll post my results shortly.
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.

The hunt coninues....
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
Yet more developments.

As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following

“d2s 80000000 02000000“

“d2s 60000000 00300000 sd a“

“d2s 70000000 01080000 sd a“

The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result

USB>d2s 70000000 01080000 sd a

SD:Waiting for card insert.........

CMD3 for SD, it's OK, ready to get RCA from response.

SD:Detected one card

SD:ready for transfer OK

pc->drive.total_lba=1E8000

pc->drive.num_heads=0

pc->drive.sec_p_track=0

pc->drive.num_cylinders=0

pc->drive.block_size=200

pc->drive.features=0

pc->drive.RCA=B368

pc->drive.drv_type=40000000

pc->drive.securedAreaSize=0

pc->drive.securityDrv=0

pc->drive.busWidth=1

pc->drive.erasedSize=0

Total card size=3D000000

DOCInfoTableinitHW+

Binary0:dwSize=80000

BINFS0:dwSize=0

FAT0:dwSize=1000000

FAT1:dwSize=2BA0000

All:dwSize=3C20000

DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.

DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.

*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.

*****************************************************************dwCheckSum of Storage=95609D16

cSectionNum=2

psImageSectionInfo[cSectionNum].dwCheckSum=0

psImageSectionInfo[cSectionNum].dwLength=1080000

Stored image of SD/MMC card checksum error!

Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
what was "task 2a"'s result?

i think that's the chkdsk option of mtty.

we're dissecting the innards of the bootloader. :D

little by little as we go along the way...

im learning something, i hope you can find the fix for your problem.
[MDA III, XDA III, PDA2k, 9090 ROM Development] omegared:
SilverSamurai,

Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.

I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.
[MDA III, XDA III, PDA2k, 9090 ROM Development] SilverSamurai:
it was sad to hear/read that.

anyways. at least we tried to revive it. but dont throw it away.

maybe someday there will be ways how to ressurect your BA.

Happy Computing! err... Mobile Computing!

:D
[Galaxy Tab 3 Q&A, Help & Troubleshooting] mon0theist:
Hello, sorry if this is the wrong place for this post. I was just curious if there are any ROMs here that will work with mobile data. So far I've tried AICP and CM13 but they both say "no SIM card". I'm on Sprint so I'm pretty sure I don't even have a SIM card. I was using a different custom KitKat ROM before that was basically the same as TouchWiz but I can't remember what it was specifically, but mobile data worked fine. I wanted to also try SlimROM but it appears the download link in the thread here is broken.

EDIT:

I have the SM-T217S. I'm looking for an AOSP ROM that works with mobile data as well as WiFi, rather than just WiFi only
[Galaxy Tab 3 Q&A, Help & Troubleshooting] RealWelder:
Which model? There are a few.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] mon0theist:
Sorry, SM-T217S
[Magisk] Setialpha:
As many of you know Nintendo's first mobile app Miitomo crashes on most custom kernels and ROMs. Since version 1.2.0 Miitomo does no longer check for root, but it checks the value of 'ro.debuggable'. If 'ro.debuggable' is set to '1' by the kernel (in /default.prop), Miitomo will crash.

So what this Module does, is to set 'ro.debuggable' to '0', using the shiny new resetprop introduced in Magisk v9. This Magisk Module is meant for people who can't use Xposed or don't want to.

For Xposed users, check my SecurityBypasser Xposed Module.

Tested on Lux (Moto X Play).

Download and Code over at github.
[Magisk] Link_of_Hyrule:
Can you make another module that sets ro.build.type=user in build.props?
[Magisk] Setialpha:
Should not be a problem. Any particular reason?
[Magisk] Link_of_Hyrule:
Because Android Wear won't work if it's userdebug.

EDIT: I was able to make a script based on an existing script for something else thanks for your reply. This is the script I made if anyone needs it.
[Magisk] Link_of_Hyrule:
[MENTION=4187311]Setialpha[/MENTION] This still works great and you should get it put on the Magisk module repo.
[Magisk] jhedfors:
+1
[Magisk] Brentboy:
I can't install this on magisk with the install module feature. Does it work through twrp?
[Magisk] Setialpha:
That's likely an issue with MagiskManager, flashing through TWRP will work.