Database Info

[GUIDE][How-To][LP 5.1] Root and Custom Recovery for Alcatel OneTouch Flash 2 (7049D)

First of all I would like to share this method as I don't see it anywhere here (yet).
This method is not mine, nor anything is of my discovery
Alactel Flash 2 Specs (please let me know of any variation of this model)
5.0-Inch HD IPS Display (720 x 1280 Pixels, 294 ppi)
Android 5.1 Lollipop OS
MediaTek MT6753 Chipset
1.3GHz Octa Core 64-bit Cortex-A53 CPU
Mali-T720 MP2 GPU
2GB of RAM
13.0 Megapixel Autofocus Main Camera with Two-Tone LED Flash
5.0 Megapixel Front Camera with LED Flash
16GB Internal Storage
Expandable Up to 128GB via MicroSD
Dual SIM (Regular + Regular)
4G LTE, 3G HSPA+, 2G EDGE and GPRS Networks
Wi-Fi and Wi-Fi Hotspot
Bluetooth 4.0
GPS with A-GPS
FM Radio with RDS
USB OTG
MicroUSB 2.0
3.5mm Audio Jack
Magnetometer
Accelerometer
Proximity Sensor
Ambient Light Sensor
3,000mAh Li-ion Battery (Non-removable)
STEPS
Requirements:
- PC
- USB Cable
- Brain
- Little bit of common sense on flashing
Download Links:Mediatek VCOM Drivers:
- Link
SP Flash Tool:
- Link
Flash 2 TWRP & Scatter File:
- Link
ETA-SuperSU-v2.52.zip:
- SuperSU link
Instructions:
1. Download all necessary files.
2. Install MTK Drivers
3. Extract SPFlash tool anywhere on your PC and flash2_twrp.zip
4. Copy the BETA-SuperSU-v2.52.zip to your phone.
5. Open flash_tool.exe, click on the Download Tab
6. Click Scatter-loading and browse for the scatter file(included in the flash2_twrp.zip)
7. Make sure flashing mode is set to "Download Only" and check mark only on the Recovery.
8. Click Download.
9. Turn off your phone, connect your phone to the PC and wait for the flashing to commence.
10. Green Ring image will show once flashing is completed.
11. Important: Disconnect your phone from the computer, press and hold Vol Up + Power.
12. Boot menu will show, select Recovery.
From the custom recovery, before rooting, backup your rom first.
To root:
1. On the TWRP Recovery, click Install.
2. Select BETA-SuperSU-v2.52.zip.
3. Flash it, then you can reboot as it is.
4. Enjoy your rooted AF2.
All files and credits belongs to:
Mr. Long NT of AF2 FB Group

NOTE: members of af2 group states that this method is bugged and you will lose OTA.

Please verify if someone successful in rooting this method. thanks

yabadap said:
NOTE: members of af2 group states that this method is bugged and you will lose OTA.
Click to expand...
Click to collapse
That is why, before rooting, it is said to backup first, besides, there is already a stock rom that is flashable via recovery.
dweller417 said:
Please verify if someone successful in rooting this method. thanks
Click to expand...
Click to collapse
Worked for me, most error they encounter is SPFT not reading their devices, and others (first batch buyers) said that their OTA was gone, but this, I am not fully aware of what do they mean.

It's work, thank you very very much.

kitipon said:
It's work, thank you very very much.
Click to expand...
Click to collapse
You're welcome. Rooting shouldn't be a problem though. Having a flashable stock rom is, might be my case only. In the AF2 FB group a recovery flashable is already done, but a SPFT one isn't, yet.

Facing a bug, can you help? Please
yabadap said:
NOTE: members of af2 group states that this method is bugged and you will lose OTA.
Click to expand...
Click to collapse
Hi, after rooting using this method, I can't install any app, from playstore as well as offline apk installation, playstore shows "error code:-504." Any idea or solution? BTW, I rebooted several times, wiped data and cache of play store and Google service framework and removed then readded my Google ID as suggested by other forums. No result...

Can I get the link for the Facebook group you are talking about
Can I get the link for the Facebook group you are talking about?

ade.sultan said:
Can I get the link for the Facebook group you are talking about?
Click to expand...
Click to collapse
Alcatel Flash 2 PH.

So who has tried this guide? I'm planning to purchase a Flash Plus 2 (Is it the same device?)

Onda V919 Air DualOS 9.7" 2048x1536 px - Z3735F/Z3736F / Download thread

