yashsingh1/xdaforums huggingface dataset:
[OnePlus Nord 2 5G] Seronez:
Hi,

I updated my AOD with the newest version 3.0.41, but now AOD won't work anymore. Could someone please upload the original apk for Oxygen OS 12? Every APK from apkmirror gets me the "not installed package is invalid" error. I already uninstalled the new version with adb. Thanks in advance.
[OnePlus Nord 2 5G] Seronez:
Canbe closed I just uninstalled the update and now it works again...i just forgot it's now in the 3 dots where you can choose that.
[OnePlus Nord 2 5G] MZMuntazim:
Worked for me thank you
[Redmi Note 11 (spes/spesn)] Apple740:
Flashed my Note 11 which was on Android 11 by twrp 3.6.1. When the install was done i rebooted and the phone reboots into twrp. What can i do next?

Edit: it now only boots into fastboot, regardless if i only press just the power button or the power button + volume down.
[Redmi Note 11 (spes/spesn)] Apple740:
New attempts: the custom rom zip file on the phone is disappeared so i have to use ADB sideload to flash the rom by the pc. When the process is done i get the following error, see picture.
[Redmi Note 11 (spes/spesn)] Apple740:
Did "format data" in twrp and it boots now normally. :)
[Fire TV Q&A, Help & Troubleshooting] Schroeder09:
Hey guys. I have a 2nd gen fire TV. There are 518 megabytes of 5.6 GB of storage available. The software version is fire OS 5.2.9.3(684782320). I have a memory card in the back of the fire TV, and I have moved every single app to that memory card. The thing is still almost out of storage. I have no idea where I can check to see what actually makes up all of the items that are supposedly filling this storage. All we use this for is for watching TV. If you can put pictures or anything on a fire TV we certainly do not have any of that. This has been an ongoing issue for about 3 years. I usually clear the cache and I am able to get the warning messages to go away. Last week I move more apps over to the memory card so that every single app is located on it. I cleared the apps cache. Now the warning messages are coming up more and more frequently, the fire TV is rebooting more often, and it is notably slower. The issue is getting to a point where it needs to be fixed. Since I have no idea what is taking up all of the storage, I'm kind of at a loss except to factory reset the thing, and I certainly do not want to do that. How do I see what is making up all of the storage space and how do I clear it? Do I need to download a third party app?

EDIT: I finally got some hits on this issue when I started searching more and more with. "XDA" in the Google search. I also started to get some hits on Reddit. Here is a short summary of what I have read. The culprit is on Reddit

It's a file called mbcache.db that's the problem. It's located here /data/data/com.amazon.tv.launcher/ databases/mbcache.db

Do I need to root my fire TV to be able to access directories and delete files? That's a bunch of crap. Is there a work around to access this stuff today in 2022? Last mention of this issue on any forum is a few years old.

Edit #2: ES file explorer on Amazon is $9.99/month? Are they high? What could you possibly do with ES file explorer to get $9.99 /month value unless you are a developer?
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
You can't access that directory without root but you can clear it to delete any accumulation of data. It's completely safe (equivalent of clear storage), just run this ADB command:

pm clear com.amazon.tv.launcher

Check your available space before and after running this command to see if that's where your space has actually gone.

You might also want to download a file manager like Total Commander (free in app store) or MiXplorer and manually check the folders to make sure you don't have any junk in your Download folder, Downloader (if you use that app) folder, or any other folders left behind by old and uninstalled apps in your main storage area.
[Fire TV Q&A, Help & Troubleshooting] Schroeder09:
Thanks for the reply. So that command will clear the mbcache.db? Does mixplorer have to be adb pushed to the firetv? I'll have to look later if it's in the app store on Amazon.
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
Yes the clear command deletes all the user data for the Amazon Launcher (com.amazon.tv.launcher), including any database files like mbcache.db. It's not harmful so feel free to clear whenever you like, the Launcher just rebuilds/reloads it over time.

Yes MiXplorer has to be sideloaded, it's not in the Amazon App store but Total Commander is.
[Fire TV Q&A, Help & Troubleshooting] Schroeder09:
I'm going to try these as commands later tonight. I'm sure I could just look this up on Google, but is issuing commands to a firetv just like issuing them to a phone?

