yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @dechughes443

Prior to your next posting please read the guidances that are stuck on top of every forum like

[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL

Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy A22 5G] fede2782:
Does someone know why Samsung Video Editor doesn't work on this device. I've added all libraries and frameworks needed however it still doesn't start but it gives me this error. Do you know how to fix this?

java.lang.IllegalAccessError: Method 'void com.samsung.app.video.editor.external.VideoEditor.<init>(android.content.res.AssetManager, android.content.Context)' is inaccessible to class 'com.sec.android.app.ve.vesdk.u' (declaration of 'com.sec.android.app.ve.vesdk.u' appears in /data/app/~~Kfv7Zxnv3soODCGDwSKEzA==/com.sec.android.app.vepreload-sEaCr2t0dcsviKP3exiveQ==/base.apk)
[Asus Zenfone Max M2 Questions & Answers] clement_mint_android:
I follow the guide to install /e/OS : https://doc.e.foundation/devices/X01AD/install

But just after install, I'm stuck in fastboot and obliged to use this guide to have a bootloader but my /e/OS doesn't work (I think it's because of flash vbmeta but I'm a noob)

Can you help me please to understand or stop this situation ?

Maybe it's because my phone is unlock ?
[Realme Narzo 30 5G (AKA  Realme 8 5G)] arhonts:
Good day. After an incorrect firmware update through mtkclient, the Rui 3 screen turned black and does not display anything. Replacement of the screen did not help. We tried to flash official firmware from the website, but it didn't work. If possible, please share lk2.bin so we can try to flash it. We have run out of ideas on how to revive the phone.Successfully entered and flashed in brom mode.
[Realme Narzo 30 5G (AKA  Realme 8 5G)] BGF12:
Sorry to inform you but based on my knowledge it is impossible to flash this phone!How do you entered brom mode ? Because i tried and it didn't worked for me!
[Android Q&A, Help & Troubleshooting] DrAkuma:
I'm new to forums, I apologize if this is all wrong and such. I was wondering if there is a way I can root a MetroPCS TCL IonX (T430W) running android 12 with magisk. I can't find anything for the IonX, it's all other variants of "Ion." I'm quite familiar with rooting and such, I'm just looking for the files, twrp or such. If you know where I can get them, please lemme know.

I'm sorry if this is in the wrong spot. I didn't see anything for TCL devices, I've never used forums before.
[Android Q&A, Help & Troubleshooting] roirraW "edor" ehT:
Hi! I don't see your particular device, but here (link below this paragraph) is where you can find all TCL devices we do have sections for. I am not knowledgeable about TCL, otherwise I'd help you myself, and these days on my Pixel, I don't even use TWRP to root - just Magisk, but I know this varies depending on the device and the files that are available. Hopefully, someone in one of the other TCL device sections can help you.

TCL

xdaforums.com

If you ever get a different brand device, you can look for your device or your brand at the top level of the forum https://xdaforums.com/. In the middle of the screen, there is All categories, which you can either expand to see a condensed copy of the brands and links to their sections, or click on it and it'll take you to a more expanded view of all brands we have forum sections for.

You can also use the following thread to request new device forums. There's no guarantee one would be created, but if there's enough demand, it might be.

*** New Device Forum Requests ***

Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...

xdaforums.com
[Android Q&A, Help & Troubleshooting] DrAkuma:
Thanks man, I'll see if I can get help. More or less, I need the firmware, I can do it if I have it. Thanks once again
[Android Q&A, Help & Troubleshooting] roirraW "edor" ehT:
You're welcome! I hope you can find it.
[Android Q&A, Help & Troubleshooting] DrAkuma:
Definitely looking. Thanks for the quick reply.
[Android Q&A, Help & Troubleshooting] damnthefall:
I have the T430W as well and after a month of trial and error I was able to get it rooted with magisk. I'll give you the quick summary of how I did it right now and once I get home from work I will try to get a more complete step by step guide for you.

1. Download and setup mtkclient by bkerler on github.

2. Enable usb debugging and oem unlock in developer options

3. Power off device

4. Open a terminal and mtk meta --metamode FASTBOOT

5. Plug phone up to computer. You should see the TCL logo and then black screen with fastboot mode in lower left corner.