Hello friends.
PREAMBLE:
1. In addition to that nice thread Onda v919 Air 3G Dual Boot 9.7" 2048x1536 px - Z3736F - 3G - Android/Windows I opened up this thread (a bit late) as an download thread for roms and other stuff only.
2. Til now I was very happy with Z3736F devices (tablets and TV-boxes) because their higher clocked performance is much more better than the Z3735F I know. But I guess these Onda V919 Z3735F devices have the same great performance as I know it from other Z3736F devices. Seems that Onda did a very good job with the hard- and firmware. Also the built quality is very good also (especially the Black/Golden Edition is an eyecatcher) and the price seems to be the lowest in the category of Intel fullHD devices with DualOS - IMHO these devices could be a really great deal for everyone. Just as an example: I bought the V919 Dual Black/Gold 3G Z3735F with 64GB in 2016-01 for 170 USD.
3. For this reason and because I prefer the Android system on a handheld (for Windows I recommend to work with keyboard and mouse) it is very important 4 me to have some modifications on the firmware - most important are root privileges and a working Playstore. For devices like the Teclast X98 you can use the same Android firmware regardless you have a 3G or non-3G or a model I or II or III. That's very comfortable. But for the V919 Onda seems to use very different hardware with different drivers. For this reason it seems that each V919 model needs its own firmware. To have a clear thread to find such files easy with an light way to change your system I opened this thread.
4. Edit 2016-09-09: I have sold my golden V919-3G-64GB-DualOS a few months ago. But I missed that very beautiful golden eyecatcher with great built quality, thin and lightweighted. So I bought the smaller edition in Gold-V919-non3G-32GB-DualOS for USD 115 a few weeks ago from a flashsale at Gearbest. You can read a little more about that in post #57. I added the recommended firmware below.
INSTRUCTIONS:
The easy way to flash (sometimes does not work):
- without installing Intel drivers
- without installing the Intel Manufacturing Tool
- without loosing your existing Windows system
you can go the way to flash a modified system just with one-click. All needed files are included in the download packages.
But nevertheless there are some important things to care for:
analyze your device model to find the matching firmware
read and understand the ReadMe in the download (incl. the xPosed Framework things if applicable)
The manual way (should work always and is not as hard as it looks first):
- without installing Intel drivers
- without installing the Intel Manufacturing Tool
- without activating the DNX mode (which I could not find until now. But maybe you have luck with point 4)
- find the matching firmware for your device
1. Install Android ADB and FASTBOOT (Please google for that - That should not be mentioned within this thread)
2. Install the Intel DNX USB drivers and the Intel Android Device drivers to your Win7 or Win10. Using Win8 you have to deactivate the drivers signature before. (Please google for that - That should not be mentioned within this thread)
3. Boot into the Fastboot mode (Droidboot) the easy way:
a) You have a working Android system.
b) Activate the developer options in system/settings.
c) Connect your tablet via USB to your computer.
d) Open a ADB command window.
e) adb reboot-bootloader
4. Boot into the Fastboot mode (Droidboot) the hard way:
Try to use different button combinations when powering on your device until you see a black screen with some words like "recovery" or "droidboot" written on it. For example:
a) Keep holding Volume minus (-) and Power simultaneously
b) Keep holding Volume minus (-) and Power simultaneously and release Power when you see "ONDA" for the first time
c) Press Vol. + and Power as long as you see the OS selector. Choose the Android system. Now quickly keep pressing the Volume- (minus) button until you will see the fastboot menu. Maybe you will boot into Android secure mode doing this on the V919 where you can make some unwanted changes (f. ex. app-installations, xPosed-settings etc.) undone to make Android boot again proper.
5. In Fastboot mode do this:
a) wipe the existing firmware parts:
b) fastboot erase cache
c) fastboot erase data
d) fastboot erase userdata
e) fastboot erase system
f) Now flash the new partitions (Always flash every xxx.img file belonging to the firmware - if not otherwise mentioned in the Download section !!!). Please use the filenames for the .img files regarding to your downloaded firmware !
g) fastboot flash boot boot.img
h) fastboot flash cache cache.img
i) fastboot flash recovery recovery.img
k) fastboot flash system system.img
l) fastboot reboot
6. After rebooting you should start and close the xPosedInstaller App without doing anything.
a) Connect ADB:
adb devices
adb shell
su
echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
b) Now enjoy the power of xPosedFramework
DOWNLOADS:
FIRMWARE:
V919 3G AIR Black Gold Edition 64GB DualOS Z3735F
3G / Gold / 64GB / Pure KitKat / Z3735F / V5 + V6
V919 3G AIR Black Gold Edition 64GB dual 20151014_V1.0.1_V5_mod
V919 3G AIR Black Gold Edition 64GB dual 20151014_V1.0.1_V5_Stock
V919 3G AIR Black Gold Edition 64GB_RemixOS_2015-08-21_V1.0.5_V5_Mod Be aware that this Remix firmware has a bad performance
V919 AIR Black Gold Edition 32GB DualOS Z3735F
non-3G / Gold / 32GB / Pure KitKat / Z3735F
V919 3G AIR Black Gold Edition 64GB_RemixOS_2015-08-21_V1.0.5_V5_Mod
non-3G / Gold / 32GB / Pure KitKat / Z3735F / V9 (only system.img and boot.img has to be flashed by Fastboot)
V919 3G AIR Black Gold Edition 64GB dual 20151014_V1.0.1_V5_mod
V919 3G AIR Black Gold Edition 64GB dual 20151014_V1.0.1_V5_Stock
V919 AIR DualOS 64GB RemixOS 3G and non-3G Z3736F
3G/non-3G / white / 64GB / RemixOS / Z3736F - Note: 3G function is not working
Removed
V919 AIR Pure Gold Edition 128GB DualOS with SatTV and AirCon and Refridgerator
No rom atm. Testers needed
OTHER STUFF:
Screenshot of my V919 Gold 3G/64GB/Z3735F using xPosed Framework
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Deactivating the Windows hardware button in the Android system of Black-Gold Edition Z3735F
Onda-V919-3G-Dual-Gold_NoWinHome
The new ReadMe
Have phun and [email protected] [email protected]! No donations please!

Testers needed - Unconfirmed roms
Here you find roms for some Onda V919 models I made. But nobody confirmed whether the software is working fine. So be aware to have a higher risk of flashing a non working rom. But if you go this way other users will be happy for your help. Please let me know about the result. Then I can add the software to post #1. Thanks in advance.
Please give me these details for a feedback or a rom request:
- My device color: White / Black-Gold
- SOC: 3735 / 3736
- Model: V5 (Back of your tablet => Bottom => SN (serial number): The 9th and 10th character = version number)
- 3G: Yes / No
- ROM: 32GB / 64GB
- Tested rom: V919_AIR_non3G_DualOS_64GB_RemixOS_V1.0.5_V5_20151008
- Everything working: Yes / No
- Issues: bla, bla, bla
Unconfirmed Firmwares:
3G / V1 / 64GB / KK
V919 3G Air V1 64GB DualOS_2015-01-27_mod

