Database Users

problems installing anything

I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.

if yr installing through and use
Make sure phone is synced
Make sure app is in tool file I'd adk file
Make sure when at command prompt Ur in adk/tools file first
Adb remount
Adb push (app.apk) /system/(app/framework)

ok I figured out my problem but fixing it is going to be quite confusing. Looks like I would have to know a lot more than I do to fix it. Basically the adb is not reading the phone as root (or something like that). And the ro.secure is set to 1 which it should be set to 0 to be considerd root. So therefore I have to reinstall a bootimg. Ive been reading it on another forum page but i cant post it cause my account hasn't been verified yet. but it's this forum and here is the thread showthread.php?t=443041&page=2
but it's like french to me!!! If anyone can dumb this down for me I would really appreciate it lol thanks a lot you guys have been so much help in the little amount of time ive been a member to this forum. Thank you

redlinethecar said:
I try to install apk packages like godzson dialer and clear_keyboard and i get errors.
I used apps installer and android dev
apps installer tells me It cannot install the app
android dev I run
adb install C:\clear_keyboard\system\app\HTC_IME.apk
I get
failure [install_parse_failed_unexpected_exception]
I searched for hours finding solutions that say i need to push the files to /system/apps and doing that there is permissions involved and I cant seem to touch anything in /system.
When I run chmod 777 /system i get an error saying unable to change read only file system.
I thought all of this was going to be simple tasks but it's getting really annoying any help would be greatly appreciated. Thanks for everything.
Click to expand...
Click to collapse
First, put your apk's in your "C:\AndroidSDK\Tools\" Folder
Second open the cmd window and do "cd C:\AndroidSDK\Tools\"
Third do "adb remount"
Fourth "adb push xxxx.apk /system/app/"
that will install them

When remounting I get error
Code:
remount failed: Operation not permitted
but I continue anyway and the
Code:
adb push HTC_IME.apk /system/app
sends the file with no problem but it doesn't install it though.

Here are steps to do if it is not already installed on your phone. However, if it is you can not install when it is already there. I'm not sure how to remove in terminal and everything I've tried it tells me read only blah, blah, blah...
I tried mount -o remount,rw /system---that is suppose to work.
1.Make sure anything you want installed is in
the root of the sdcard..(/sdcard/nameoffile.apk)
2. Download a terminal emulator from the market.
If it installs continue..If not then continue on back to the thread.
3. Open up the terminal emulator. It should ask permission from SU. >Always allow
4. Now type the following
su (hit enter)
install /sdcard/name_of_file.apk /system/app/name_of_file.apk----if it is a system app
If it is a downloaded app then use /data/app

Ok.... well I tried that way also and I get the error
Code:
install: not found
I downloaded the terminal app from the market and entered the commands as you said for ex.
Code:
install /sdcard/HTC_IME.apk /system/app/HTC_IME.apk
Thanks a lot though I wish it could have been that easy.

Guide to install LXDE on samsung galaxy s

