Database Info

Alcatel One Touch Hero / TCL Hero N3

Alcatel One Touch Hero (OT-8020D) / TCL Hero N3 (Y910)
1. Specs
- Dual SIM (standby)
- MediaTek MT6589T (4 x 1.5 GHz)
- 2 GB RAM / 16 GB ROM
- 6" IPS OGS FullHD (1080 x 1920)
- 3400 mAh
- stylus (Alcatel OT-8020D only)
2. ROMs are in post #2
3. HowTo and Utilities are in post #3
4. Links
Official pages: Alcatel, TCL
5. Other stuff
Alcatel One Touch Hero in France, Serbia, Russia, Ukraine
TCL Hero N3 in China

ROMs Section
Source Code: Link
Beware of SMSReg
TCL Hero N3 (Y910)
01003 Full ROM (install via stock recovery)
01005 Full ROM (install via stock recovery)
01007 Full ROM (install via stock recovery)
01010 Full ROM (install via stock recovery)
01011 Full ROM (install via stock recovery)
TCL Hero N3 FOTA Updates
Alcatel One Touch Hero (OT-8020D)
Russian DUMPs
01002 - Full dump (install via SP Flash Tool)
01003 - Full dump (install via SP Flash Tool)
01004 - Full dump (install via SP Flash Tool)
German DUMPs
01001 - Full dump (install via SP Flash Tool)

HowTo and Utilities
TCL Updater S 2.8.1
Alcatel Mobile Upgrade S 4.0.6
Alcatel Mobile Upgrade S 4.1.3
Alcatel Mobile Upgrade S 4.3.1
SP Flash Tool
HowTo Root
1. Before rooting you must turn option on: Settings/ Developer Options / USB Debugging
If you don't see menu Developer Options then go to About Phone and click text Build Number 10 times
2. Follow instructions from here: http://forum.xda-developers.com/showthread.php?t=2434453
HowTo Install CWM recovery
1. Download recovery
ClockworkMod recovery (CWM) 6.0.1.2 (Custpack backup) - https://mega.co.nz/#!o9UlVbID!aOJEOWJt479glvWiJo8jjn7HrutBpksePsS9AxVrsKM
ClockworkMod Recovery (CWM) 6.0.3.3 (NO Custpack backup) - https://mega.co.nz/#!IpM22RCB!eqaJUlUXSGVv0cXS1BtNqzOUiotvHKiJVAEt7559oZ0
2. Don't forget rename to recovery.img
3. Connect phone to PC and copy recovery into root of media-disk
4. Download and install Mobile Uncle Tools: https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox | https://www.dropbox.com/s/8ro1gsp04....toolbox-12d21e28b11a68788b789a9b9bbcc6ad.apk
5. Run MobileUncle Tools, allow root permissions to this app, choose Recovery option in menu, choose recovery.img in section "recovery file in sdcard" and complete process by flashing recovery
http://3.bp.blogspot.com/-PH7dJ880W...00/Flash+recovery+using+Mobileuncle+Tools.jpg
HowTo Install Google Apps
1. You must have CWM-recovery
2. Download gapps from here: http://goo.im/gapps/gapps-jb-20130812-signed.zip
3. Connect phone to PC and copy gapps into media-disk
4. Reboot into recovery and flash (to reboot: turn phone off, wait 5 sec, turn on by pressing and holding VolumeUp + Power)
HowTo Flash ROMs via SP Flash Tool
Flashing process is similar as in Idol X: http://forum.xda-developers.com/showthread.php?t=2451831
Before flashing the ROM its strickly recommend taking a backup with Uncle Mobile Tools, in case something goes wrong with this guide
Backup/Restore Wihout CWM
Choose scatter-file from ROM only to avoid misbehavior (different roms = different scatters)
Beware of flashing preloader and formating all partitions
HowTo Make Full Dump/Backup
http://forum.xda-developers.com/showpost.php?p=51077322&postcount=116