1.) In platform tools folder issue .\adb devices, .\adb reboot bootloader, then issue your command?

Does having mixplorer help much with this particular issue or will clearing these things require root access?

Granted I haven't had time to do deep searches, the last rooting attempts I saw online for a gen 2 firetv were a couple years old with notes that the root access wouldn't persist through a reboot.
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
Yes the ADB command line is the same on FireTV and Android. The easiest way to run ADB commands is to install Remote ADB Shell on an Android phone/tablet, and connect to the FireTV over WiFi.

Remote ADB Shell - Apps on Google Play

Connect to ADB running on another Android device over the network

play.google.com

If you prefer you can use a computer to connect to the command line (ADB connect <IP of FireTV>)

Having a file manager app will let you see any files that user apps downloaded, or that you uploaded. You won't be able to see system app data without root, but you can still use the clear command to delete their data.

If it's the 2nd gen Stick (Tank), there's this:

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)

Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...

xdaforums.com

If it's the FireTV 2 box (Sloane):

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Fire TV Q&A, Help & Troubleshooting] Schroeder09:
I used the above advice and issued the commands from my PC. I didn't download the app to my phone. I was able to connect with ADB over wifi. Issuing your command ( with the addition of "adb PM" or something like that added to the front) gave me a message in the PowerShell that said "successful" almost immediately upon issuing the command. However, the storage didn't change by a single MB. I then downloaded file commander on the Amazon firetv and saw all the different apps' package names. I said the same command you listed for the launcher for each of these different apps. After doing 95% of the apps the storage dropped by about 100MB.

What is there left to do? File commander lets me see all the different file says even if I can't delete a lot of them, and none of them are that large. I'm at a loss on this? There are discussions about this topic all over the internet. The only thing to do is to factory reset or root and manually delete files? That seems absurd. What was Amazon thinking? Rotting kinda defeats the point of the whole investigation anyway. I didn't wanna have to wipe the fire TV and start all over. I don't have all that time. For $100-$130 I'll just get the Amazon cube TV thing. Are these gen 2 fire tvs really this unserviceable?
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
If you open a shell prompt you will get more output, in case there are any errors running a command. But it sounds like it ran fine.

ADB connect <fireTV IP address>
ADB shell

Now you should be at the FireTV's shell prompt.

Check your user storage

cd /sdcard
du -hs */ | sort -nr | head

This will list all your user folders and their size and give you an idea if there is any trash you can delete.

The other primary area that uses up space is /data/data where app data and cache is stored but you can't traverse that directory without root. So I'm not sure how you can see how much space is being used by system apps there.

Factory reset of course is an option.

It's getting harder to run a device on 8GB, as apps themselves grow in size as well as their cache and storage requirements.

My personal bias is that the 2nd gen Cube for $60 on sale is still the best bang for your buck. It comes with 12.9GB of usable space vs 5.6GB on the sticks. And is the fastest AndroidTV (FireOS) box you can get at that price and that can stream from all the major streaming apps.
[Samsung Galaxy S22] tr0ji:
Delete
[LG K10 Questions & Answers] pabloyts:
hello I'm trying to revive my lg k4 120ar brick I'm trying to flash and I get this error could anyone solve it?

View attachment 5781939
[Android General] WillisD:
Thank you so much, I have been searching for 2mos since mine soft bricked with an ota
[Android General] WillisD:
@Viva La Android why is the firmware encrypted? i didnt see where the password is
[Android General] WillisD:
Pls delete this
[Android General] Viva La Android R.I.P.:
I'm waiting on the okay from Hot Pepper™ to release this firmware package to the public. I should get the go ahead any time.
[Android General] Viva La Android R.I.P.:
Firmware is live @WillisD
[Android General] WillisD:
I just want to thank y'all for letting me be able to resurrect this phone, first ota and got a dm-verity error and became a paper wieght. Fully fixed and booted right up. Thanks so much!!!
[Android General] Viva La Android R.I.P.:
@WillisD that's the stuff I love to hear. Glad it recovered your device. So no issues with the instructions?
[Android General] WillisD:
Not at all, but I'm far from a rookie, but they are good, was actually something different for me. Never messed with mediatek like that before. However, it said it relocks bootloader, it however left mine unlocked. So I don't know if I'm the only one, or known issue, or if for once in lucky? Lmfao
[Android General] Viva La Android R.I.P.:
What method did you use to unlock your bootloader initially? Just the standard fastboot command line?