So 3 days of trying to install ubuntu on chroot and a little knowledge of linux and terminal, i was rather surprised to log into it and there i was, faced with an LXDE interface.
I want to thank coralic, burningbroccoli, lifehacker, josh_axeY and backfireNL for supplying the information i needed to make this possible.
So a brief overview of whats going to be done. First we will need to root our galaxy s in order to access terminal. An ubuntu image will be created and used in chroot environment by mounting (loading) it. Finally a vnc server will be setup and will be logged in using androidVNC.
So for the guide i suppose!
Guide:
First your going to need to root your phone. This is to access terminal and enter the commands required. This is taken from backfireNl's easy way to root your phone.
1. Download: 2.1 Update .zip
2. Put update.zip to root of /sdcard (not /sdcard/sd) (not on the physical SD card but the Internal SD card/Phone Memory)
3. Turn off phone
4. Hold down volume up + home button + power (tip: release the power button for half a second when you see the samsung logo)
5. Phone will reboot into recovery mode
6. Wait until you see the Recovery Screen and then release the buttons
7. With the volume down key go to the option: "apply: /sdcard/update.zip"
8. Press the home button
9. Phone will start updating
10. Phone reboots... and there you go! your phone is rooted!
So that wasnt too hard was it? Although once you have done this, you will need to download a couple of programs from the market. Goto market and download the following programs:
-Busybox
-Terminal Emulator
-androidVNC
Ensure all of these are installed as this is what you shall need in order to successfully run LXDE on your phone.
Next is the image for the install! i will post up an image file for download although for the sake of people wanting the whole info on how-to here it is.
1) login on your ubuntu machine and fire up terminal.
2) login as the super user by entering "sudo su"
3) you will be required to enter your su password, enter this and you will be logged in as root
4) In terminal enter "apt-get install rootstock"
5) One this package is all installed, enter the following code into the computer terminal:
sudo rootstock -f localhost --login ubuntu --password ubuntu --imagesize 1G --notarball --dist lucid --seed ssh,tightvncserver,lxde,expect
6)The image will be stored in the home folder. The image will need to be a .img file or it wont work. So extract the file if necessesary and rename the file so it reads "ubuntu.img"
7)Now you will need to put the ubuntu.img on the phone. The directory which it needs to be installed into is "/sdcard/ubuntu/"
8) All done for this step!
Ok so you have everything setup and ready to do the fun part! so lets get everything mounted and configured!
1)Open up terminal emulator on your phone
2)enter "su". this logs you in as superuser
3)I found you will need to make the following directories in order to work, so in terminal emulator enter:
mkdir /data/local/mnt
mkdir /data/local/mnt/proc
mkdir /data/local/mnt/dev
mkdir /data/local/mnt/dev/pts
4)enter "cd sdcard" then "cd ubuntu"
5)You will then be in the folder with the image. Type into terminal:
export HOME=/root
export USER=root
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
busybox mount -t ext3 ubuntu.img /data/local/mnt
busybox mount -t proc proc /data/local/mnt/proc
busybox mount -t devpts devpts /data/local/mnt/dev/pts
busybox chroot /data/local/mnt /bin/bash
/etc/init.d/ssh start
6) Although it doesnt seem it, your now into your distro!
Okay so your into your distro but it looks all horrid and "text based". wouldnt it be lovely to see a proper desktop? so lets go!
1) enter into terminal "apt-get install x11vnc" this installs x11vnc to your phone. This may take a while depending on how your connected to the net
2) once x11vnc is installed, type "x11vnc -storepasswd" and enter a password. It will ask to verify the password so enter it again, then enter "y" to setup a password for it
3) first enter "vncserver" to initiate the server on your distro. For some reason without this, androidVNC will start to connect then crash
4)finally enter "x11vnc -usepw -find"
now your x11vnc is setup using a password hooray! last step in this guide and you will be away in no time! So is everyone ready?
1)hit the button on the bottom to return to the desktop but keep terminal emulator running
2)goto androidVNC and enter the following:
Nickname: root
Password: (whatever password you setup in x11vnc)
address: localhost
Port: 5900
color format can be anything, i set it to 4 bpp and use local mouse pointer
3)Simply click "connect" and viola! welcome to your impressive lxde environment!
This has been done before although i tried to do every step, base it around the phone as much as possible so no connecting to the computer.
any questions or problems i will try my best to help you guys, and thanks for the guys who helped me on this voyage.
i will write a bash script soon to try and incorporate as much of the manual typing in as possible
good luck!
Things which need to be done:
Upload image: Completed! - http://www.megaupload.com/?d=H55O5UEM
Bash script for terminal emulator: Completed, needs to be uploaded
Bash script for setup process of terminal emulator: Not completed
Startup script for image: Not completed
Youtube video: Not completed
Include internet browser and x11vnc in image file: Not completed
If anyone has any recommendations on how to make the process easier please let me know and i will try my best

Good to see the info consolidated into one post!
Cheers for the shoutout.

no probs your information helped me soo much, i just thought it would be good for someone to goto a post and go "oh yeah thats how to do it" instead of going to loadsa websites

i will try it very soon, thank you.

awesome!
When will you post your img file? I'll have a try.
I have no ubuntu installed, I'm using ArchLinux.

okay ive written a bash script to automate most of the process although there are a few things i could tweak before im fully happy
i have also posted a youtube video to demonstrate how easy it is! the first post will be updated with the link.
people ask me the reason for doing this and i have 2 replies:
1)to show the true potential of this phone (and working in a phone shop it really works)
2)for development purposes. Things like this are the next step in unlocking the true potential of the phone
lijgame: Im just uploading it now for you

Good work, will give it a try. And what about any browser ? Like firefox ?

hi.
okay so this is installing ubuntu into a chrooted environment and vnc'ing to it.
does anyone know if it is possible to blow away android and install pure debian on it? does anyone know of a hardware list on the sbc in this thing and what sort of support one might need to hack in to get a such a thing to work?