Thank you sir, the rom will be useful for backup
Kindly update if there is another custom rom for this lovely phone
Sent from my TCL Y910 using Tapatalk 2

Just got mine and updated to latest firmware it had. This device's is CRAZY good for its cost, the screen ratio is amazing.
Will give these a whirl just now, Thanks!

Thankss

the rom in post #2 is original rom or is custom rom?

Where can I get one of these that will work in the US with AT&T HSPA+? I see that they have several model numbers:
Single SIM Versions: 8020 / 8020A / 8020Y
Dual SIM Versions: 8020D / 8020E
NFC Version: 8020Y
What are the differences?
Sorry if this is not the place to ask about this.

@gerardo66 - i think it is the original stock one, since that version is the latest my TCL upgrades to.
@luvboox - The specs on the Alcatel page say what each model differs in every category.
Networks: GSM Quadband 850/900/1800/1900, UMTS 850/1900/2100 (8020A / 8020E / 8020Y); UMTS 900/2100 (8020/8020D).
Click to expand...
Click to collapse
Google tells me AT&T use the 850 and 1900 MHZ bands. Not sure if that's correct, but if it is, you want the A, E or Y editions - The non-lettered or D versions don't support those bands.

Hi there, any update?
I've heard 01006 is out
Also, maybe someone kind enough to collect all roms / mods for y910, such as Lewa, miui, or modified factory rom
My review after using this beauty for 3 weeks:
1. Very handsome look, thin, pure black screen while off
2. Very happy for the battery, I've do the test, and manage to get 5.5 hours screen on!
3. The stock rom is full of bloatware!
4. hard to find appropriate forum in English, I only found in Russian, Spain, and of course Chinese language (Google translate is your friend)
5. Lucky there is root and cwm, at least it make us able to "do something" with this stock rom
6. Very good phone, this is the phone that have design, not just "another mtk phone"
Sent from my TCL Y910 using Tapatalk 2

No 01006 here through the official ROM.

Just update last night using updater
{
"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"
}
Sent from my TCL Y910 using Tapatalk 2

