Database Users

[Q] SU files installed but not giving permission via ADB

I've been trying to fix my kindle fire for a while now. My ultimate problem is that my build.prop is not in my /system/ but I have been trying to push a replacement build.prop to that directory to no avail. It looks like I have superuser installed. Superuser.apk is in system/app/ and there are a few SU directories around my file system.
My problem is that even though I have SU in my file system, I am not getting the correct permissions when accessing the KF through adb. Whenever I type in su it says permission denied. Similarly, whenever I try to change the permissions for /system/ I am denied as well. Whenever I type in su, it says "segementation fault".
It seems to me that there are three possibilities:
1. I somehow have the superuser files in place but the SU program itself is not installed.
2. SU is installed but because I can't fully boot up my KF, I can't give ADB Root access through SU because I can't pull up the "allow access" dialog box.
3. Something stupd like I"m trying the wrong commands.

Maybe your kindle auto updated and broke root? But if you've already updated and re-rooted I'm not sure what the issue would be.
Sent from my Nexus S 4G using XDA App

hmmm...I think a main thing I need to know for sure before I continue is if my phone is even rooted for sure. I have the superuser.apk in system/app. I don't have anything in data/local. I have a SU directory in a couple places. Is there any way for ADB to recognize if a phone is rooted (perhaps if the file system is set up a current way?) without having access to root priveledges itself?

Same here, BurritoRoot, I've tried this on both Linux/Mac, but either way, I can never get su to work so my Kindle can be r/w.

Maybe try
adb shell
$su
If $ changes to # you have root.
When installing su check the file permissions on the directory as well.
Sent from my Kindle Fire using Tapatalk

just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w

b63 said:
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
Click to expand...
Click to collapse
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.

Jessical said:
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Click to expand...
Click to collapse
that command only remounts the system partition r/w - not permanent !
but after issuing the comand:
you can copy files, change permission or whatever
you can also run kfu to permantly root with superuser

Fixxxxxxxxxx!
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue

taseedorf said:
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
Click to expand...
Click to collapse
It just stalls at:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'...
Then nothing.

Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory

taseedorf said:
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
Click to expand...
Click to collapse
How would I do that? I downloaded twrp-blaze-2.0.0RC0.img
I have used the terminal in the past, even compiled stuff like Chrome OS, but I don't know anything except the stuff that people put in the instructions...
Where is the boot.img itself coming from?

removed accidently some systemapps

hey guys I removed some systemapps and now I cant install the new row update. can some one please upload a titanium backup
thanks

titanium backup won't work for system apps. you will need a system dump. which apps do you need? i have a dump but i won't upload the whole dump cause its about 1 gb.

ok. thanks for the quick reply. im not sure but it sholud only be the music app. it would be great if you could upload it.

just unpack it and copy both files into the /system/app folder with i.e. rootexplorer etc.

here i uploaded nearly the whole dump:
System Dump

i am the same don't know how to do now.
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
@bananenlarry
I delete some app after root,then I unroot for some reason.
I can't not get root again,and also can not update OTA2 because missing APP.
waht can I do now?

@feskey
how did you unroot? did you delete superuser.apk from /system/app? then download Superuser from market again. because the su file from /system/xbin/ should still be there.

@bananenlarry
Unroot by following command.Su was clean up.
Instructions
1. Follow instructions to set up ADB.
2-Run "adb shell" from a command prompt.
3-In the ADB shell, type the following commands:
su
(this will cause a prompt to come up on the phone asking you to grant root permissions, accept this)
Then, back in ADB shell:
mount -o rw,remount /dev/block/system /system
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su

omg you really unrooted your device thought you just deleted the superuser.apk. i don't know exactly how the root exploit works but as i know it uses a lenovo app to do so. if you also deleted that app, root isn't possible in your case. you will have to wait until there will be another method for rooting.

[MOD] [LG P500] CRT Screen Off for Optimus One

Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!

Does it workss ???????? Reply anyone