I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
In terms of installing a clean debian would need more than just a straightforward port. You would be looking at making an environment which supports the arm architecture, porting all of the drivers over, creating an option to support telephony, messages and gps too. If you wanted a debian environment it would probably be best to either run it like how the n900 does or getting a distro of it which is specifically made towards mobiles and modifying it.
Although you have an extremely good point there! Tell you what, once ive got everything running on here i will have a look and see what i can do in terms of atleast getting a debian shell running or a limo version

.kiz said:
I will apologise now for the delay in image upload, the image file is 1gb and im having trouble finding a place to upload it.
Click to expand...
Click to collapse
Just create zip/tar-ball of img file and it will become around 300MB. Then you can upload it on multiupload (or megaupload/rapidshare/mediafire).
I just created that image too and will be testing on my Galaxy S soon, so if its working for me then I will upload my image too.
Thanks for your good work

haha i shouldve really thought about compressing the file really
this will be a pre-image im just working on getting a better image with optimization, x11vnc and firefox

okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started

Tnx for the credit!

Ubuntu image is uploaded and ready to go, im currently working on a better image so when ive finished that, it shall be released.
Also i have recently installed an internet browser and it is functioning properly. I will post screenshots soon

.kiz said:
okay guys the first post is edited with the image for the install.
http://www.megaupload.com/?d=H55O5UEM
I am currently in the process of playing about with images to include everything you need, so soon enough i will have an image with everything you need to get started
Click to expand...
Click to collapse
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists

Try creating a second loop device with: mknod /dev/loop2 b 7 0

