yashsingh1/xdaforums huggingface dataset:
[Connected Car] galaxys:
Keep us posted on your project progress...
[Connected Car] jivenene:
Wondering how this is coming along?

My question for you is, will the tablet charge and use data via the OTG cable simultaneously? Did you need to run a custom kernel to enable that?

thanks.
[Connected Car] theGeekyLad:
Quite in consonance with what I've been wanting to achieve. Nevertheless, the plan was frustrated by other priorities. Would love to see how this emerges. Meanwhile here's a basic experiment I've tried.
[Motorola Droid Maxx] marioghost7:
What are the safest ways to backup my Maxx and then unlock, and if possible, root it? As in the title, I have an (old!):

droid maxx

Motorola X8

Android 4.4

Kernel 3.4.42-ge1d6506-0006-g9ddacc8... (Wed Apr 30 2014)

Build "

Build SU2-3.3

Unfortunately, it is (most likely) not a developer version, just a plain old Verizon customer version (bought I think in 2014).

It only took a system update once a long time ago when my SO accidentally updated it (many years ago). Since then, it keeps annoying me for system updates now, but I keep rejecting them and disabled the play store ( Google Play Store vers 10.8.33-all [0] [PR] 205773289) and as many things as I could, hoping I can root this sucker at some point. I just install apks directly whenever I need something.

If it is not unlockable/unrootable, are there any other options for playing with it through adb on the computer, etc...? Are there any options for permanently disabling the pesky update notifications so I never accidentally hit them, or even better, getting rid of whatever the update was? I'm a long time lurker on this forum but always got too busy to play with it before. I am currently using it as my primary phone as I'm trying to save money by not buying a new one. I love the battery life on this thing, even with regular use for 5 or 6 years.

Thank you all so much.
[Motorola Droid Maxx] PicelBoi:
1: Back up ALL data.

2: Install Sunshine from theroot.ninja.

3: Enjoy twrp.

Sunshine requires you to pay $25 USD dollars.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] RioIT:
Hi, since a few week i'm having some problems with my battery.

My battery fastly switch from 40% to 3% or from 20/23/ecc... to 2/3%....

Could be a Software problem? Sorry for bad english
[Samsung Galaxy S7 Edge Guides, News, & Discussion] RioIT:
Should i try to reset or change the Battery
[Tilt, TyTN II, MDA Vario III General] Maurozac:
Hi to all.

I don't know which kind of problem I have!

The last week my Kaiser stopped to download my mail and the Pocket weather updates!

I've set up my mail (standard windows mail) to check mail every hour and my pocket weather to be updated every three hours.

After few months where everything was ok, now it doesn't work.

I checked manually and found out that the mail and pocket weather cannot "launch" the connection to the net.

In the mail I click on "send/receive" and in the information row appear "connessione in corso" (that means: connection underway - I don't know the right english term) and stay there until I stop it clicking on "stop send/receive".

The same for pocket weather.

Instead, if I launch Internet Explorer or Net Front the connection to the internet start and everything works fine.

To note that, also if the telephone is connected to the net both Pocket weather and the mail doens't work.

I checked the connections (both in mail addresses and in PW) and everything is as it was.

The only way to make them work is to reset the phone: the first 2 - 3 hours (2 - 3 downloads? I did not understood this either - why it stops working and when!) work then it stops.

help!!! it is getting me crazy!

thank you in advance,

Mauro

ps. i still not upgraded to 6.1
[Tilt, TyTN II, MDA Vario III General] elypsar:
Are you running a stock or cooked rom? What country are you in?
[Other SmartWatches] Melanthyus_4j:
Good day, and wishing all members all over the world, the happiest and most productive 2020.:)

I own the old but lovely fifine w9 smartwatch, and I am desperate to locate a piece of it's charging box, mine has already weared out a lot.

Please, if in good condition, used, if you have a spare, or you don't need your own one anymore, please, let me know how much you wish to be paid for it, and I will cover the price and shipping fees, there is no problem even if your country is far, far away from mine(Greece).

Please, let anyone who might know where to get one of this thread.

Thank you,

Kind Regards,

Christopher Stathopoulos.
[General Questions and Answers] hrist777:
Recently I updated my galaxy note 9 to android 10 and rerooted it like normal but when I tried to edit build.prop it just didn't save the changes after reboot.

