yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] nmyshkin:
I'm not sure Relaunch can do what you need. You can "see", yes, but that doesn't mean you can change. To do that, /system has to be mounted as R/W and I don't know if Relaunch can do that. Back in the day I used an app called Root Browser. Now I just use ES File Explorer as a general file manager. It can be set for root access and also can mount /system so you can make changes. I've attached a copy below.
[Nook Touch General] muhammad hunain:
why play store is not available in my phone?
[Nook Touch General] nmyshkin:
If you are asking about the NST, Google abandoned Android 2.1 back in 2017. No market access. You'll have to search online for what you want and side-load it.
[General Questions and Answers] cobe1202:
Hello Guys

PLEASE HELP

A have been struguling with this for some time now.

I want to disable all notificationss on a specific app exept vibrations.

If i disable them in Notifications and a i select do not show on Lock Screen,when i slide down my finger on the screen there are still notification below the short switches.

I dont want any notifications anywhere exept vibrations

Thank you
[Nubia Red Magic 3 Questions & Answers] SavageCat-TX:
I'm used to being able to select different sounds for different events but with the RM3s, I only have a "default" notification. Am I missing a setting somewhere to change this?;
[Windows Mobile Development and Hacking General] Nixeus:
Hi,

I have a HTC TOUCh ( ELF ) and a MIO P550 !

These 2 devices are on wm6.1 roms which i have cooked myself !

In my HTC ROM, i have integrate the HTC TaskManager !

I have tried to integrate the HTC TaskManager on my MIO ROM, but the HTC TaskManager don't function on my rom !

I just want to know if the HTC Apps ( like HTC TaskManager ) are only for HTC device, or if it is possible to "hack" their apps in order to install on other device ?

Great thanks :)

Nixeus aka CrashOverHead
[Windows Mobile Development and Hacking General] nir36:
the first thread in this section of the forum says:

Questions & Answers, ask here! *DO NOT POST A NEW THREAD UNLESS YOU ARE CONTRIBUTING

it couldn't be clearer than this...
[Windows Mobile Development and Hacking General] Nixeus:
OO i'm sorry, but i have difficulties to understand : What do you say about "contributing ???"

I'm a senior member, and contribute to this forum !

:)
[Windows Mobile Development and Hacking General] wacky.banana:
Nixeus,

What he is saying is that you should have posted your question here to stop cluttering up the board...http://xdaforums.com/showthread.php?t=398571

Give it a try. Good luck.

WB
[Samsung Gear S3] [MaNdAx]:
Hello,

I can't get the mobile phone to send the notifications to the watch. I have enabled the pluging in Access to notifications and disabled the battery optimization option.

Can you think of something?
[Xiaomi Redmi Note 7 Questions & Answers] NatorJ:
Hi. I installed qualcomm drivers and after that QPST and started PDC tool but it doesn't recognize my phone,even tough I activated USB debugging. Any ideas?
[Xiaomi Redmi Note 7 Questions & Answers] joke19:
Usb port 3.0? Then use then usb 2.0 port, an other port or another usb cable
[Xiaomi Redmi Note 7 Questions & Answers] vlouis:
The phone need to be switched to diag mode.

Before doing this Mod you should backup EFS-partition !!!

Need to have adb installed and phone rooted. Open cmd window and type:

adb devices (check if phone connected)

adb shell

su (grant root)

setprop sys.usb.config diag,serial_cdev,rmnet,adb

You will find new device in PC device manager "Qualcomm HS-USB WWAN Adapter 9091", then PDC tool will recognize your phone.

More info here: https://xdaforums.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
[Xiaomi Redmi Note 7 Questions & Answers] NatorJ:
Qualcomm recognized but PDC tool doesnt recognize it
[Xiaomi Redmi Note 7 Questions & Answers] NatorJ:
https://imgur.com/a/CODbtYN
[Xiaomi Redmi Note 7 Questions & Answers] vlouis:
In device manager you have "Qualcomm HS-USB Modem 9091" and not "Qualcomm HS-USB WWAN Adapter 9091".

Few weeks ago I changed my modem config using this method. I used Xiaomi.eu 20.7.9 MIUI12 weekly ROM. Or try to change the qualcomm drivers.
[Xiaomi Redmi Note 7 Questions & Answers] vlouis:
Delete row_commercial profile with pdc tool.
[Xiaomi Redmi Note 7 Questions & Answers] jengyiing:
Yes. it does work! after remove the row_commercial profile in PDC and reboot the phone. The profile now not fall back and VoWIFI is actully working now.

