yashsingh1/xdaforums huggingface dataset:
[Fire General] najoor:
When I disable updates it breaks alexa. With this app disabled, a!exa frequently responds by saying I am sorry, I am having trouble connecting, or I am having trouble understanding right now.

Has anyone found a way to disable updates without breaking Alexa?
[Fire General] DB126:
How did you disable updates? Many contributors (wrongly) specify a cocktail of tweaks that yield unpleasant side effects.

Simply rename DeviceSoftwareOTA.apk and call it a day. If you have applied other remidies and didn't keep a log you may have to rollback and start over.
[Fire General] da-pharoah:
Hello guys looking for some help. I cant seem to get the amazon fire 7 9th gen (2019) windows drivers. They don't install. I want to follow this rooting process but the drivers don't install on my pc. I have followed all the methods provided in these posts as well as the drivers install info from amazon.com with no luck. I have dev options along with usb debug and mtp options on, but still nothing. Is there something I'm missing? any help would be appreciated.

edit:

I have even used different usb cords as well as different usb ports. still dosent install the driver.

edit2:

I'm also on a 64 bit system

edit3:

got it. I had to install a default 64 bit composite driver to get it going. dumb amazon doesn't know how to say they don't support 64bit systems. I called and chatted them with no success.
[Fire General] tomjfmu:
How do I open the metallic shield?
[Fire General] Dan_firehd:
You open the metallic shield by gently lifting it up.

There is no soldering. It is simply clipped on to the PCB.
[Fire General] tomjfmu:
If you open it, to get into bootrom mode is there any soldering? I also tried to lift up the shield with my fingers, but it wouldn't move
[Fire General] Dan_firehd:
There is no soldering.

Use a pry tool and carefully pry open the metal cover from the PCB. It is very tightly clipped on to the PCB.

See the before and after pictures of removing the metal cover here:

https://xdaforums.com/showpost.php?p=79833085&postcount=9
[Fire General] melvinp:
Rut-Ro

Brand new Fire 7 (latest gen), unboxed it, I ran the mtk-su and got root, my wife was on my case becasue we had to leave, I left everything as is and came back the next day and the OS had updated.

Now I mtk-su and it only returns:

armv71 machine

Failed critical init step 4

This platform is not supported

Any thoughts??
[Fire General] DB126:
Not going anywhere with the updated FireOS build. Request an exchange from Amazon (say the device isn't holding a charge) while still under warranty. Be sure to keep the replacement off WiFi until you have successfully blocked OTA updates (rename DeviceSoftwareOTA.apk; don't be duped by any other method).
[Fire General] melvinp:
Threw a hail marry and downgraded to: update-kindle-NS6312_user_1827_0002517050244.bin with an adb load. Quickly turned off wifi (becasue oddly enough my settings and apps were still intact), fired up adb and got to work. mtk-su was still in the directory I put it in ran it and bingo...
[Fire General] DB126:
Great - thanks for sharing! Ya put your privates on the chopping block with that maneuver but it paid off both for you and others who find your post. :)

(actually not so risky as the warranty exchange served as a safety net)
[Fire General] seansean23:
hi, can you give the exact command you ran?
[Fire General] seanton:
hi, can you give the exact command you ran?
[Fire General] melvinp:
- Download an update package, I used "update-kindle-NS6312_user_1827_0002517050244.bin" (found here: https://fireos-tablet-src.s3.amazona...2517050244.bin)

- Reboot into recovery (power + volume button)

- Select "apply update from ADB" in the recovery menu

- Run "adb sideload update-kindle-NS6312_user_1827_0002517050244.bin" (please substitute if you used a different file)

- Rebooted Device

- Turned off wifi

- Then followed the instructions at the very beginning of this thread and voila

- Valdiated root by removing bloat apps and removed OTA updates using additional adb commands,
[Fire General] seanton:
Thank you!!! :)
[Fire General] daLareid:
Anyone able to help out with Package Disabler? I did this from scratch so there's no account activated nor registrated to my Amazon Fire 7 (2019), however when running the adb command I get a message Trying to set the device owner, but the user already has a profile owner.

I've tried everything but can't get pass this.

Also tried to root using the guide here but the scripts on init.d but it's not working either, I followed the instructions except for using the R16 file because it's no longer available, tried R17 and R19 from the arm folder and it's not working, can't get root.
[Fire General] Michajin:
I have tried using the package disabler, but i could only get it to work with root. You can disable from a adb, user level that seems to be effective (there are rumors that they can be re-enabled by amazon, but i have not seen it)

