yashsingh1/xdaforums huggingface dataset:
[Android General] Rwmega:
[MENTION=9914104]croquettelehamster[/MENTION] glad the boot.img trick worked for you. This last update seems to have fixed my screen (Yay) but sadly it didn't help everyone.

To anyone reading if you choose to flash just the boot.img file to your phone it will not delete your data/apps/or settings; and best of all it does not change your modem.

Prior to the 0705 update I was using the 0605 system update with the EU boot.img of the 0621 download (that one was on the thread of the EU 0605 update). I didn't want the 0621 full update because it was EU and that made my reception in the US horrible.

It doesn't hurt to try to flash other boot.img files from the other updates from umidigi. If your phone was working before hopefully you can find the boot.img that will fix or make your phone usable again. Just select download option on SPFT, use any scatter file, uncheck everything but the boot.img and select the boot.img of your choice from your downloads, and flash.
[Android General] derricksrs:
yeah me too flash back 051310 boot.img and is working fine now.
[Android General] stazz83:
My phone just updated to the 20190708-0919 version (EU). I imagine Umidigi is trying to address the touchscreen issues. I haven't had those since the last few updates, so I can't tell the real difference between the last builds.
[Android General] derricksrs:
:) yeah they are trying hard on the touchscreen issue.
[Android General] derricksrs:
At least there is no need to sleep then wake up although there is still some lag in on the upper portion of th screen.
[Android General] I opus l:
Woke to my screen on in TWRP mode last night around 2AM. Tried rebooting, but it looped back to recovery. It's still encrypted because I can't get past it even though Merkurial was gracious enough to show how he did it. Completely panicked because I rely heavily on my phone for work and I can't just restore a backup from TWRP. Went downstairs grabbed my micro SD card I was using this weekend with it. I had the last 2 Umidigi updates on it. Flashed the latest boot.img and recovery.img from TWRP. It booted to an Android error screen with a cache error. Pressed power+ vol up, let go of vol up, and got into stock recovery. Went down to wipe cache and rebooted back to to my system. All better. If your encrypted, TWRP won't let you wipe the cache anyway. Hopes this helps someone out there.
[Android General] flyingmk:
Waked up this early morning by my S3 pro bootlooping. Beside forced go into Recovery the phone won't do anything else.

So I downloaded the 2019070622_g38v71c2k_kw_s3_pro rom and trying to flash with SPFT, the default Download mode failed with error and I was asked to use Format+download, which was done successfully.

But upon restarted the phone, I immediately noticed two big red "Inactivate" on the right-upper corner of the screen (for TEE and Google), and MEID, IMEI 1/2 all lost.

It can only connect to WiFi now, no calls no data even with correct Sim card (my network carrier is recognized).

I tried re-apply the OTA via Recovery before doing SPFT and it was failed with error as well.

Contacted with Umidigi and waiting for reply. What should I do now?

Any help would be appreciated!
[Android General] MikeyLee:
Ordered mine tonight and should be here Friday. Got a smokin' deal on Amazon with a $60 voucher they had. Final price $239!
[Android General] croquettelehamster:
More and more people are currently discovering that their S3 Pro has the touchscreen grounding issue.

Amazon refunded me yesterday and I will send back my S3 to them today.

I will paste here the three posts and replies I wrote on the UMIDIGI S3 Pro official forum since yesterday : https://community.umidigi.com/forum.php?mod=viewthread&tid=18785&extra=&page=5

These posts may help people that will discoverer that their phone has this issue. I also made a quick video before packing the phone to ship it back to Amazon :

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

I made a quick video before packing the phone to ship it back to Amazon.

This video may help you to check if your S3 Pro has the touchscreen grounding issue.

This is the end of the story for me, I will not buy another UMIDIGI S3 Pro. I currently use a MI 9T 6/128 and a K20 Pro 8/256.

Honestly, the S3 Pro was really a beautifully made phone, with very good build quality. I really regret that this model has been plagued by touchscreen problems caused by manufacturing / assembly issues. UMIDIGI tried to hide these issues with software updates that reduced the symptoms. In the end , they were unsuccessful.