6. fastboot flashing unlock and confirm on device with volume keys(WARNING this will erase your userdata)

7. Install LineageOS pre rooted GSI using DSU sideloader from github.

8. Either use a partition backup or adb shell then dd if=/dev/block/by-name/boot of=/sdcard/boot.img

9. Reboot to return to original system.

10. Patch boot image with magisk manager make sure the disable vbmeta option is selected.

11. Repeat steps 3 & 4

12. fastbooot --disable-verity --disable-verification flash vbmeta vbmeta.img {flash blank vbmeta image(I used the one from the google source page for DSU)}

13. fastboot flash boot /path/to/magisk_patched_img

14. Reboot and enjoy your rooted Ion X.

Or if you would like I can upload either the stock boot image or magisk patched image as long as you have done the UG67 OTA update.

We have no DA or AUTH files for SP Flash Tool and none of the current bypass methods work on our chipset, so whatever you do make sure you do not flash mmcblk0boot0 or mmcblk0boot1 as this will render your device hard bricked. The kernel source is available on sourceforge, I have gotten it to compile with no errors but haven't had a chance to test it yet. I'm working on getting TWRP or OFRP for our device compiled but haven't gotten very far. So far I haven't had any issues being rooted on the stock rom. I'm really glad that you posted this because I have been meaning to type up a guide as I believe being able to root your phone should be an option for everyone, but you posting this gave me the kick in the rear to actually do it.
[Android Q&A, Help & Troubleshooting] damnthefall:
Here is the stock boot and magisk patched boot image plus the blank vbmeta image
[Android Q&A, Help & Troubleshooting] Kireej:
python mtk meta --metamode FASTBOOT ???? not working for me
[Android Q&A, Help & Troubleshooting] jasons550i:
Thanks worked great. To be clear all you need mtk client for is getting into fastboot.
[Android Q&A, Help & Troubleshooting] iShoaibMughal:
kindly help
[Android Q&A, Help & Troubleshooting] TNSMANI:
MOD ACTION:

Thread closed as duplicate.

@iShoaibMughal

Please familiarise yourself with the Rules of XDA, especially Rule 5:
[Xiaomi 13 Pro] victormvs022:
Hi guys,

I have a problem with my Xiaomi 13 Pro when I tried to flash the "V14.0.22.0.TMBEUXM" ROM via Fastboot with the MiFlash application. After flashing my Xiaomi got stuck in Fastboot mode after displaying an error on screen. Unfortunately I checked the option that re-lock the bootloader after flashing and now it is locked.

Now I can't flash other Custom ROM:

View attachment 5901671

I tried to re-unlock the bootloader via MiUnlock and ADB but it does not recognize the device (I cannot activate USB debugging mode because the system not start).

View attachment 5901673

View attachment 5901683

Devices logs:

View attachment 5901681

Summary:

Phone state: FASTBOOT LOOP

Bootloader: LOCKED

USB Debugging: OFF

ADB recognizes device: NO

Fastboot recognizes device: YES

Can You help me to recover my Xiaomi?

Thank you very much
[Xiaomi 13 Pro] SLP27:
Try to unlock using 6.5.810 batch, https://yadi.sk/d/lYw_K3aJSTgJWw?w=1
[Motorola Edge 40 Pro  / Moto X40 (China)] jody2k:
Hello Guys

I want to link my topic of last month for my motorola X40 as I can see the moto x40 / edge 40 pro has a own XDA forum now.

Link of the topic is to be found here:

https://xdaforums.com/t/i-screwed-up-moto-x40-bricked-any-edl-mode-available.4567913/

Short story: I bricked my moto X40 last month by flashing the wrong firmware (edge 30 pro) with result my phone is semi bricked. (+ relocked the bootloader).

My phone is detected now as a edge 30 pro in firmware.

It's still booting and I can even play games on it but the touchscreen is not working anymore, touch itself works but the calibration is completely wrong, it's touching a complete different point on the screen compared where I put my finger on. So touch is unusable