By the way this is a phone i am presently beta testing for Hot Pepper Mobile. Very nice device and T-Mobile certified. I highly recommend this phone once it is released for the public market.

https://xdaforums.com/t/info-index-...eneral-info-discussion-thread.4522453//unread

Also, if you wouldn't mind, can you confirm that this firmware is based on Android 10 (Go Edition) please. And please post a screenshot of your kernel version, baseband version, etc., for my reference. I don't actually have a Serrano, but I would like to add the firmware specifics to this guide. In fact, if you could post the info provided by running

fastboot getvar all

It wouid be extremely helpful. Thank you
[Android General] odilonser:
Hello ! Sorry, where can I found the download link or someone can reupload this stock firmware please ?

Thank you very much.
[Android General] Viva La Android R.I.P.:
Greetings @odilonser. Technically speaking, this factory firmware mage for the Serrano is a leaked resource. Because I maintain an amicable relationship with Hot Pepper Mobile, I need to first ascertain that the company's upper echelon is okay with me hosting this particular firmware package before reposting the link.
[Android General] VenomousSteam81:
@Viva La Android what is the decryption key? if you cant do that can you upload the boot image by itself please?
[Android General] Viva La Android R.I.P.:
Sure. What all do you need? Just the stock boot image? As it stands, sharing the entire factory signed package cam delve off into ethical and even civil questions. However I have no problem sharing some individual images.
[Android General] VenomousSteam81:
Yes, just the boot image.
[Android General] Viva La Android R.I.P.:
This folder includes both boot images: boot.img & boot-debug.img; it also contains vbmeta.img, the scatter file for the firmware, recovery.img, ramdisk.img & preloader.img

72.86 MB folder on MEGA

7 files

mega.nz

If you're using the boot image to patch for Magisk systemless root, you'll likely need to disable AVB/dm-verity using vbmrta.img.with the corresponding fastboot command.

To clarify, these images

were pulled from the HPP-L55B-J-9.0.0 build.
[Android General] VenomousSteam81:
Ok, thank you! I don't like mega, but as long as i can root my phone, it should work. Ah, its another service I'm thinking of. I take that back lol
[Android General] Viva La Android R.I.P.:
Cool. Yeah Mega is fully.safe: encrypted file.srorage and end-to-end encryption file transfers.
[Android General] Viva La Android R.I.P.:
fastboot flash boot patched_boot.img

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

fastboot reboot
[Android General] Viva La Android R.I.P.:
@VenomousSteam81 ... Does the stock boot image have a dedicated ramdisk? Does the Magisk app indicate yes or no next to ramdisk? Nevermind on thatI just decompiled the boot image and saw tharthere is a boot-ramdisk.
[Android General] Viva La Android R.I.P.:
Ok guys I'm writing a full rooting guide for this phone. I need somebody to confirm the bootloader unlock command. Is it

fastboot OEM unlock or,

fastboot flashing unlock
[Android General] VenomousSteam81:
Yes, it does (at least Magisk says so). Also, can you please help me? Trying to unlock the bootloader gives me this output:

`Unlock failed - Err:0x1000`
[Android General] VenomousSteam81:
Yes, it does. Also, can you please help me? Trying to unlock the bootloader is giving me this error:

`Unlock failed - Err:0x1000` Oh, what the heck? It showed my above post AFTER I posted this one thinking I didn't post.

I have the `Allow bootloader unlock` enabled in settings, as well
[Android General] Viva La Android R.I.P.:
Typically, when fastboot returns a 0x1000 error following the initiation of a bootloader unlock command, this indicates that the bootloader isn't supported for unlocking.

MTK Client will be the likely workaround, which can exploit locked down bootloaders on a number of MediaTek chipsets. I'll post some info on the tool.

Okay, it appears that somebody has used the MTK Client exploit to unlock this device. Here's the link

https://xdaforums.com/t/hot-pepper-serrano-hpp-l55b.4470523/
[Android General] VenomousSteam81:
Ok, thanks for the guide. Already experimenting with mtkclient.
[Android General] Viva La Android R.I.P.:
It's a very effective tool, but not the easiest to configure.
[Android General] VenomousSteam81:
Yes, unless you can't enter BROM mode lol. I made a comment asking about the error I get (on the guide), and am awaiting a response. I realized I had previously looked at that guide and saved it for later reading, but forgot about it.
[Android General] odilonser:
Hello everyone,

