yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).

EDIT: Sorry for the earlier drama; you were headed for a cliff ...

Recheck the guide (post #1) from the thread you linked. Note there are

two

sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
No worries!

1. Yes, I had a backup.

2. Nothing got broken, so everything is peachy.

3. The way that post is written, there is absolutely no easy way to tell (for the average user) that you still don't edit the file with build prop. All it appears is that you need a different roll back file for 3.2.5 and 3.2.6 variants instead of the earlier versions.

Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."

However, I thank you for the added information. I'll give it a whirl and see if that works. It would be nice to get beyond at least point C so I can get to the steps I want to do. I keep getting stuck at the point just before where things get nice.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Glad nothing got busted!

It's an old post created before 3.2.5+ was released. I do not know if the OP is still around. As many others have commented the hdx forums are generally a mess (with a few notable exceptions) as the landscape is continually changing. No one has the time/energy to create and validate step-by-step guides given the number of permutations/combinations and high risk of bad outcomes given a touchy device with limited recovery options...especially for those who can't install twrp and/or unlock their bootloader.

Note to newbies

: Many tinkerers come to these forums thinking all the cautions are the byproduct of excessive hand wringers blowing smoke out of a certain orifice. Hey, if I create a brick I'll just whip out my magical fastboot cable, arsenal of fastboot commands and make everything right again. Err, no. Fastboot cables don't work on the HDX nor to most other recovery techniques. Tread carefully...respect the kindle. Rewards will come soon enough.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?

"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,

. . . . .

7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."

I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.

I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Tanks for the thanks. As a new comer I struggled a bit and got help from some kind souls in these forums. Giving back ...

It is a tethered operation as you probably gathered. Step 4 means you need to put the .bin file in the same folder on Windows where install.bat lives. If you edit the batch file you'll see it generates a signed flashable image from the bin file and then issues a bunch of adb commands on your behalf. For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.

Footnotes:

- when you download the batch file be sure to use the blue "download now" button. Filename should be "rollback.zip" .The orange button yields an executable called "rollback.zip.exe". Probably fine but since I can't see into it can't tell for sure. Also, make sure to download the file appropriate for your device (7"/Thor or 8.9"/Apollo).

- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.

- I would strongly recommend flashing twrp immediately after, test and backup of you stock rom from within twrp. Leave the image on your kindle if you have room.

- Once everything is working to your satisfaction flash the nexus rom (v2.0.5) and optionally the 3.2.3 bootloader update as described in earlier posts. Read up on any caveats.

- (optional) Unlock your bootloader. This not necessary to run Nexus and CM11 but is for some CM12 builds. An unlocked bootloader also opens additional recovery options should you loose twrp. That said, unlocking the bootloader is not for the faint of heart and carries its own set of risks.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
Okay. New headaches.

First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.

At this point I figure 1 of 3 things happened. Either:

A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer

B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?

or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.

So what am I missing?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Hum. Everything seems ok. Bin file is in the correct location (/storage/emulated/0). Make sure OTA is enabled using the same tool/technique you originally used to disable (there are several methods) and reboot. Some posters claim they had to toggle it on/off a few times. While my device recognized the update fairly quickly (minutes) others mentioned it took a while. Keep checking settings->device->system updates. Some say the update did not take until WiFi was

disabled

. Might want to try that first. I recall seeing something about airplane mode but can't immediately find the post.

btw, you can mitigate the automatic update risk by making sure there are NO WiFi profiles on your device and you are not in range of any open hotspots (if possible).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
Well, still no dice.

I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.

Very frustrating.

I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Sorry for your troubles. One or more of the following are likely culprits:

- OTA capability not fully restored (try HDX Toolkit if you haven't already)

- ensure the .bin file name matches exactly and is located in the proper folder

- Verify .bin MD5 on the device (use a tool like hash droid) MD5=0F2BC5278C057E7A6B4823B0F68D0727

- use notepad to view the batch file; make sure all the files made it to respective directories on your HDX

- repeat the preliminary steps with your device tethered

If everything checks out then the real fun begins. You'll need to comb threads for others who have experienced a similar problem. You are looking for some morsel that may provide a path forward. Frustrating - yes! One reason there are not step-by-step tutorials as everyone's device seems to respond differently; too many uncontrolled variables. Not sure anyone really knows what all those variables are.

Remain calm and don't do anything crazy. Be wary of fixes that involve manually modifying build.prop or flashing via adb. Both are legitimate tools/techniques in skilled hands. Used incorrectly they can (and usually do) yield a brick.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.

No idea what I did. It just started playing nice.

14.3.1.0 now installed. I'm going to go get a drink. :D
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Funny how some devices take their time processing update files. Would love to know the criteria for checking and if processing can be manually triggered. Don't forget to disable OTA or keep WiFi off as long as there is a version of stock os in the system partition. One you load nexus or some other rom OTA worries will be history.

Edit: Enjoy that drink; you earned it :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
So I thought I would just report back with a final update as of 20 minutes ago:

Finally got the device rolled forward to 14.3.2.4

Re-rooted

Re-safestrapped

Backedup

Partitioned

And Nexus 4.2.2 running perfectly fine in Rom slot 1.

I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.

:cool:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.

Don't forget to reblock OTA if you haven't already. Enjoy your 'new' device :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.

In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.

I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.

If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
Second thing I did. ;) Rebooted into the stock rom and retested. KB works fine on that slot. So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.

I haven't had time to do any more playing with the tablet - Wife's birthday, but I'll retest once I know more. Should probably make a new thread however....
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] begalund:
Well, that's verified. :good: Although on the plus side, I did have a completely problem free rollback to 14.3.1.0, got twrp installed, and then cycled through a couple of the roms available looking for one that worked with the KB. Again, much thanks for all the assistance - including the assistance you lent to another user in the main thread - it helped immensely with getting twrp working on the first attempt. :victory:

