yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] captain_xyz:
Does any one have a stock Amazon recovery from fire os 4.5.3 or from the 13.3.2.8 firmware ? I made a huge mistake by downgrading to 13.3.2.8 and I know I probably shouldn't have done it but I got root access and flashed twrp on my kindle via flashify, now when I try update back to fire os 4.5.3 it just straight up fails.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Native twrp is incompatible with any firmware above 3.2.3.2. As surmised you trashed your recovery which is required to perform updates. You can extract the necessary components from a 3.2.8 bin file then create (package) a recovery image using a tool similar to the one described in this thread. I have not used this tool and can not assist you further.

Check your device to for a backup of the original recovery. Flashify can also create backups although I don't know if it does this by default.

Some stock recovery images can be used with various firmware levels. The 3.2.6 thor image here has been shown to work on 3.2.5. To my knowledge it has never been tested on 3.2.8. Use at your own risk.

You can not use a 4.5.3 recovery as you are currently on 3.2.8 (different firmware generations). You also can't use Flashify to update your system. It's only use on 3.2.8 is to flash recovery which I normally would not recommend except you have little choice at present other than going straight adb. Once you have a working recovery get rid of Flashify.

Good luck.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
That's very much open to interpretation, I would say..

If you mean bootloader, when you say "firmware", I agree with you.

BUT, for reference, I'm running 4.5.3 for everything including a bunch of

other firmware EXCEPT the bootloader (which is, of course, 3.2.3.2).

Actually, everything you need to generate a recovery image is included in .bin and your tablet.

Unzip the .bin and check the 'recovery' folder. The shell script there -when run on your Kindle- will turn the

'boot.img' and the binary patch into a recovery image (flashed right on to your device, unless you change

the script; so, be careful, check the paths in the script, and play it safe).

Good idea!

Hmm... I'm not entirely convinced that this info is accurate.

Looking at the update scripts, it would seem that the recovery is flashed first,

and possibly even used later as part of the update process..

BUT, it's best to be careful.

While I do think generating a recovery from 4.5.3 following my loose hints above

and flashing on 3.2.8 should work, I never tested this (for obvious reasons); so, I