Thank you, great work !
V919 AIR DualOS 64GB RemixOS v1 Thank you, I can try it, just please answer:
- what's included into package ?
- is it rooted ?
- how to install it ?
PS: inside files there are instruction "This rom is made for the non3G Onda V919 AIR DualOS 64GB RemixOS 3735F" Is this the same as original Remix OS for Onda v919 Dual OS which is also working on Onda v919 3G Dual OS (I have this tablet v1 but it's 3736 processor)
---------- Post added at 08:39 PM ---------- Previous post was at 08:07 PM ----------
Anyway I decided to install IT !
I can confirm that on ONDA v919 3G Dual OS "V919_Air_non3G_DualOS_64GB_RemixOS_V1.0.5_V1_20151 110.part1" working without any problems !!

mcride50 said:
...
I can confirm that on ONDA v919 3G Dual OS "V919_Air_non3G_DualOS_64GB_RemixOS_V1.0.5_V1_20151 110" is working without any problems !!
Click to expand...
Click to collapse
Thanks. I added the links to post #1.

Hi,
can you please sugest any rom for gold Dual boot 64gb 3G V6 ????

dax32 said:
Hi,
can you please sugest any rom for gold Dual boot 64gb 3G V6 ????
Click to expand...
Click to collapse
Please read the blue description of the first download section. U have the same device as I have.
P. S.: You don't have to leave a feedback. Your firmware and your device was tested positive already.
I was hoping that my OP was easy to understand. But it wasn't as it seems. ? My fault. Sorry. But no idea what to change.
Sent from my Teclast X98 3G using Tapatalk

Thank you,
how can i get into Dnx Mode on V6 ???
On+vol+ and vol- doesn't work???
and how can i udate to the latest bios???
pogodancer said:
Please read the blue description of the first download section. U have the same device as I have.
P. S.: You don't have to leave a feedback. Your firmware and your device was tested positive already.
I was hoping that my OP was easy to understand. But it wasn't as it seems. My fault. Sorry. But no idea what to change.
Sent from my Teclast X98 3G using Tapatalk
Click to expand...
Click to collapse

@ dax32
OH, you r on Remix atm and want to go back to KK. Sorry, don't know how to enter dnx. Recognized that it's not working the usual way. Will have a try tomorrow and will let you know if I have success.
Sent from my Teclast X98 3G using Tapatalk

onda v919 dual boot
Hallo.I have onda v919 dual 64gb V8 black gold edition.Is possible instaling remix OS to?
Thnx.
Radik

Hi i managed to install your Onda_V919_4.4.4_1.0.1.v5_20151014_Mod using this method http://www.ondaforum.com/topic/3833-the-v919-3g-air-v567-model-and-fixes-included/ and it is worked!!!
but after running XposedInstaller. Touch "Framework" and touch "Install/Update ....it is rebooting continuously-without entering in android....how can i fix it???

radik1963 said:
Hallo.I have onda v919 dual 64gb V8 black gold edition.Is possible instaling remix OS to?
Thnx.
Radik
Click to expand...
Click to collapse
If u have a firmware 4 ur device it's possible. You can flash the official way at first. After I can make a modded rom 4 u.
Sent from my Onda V919 Air 3G DualOS using Tapatalk

dax32 said:
Hi i managed to install your Onda_V919_4.4.4_1.0.1.v5_20151014_Mod using this method http://www.ondaforum.com/topic/3833-the-v919-3g-air-v567-model-and-fixes-included/ and it is worked!!!
but after running XposedInstaller. Touch "Framework" and touch "Install/Update ....it is rebooting continuously-without entering in android....how can i fix it???
Click to expand...
Click to collapse
Hi dax,
I thought u were on Remix before flashing.
1. When u flashed KK on Remix base u r walking on thin ice.
2. Reading my tutorials inside the firmware downloads is a must. Especially the ones belonging 2 xposed framework. U have 2 to do a few steps in ADB before starting the xposed installer.
3.Check if u still have ADB. Do a quick Remix flash or do a long KK installation with Windows.
Sent from my Onda V919 Air 3G DualOS using Tapatalk

pogodancer said:
Second you have to pay attention to:
read and understand the readme.txt or readme.bat in the download
do a factory reset after having flashed successfully
read, understand and do the ReadMe4xPosed.png from the download if you want to use xPosed Framework
Click to expand...
Click to collapse
@ all
Especially in the readme I made clear that the method of flashing I offered you with my downloads is critical if you don't do exactly what's described.
But unfortunately many users don't seem to be interested to prevent their devices from a softbrick - because they did not take care of that. Additionally there was a guy who used my script, made it in blue color, made it public in another forum BUT did not explain the disadvantages of the script. IMHO that is a timebomb because people are using the script careless for any kind of firmware flashing.
It is important for me that your devices are running as good as possible without any damage. Therefore I corrected the fastboot-script and the content of my downloads. All you have to do is to install the usual ADB drivers and chose the correct firmware matching to your device.
My rework has these benefits:
- a safe and easy way to flash your device
- no matter which firmware you ran before flashing
- automatic factory reset
- one-click flash method
- short and easy ReadMe included
Important:
I renewed all downloads. That means if you downloaded files before 2016-02-20 you should download again. Delete your old downloads then.

Hey pogodancer,
I have the same tablet as you (gold black air 32gb) except the v8 model, will the v7 files work on it?
Thx

HoMsEy-4-LiFe said:
Hey pogodancer,
I have the same tablet as you (gold black air 32gb) except the v8 model, will the v7 files work on it?
Thx
Click to expand...
Click to collapse
Nobody knows until someone will test it.
Sent from my Teclast X98 3G using Tapatalk

pogodancer said:
Nobody knows until someone will test it.
Sent from my Teclast X98 3G using Tapatalk
Click to expand...
Click to collapse
Alright I'll give it a try sometime this week and report back

HoMsEy-4-LiFe said:
Alright I'll give it a try sometime this week and report back
Click to expand...
Click to collapse
I hope you know what you do.
Do you have your stockfirmware. And do you know how to reflash the stockrom just in case the device does not boot anymore.

pogodancer said:
I hope you know what you do.
Do you have your stockfirmware. And do you know how to reflash the stockrom just in case the device does not boot anymore.
Click to expand...
Click to collapse
Hmmmm, well, things didn't go quite as planned. After running the bat file, it successfully rebooted in bootloader and erased cache, data, userdata and system. When it came to flash boot, fastboot, recovery and system, it gave me errors and skipped those steps. Not sure why, I'm guessing drivers issues but there is no way to be certain. Now I can't even boot in bootloader by holding vol up+power.....
Man CMW is so much better to use, how I miss it. Is it still possible to flash those things manually?

As long as you don't reach Fastboot mode or dnx mode you have to fully flash your device via USB. Then you will lose WI dows
Sent from my UMI Rome Gold using Tapatalk

pogodancer said:
As long as you don't reach Fastboot mode or dnx mode you have to fully flash your device via USB. Then you will lose WI dows
Sent from my UMI Rome Gold using Tapatalk
Click to expand...
Click to collapse
That's fine, I don't mind reinstalling windows. Just want to make sure it's the instructions from this post :
http://www.ondaforum.com/files/file/569-flashing-instructions-in-englishpdf/
Thx,

[GUIDE] ZTE Blade Vantage (Z839) Specs & Information

ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide​
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD; OTG USB support)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As to the filesystem of this device, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).

Oh hell yea !!!
MotoJunkie01 said:
ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide​
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As for the partition index/filesystem, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).
Click to expand...
Click to collapse
OK I don't Have the Device Yet...
BUT I am here and Team_Astr4y4L's Got your back!
Brother If you need anything from us over here you just name it and we're on it !!
Attention XDA Take notice; you have in your presence the Koolest Tower-climbing Rom developer I know !! If it can be done @MotoJunkie01 with the help of his Friends will make it reality !!!
@MotoJunkie01 Brother we will be watching this closely...
you know how we feel Over here about Big-Red ... LOL
Astr4y4L
Team_Astr4y4L

As always, your continued support and assistance are beyond value. By the way, you may know the answer to this. I have a new BLU Studio M4 with a Spreadtrum sp7731 processor. I'm having trouble finding proper USB drivers for my Windows 10 PC. Are you familiar with this chipset?