Thanks for your help!
[Xiaomi Redmi Note 7 Questions & Answers] Goodtag:
I have the same problem as @NatorJ

Did the "adb shell; su (grant root);setprop sys.usb....." thing. Device get's recoginzed in device manager as "Qualcom USB Composite Device 9091" but NOT PDC tools.

Please Help
[Xiaomi Redmi Note 7 Questions & Answers] KoshoNSA:
hello, how did you put the Row_Commercial profile back in pdc tool?
[Xiaomi Redmi Note 7 Questions & Answers] reisaaz:
Very much thanks for this information
[Samsung Galaxy Note 9 Questions & Answers] shonkin:
Finally, the unlocked version of the Note 9 got its update this morning... Samsung released the T-Mobile update to UI 2.1 (dated July 7) today, August 11 2020. There's an important note for some who will run into one annoying issue:

I installed this and hit an issue after the install completed re an error message (see photo). This error apparently is happening in a widespread way, and the 3 solutions offered by Samsung did not work. What *did* (I think) work for me was to go to Settings > Software Update > UICC Unlock. Beneath that button on the N960UI it reads (as it should) "Your device is unlocked to support any sim." I click it anyway and I get a report that my device sim is restricted, bla bla bla. I hit the "OK" and reboot the phone to see... and sure enough, that's all it apparently took to remove the annoying nag about the install not having completed. In fact I get a successful "handshake" message between T-Mobile and the phone having formed a more perfect union or some such.
[General Accessories] leodp:
Hi,

I own some bluetooth headsets, which generally work ok in stereo mode wherever I listen to music/videos/Youtube.

But during calls those with a physical & electrical connection between left and right ear still deliver the caller's voice to both ears, while the earbuds (separated objects for left & right ear) default to mono and I hear the caller's voice only on one of them. Is this last behavior avoidable?

I have tried without success different pairing methods, i.e. some ear buds suggest a procedure in which one earbud should first pair to the second bud, and then this one pairs to the phone.

I have searched the net but no real answer is popping out.

Thanks, Leodp
[General Accessories] leodp:
Hundreds of views and no reply?

Jesus!

You all are condemning me to cross-posting somewhere else!!

Please, reply! I do not want to get this black spot on my seamless internet history!!

:)
[Samsung Galaxy Watch] orbitech:
Hi I have the LTE Galaxy Watch Active 2 SM-R825F .

I have the R825FSSADBT s/w version.. I have issues with local esim compatibility here in Greece and I want to test a Greek CSC. Can anyone help with EU/COS version of this watch to flash? And if it is uploaded somewhere can anyone provide me with a link or the files?

Thanks in advance
[Samsung Galaxy Watch] chris.lu:
https://xdaforums.com/smartwatch/galaxy-watch/sm-r825f-csc-change-tutorial-t4061905
[Samsung Galaxy Watch] amitdon:
Y u want to try i can help you

do you know how to use net odin and r u ready to take risk. :mad:
[Samsung Galaxy Watch] orbitech:
Thanks for your time man yeah I've been doing this since HTC HD2 era I wasn't afraid of that. :)

I thought it was a specific f/w I had to d/l for flashing the specific CSC of my country in order to change it..Just like with ROMs. Then I watched the whole procedure and realised it had to do with messing with inf file after flashing a universal f/w to change the CSC and then push the commands through terminal before flashing back the OG f/w.

The proceduce was successful and now I can use mobile services of my country, which wasn't feasible before :)

Again thanks for your time
[Touch Pro, Fuze General] twisted-pixel:
I see from another posting in the diamond forum that people have managed to get BB Connect running on the diamond.