cannot guarantee that doing so won't result in breakage...:(
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Yes - you are correct on the first point as I have acknowledged in other posts recognizing your work from which many have benefited. I must be more mindful of wording precision or provide appropriate disclaimers. That said, for the vast majority of visitors the terms 'bootloader', 'kernel', 'fire os' and 'firmware' all mean the same thing when referencing upgrades/rollbacks and options from a given starting point (bootloader may be the lone exception as it has been called out for special treatment and the gifts come from unlocking). Responses are often a compromise of technical accuracy, brevity, applicability and, most importantly, understandability. I don't claim to do any of these things well but my responses are mindful of the goal.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
And, they are appreciated by many. (-;

I double-checked the updater-script and it seems I was wrong

about recovery being flashed first. In fact, it would seem that

the updater-script only installs the necessary bits and pieces to

generate recovery from boot, but doesn't actually run the script

(not directly, anyway).

BUT, it's still true that one can use a modified version of the script

'recovery/etc/install-recovery.sh' in the updateXXX.bin to generate

a recovery.img from boot.img.. These are the files needed (also from the

same updateXXX.bin, names are relative to the root of the unzipped archive):

boot.img
system/etc/recovery-resource.dat
recovery/recovery-from-boot.p

These can be pushed to an arbitrary directory on the Kindle,

and the 'applypatch' line from the above script, modified to

use files from that directory, executed...

Example:

adb shell mkdir /sdcard/R
adb push boot.img /sdcard/R/
adb push system/etc/recovery-resource.dat /sdcard/R/
adb push recovery/recovery-from-boot.p /sdcard/R/
adb shell applypatch -b ...

Here's the original line from the script for 14.4.5.3

applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:7761920:e6c225555c10d8b547c28ad29859db38937a7d8e EMMC:/dev/block/platform/msm_sdcc.1/by-name/recovery [COLOR="Red"]f74d5a9b25ab0fc3f52440605ef6351c99ca2bf9[/COLOR] 9521152 e6c225555c10d8b547c28ad29859db38937a7d8e:/system/recovery-from-boot.p

Here's the modified line (also prepended with 'adb shell') using '/sdcard/R'

from the example above:

adb shell applypatch -b /sdcard/R/recovery-resource.dat /sdcard/R/boot.img /sdcard/R/recovery.img [COLOR="Red"]f74d5a9b25ab0fc3f52440605ef6351c99ca2bf9[/COLOR] 9521152 e6c225555c10d8b547c28ad29859db38937a7d8e:/sdcard/R/recovery-from-boot.p

Unless the target file ('/sdcard/R/recovery.img') already exists (it normally

won't), the following (harmless) warning is issued:

patch /sdcard/R/boot.img: failed to stat "/sdcard/R/recovery.img": No such file or directory

The generated 'recovery.img' can be checked

to match the required SHA-1 hash (in red above)..

Of course, this hash varies between devices and versions...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Thank you, draxie! This post will be quite helpful for those wishing to return to stock after installing an alternate recovery (twrp) or have a damaged stock recovery. I know of at least two individuals who are currently in this situation; probably several more waiting in the wings.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] slvr32:
HDX 7 still alive in 2020...

Should the new recovery work with an unlocked bootloader, or does the below suggest that the bootloader also needs to be reverted to stock and/or locked again?

I happened to use the following to generate a new recovery.img using the 4.5.5.3 .bin

adb shell applypatch -b /sdcard/R/recovery-resource.dat /sdcard/R/boot.img /sdcard/R/recovery.img f3895b2c29badf911e44bd1ec2b59eec113ee862 9590784 7a3496bfbf6029990640982b9ee6639650c17aaa:/sdcard/R/recovery-from-boot.p

and the sha1 checksum looks good on the resulting recovery.img

$ sha1sum recovery.img
f3895b2c29badf911e44bd1ec2b59eec113ee862 recovery.img

but after a stock upgrade attempt left me at a fastboot prompt, when I believe the tablet is trying to boot the stock recovery, I also discovered that the tablet doesn't seem to want to boot from the recovery.img via fastboot

$ fastboot -i 0x1949 boot recovery.img
downloading 'boot.img'...
OKAY [ 0.327s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.402s
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Not sure what (or why) your are doing here. Install vulnerable aboot using one of the two methods in the general thread. If using the manual method boot into TWRP and install any ROM, but do NOT include Magisk/SuperSU in flash package. Boot ROM to generate unlock key. Complete bootloader unlock, update to TWRP 3.x and install Lineage 14.1, GApps and the root manager of choice.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] slvr32:
The goal is to return to stock, upgrade to the latest stock OS, lock the bootloader again if necessary, etc.

I thought I provided enough context to make it clear that I regenerated a stock recovery, but that the stock recovery doesn't actually seem to be usable, possibly due to the unlocked bootloader.

I could've quoted the previous post in the thread, but this was essentially a follow-up to draxie's code snippets and the assumption that the stock recovery would actually get someone back to a real stock tablet, with working stock amazon OS upgrades.

In practice, the stock recovery doesn't seem to want to run, as illustrated by the details in my previous post.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Stock recovery restoration is theroritical with a successful case never publicly revealed in XDA forums. Several have tried and failed, albeit not with sustained effort. Uncertain what the core issue is; was never motivated to look deeper. Good luck, mate.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Why, oh why?

You _can_ restore stock recovery. The steps you took look right, but as you have correctly deduced, you'll need to flash a newer bootloader (aboot) as well.

The vulnerable bootloader is from the 3.2.x series and uses a v1 device tree blob (dtb), while the 4.x.x series switched to v2 DTB *and* uses a slightly different syntax for specifying the video device on the kernel command-line as well; so, newer boot and recovery images will not boot on the vulnerable bootloader without modification.

I'm not sure what motivates going back to stock recovery at this point. I've only ever done that before returning a device.

I'd expect that any buyer today would prefer the bootloader unlocked...

If all you want is the latest system update from Amazon, then you'd be better of using my tools (specifically, `upHDX` [although that one relies on some of the rest of the Python scripts in `tools.zip`]) for re-packing the .bin into a .zip that you can simply flash with TWRP...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
There you have it.

[MENTION=5504473]slvr32[/MENTION] - be the first to post successful restoration of stock recovery on HDX and make XDA history. No doubt it can be done, albeit why (in practical terms) remains the $64K question.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] slvr32:
I happen to have an hdx7 w/LTE connectivity, and I've had LineageOS 14.1 on it for quite some time, and I used one other ROM briefly, but the stock Amazon OS really is the most stable, reliable OS for this particular hardware., if working LTE and stable wifi are priorities.

