yashsingh1/xdaforums huggingface dataset:
[G4] d4rkfun3ral:
thanks for the message, but i cant find the article on google..im using a built in bluetooth btw.....can u PM me with the directions ? really appreciate it if u can help...
[G4] G40:
To the Guy with the bluetooth sycronization problem. yes it does work on the s200. I am using it now.

Here is how to do it for windows XP.

1.disconnect your phone from your pc if it is connected.

2. Find the bluetooth icon in the windows control panel and open it.

3. Under the device tab if you see your phone delete it.

4.under the Options tap check the turn discover on box. The other 3 should already be checked.

5.go to the COM Ports tap and click add.

6.select Incoming (divice initiates the connection ) and click ok.

7. Look at the the com port # given in the table. And write it down.

8. Click ok and close the bluetooth devices window.

9.right click the ActiveSync icon on

Your system tray and click on connection settings.

10.check the allow connections to one of the following check box. And in the drop down right below it pick the same com port as the one you had written down.

11. Click ok to close the connection settings window

12. Open activeSync on your phone. (i made a short cut to it in my start menu.)

13. Click menu and click on connect via bluetooth.

14. You mite be asked to make a bluetooth partnership on your phone. Click yes.

15.click new partnership on your phone. Then click your pc from the list when you see it.

16. Then click next.

17. Enter a pass key on your phone.

Click the bluetooth icon on your pc and enter the same pass key.

18. Click next and finnish on your pc and when asked do the same on your phone.

19. Now it is set to setup to use activeSync via bluetooth.

20. To use it. open activeSync on your phone. Click menu and click connect via bluetooth. That should get you on.
[G4] finsterling:
Thanks man. Now it works :) .
[G4] 3to4:
Thank you. It works on my TD2.

I was looking for a way to do quick GPS when I am on a trip in a hotel room with cabled internet connection only.
[Galaxy S 4 Q&A, Help & Troubleshooting] Poroto:
So yeah, both menu and back buttons dont work after performing a OTA update, what could be happening ? This is my current status:

[IMG="about device"]http://i.imgur.com/uq3hrSI.png[/IMG]

I wiped cache and factory reset through stock recovery and it wont help, any idea?

Please help me out!
[Galaxy S 4 Q&A, Help & Troubleshooting] irishdh:
Cant help but im in the same situation as you.

Dial *#2663#, my touch fw does not match and I cant fix it for life of me, might fix your problem though.

Phone's Touch key FW version :0x10

