> Important!

We strongly recommend to familiarize withRules section "Android - devices"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Ramos MOS3 - Discussion | Smartphone 5.5 "



Rep: (2)
DiscussionRamos MOS3
PictureRamos MOS3
Discussion �


Specifications
Manufacturer: Ramos
Band Mode: 2SIM / Dual-Bands
Battery Type: Non-removable
Display Resolution: 1920x1080
Release Date: 2016
CPU: MTK 6755V-E
Camera: 13.0 MP (Aperture 2.8 ) Frontal: 8.0 MP.
Dimensions: 154.6x76.2x8.0mm
Battery capacity: 4100mAh
RAM: 4
Built-in memory: 32 GB
Screen diagonal: 5.5
Charging Port: usb type-c

Photo
Attached Image
Attached Image
Attached Image


Useful

Drivers and Utilities

TWRP
The mini jack connector does not work, maybe it's in the firmware.
A very bad aperture 2.8 of a good camera, if not for it, the photos would be much better.
Firmware, and tools, and tutorial



There is no curator in the subject. For questions about filling the caps, please contact the section moderators via the buttonPictureunder the messages to which you want to add links.

Post has been editedMgalex - 09.04.19, 23:29
Reason for editing: Global firmware for FlashTool



Rep: (-1)
I present to you, the "global" for our device (multilingual, the one from the seller on Ali)
It is sewn through SP FlashTool, bundled twrp. In any case, the root will have to be done - the on-screen navbar is displayed by adding a line to build.prop
qemu.hw.mainkeys = 0
Firmware
https: //drive.google.c...HFoiOKErBCkKFNkGD8VCv/
Screenshots
https: //drive.google.c..._YPgo05btIAN8y1qNMV7dR

If anyone has flashed format + download, imei are poured using Maui META

Post has been editedMgalex - 09.04.19, 23:29
Reason for editing: In the header



Rep: (1)
* Android775 I’ll test tomorrow, where did I get it?



Rep: (1)
Pulled from a hacker (How to enable the navigation bar for someone who is missing)
It's still simpler here. In Android, there is a special debugging variable qemu.hw.mainkeys, which allows you to control the visibility of on-screen navigation keys.
If it has a value of 0, the keys will be shown on the screen, 1 - the opposite effect.

We write the variable with the desired value to the file/system/build.prop , and that is all:

# su
# mount -o remount, rw / system
# cp /system/build.prop /system/build.prop.bak
# echo qemu.hw.mainkeys = 0>/system/build.prop

**********************************************************************************
But it’s better to handle this variable with pens, because it already exists in this file
just looking for a stringqemu.hw.mainkeys and change the value to zero


Full version    

Help     rules

Now: 08/26/19, 08:33