Some subset of the userbase has always been affected by touchscreen issues. When they "solve" (I would rather use the term "hide") the problem for some people by tweaking the touchscreen parameters in a new update, other people who never had any previous touchscreen issues are suddenly affected by touchscreen problems. This is what happens since launchday.

The root of the problem is simply a manufacturing / hardware issue on some units (I think that a lot of S3 Pro are affected, this could be a design flaw... The phone design and conception phase was probably rushed in order to meet Indiegogo's time limits and delays).

Good luck to everybody ! I sincerely wish and hope that you will all be luckier than me with the UMIDIGI S3 Pro !

Big thanks to ghost45, Rwmega, and all other participants in this thread !
[Android General] Rwmega:
[MENTION=7539878]flyingmk[/MENTION] you selected the one option umidigi says not to use according to their site.

https://community.umidigi.com/m/?a=viewthread&tid=16931

Read their tutorial, they have a link get imei's again but I think you basically have to use a generator unless you saved your old ones somewhere.

Sorry hope this helps
[Android General] RaRa2019:
Is there any way to get google camera apk for the umidigi S3 pro ??
[Android General] flyingmk:
Sorry if I don't make it clear [MENTION=7286308]Rwmega[/MENTION], format is the only option I can flash the rom. I got the "PMT changed" error with default download mode.

Anyhow, after some more reading on this site and googling, I decided to give SN Writer a try and successfully get all MEID, IMEI 1/2 back to phone, and 4G, call sms all work normally.

Only thing left now is that ugly TEE/Google inactivate thing permanently on the screen :(

Little bit tricky to use SN Writer though

- you need the latest ver 1.1916 which support MEID

- I used the same vcom driver which is used for rom flashing

- using the AP / MD files from the rom package

- config the tool per tutorial, try first by connect the powered off phone

- most likely the handshake will timeout, now look at your phone screen, there is a tiny text on the left-lower corner says "meta mode", now go back to tool's option, check Already in meta mode, try again, it will go through

- in my case the process still failed at the end when it is trying to make nvram backup but the numbers are written back to phone correctly
[Android General] Zahr:
I had to use sn writer as well for that same issue & was able to get Google Certificate back/get rid of the TEE GOOGLE red text.

I used SP Flash Tool 5.19 to flash the stock ROM.

In SN Writer I left only wifi & BT checked in the upper left write option section to auto generate then saved.

Next, loaded the appropriate database files & next I just hit start & it passed.

After seeing the red text was gone upon reboot I then checked IMEI & MEID, typed them in, reran the process again & it passed.

I didn't pick the already in Meta option, just unplugged then plugged the cable in & it continued.

Hope this works for ya.
[Android General] flyingmk:
Thank you [MENTION=4261514]Zahr[/MENTION], that is a very helpful info which I have to try, and glad you got everything back for your phone.

Could you please just confirm some info for me:

- The red text things were caused by "format+download" flash in your case?

- There are two edb files in the rom package (the names are similar but sizes big diff, couple of hundred K vs 17MB, I was using the big one), which one you were using in your case?

Thanks a million.
[Android General] Zahr:
I worked 2 days trying to get it fixed & ended up needing to update system drivers beforehand before I was on the brink of totally giving up on being able to fix it.

In my case of the red text, I think it was caused by using the "format whole flash except bootloader" under the Format tab in SP Tools in an older version of SP Tools because I got the PMT changed for the ROM msg.

SPFT 5.18 would fail every time so I found a newer version 5.19 & first reflashed the 4/30 dated ROM without getting the PMT msg.

The SN Writer I used was the NON EU one since I'm in the US.

I only left BT & WiFi write options ticked in the Write Options for getting rid of red text.

In the MD1_DB spot I used the one with "MDDB.META" at the beginning of the file name, size 289kb.

In the AP_DB I used the one without the "ENUM" at the end of the file name, size 168kb.

Let me know if it works.
[Android General] flyingmk:
Thx for your details [MENTION=4261514]Zahr[/MENTION] but unfortunately the red text are still there :(

You mentioned that "Non EU" version of SN Writer, where can I download that? I'm in Canada.
[Android General] Zahr:
https://community.umidigi.com/m/?a=viewthread&tid=18634

It's in the "What you need:" part in blue font color. The last one "S3 PRO non EU:" clicking on the link will immediately download the SN Writer.
[Android General] flyingmk:
Thank you, thank you thank you... [MENTION=4261514]Zahr[/MENTION], you are the champion! That special SN Writer immediately worked.

Now my phone back to normal, what a relief ?
[Android General] CAPPIE37:
battery time

for using only as a PHONE, this thing is GREAT......

18, yes, i said EIGHTEEN days since last charge, and i still

had 23% left.. loaded with well over 100 apps.

i dont know how they do it, but just the battery time is

worth $300...

i had a pic to upload buy dont know the URL?

pic is on my computer
[Android General] Zahr:
I'm very glad that it worked for you! I was super excited when I finally seen that the writer said "OK" during the handshake stage & even more so when I seen "PASS" show up.
[Android General] MikeyLee:
Has anyone got this device working on MetroPCS? I cannot get it to work to save my life.
[Android General] Rwmega:
I just helped a friend of mine get a phone (not s3 pro) on metro, you have to go into a store. Tell them you want to activate the device on their service, and they have to manually put the IMEI into their system. Once that is done reboot phone with Sim in and you should be good.

We have two imei's so be sure to give them the one for the slot you will be using, and be prepared metro charges to activate any phone on their Network, $15 to $18.

Unlike att or tmo where you can just pop in Sim into any phone, metro makes everyone "register" IMEI before being allowed on their Network
[Android General] MikeyLee:
Cool I'll give that a try and see if it works. I already have Metro but swapping the SIM out from my Huawei device to the S3 isn't working. Hopefully the IMEI is the issue and it will work.
[Android General] Zahr:
My carrier charges $25 upgrade/activation in-store. I call it a "clerk setup fee" 'cause they won't hand over the phone even if you tell them you know how to set up the new phone.
[Android General] GarfieldM0:
oses?

Hi,there Is Chance to install win10 arm or lot or arm Linux into dual boot...
[Android General] MikeyLee:
So, got the phone got the OTA and got the Metro issue worked out. Now about Root? Has anyone been successful in rooting without it affecting the device? And most important, is there a way to get the damn Google Search widget off of the stock home screen? I haven't been able to.
[Android General] derricksrs:
My advices is backup nvram. Nvcfg using twrp so any mishaps while flashing custom rom. U could just flash the nvram, nvcfg to get back your imei.
[Android General] shookica:
I finally decided to give up on the S3 Pro and went back to my trusty Lenovo P2.

There were just too many issues with the phone like bad mobile/wifi reception, wifi dropping issues, touchscreen issues and dissappointing camera app. I don't even trust some of the bloatware stock system apps that come with the phone, like the suspiciously large flashlight app, and several hidden ones. On top of that the screen cracked on the first fall it took, from about 1m.

About the only thing I did like is how easy it was to unlock and flash the phone, and install treble images.
[Android General] mbsans:
Rooting the phone is easy, just need to unlock it first. Install TWRP then magisk, then you're rooted. However when rooted you cannot update OTA, when I tried, the phone boot-looped into TWRP, and had to do a full reset with SP flash tool, lost one full day. Now I've frozen "Wireless Update" with Titanium Backup.

As for your second question, I got rid of the Google Search widget using the NOVA launcher, otherwise it's not possible to get rid of it (at least for me), even after you uninstall or freeze it.

---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------

My phone doesn't seem to be affected by this hardware grounding issue. So far it's working properly, thank God!

Thanks for the advisory!
[Android General] Zahr:
I've experienced a touchscreen unresponsive only a couple of times, but it went away in a few seconds & hasn't happened again.

As far as rooting, I got BL unlocked BUT could never get TWRP flashed using adb. CMD would sit at "waiting for device" or say no recovery image found even though there is one in the folder CMD is opened in. So I had to use SPFT to flash TWRP. Noticed BL relocked, but TWRP & root remained intact. All good though.
[Android General] Davindy:
I don't understand why all you guys run the risk of installing TWRP? You guys are wiping your NV partitions, creating boot loops, and still running the half-assed version of Umidigi's Android with options removed...

All you need to do with this phone is unlock the boot loader, then push a new Treble based ROM using fastboot and you're done! Everything works perfectly for me, I'm running BlissROM and haven't had any issues in 4 weeks now. The battery is amazing, even better than stock! If you just want a custom ROM that will work and have all the features and then some of the latest Android then this is all you need to do! Always take a backup of your NVRAM before doing anything to your phone just in case, but you won't need it if you just follow these steps!
[Android General] I opus l:
I tried like hell to get bliss going. Got it installed and it looked beautiful, but could not get it to recognize sim cards.
[Android General] Davindy:
I had this same issue when I first got my S3, you must have wiped your NVRAM somehow, clearing out your IMEI's....but not sure how you restored it either if that's the case...?

But using my method it will work. Just flash everything back to stock using the SP Flash Tool and then fastboot a Treble ROM over to your phone if your boot loader is already unlocked.

It truly can't be any easier, and it's so much safer.
[Android General] MikeyLee:
Does anyone have the issue of this device defaulting to the Recent Apps screen when you unlock it?
[Android General] Chrisdorum:
it was mentioned that they contracted companies and that the total amount ofpieces in the phone is like 3k pieces assembled into the phone. Now here is an interesting thing tho. Some users phone will show S3_pro while others will have A-Gold, and A-gold is also a manufacturer and this is the version I have and so far I have had no hardware issues that people are talking about. Altough It seems that wifi and bluetooth signal is pretty poor thats what I thought was a problem on my phone but its the design thats faulty. Comparing to my old xiaomi redmi note4x it gives pretty good signal where 2 bars will still give internet, while my phone will either not see the acces point or gives me incorrect bars (2 bars = no internet) I will probably buy another xiaomi in the future at least they have some pretty good networking gear (courtesy of papa huawei)
[Android General] Zahr:
Last couple of days including today screen problems have occurred. Touch capacitive buttons are going haywire like they're being touched rapidly, all at the same time or held down. Status bar acts like it's being slid down briefly. All while I'm not even touching the phone lol No moisture has gotten into the device nor has it been dropped.

Data signal is atrocious now as compared to before I had to regain IMEIs MEIDs & GC.

So I'm dropping to a previous ROM version. Not really worried about the camera as I'm not too into taking photos.

Actually going to try the boot.img trick to see if that fixes this screen.
[Android General] mbsans:
Great point, I'd like to install Bliss OS, but maybe you can clarify a few things for me:

1- When you say fastboot, what are the exact steps, what's the command, just copy the whole image over? I'd appreciate if you post a link on how-to.

2- By installing Bliss OS, I'd like to completely disable the encryption, is it possible?

3- I'd really like to have TWRP in my phone. Will it have access to the Main Storage after installing Bliss OS? Right now, TWRP with the stock rom doesn't have access to it.

Thank you.

---------- Post added at 12:38 AM ---------- Previous post was at 12:32 AM ----------

No, not an issue for me, never had that, but maybe a reset could fix it.
[Android General] I opus l:
I'm getting the rapid button tap too. First it was playing clash of clans and highlight a specific item rapidly. It's coming more and more frequently it seems.
[Android General] Davindy:
Assuming your bootloader is already unlocked, or that you know how to do it - just follow these steps:

Download a Treble based ROM from here:

https://xdaforums.com/project-treble/trebleenabled-device-development

Bring up ADB

Then issue these commands:

fastboot reboot

fastboot flash system "system_img_name".img

fastboot reboot

And your done!

I have not tried disabling encryption, nor do I think having Bliss installed or any other Treble based ROM, makes it any more possible?

The problem with TWRP that I don't like is that there is no official version for our phones, so it only works half-ass. Plus you have to run the DM-Verity or risk bricking your phone, but this script, if you're not careful, will wipe your NVRAM leaving you in a much worse position. So I don't bother with it, there's really no advantage to having a custom recovery if all you want is a custom ROM. I believe you can remove the encrypted partition by using TWRP and changing the file system type, then changing it back. TWRP will re-create the partition unencrypted, but again why, what's the advantage?
[Android General] MikeyLee:
So this isn't working at all. When in Fastboot mode the oem unlock command errors out. FAILED (remote: 'unknown command") Drivers are installed, phones is recognized by ADB etc... Also as it's noted that you can boot the phone into bootloader mode via Pwr and Vol up, this also does not work. There are no options that appear. So can someone who has successfully unlocked and rooted please post the method you used?
[Android General] Davindy:
If you're fastboot isn't working make sure you have the latest version!
[Android General] I opus l:
I just like having nandroid backup on hand at all times. I have had Majisk modules boot loop after install. Instead of going through a new set up, and restoring everything from titanium, restoring ring tones, SIM card setup, etc, I prefer to just have the backup on the device. That's my reason for TWRP. I know you can backup with adb, but that involves being attached to PC and is more involved. You're right though it sucks not having an official version.

As soon as I get the time I'm going to take you're instructions and try to get this thing unencrypted and running Bliss. Think all I have to do is run your instructions.

*Edit Have Twrp installed prior with Stock and backup Nvdata

Get Bliss running fresh setup but encrypted

Install TWRP

Format data

Boot into fastboot

Flash Bliss again from adb.

Boot into TWRP

Install dm-verity

Install Majisk

*Edit Restore nvdata

Reboot into Bliss

Anyone see any issues with that plan?

*Edit Got It!

Just got installed and setup. Only issue I see so far is no dual LTE on Sim cards. I'll update if anyone is interested
[Android General] MikeyLee:
Fastboot is working. Other fastboot commands work fine. The OEM unlock command is what's not working. oem unlocking is checked in dev options also.
[Android General] Davindy:
You should be using this command:

fastboot flashing unlock

Additionally, you can run fastboot devices to make sure fastboot sees your device....
[Android General] I opus l:
Correct fastboot oem command does not work, it has to be the second one. "o" in the instructions should have been "or"

fastboot flashing unlock

If your on a Linux system and that didn't work try

sudo fastboot flashing unlock

I had to on Linux Mint
[Android General] MikeyLee:
Got it unlocked finally. Now have to get TWRP working. So far it's not flashing for me
[Android General] Zahr:
I got v3.3.1-0-aubrey twrp from official app in Play Store. Still asks for password, but no biggie. I move stuff to external card when I gotta flash something.

Flashing older ROM version boot.img has so far gotten rid of or at least stopped for now, the screen tapping itself issue.

Is signal, data speeds better with the other ROMs as compared to stock?
[Android General] MikeyLee:
Ok so after a dozen tries, I have not been able to get TWRP on this device. I've had it appear as if it flashed but still nothing there. Any suggestions?
[Android General] Zahr:
I had to flash twrp through SP Flash Tool. Phone relocked, but remained rooted with twrp.
[Android General] m1chaeldg:
After installing bliss os, how to install gapps and root it without flashing the recovery? Thanks
[Android General] Davindy:
Gapps comes with Bliss so no need to do anything there...

Root didn't interest me so I have not tried that yet. But I'm sure there's a way....
[Android General] mbsans:
Thanks Davindy. Yea, I know that this TWRP version is not official, but it's way better than the stock recovery. Your way on how to disable the encryption by using TWRP and changing the file system, is really interesting.

Now, the advantage of having a unencrypted partition is that I have complete access from the TWRP to that partition, currently I can access only my external microSD card.

However, given that my rooted+TWRP stock ROM is running fine with no issues, I'd wait a bit more until we have a solid safe way to decrypt the partition and have an official TWRP version, but I surely have my eyes on Bliss OS.

Thanks again.
[Android General] kaooss:
Google camera for umidigi s3 pro

Hi all, which newer version of gcam worked on umidigi s3 pro, I installed different versions for test. but only one works and this

MGC_5.1.018_FinalMod_v4.apk

celsoazevedo.com/files/android/google-camera/f/changelog83/