MotoJunkie01 said:
As always, your continued support and assistance are beyond value. By the way, you may know the answer to this. I have a new BLU Studio M4 with a Spreadtrum sp7731 processor. I'm having trouble finding proper USB drivers for my Windows 10 PC. Are you familiar with this chipset?
Click to expand...
Click to collapse
you can try to follow this Here
https://forum.hovatek.com/thread-827.html
it deals with
[Tutorial] How to manually install Spreadtrum USB drivers on a Windows PC
wow copy past was kinda size-crazy there ...LOL
but it's dated Oct 2013
but again,
it references in first paragraph
Disable driver signature verification enforcement if using a Windows 7, 8, 8.1 or 10 PC (see https://forum.hovatek.com/thread-752.html )
SO maybe this will work for you Bro.
IDK not familiar with the platform personally but I do Know
WINDOWS-BLOW's ..
noticed that it's also used in several of the newer Samsung devices also...

Astr4y4L said:
you can try to follow this Here
https://forum.hovatek.com/thread-827.html
it deals with
[Tutorial] How to manually install Spreadtrum USB drivers on a Windows PC
wow copy past was kinda size-crazy there ...LOL
but it's dated Oct 2013
but again,
it references in first paragraph
Disable driver signature verification enforcement if using a Windows 7, 8, 8.1 or 10 PC (see https://forum.hovatek.com/thread-752.html )
SO maybe this will work for you Bro.
IDK not familiar with the platform personally but I do Know
WINDOWS-BLOW's ..
noticed that it's also used in several of the newer Samsung devices also...
Click to expand...
Click to collapse
Thank you. Yes that did work. Disabling kernel signing was necessary on my Windows 10 (64 bit) setup first.

Well I tried.
Okies so I did actually try to unlock the bootloader. I plugged it in then used the
Code:
adb devices
command, it showed up so then after trying
Code:
adb reboot bootloader
it just booted regularly. So I decided to use
Code:
adb reboot recovery
, it went into recovery mode. But when I tried
Code:
fastboot devices
nothing happened. I then tried to put it in to bootloader mode using the key combo and still
Code:
fastboot devices
did not do anything so this leads me to believe that for some reason the fastboot command doesn't recognise that there is anything attached. Not sure where to go from there, so I am calling it a night for now. I will likely try again sometime tomorrow or the next day as I have them off. Good luck to anyone who tries after this post.

Ubervillin said:
Okies so I did actually try to unlock the bootloader. I plugged it in then used the command, it showed up so then after trying it just booted regularly. So I decided to use , it went into recovery mode. But when I tried nothing happened. I then tried to put it in to bootloader mode using the key combo and still did not do anything so this leads me to believe that for some reason the fastboot command doesn't recognise that there is anything attached. Not sure where to go from there, so I am calling it a night for now. I will likely try again sometime tomorrow or the next day as I have them off. Good luck to anyone who tries after this post.
Click to expand...
Click to collapse
Yeah, just like LG, ZTE oftentimes disables fastboot mode on their devices, making it all the more difficult -- if not nearly impossible -- to unlock the bootloader or achieve systemless root. If I can find stock firmware for the Z839, I will try to reverse engineer the boot chain, and try to find a workaround to get into fastboot.

Hello I have the ZTE Blade Vantage (z839) and when I click activate account on Message+ it says please wait starting service for like a second and goes off. It never activates. Please help

Hey @MotoJunkie01,
Any more news on this device?
Team Astr4y4L's looking at it again.
I'm doing Gofer Work.

@MotoJunkie01
How far is the development going on for this device and also does any know how to root this device?

from what I can tell Root will require some sort of exploit to unlock the bootloader.
it's msm8909 so there may be a firehose file for another zte msm8909 device and that may let us play with QFIL and QXDM.
I am digging everywhere trying to just find a stock firmware file for it. and coming up empty

George_Jetson said:
from what I can tell Root will require some sort of exploit to unlock the bootloader.
it's msm8909 so there may be a firehose file for another zte msm8909 device and that may let us play with QFIL and QXDM.
I am digging everywhere trying to just find a stock firmware file for it. and coming up empty
Click to expand...
Click to collapse
Yeah, due to its locked down bootloader and lack of factory images, development has failed to get off the ground for this device. Shame too, it has great specs for a budget smartphone. I'm pretty sure there are some available firehose files for the Qualcomm chipset. I had the same thoughts. If the stock boot image could be patched for systemless root, there is a chance we could push the patched boot image with QFIL. But where to get stock images is the key.

Hi, ZTE BLADE VANTAGE only comes w/ LTE Mobile Network Settings. I'd like to know if it's going to be posible in the future to change this option to Global Setting (and how?) so it could be use internationally. Thanks..
MotoJunkie01 said:
ZTE Blade Vantage (Z839)
Verizon Wireless (Prepaid)
Specs & Information Guide​
The ZTE Blade Vantage (Z839), released by Verizon on October 5, 2017, is a budget smartphone packing a ton of mid to high end features, and is Verizon's very first LTE only smartphone. The Z839 has the following basic specifications:
Android Version: 7.1.1 Nougat
CPU Platform: Qualcomm Snapdragon 210 (MSM8909)
1.1 GHz Quad Core ARM Cortex A7 (32 Bit)
GPU: Qualcomm Adreno 304
Display: 5.0" TFT (FWVGA) LCD, 196ppi (480x854)
Battery Li-Ion 2500 mAh Removable
23.4h Talk; 312h Standby
Storage: 16GB (Supports up to 256GB external micro SD; OTG USB support)
RAM: 2GB
Weight: 5.29oz (150 g)
Connectivity: Qualcomm X5 LTE Modem
LTE Bands 2, 4, 5, 13 (LTE Cat 4)
Band 2 / 1900MHz (PCS)
Band 4 / 1700MHz (AWS)
Band 5 / 850MHz (Cellular)
Band 13 / 750MHz (Upper 700)
Bluetooth: 4.0
SIM: Nano
Headphone: 3.5mm Jack
Telephony: HD Voice; VoLTE; WiFi Calling
Camera 8MP Rear; 2MP Front
As to the filesystem of this device, the Z839 operates on an SD/eMMC partition type. The 16GB eMMC is comprised of a 3.5GB /system partition, a 2GB /cache partition, and an 8.7GB /userdata partition, all formatted by way of the ext4 file system. In addition, the eMMC is formatted with 27 additional partitions for various system and radio firmware functions (/modem, /boot, /recovery, etc.).
Initial inspection of the Z839 indicates that, following Verizon's typical policy, the bootloader is locked. I have not yet explored possible exploits or manufacturer support forums for unlocking the Z839 bootloader. Regarding root access, the Z839 features an Android 7.1 1 Nougat build which does not appear vulnerable to the typical one-click root methods, such as KingRoot or KingoRoot. Thus, in theory, and by a plethora of personal experience, it will be almost imperative, in order to gain root access of the stock OS, to unlock the Z839 bootloader. Subsequently, flashing a custom recovery should be possible. Then, a SuperSU or Magisk systemless root package may be installed from custom recovery to achieve superuser access of the stock Nougat ROM.
Because the Z839 is a newly released smartphone (October 5th, 2017), development on the device seems to be in the very early stages. For the price, my personal experience with this phone has been absolutely great. I intend this thread to be a gathering place for interested developers, contributors, and enthusiasts to explore, hypothesize, theorize, and eventually develop custom recoveries, ROMs, kernels, etc., for the ZTE Blade Vantage (Z839).
Click to expand...
Click to collapse

Here is the B20 firmware package (Z839V1.0.0B20) it also includes the firehose for this device allowing you to use QPST/MiFlash to restore your device or to flash custom boot.img's among other things.
https://www.androidfilehost.com/?fid=1395089523397895595
Separate download with just the firehose, rawprogram0.xml, patch0.xml
https://www.androidfilehost.com/?fid=1395089523397895596
I have also uploaded a few other tidbits that aren't super useful but maybe will help someone down the line:
Verizon Repair APN tool (Could be useful if you break something)
https://www.androidfilehost.com/?fid=1395089523397895588
ZPST for the ZTE MultiDL Tool (Not useful unless you have the ZTE MultiDL Tool)
FRP/Kill Switch Reset tool (Requires License file so not useful)
https://www.androidfilehost.com/?fid=1395089523397895587

Any updates on this device?
It's been a while since this device has come out, and now we have more available files for it. Is anyone interested in looking into maybe rooting this device?

Would be super awesome if someone could root it!! If I was any better at this I would give it a shot but I am not there yet lol!

When I power on my zte z839 am stuck on bootloop,and even when I plug my charger my phone powers on and sticks on bootloop. I need a solution pals. Moseti(Kenya).

Hey everyone. It seems that there is now a bootloader unlock for this device. Anyone want to look into this?
https://forum.xda-developers.com/android/software/bootloader-unlocking-qualcomm-zte-t4100897

still no easy way to root this device? or any successful way?

Hey everybody! Thanks for your help in advance. I also have the ZTE Z839 and I want to use it with a carrier other than verison when I try to unlock the phone, it asks for a verification code. I got the code from cx service however it said incorrect code. The cx rep. had only 1 code and it didnt work! then he simply said either I can get verison service or the phone is incapable of using on other networks......... Duh why would there be a option in settings to use with different carrier and ask for a code if it is incapable? I tried tech support also to no avil. Ive spent hours on hold with cx and have troubleshot in every way I know how. Can anybody confirm if this is even possible or not and what is the code or should I just give up?

[MASTER THREAD][SM-J260F/G/M/Y/DS][J2CORELTE] Samsung Galaxy J2 Core 2018

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Versions: SM-J260M/DS (LATIN); SM-J260Y/DS (Philippines); SM-J260G/DS (India); SM-J260F/DS (CIS)
*CIS - Union of Independent States (Russia, Kazakhstan, Tajikistan, Uzbekistan, Armenia, Belarus, Azerbaijan, Kyrgyzstan, Moldova)
NETWORK
Technology GSM / HSPA / LTE
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 900 / 2100 - J260Y/DS, J260G/DS, J260F/DS
HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 - J260M/DS
4G bands LTE band 2100, 1800, 850, 2600, 900, 700, 2600, 2300, 2500 - J260Y/DS,
LTE band 2100, 1900, 1800, 1700/2100, 850, 2600, 900, 700, 700, 700 - J260M/DS
LTE band 2100, 1800, 850, 2600, 900, 800 - J260G/DS
LTE band 800, 850, 900, 1800, 2100, 2300, 2500, 2600 - J260F/DS
Speed HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps
GPRS Yes
EDGE Yes
LAUNCH
Announced 2018, August
Status Available. Released 2018, August
BODY
Dimensions 143.4 x 72.1 x 8.9 mm (5.65 x 2.84 x 0.35 in)
Weight 154 g (5.43 oz)
SIM Dual SIM (Micro-SIM, dual stand-by)
DISPLAY
Type PLS TFT LCD capacitive touchscreen, 16M colors
Size 5.0 inches, 68.9 cm2*(~66.7% screen-to-body ratio)
Resolution 540 x 960 pixels, 16:9 ratio (~220 ppi density)
Protection Corning Gorilla Glass (unspecified version)
PLATFORM
OS Android 8.1 Oreo (Go edition)
Chipset Exynos 7570 Quad (14 nm)
CPU Quad-core 1.4 GHz Cortex-A53
GPU Mali-T720
MEMORY
Card slot microSD, up to 256 GB (dedicated slot)
Internal 8 GB, 1 GB RAM
MAIN CAMERA
Single 8 MP, AF, f/2.2
Features LED flash, HDR, panorama
Video [email protected]
SELFIE CAMERA
Single 5 MP, f/2.2
SOUND
Loudspeaker Yes
3.5mm jack Yes
COMMUNICATIONS
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot
Bluetooth 4.2, A2DP
GPS Yes, with A-GPS, GLONASS, BDS
Radio FM radio
USB microUSB 2.0, USB On-The-Go
FEATURES
Sensors Accelerometer, proximity
Messaging SMS(threaded view), MMS, Email, Push Email, IM
Browser HTML
BATTERY
Removable Li-Ion 2600 mAh battery
MISC
Colors Black, Gold, Lavender
SAR 0.61 W/kg (head) * * 0.61 W/kg (body) * *
SAR EU 1.39 W/kg (body) * *
Price About 100 EUR

(ذ)

It's a February 2019 2 Year old thread...

How to fix safetynet in my device j260g ?

This thread would be almost unattended, for me it's a fresh start, interested on building the TWRP recovery project for SM-J260M ( The common Latin-American variant I think, 2018 version) and have seen your posted trees on GitHub, given the fact that this user: https://github.com/Vladislav4KZ belongs you. In the case that you can advice me a little nuances for this device --being a noobie on this matter-- please are you able to describe how you grasped the kernel tree? I´ve picked a kernel tree from: https://github.com/MT6797/kernel-3.18 . Due to I've looked on my phone's settings that it's Linux kernel version was 3.18.14 (See Attachment below) .
About the vendor tree, which one have you used? I'm currently picking this universal exynos7570 Android8.1 vendor tree from: https://github.com/OpenExynos/android_vendor_samsung_slsi_exynos7570/tree/android-8.1.0_r1 .
The device-tree, I've leveraged from SebaUbuntu's device tree generator: https://github.com/twrpdtgen/twrpdtgen . After that, I've chosed the repository from https://android.googlesource.com/platform/build/+/refs/tags/android-8.1.0_r51 to perform the build. I've got some errors, specially when compiling the kernel, I've worked-around the common erros that were most related to an outdated programming language: python2 on files that were being built with python3.
When I've finalized clearing that files, they were few, I've decided to take the kernel and vendor tree out of the build. So i've chosen the omni_device_tree that's for default created when creating the google-Android building repo and syncing it. Got a successful recovery image, until I've tested it and got the problem of the classical blinking-screen when I've booted the device at recovery.
🗨🗨 Questions:
How you grasped the kernel-tree?
Which vendor-tree have you used?
How can I compile the kernel adequately for this model that is a little bit different than your: SM-J260F ?
Have you compiled a recovery image for your device? If yes, were you succesful? What problems you've faced as the main rocks hindering the build process's completion? What you changed, in case you've flashed it but got a blinking screen?

EyzTOP01.L said:
This thread would be almost unattended, for me it's a fresh start, interested on building the TWRP recovery project for SM-J260M ( The common Latin-American variant I think, 2018 version)
Click to expand...
Click to collapse
Hi, I just built TWRP 3.6.2-9 for your device. Can you test it? Here's the flashable file

notnoelchannel said:
Hi, I just built TWRP 3.6.2-9 for your device. Can you test it? Here's the flashable file
Click to expand...
Click to collapse
Thank you, first sucessful TWRP image that past beyond the blinking screen, in fact it booted-up smoothly, unfortunately it's not recognizing the touchscreen and that limits it's ability to test and point more flags about it. What have happened when I've tried to reboot to the system is that it didn't worked, when an odd-recovery image is flashed on this device model seemingly it doesn't return to normality unless you're able to do that from the recovery itself i.e not forcing it by withdrawing the battery or pressing button combinations for restarting; I've fixed that issue by flashing the stock recovery back to the device via Odin ( the only resource for rescuing this device) and worked up to the normal state, no problems after that. Here I show you below, sorry for my phone's state, it has suffered a fall that slapped it's external surface, fortunately hardware still intact, and relative to it's touch sensitivity it works seamlessly as you can note in the next attachment.
There for that particular problem, by changing or adding some flags on your BoardConfig.mk file that lies on the device tree folder you can fix it. It's mentioned on other XDA threads and some TWRP-compiling channels found youtube. I would be pretty grateful in case you show point me out the device, kernel and vendor blobs that you've used for compiling the recovery. As I've previously stated: the blobs I've used led me to the blinking screen failure and I am figuring out about what I've made wrong, I'm a beginner and would appreciate the epiphany that you'd cater me in case you teach me about the code and what you've made, particularly on the blob trees. Thank you very much in advance.

EyzTOP01.L said:
Thank you, first sucessful TWRP image that past beyond the blinking screen, in fact it booted-up smoothly, unfortunately it's not recognizing the touchscreen and that limits it's ability to test and point more flags about it. What have happened when I've tried to reboot to the system is that it didn't worked, when an odd-recovery image is flashed on this device model seemingly it doesn't return to normality unless you're able to do that from the recovery itself i.e not forcing it by withdrawing the battery or pressing button combinations for restarting; I've fixed that issue by flashing the stock recovery back to the device via Odin ( the only resource for rescuing this device) and worked up to the normal state, no problems after that. Here I show you below, sorry for my phone's state, it has suffered a fall that slapped it's external surface, fortunately hardware still intact, and relative to it's touch sensitivity it works seamlessly as you can note in the next attachment.
There for that particular problem, by changing or adding some flags on your BoardConfig.mk file that lies on the device tree folder you can fix it. It's mentioned on other XDA threads and some TWRP-compiling channels found youtube. I would be pretty grateful in case you show point me out the device, kernel and vendor blobs that you've used for compiling the recovery. As I've previously stated: the blobs I've used led me to the blinking screen failure and I am figuring out about what I've made wrong, I'm a beginner and would appreciate the epiphany that you'd cater me in case you teach me about the code and what you've made, particularly on the blob trees. Thank you very much in advance.
Click to expand...
Click to collapse
I compiled TWRP on android-8.1 branch too. That might be the solve of the no touch problem.
About compiling, you'll just have to get these:
Minimal TWRP manifest twrp-8.1 branch here
And a device tree from here
In the device tree, we already have a prebuilt kernel. So we don't need any kernel source. Same for vendor.
I'll try to fix touch by building on higher branches.

Here's a smaller PORTED twrp version:

notnoelchannel said:
Here's a smaller PORTED twrp version:
Click to expand...
Click to collapse
Same issue with the touchscreen, can't swipe to unlock, the only noticeable change was the color and of course it's smaller size. Have you tried adding some flags at the BoardConfig.mk? Could you please try developing with the 9.0 Branch, I only have the 8.1 one and low space on disk. Thanks

Sorry, Sir, excuse me for asking advice there, but I got stuck and found no way to get out of this issue when compiling the recovery-image fror the J260M: on my build directory: bionic/libc/bionic/grp_pwd.cpp . This file deploys a bunch of errors that are related with the C++ language, such as = bionic/libc/bionic/grp_pwd.cpp:137:46: error: unknown type name 'android_id_info' or undeclared identifier on some other lines. Finally outputing the following hurdle for continuing the process:
fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated.​What could I do, it's my mistake or it's one from the android-security-8.1.0_r81 branch code? ( which was the one I've initialized and synced the repo for building). What have you made to compile the image without those errors?. No matter if I build with/without kernel source this error always stucks my progress.

EyzTOP01.L said:
Sorry, Sir, excuse me for asking advice there, but I got stuck and found no way to get out of this issue when compiling the recovery-image fror the J260M: on my build directory: bionic/libc/bionic/grp_pwd.cpp . This file deploys a bunch of errors that are related with the C++ language, such as = bionic/libc/bionic/grp_pwd.cpp:137:46: error: unknown type name 'android_id_info' or undeclared identifier on some other lines. Finally outputing the following hurdle for continuing the process:
fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated.​What could I do, it's my mistake or it's one from the android-security-8.1.0_r81 branch code? ( which was the one I've initialized and synced the repo for building). What have you made to compile the image without those errors?. No matter if I build with/without kernel source this error always stucks my progress.
Click to expand...
Click to collapse
Build with the device tree and manifest i linked

notnoelchannel said:
Build with the device tree and manifest i linked
Click to expand...
Click to collapse
No matter what I've tried, followed your steps closely, even switched to the 9.0 branch but it seems to not work up due to so many erros on the code of the whole android source. What would have I messed up for the Building Platform to deploy so many issues and hence leaving me unsuccesful from completing the recoveryimage compilation . How can I work this? If i haven't wrote the android source code...

any updates?

EyzTOP01.L said:
Same issue with the touchscreen, can't swipe to unlock...
Click to expand...
Click to collapse
The touch driver doesnt load when you are in recovery mode as you can see here - synaptics_i2c_rmi.c#probe. You should try installing the recovery image in boot partition and see if it works.
If it works then rebuild the kernel with that check disabled, so it works while in recovery mode.

Thank you for your reply, a few months ago I managed to build a TWRP with almost all partitions, except "cpefs" partition, working, I've used the kernel source for it, however I've excluded on the main kernel makefile manifest the following files which I've ported from other exynos7570 devices such as the J5 Prime: exynos7570_acpm_draminit_s.fw ; exynos7570_acpm_pedo.fw . By that I've got this result, I'm going to build what you've suggested to look if I can make now the touchscreen driver work, despite that, if you use OTG cable for connecting a mouse, then you can confirm that on this recovery image all of the partition except the one I mentioned above get mounted.
Flash it via Odin.
Wasn't easy, nor impossible. This prototype will hopefully become the effective one.

EyzTOP01.L said:
Thank you for your reply, a few months ago I managed to build a TWRP with almost all partitions, except "cpefs" partition, working, I've used the kernel source for it, however I've excluded on the main kernel makefile manifest the following files which I've ported from other exynos7570 devices such as the J5 Prime: exynos7570_acpm_draminit_s.fw ; exynos7570_acpm_pedo.fw . By that I've got this result, I'm going to build what you've suggested to look if I can make now the touchscreen driver work, despite that, if you use OTG cable for connecting a mouse, then you can confirm that on this recovery image all of the partition except the one I mentioned above get mounted.
Flash it via Odin.
Wasn't easy, nor impossible. This prototype will hopefully become the effective one.
Click to expand...
Click to collapse
good luck for getting twrp working for this device, if you are tired of building, i can build freely

Okay, i'll try to build the kernel with patched touchscreen driver, wish me luck

notnoelchannel said:
Okay, i'll try to build the kernel with patched touchscreen driver, wish me luck
Click to expand...
Click to collapse
Sorry for disappearing for a long time, now i'm really building the kernel
Edit: it failed

just tried to port twrp with Hovatek Samsung Auto TWRP recovery Porter 1.1, give it a try:https://www.mediafire.com/file/92ri...J260YDS-A9-Test-by-autotwrprecporter.img/file
Another thing that can be tried is to take fstab from this build and merge it with old builds and so twrp should be able to mount partitions, this if hovatek build does not boot

UMIDIGI F1 Play

New UMIDIGI F1 Play
New thread for the new model UMIDIGI F1 Play Helio P60 Octa core Mtk 6771
Umidigi F1 Play MT6771 Octa Core 4G LTE 802.11ac 6GB 64GB Android 9 Smartphone 6,3 inches
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Attention this UMIDIGI F1 play is different from UMIDIGI F1 .
the two models have different hardware and different Kernel !
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

Specification
Basic Information
Brand: UMIDIGI
Language: English, Bahasa Indonesia, Bahasa Melayu, Cestina, Dansk, Deutsch, Espanol, Filipino, French, Hrvatski, Latviesu, Lietuviu, Italian, Magyar, Nederlands, Norsk, Polish, Portuguese, Romana, Slovencina, Suomi, Svenska , Tieng Viet, Turkish, Greek, Bulgarian, Russian, Ukrainian, Hebrew, Arabic, Thai, Khmer, Korean, Simplified / Traditional
OS: Android 9.0
Provide Services: Unlocked
SIM slot cards: Dual Nano SIM
SIM Card Type: Double Nano SIM
to Sciarba type: 4G Mobile
Hardware
CPU: Helio P60
Cores: 2.0GHz, Octa Core
External Memory: TF card up to 256 GB (not included)
GPU: Mali G72 MP3
RAM: 6GB
ROM: 64GB
Network
2G: GSM 1800MHz, GSM 1900MHz, GSM 850MHz, GSM 900MHz
3G: WCDMA B1 2100MHz, WCDMA B2 1900MHz, WCDMA B5 850MHz, WCDMA B8 900MHz
Network Type: FDD-LTE, GSM, TDD-LTE, WCDMA
WI-FI: WiFi 2.4G / 5G, 802.11a / b / g / n / ac Wi-Fi
wireless Connectivity: 3G, 4G, Bluetooth, WiFi, 2.4GHz / 5GHz WiFi
4G LTE: B28a / B28b, FDD B1 2100MHz, FDD B13, FDD B17 700MHz, FDD B2 1900MHz, FDD B20 800MHz, FDD B3 1800MHz, FDD B4 1700MHz, FDD B5 850MHz, FDD B7 2600MHz, FDD B8 900MHz, TDD B34 2100MHz, TDD B38 2600MHz, 1900MHz TDD B39, B40 TDD 2300MHz, 2500MHz TDD B41
Screen
The Screen resolution: 2340 x 1080
the Screen Size: 6.3 inches
Screen Type: Capacitive
Camera
Retro camera: 48.0MP + 8.0MP
of camera type: Triple Cameras
Camera Front: 16.0MP
Multimedia Formats
Music Format: AAC, AMR-NB, AMR-WB, APE, WAV
Video Format: H.264, MPEG4
Other characteristics
Additional Features: Alarm, Browser, Calculator, Calendar, Camera, fingerprint recognition, FM, MP3, MP4
Bluetooth version: Bluetooth V4.2
Google Play Store: yes
I / O interface: 3.5mm Output Port, Card Slot Nano SIM / TF, type-C
Sensor: Accelerometer, ambient light sensor
Battery
Battery capacity (mAh): 5150mAh
Battery Type: Not Removable
Package Contents
Back: 1
Phone: 1
Charger: 1
English Manual: 1
SIM Needle: 1
USB cable: 1
Dimensions and weight
Package size: 20,00 x 18,00 x 15,00 cm / 7.87 x 7.09 x 5.91 inches
Weight Package: 0.4200 kg
Product Size: 15.70 x 7.50 x 0 90 cm / 6.18 x 2.95 x 0.35 inch
Weight of Product: 0.1870 kg
Attention this UMIDIGI F1 play is different from UMIDIGI F1 .
The two models have different hardware and different Kernel !​

Recovery modded +
How to receive Right Root in this new Device
F1_Play From UMIDIGI Brand
Attention this UMIDIGI F1 play is different from UMIDIGI F1 .
the two models have different hardware and different Kernel !
This Thread is not for beginners and all the steps made will be down the warrancy at own risk.
This tutorial will guide you through the process of installing a custom recovery image
on your MediaTek based UMIDIGI smartphone and to receive right root access.
Some possible issues that might need your attention:
Custom recovery images of different Android versions are not always interchangeable. For example, you can't install an Android 5.0 recovery on a 4.4 system and so on. Any exceptions are mentioned in the list of recovery images.
At most of the devices, after flashing the TWRP image, first you have to boot into recovery (TWRP) or the stock recovery will be restored.
At some devices, after flashing TWRP, first you have to root your phone (install SuperSU or Magisk) or it won't be able to boot into the system.
Once you've rooted your device, you won't be able to install OTA updates anymore but the only way to update your phone is flashing with SP Flash Tool. Flashing a stock ROM (with the stock recovery) will make you able to install OTA updates again.
At some devices (or specific ROM versions), when powering on your phone to boot into TWRP (power + vol-up), after about 3 seconds, you have to release the power button (even if your screen is still black) and keep only the vol-up button pressed until the TWRP welcome screen pops up or the recovery will be skipped and your phone will boot into the system.
What you need:
Driver for Preloader USB VCOM mode:
Windows 10 already can automatically install it or you can use this:
MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe
SP Flash Tool application:
SP_Flash_Tool_v5.1812.rar
Adb Command for Windows pc:
Command adb for dos/windows
A custom recovery image that fits your phone
Scatter + Recovery twrp
Test 1 Phase......
@Everybody
the custom recovery twrp test1 is already in testng phase.....................​

Procedure to how to flash the Recovery into Umidigi F1 Play
Now is not possible to flash the recovery throught flashtool because there is a bootloader locked so we must go ahead with adb command.
1) download all the previous files;
2) in Android F1 Play in "Settings System details" enter in about phone ot make visible the developer options click several times on about phone ....
3) in Setting System will be now shown the developer menu' enter and switch to visible OEM unlocking allow the bootloader to be unlocked.
4) reboot the phone and with power menu' and volume + in the same time enter in booting menu'.......select fastboot mode.
5) Now in windws pc run the commad cmd or open a ms-dos window and enter in the adb folder ;
6)write the command fastboot devices...and the phone connected with the usb cable must answer the command that is connected..
7) use the command fastboot oem unlock and wait....
8) copy with windows command the recovery twrp.img in the adb folder and renamed it with recovery.img
to flash in the phone use this command : Fastboot flash flash recovery recovery.img
the process will start ...and wait it...
9) make this command to reboot into recovery mode: fastboot reboot.
10) now take the buttons pushed with power menu' + volume + and select recovery mode....
11) in recovery mode will show probably russian language...skip the alert with the arrow back and enter in details menu' on the right top to change the language...
NOW NOT REBOOT INTO ANDROID SYSTEM WITHOUT MAKE THE ROOT STEPS
because the android system protection will flash automatically the recovery original and all of you will lost the recovery twrp flashed before
and all of you will repeit all the preious steps again
How to Root your Umidigi F1 Play
How to Root:
Enter in the Recovery mode.....
You need to FORMAT the partition given TWICE a simple deletion is not enough it seems in Android 7 and upper.
Follow this procedure in this exact order and should solve most problems.
1. Install TWRP through flashtool or adb command and then directly restore in recovery (twrp) do not enter in android system under penalty of twrp deletion and restoration of the original recovery.
2. Select Wipe / Advanced / select date Yes to confirm. When finished, choose Restart, then always in recovery.
3. Choose Wipe Advanced Format DATA again type Yes to confirm When it ends choose Restart always in recovery.
4. Select Wipe and select cache and Dalvik scroll to confirm When it finishes choose Restart and always in Recovery.
5. Now install Magisk 17.1 use this version tested
Magisk 17.1 (Tested)
you can restart in the android system and you will find magisk installed.
For a full root you have to install from the play store busybox app and install the busybox binaries at least in sbin and bin (system folders) the app will guide you
Busybox see here:
Busybox in the google playstore
I prefer this app to others because of its track automation that doesn't require much experience.
@Everybody
the custom recovery twrp test1 is already in testng phase..................... ​