Community ROMs on this device tend to have flaky wifi and/or non-working LTE.

More generally, I've used a handful of community ROMs over the years on several different devices, but depending on the particular need, a stock OS really does end up being the most usable, reliable OS for a particular device in many cases.

I also realize that no one has packaged a 4.5.5.3 upHDX TWRP flashable zip, because that would contradict the third-party ROM interests, root, TWRP, downgrades, etc... with later FireOS releases.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
I tend to agree. All of my newer devices remain on stock, occasionally rooted but usually not. Community ROMs rarely achieve the stability and functionality of OEM, especially with finicky hardware interfaces. Custom ROMs for HDX gizmos were (are) better but not without faults. Yet still better than FireOS v4 which struggles with modern apps and Play Services integration. If LTE is a priority then stock or the original Fire Nexus ROM are your only real choices. Only a handful of those devices exist in the wild...hence the lack of interest.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] gwardsc65:
slvr32, sent you a pm
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Actually, I'm 100% positive that I had posted on having restored to full stock years ago.

I even took the trouble of sketching the steps (although did not break it down to hand-holding step by step instructions).

RIght... I fully understand. I used to have an LTE Apollo and I kept it on "almost stock" (upHDX) for the very same reason.

BUT, you don't need full stock for that. I certainly wouldn't want to give up the convenience of TWRP.

As for upHDX not being packaged, I don't know why would anyone do that. The tool to do so is readily available.

Amazon still hosts their latest updates. Anyone can roll their own.

https://www.amazon.com/gp/help/customer/display.html/ref=aw?ie=UTF8&nodeId=201596890

Are you serious about Fire Nexus? The latest stock with all the security updates is probably a safer choice.

(Of course, at this point, that might not matter, since bad stuff kept coming even after the HDX was EOL:ed.)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
I recall that post and even commented on it. That said, Draxie 'wins' are not in the same league as the average slob (self included) that roam these forums.

First choice would normally be stock (as stated) but if one must go custom then Fire Nexus is the only HDX community ROM that supports LTE to the best of my knowledge. And no, I'm not concerned about the patch level on an Android gizmo. Where you surf is a far better predictor of potential issues than some script kiddie sitting in the airport trying to MiTM intercept your WiFi. And if one is really worried about that put a quality condom around your network comms (aka VPN) and be done with it.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] slvr32:
Funny thing, it looks like the lineageos-14.1 rom for thor was updated a day or two ago, and there's mention of LTE now working, but I haven't verified that yet.

https://xdaforums.com/kindle-fire-hdx/orig-development/rom-cm-14-1-thor-t3517481/page153
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Yep, noted that observation; somewhat surprising on a couple levels. Nice to hear from [MENTION=5749760]ggow[/MENTION] who is the undisputed SME on this device. Also appears a LOS 14.1 build released in Sept '19 restored LTE functionality which escaped my attention. There were few LTE mentions in that thread between then and now aside from what has recently transpired.

You may want to reach out to [MENTION=9596095]cl-i[/MENTION] as h/she may have some insights on LTE functionality on HDX w/Lineage.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
back2stock

Apologies for quoting my own post and probably being off-topic as well!

I made a surprise discovery today: a script called 'back2stock' dated Nov 19 2017

was hiding in one of my folders (appropriately named 'misc').

I figured someone might find it useful, although it's provided with all the usual

disclaimers, and no warranty or any implication of suitability for anything else

then potentially learning how to write unmaintainable bash scripts... ;^)

### REMOVED OBSOLETE CODE ###

I also have the distinct feeling that I may have posted this in the past,

