yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] jjosemata:
Hello, I Once bricked my firestick, sent a message to amazon, with in 3 days

and they sent a new one, and did not want the bricked firestick back

so later on i found a guide on how to unbrick a firestick

they both still working fine
[Fire TV Q&A, Help & Troubleshooting] SweenWolf:
You will need to reinstall the MX Player.

Uninstall the app first.

Connect with firestick using adb

Install the app using this command

adb install -g MX.apk

Here MX.apk is the name

Firestick sometimes doesn't allow changing storage permissions after the app is installed thats why you will have to use the above mentioned code to give the necessary permissions at install time.
[Fire TV Q&A, Help & Troubleshooting] atlantis187:
I have my own ext. usb hard drive connected to the firestick to watch me mp4 movies using mx player but for some reason the video artwork doesn't display properly it seems to be zoomed in, is there any way to fix this?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
As you know the Note 20 Ultra, Received its last Major One UI Version which was Android 13/One UI 5 I thought I would port Lineage OS.

And Continue to Support it for a while, with Major Versions, hopefully, all the way to Android 15/16.

Follow the developments here:

{Mod edit: Link removed}

Any Questions Ask here

Exynos only

No ETA PLEASE don't ask
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Phaze1585:
Is this going to be official?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
Yes it will be
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] NightshadeTheDev:
Proof of being official? Any ETA?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
No ETA yet as I'm still working on it
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] blackbravo:
wow nice, lets do it
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] jomolocco:
Exynos ?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
Yes
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] NightshadeTheDev:
Official proof? Statements?
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
Bro are you okay? I literally told you when it's built I'll apply for it. Stop asking
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Oswald Boelcke:
@Raheem280900 Thread has been moved from the development section, for which it didn't qualify, to the Guides & News section. Prior to your next posting, please read the announcements and guidances that are stuck at the top of every forum like

RULES for posting in Development

I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier Only the following topics are allowed in DEVELOPMENT area: [DEV] - Development for any...

xdaforums.com

However, I've removed the link from your opening post. Please review the XDA Forum Rules that I partially quote below:

Last but not least and just to mention if you eventually intend to publish a ROM on XDA. In accordance the XDA's policy regarding the GPL you will be required to provide a link to your kernel source. Please be aware that XDA enforces this mandatory requirement.

I hope a vivid and fruitful discussion develops in this thread - and as you said without any questions about ETA's - that supports you in the progress of your ROM development. Do not hesitate to report any "ETA posts" (best via the report function), and we're happy to remove those from the thread on your behalf.

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Raheem280900:
I understand
[Samsung Galaxy Note 20 Ultra Guides, News, & Discu] Nomaan Asim:
thanks man and good luck
[Google Pixel 7 Pro] amtrak23:
Editing the build prop on my old Pixel 3xl worked great for tethering with the native hot spot, but I'm not seeing anything similar for the 7. Is there a newer or better way to hide the data usage from Verizon that I'm not seeing?
[Google Pixel 7 Pro] viper8u2:
I am using this on old grandfathered data plan (true unlimited)

https://xdaforums.com/t/at-t-hotspot-tethering.4510051/post-87634819
[Google Pixel 7 Pro] simplepinoi177:
that's amazing! can't believe you guys are still on that grandfather (more like great-great-great grandfather) unlimited plan!

I originally had it too on my LG Voyager when it was $30 unlimited and kept it throughout my 3 Motorola Droids -- so I originally had the plan from '07 and tried to hold on to it until '15)! But when Verizon kept raising it more and more incrementally to $50+, it wasn't worth paying all that much if I wasn't going to be using up to 60+GB at least (per line)...and then they friggin brought back unlimited but with restrictions and "priority" only up to the first whatever-GB (that's why I stay in regular alotted GB with carryover, at least it's not throttled)....

I hated the small print that they could keep unlimited and not throttle it, but it didn't say anything about not increasing the price for the grandfathered plan either...

Still amazing you guys are still on something that started around '07!
[Google Pixel 7 Pro] amtrak23:
That's interesting, thanks.