Examples...

adb shell pm disable-user --user 0 com.amazon.kindle.otter.oobe.forced.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override

adb shell pm disable-user --user 0 com.amazon.kindle.kso

Try the instructions here and post what errors you are receiving.

https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213

You might have to downgrade to temp root. You can also root the hardware way (it is easy), The init.d is for temp root (it runs the mtk-su file on boot). You should look at permanent root and unlocking. With the temp root, you can install permanent root though. Depending on what version your fire is on, the mtk-su might be blocked, but reports are you can downgrade to a working version (see posts above)

Both options have instructions here, i have done it both ways and the end result is the same, full root with TWRP.

https://xdaforums.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365
[Fire General] daLareid:
Thanks for your help. I tried the temp root which enabled me to use Package Disabler, I think I wanna stick with the temp root since I wouldn't want to screw up with the hardware part.
[Fire General] Michajin:
if you have temp root you don't have to do the hardware part. Just need linux or a linux live disk to run the scripts... Lineage is about 10X better on this device in my opinion......
[Fire General] daLareid:
I'm still running the init.d from the tutorial here, how would I got about replacing init.d for Lineage?
[Fire General] Michajin:
Just follow the software method here.....

https://xdaforums.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365

Download Lineage for mustang, when you get into twrp, wipe and flash LOS.
[Fire General] nypaulie:
Tried the mtk-su method but keep failing...

I actually tried 5 different versions of the mtk-su file and keep getting the following:

paulie@paulie-ThinkPad-T61 ~ $ adb shell

mustang:/ $ cd /data/local/tmp

mustang:/data/local/tmp $ chmod 755 mtk-su

mustang:/data/local/tmp $ ./mtk-su

/system/bin/sh: ./mtk-su: not executable: 64-bit ELF file

1|mustang:/data/local/tmp $

Anyone know what I am doing wrong?
[Fire General] DB126:
Try the 32-bit variant. Another potential obstacle is a patched FireOS build. No need to try older versions of mtk-su as they will yield exactly zero benefit over the latest.
[Fire General] nypaulie:
Tried the 32bit version (19) and got this:

paulie@paulie-ThinkPad-T61 ~ $ adb push mtk-su /data/local/tmp/

857 KB/s (34312 bytes in 0.039s)

paulie@paulie-ThinkPad-T61 ~ $ adb shell

mustang:/ $ cd /data/local/tmp

mustang:/data/local/tmp $ chmod 755 mtk-su

mustang:/data/local/tmp $ ./mtk-su

Failed critical init step 4

This platform is not supported

1|mustang:/data/local/tmp $

---------- Post added at 01:34 PM ---------- Previous post was at 01:31 PM ----------

I successfully rooted my Fire HD 10 using the following instructions. Do you think the same would work on the Fire 7?

https://xdaforums.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860
[Fire General] nypaulie:
I tried it anyway and got excited when all the data started to scroll but ultimately I bombed out when typing "su" did not work. When doing this for my HD 10 I had to repeat the process a couple of times but finally got it to work. I just did a repeat on the "7" and still can't get a root (#) prompt.
[Fire General] DB126:
Latest FireOS build has been patched on Mustang.
[Fire General] nypaulie:
Please explain what your post says. Are you saying the mtk-su method no longer works on this Mustang update?
[Fire General] DB126:
Correct; follow previously posted guidance if you wish to root.