but couldn't find it anywhere...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
In case anyone still cares, I posted a newer, better documented and more functional,

version of my back2stock script here.
[Nexus 6 Accessories] whoamanwtf:
I ended up not liking my Nexus 6, unfortunately I had already ordered two cases. I live in the western states and whoever wants to pay shipping can have the cases for free (Or at least nearly free, I just don't want to lose anymore money on them so you pay shipping and they are yours.) Shoot me a PM and just send shipping over PP and they are yours, I ended up getting a completely different phone so I have no use for them.

[IMG="cases"]http://i.imgur.com/sfnR5fb.jpg[/IMG]
[Nexus 6 Accessories] Waynehead69:
I'll take them!
[Nexus 6 Accessories] the green man:
I'll take the caseology one if it's still available!
[Nexus 6 Accessories] whoamanwtf:
Hey I probably should not have posted this right before I went to work, but when I get home tonight I will get it all situated, I am going to do first come first serve so if Wayne is wanting them both (which I think the best deal would be) then he is going to get them so thanks guys.
[Nexus 6 Accessories] 20degrees:
I don't need any but you should do a first come first pick.

Give 2 people the option to get a good deal.
[Nexus 6 Accessories] nixie2121:
if not gone, im interested please
[Nexus 6 Accessories] mmessina:
Also have interest
[Micromax Canvas Turbo A250] muftiazan:
My neighbor's phone was locked out by AVG and I dont want to reset it because of important notes and messages. I cant connect ADB since he hadn't enabled Debugging. I went to stock 3e recovery and took backup fro there and got .backup file in internal storage. I want to edit this file and remove the AVG and restore it back. How do I do so?
[Micromax Canvas Turbo A250] FSadino:
Unpack system.ext4.tar and delete AVG from /system/apps. Dont know if work but you can try.
[Micromax Canvas Turbo A250] muftiazan:
As I said before, I have stock recovery and I got .backup file format in stock recovery.

Sent from my HTC One
[Micromax Canvas Turbo A250] FSadino:
Yes i understand now, you cant have access to that file.

Make a update.zip to replace build.prop and add this line in prop file.

persist.service.adb.enable=1

Edit: flash cwm first :)
[Micromax Canvas Turbo A250] muftiazan:
Will cwm reset anything?

Sent from my HTC One
[Micromax Canvas Turbo A250] FSadino:
No, CWM recovery is just to flash the update.zip with the modded build.prop.

If you have stock rom installed, download stock rom and unpack system.img to get the build.prop file.

CWM can be flashed with SP Tools
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] neomesjasz:
Hi have rooted device installed twrp app from google play, app changed automaticly line code in platform. XML checked code is added device restarted few times formated too but still can't write any file on my micro sd card tried with es file Explorer and astro fm

Any tips?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] muzzy996:
Are you sure you added the entry into platform.xml correctly?

Does it look like this?

http://xdaforums.com/showpost.php?p=51110595&postcount=13

Note that the entry needs to be within the WRITE_EXTERNAL_STORAGE section.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] neomesjasz:
Yes looks same twrp app added automaticly http://imageshack.com/a/img673/337/rcZJX2.png
[One (M7) Q&A, Help & Troubleshooting] UglyCody:
Everytime I install a custom ROM on my HTC One M7 (AT&T), when I choose the option to reboot, it only reboots into Recovery! Can anyone help me?
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
can you post fastboot getvar all please ?

Which rom are you trying to flash ?

Which recovery are you using ?
[Verizon LG G3] jmotyka:
So i actually have two issues of concern i want to bring up in this thread, and hope there are a few who are expierencing the same issues i am so i know im not going crazy.

I would like to start by saying i am a music lover/audiophile i have over thousands of dollars of headphones and amps. Now both problems can be addressed if i purchase a usb dac but there are two reasons why i dont use portable dacs, 1) i cant use software eq when using a dac, 2) i just dont like tugging around another piece of hardware on the go.

My first issue is that from the day i bought the phone when i have any pair of headphones plugged in there is a ridiculous amount of white noise and cellular feedback that i never had on my htc one. This noise has also gotten louder over time in my left earphone. There is also always a popping noise that produces driver flex in the left earphone every time i plug them in and when im switching from app to app or navigating a handfull of apps. Driver flex is not ideal for any earphone and it can damage an earphone pretty quickly.