Do you lose contacts on phone or sim?

Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..

chrisdf said:
Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!
Click to expand...
Click to collapse
You cant use this on anything but stock LG 2.3.3!
That means Cyanogenmod, AOSP, etc

kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
Flash stock v20g using KDZ then root and do what this post says right away, i assure you it works.
This is only for STOCK 2.3.3

Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
On your phone, but if you have it linked to your gmail account, when you sinc you will have them back.
you should still back up anyway, its safer that way

Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2

Are there any available screenies?

doesn't work for me..

kotobodj said:
Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
If you want it on any GB Rom, follow the tutorial i followed, check at the end of the post there's a link.

kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
i think nothing to angry for this. just read carefully before do anything :laugh:

)
cool!)

[Q]Nexus 4 system partition permission

Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks

Ikran said:
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Click to expand...
Click to collapse
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.

ksilver89 said:
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
Click to expand...
Click to collapse
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how

What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4

Ikran said:
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
Click to expand...
Click to collapse
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot

andyabc said:
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions

Ikran said:
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Click to expand...
Click to collapse
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4

occupied icinme
andyabc said:
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit

Ikran said:
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Click to expand...
Click to collapse
Then you are just booting to it (not flashed) but anyway one you get on there you have to TWRP, Advanced and then Terminal command.
Go to the system folder and type the following commands IF you have the backup:
rm build.prop
mv build.prop.bak build.prop
Sent from my Nexus 4 using Tapatalk 4

ksilver89 said:
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
Click to expand...
Click to collapse
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus

Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
Go to the bootloader, it has Fastboot from there.
EDIT: Oh you where talking about ADB, try using the method I posted on the previous page.
Sent from my Nexus 4 using Tapatalk 4

Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.

ksilver89 said:
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
Click to expand...
Click to collapse
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4

It is worth mentioning that the command "fastboot oem unlock" will actually erase all the personal data (should also include sdcard folder) and make it a blank phone! Use with cautions!

andyabc said:
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
so the phone when i turn it on, the logo from google appears and under that the unlocked lock , next, the 4 colored lines of nexus should appear . my phone doesnt gets to that, after the image of google disappears , its just a black screen , think is that bootloop you were saying.
BUT i managed to install cwm 6.0.3.5 on the phone and i am able to boot into recovery now . twrp wouldnt load for some reason, just frozen on the google logo when it was suppose to load .
so at this point i am here as you said:
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here. ( cwm 6.0.3.5 )
ROM: Not Running
in cmd i did: adb devices >result:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
00765833628b346b recovery
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found

Ikran said:
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Click to expand...
Click to collapse
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.

ksilver89 said:
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
Click to expand...
Click to collapse
thanks it worked, i had to mount the /system partition for the shell command to work, the phone booted up now, and it works, but for some reason everything is wiped from the phone i had some backup , i will see if i can restore anything from it. if not c'est la vie.
Thanks again

Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.

Rockstar600 said:
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Click to expand...
Click to collapse
Yes, maybe.

Nuu~ said:
Yes, maybe.
Click to expand...
Click to collapse
Okay,
Let me quote my problem,
I also posted it on MSkip's Toolkit thread,
I did search but wasn't able to find a proper solution,
I was on a 4.3, with latest TWRP installed,
I flashed a ROM that was 4.2.2 after I flashed the phone was not booting up, and was stuck on Google logo,
I did wipe in the TWRP and even re-installed the ROM, had the same issue again,
So, I thought to flash 4.2.2 Google Factory Image via this toolkit,
I downloaded the Factory Image from Google and placed it in the folder which says "Put factory image here"
Followed all the procedures, and flashed the 4.2.2 factory image in my phone,
Now the phone is stuck on the X logo,
I tried going into the stock recovery and did a factory reset, but again the same thing,
The phone isn't booting up,
Also one thing i noticed, while the phone is booting the "Google" logo stays around a minute, and then the X boot animation appears,
Any clue what to do??
I tried pushing the factory image via toolkit several times, but again I'm stuck at the same boot animation,
Please help me regarding this,
I'm at work, trying to search and find information as much as I can,
I can now boot on 4.2.2 but in settings the phone says that the base band is unknown, IMEI is gone,
And I cannot even see the internal storage when I connect my phone to PC.
Here is what I'm facing.
Also check this,
I got this error too, unable to post the image so posting the link http://imageshack.us/photo/my-images/9/jys1.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need any other details, please just do ask me, I will try my best to answer you properly.
Thank you.