https://xdaforums.com/amazon-fire/general/fireos-6-3-1-0-amazon-fire-7-2019-t3937209/post81065293
[Fire General] nypaulie:
I Did follow that instruction set, using the software method (I'm reluctant to open the case and do the hardware fix). I keep getting this error:

paulie@paulie-ThinkPad-T61 ~ $ adb shell

mustang:/ $ cd /data/local/tmp

mustang:/data/local/tmp $ chmod 755 mtk-su

mustang:/data/local/tmp $ ./mtk-su

/system/bin/sh: ./mtk-su: not executable: 64-bit ELF file

1|mustang:/data/local/tmp $
[Fire General] diplomatic:
First off, that device needs the arm version, not arm64. Second, your firmware is not supported by mtk-su, as the tool reported when you ran it correctly. However, there is still a chance for a software-only method: see this guide. Be careful about downgrading, YMMV.
[Fire General] nypaulie:
Rooting Fire HD 7

First, thanks for your help. I am following the steps in the linked instruction set.

Did the download and ran adb reboot recovery. When I got to step 4: "Use the volume up and down icons to scroll to flash a recovery image from the ADB". As my attached screenshot shows, there is no choice for flashing a recovery image, so I need more help.
[Fire General] nypaulie:
I went ahead and downloaded the "update kindle..." bin file. When I try to use "adb sideload update..." I get an "error-closed" msg. I then tried "adb push updatekindle....bin /". After quite a while I get a "Read-only file system error".
[Fire General] diplomatic:
Well, then it's "apply update from ADB". Not sure why he calls it "flash a recovery image from the ADB".
[Fire General] nypaulie:
Yes I ran "apply update..." This gave me a choice on the Fire 7 of running "adb sideload <filename>..." This gave me the screenshot.

I've downloaded the adb version needed and will install it later and try again. I see success in my future. Thanks again!
[Fire General] nypaulie:
I was able to update my adb version which enabled me to run mtk-su. Here's my screenshot. Now I have to figure out how I can use it and what the next business is.
[Fire General] justprice:
Does this work for Fire 10?

Does this work for the 2019 9th Gen Amazon Fire 10 inch version or only 8 inch?

Thank you!!
[Fire General] slacka123:
Play Store Instructions Out of Date

The Fire 7 (2019) Tablet device runs Fire OS 6, which is based on Android Nougat (Android 7.1.2, level 25), so the correct Google Account Manager is 7.1.2

Google Account Manager v7.1.2

Google Services Framework v7.1.2

For these last two links, select the version closest to the top of the list which doesn't have "beta" in the name.

Google Play Services (32-bit ARM, nodpi, Android 6.0+)

Google Play Store (32-bit ARM, nodpi)

See https://www.androidpolice.com/2019/11/25/install-play-store-amazon-fire-tablet/

[MENTION=773514]guizzzmo[/MENTION] can you please update your post?
[Fire General] regularcat193:
I have never attempted to root anything before and am completely lost.

How likely is it that someone with zero knowledge can actually do this?

Is there a video on how to downgrade firmware and root the tablet?

While the written instructions seem very clear, having never seen it done is causing great confusion.

I have managed to get the Google Play Store onto the tablet.
[Fire General] parkskier426:
It looks like they've removed all options to install a firmware via ADB recovery. This was a friend's tablet that has likely updated itself, but I did attempt a factory reset to no avail.

Does anyone know of another way to install a downgrade?

[IMG="Latest ADB Recovery"]https://i.imgur.com/YQPghpI.jpg[/IMG]
[Fire General] theholmboy:
I haven't found the rooting videos as helpful as a thread like this... The simple answer to your main question is to start with a tablet or phone that is easier to root than a Kindle, which can be challenging. Last month, I rooted two Kindle Fire HD7's (tate) and yesterday a Fire 7 2015 (ford) and would say they both have a difficulty of about 7/10. Many years back, I rooted a LG G3 (vs985) (5/10 difficulty) and have kept it up-to-date, currently running Android 9. I also have a Samsung Galaxy Tab 2 7.0 (P3113) that I rooted many years back, reverted it to stock and used it for a few years, then recently rooted it again and would say it is about a 4/10 difficulty to root. So yes, I would opt for starting with something like an older Samsung tablet, which will help you understand how it all works, but uses a program called Odin that is user friendly and can be ran in modern versions of Windows. Rooting the Kindle (tate) requires Windows 7 32-bit (or Linux) and the Kindle (ford) currently only has Linux instructions, so that is another consideration.

One other consideration is that for any thread like this, you will want to read (or at least scan) through the whole thread and I recommend starting from the last post and working backwards. It seems like a lot of work, but it can save you time (and pain) to spend the time.
[Fire General] Michajin:
Looks like they removed it adb apply update option. If you are looking unlock or root you can via the hardware method. It is pretty easy also...

https://xdaforums.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365
[Fire General] bluepitt:
Fire 7 9th Generation. The damn thing started flashing on the home page. Factory reset made it just stay in the fire logo loop and wound not continue. Now I find that you have to have the adb turned on, I DIDN'T! ARE WE ****ED? Think so. Support is not helping with people that are speaking English as a second language. I ended up agreeing to buy a new one and the support person said they would take 15% off. I said how about 50%? They took it to 30%! Sold, I am bald now trying to get this thing working. All help found on searched such!
[Fire General] Michajin:
Is there a question or request here?
[Fire General] moxiot:
(I chuckled with this comment)

I have just begun the process of rooting. Quick question, I have noticed that there's less development for the Mustang as compared to other generations, is there a particular reason for this?
[Fire General] Michajin:
No reason, the main developer is taking a break. ggow made the first custom LOS rom, it is pretty stable. Maybe it hasn't been a big seller and developers are not into it. Ziona has taken up tweaks, and there are updates, just patches mainly. I think there was a post that had the ROM with the tweaks builds into it. The only development on any of the amazon devices lately seems to be the HD8. It is a solid device for the price...
[Fire General] JoeReichard:
I don't get it

I don't understand this where is the ground and what do I connect to a more detailed picture or YouTube video would probably help
[Fire General] Michajin:
Run the bootrom script. The shield cover would work for a ground. I piece of aluminum foil rolled up would work. Touch the red don pit to the shield cover retainer (about 1/8" away from it?) and power it on while the script is saying waiting for device.

https://xdaforums.com/showpost.php?p=79683131&postcount=22
[Fire General] ramsam:
Fire 7" 9th generation

I can boot my fire 7" 9th generation on fastboot mode how to root and install custom recovery
[Fire General] HellfireXD:
For me, when i ground this pin to the shield, the device doesn't power on and I dont see any other points labeled as "CLK/CMD/DAT0" on the board.

The software method doesnt work either.

Ubuntu:~$ fastboot oem unlock
...
FAILED (remote: the command you input is restricted on locked hw)
finished. total time: 0.005s

Ubuntu:~$ fastboot flashing unlock
...
FAILED (remote: the command you input is restricted on locked hw)
finished. total time: 0.005s

NOTE: My Fire 7 came with firmware 6.3.1.5. Do i need to find a way to downgrade?
[Fire General] Michajin:
You can't lock with conventional fastboot unlock, you have to run the bootrom script, then when you see "waiting for bootrom" short and plug in. The tablet will look dead, it will handshake run the scrip, then boot you into a hacked fastboot, where you can run the fastboot step. The mtk-su is blocked now....

Use this thread...

https://xdaforums.com/amazon-fire/orig-development/fire-7-2019-mustang-unbrick-downgrade-t3944365

The exploit is through the mediatek bootrom. When shorting in ubuntu lsusb, you should see mediatek phone or preloader (you want phone). I would nto try downgrading, i dont think it is possible on this device.
[Fire General] HellfireXD:
Before I continue, thank you for your help! :)

I figured out my issue... Like an idiot :eek:, I thought I could pass the USB device by a serial filter through to a VM and that would work... it doesnt.

Anyway, on a unvirtualized *buntu boot, It shows up but I haven't been able to get it to show mediatek phone only mediatek preloader.

sudo ./bootrom-step.sh
[2020-10-05 00:42:10.274210] Waiting for bootrom
[2020-10-05 00:44:20.712277] Found port = /dev/ttyACM0
[2020-10-05 00:44:20.743502] Handshake

* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *

Traceback (most recent call last):
File "main.py", line 161, in <module>
main()
File "main.py", line 82, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/ubuntu/android/amonet-mustang/modules/load_payload.py", line 99, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/home/ubuntu/android/amonet-mustang/modules/common.py", line 147, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/ubuntu/android/amonet-mustang/modules/common.py", line 84, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

This is my dmesg

[Oct 5 00:44] usb 1-1.2: new high-speed USB device number 4 using ehci-pci
[ +0.110424] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[ +0.000006] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0.000003] usb 1-1.2: Product: MT65xx Preloader
[ +0.000002] usb 1-1.2: Manufacturer: MediaTek
[ +0.022382] cdc_acm 1-1.2:1.0: Zero length descriptor references
[ +0.000021] cdc_acm: probe of 1-1.2:1.0 failed with error -22
[ +0.040187] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device