Did you get an email from Verizon when you pop the sim in asking you to add a hot spot package?
[Google Pixel 7 Pro] amtrak23:
I'm about to dump it finally. I have had this line since 01 or 02 and they just keep getting worse. It's like each additional year of loyalty makes them try harder at being terrible 😅.

For some reason Dish is up on a tower across from my business and their 5g has been working pretty decent for the last 2 months. And I have to be about the only person using it as there is nothing else around there except vehicle traffic. So I'll probably give it another month and see if anything goes wrong with Dish and then drop Verizon once and for all.

I have the Dish service for free for the next 21 months, so that will help offset some of the overpriced Verizon billing for the last two decades.
[Google Pixel 7 Pro] simplepinoi177:
I'm with you....I got my line in '02....it really kinda feels/means something sticking to it for so long.... But if one gets too complacent and not able to recognize a better deal, it's unfortunate; I admire you being able to have a better option and/or being able to break away...
[Google Pixel 7 Pro] viper8u2:
No I did not. I have the unlocked version and did remove all verizon stuff that it tried to install right away
[Google Pixel 7 Pro] rester555:
Best way is to use the magisk module for tethering bypass. Or rooted app VPN tether.
[Google Pixel 7 Pro] zetsumeikuro:
Yup, use the Magisk module to enable tethering does the same thing is the build prop edit. I used it no problem on the OG unlimited data plan with Verizon.
[Google Pixel 7 Pro] AngelNine:
Don't you have Unlimited contracts in America, I pay 60€ a month for mine in Germany (from Telekom).

Or what is the problem here with tethering
[Google Pixel 7 Pro] EtherealRemnant:
Tethering is not unlimited here. I think the highest cap on a consumer plan is 40 or 50GB right now unless you get Visible which is unlimited but throttled to 5Mbps.
[Google Pixel 7 Pro] AngelNine:
Wow, I use hotspot or USB tethering all day and thus create a little over 1000GB data volume ;)
[Google Pixel 7 Pro] EtherealRemnant:
Our networks couldn't handle that in a lot of places. Sometimes when the network is busy here, I'm lucky to be able to load a webpage.
[Google Pixel 7 Pro] eloko:
Root the phone, VPN Hotspot from playstore... Works like charm
[Google Pixel 7] uhero2:
I received today my pixel 7 and I'm planning to root it. I wonder what are the downsides of rooting... For example, on my previous phone (oneplus 7), unlocking the bootloader would change widevine from L1 to L3... Will I lose widevine L1 if I root the Pixel 7? Will I still be able to update via OTA? Are there any other downsides which I need to be aware of before rooting? Except for google pay, which I don't use
[Google Pixel 7] dewri21:
No, you won't lose Widevine L1

Yes, you will get OTAs. However, it's failing to install on mine. Might need to unroot and install the update (I am not sure).

I can't think of any other downside.

For banking apps to work perfectly, do these:

1. Repackage to hide the Magisk app

2. Enable Zygisk in Magisk

3. Enforce DenyList in Magisk

4. Configure DenyList and check all the boxes for the apps you want to hide root access

5. Use AirFrozen to freeze Magisk (unfreeze whenever you need to grant root access to any app)
[General Questions and Answers] sharkstalk:
I am having issues booting into my unofficial TWRP installation on my Moto g stylus 5g after attempting to install an unofficial modded LineageOS image.

My problem:

I try to boot into TWRP through the command line on my computer using

fastboot boot twrp-boot.img

, but my new phone disconnects from my computer before the command can finish. Though TWRP is already installed and I can access it by entering recovery mode without my phone needing to be connected to my computer, the touchscreen on the installation does not work. The touchscreen only works if I use the

fastboot boot twrp-boot.img

command.

My drivers are the latest version: 33.0.3.

I unlocked the bootloader. To do this, I:

Tapped on the build number to become a developer.

Enabled OEM unlocking and USB debugging.

Unlocked my bootloader.

I installed TWRP recovery. To to this, I:

Downloaded the unofficial TWRP image linked in the first paragraph, as well as the Magisk ZIP.

Ran

fastboot boot twrp-boot.img

while in bootloader.

Copied the image and the Magisk ZIP from my computer to my phone.