Anyone has access to bbs.anzhi.com?
Interesting threads are hidden(
http://bbs.anzhi.com/thread-8719365-1-1.html
http://bbs.anzhi.com/thread-8714702-1-1.html

Very good news.
Alcatel/TCL posted source code: Link

how we update?

Had the update myself. Through the usual about-system update screen.
Good to see the source released, lets hope its usable. I'm waiting to see how OmniROM handle their Oppo r819 ROM and hopefully we might use both to create a base for omni/CM.
Sent from my TCL Y910 using Tapatalk
EDIT: Ah, It doesn't like updating my CWM/rooted install. Did you revert those changes before applying the update? or you still have the stock recovery, perhaps?
EDIT2: OK, apparently one APK was missing from my system that the update expects to find, PartnerBookmarkProvider.apk, so i removed the patching for that from the updater-script. Now i get some setperm failures, need to see whats up with that.
EDIT3: set_perm on /system/xbin and /system/vendor/pittpatt failed because i don't even have those directories for some reason; removing them allows the update to complete. After that, im on latest firmware, CWM made sure to alert me to disabling the stock recovery restore and keeping root intact.

gerardo66 said:
how we update?
Click to expand...
Click to collapse
You can use the updater given by op
I'm using the pc style
Just open the update exe in pc, plug in your hero (off), it will begin the process
Precaution:
1. 01006 takes more than 1gb, be prepared
2. Make sure you back up your rom (copy to pc), and your data as well, because it will completely erase your phone
3. Make sure phone battery full; notebook is recommended (not dependen on power supply); good Internet connection (fast connection lead to faster process, interrupted connection will be horrible)
I found some bugs, most annoying is the "network location failed", which used to appear
I really hope the source code can bring more goodies, and also can be used for tcl
Sent from my TCL Y910 using Tapatalk 2

Friends, who has Alcatel OT-8020D, please post product id and version of Rom. It looks like 8020D-xxxxxxx, where x - any symbol.
Ex. 8020D-2AALRU1 - product id in Russia. Russian version has 01002 Rom with german, french, russian, ukrainian and two english (uk, usa) languages.
You can find product id on the retail box.
Or dial *#2886#, choose manu, then tracability, then find cu-ref string.
P.s. chinese unicom version product id: Y910-2ALCCN1
Отправлено с моего ALCATEL ONE TOUCH 8020D через Tapatalk

FOTA Updates
FOTA Updates for TCL Hero N3 (Y910)
from 01003 to 01004 (48 MB)
from 01004 to 01005 (60 MB)
from 01005 to 01006 (10 MB)
from 01006 to 01009 (33 MB)
Requirements: TCL Y910, stock ROM without system changes, stock recovery
https://mega.co.nz/#F!shsRAQQY!IKc83TfNwbMd2AyMF5FyjQ

Thanks, could come in handy. Is there a full stock 01006 rom somewhere?
Sent from my TCL Y910 using Tapatalk

installing gapps on Huawei G730-T00?

I can't find much information on Huawei G730 outside Chinese forums. This phone runs on android 4.2.2 with no gapps. I managed to root the phone with a Chinese tool on PC (I am not endorsing this tool). towelroot apk didn't work for me
I tried different ways to install gapps, initially I installed google play store and google service framework from Huawei market. It worked with one exception, not syncing contacts
Then I tried to flash different versions of gapps (from goo.im and other sources) for 4.2 and all I got was google service framework crashing. With some gapps packages I don't even see the apk after flashing. The custom recovery (CWM and TWRP) does not seem to work very well and I noticed mounting failures (the flashing can succeed when the OS can't even mount the filesystem?)
Also I tried to put google offical apks from apkmirror into /system/apps and Google Service Framework still crashes (again I tried different apks). Any thoughts on how to get gapps to work on the MTK 4.2.2 phone (MT6582M)? In China Google services are completely censored so there's very little interest on Chinese forums to get gapps working on this phone (China Mobile version)
Key Specifications/Special Features:
1) Brand and model: Huawei G730-T00
2) Operating system: Android 4.2.2
3) CPU: MT6582M Quad Core 1.3GHz
4) RAM: 1GB 5) ROM: 4GB, about 2GB available
6) SIM card quantity: dual SIM
7) Camera: dual cameras
8) Connectivity: 1 x SIM slot, 1 x micro SIM slot, USB 2.0, earphone 3.5mm, TF card (micro SD card) slot
9) Supports G-sensor, proximity sensor, light sensor
10) GPS: supported, also supports AGPS
11) Material: plastic
12) Network mode:
Dual SIM/dual bands network:
1) Network type: TD-SCDMA and GSM network
2) Band (3G): TD-SCDMA B34 (2010-2025MHz)/B39 (1880-1920MHz); band (2G): GSM 900/1800/1900MHz
3) Wi-Fi: 802.11b/g/n wireless internet
4) Bluetooth: V4.0

As you can see, there's practically no support for any G730 version in this forum. I've been trying to unlock the bootloader of my G730-U251 and install custom recovery to no avail. Though I've rooted my phone easily with Framaroot, and my version fully supports Google. Guess we just can't have everything from Huawei...

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,