I tried different editor root explorers even tried to pull the build prop whith adb but nothing worked if someone can help I will be very grateful thanks
[LG V40 Questions & Answers] 3laws:
I bought two

AT&T locked

LG V40 last month on eBay. I carrier unlocked one and was waiting for the unlock code for the second. I crossflashed freshly unlocked one to Unlocked ROM Pie; no issues, great experience... but this is where it goes down. I resold the completely unlocked one and proceed to flash the Pie KDZ into the STILL carrier locked AT&T! You see, I barely use data/phone services so I totally forgot I never carrier unlocked this unit.

Here's the deal. Now I have the unlock code but the firmware was not design in input an unlock code for carrier.

Is there a workaround, I'm stuck with an AT&T locked LG v40 with unlocked ROM?

Extra comments: Maybe I can flash LineageOS and find a way to input the unlock code but here is where my experience falls short.
[LG V40 Questions & Answers] Ainz_Ooal_Gown:
Pretty much unless you happen to have a backup of the stock AT&T firmware? But question why didn't you just OTA to AT&T pie first?
[LG V40 Questions & Answers] DEXEIL:
Hi. How did you crossflashed att version to unlocked rom?

To enter unlock code try dialing 2945#*405#, a menu will appear
[Android General] noskojv:
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!

1) Activate the "for developers" item in the settings (7 times click on the "build number" in the "about phone" settings at the bottom)

2) Go to "Settings"(the main screen of the application) go to "for developers" and move the switches to the enabled position near the items "USB Debugging" and " Unlocking the bootloader"

3) Then download platform tools from here https://developer.andr...eleases/platform-tools

4) Unpack the archive from platform tools to the root of the C: drive(so that the platform-tools folder is in the root of the C drive: )

5) if the process does not go install VCOM driver

6) Switch your smartphone to fastboot mode:

6.1) connect the included phone to the computer

6.2) Open the command prompt

6.2.1) Click Win+R

6.2.2) in the window that appears, write "cmd" and click " OK"

6.3) in the command line when the phone is turned on, write(without quotes)

6.3.1) " cd " (note that there is a space after "cd") and drag the "platform-tools" folder with the cursor to the command line window, press Enter

6.3.2) the Following command "adb reboot bootloader"

6.3.3) Your phone should reboot into Fastboot mode or a window should appear on the phone asking for debugging permission for this computer - put a check mark "Always allow debugging from this computer" and click "OK", repeat point 6.3.2

7) After that, on the computer in the same command line, enter " fastboot flashing unlock"

8) when the smartphone screen will prompt confirm by pressing vol+

9) after you see Finished, restart your device

Now the logo will be labeled Orange state when loading
[Android General] zironia:
I've rooted my F2. I used magisk to patch the boot.img then flashed the boot.img through fastboot on Linux. It didn't work with magisk 20.1. Had to used the newest magisk manager. I am interested in your twrp if you have one to try. Would you upload it so I may try to flash it.
[Android General] Juanito_R:
Please upload your patched boot.img file. Thanks
[Android General] _cab13_:
I would love to have that boot image as well! What magisk version did you use then ? I can start crafting a guide.

EDIT: what boxes did you tick in Magisk Manager ?

EDIT 2: did you pad the boot image with DD ? Or maybe you wiped the boot partition beforehand to make it all zeroes ? It seems to be the missing thing and a known bug in Magisk.
[Android General] zironia:
Magisk 20.2 was what I used. Then flashed the boot through fastboot using Debian Linux.

Rooted f2 boot IMG
[Android General] ajsmsg78:
I've tried everything to get it rooted but any magisk patched boot image I flash just sends it into a bootloop including the one posted in this thread. It doesn't matter whether I flash it in Linux or Windows, in fastboot or in SP Flash Tool. What stock build are you guys on, the European or the Global? It seems that the boot.img is the same in both.
[Android General] _cab13_:
Apparently the issue is that the bootloader really doesn't like the fact that the image is not the full size of the partition. I'll try to dd it to the "max" size so it completely replaces the boot image and not only parts of it.
[Android General] _cab13_:
Seems to be an issue with the bootloader which doesn't like being flashed with a smaller boot image than it's partition size. Could you try padding it ? https://github.com/topjohnwu/Magisk/issues/2005