Installed TWRP using "Install Recovery Ramdisk".

Installed Magisk.

I attempted to install LineageOS. To do this, I:

Downloaded OTA ZIP, copy partitions ZIP, and boot image from the LineageOS thread linked in the first paragraph.

Flash booted the boot image.

Selected ADB Sideload mode in Lineage recovery.

Ran

adb sideload copy-partitions-20210323_1922.zip

and

adb sideload LineageOS-Modded-19.1-Osaka-V2-OTA.zip

on my computer.

I attempted to re-access TWRP recovery, after Lineage recovery seemed to replace it. To do this, I:

Ran

fastboot boot twrp-boot.img

while in bootloader.

Installed TWRP using a different method than the previous installation (maybe "Install using this image") because I couldn't copy the installation files to my phone as my phone was no longer writable.

After I rebooted I could no longer use the touchscreen to navigate TWRP. That is, until I figured out

fastboot boot twrp-boot.img

worked. But after I attempted to enter ADB Sideload mode using TWRP and install one of the ZIP files I needed to install for LineageOS (

copy-partitions-20210323_1922.zip

), my phone began periodically turning black and disconnecting from my computer, again.

It had been turning black, disconnecting, then turning back on and reconnecting on a regular interval while I was trying to unlock the bootloader. I almost made a post about it. When I tried one more time, just to get the error message I could copy and paste, the command I had been trying to run ran fast enough and it worked. What I had done differently that time was I ran the command right away, without running

fastboot devices

.

After a while the phone stopped disconnecting periodically. After I installed one ZIP, it started again.

How can I get my phone to stop periodically disconnecting from my computer? How can I access TWRP again?
[General Questions and Answers] Droidriven:
First of all, the command that you tried to use is not even the correct command for fastboot booting TWRP(unless your TWRP file is named "twrp-boot.img" and if the file is stored in your fastboot folder on PC). The correct command is:

fastboot boot twrp.img

The command you typed isn't even an actual command, that I know of. The command you typed is trying to tell fastboot to tell TWRP to boot a boot.img, which, makes no sense at all and isn't how it is done.

There is:

fastboot boot twrp.img

And

fastboot boot boot.img

As far as I know, there is no such thing as:

fastboot boot twrp-boot.img

The way fastboot commands typically work is:

fastboot <what you want fastboot to do> <what you want it to do it to>

In your case, you want to use fastboot command, so, you type: fastboot

You want it to boot a .img, so, you follow that with: boot

You want it to boot a twrp.img, so, you follow that with: twrp.img

If you put that all together in one command, you get:

fastboot boot twrp.img

This command is typically used to boot(not flash) a live TWRP session on devices that have locked bootloader because they can't actually flash TWRP "onto" their device with a locked bootloader. This command would probably actually boot your twrp.img if it is stored in your fastboot folder on PC and if the file is actually named "twrp.img"(you can rename it to "twrp.img" if it isn't). But, it wouldn't be booting the TWRP that is installed in the recovery partition on your device, it would be booting a live TWRP directly from the TWRP file in your fastboot folder. In other words, it boots on your device "from" your PC "onto" the device without flashing it, instead of booting on your device from the recovery partition on your device.

If you wanted to flash the twrp.img, the command would be:

fastboot flash recovery twrp.img

Fastboot followed by what you want fastboot to do(flash recovery) followed by what you want it to do it to(twrp.img).

But, all of that is beside the point because you say you already have TWRP installed. If you already have TWRP installed on your device, you don't need to use the "fastboot boot twrp.img" command line. You should be using adb, with this adb command:

adb reboot recovery

This adb command that I posted is used to boot into TWRP on devices that already have it installed. It is also used to boot into stock recovery if stock recovery installed. In other words, it boots yo whatever recovery you have.

Hopefully, you understood all of that without my wording confusing you.
[General Questions and Answers] sharkstalk:
Hello. Thank you for responding. "twrp-boot.img" is just the name of the file on my computer. I changed it to "twrp.img".