maybe, i'm on wrong section but about this Serrano 3 (HPP-L55B) also, do you know: how to enable LTE band 3 ( 1800 ) and 3G (2100) ?

Because, i have this phone, but the pre-enabled bands on the phone is not working with the Carrier at my country.

i already try to modify the nvram.bin file but not working, maybe i make wrong modification.

Thanks !
[Android General] Viva La Android R.I.P.:
It can be done, certainly, but may require the bootloader to be unlocked. Were you successful in flashing the modded nvram.bin file back to the /nvram partition?

Because I have not yet started a dedicated general info & question thread on the Serrano 3, your question is okay here. So you're in the right section, friend.
[Android General] odilonser:
I make firmware backup using free tool, TFT MTK Tool, so i have nvram.bin and others files with Mtk_scatter file.

I just edit nvram and flash it back directly using flashmode, not on fastboot mode.

https://xdaforums.com/t/free-flashing-tool-tft-mtk-module-v7-0-zip.4502279/

TFT MTK tool support BROM mode for this device.
[Android General] Viva La Android R.I.P.:
Ok so you have successfully exploited the locked bootloader using MTK Client via BROM mode. That is certainly good news. I don't own this device, so user feedback is the extent of my device-specific knowledge.

The MediaTek mt6739 integrates the MT6177m LTE radio chip for cellular connectivity. LTE Band 3, as well as other bands, have been disabled by the manufacturer of this phone. Enabling these inactive bands will likely require a nv diag tool (also a BROM flashing protocol) to tweak the radio parameters. I'll do some research on modding the mt6177m in particular and see what surfaces.
[Android General] odilonser:
Ok, Sir, thank you in advance for this research.

I already try with META MAUI TOOL for trying to enable this bands, but not success for moment.

This is my nvdata.bin and nvram.bin if you need for this. (extract)
[Android General] VenomousSteam81:
How did you manage to get into BROM mode?
[Android General] VenomousSteam81:
That failed for me, as I've already said previously lol.
[Android General] Viva La Android R.I.P.:
Correct. I posted that question before you posted about the 0x1000 error.
[Android General] Viva La Android R.I.P.:
@odilonser, this is a resource guide on enabling additional LTE, WCDMA & GSM bands using a protocol that employs MediaTek Engineer Mode. I do know that this method has been used on a number of newer Android mobile devices, as well as some devices with the MediaTek nt6177m LTE cell radio chip in particular. So, compatibility shouldn't be an issue.

How to Enable GSM WCDMA LTE Bands On Mediatek Smartphone

Now. i will share to you one of all feature from MTK Engineer Mode. it is how to setting enable and disable GSM ( 2G ) WCDMA/UMTS ( 3G ) and LTE ( 4G) band frecuency on Android mtk smartphone.

www.teknokia.com

Also, here is a comprehensive list of the various codes corresponding with MTK Engineering Mode. https://naijaknowhow.net/mtk-engineer-mode-code/
[Android General] lunarox2014:
la contraseña?
[Android General] Viva La Android R.I.P.:
The firmware package isn't available yet for download. I'm working out some details with the manufacturer on that.
[Android General] Mrhaus808:
Where can I find it?
[Android General] DrScrad:
Have you ironed out the details about when you might be able to post a link to this phones firmware?
[Android General] Viva La Android R.I.P.:
Indeed. The links will be working again by Feb 5th. So another day.
[Android General] DrScrad:
not today by chance?!
[Android General] Viva La Android R.I.P.:
The firmware is live
[Android General] DrScrad:
Same link as OP?
[Android General] DrScrad:
Nevermind.. gracias mi amigo
[Android General] Viva La Android R.I.P.:
De nada Esse
[Android General] Alkuam:
Does the dm-verity error keep showing after flashing? It's doing it to me, but the phone will boot now.
[Android General] WillisD:
No, but get the usual jive about the bootloader being unlocked, even had a software update the other day
[Android General] Alkuam:
Interesting, I wonder why this one still has the error.
[Android General] Viva La Android R.I.P.:
It isn't an error. It's merely a persistent notification during the boot sequence that indicates the bootloader is unlocked.
[Android General] Alkuam:
I never unlocked the bootloader, and didn't the guide say that flashing the firmware this way would lock it again if it was unlocked?
[Android General] Viva La Android R.I.P.:
Generally yes, the bootloader will be relocked if in an unlocked state, depending on the settings you use with SP Flash Tool.