With this command

dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431

EDIT: Double post, my internet is pretty bad, I thought the first one didn't go. Can't delete apparently.
[Android General] zironia:
When I unlocked the bootloader I also unlocked critical areas

fastboot flashing unlock_critical

Warning---- this will wipe your phone again just like the bootloader unlock.
[Android General] _cab13_:
Haha seems to be the key to it ! Thanks for the update !
[Android General] _cab13_:
I've tried everything as well. Still bootloop. Your patched image doesn't work for me. I've unlocked critical as well as regular unlock.

1. Did you tick any box in Magisk Manager ?

2. Did you relock afterwards ?

3. What firmware version ?
[Android General] zironia:
I downloaded the new update today and I haven't been able to root the boot.IMG so far. I will keep trying and note anything that is successful.
[Android General] _cab13_:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.

1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT

2) Download the f2rootedboot file from zironia

3) Start ADB while booted; run adb reboot bootloader

4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical

5) I flashed a bunch of partitions with dm-verity disabled.

6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img

7) fastboot --disable-verity --disable-verification flash recovery recovery.img

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

9) fastboot --disable-verity --disable-verification flash super super.img

10) fastboot --disable-verity --disable-verification flash tee1 tee.img

11) fastboot --disable-verity --disable-verification flash tee2 tee.img

12) fastboot --disable-verity --disable-verification flash cache cache.img

13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img

13) fastboot reboot

I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
[Android General] zironia:
This worked for me to reroot after the update today. Not sure what part of it is necessary for the boot image to work right though. I left off the userdata.img so I could keep my files in place.
[Android General] ajsmsg78:
Confirmed working, thanks. I ended up patching the new boot.img myself and that also worked. I own a Note 10 + and OnePlus 7 Pro and honestly I think the Umidigi is an awesome deal, everything is pretty good on the device. It's something I wanted to try out and I'm actually impressed.
[Android General] ubuntuh:
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
[Android General] zironia:
Currently there is no twrp recovery for the f2. I've tried a couple ports of twrp but can't get past the splash screen.
[Android General] _cab13_:
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
[Android General] zironia:
True. Twrp just makes it quicker and has easier backup option
[Android General] _cab13_:
Umidigi F1 Play TWRP should work, it's the same chip, the same screen size. I don't know what's wrong with it not booting like it didn't boot Magisk before. Maybe we need to flash all the partitions with the disable-verity flag like we made Magisk work ?
[Android General] ajsmsg78:
TWRP hangs at the boot screen as well for me. Also, to root you only have to disable verity in boot, recovery and vbmeta.
[Android General] yipsama:
May I ask what box is checked and which magdisk version when you patched the boot.img? I am trying to patch the new boot.img with Edxposed's magdisk. It can boot into the system. But when I tried to type my password, its screen went black. I can do nothing but to reboot and flash back original boot.img..
[Android General] ajsmsg78:
Preserve force encryption and Preserve AVB is checked, that is all. On a side not I lost my fingerprint scanning function. I even flashed the older firmware, went back to complete unrooted, locked bootloader and I have no fingerprint unlock anywhere in settings. My IMEI's were gone and so was my MEID. I was able to get everything back by using the MT IMEI Flash tool but the fingerprint is still not there. It's probably due the fact that I did a format+download in SP Flash Tool. Can someone back up their stock Tee partitions in SP Flash Tool (the read back section) and send me the img files?
[Android General] yipsama:
Patching boot.img is still having many problems. Hope someone can build TWRP for F2.
[Android General] _cab13_:
[MENTION=1397125]ajsmsg78[/MENTION] afaik using other's tee partitions doesn't work, someone already asked me for one which I gave (Umidigi One Max) and he still couldn't make it work.

Concerning TWRP, I've got the F2 device tree ready, can someone compile it for me?
[Android General] _cab13_:
Please create a boot image with the latest Canary build of Magisk Manager. Howdo you even patch a boot image with Edxposed ? Did Ed create a Magisk fork that I'm not aware of ?
[Android General] ubuntuh:
Did you manage to mount system R/W with magisk installed?