[HOWTO] Alternate Unbricking Method

This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk

r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.

GSLEON3 said:
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
Click to expand...
Click to collapse
Thanks. I thought about adding a wipe system command, but if the download was corrupted, they'd be screwed. So I left it out.
Sent from my Nexus 7 using Tapatalk

I went ahead and added another command to the OP that may/may not help. It couldn't possibly cause any harm, though. Has anyone actually tried and confirmed this to be working?
Sent from my iPod touch using Tapatalk

When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied

dcoig1 said:
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
Click to expand...
Click to collapse
Are you sure you have root?

r3pwn said:
Are you sure you have root?
Click to expand...
Click to collapse
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"

dcoig1 said:
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
Click to expand...
Click to collapse
Hmmmm. Try pushing it to /sdcard and change the path in your echo command to reflect that.

I am guessing that somehow the /cache/kindleupdate.bin is in a secure area that we cannot push to. Is there any area that we can push to? It seems we may have to push somewhere else and then move into the secured area using adb shell with su permission like here:
http://forum.xda-developers.com/showthread.php?t=1687590&page=5
but we don't have an sdcard with our devices.
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
we actually do have an sdcard directory though... i will try to push there
---------- Post added at 10:54 PM ---------- Previous post was at 10:35 PM ----------
so i pushed the update file to the /sdcard/ directory then moved the file to the /cache/ directory, then renamed to kindleupdate.bin . Still does not help the system recovery issue. When I enter 'adb reboot recovery' it brings up a screen which says:
"Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
---------- Post added at 11:48 PM ---------- Previous post was at 10:54 PM ----------
If it makes any difference I am not bricked at the grey kindle logo but the white and orange. It just keeps refreshing the animation over and over... nothing seems to ever happen. What should I normally see when I boot to recovery? An extra option to update or something?

No. What I meant was try pushing it to /sdcard then changing the echo command to reflect that.

so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery

dcoig1 said:
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
Click to expand...
Click to collapse
Yes. Try that.
EDIT: Wait. It'll probably say permission denied or some other lame error, so add
mount -o rw,remount /data
After the cache remount then change everything that references "/sdcard/" to "/data/media/0/".

That didn't work either. I keep getting the same result. I don't get errors using the sdcard directory though either, but I also tried with data/media/0. No errors, just doesn't work for me.

so do i.
adb push "bin" to sdcard can work,but after reboot recovery,
only show on screen like this：
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------

Do not reset to factory defaults

I wanted to mention fastboot works. Read more...

I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin

Faznx92 said:
I wanted to mention fastboot works. Read more...
Click to expand...
Click to collapse
Not really. Not nearly as useful as the KFHD's. No useful commands work.
ChittyChittyGangBang said:
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Click to expand...
Click to collapse
And did this help you unbrick your device?

Unbrick my Kindle
Sorry to interrupt, but my kindle fire HDX 7" is also bricked, I can not get past the gray "Kindle Fire" screen, I can get into fastboot. My device is not detected in ADB. Is there any hope for my kindle or is it dead?

r3pwn said:
Not really. Not nearly as useful as the KFHD's. No useful commands work.
And did this help you unbrick your device?
Click to expand...
Click to collapse
Nope. Ended up wasting half a weekend on it.
I just sent it back and bought a Samsung Galaxy Tab. Now I have GPS and IR in addition to a device that works like a Droid device should.