Native Nexus - no go. It had the same issue. Eventually found it, but never recognized any key strokes. :crying:

Swapped to CM11 and at first it appeared to not work either (more on this), as the rom never got past the boot stage, so I bootloaded and realized I made an error (forgot to mount). Then the rom loaded but everything crashed on opening (rebooted again, wiped and reinstalled) now everything worked but the KB - I'll come back to this one.

Was about to try magic beans when I read something about the KB being "finicky" - so I swapped back to native nexus and played with the BT a bit. after 20 minutes of trying it never synced up, so I went back to CM11.

Turns out it does actually recognize it. You need to turn the KB on, then press its BT pair button, and then have the system search for new BT devices (in that order). It still has an issue where certain apps like titanium backup (or anything else that makes root calls) cause the system's BT to drop the KB - but it does find it and it works just fine 90% of the time. And when it does drop, it can be reset pretty easily in settings by removing the pairing and going through those steps again. You'll also have to do this every time the system is first turned on and you want to use it. A bit aggravating, but better than not having it any functionality or needing to swap back to FireOS.

Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus. ;)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Thanks for posting your BT findings with various HDX roms (below). Helpful to others who may be experiencing similar issues. I agree Nexus (based on Jellybean) is getting a bit long in the tooth. I stick with it given overall stability for the apps and and devices that I use including a AmazonBasics keyboard which pairs fine. I have been monitoring the HDX CM11/12 threads and will likely move there as the few remaining issues of concern to me are hammered out. Been running CM11 on another device (HD) for 15+ months; great rom that brought new life to an aging device.
[Kindle Fire Q&A, Help & Troubleshooting] 6Slipknot6:
Hey,

Does anyone know where these things are located in my Kindle Fire:

Episodes downloaded from Amazon

My Amazon account information
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Which system version is on the device?
[Kindle Fire Q&A, Help & Troubleshooting] 6Slipknot6:
Kindle System version 6.3.3. I don't know what Android version it is though.
[Android General] k02a:
Hi all,

I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.

If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).

I have included my .config file. Feel free to use and reconfigure it as you like.

The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.

Good luck!

Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
[Android General] newbit:
Hey k02a,

thanks! I was looking for that, and installed it over the custom install feature and works flawless.

But there is one more thing, and maybe you can help me. I am looking for a tar version for android

that supports the --H ustar option like the linux one. To create odin packages within the phone.

I cannot find anything usefull for this. Any Idea? Maybe cross compile?

Cheers

NewBit
[Android General] k02a:
Good to hear that the binary worked on your device too!

Regarding the lack of flags and options in BuxyBox, I assume the developers have made a trade-off between functionality and binary size. - and in your case, the need for supporting the -H ustar format (e.g. for making Samsung/Odin images) have obviously not been considered. ;)

Anyway, to get around this problem, I looked at my LG G3:s tar binary and discovered that it obviously supports the ustar format. I have included this file and hopefully you are able to use it as well. I hope this will help you a bit.

Kind regards,

k02a

shell@g3:/ $ /system/bin/tar --version
/system/bin/tar --version
tar (GNU tar) 1.16
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

...and this:

shell@g3:/ $ /system/bin/tar --help
...
Archive format selection:

-H, --format=FORMAT create archive of the given format

FORMAT is one of the following:

gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
...

Here is the MD5 hash sum:

shell@g3:/ $ busybox md5sum /system/bin/tar
busybox md5sum /system/bin/tar
d19775629f7f966e65bf1de7e2f695cf /system/bin/tar

Some kind of integrity verification in Linux (Slackware 14.1).

bash-4.3$ file tar; md5sum tar tar.zip
tar: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
d19775629f7f966e65bf1de7e2f695cf tar
e72aefb1060bc70725a1e2e0d432c9e0 tar.zip
[Android General] newbit:
Bamn, it's done! Thank you so much. It works great, this is exactly i was heading for! I own you a favour!

Btw: I have a Samsung Rugby Pro I547C with Android 4.1.2 and CWR.

Cheers

NewBit
[Android General] k02a:
I'm just glad to be of some help.

Take care

k02a
[Android General] Halcyon:
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
[Android General] newbit:
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.

Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.

Cheers

NewBit
[Android General] Halcyon:
Thnks , sorry what should i send you? You mean a busybox installer pakage?
[Android General] newbit:
Nooo, the busybox installer pakage is actucally that what you wanted!?

I ment a working update zip for whatever, but known as runable. So I could just add the code

for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated

the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.

It worked on my S3 GT-I9300. So give it shot and me a feedback.

How do you proof if busybox is proper installed?
[Android General] Halcyon:
Seems goot , thanks
[Android General] k02a:
Great, you already seemed to solve it even before I logged in! :good:
[Android General] momojuro:
Via Terminal Emulator or on ADB, you can type "busybox" after you got superuser's permissions and check the version. :)
[Android General] exodius48:
[MENTION=4747585]k02a[/MENTION] Does this busybox support x86 intel device?
[Android General] gopu136:
[MENTION=4747585]k02a[/MENTION] i rooted my lenovo a7000 today. busybox installer shows busybox 1.21.1-jb installed in /sbin. so do i need to install busybox 1.23.2 and where to install? /system/xbin? and if yes then do i need to uninstall older one from /sbin?
[Xperia Z3 Q&A, Help & Troubleshooting] RockStar2005:
Does anyone who's had the Z/Z1/Z1s/Z2 recall initially have STAMINA mode issues that were corrected with the phone's first MAJOR update?? If so, please tell us more. I'm having issues and I'd like to know if perhaps there's a history of updates correcting this or not.

Thank You,

RockStar2005
[Xperia Z3 Q&A, Help & Troubleshooting] Newbyallthetime:
Stamina mod

Just got my z3 few days ago. When I do activate stamina mod my mobile data remains active even in stand by. It shoudn't or I miss something? Some help please! Thanks!!
[Verizon Samsung Galaxy S 4] streetdk:
Hi, I just finished flashing the Hyperdrive ROM, and my WiFi doesn't work. I try enabling it, but nothing happens. I've looked on the thread about WiFI issues, and found this:

The following was already set to false in my build.prop:

ro.securestorage.support=false

Yet, my WiFi still won't turn on. Help please!
[Verizon Samsung Galaxy S 4] meazz1:
Try this gogolies-wififix-VZW-FN2-NC2-w-modules-SS.zip

https://www.androidfilehost.com/?fid=23487008491963696
[G 2014 General] bluehacker007:
There are a number of reasons one may want to change their WiFi mac address that are not worth discussing here. The point of this guide is only to provide instructions for making the change on a KitKat 4.4 2nd Gen Moto G. It might work for Lollipop but I've not tested it.

This requires root access.

Go to the WiFi settings panel and open the menu at the bottom right corner.

Click 'Advanced' and write down the MAC address shown (second to last entry)

Use your root enabled file explorer (ES File Explorer is one example) to navigate to /persist and copy the file called 'WCNSS_qcom_wlan_factory_nv.bin'

Paste the file in a place where you can edit it (ex the downloads folder)

Download a hex editor app and open the file from the location you just copied it to

You should be able to find a set of characters in this file that matches your MAC address - make sure that the set matches exactly what you wrote down before

Change the characters to a new MAC address of your choosing and save the file

Using your file explorer, rename the original file 'WCNSS_qcom_wlan_factory_nv.bin' in the /persist directory to something like 'WCNSS_qcom_wlan_factory_nv_bak.bin' to create a backup file

Copy and paste the modified copy of 'WCNSS_qcom_wlan_factory_nv.bin' from your Downloads folder (or wherever you put it) to the /persist folder

Reboot and check your mac address as detailed in steps 1-2 to ensure that it has changed. This change will be persistent.
[G 2014 General] zman01:
I used this small apk to change it:

https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer

I think it's easier to change with one of the apps from the google play.