[Q] Can't unlock the unlockscreen - 7" Kindle Fire HD Q&A, Help & Troubleshooting

i tried to install swype custom keyboard and it was a fail and when i rebooted as required after install i can't type in my password to unlock the screen because it says swype has stopped and i could just remove the app but i can't unlock my screen because i can't type in my password i tried ADB to remove the the app but that didn't work because it is a system app and it keeps on saying i don't have permission when i try the remove command and i tried to run the root command and su command on adb so i could remove it but it didn't work even though my kindle is rooted so now what do i do that is a alternative to a factory reset ( last choice )

You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
it didn't work it said not permitted can you give me some ideas of what i might have done wrong

darth45013 said:
it didn't work it said not permitted can you give me some ideas of what i might have done wrong
Click to expand...
Click to collapse
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"

stunts513 said:
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"
Click to expand...
Click to collapse
sends back error device not found

darth45013 said:
sends back error device not found
Click to expand...
Click to collapse
hows that possible, you were already able to access a adb shell before this.

stunts513 said:
hows that possible, you were already able to access a adb shell before this.
Click to expand...
Click to collapse
its the only command that does it to

Then don't run it that way, try it this way:
Code:
adb shell
su
reboot bootloader
I just combined them for convenience last time so try running it like that.
Sent from my Amazon Kindle Fire HD using Tapatalk

h i will have to re try tomorrow also is their a way to open the default keyboard or set it to default via adb

Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk

i have found the adb command for changeing defaults but i don't know how to use it for kindle fire hd

stunts513 said:
Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Does anyone know the adb shell commands to change the default keyboard could really use them or I will have to do a factory reset

How do I do a factory reset on my kindle? I'm having the same issue with keyboard not comin up on lockscreen
Sent from my SPH-D710 using Tapatalk

Related

Root instructions...

Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools

Unroot Droid 3 without computer?

Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!
ajgates92 said:
Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!
Click to expand...
Click to collapse
Open market and grab "terminal emulator", once you have it open it up and follow the steps as root (first thing you type into the terminal emulator is "su")
1./ remount /system to rw "busybox mount -o remount,rw /system
2./ erase root files "rm /system/xbin/su" "rm /system/bin/su" "rm /system/app/Superuser.apk" "rm /system/xbin/busybox"
3./ remount system ro and reboot "busybox mount -o remount,ro /system" "reboot"
these paths are for root w/zergs but they might be the same for Petes etc. This will clear all files and symlinks that were created when you rooted your device.
I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!
Droid 3 stock cables suck f(2 d3s and both cables died).. be sure to also check with no stovk cable...
Enviado desde mi DROID3 usando Tapatalk
ajgates92 said:
I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!
Click to expand...
Click to collapse
No worries, I'm glad you got it working. You're not an idiot, I'm a cryptic poster
So terminal app comes with superuser and busybox?
poetryrocksalot said:
So terminal app comes with superuser and busybox?
Click to expand...
Click to collapse
No, terminal app usually comes on custom roms but stock rooted users will have to download it for free off the market.

[Q] bootloop on fire hd7

Hello,
I have been trying to install whatsapp on my kindle fire hd and followed a guide that said to use the allwinner mod apk.
I did install the allwinner mod, selected samsuns s9000 and tried to install whatsapp
It failed, so i rebooted the kindle.
Now I am stuck at bootloop.
I see the kindlefire boot going but the system never boots.
I tried with kindle first aide to re-flash the original firmware, but failed since it seems unable to connect.
I tried to connect from command line but I cant get the fastboot command to go, tried with the original cable and with another one that I have got and that has always worked.
Im now out of ideas.
Since the kindle is rooted I dont think i can send to amazon, any idea?
Thanks
You need to get a fastboot cable to get your kindle into fastboot mode in order to flash it. They are pretty cheap.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to get a fastboot cable to get your kindle into fastboot mode in order to flash it. They are pretty cheap.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hello and thanks
I noticed that it responds to adb with a normal cable,
since i know that the allwinner mod changes the build.prop I was wondering if there is a way to restore the original one via abd.
Is there someone that has a build.prop to send me (kindle fire hd 7)
In the meanwhile I put on order the fastboot cable...
Thanks
A lot of build.prop can be found at persano's thread http://forum.xda-developers.com/showthread.php?t=2116243
But make sure to pick the right one.
Unfortunately I don't know If you can resp. how to put it in the right place to make it work.
Mistaz said:
A lot of build.prop can be found at persano's thread http://forum.xda-developers.com/showthread.php?t=2116243
But make sure to pick the right one.
Unfortunately I don't know If you can resp. how to put it in the right place to make it work.
Click to expand...
Click to collapse
Hello
many thanks I managed to get it out of the bootloop.
the procedure is:
download the build.prop and save to the computer /home (i use linux) then open a terminal and connect the usb cable to kindle
Code:
adb shell
su
mount -o remount,rw /system
exit
exit
adb push ./build.prop /sdcard/build.prop
adb shell
su
cp /system/build.prop /sdcard/build.prop.old
cp /sdcard/build.prop /system/build.prop
exit
exit
adb reboot
and that's it.
How was adb working during a boot loop? That's bizarre.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[ROOT][10-29-13]How to Manually Root the Nvidia Shield

Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.
Does anyone if the root stop you from updating the device like GS4?
Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.
Finally success root my shield
oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?
Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.

[Q] did I brick my kindle? :(

I have a rooted kfhd and I accidently removed SystemUI.apk. I can power on the kindle and it will take me to lock screen...after i unlock i get black screen. I tryed to push SystemUI.apk back with adb but it failes. "failed to copy 'SystemUI.apk' to 'system/app/SystemUI.apk' : Read only file system".
Can i unbrick my kindle without factory cable?
And if so can someone tell me how
Thank you
muska.ovidiu said:
I have a rooted kfhd and I accidently removed SystemUI.apk. I can power on the kindle and it will take me to lock screen...after i unlock i get black screen. I tryed to push SystemUI.apk back with adb but it failes. "failed to copy 'SystemUI.apk' to 'system/app/SystemUI.apk' : Read only file system".
Can i unbrick my kindle without factory cable?
And if so can someone tell me how
Thank you
Click to expand...
Click to collapse
Yes, you need a fastboot cord now to flash the original firmware. You can get one on Ebay or buy a tip here http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make your own with instructions located here http://forum.xda-developers.com/showthread.php?t=2207122
Use this tool http://forum.xda-developers.com/showthread.php?t=1951254
Now you want to do is make sure to download SDK so you can use ADB and fastboot commands. Here is a video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw
Should the drivers be a little outdated, Stunts has some good ones here that have helped many http://forum.xda-developers.com/showthread.php?t=2477379
Good Luck
Actually if you don't mind putting some time in you could fix without reflashing it, you need to mount /system as read/write and push systemui.apk to the sdcard, the cp it to /system/app, then chmod its permissions and it would fix the problem.
^^ his method is way easier though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Actually if you don't mind putting some time in you could fix without reflashing it, you need to mount /system as read/write and push systemui.apk to the sdcard, the cp it to /system/app, then chmod its permissions and it would fix the problem.
^^ his method is way easier though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
can you put the lists of comands pls...i cant get a factory cablle...
how do i mount system as a read/write?
how do i copy it from sdcard to system/app
and how do i chmod it.
As long as you already had adb enabled you don't need a fastboot cable, just run
Code:
su -c "reboot bootloader"
and it should go into fastboot where you can reflash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Categories

Resources