Second problem is as of the last couple months across all roms(stock, 4.4.4 aosp and 5.0 aosp roms) 90% of the time i plug my earphones into the port i will not have audio, i have to either open more than one audio app and start pressing play until i start to hear something from one app to the other. It started happening on lollipop roms so i thought it was only an issue native to lollipop roms until i decided to go back to a stock rom. Once i was back to stock i was able to replicate my issues. Then i went to 4.4.4 aosp rom and still the same issue.

So my questions are, Do any of you lg g3 owners experience these issues(noise,popping) and no audio output from time to time?

Have you found solutions to any or all of these issues?

Do you think they are hardware related?

I i think it is hardware related. I plan on getting a replacement phone soon to see if i can replicate my issues on a fresh new lg g3. If this is the norm for any of these issues i will be getting a different phone. Inlove the lg g3 but audio playback without issues is a big concern of mine when purchasing a phone.
[8525, TyTN, MDA Vario II, JasJam ROM Development] JPS:
Got my new Vario2 (Hermes yesterday) Straight backonto the forum after a long departure and instantly started playing with Mobile6 thanks to all the fantastic programmers on here. Only issue was having to reload al the gprs and mms data each time. After a long search on the tmobile site I found the following instructions for the UK network.

If anyone with the know how wishes to make a cab that can be installed easily each time I re-flash that would be highly appreciated and I'm sure some others will find it of use too.

Thank you in advance to any takers

How to configure Picture Messaging on your T-Mobile MDA VarioII

Setting up your connection

1. Select the Start menu and then Settings

2. Select the Connections tab

3. Select the Connections icon

4. Select the Advanced tab

5. Tap on Select Networks

6. select the button New… .immediately beneath the network drop down box and

follow the remaining instructions below to set up an internet connection

7. In the box Enter a name for these settings enter T-Mobile Internet

8. Select the Modem tab

9. Select New

10. In the box Enter a name for the connection enter T-Mobile Internet

11. Under the second drop down list Select a modem select Cellular Line (GPRS)

12. Select Next

13. In the box under Access point name enter general.t-mobile.uk

14. Select Next

15. In the box Username – leave blank

16. In the box Password – leave blank

17. Select Finish

18. Select ok three times

19. Tap on x to close the Settings screen

Setting up your Picture Messaging profile

1. Select the Start menu and then Messages.

2. Select Messaging

3. Select Menu and Tools then select Options

4. Tap on MMS

5. Tap on the Servers tab.

6. Tap on New.

7. In the box Server name enter T-Mobile MMS

8. In the box Gateway enter 149.254.201.135

9. In the box Port number enter 8080

10. In the box Server address enter http://mmsc.t-mobile.co.uk:8002

11. Select the Connect via drop down list and select your internet profile (T-Mobile Internet or T-Mobile GPRS

(Web))

12. Select the WAP Version drop down list and select WAP 2.0

13. Select OK

14. With T-Mobile MMS highlighted, tap on Set As Default

15. Select ok

Your phone is now ready to send picture messages.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
PLEASE search the forums, there is a program in progress (very nearly finished) which will apply the settings for ANY network. You will find the thread here.
[Nexus 6 Q&A, Help & Troubleshooting] zingxao:
Couple of questions. Nexus 6 has Gorilla Glass 3. Do I need a screen protector? My reason for asking is because a friend has the Xperia Z3 and it has a couple of small scratches on.

Also, does the Nexus 6 occasionally reboot? I've had mine 4 days or so and it rebooted today when I turned on wifi. That okay/normal for an occasional reboot?
[Nexus 6 Q&A, Help & Troubleshooting] jaythenut:
yes get a scratch cover

no reboots here
[Nexus 6 Q&A, Help & Troubleshooting] zephiK:
No you don't need a screen protector, would it hurt to get one? No it wouldn't hurt. It all depends on you if you want to invest $10-$15 for a screen protector or invest in a digitzer/screen replacement when you have a scratch. Screen protector is probably the safer bet.

No reboots here.