yashsingh1/xdaforums huggingface dataset:
[General Topics] 2PMintheAM:
Any well know brand will last you well over 2 months. Plugged in endlessly may sound risky, but in my opinion, they should last years, even if plugged in all day every day.

By well known brand, I mean something like a Samsung, Motorola, etc, because you can find some seriously cheap android tablets for extremely cheap prices, but they don't even have a name brand. The boxes just say "Android Tablet". Stay away from these. Go with a Samsung, Asus, Motorola, Sony, etc.

Another tip, a very important tip, use the standard USB cable and USB Brick Wall Adapter that come bundled with your tablets. If a cable becomes worn or breaks, I highly recommend purchasing one directly from the original manufacturer.

You certainly will not have to replace them every couple months. Depends on the tablet, but any name brand should last you at least a year in my opinion, as long as you stick with the original charging cables and wall adapters, and take good care of them. (If the tablets are prone to direct sunlight all day long, this will overtime have an impact on the device, most likely screen discoloring. As long as they're inside at average room temperature, you should be good with the tablets for a very very long time.

Sure I'm some random person giving you advice, and it's ultimately up to you to believe what I say. My posts have been a mix of facts and opinions, so do take that into consideration. I'd like to include I've been an android device owner for about 4 years, and I've owned about 11 different android phones, and 7 different android tablets. I root them and install custom ROMs, I use android devices every single day, and I would consider myself more knowledgeable with android devices than the average android user.
[Galaxy Note 4 Q&A, Help & Troubleshooting] starzxfp:
I really wanted to get a Note 4 with an exynos processor to use on the AT&T network. I was scheduled to pick one up tomorrow actually.

After snooping around more I found that the SM-N910U will not work with AT&T LTE, or so I think... (I wish it did.)

And I found that the SM-N910C will work with AT&T LTE with no problems.

I am so sick of the variation between model numbers and Snapdragon/Exynos.

I just want someone to clarify that I'm right so I can buy the proper phone.

(Wanted a Nexus 6 but now they are more expensive (6xx-650 Note 4 / 699 + 60$ for tax Nexus 6 64gb) than the Note 4, with less capabilities)
[Galaxy Note 4 Q&A, Help & Troubleshooting] zurkx:
at&t whitelists phones which it wants to work with. 910U will work with at&t lte if they allow it but they dont. suggest you ditch at&t for tmo and get a 910u.
[Nexus 7 (2013) Q&A] Kameechewa:
So I flashed CM12 to my 2013 Nexus 7 and it used the audio for the keyboard that kit kat uses and I hate the way it sounds. So I went to /system/media/audio/ui and replaced those files with with the ones from my friends 2013 Nexus 7 who is on stock 5.0.2 and now it makes no sounds. So I then downloaded stock image for my Nexus 7 from Google and extracted the system.img and took the sound files from it and placed them on my Nexus and it still won't make any sound. When I play the .ogg files on my computer they all work but when i play them on my Nexus only a few play like NFC sounds but things like Lock/Unlock and keyboard clicks won't play.

Edit: So there was an update for CM this morning and upon updating the keyboard clicks and lock/unlock sounds work but they're those disgusting kitkat sounds. Is there any way to change these to lollipop?

Edit: I figured it out so this post can be deleted.
[Verizon Samsung Galaxy S 4] YoshiFan501:
With the unified device of jflte on cyanogenmod, do i update to cm12 on jflte or jfltevzw because both have nightlies
[Verizon Samsung Galaxy S 4] YoshiFan501:
Anyone?
[Verizon Samsung Galaxy S 4] Triscuit:
I would recommend jfltevzw, the unified version "might" give you issues with cell service.
[Verizon Samsung Galaxy S 4] hugehead83:
I would say only do the jfltevzw if you're on Verizon...

How did it go?

I have the jflte on Sprint, but have been waiting for a specific jflte CM12 build for it :/
[Galaxy S III Mini Q&A, Help & Troubleshooting] LurkAshFlake:
Update

i called telus (it's a carrier/network provider here in canada) and gave my iemi, it's their.

Who's the cheapest unlocker?
[MDA, XDA, 1010 Software Upgrading] arxxx:
can u tell me how to upgrade my old phone MDA 1..its same like XDA1,,i already download the rom and follow the instruction,,but its always error..its say it doesnt connect altought the phone was perfect connect...something wrong??can u tell me why???
[MDA, XDA, 1010 Software Upgrading] arxxx:
thanks,,,the problem solved...
[XDA Assist] XDA Visitor:
I was recently flashing a rom on my rooted Verizon S5 via Safestrap on one ROM slot. I flashed the rom then downloaded the 0A8 kernel. Upon bootup, the phone was stuck on a boot loop, but I can get into recovery and download mode. I have already tried to factory reset the phone via recovery and I have also tried to put on the stock kernel again. Both were unable to resolve the issue. I have a fulll nandroid backup so wiping anything would not be an issue, but is there any way to solve this problem?

Also, when the phone boots up, it stays on the S5 boot screen and you will hear the boot sound but it will remain at that screen for an infinite amount of time. Can anyone help?

Thanks
[XDA Assist] Men_in_black007:
All Your Question/Answers Goes Here : Galaxy S5 Help Forums
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
I get to unlock the bootloader of my kindle hdx 8.9

Prerequisite:

- Bootloader shipped with firmwareversion 1[34].3.1.0 <= x <= 1[34].3.2.4 (as we use the rsa bug)

- Rooted kindle

adb shell

cat /sys/block/mmcblk0/device/manfid

cat /sys/block/mmcblk0/device/serial

create a file unlock.img with following content:

0xmmssssssss

where mm=manfid and ss=serial

encrypt it with my vortox fork of signing tool at

https://github.com/dpeddi/Cuber

./cuber_unlockbl --sign ./unlock.img ./unlock.signed

connect the hdx to a linux box and do following command:

./fastboot -i 0x1949 devices

./fastboot -i 0x1949 flash unlock unlock.signed

./fastboot -i 0x1949 reboot

adb shell

idme print

[...]

unlock_code: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMsv9S[...]WRUFx7FaA==

to get into fastboot mode you can press:

standby volume+ volume- at the same time and keep pressed

follows list of fastboot command:

fastboot -i 0x1949 getvar product

fastboot -i 0x1949 getvar version

fastboot -i 0x1949 getvar kernel

fastboot -i 0x1949 getvar serialno

fastboot -i 0x1949 getvar production

fastboot -i 0x1949 getvar partition-size:userdata|sytem|cache

fastboot -i 0x1949 getvar partition-type:userdata|sytem|cache

fastboot -i 0x1949 getvar max-download-size

fastboot -i 0x1949 boot (still untested by me)

fastboot -i 0x1949 verify (still untested by me)

fastboot -i 0x1949 flash (still untested by me)

fastboot -i 0x1949 erase (still untested by me)

fastboot -i 0x1949 continue

fastboot -i 0x1949 reboot

fastboot -i 0x1949 reboot-bootloader

fastboot -i 0x1949 oem device-info

fastboot -i 0x1949 oem idme ? (only if unlocked)

fastboot -i 0x1949 oem idme cl3an (untested by me but is destructive!)

fastboot -i 0x1949 oem idme v3rsion (untested by me but seems destructive!)

fastboot -i 0x1949 oem relock (i'm lazy to test it)

fastboot -i 0x1949 dump (don't work with current windows implementation of fastboot that i'm using now - try this)

you can use python only tool too :

http://xdaforums.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689

http://xdaforums.com/kindle-fire-hd...e-software-t3030281/post58897784#post58897784

Regards and thank to all (ralekdev, jcase, Hashcode, Cpasjuste, Vortox, draxie...)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] EncryptedCurse:
Congratulations! This is a huge breakthrough. Perhaps this will finally attract the developers these devices deserve.

Just to let you know, there are some errors upon compilation:

g++ -Wall -Wextra -Wno-unused-result -march=native -O2 -Iinclude cuber.cpp -o cuber -lcrypto
g++ -Wall -Wextra -Wno-unused-result -march=native -O2 -Iinclude cuber_unlockbl.cpp -o cuber_unlockbl -lcrypto
cuber_unlockbl.cpp:204:2: warning: "/*" within comment [-Wcomment]
/*
^
cuber_unlockbl.cpp: In function ‘int sign_image(char*, char*)’:
cuber_unlockbl.cpp:194:11: warning: variable ‘imagesize_actual’ set but not used [-Wunused-but-set-variable]
unsigned imagesize_actual;
^
cuber_unlockbl.cpp:250:16: warning: unused variable ‘hash’ [-Wunused-variable]
unsigned char hash[65];
^
cuber_unlockbl.cpp: At global scope:
cuber_unlockbl.cpp:322:33: warning: unused parameter ‘image_ptr’ [-Wunused-parameter]
int verify_image(unsigned char *image_ptr, unsigned char *signature_ptr, unsigned int image_size)
^
cuber_unlockbl.cpp:322:87: warning: unused parameter ‘image_size’ [-Wunused-parameter]
int verify_image(unsigned char *image_ptr, unsigned char *signature_ptr, unsigned int image_size)
^
cuber_unlockbl.cpp: In function ‘int check_image(char*)’:
cuber_unlockbl.cpp:135:64: warning: ‘imagesize_actual’ may be used uninitialized in this function [-Wmaybe-uninitialized]
verify_image(image, image + imagesize_actual, imagesize_actual);
^

Additionally, how exactly do we create the image file? (i.e. what format and all that)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] icedtrip:
This is great news! I'll take a further look tomorrow into trying this out. Getting late and time for bed.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
As writtten before the unlock file is x9911223344 nothing more.

This file is encripted as well using similar method like the image files.

But is not hashed... just encripted with private key.

Image otherwise is hashed and just the hash is encripted.

I'm not interested in fixing code warning... if you want pull me the fix to github. I was interested only by unlock my device.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AmazonLeaker:
Hearty congratulations [MENTION=438903]dpeddi[/MENTION] !!!!

Can you let us know which sw ver is this applicable to ?

As amazon is again allowing the roll back process with almost no questions asked, if this implies to the downgrade they are allowing its a massive win and breakthrough in HDX DEVELOPMENT (i dont exactly remember the version they are downgrading to - its the one that has been patched with vulnerability)

Edit: its 14.3.2.8

Edit 2 : i believe the answer would be NO, just compared the version number you mentioned, can there be any possibility for 14.3.2.8 version kindles to get root or downgrade or any thing ?

To be honest it would be a shame that just on software version kindle has no future and other software versions have :(

Again cheers for your achievement
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
Should be up to 3.2.4. However wit unlocked bl.. development should be a little safer.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AmazonLeaker:
Yes true bit this clearly means that 14.3.2.8 will have no development right ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
Exactly. .. encrypted unlock file isn't valid with patched openssl vulnerability. However if you want you can give a try.. i've uploaded more time invalid unlock file with no issue.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
I forgot to tell you that if you upgrade bootloader to newer image with fixed openssl you lost unlock.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rubinho:
[MENTION=438903]dpeddi[/MENTION]

I get an error message when I sign the file

I assume that this message is not normal.

My OS is Ubuntu 14.4 x64 and my HDX Modell is Thor 32GB (Bootloaderversion 3.2.3)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
Ok I'll fix the program. However if you have a signed image not empty it should be good.

Please ignore that error...

3am work not always is without stupid warning :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
fixed error, pull code again. . I confirm the error is not a true error
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mxzwhx:
Is this work on 14.3.1.0?I am little confused cause you said x>14.3.1.0
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
Sure, my wrong... I correct first post
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mxzwhx:
Thanks ,I've noticed one of step need a Linux box,but I just have a Windows PC as I think many people just like me as well,how do we fulfill that step?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
You need linux for all steps (both fastboot and signing).

I read here (at xda) that windows fastboot can't run with Kindle hdx.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rubinho:
Fastboot works fine on my Windows 8.1 x64

I use following Amazon adb/fastboot drivers.... https://mega.co.nz/#!8JtUkSyZ!UbWCYyHVlfpk51FMYzQ5wR89CLWu9gTccJFVEx0lhjI

I have the unlock procedure now been successfully completed. I think at least. :D (thx [MENTION=438903]dpeddi[/MENTION])

Do you know a command that I can query the bootloader status ? "oem unlock" does not work

with "fastboot -i 0x1949 oem device-info" comes following message ... Device tampered: false. (whatever that means)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] dpeddi:
Look at photo attached on my first post.

You should see unlock successful. Fastballs one unlock doesn't exist on our device.

Adb shell idme print should show you if unlock is ok.

You should see unlock code set with as ascii
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rubinho:
OK thx for the info.

The result was exactly as you described it have.

Thus my bootloader should be unlocked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mxzwhx:
Hello,can you teach me step by step to unlock the bootloader on Windows 8.1 64bit version ?I am afriad something would go wrong if I do it myself .

---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------

[MENTION=279255]rubinho[/MENTION], is that okay ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ScouseReaper:
Hi, thanks, Now I get error: cannot open 'mmssssssss.unlock :(. Do I need to rewrap the unlock file?

Edit: tried rewrapping without 0x and code is still incorrect :/
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Hum. Not sure what's happening. In your shoes I would triple validate your manfid and serial (for the 48th time...) and then regenerate the unlock file. Run the script in a static command window so you can pickup on any errors that are generated. Gotta be something stupid/weird that's being overlooked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ScouseReaper:
Static command window?

---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------

OK, I ran the commands again and my manfid and serial are correct, not sure what is going on here for the code to be denied.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Sorry. Simply means open a command window and execute the commands from within. Increasingly I see people use the Win 7/8 search box to issue 'dos' commands. Messages zip by and are lost when the window closes.

---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------

Grasping at straws ... you rolled back to xx.3.2.3 (or lower) before trying to unlock the bootloader? A recent post suggested you were at 3.2.8; perhaps that was a different device. As you probably know 3.2.8 can not be rolled back so the BL on that particular device can not be unlocked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ScouseReaper:
Yeah, I found a rollback image and now I am on 13.3.0.9.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Same device that previously had 3.2.8? If so you can't unlock your bootloader. Your Fire OS firmware may be showing 13.3.0.9 but the bootloader is likely at some other level that can not be exploited. Someone smarter than I can post a correction but that's my understanding.

That said, if you have discovered a way to successfully roll back 3.2.8 to 13.3.0.x -and- leverage the vulnerabilities that permit bootloader signature bypassing and unlocking then open up a stand and charge admission as there is a long line of folks stuck at 3.2.8 that would love to know your secret. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ScouseReaper:
Maybe you are right, would signing the unlock make any difference or is that it? if that doesn't work then I just wait? if so that's fine, thought I was onto something here haha. Thanks anyway bud.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
If it were that easy someone would have done it by now. Moving on.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mech_supernova:
I am stumped, my Kindle fire hdx messed up so I decided to go ahead and unlock the the bootloader, I factory reset it got it downgraded to 13.3.1.0 without much trouble then flashed the bootloader on up to 13.3.2.3.2. i got the manfid and serial file made, I took 0x453038c783 saved it in a file called unlock.img after that I am completly clueless i have no idea how to even start with the python program or linux everytime i try to open the cuber files they just open as code and i dont know where/how to put my unlock file into it, my kindle started out at 13.3.2.6
[Kindle Fire HDX 7" & 8.9" Original Android Develop] D0ubl3_X:
Hello,

steps for unlocking described by [MENTION=3510401]ceyo14[/MENTION] here
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Some additional tips/guidance here which complements the link in the post by [MENTION=729329]D0ubl3_X[/MENTION]. Although there are several different BL unlock guides/tools circulating I have found the one by [MENTION=230364]cey[/MENTION]014 works best for my limited brain power.

Unlocking is not hard but does involve utilizing tools/techniques you may not be familiar with and potentially fighting with Windows device drivers/security...especially on Win 8.1 x64. Ask targeted questions along the way; folks are generally willing to help if you have done your homework. There are no one click apks or hand holding tutorials. Grab the beverage of your choice, roll up your sleeves and plan to spend a fun evening screwing with stuff that is somewhat arcane.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mech_supernova:
thats just the help I needed I want to thank you for that most helpful post:) im all set got my recovery in place and playing around with the cm12 rom:)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hasney:
Got it done through this method, thanks so much for making an easy to follow guide.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] conan1600:
A video tutorial would help so much
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stefanero313:
Hi Guys,

maybe someone has an idear, I run NexusHD rom currently, and have TWRP 2860 installed.

I am trying to unlock my bootloader and I followed the guys as good I can, but when I flash thruw fastboot

it goes to "OFFLINE", so I see the device with

fastboot -i 0x1949 devices

D072A0A0344201K4	fastboot

but when I flash my unlock.img it goes to OFFLINE in fastboot, the way I created the unlock file was with the

cuberHDX.py script via

does anyone have an idear?

thank you very much
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stefanero313:
Hmm

has noone seen that before? I tryed it from the beginning once more but same result.

When I flash my unlock file, the devices shoes on the fastboot screen "offline" and sending is stuck
[Kindle Fire HDX 7" & 8.9" Original Android Develop] travanx:
Are you sure you typed

python.exe cuberHDX.py 0xmmssssssss

and have a file called 0xmmssssssss.unlock in your directory?

Your post should read, python cuberHDX.py 0x15e709eab4

notice what I bolded.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
This seems unusual (toggling on/off line) is likely a driver or connectivity problem. A few long shot ideas:

- try a different port on your PC

- swap cables; the stock cable is not the highest quality

- make sure all connections are tight

Driver issues are tougher to diagnose. If possible try using a different host - preferably Win XP or 7. Win 8.1 has security features that can block/interfere with communications. Better yet is a Linux box (real or virtual) but not many of those hanging around.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stefanero313:
well first of all thank you both for the reply,

I am runing linux nativ so hopefully no driver issues :)

also I just missed the 0x while coping

So the file looks okay I guess, I also created it with the original python program from GitHub it creates the exact same file as the one I have, md5sum are equivilant.

I will try a different PC, and swap around the cabels a bit. Maybe it helps, alltho I transfered a few hundred MB over this USB, but you never know ;)

thnx once more, maybe I will look for a Windooze PC just to try a different fastboot version.

---------- Post added at 08:58 PM ---------- Previous post was at 08:47 PM ----------

BAM !

So transfering data over ADB is different then over fastboot !

Removed USB extention cable and retryed

Thank you !
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Reckerr:
I'm getting lost with all these different threads. I'm lost with the cyber.python thing...everything.

I got the recommended programs I believe. I'm lost at getting the command prompt to see my HDX in bootlader. Screen says "ready" but I'm getting a bit confused at what I'm really supposed to type in the cmd prompt. I'm not even 100% sure that I have the command prompt stArted the right location.

I'll be attempting this finally once and for all on the weekend. The current Rom I'm on starting giving lots of issues nradomly. Rotation weird. Screen turning off and only coming on when rotated. Sound got wacky. Only half way + on volume creates sound. Battery life worse now. It's terrible. I need the cm12 Rom.

I look forward to weekend and hopefully some help.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Sorry for your troubles. It's pretty easy to get overwhelmed with the piecemeal information. Lots of gems in the thread; just gotta know what to look for.

Before unlocking have you tried a different rom to rule out hardware issues? I suggest flashing Nexus 2.0.5 (here) as it has proven rock solid with no bad behaviors other than not supporting LTE. Purpose of this 'test' is not to permanently revert to Nexus but to rule out other issues before taking on a bootloader unlock and CM12 which has its own set of issues.

I assume you have already flashed twrp and CM11. If you are running safestrap and/or some other rom then there may be other unsatisfied prerequisites required to unlock and eventually load CM12. What rom are you currently using?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Reckerr:
I actually didn't do any changing of ROMs for a while. You mentioned the 2.05 and I completely forgot about that.

I was on 4.5.2 flashable with TWRP because I needed the wireless display working. I got a full pc up and running and I just realised I don't have a great need for the wi display now.

So now I'm on nexus 2.05 and it is a billion times better. I still want to attempt the full unlock later(mosr likely this weekend) though. And have it done once and for all.

It was that ROM then maybe. Everything is perfect now.