[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 S3 Pro

New UMIDIGI S3 Pro
New thread for the new model UMIDIGI S3 Pro Helio P70 Octa core Mtk 6772
Umidigi S3 PRO MT6772 Octa Core 4G LTE 802.11ac 6GB 128GB 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"
}
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: Multi language
OS: Android 9 Pie
Provide Services: Unlocked
SIM Slot cards: Standby Dual
SIM Card Type: Double Nano SIM
to Sciarba type: 4G Mobile
Hardware
CPU: Helio P70
Cores: 2.1GHz, Octa Core
External Memory: TF card up to 256 GB (not included)
RAM: 6GB of RAM
ROM: 128GB
Network
2G: GSM 1800MHz, GSM 1900MHz, GSM 850MHz, GSM 900MHz
3G: UMTS (WCDMA) / HSPA + / DC-HSDPA: BAND1 / 2/4/5/6/ 8/19
Network Type: FDD-LTE, TDD-LTE , WCDMA
WI-FI: WiFi 2.4G / 5G, 802.11a / b / g / n / ac Wi-Fi
wireless Connectivity: 3G, 4G, Bluetooth, GPS, WiFi, GSM, 2.4GHz / 5GHz WiFi, A-GPS , WiFi Dual Band
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 B38 2600MHz, TDD B39 1900MHz, 2300MHz TDD B40, B41 TDD 2500MHz
Screen
The Screen resolution: 2340 x 1080
the Screen Size: 6.3 inches
Screen Type: Capacitive
Camera
Auto Focus: Yes
Retro camera: 48.0MP 12.0MP +
Functions Camera: Beauty face, face recognition
of Camera Type: Cameras Triple
Flashlight: Yes
Camera Front: 20.0MP
Fire Touch: Yes
Video recording: Yes
Multimedia Formats
Live Wallpaper Support: Yes
MS Official format: Excel, PPT, Word
Music Format: MP3, AAC, AMR-NB, AMR-WB, APE, WAV
Picture Format: BMP, GIF, JPEG, JPG, PNG
Video format: MP4, H .264, MPEG4
Other characteristics
Additional Features: Alarm, Browser, Calculator, Calendar, Camera, E-book, fingerprint recognition, fingerprint release, Gravity sensing, Gravity Sensor System, light sensor, Light sensor system, MMS, Notification, proximity Sensor, Sound Recorder, Video Calling
Bluetooth version: Bluetooth V4.2
Google Play Store: yes
I / O Interface: 1 x Nano SIM card slot, 3.5mm audio output port, Microphone, Card Slot Nano SIM / TF Speaker, Type-C
Sensor: Accelerometer, E-Compass, geomagnetic sensor, gravity sensor, gyroscope sensor proximity
Sound Recorder: yes
Battery
Battery capacity (mAh): Built-in 5150mAh
Package Contents
Back: 1
Phone: 1
Charger: 1
SIM Needle: 1
USB cable: 1
Dimensions and weight
Package Size: 18.50 x 18.50 x 4.20 cm / 7.28 x 7.28 x 1.65 inches
Weight Package: 0.5840 kg
Product Size: 15.70 x 7.50 x 0 85 cm / 6.18 x 2.95 x 0.33 inch
Weight of Product: 0.2170 kg​

Recovery modded +
How to receive Right Root in this new Device S3PRO From UMIDIGI Brand
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.1904
Adb Command for Windows pc:
Command adb for dos/windows
A custom recovery image that fits your phone
Twrp By material Design test 1:
Scatter + Recovery twrp
Twrp By material Design test 2:
https://www.mediafire.com/file/r486...wrp_323_Mat_Des__UmidigiS3_Pro_test2.rar/file
New Twrp 3.3.1 test 1:
http://www.mediafire.com/file/kajeg9bbcb0kb55/recovery-twrp-3.3.1_Umidigi_S3_Pro_Test1.rar/file
Procedure to how to flash the Recovery into Umidigi S3 Pro
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 S3 Pro 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) in Setting System --> the developer menu' --->debug usb activated and connected the usb cable to the phone and the other side to the pc...
5) Now in windows pc run the commad cmd or open a ms-dos window and enter in the adb2 folder
(adb folder when you extraced the adb command and check with adb command);
Type: adb devices .....if the device is recognized type: adb reboot bootloader
6) SEEMS NOT RUN THIS STEP IN THIS DEVICE
(reboot the phone and with power menu' and volume + in the same time enter in booting menu'.......select fastboot mode.)
7) do not remove the usb cable.....now you entered in Fastboot menu...
write the command fastboot devices...and the phone connected with the usb cable must answer the command that is connected..
8) use the command
fastboot oem unlock
o
Fastboot flashing unlock
and wait checking the device screen.....
9) 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...
10) make this command to reboot into recovery mode: fastboot reboot.
11) now take the buttons pushed with power menu' + volume + and select recovery mode....
12) 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 S3 Pro
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..................... ​