I can control my screen phone with a bluetooth mouse or gamepad controller. (i'm using it for now as a switch emulator or I play some games from the play store).

I haven't managed to unlock the bootloader anymore, the option is there in developer menu but when I try to enable it, the developer menu just crashes (stopped working error).

My theory behind this is you can only unlock the bootloader once.

So this topic is for anyone has encountering the same issue as me, who knows there will be any solution in the future.

I think only EDL mode can unlock the bootloader again or flash the phone back to original firmware.

But we don't know yet how to get into EDL mode for this phone yet.
[Motorola Edge 40 Pro  / Moto X40 (China)] MAS:
Did you try using blankflash? as it works from 9008 port and probably flashes the boot image.
[Motorola Edge 40 Pro  / Moto X40 (China)] jody2k:
Yes I think I saw a post somewhere couple of weeks ago there was a blankflash file for this phone but not yet a working method to flash or use it. I could be wrong

The main problem is I can't get it to 9008 (EDL) port otherwise I could have flashed it back easily also with RSDlite or Qfil tool.

EDL mode (9008 port) is required to flash with blankflash(or any other method) if you can't unlock the primary bootloader anymore from the firmware side.

If i'm not wrong I don't think anyone has found out yet how bypass the snapdragon 8 gen2 primary bootloader to access the secondary bootloader (edl mode).

Shorting some test-points on the motherboard circuit could work, only we don't know yet which ones exactly

1 guy has tried this out I found on the russian forum:

Motorola Moto X40 / Motorola Edge 40 Pro - Обсуждение - 4PDA

Motorola Moto X40 / Motorola Edge 40 Pro - Обсуждение, Смартфон, 6,7"

4pda.to

He tried to short the circuit with test points on the motherboard and succeeded to bypass the primary bootloader and tried to get into EDL mode on (port 9008). But I think regardless of that he still wasn't able to flash it (used bad google translation from russian to english. Even he tricked the phone into EDL mode at some point he got stuck in the flashing process, my guess is there are some additional security added to this SOC to avoid this.

Edit: Maybe this is some useful info for other people reading this

Based on my previous research

Normal fastboot mode = primary bootloader (non EDL mode)

EDL mode (port 9008) = tied to secondary bootloader

The secondary bootloader is always present on a snapdragon SOC, but ofcourse due security reasons it's a bit of a secret how to access it. Guess time will tell if someone find it out how to get into EDL mode on this phone (moto X40 or edge 40pro which shares both same SOC).
[Motorola Edge 40 Pro  / Moto X40 (China)] Bofahad:
the same problem here

https://xdaforums.com/t/need-help-stucked-on-bootloader-with-no-permission.4581361/
[Android Head-Units] Gunrack:
I picked this head unit up and it works well when it works. It will work fine one day and then the next time I get in the truck it won't power on. I've found that if I pull the unit out, unplug the wiring harness and plug it back in it comes back to life. Last time I did this it hard reset and I lost all customization. I had the accessory turned on setting it back up. Turned the acc off, started the truck and it's dead again. Anyone have an idea why? Cheap Chinese torture device? Thanks!
[Google Pixel 7 Pro] stslimited84:
Anyone experiencing poor battery life after this latest patch?

My mobile network battery is very high and I'm on wifi.

Ideas?
[Google Pixel 7 Pro] EtherealRemnant:
The latest patch as in the one that released today? If so, high usage is normal for a few days. If it's the update from last month, you might consider a factory reset and setting all your apps up from scratch. Time consuming for sure but gives you a clean slate with the battery.
[Google Pixel 7 Pro] rspkt:
I concur with this assuming you're on the May update which only just was released. I'd be patient and report back after a few days at least.
[Google Pixel 7 Pro] stslimited84:
I just updated to the April patch due to a rooting error and reinstalled from scratch. Phone was fine prior to that.

Guess I'll just update to the newest one and see what happens? The strange thing is the high mobile network battery usage
[Google Pixel 7 Pro] EtherealRemnant:
If you just set your phone up from scratch, you have to give it a few weeks to learn your usage patterns.
[Google Pixel 7 Pro] stslimited84:
I understand. Reason I posted is this is new behavior that didn't happen previously combined with the culprit being mobile network battery drain. Appreciate your responses
[Google Pixel 7 Pro] pgrey2:
Yep, this is what I see too, I posted the pics in another forum and got a number of "that's odd" comments, where my overnight drain due to the mobile radio was crazy-high (this happened back in the Nov timeframe, fixed with the Jan update, and started again with March, pretty consistent, for me).

I typically charge in the AM, wirelessly, while I catch up on emails and such, so the phone had light use all day, and the bulk of the discharge was from 12A until around 9A, when it was not in-use.

We're located in a suburban area with very strong LTE and decent 5G towers all nearby, with (almost) always very low (e.g. "good") dBM signal values, for the mobile radio.

View attachment 5902317
[Google Pixel 7 Pro] NippleSauce:
I flashed the April update as soon as it was released. I have also noticed that my battery life has been a bit worse on the April update.

Furthermore, I also root my phone. However, I always do a full wipe and fresh install with each update. So, I can confirm that there does indeed seem to be a potential battery drain issue on the April build. And as you have stated, I believe that it has something to do with the mobile data scanning. However, when I stay connected to WiFi, my battery doesn't drain as quickly as it does when I turn WiFi off.

Regardless, the May update has released today and so I'll likely be updating to that tonight to see whether or not this faster battery drain issue continues.

*Edit* - The May update - although only running on my device for around 12 hours - does seem to have improved that battery drain issue that was visible on the April factory image. However, this mobile data battery issue could very well be a result of Google pushing out all of these carrier service updates. Of which, they are presumably doing so in order to test the stock OS setup for their two new devices that will be launching within the next month: the Pixel 7A and the Pixel Phold. Therefore, if carrier service testing was the culprit of this issue, then I wouldn't be surprised if we see this issue pop up again due to further mobile data stability/reliability testing.

*Edit 2* - May update was installed for a few days. My battery life is MUCH better. It is essentially how it was prior to the April update.
[Google Pixel 7 Pro] stslimited84:
Did you find any fixes? i updated to the May build and the issue is even WORSE. Phone idle for last two hours after full charge, down 12% already from mobile wifi data. Its literally sitting screen off burning 6% per hour
[Google Pixel 7 Pro] stslimited84:
View attachment 5902537

four hours of on time after full charge. 15% battery discharge - done by mobile network....ive been on wifi the whole time.

what gives?
[Google Pixel 7 Pro] pgrey2:
On the AndroidCentral forums a user referenced an actual Google support thread (which had been locked, interestingly), where they had supposedly been told, by support, to revert to 3G.

That's sort of tough to believe though, if you ask me, given the fact most carriers in Google's largest Pixel market sun-setted 3G some time ago (my carrier, TMo, did it last summer, not that I cared much, but I was tracking things).

I'd say they might have confused 3G/4G-LTE, except that they specifically called out moving from 5G/4G-LTE -> 3G, weird, eh?
[Google Pixel 7 Pro] pgrey2:
I would bet this is because the algorithmic calculation is done based on carrier-type use, which would involve pretty much any interrupts regarding phone/sms/rcs.

My guess anyway, I tried this too, one night, and saw a similar deal.
[Google Pixel 7 Pro] stslimited84:
Whatever the cause may be, it's software related and it's very aggravating. Phone was fine a few days ago
[Google Pixel 7 Pro] spoeckes:
I had the same problem with the April update. due to a change of contract i now only have lte, no more 5g. Since then the battery has held up like it used to.
[Google Pixel 7 Pro] jaseman:
I have to wonder what some people are doing to make their phones...or batteries...so awful?

I have the latest May, 2023 update installed. I happened to sideload the OTA instead of waiting but I do not think that makes any difference in the end. However, the very first thing I noticed was that everything seemed a little smoother??? (placebo effect??)

The very next thing I noticed was battery life...mine improved exponentially and it wasn't bad before the update!

For example I removed the phone off of the Google wireless charger around 5 AM, then I used it on Android Auto for a round trip of about 33 miles, and when I got home (four hours off the charger) I was STILL AT 100% Hand-of-God!

When I went to bed around 9:30 PM (yes, I'm getting old) the phone was at 90%...honest to GOD again!

Looked at the battery again around 6 AM and it was at 85%. The phone was on all night with DND activated, but everything else active.

I can only guess that one of two things are happening here...either some of you have installed crap-apps that have hosed your phones, or.....you have defective phones/batteries.

YMMV
[Google Pixel 7 Pro] mikebb00:
I haven't noticed much of a change with the battery after applying the March update, purposely left the phone off the changer overnight with battery at 100% (12am) - looked at the phone at 6am and percentage was down to 97%.
[Google Pixel 7 Pro] stslimited84:
Whatever the cause may be, it's software related and it's very aggravating. Phone was fine a few days

did you read the post or just decide it was user error b/c your battery life is fine right now?

There were multiple pictures posted of the mobile network battery drain which has been documented elsewhere and confirmed by another user in the thread.

Battery life was great until the April update then the mobile network drain started which hasn't been corrected by multiple updates and full wipes.
[Google Pixel 7 Pro] stslimited84:
that's how mine was previously
[Google Pixel 7 Pro] otonieru:
May update. Great as usual. Avg 6-7hrs SoT (which am happy with, consider i have 8 running app services and near 24h vpn)
[Google Pixel 7 Pro] HipKat:
Well, I wouldn't go THAT far....
[Google Pixel 7 Pro] cd993:
Yup, May update here and battery draining significantly more...
[Google Pixel 7 Pro] Lughnasadh:
Battery is fine for me on the May update. 8.64%/hr active drain and .57%/hr idle drain so far.
[Google Pixel 7 Pro] bobby janow:
That's really good. I usually get around 0.8% / hour overnight unless I charge to 100% which I'm not supposed to do. Then I get anywhere between 0.4 and 0.6%. For anyone reading this, if your idle drain is unwieldy install BBS and find out what's keeping your phone awake while idle. And read the first four or so posts by the OP to get things right be it rooted or stock.

https://xdaforums.com/t/app-2-2-11-dec-2022-v3-1-betterbatterystats.1179809/
[Google Pixel 7 Pro] cd993:
I let my phone completely die, gave it a full uninterrupted recharge and even cleared the battery stats too (I know, probably didn't help...) but after yesterday's fast discharge after the update last night's idle drain whilst I was sleeping was 0.5%p/h
[Google Pixel 7 Pro] schmeggy929:
What makes you think you are not supposed to charge your phone to 100%?
[Google Pixel 7 Pro] HipKat:
There is some theory that charging to 100% shortens battery life, or something like that
[Google Pixel 7 Pro] bobby janow:
Yeah exactly. But it's not uncommon among those who truly seem to know. I've read 20-80 is the range for longest battery life but I usually go somewhere higher. Just reporting what I've read, multiple times.
[Google Pixel 7 Pro] wangdaning:
Doubt you will continue to use the phone long enough for that to matter.
[Google Pixel 7 Pro] blackspp:
I took it from the charger at 8 this morning, it's now 12:11 and battery dropped to 98%. Only responded to a few chats and mails, took some pics and a 30 seconds video. I'm still super impressed with battery life as I usually end the day with 40-50% left using it all day with the regular browsing, apping, taking pics and so on. No super intensive tasks, o games (except Wordfeud and 2048).

Secret sauce:

- I switch the phone off at night so the battery wears down less fast

- I removed (adb) some apps and disabled all services I don't use

I'm still really impressed with the whole package although, to be honest, I could have kept my Samsung Galaxy Note 20 Ultra for another year.

About charging to below 100% only: many battery manufactures and appliance manufactures (cars, home batteries and so on) use charging software to keep the batteries charged between a certain range but never charge to 100%. I assume our batteries are also managed to stay > 0 and < 100%. On top of that many phone manufacturers offer options to stop charging at some percentage.

I'm not too worried about battery degradation. And in any case I sell my phone long before the battery is toast ;}
[Google Pixel 7 Pro] HipKat:
That is my stance on it
[Google Pixel 7 Pro] bobby janow:
True for some people but certainly not all.
[Google Pixel 7 Pro] wangdaning:
How many years will you use your phone? If the battery is not defective it would be 10+ years before the degradation would show any significant impact. This also depends on environment though, if you are in a warm place it will happen faster.
[Google Pixel 7 Pro] Whistler_nl:
As far as i know there's a battery management system in you phone that doesn't allow to overcharge your battery. Just like a Tesla batterypack says it's full when it's chraged the battery to 90% or so? Also there's a limit to how far you can drain the battery so there's still enough power in it not to die.