Reserved future use 3

I'm surprised this phone isn't getting more noticed! There isn't much options for sub-$200 phones with USA bands from what I can tell, and this supports the usually omitted 4G Bands 2 and 4. From what I can tell, UMIDIGI is lacking a bit in the software optimizing department, but the hardware here looks pretty great! Sounds like this phone has real potential for the sub-$200 US market.

Project Treble GSI images?
After applying the custom recovery image; has anyone tried the [gsi] project treble images noted in the UMIDIGI F1 post to see if they work on the "play" verison of the F1 device? https://forum.xda-developers.com/android/development/psa-project-treble-t3917284

@mattybaby,the umidigi f1 and f1 play is different inside.
They have hardwares differently and the kernel is different, so attention to flash that is build for different models!

ghost45 said:
@mattybaby,the umidigi f1 and f1 play is different inside.
They have hardwares differently and the kernel is different, so attention to flash that is build for different models!
Click to expand...
Click to collapse
Understood @ghost45 I wanted to know if any of the owners of the umidigi f1 play have gotten any of the project treble images to work like those on the umidigi f1 device?

I have installed the Bliss ROM A/B with gapps. So far I haven't noticed any issues. I just finished install about 2 hrs ago though. I will update with any news.

zironia said:
I have installed the Bliss ROM A/B with gapps. So far I haven't noticed any issues. I just finished install about 2 hrs ago though. I will update with any news.
Click to expand...
Click to collapse
Update... Used blissrom for about 3 hours. When I restarted the phone it would not boot. It kept getting stuck in a bootloop. I still have my recovery but I cannot get it to boot. I use my nandroid backup but it still will not boot. I will need to use SP tools to recover my phone.