At the moment I use system7 on my nokia n95 to get email pushed from my work exchange server, however everyone else in the office has a blackberry (I didn't want one of these hence my finding an alternative solution).

does anyone have any experience of the direct push technology offered with windows mobile 6?

I might use the bbconnect application (if I can get it working) as it appears to do everything I want it to, but I just thought that if there's already an app in WM that does the trick, I might as well stick with that.
[Touch Pro, Fuze General] mrvanx:
You say you have exchange at work?

The push email system will work just nicely with it, you might have to get onto your network admin and see if they offer activesync connection to it but its very likely they do. You sync your email, contacts, tasks and calender with it...works a treat.

I currently use DenaiL's service on here and it works very nicely...you should be up and running pretty swiftly if ur network admin confirms you can use it.

EDIT: Activesync is built into EVERY ROM in windows mobile and this is the primary way to sync the device over the air (via GPRS/HSDPA or wifi to get push email) or via USB.
[Touch Pro, Fuze General] twisted-pixel:
we have exchange server at work, but I doubt they'll let me add any software (activesync) to it.

Exchange already has the software needed in it, its a native function of exchange to allow a windows mobile device to sync with it.
[Touch Pro, Fuze General] rhedgehog:
EAS is a native part of exchange, but it is turned off by default i think.

I know my place have it turned off, despite all the company mobile supporting EAS, and all the employees using HTC devices that natively support it.

Go figure.

I think they want to save a couple of hundred of quid on a certificate, and spend thousands of pounds on corporate intellisync licenses instead.
[Touch Pro, Fuze General] twisted-pixel:
so my company would have to invest in a new license to enable EAS?

I'm pretty sure they would have to buy a license to allow me to use BBConnect too? I know that we are running 5 or 6 BBs in the company, each one requiring a license....or have I been misled?

thanks, I really want to ensure that my push email will work perfectly on the device when I get it.
[Touch Pro, Fuze General] anandoc:
I dont own a HTC Touch Diamond or a Touch Pro. I own a HTC Touch and use Hosted Exchange as my primary email service provider. I use the direct-push technology in WM6 and sync with my exchange account. It works like a charm and I have yet to experience any problems with it. I get my email on my Touch within 10 seconds of receiving the email in my inbox.

Memory fades about Exchange 2003, however, I *think* Exchange direct-push is enabled by default on Exchange 2007. Someone please correct me if I am wrong.
[Touch Pro, Fuze General] DeniaL:
Exchange 2003 w/ SP2 automatically enabled Direct-Push. Same w/ all flavors of 2007. With Exchange 2007, admins DO need to enable Active Sync, but they can do it on a user by user basis if they want to. It shouldn't be a big deal for your IT admins to turn it on for you. Hope this helps.
[Touch Pro, Fuze General] twisted-pixel:
excellent, thanks for the replies. We are running 2003 SP2, so hopefully in a few days time I might have proper push email. the app I'm currently running (system7) is totally crap at the moment..had nothing pushed for nearly a week!!
[General Questions and Answers] he-lpMe:
hello every one :good:​

i have a lenovo a319 that stopped working after i wiped data instead of factory reset , wich apparently deleted the os and the recovery mode itself. now the phone does not turn on or charge ( no boot loop )and when i try to access the recovery mode the screen remains black. When i connect it to pc this error message appears '' the last usb device you connected to this computer malfunctioned and windows does not recognize it''

aditional info ; the phone had a custom rom

this is my first thread here , thank you everyone .:good:
[Asus Zenfone Max M2 Questions & Answers] Surendra Ravindra Sonawan:
You're smartphone its continually rebooting to fastboot mode because you wipe system partition or

You're system currapted for fix it flash vbmeta file using fastboot command

fastboot flash vbmeta vbmeta.img

If the above is successful, remove the cell phone from the PC, push the power button for a long time until the notification appears immediately just press the volume and the option will appear later, select recovery to enter twrp. If you successfully enter twrp, please install stockrom / flash GSI

Vbmeta file will found in ...

@x01adhelp
[Android Q&A, Help & Troubleshooting] zdaddi:
How well does it work?
[Android Q&A, Help & Troubleshooting] tetrig:
Ok, it's not super custom layout, just dynamical partitioning was used. There are docs on

https://source.android.com/devices/tech/ota/dynamic_partitions/implement (new account, can't post links)

[IMG="dynamic partitioning, source.android.com"]https://source.android.com/devices/tech/ota/images/dynamic_partitions_table.png[/IMG]
[Android Q&A, Help & Troubleshooting] hermeez:
Have you managed to get TWRP on the recovery partition? I have root but, unable to flash recovery proper
[Android Q&A, Help & Troubleshooting] dr_drache:
Currently I have a Device tree setup : https://github.com/DrDrache/umidigis5pro_TWRP

and already pulled the minimal manifest of TWRP - sadly I cannot get a quick compile (see code error below)

I havn't built a recovery in YEARS (6?) - so if we could find someone to give me the pointers; I can finish I think.

drache@drachedock:~/TWRP-SRC$ lunch omni_S5_PRO-eng
WARNING: device/umidigi/S5_PRO/omni.dependencies file not found

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_S5_PRO
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.8.1-xanmod1-x86_64-Ubuntu-20.04.1-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=/home/drache/TWRP-SRC/out
ROM_BUILDTYPE=HOMEMADE
============================================
drache@drachedock:~/TWRP-SRC$ mka recoveryimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_S5_PRO
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.8.1-xanmod1-x86_64-Ubuntu-20.04.1-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=/home/drache/TWRP-SRC/out
ROM_BUILDTYPE=HOMEMADE
============================================
device/umidigi/S5_PRO/omni_S5_PRO.mk was modified, regenerating...
device/umidigi/S5_PRO/omni_S5_PRO.mk was modified, regenerating...
[ 99% 260/261] finishing build rules ...
vendor/omni/build/tasks/kernel.mk:111: warning: ***************************************************************
vendor/omni/build/tasks/kernel.mk:112: warning: * Using prebuilt kernel binary instead of source *
vendor/omni/build/tasks/kernel.mk:113: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/omni/build/tasks/kernel.mk:114: warning: * Please configure your device to download the kernel *
vendor/omni/build/tasks/kernel.mk:115: warning: * source repository to
vendor/omni/build/tasks/kernel.mk:116: warning: * for more information *
vendor/omni/build/tasks/kernel.mk:117: warning: ***************************************************************
FAILED: ninja: '/home/drache/TWRP-SRC/out/target/product/S5_PRO/obj/STATIC_LIBRARIES/bootctrl._intermediates/export_includes', needed by '/home/drache/TWRP-SRC/out/target/product/S5_PRO/obj/SHARED_LIBRARIES/android.hardware.boot@1.0-impl-wrapper.recovery_intermediates/import_includes', missing and no known rule to make it
18:58:17 ninja failed with: exit status 1

#### failed to build some targets (01:32 (mm:ss)) ####
[Android Q&A, Help & Troubleshooting] Halwer:
Hi @dr_drache!

Have you figured something out, yet? I can also list all the partitions from Fastboot, but cannot flash a working custom GSI ROM. What I found really interesting, as you all mentioned before, is that the device has a super partition, but for example the ,,GSI checker" app says that the device is very likely a-only.

I am also thinking about trying to build the recovery for the UMIDIGI S5 Pro after watching and reading some tutorials I guess...

I am just interested in your progress. :)
[Android Q&A, Help & Troubleshooting] Halwer:
Dear fellow Developers!