fslateef said:
The image is only 11MB and is corrupted
Moreover, I tried to mount my ubuntu.img to /data/local/mnt but it is giving error (sort of -> loop back device can't be mounted: No such file or directory) although I created and checked /data/local/mnt directory which exists
Click to expand...
Click to collapse
im guessing because the image is corrupt, your unable to mount it.
I have just uploaded my bash script making it easier to mount each time.
bash script: http://www.megaupload.com/?d=CEU6R5J4
Image file: http://www.megaupload.com/?d=H55O5UEM
ensure you have made the directories explained in my first post.
pop the hsetup.sh file inside /sdcard/ubuntu (along with your image)
then fire up terminal emulator and type:
su
cd sdcard
cd ubuntu
sh hsetup.sh
This mounts everything for you and logs you into LXDE, all you need to do after is type in:
/etc/init.d/ssh start
vncserver
x11vnc -find
Then log in using androidVNC
i will attempt to upload the file to another location and i will test the image file to ensure its not a compression error

i apologise, ive just looked at the zip file and it is corrupt.
just compressing a new one and i will upload it

.kiz said:
im guessing because the image is corrupt, your unable to mount it.
Click to expand...
Click to collapse
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....

fslateef said:
Nops, I am using my own created ubuntu.img file according to your command which is 1GB in size .....
Click to expand...
Click to collapse
I found the problem. As mentioned by ArminC, I found that there isn't any loop device node in my mobile hence I created one and its mounted
Great ... Now going ahead .....

G2 Rooting Problem

Hey all,
I would like to know, what I might have done wrong in the rooting process. I used
This Tutorial hxxp://g2hacks.com/g2-hacks/how-to-root-g2-phone/
I made it to step #18 and was stopped by this error:
Code:
/data/local/tmp/root: data/local/tmp/busybox: not found
/data/local/tmp/root: data/local/tmp/busybox: not found
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Ideas?
Thanks,
Danny

Here is a screenshot of what I pushed to the phone:
hxxp://i.imgur.com/No1id.jpg

You have a typo in your push command for busybox (you renamed it to root instead, which then got overwritten when you pushed root). Just push busybox again.

How do I back out and enter that push command again?
What would I type?
I'm a total novice.

On your comp, just type the command again:
Code:
adb push G2TempRoot/busybox /data/local/tmp/busybox
Then on your phone, in Terminal, just run the root command again:
Code:
/data/local/tmp/root
It should complete this time.

I made a mess. Check it:
hxxp://i.imgur.com/y3NRW.jpg

You are still in the adb shell (basically creates a terminal on your phone that you can interact with on your computer).
Type "exit" to leave the shell. This will return you to the regular command prompt (instead of the $). Then try the push command again.

So now the phone terminal gives me this:
Code:
/data/local/tmp/busybox: permission denied

Oh sorry, forgot you needed to set permissions on the file. Run this command again from your computer:
Code:
adb shell chmod 0755 /data/local/tmp/*
Then it should all work fine.

The errors are getting shorter
Now I get this:
Code:
mkdir failed for /system/xbin, File exists

This error doesn't matter (it's really more of a warning in this case) and is actually expected.
You should actually be rooted if you didn't see anything else.

AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?

Danny.B said:
AND I'M ROOTED... THANK YOU!
I'm new to Android from iOS. Any ROMS you would recommend?
Click to expand...
Click to collapse
Congrats! And there are a few threads about this that you can read through (just search for them). If you like HTC Sense (the interface HTC adds to a lot of their phones---basically lots nice visuals and extra polish to things), you can try Virtuous. If you like the stock look that the G2 comes with, there is a stock DEODEX rom out there. By de-odexing the rom, you can do things like customize the framework (e.g., customize the status bar icons/colors or add a battery percentage to it). Lots of people here (myself included), use CyanogenMod. It's close to stock but with lots of tweaks/extras (it's based on the Android Open Source Project or AOSP). It's also nice because it has frequent updates and constant development (they recently started pushing test builds that are based on Gingerbread---the new Android update only available on Nexus S).
Now that you are rooted though, it's easy enough to install Rom Manager and test them all out. Be sure to create a backup first as well.

ROM Manager installed. I'm backed up.
Thanks again for your help.

i cant flash the engineering hboot keep getting error md5sum : not found Verification of hboot-eng.img failed i re-download the files, re-extracted them to my SD card, and ran the flash_hboot script 3x still nothing plz help but im rooted and backed up

Did not want to create a new thread so I'm posting it here.
First off, I haven't tried rooting any of my phones previously so I'm obviously making a mistake somewhere.Hope someone here can help me out.
I installed visionary+ r14 but it just blacked out the screen with a heading.I've read elsewhere that it has all to do with the new firmware updates.My update for the DZ seems to be country a specific one and came out a couple of weeks back.
Anyway,
I tried this visionary method a few times but the phone just hung and I had to go to the homescreen and uninstall Visionary and reboot to get the phone to run smoothly again.
Then I read another way of rooting the thing and it took me here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
After a couple of tries I was able to push the files to the DZ but got stuck at this command:
adb shell chmod 0755 /data/local/tmp/*
The error it gives me is:
Unable to chmod /data/local/tmp/sqlite3: operation not permitted
Strange thing is, yesterday at the same point it gave me the same error but it was 'busybox' instead of sqlite3 and right before that it was something else.Which should mean that those earlier commands were run successfully by the terminal.
P.S. Debugging mode is on.Visionary is uninstalled. followed all the steps mentioned in the guide.

Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.

mohitanfield said:
Okay.So I format the phone memory and I'm now able to move a few steps ahead.
But as soon as it seems that everything is going well, the terminal emulator refuses to open at this step:
"Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell "
waited a while and there is only a blank screen showing up.
Click to expand...
Click to collapse
It looks like you are trying to root a DZ with a firmeware version >= 1.72.
If yes to have to downgrade it to 1.34 first.
See either the instructions here: http://forum.xda-developers.com/showthread.php?t=905261 or the more comprehensive at http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
But if your CID is other then the ones stated in the the first thread you need a goldcard to downgrade first, which is also described in the first thread.
have fun - Guhl

Thanks a lot for your reply and as is the case, my phones CID is HTC_38 which does not seem to be downgradable without a gold card.
I read the procedure and although its well explained, it will take a bit of time.
Will try it sometime soon hopefully, although I wish someone would just make a simple rooting app for the newer versions!

It took us month without sleep to create the existing rooting tools. So I do not see any simple rooting tools on the horizon

[Q] Honeycomb Keyboard

I'm kinda new to android
I've started to delete useless apps through Titanium Backup(acer staff,games etc) , and exidently deleted smth connected with honeycomb stock keyboard.
Now every time when i want to use stock keyboard, pops up a messege "The application Android keyboard (process com.google.android.inputmethod.latin) has stopped unexpectedly. plz try again".
Ive tryied to reset factory data but it wont helped. Is thera any solution for this problem? if there no, plz tell how to completely reset tablet) ive read "system Images " thread but i didn understand some things
here is my recover steps: (for a500 which is bricked)
for a500 is normal:
root it
put the system.img into a500
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
then reboot
Click to expand...
Click to collapse
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
what that means)

You might very well have ruined your tablet.
I'm not a developer or coder so I can't make any sense of the code you posted but if a reset didn't fix it then you've certainly deleted something important. Hopefully someone has some ideas.
If not, then maybe you can return it? And next time, don't delete something unless you know what it is you're deleting.

ok ive recovered from image, but now wifi is not working , what should i do?

There are posts about having to change file permissions to fix wifi. Search this forum, there are a few.
edit - linked post
http://forum.xda-developers.com/showthread.php?t=1074449&highlight=wifi+permission

yeah ive read this but i dont know how to move that files to system folder on devide, wifi is down , so i cant download any file managing apps from market and theres no any file managers on stock Rom

If you've got the adb working, you can use the command mv to move the file.
I'm not sure of the exact path involved, but for example. the file is in /mnt/sdcard/filetobemoved and needs to go into /sytem/lib/modules
mv /mnt/sdcard/filetobemoved /system/lib/modules
That'd put it in the location you need. To change the permissions, you'd use the command chmod
chmod 655 /system/lib/modules/filetobemoved
The 655 is an octal(0-7) representation of the file's permissions. I'm not sure what permissions it needs, but you could try 655 as a start unless someone else knows for sure.
if you want, hit me up on msn, I can try to walk you through it: [email protected]

Glebaka said:
ok ive recovered from image, but now wifi is not working , what should i do?
Click to expand...
Click to collapse
Ah *phew* Good to hear.

gammaRascal said:
Ah *phew* Good to hear.
Click to expand...
Click to collapse
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?

muqali said:
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
Click to expand...
Click to collapse
No clue. I really should start reading up on HC app development and at least familiarize myself with that environment.
I haven't rooted yet cause I'm e'scarded to.

ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules it says i dont have permission to do this.
tryed in connectbot type "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted what if

Glebaka said:
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules i dont have permission to do this.
tried connectbot tryied "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted
Click to expand...
Click to collapse
type mount and paste/retype the line that has /system in it. It might be mounted read only.
or try the cp command in place of mv
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path

ah im total noob tried cp instead of mv it said permission denied .
t
ype mount and paste/retype the line that has /system in it. It might be mounted read only.
Click to expand...
Click to collapse
i didnt get that (
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
Click to expand...
Click to collapse
yeah thats i know)

Are you logged into the tablet using adb's shell? I've only used that once on a different tablet, but iirc the commands are standard Unix/Linux commands. Someone correct me if I'm wrong but aren't you already logged in as superuser like this? You don't need to 'sudo' or 'su' to switch over do you?
I'm not familiar enough with this specific environment to figure out what might be keeping you from placing those files in that location. The command to check the partitions mount options is
mount
It should return a bunch of text, one line of which is gonna be the /system partition. If it's ro(read only) then you can't write to it and would need to remount it.

yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)

My knowledge of adb is limited as well. All I know is that I can connect to it, type: adb devices (in the command prompt) to make sure it sees my tab then 'adb push filename.extension /directory/structure' to force files... Conversly, I think adb pull filename.extension /directory/structure will grab files on the tab if you know what they are called and where they are located.

Glebaka said:
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
Click to expand...
Click to collapse
what was the /dev/block/mtdblock for /system?
there is a number after it...for example /dev/block/mtdblock1
mount -o rw,remount -t ext4 /dev/block/mtdblock1 /system
would remount it read/write, provided that it is mtdblock1, change the number depending on what your device has.

yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager

Glebaka said:
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Click to expand...
Click to collapse
If cp won't put it there either, I'm out of ideas. Maybe ask in the other thread how they were able to copy/move the file and set the permissions?

I know it may not be really classy, but how about downloading an .apk That will let you mount the drive, to an sd card in a computer then transfer that to the Acer. (If it's an extreme case and nothing else will work..not condoning piracy, but don't know what would work...)
or is it possible to copy the system data from a Titanium backup and send it over so he can restore the missing files?

This following step I can't be responsible for it's safety. It looks safe to my eyes, but proceed having been forewarned. I did some research and you might be able to use dd to get the file there.
dd if=/mnt/sdcard/filname of=/system/lib/modules/filename

[FIX] HDX 8.9 Bootloop Brick Recovery Steps...

I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.S

Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.

Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)

Poesini said:
Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)
Click to expand...
Click to collapse
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW. Once that is done, make sure the permissions are set to 0644, or rw-r--r-- & check the ownership to make certain the owner & group are both set to "Root". If you do not work on the "live" build.prop, then copy the edited build.prop to the root folder (/) first, then check permissions or change them using adb chown & chmod commands as required.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.

chratcliff said:
Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.
Click to expand...
Click to collapse
Glad to get you pointed in the right direction. This is what XDA used to be. How I learned anything at all. I am a mechanical engineer, not a software or hardware guy. Just a guy that will not give up on something broken.
It's all about taking little queues from here & there & then trying to assemble parts of different things into accomplishing what it is you are working on. All of this was based on things I tried or read in the past, working to root devices like the Xoom, etc... After reading about the exploit we had applied (what it is & how it works, some of which was beyond me), I was able to surmise that the exploit we used was still there as was the ability to access root permission, but that the tablet had "forgotten" we had root access rights because of the wipe. We just had to use adb to give it the files "memory" of our access to root & the permission to use them, in essence, tell it what we wanted. Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done. We need to provide that for it's brilliance to become useful.
As mentioned above, I highly recommend modding the build.prop & re-flashing the update.bin to have a clean slate.

GSLEON3 said:
Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done.
Click to expand...
Click to collapse
This is the damned truth never better spoken lol
Sent from my SPH-L900 using xda app-developers app

GSLEON3 said:
Ahhhhh.... XDA! The thrill of it all, you desperately want something now, you're a smart guy, you can do it & nothing beats that feeling of your sphincter tightening up, your heart racing, as you wait for that device to reboot....wait.....maybe another minute.....okay....crap... what do I do now? I love that feeling! I mean YOLO. Livin' dangerous dog, lol... Okay, I "bricked my device on PURPOSE, since there is a Play Store script in a ceertain tool that seems to be broken, or is missing information from the instructions, such as safestrap, or something.... That part I haven't figured out. I asked the creator to take a look at what he did & in the mean time, this should get you fixed up. It is actually much easier is you were not panicked to the point of factory resetting, but either way, the info below will get you sorted out.
I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.
Click to expand...
Click to collapse
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?

TOM XIE said:
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?
Click to expand...
Click to collapse
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?

GSLEON3 said:
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?
Click to expand...
Click to collapse
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.

Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....

TOM XIE said:
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.
Click to expand...
Click to collapse
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.

scx110a said:
Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....
Click to expand...
Click to collapse
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.

GSLEON3 said:
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.
Click to expand...
Click to collapse
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.

TOM XIE said:
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.
Click to expand...
Click to collapse
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.

GSLEON3 said:
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.
Click to expand...
Click to collapse
Hope you good luck.... That's really a complex thing since Amazon did so many changes to the DownloadProvider....

May ask you a question? plz
GSLEON3 said:
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.
Click to expand...
Click to collapse
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english

cjdfyd2 said:
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english
Click to expand...
Click to collapse
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.

GSLEON3 said:
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
(still can't post links)
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.
Click to expand...
Click to collapse
Tried using this method after the installation of gapps failed due to system directory being full (1gb)... I already gave up on this device until I saw this... Many Thanks! :highfive:

Thanks your answer and happy new year, i was wonder if could you help me?
GSLEON3 said:
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.
Click to expand...
Click to collapse
my device is kindle 7", i had followed step Cpasjuste's http://forum.xda-developers.com/showthread.php?t=2577826 and i delete these files
"/system/app/amazonmp3_4010410.apk" -> amazon mp3 ..
"/system/app/Email_310006810.apk" -> email app, replaced by gmail which is currently broken !
"/system/app/Photos_7016610.apk" -> photos app
"/system/app/OfficeSuiteViewer.apk" -> office ..
"/system/app/S2Service.apk" -> something to do with cellular i think
"/system/app/Launcher-release-signed_81224610.apk" -> amazon launcher
"/system/app/AmazonWebViewLib_1109110.apk" -> slik browser
"/system/app/com.amazon.cloud9-platform_38038110.apk" -> amazon cloud/sync
and flashing he's gapps file. and then my device is bricked. it's shown grey kindle fire logo only, so i reboot many times but still shown kindle fire logo only.
So i install ubuntu my laptop, and follow your step jcase's file download on my computer.
but i don't know how next step? how open "su" file? by sdk? work on window os? or linux os? sorry for many question plz help me..and happy new year

Hello,
My kindle is bootlooping on the grey kindle and orange fire logo. This is a HDX 7.
I rooted, went a bit crazy with uninstalling kindle bloatware, screen went black, thought factory reset would do the trick, end up in bootloop.
My computer recognizes the kindle so what should I do?