If it helps, the Fire 7 i have came with firmware 6.3.1.5 pre-loaded :(.
[Fire General] Michajin:
That is preloader, you have to see mediatek phone for it to work... Short and plug in during the "waiting for bootrom", may take a few tries... Unless you have a updated mediatek device. Some of the new releases have had the exploit blocked.
[Fire General] roman.r:
There is a metal cover securing access to the pins needed on a Fire 7 (9th gen) Sep 2020, anyone faced this? Does anyone know if a workaround possible / is available somewhere described?
[Fire General] virulous:
Yes. The work around is a small flat screw driver. The metal cover is only clipped on by tension, use the screw driver to pop it off.
[Fire General] progman32:
How would an updated mediatek device behave here? I'm attempting a downgrade. Shorted the pin to the shield via a soldered flying lead and this successfully interrupts the boot, but I've only been able to get the device to enumerate as preloader. If I un-short and power cycle the tablet boots up normally. Am I out of luck? Is it worth removing the PCB and accessing pads on the back?

Side question: how does the PCB come out? I'm afraid of disturbing what appears to be the touchscreen selfie cam ribbon as part of it seems to be glued to the PCB.
[Fire General] Michajin:
Downgrading likely wouldn't help. The bootrom was disabled after January 2020.

A updated device goes into preloader only.
[Fire General] progman32:
Thanks. Guess I'll have to get rid of it, no interest in using Amazon spyware :)
[Wing, P4350 General] detroit_leon:
does anyone have a program/.cab/ or anything that would help me send MMS messages?
[Wing, P4350 General] dougstoner:
Did your phone lose the ability when you flashed to a new rom?
[Wing, P4350 General] ivanmmj:
Some ROMs are not able to send MMS messages, unfortunately. I'm not sure about omega, but not all of them have a fix for it.
[HTC U11  Questions & Answers] mindmash:
Hey,

I just installed lineage os using trwp, and found that the wifi doesn't turn on. Whenever I try to turn it on, it turns itself back off. When I reset the phone using trwp, I get the error: unable to mount storage. Does anyone know how to fix this?

Thanks.
[HTC U11  Questions & Answers] necktru:
Did you format system, data, and internal storage before flash LOS??

try flashing again, but with a previous version of LOS, I think I read that problem in last release.
[HTC U11  Questions & Answers] miffymiffy:
Were you on nougat firmware? Oreo is latest firmware that works, or you could flash the oreo dsp file from leedroids thread..
[HTC U11  Questions & Answers] mindmash:
I have flashed back the stock firmware, and found that the wifi was working. I am currently upgrading the stock rom to Oreo, then I'll try flashing Resurrection Remix using twrp. Hopefully I won't find any issues with the internal partitioning.
[HTC U11  Questions & Answers] mindmash:
It worked!

Thanks.
[Android General] devashishtiwari:
Hello experts.

I am a software engineer and currently working on an evaluation module from TI (Texas Instruments). I have a AM5728 Evaluation Module with me and I have successfully compiled Android SDK 5.03 (8.1 Oreo) on it. After compilation, I found that camera app is not working (black screen for a first run and getting crashed on subsequent runs). It seems to me that board is not able to detect the camera device/module even though it is attached to the board. I probably think it is related to camera HAL issue.

However, the USB camera works completely fine when attached to the EVM and is verified using simple usb cam application. The system camera is not being detected at all.

Therefore, I would like to customize Android at a source level and add code to automatically switch the default camera to the one connected by USB when it is available. Or if switching dynamically is not possible then disable the primary (built-in) camera and make USB (external) camera as the default one.

This way all applications should detect the external (USB) camera as the primary camera. For example, if I open camera application then the device take the picture from the one which is connected via USB.

I have the Android SDK source code available with me, but I am not sure how to proceed.

Really appreciate your help.

Thanks!
[Android General] hardik_garg:
hey @devashishtiwari.

I am having a similar problem. Did you find a solution. if yes, please contact me at 2006hardikg@gmail.com, its really urgent.
[Samsung Galaxy S10+ Questions & Answers] itsmohsink:
The worst thing of Android devices is ads pop up for no damn reason, now when I am opening some apps on my galaxy S10+ Google Chrome opens automatically shows me ads of dating sites that is so freaking annoying and frustrating...is there a way to stop this embarrassing ads thing? (Don't mention Adhell3) some other option if its working on Samsung phones!
[Samsung Galaxy S10+ Questions & Answers] jemfalor:
delete all site notification which you have allowed while surfing the web.
[Samsung Galaxy S10+ Questions & Answers] Jostian:
DNS66 works well, just remember to go to Chrome://flags on chrome on your phone and search for async and disable it, then install DNS66 and voila, no ads anywhere, you can bypass the vpn created for individual apps in the DNS66 apps tab, or just select bypass system apps except for browsers in the settings on DNS66.