Is there some progress on twrp developpement?
[Android General] _cab13_:
[MENTION=5186340]ubuntuh[/MENTION] any system modification seems to lead to bootloops. Concerning TWRP, I'm trying to build it but I don't know how to do so. I have the device tree waiting.
[Android General] ubuntuh:
we might have to decrypt the data partition by flashing the decrypt zip through twrp. But for that we need a working twrp. what are you missing to compile the twrp?
[Android General] yipsama:
Edxsposed provides its version of Magisk zip file.
[Android General] yipsama:
It is better to upload it to github if you have the device tree. It would be convinient for every one to grab one and try compiling twrp.
[Android General] _cab13_:
[MENTION=10173279]yipsama[/MENTION] using an unofficial Magisk is not supported and I won't help you with that.
[Android General] _cab13_:
Unofficial TWRP; Not tested, not compiled. Please report anything. https://github.com/defvs/android_device_umidigi_f2

EDIT : Built it.

Great news; it boots. Bad news, stuck on splash screen. Still needs some work.
[Android General] _cab13_:
Even greater news. It works. Kinda. No /system /vendor /data because TWRP is not made for Android 10 yet. Check their blog post here https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
[Android General] ubuntuh:
Would it be possible for you to upload the recovery.img please. im not used to compile from github. Thank you for your effort!!
[Android General] _cab13_:
[MENTION=5186340]ubuntuh[/MENTION] Link on main thread.

Or be lazy and use that direct link https://github.com/defvs/android_device_umidigi_f2/releases/download/v0.1/twrp_f2.img
[Android General] Juanito_R:
For me you recovery TWRP_F2 not working. Can't month SD card to install a new zip file.
[Android General] _cab13_:
[MENTION=10440971]Juanito_R[/MENTION] are you talking about external sdcard ? I can't test it as I don't have one. I would recommend you sideload the zip you need using adb.

EDIT : fixed https://github.com/defvs/android_device_umidigi_f2/releases/download/v0.2/twrp_f2_v0.2.img
[Android General] zironia:
Deleted
[Android General] catzilla:
New OTA today, updates to UMIDIGI_F2_V1.0_20191122_20200116-2132

I took the liberty to reupload the zip: https://mega.nz/#!aREiUIpJ!yE21j3bD4_vf-QpYdY-GteQfuniekrijLG8HFJ7s1Qw

It seems to contain a patch to boot.img and I am scared to flash this (having rooted already).

Official page is not updated yet, I am going to wait for the full rom to be available before I try to update/reroot.
[Android General] _cab13_:
I wouldn't try it myself at least not yet. It's not that risky, we can still go back to old ROM.
[Android General] Romz24:
I use V1.0_20200116.V3.09 ROM. When I try to install TWRP or magisk_patched, my phone starts to reboot endlessly when I try to turn it on. How do I get root and fix endless phone reboot?

Orange State
Your devices has been unlocked and can't be trusted
Your devices will boot in 5 seconds
[Android General] palbeda:
Success!!!

Ok, so I am typically a person who wants to do nothing more then strictly necessary and so I found out what is minimal needed. I updated my phone to the last available update. Then I unlocked the bootloader and also unlocked critical. I used the readback function of the flashtool to read boot.img vbmeta.img and recovery.img. I patched boot.img with Magisk manager (and just to be safe), I padded the file to the full length. I flashed the patched boot.img with the parameters that were descibed, but found out that indeed you have to flash al three files with the parameters to prevent startup loops. But if you flash all three files, success!!!

So VERY happy with this thread.

Thanks, Peter

---------- Post added at 07:49 PM ---------- Previous post was at 07:43 PM ----------

Did you flash only the patched boot.img? Then you will get the loops. If you flash recovery and vbmeta, all three with the suggested disable parameters, it should work!
[Android General] Romz24:
I was flashing 3 files.
[Android General] _cab13_:
Make sure you flash them in the bootloader and not fastboot / fastbootd
[Android General] catzilla:
Hold up, which boot.img are you using?

The latest update contains some kind of patch to boot.img, so the version from 3.08 should be incompatible!

What version does your phone say you have when you go to about phone -> wireless update?

I am afraid to install the last OTA on top of already-rooted boot.img!

Perhaps the way to go is:

1) Flash original boot.img from latest full flash (and the other two files just in case)

2) Reboot, apply official OTA update

3) Flash the same rooted boot.img (plus the other 2 files)

Anyone tried this?
[Android General] zironia:
I have done this and I am rooted on the new ota just fine.
[Android General] catzilla:
Can you please clarify what you did - did you apply OTA on top of dirty rooted boot.img or on top of clean factory boot.img? Just want to be absolutely sure.
[Android General] zironia:
I loaded non rooted boot.img. Took ota and rerooted boot img
[Android General] _cab13_:
[MENTION=3828105]zironia[/MENTION] any idea what the new OTA changes ? They only say bugfixes.
[Android General] zironia:
I think it was mostly bug fixes. I noticed my volte icon would flash off and on often and it seems stable now. Umidigi seems to get phones stable then end updates. This may be the last update for the f2. We will see what happens.
[Android General] zironia:
I have read that orange Fox recovery works better with Android 10 than twrp. If anyone is capable of settng it up maybe we can use it instead.

https://gitlab.com/OrangeFox
[Android General] _cab13_:
[MENTION=3828105]zironia[/MENTION] I'll see what I can do for sure ! Probably super easy to setup since I've got the device tree already.

Edit : Looks promising. I'll download the manifest and build it tomorrow.
[Android General] _cab13_:
Managed to download sources and compile. I'm stuck in a bootloop. I'll see what I can do about it later !

EDIT: Hanged out with someone on OrangeFox telegram chat. Will not be able to make this work. 1st : Broken boot for Umidigi devices they don't know why. 2nd : It's using TWRP sources, and like TWRP it won't support 'super' partition (aka. dynamic partitions, it contains both system and vendor). So the only benefit to having OF would be style and boot image patching I guess. Not worth the effort.
[Android General] zironia:
Thank you for all the efforts.
[Android General] updatesvc:
Unencrypting data partition

How can unecrypt the data partition.

Usecased : uninstall bad (bootloop) magisk modules by deleting them.

I tried delete the encrpted files in the encrypted folder names /data/adb/DhFunUJhGHiOr but ended in a bootloop

or is there way to remove bootloop modules (magisk modules) when data is encrypted?
[Android General] _cab13_:
You cannot decrypt data in TWRP.

Here are some things you may try:

-----

Hook your device up to a computer (or other device you can run adb from) and execute the following command:

adb wait-for-device shell magisk --remove-modules

After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot.

-----

You could also try :

If you can't boot your device, this can be done by placing a file in /cache (/data/cache on A/B devices) named ".disable_magisk" (without quotation marks and with the leading dot). This will enable Core Only Mode and you can boot up your device, uninstall the troublesome module and then go into the Manager settings, disable Core Only Mode and reboot. In TWRP you can create the file through the TWRP terminal with the touch command, see below for an example.
[Android General] updatesvc:
Thank You

Thank you.

I will try this the next time I endup in a magisk module-bootloop)

I ended up doing a full data wipe XD (that's before reading this)

Also is there a good way to backup the userdata.img or in general what's the easiest way to create an offline backup of the F2 data partition?

Might also add maybe you can update your original post to have this.

SPFT :

You might need to press the volume + button and power button to enter download mode.

TWRP:

To boot to TWRP you need to press

the VOL + and Power Button

once powered on use VOL+ to scroll to

Boot to Recovery<<

Edxposed: (still a bit finnicky)

1. In magisk download the Riru Core module and flash

2. Download the canary builds for YAFHA or Sandhook (The current stable builds may have issues with activating modules and might need the patched magisk installation)

Tested with this Canary Build EdXposed-SandHook-v0.4.6.1 (4504)-tdgptedc-release

github.com/updatesvc/EdExposedCanary/blob/master/EdXposed-SandHook-v0.4.6.1%20(4504)-tdgptedc-release.zip?raw=true

3. Flash this build using magisk

4. Install Edxposed Manager.apk tested with 4.5.4

github.com/ElderDrivers/EdXposedManager/releases

6. Reboot

7. Install Xposed modules (not all work at the moment)
[Android General] _cab13_:
Sure, thanks. Btw you shouldn't need to press any key to get into download mode, just turn off the phone, unplug it, start the download on SPFT and plug it in.