Part's Touch key FW version : 0x12
[Galaxy S 4 Q&A, Help & Troubleshooting] Poroto:
Mine also doesnt match, what does that mean?
[Galaxy S 4 Q&A, Help & Troubleshooting] Poroto:
Could anyone please help me out here? :(
[Galaxy S 4 Q&A, Help & Troubleshooting] chashmaa:
Me to also does not match. 0×10 and 0×1c.
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
In case anybody cares, here's a pure C reimplementation of 'cuber.py'

(my own earlier reimplementation of [MENTION=4450207]vortox[/MENTION]'s signature.py).

This is what I'm using in my '1-Click' bootloader unlock VM...

See 'grep ^gcc' for "build instructions". ;)

Hack, you can probably build this for ARM and run it right on your very HDX tablet... (-;

UPDATE (JanuaryFebruary 2017):

OK; so, [MENTION=1370456]zivimo[/MENTION] had built this for ARM, but people still haven't noticed.

I repacked his binary from a .tar.gz to a .zip archive and decided to spell out the instructions for use.

Perhaps, this helps... With the right bootloader in place, and adb/fastboot installed (and working),

the unlock is as easy as follows...

Download and extract unlock.zip (SHA256: e40e3010f8eccfa9cbd1e73eecac30cf799099d183de23b2d256fc3407f143f6e5db0b8d82c8fd2a25a22b0a598014d22a2ec33cef27a8d4b65a36acde08f27a)

to the same directory that holds the adb and fastboot executables (unless you have added them to your PATH)

Click on get_code.bat in the extracted folder

-- optional (but commonly required) step(s) --

fix root (roll back, if you need to), flash vulnerable bootloader

[you'll definitely need to perform at least some of these if the last step fails]

Click on unlock.bat in the extracted folder

The archive also includes .sh variants of the .bat files for convenience.

You could also just click to show the hidden section and cut&paste... (-;

[STRIKE]unzip cuber.zip[/STRIKE]
adb push cuber /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/cuber
adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'
adb pull /sdcard/unlock.code
adb shell rm /sdcard/unlock.code /data/local/tmp/cuber
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.code

NOTE: download and extract the attached 'cuberunlock.zip' and run the above commands

in the directory where 'cuber' got extracted to.
[Kindle Fire HDX 7" & 8.9" Android Development] vortox:
Nice job! Originally I wanted to use OpenSSL BigNum too, but I hadn't enough time and Python was easier to use :D
[Kindle Fire HDX 7" & 8.9" Android Development] zivimo:
hey,

made a static compile with an arm debian (jessie). seemed the easiest solution to me. compile command:

# gcc -fPIE -static cuber.c -o cuber -lssl -lcrypto
# strip cuber
# ldd cuber
not a dynamic executable
# ./cuber
Usage: cuber [RSA-bytes] < data > sig

seems to work. arm(!) binary attached.
[Kindle Fire HDX 7" & 8.9" Android Development] chin_bone:
ok draxie, you pointed me here but something seems to be missing. i downloaded unlock.zip, put the files in my adb directory. when i run get_code.bat, it pushes cuber to the kindle in the right directory, changes permissions (dont see any errors there) but then stops saying the system can't find the specified path. Whats funny is i used es file explorer to check the paths in the script, and they are there so not sure where the hang up is.
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Did you check all three paths?

/data/local/tmp

/sdcard

/sys/class/block/mmcblk0

The 2nd one _may_ be problematic if you're on SafeStrap.

I don't know why. I'm yet to install that on one of my test

devices to investigate. (Or, was that the 1st... ;))

The 0 in the 3rd one may actually be a 1 on some systems.

I have a few extra lines in my VM script to work around

that, I can easily add that here as well, if that turns out

to be the issue.

BUT, to try and troubleshoot: how far does the script get?

If it didn't complain with the permissions, the 1st path is probably OK.

Does it print your manfid/serial?

If so, mmcblkX would be right as well.

Any chance that you're on SafeStrap?

Can you push/pull to/from /sdcard?

- - - - -

On a second thought: I've only ever tested this on Linux.

String quoting on Windows may work differently, and could *royally* mess up how that more complex command is interpreted.

I'll test tomorrow; it's like 20 past 1am here. I need to get some sleep.

In the meantime, as a workaround, you could just hard-code your manfid/serial, and replace this line:

adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'

by the decidedly much simpler:

adb shell 'echo 0xmmssssssss | /data/local/tmp/cuber > /sdcard/unlock.code'
[Kindle Fire HDX 7" & 8.9" Android Development] chin_bone:
It's all good draxie, i figured out what i was doing wrong with the other procedure, that damn STEP 2, once i did it, everything fell into place. Bootloader unlocked and now just trying to figure out which rom to try first. Thanks again, you guys are great and i know how valuable everyones time is. :good:
[Kindle Fire HDX 7" & 8.9" Android Development] pdanforth:
I keep hitting road blocks, I am rooted and on Fire OS 4.5.5.2 I click get code a screen flashes up then I click Unlock and my Kindle boots to the Grey Kindle screen with Fastboot underneath and nothing else happens. Same happens when I copy and past the code into ADB. What step am I failing at? Thanks for the help!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
[MENTION=5828306]draxie[/MENTION] - I have no experience with this tool; python/gmpy2 works reliably for me. Sorry to pull you in ...
[Kindle Fire HDX 7" & 8.9" Android Development] pdanforth:
I am up and running now, unlocked and running kk-fire-nexus-rom-thor-20161017. Play store is also up and running.
[Kindle Fire HDX 7" & 8.9" Android Development] draxie:
Did you end up using some other method, or did these scripts work for you in the end?

Either way, others may find useful if you could share whatever worked for you. (-;

Unfortunately, I still haven't had a chance to test these scripts in Windows;

so, I couldn't answer your first call for help in a good way. If there's something

wrong and there's enough interest, I'll be happy to fix it as soon as I can.
[Kindle Fire HDX 7" & 8.9" Android Development] pdanforth:
[MENTION=2226076]stangri[/MENTION] did my unlock file and I used this thread to unlock https://xdaforums.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982

I had trouble making the Unlock file, once that was done and some help from other users I am now up and running!
[General Questions and Answers] Alessioromatm:
Is possible to fix proximity sensor calibration without root, how? If is not possible, is there a way to turn off permanently it? I ask this because on a huawei y625 during whatsapp or facebook call, the screen turns off but doesn't turn on if the receiver doesn't refuse the call.
[General Questions and Answers] droid_god:
A trick for you.

I tried it coz of same problem.

When dialling any call or reciving it. As soon you enter chatting. Switch off the screen using power button. Doing this will switch off procximity sensor during call and you can wake up screen by pressing power key again.

Hit thanks if helped

Well anyway i liked that ninja hathori pic of yours
[Kindle Fire HDX 7" & 8.9" General] draxie:
UPDATE 2022-03-05: Network Access Snafu

During the last week or so, a server-side issue caused 1-Click to fail

either silently or with a "1-Click needs network access!" message

on startup. If you experienced the above, please try again!

Changed:

VirtualBox 6.1.x support (tested with 6.1.16)

works fine on Linux with Firefox and USB2 ports

tends to be flaky on MacOS with Safari; PLEASE use Firefox or Chrome!!

may need to connect via a USB2 hub or try different ports and cables

More accurate state assessment (i.e. rooted/unlocked/etc)

More aggressive planning logic

always look for ROM/GAPPS/SU in internal storage

may end up offering choices that make very little sense

Assorted fixes and improvements

hopefully fewer new bugs were introduced than old ones fixed

Unchanged:

No prerequisites on the device side

no root needed

full stock is OK

stuck in fastboot is fine

heck, it even works with _some_ soft-bricks

Does NOT work on Windows

1-Click is a virtual machine and a script that starts the VM in VirtualBox.

Unfortunately, VirtualBox on Windows fails to pass certain USB devices

including the HDX in bulk mode from Windows to the VM.

Network access required to grab the right aboot + TWRP for your device

Optional TWRP magic to auto-install ROM.zip, GAPPS.zip, and SU.zip from internal storage

PM me for a personal link and please state your regular

HOST

operating system.

Gotchas:

Requests without HOST OS information will be ignored.

Naturally, the same applies to requests with a Windows HOST OS.

Running 1-Click inside another VM is almost guaranteed NOT to work.

Link requests should be sent at the earliest 2 weeks after join date.

Freshly joined members are encouraged to spend some time

familiarizing themselves with the details of working with this device

by studying the relevant threads in this forum.

If you send a request be sure to monitor your account for replies!

A response should arrive within a week (or so), but the link is only valid for 2 days.

Don't miss your chance!
[Kindle Fire HDX 7" & 8.9" General] DB126:
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).
[Kindle Fire HDX 7" & 8.9" General] draxie:
Any takers?

BTW, this works with already unlocked devices also, :p

if anyone is willing to do some independent testing.

This is how I tested also... should be completely harmless. ;)
[Kindle Fire HDX 7" & 8.9" General] codeshane:
Ran this against my HDX 7

Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..

> fastboot -i 0x1949 oem device-info

kindle fire [fastboot]

oem device-info...Device tampered: false

Ok.

I'll do some more testing later.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Thanks for reporting back!

The puttytel message is normal: the serial port it's talking to

disappears when the VM shuts down.

If/when you test again do check your Kindle after the fastboot prompt

appears but **before** you hit [Enter] in the puttytel window!

You should see "Unlock code correct" in green,

if the unlock worked...

Other than that, since you seem to have fastboot working, you can use

fastboot -i 0x1949 oem idme ?

to see if your device is unlocked (see here for a list of commands).
[Kindle Fire HDX 7" & 8.9" General] codeshane:
C:\>fastboot -i 0x1949 oem idme ?

...

(bootloader) board_id: 0c0400

(bootloader) serial: xxxxxxxxxxxxxxxx

(bootloader) mac_addr: 00BB3Axxxxxx

(bootloader) bt_mac_addr: 00BB3Axxxxxx

(bootloader) productid: 0

(bootloader) productid2: 0

(bootloader) bootmode: 1

(bootloader) postmode: 0

(bootloader) bootcount: 203

(bootloader) panelcal:

(bootloader) time_offset: 0

(bootloader) signature:

(bootloader) idme done

OKAY [ 0.359s]

finished. total time: 0.361s

I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort! :D

Update:

Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155

Happily considering ROMs to blow-away Amazon's 'os' with :D
[Kindle Fire HDX 7" & 8.9" General] DB126:
Thoughts:

- take a backup of your current rom before flashing; leave it on the device until the new rom is stable (simplifies recovery)

- if you get a response from 'fastboot -i 0x1949 oem idme' your bootloader is unlocked!

- once you overwrite FireOS there is no chance of loosing root due to Amazon actions. OTA capability is baked into FireOS - not the device firmware.

- If you like AOSP go with Nexus v4. Any of the other HDX roms (CM11, CM12, SlimLP) are also fine choices. Each has a few minor quirks but no major 'gotchas'.
[Kindle Fire HDX 7" & 8.9" General] codeshane:
Sorry for the delay, wrote back a while ago but I guess it didn't post (cellular, pfft.)

Went for the Nexus v4 rom, which is running great so far. Thanks again for such a brilliantly simple unlock utility! :cool:
[Kindle Fire HDX 7" & 8.9" General] zXiC:
I have a few questions.

1. How can I tell I have a vulnerable bootloader?

I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?

2. Where do I start with this?

Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.

3. After the unlock where do I go from there?

I'm so out of the loop I don't know what's the ideal stable rom to use :D.

Thanks, I'd appreciate any help :).
[Kindle Fire HDX 7" & 8.9" General] DB126:
Check your FireOS version in the stock slot. If 3.2.6 or below you can unlock the bootloader. The rollback procedure depends on the current version of FireOS. Report back and we'll go from there.
[Kindle Fire HDX 7" & 8.9" General] Cl4ncy:
Just a little add-on to [MENTION=5488402]Davey126[/MENTION]'s info:

3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first. ;)

Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!
[Kindle Fire HDX 7" & 8.9" General] draxie:
Just a quick comment: since there are no known adverse affects of a failed unlock,

you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..

If the unlock fails, you could move on to figuring out if downgrading is an option.
[Kindle Fire HDX 7" & 8.9" General] DB126:
True!! But for for the 'typical' Kindle user (I know...sterotypes) working with a Windows host the effort to unlock far exceeds that of simply checking the FireOS version if still installed.
[Kindle Fire HDX 7" & 8.9" General] fuxkamazon:
Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!
[Kindle Fire HDX 7" & 8.9" General] draxie:
More accuracy please! (-;

Hi there,

I'm convinced that I can help you,

but I would need a more accurate

trouble report...

In the meantime, I'll try to give some background

and possible causes and remedies to what I think

might be your problem. ;)

1-Click relies on VirtualBox's USB filter mechanism

to pass through any USB device with Amazon' s

vendorId (0x1949) to the 1-Click VM.

This may not always work.

The most common reasons are as follows:

No device is connected.

I presume this does *not* apply... :o

The device is in use.

This could happen easily, e.g. if you were browsing files on your Kindle.

Apart from possible privilege issues (see next bullet),

these kind of issues are usually solved by simply disconnecting

and reconnecting your device while the VM is running.

This is the most common/likely case, which 1-Click also tells you about..

Have you tried this? (Your report is not very clear on this.)

Possible lack of privilege.

I've only encountered this on Linux (as described in the first post),

but, then again, on all the Windows boxes I tested on, my user is

in the Administrators group; so, this may still apply there.

BTW, I'm guessing that you are on some 32-bit version of Windows,

although I must admit that the "windowX86" moniker in your post

doesn' t make this crystal clear.

Global USB filter rules in VirtualBox may override the rule used by 1-Click.

This only applies if VirtualBox had already been installed

and configured with global USB filter rules before 1-Click.

There may be other reasons, but the above should cover

the most obvious/common cases.
[Kindle Fire HDX 7" & 8.9" General] fuxkamazon:
ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,

Welcome to 1-Click

mount: proc mounted on /proc.

mount: sys mounted on /sys.

mount: dev mounted on /dev.

* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available

ning. starting it now on port 5037 *

* daemon started successfully *

Please make sure ADB is enabled on your Kindle

and connect the device to your computer

In case you don't already know, ADB is enabled by turning on the

'Settings/Device[ Options]/Developer Options/Enable ADB' option.

If 'Developer Options' is missing in 'Settings/Device[ Options]',

tapping 'Settings/Device[ Options]/Serial Number' seven times

will enable it..

Hit [Enter] to continue

No device appears to be connected..

You may need to disconnect and reconnect your device

Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized

so hope you can find whats going wrong. ty!
[Kindle Fire HDX 7" & 8.9" General] draxie:
This looks fine. The question is what you did next..

Have you tried disconnecting and reconnecting your Kindle

as the message above suggests?

(BTW, since this was the only direct question in my previous post,

I sort of expected you to answer that, but now you get another chance. ;))
[Kindle Fire HDX 7" & 8.9" General] conan1600:
just tried this. i had rooted my kindle when root first came out without safestrap as i didnt like all the restrictions of safestrap. i installed twrp much later and then cm 11 for twrp without an unlocked BL. tried this one click and had to disconnect and reconnect the tablet at one point, no biggie. at another it sat there with no instructions till i hit enter, but it did complete and said it was successful. so ty very much. at some point soon ill try a rom that requires an unlocked BL and see that my BL is really unlocked. great program if it really did work. will donate soon
[Kindle Fire HDX 7" & 8.9" General] nickytun:
I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?
[Kindle Fire HDX 7" & 8.9" General] Cl4ncy:
You can NOT unlock versions above 3.2.3.2, so you must downgrade first.