I know I don't have to boot a live TWRP session from an image when it is already installed. However, whenever I try to use the TWRP I already installed, I cannot press anything becaue the touchsceen doesn't work. When I boot from live, that touchscreen works. It would be good to know how to fix the touchscreen on the installed version, but I'm willing to make do with booting from live if that is possible.

When I use "fastboot boot twrp.img" after renaming the file (it gave me a "no such file or directory" error before renaming the file), I still have the problem where it loads for a few seconds, then my device does black and disconnects from my computer, then soon goes bright and reconnects to my computer. This is what this looks like in the command line:

fastboot boot twrp.img

Sending 'boot.img' (98304 KB) FAILED (Status read failed (No such device))

fastboot: error: Command failed

Now it is not as though my device was never connected. I can use "fastboot devices" to verify it is connected when the screen isn't black. Also, the output looks different when my phone isn't connected at all:

fastboot boot twrp.img

< waiting for any device >

In one instace, the phone is connected and then disconnects. In the other instance, it is never connected.

My phone disconnects from and reconnects to my computer periodically. That is, roughly every 33-34 seonds. It reconnects quickly without my input (roughly every 4.5 seconds). I used a stopwatch to make sure of this.

Spoiler content hidden.

I tested using "fastboot boot twrp.img" at the beginning of a connected interval. The command ran for the whole 33-34 seconds before the phone disconnected and it gave me that same error. I don't think that command took so long to execute when my phone wasn't turning black periodically. I can run other commands like "fastboot devices".

When my phone isn't connected to my computer, it doesn't turn black every 33-34 seconds.

Entering "adb reboot recovery" produces this error:

adb reboot recovery

error: no devices/emulators found

"adb devices" shows no devices attached. That has always been the case when running adb commands in the bootloader. I can run them when my phone is turned on normally (there is no OS so I can't do that now).

Thank you for your advice. Do you know anything about the phone disconnecting?
[General Questions and Answers] Droidriven:
Try this, type:

fastboot devices

Then type:

fastboot reboot recovery

Or

If your device has a bootloader mode, try this, type:

fastboot devices

When it returns the serial number, type:

fastboot reboot bootloader

If you have a bootloader mode/menu, it should boot to that, then either select "reboot recovery" or type:

adb reboot recovery

Or

fastboot reboot recovery

ADB may or may not work in bootloader mode, if you have it.

Are you certain that your bootloader is unlocked and are you certain that you correctly flashed TWRP recovery to the correct partition and that the TWRP.img that you flashed onto the device is an actual TWRP recovery .img and not some kind of modified boot.img? I ask this because in your post above, you typed:

fastboot boot twrp.img

Then it returned

"sending "boot.img"(98304 KB) Failed"

This implies that you are using a boot.img, not a recovery.img/twrp.img. I think your file may be some kind of boot.img to be used in association with something to do with flashing/using TWRP or a boot.ing for your device that is meant to be flashed via TWRP(TWRP can flash .img files)

You can also try booting into your one-touch working TWRP, then, connect a USB hub to your android device and connect a mouse and keyboard, it should natively support the mouse and keyboard, you can use the mouse and keyboard to work inside TWRP to make selections.
[General Questions and Answers] sharkstalk:
Thank you. I tried doing "fastboot devices" then "fastboot reboot recovery" and "fastboot devices" worked and returned a serial number but "fastboot reboot recovery" kept running until the screen turned black and the phone disconnected from my computer. The same thing happened when I tried "fastboot devices" then "fastboot reboot bootloader".

I remember unlocking it by using I code I got from the phone to get another code I got from the Motorola website. It says "flashing_unlocked" on the screen when it hadn't before. I'm pretty sure I unlocked it unless it's supposed to say something else. I've seen another Motorola that just said "unlocked" but it wasn't the same exact device.

I am not certain I flashed TWRP to the correct partition.

I will try connecting a mouse and keyboard so I can use TWRP.
[Samsung Galaxy A30s Questions & Answers] UltraVegito_420:
Sup, just had this problem like 30 minutes ago lol, and then I said to myself "would that even work?..." and guess what, it worked!

I guess you want to know how to unbrick it lol, here's how + ur welcome + i bet you thought your phone bricked lol

Press down vol- + power until it powers on and keep on holding down, as you can see it keeps on rebooting as long as u keep on pressing down the buttons, now we have to get into download mode, its kinda tricky tho -

Firstly, put the usb into the charger BUT not completely, halfway. Now press vol- + power and hold until it restarts AND as soon as the screen goes black

1- completely connect the USB

2- release the power button (dont release the vol - button) and at the same time press the vol+ button

Thats it, you should've now booted into download mode - if it didnt work and the screen went green and crashed, keep on trying and do it as quickly as you can. If you cant pull it off, ask meho. at least your pne isn't bricked, it's only tricky to fix it.

Once you're into dowload mode, use EFTSU flash tool and flash it with your firmware version (you can find it in etsu . com)

You can also flash it with ODIN and the non-modified recovery image, or just factory reset it with the original ROM and start again.

and this time around be careful trynna twrp flash, me too ofc, i wont even do it anymore, i was just messing around lol
[Samsung Galaxy A30s Questions & Answers] zzmak:
It works, thank you so much! :-))
[Samsung Galaxy A30s Questions & Answers] Shishir7889:
Bro How long will it take ? Please answer, this is very important
[Samsung Galaxy A30s Questions & Answers] UltraVegito_420:
To flash it? To get into download mode?