Just so I'm clear on your issue, can you post a photo of the notification or error you are referring to? Thanks
[Android General] Alkuam:
I can't post a picture at the moment since it isn't my phone and the owner isn't home right now.

It's the dm-verity corruption message that shows up during boot.
[Android General] Viva La Android R.I.P.:
So the error specifically mentions dm-verity?
[Android General] Alkuam:
Yes, it's the same message that showed up before flashing. The phone at least boots up now.

I've considered disabling the message in fast boot, but I'd like to be able to enable it again later just in case. I haven't found the command to do so yet.
[Android General] Viva La Android R.I.P.:
When you get the opportunity, post a photo of the notification. I don't want to assume and give you erroneous instructions. I am pretty sure I know what's going on but I want to be fully sure. Thanks
[Android General] Alkuam:
Will do, thanks for being quick to respond.
[Android General] Viva La Android R.I.P.:
By the way I do believe I was mistaken earlier when I stated that yours was a notification and not an error. At first I thought you were seeing the Orange State notification during the boot sequence, indicating merely that the bootloader is in an unlocked state. If you are getting a dm-verity notification during boot, it does sound like a type of error. My bad for being presumptuous on your issue.

Once you post the error and I can confirm the issue with certainty, I believe I have a resolution to make the persistent boot error disappear.
[Android General] Alkuam:
No worries, here's the error image. Shortly after pressing the power button a few times the error message disappears from this screen and the phone will boot.

View attachment 5879219
[Android General] Viva La Android R.I.P.:
I have a solution that should work for removing that persistent error and getting your boot sequence back to normal.

Backup any important data you wish to keep that is saved on your device. Boot your device into recovery mode. Select factory data reset from the menu and proceed with the option. Once the reset finishes, power your device off. Now, reflash your device with the firmware using SP Flash Tool. Rebooting should now be normal and without the error. But, if not, let me know and I have another thing to try.
[Android General] Alkuam:
Why will flashing it a second time clear the error when it didn't the first time?
[Android General] Viva La Android R.I.P.:
Because your /userdata and /cache partitions were not formatted before the first flash. A factory data reset performs both of these actions. I can't guarantee this alone will correct the boot sequence, but I do know that not formatting /userdata and /cache before a flash can sometimes cause errors. It's definitely worth trying. If this doesn't work we can manually disable dm-verity.
[Android General] Alkuam:
Does it make a difference that I tried clearing the cache partition and doing a factory reset before the flashing the first time, or does it need to be done after flashing the firmware because it tried to factory reset with the corrupted version?

Also, is there a command to enable dm-verity? I was only able to find the comand to disable it.
[Android General] Viva La Android R.I.P.:
I don't know about a.command off top of my head, but a hex editor can be used to disable and re-enable verity. The factory data reset may not work if you already factory data reset first time around. If you want to skip this and disable verity, we can jump straight to that. You will need to unlock your bootloader to disable verity. Here's my guide for that procedure.

Serrano 3 Bootloader Unlocking & Rooting Guide

Out of curiosity, is your Serrano 3 the QLink variant?
[Android General] Viva La Android R.I.P.:
@Alkuam, as you inquired earlier, the command to enable dm-verity is:

fastboot oem enable_dm_verity

Give that a try first.
[Android General] Alkuam:
It is indeed the QLink variant.

Thanks for all your effort. I'll give this stuff a try if the phone bricks again, for right now it seems to be working (as well as it can anyway) for now.
[Android General] MachoRetro:
If anybody finds it helpful Here is a pack of OTA updates to go from j9 the OP posted to j13. they still haven't fixed the abi even though there have been lots of updates, some of you may have noticed that they have disabled the arm-v8a set entirely so no 64bit or programs that rely on it....
[Android General] Viva La Android R.I.P.:
Very nice. Thank you for sharing. I will host these in the downloads section if that's ok with you and credit you with the contribution.