I have wonderful news! I successfully compiled a TWRP Recovery from source as a late night program for myself, but it was definitely worth it! I used the stock recovery image from the V1.3 stock ROM.

We are in the finish line, however I attached a screenshot and there are some problems need to be fixed.

The problems are:

E: unable to update logical partition: /system_image

E: unable to update logical partition: /vendor_image

E: unable to update logical partition: /product_image

Failed to mount 'system_root' (Permission denied)

I will leave a link here to the recovery image, built by me: MEGA

Every help is welcome, because we are really close now to make a working recovery for this phone and to start flashing custom GSIs!

Thank you!

Edit:

You can flash the recovery from fastboot and you can also use the SP Flash Tool to flash it.

View attachment 5263975

Edit 2:

There is a photo of the building, I think that there warnings are not relevant, are they?

View attachment 5263983

Update:

After editing some lines in the /etc/fstab file from ,,ro" to ,,rw" and then doing a mount -a the filesystems are successfully mounted, however trying to flash a GSI to the system partition drops the next error: Size of image is larger than target device

Also there is this interesting super partition and flashing the GSI there is working, but after that the device can't reboot to the OS, it boots to fastboot after the first failed boot. I think that we need to figure out how to correctly mount the filesystems or to resize the system partition or not and how to find it's original mount point.

Update 2:

So I found this on source.android.com: ,,Devices with dynamic partitions (whether it launches with or retrofits dynamic partitions) must not use system-as-root. The Linux kernel can't interpret the super partition and so can't mount system itself. system is now mounted by first-stage init, which resides in the ramdisk." How should we ,,find" now the /system partition? Because I didn't find it either through TWRP. I guess we have no other choice, than wait for the TWRP developers to figure this super partition layout out. I will keep up with the developments and will compile the recovery again, if progress has been made.
[Android Q&A, Help & Troubleshooting] prazola:
I think the reboot to recovery is related to some system partition. I remember that flashing GSI on a Mi9 SE caused the same behaviour after a full wipe.
[Android Q&A, Help & Troubleshooting] petesanchez:
Just recently bought S5 pro phone from official umidigi eBay store for AU$177. Very happy with purchase, great value plus doesn't have a notch or hole punch display.

After some searching and some trial and error, i can flash GSI images to device.

1) Unlock the bootloader

fastboot flashing unlock

and pressing Vol+

2)Boot to stock recovery.

fastboot reboot recovery

3)Select from recovery menu Wipe data/factory reset

4)Select from recovery menu Wipe cache partition

5)Select from recovery menu Enter Fastboot (fastbootd)

fastboot -w (CAUTION: deletes userdata, storage)

6)Delete product partition

fastboot delete-logical-partition product

7)Flash GSI to system partition

fastboot flash --u system lineage-18.1-20210411-UNOFFICIAL-treble_arm64_bvS.img

8)Reboot to normal fastboot (not fastbootd)

Flash the stock vbmeta.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Select from recovery menu Reboot system now

Not Working so far:

In screen fingerprint reader. Thinks reader is at back of phone, not sure how to fix.

Does TWRP allow for /system partition resizing thus keeping /product partition intact? Wondering if the product partition is needed for fingerprint to work?
[Android Q&A, Help & Troubleshooting] Halwer:
Hello!

Oh my God how did you figure this out by yourself? I completely gave up when I saw the terrible partition layout. I will try to flash one GSI following your guidance. So is it actually possible to avoid using TWRP and to flash GSIs from fastbootd? I thought Umidigi made it impossible with the lack of write permissions. If what you are saying here is true, then in theory we also can perform these steps from my beta TWRP, however I saw some updates on the project, maybe I will compile it again later.

Thank you so much for your help! I will post updates after flashing the GSI.

By the way, how is this phone AB? I didn't think that it supports seamless updates.
[Android Q&A, Help & Troubleshooting] petesanchez:
I honestly didn't figure it out, followed this good post below, it's a different Umidigi device but apply's to S5 Pro too.

https://xdaforums.com/t/umidigi-power-3-android-10.4044531/

Keen to try steps 15, resize product and system partitions & Unpacking and repacking super.img when i have some time as i would like fingerprint functionality.

Your TWRP image would be great to have, for backups etc and system edit's without root.

Arm64 A only images bootlooped, but A/B arm64 worked.
[Android Q&A, Help & Troubleshooting] Halwer:
Thanks for the link, I will check it out! I am also concerned about the fingerprint reader, since we don't really have kernel sources as far as I know. It would be great to keep the /product somehow. So basically the treble checker app gives false information about the system layout, because it said that the S5 Pro is a-only...
[Android Q&A, Help & Troubleshooting] Ed Haddon:
Hi, Halwer Treble Info shows that the S5 Pro uses an A/B operating system and that it supports VNDK and is an arm64. Try using this app as it reports the phone correctly.

The S5 PRO does not support seamless upgrades so you must enter recovery to install upgrades.

It also reports that it uses Dynamic Partitions (super partition) and that you can only flash high-level partitions through fastbootd as other methods will report an error saying the partition does not exist.
[Android Q&A, Help & Troubleshooting] Halwer:
Hello,

I am still not sure, look at this screenshot!

I mean in general this is really not a big deal. GSI ROMs tend to act a little weird with partition layouts, anyway.

The big deal will be a working TWRP in my opinion.

View attachment 5314185
[Android Q&A, Help & Troubleshooting] Ed Haddon:
Andy Yan has brought out another GSI version lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img.xz
[Android Q&A, Help & Troubleshooting] Halwer:
Good news!

I will also try to build a more up to date version of TWRP when more commits arrive on GitHub. It would be good to be able to resize the system partition from TWRP, so we don't have to touch or remove the /product partition.
[Android Q&A, Help & Troubleshooting] Ed Haddon:
Try Trebel Info instead as it seems to report the phone correctly as an A/B with unsupported seamless system updates. This seems to be what others are finding as the A-only OS causes boot loops.
[Android Q&A, Help & Troubleshooting] Halwer:
Okay, thanks. Interesting.