The flashing and re installing the rom should take about 10 minutes or so, about getting into download mode it's a mix of luck, patience and speed. But yeah about 10 tries? 20 at most?

Have you managed to do it yet? I'm sorry for the late reply.
[Touch Pro, Fuze Themes and Apps] Chefdecuisine:
I get my imported Euro Touch Pro to use on AT&T in less than 2 weeks!! Anyway, any suggestions for ROM's, Emulators and apps would be cool. I know of apps like Gyrator, google maps and stuff. So really, a program that you guys really enjoy, Thanks to anyone who posts. :rolleyes:
[General Questions and Answers] tralph3:
So I'm planning on learning how to port roms to (currently) unsupported devices. The phone I currently have for testing is an Alcatel 3X (2019). I have already unlocked its bootloader, which luckily was an easy process, so I'm covered on that front.

Problem is, I haven't found many guides detailing how to do it, and many ask for previous experience with phones that I simply don't have. I have tons of experience with Linux and CLI, but I've never delved into Android's development environment. I've never built AOSP or anything like that for instance.

But before I even begin with any of this, I'd like to know what I should take into account, and what precautions I should take to ensure I do not screw up the device. It'll probably be hard to find the stock ROM and recovery if I ever brick it, so I would need to know how to back it up. That I guess is my *main* concern, since you can unscrew yourself from most situations by just flashing the stock ROM.

What I'm looking for is basically some tips and advice before I get to it from more experienced users. Hope I don't bother with such a broad question.

Thanks.
[General Questions and Answers] EonOfBlack:
If you're wanting to build for an Alcatel device, you're most likely not going to have much luck as they don't seem to release kernel sources. If you're wanting to just see how the basic build process works, I recommend following a guide from Lineage OS. https://wiki.lineageos.org/build_guides
[General Questions and Answers] tralph3:
Ah, so these kernel sources are needed? No way around that?

Hey! I just found the kernel source code here: https://sourceforge.net/projects/alcatel/files/5048Y_5048D_20200508.tar.xz/download

So that's good right? My particular model seems to be 5048A, but pretty close I guess.
[General Questions and Answers] Fytdyh:
If you want to delve inside Android development I strongly suggest Xiaomi as your first devices. They share the entire code and everything is at your fingertips. Plus some devices already have so much custom rom support. Alcatel isn't the same, you will struggle a lot.
[General Questions and Answers] tralph3:
I already have a Huawei phone on which I installed an unofficial custom ROM. Since the phone is old and it's not getting updates anymore, I wanted to get into it to update it myself. But since it's my daily driver, I can't just test on it.

I just happen to have this Alcatel device because a relative of mine recently changed their device, so I can use it to test on it. I do not have a Xiaomi device nor could I buy one anyway.

I have found both the kernel source code and some firmware files for the phone. Is this enough to get started? Even if it's a pain, I want to learn how to do it.