Good News is you can downgrade to 3.1.0 using the downgrade images provided by [MENTION=5749760]ggow[/MENTION]. Check page 2 here (page 1 is about 3.2.5/3.2.6 users who can NOT use these images!). Then flash TWRP, update the bootloader to 3.2.3.2, unlock the bootloader, then use ROM of your choice.

Read the info, ask if you've any questions before you brick your HDX! Note that factory reset in Safestrap means the standard wipe only (wipes data, cache & dalvik only)! Do NOT go into advanced wipe, do NOT wipe System!

Be sure to make backups of your current system (even if you don't need it anymore), remove the secondary slot(s) in Safestrap to get back the storage used by it (if you created any), and after installation of TWRP create a backup of your Fire OS before you flash any custom ROM.
[Kindle Fire HDX 7" & 8.9" General] DB126:
If running Nexus 4.0.5 the bootloader on your device is not vulnerable to signature forging and can not be unlocked.
[Kindle Fire HDX 7" & 8.9" General] yunios:
Thanks for your reply.

But how can I rollback from Nexus to the firmware 4.5.5.1?

I see here can help me rollback from 4.5.5.1 to 3.2.8, which enable me to unlock my bootloader.

I wanna flash CM13:crying:
[Kindle Fire HDX 7" & 8.9" General] DB126:
- CM13 is a non-starter on the device in question. Only KitKat based roms (currently Nexus and CM11) running under Safestrap v4.

- rolling back to 3.2.8 does not restore a vulnerable bootloader

- you can not roll back to an earlier version that has a vulnerable bootloader; device will permanently brick

- steps to restore FireOS 4.5.5.1:

>> flash a safestrap v4 compatible version of FireOS 4.5.2 from here to the STOCK slot in Safestrap v4 (overwrites Nexus 4.0.5)

>> boot to FireOS

>> download FireOS 4.5.5.1 (not 4.5.5.2 or above) from here and place in root of /sdcard ("internal storage")

>> renable OTA following directions here

>> check for updates; device should find 4.5.5.1 file and update accordingly

>> when device reinitializes do not enable WiFi to prevent immediate update to 4.5.5.2 which is not rootable at present

>> use desktop version of Kingroot to root via tether

>> reenable OTA block using instructions here (step #1 only; do not install GAaps)

>> now safe to reenable WiFi and reinstall Safestrap v4 (if desired)
[Kindle Fire HDX 7" & 8.9" General] yunios:
Thank you!

Now i know i can only have a KK rom.
[Kindle Fire HDX 7" & 8.9" General] Fallingwater:
Yes, I'm running nexus hdx (old long-discontinued jellybean version) which is pre-rooted. I can su both in adb and in the terminal emulator no problem.

Edit: not sure if it's relevant: the terminal inside safestrap already starts out as root.