I am awaiting my F1 Play to be delivered soon and look forward to using TWRP with it.
Is it the very first thing I should do before anything else or are there recommendations how to proceed with a brand new device. I don't want to brick it on day 1.
I have quite some experience with flashing recoverys and ROMs, coming from a Samsung Galaxy S3 and S4 with LineageOS ROMs of various versions (14 through 16), and even CyanogenMod before those.
Thanks for any hints and pointers!
Cheers,
Sascha

You really can't brick the mediatek. With SPtools your can recover pretty much anything.

zironia said:
You really can't brick the mediatek. With SPtools your can recover pretty much anything.
Click to expand...
Click to collapse
Good to know, thanks! Can't wait to finally get my hands on the device. Got the notification of the shipment just yesterday, and it will still be two to three weeks until I have it. We'll see...
Posted with my GT-I9300 via Tapatalk

I installed pixel experience 3/24 a/b gsi build last night and have been using it today with great success. The camera app with the rom doesn't work right though. I rooted the phone with magisk and enabled camera 2api then downloaded gcam from the play store. It works fine. None of the issues I had with Bliss Rom.

gcam night sight
zironia said:
I installed pixel experience 3/24 a/b gsi build last night and have been using it today with great success. The camera app with the rom doesn't work right though. I rooted the phone with magisk and enabled camera 2api then downloaded gcam from the play store. It works fine. None of the issues I had with Bliss Rom.
Click to expand...
Click to collapse
@zironia Does Night Sight work with the gcam from the google store (com.google.android.GoogleCamera) ? Do the photos (HDR) look better than the stock camera before the ROM replacement?
Thanks

No. It's gcam 4.1 from the play store. Everything works fine but we will need a developer make a higher version for this phone.

Stock camera takes better pictures. Gcam pictures are good but not like stock. Color are washed out. We need someone to port the stock camera to gsi roms.

@ghost45 thanks for the thread and the direction.
I've had the f1 play for several days.i was lil scared to try this phone but the price was right and I had to try .Now that it's in my hand I absolutely love it.Clean,fast,and the screen is a pleasure.no issues with it.works great on T-Mobile.im really impressed with the design,software and battery life.Hope to see the f1 play community grow and get it's own dedicated forum.
Oh yeah ... @zironia thanks for testing and sharing your experience.

Mine is on the way and it's supposed to be delivered next Tuesday. Can't wait to get my hands on it. First thing I'll try is to root it. [emoji16]
Gesendet von meinem GT-I9505 mit Tapatalk