This could be best in class for the price ($279.99 on sale). What's the developer community like for Umidigi? Is bootloader normally unlockable etc? Very tempting compared to Redmi Note 7 Pro

Just purchased one, well soon see how good.

any word on root?

THANK YOU
Woooo-hooooooo! got me one ordered....
I cannot wait to see That you guys (and ladies) have
in store for this phone. hopefully as many goodies as you have for galaxy s5
-----and,......thank you ALL for all of that, by the way.....you guys are
:good::good: !!!AWESOME!!!:good::good:

Don't get your hopes up... there is no root for the S2 Pro still. I read something about efuse protection but unconfirmed.
Hoping a dev will try to root this S3 Pro
...and that UmiDigi learned from their previous mistakes and deliver a great phone with no camera/battery/charge-port issues, that is really running Pie.
It is a big gamble, but one I was willing to make for $289.
BOUNTY: If a Dev does make a way to root my S3 Pro, I will send them a free S2 (lightly used, doesn't always charge but does sometimes, and always works when plugged in). -lol, if they want it.
(Bounty not valid if it turns out the phone is easily rooted using available tools)

Hi, yes when the device will arrive in my hands i will continue to make a review and i will open a specific detailed thread about how to receive right root and others mods on it!

Can't wait for my Umidigi S3 Pro that is due to arrive in 1-2 weeks.
Generally, do you guys know what is Mediatek devices development like? Any hope for the P70 processor to get some custom ROMs?
Sent from my Lenovo P2a42 using Tapatalk

stazz83 said:
Can't wait for my Umidigi S3 Pro that is due to arrive in 1-2 weeks.
Generally, do you guys know what is Mediatek devices development like? Any hope for the P70 processor to get some custom ROMs?
Click to expand...
Click to collapse
Is too early to speak about the custom rom... This device is not arrived to anyone and no one firmware is pubblished yet!

Yeah, true, but my question is about Mediatek devices development in general. What could we hope for?
Sent from my Lenovo P2a42 using Tapatalk

Project treble
ghost45 said:
Is too early to speak about the custom rom... This device is not arrived to anyone and no one firmware is pubblished yet!
Click to expand...
Click to collapse
Will treble project be possible on this device?

totmakina said:
Will treble project be possible on this device?
Click to expand...
Click to collapse
Probably yes when it will arrive in my hands..

ghost45 said:
Probably yes when it will arrive in my hands..
Click to expand...
Click to collapse
Thanks. The S3 pro will be an excellent mobile. With twrp already impressive !!

I don't know guys... I'm worried about this phone and the camera app. Do you have any informations about slow motion video and night mode photography? For this Sony sensor and this processor should be super easy...
But te umidigi team is really small and I'm worried that they don't know how to use potential of this Sony camera sensor and mediatek processor.
I hope I can install GCAM or openCamera
I see they have huge problem to sent s3 pro to indigogo customers but what about aliexpress customers...? How long we have to wait for it?

The twrp is pubblished in official forum... I will update also this thread.. I need a period of test phase....

Good Notice! TWRP!!
ghost45 said:
The twrp is pubblished in official forum... I will update also this thread.. I need a period of test phase....
Click to expand...
Click to collapse
Hello Ghost! I already saw the publication of your post in the official forum. Now download the twrp and also download the official rom to have it in reserve.
Hopy bought the s3 pro. I just hoped that the official rom would come out to carry a twrp that already had realme u1 if no one did it. But luckily you posted one that will be installed when I get the smartphone. When I arrive, you can count on me for any help. It would be nice to have treble for this team. We trust you !!

Hi
Just received this phone, do you know if xda will open a new dedicated forum?
Thx

cy-rock said:
Hi
Just received this phone, do you know if xda will open a new dedicated forum?
Thx
Click to expand...
Click to collapse
How long did it take to receive it, my friend? I asked for it yesterday and I already want to have it in the. Hands