Hi all, I am new to the forum, I have rooted my kindle fire and while I was trying to copy vending.apk into the system, I cant.
So I changed the permission of the system\apps folder to read write, then file expert crashes and the kindle hanged.
After a reboot it is stuck at the kindle fire startup screen and kept looping.
Any recommendations on what I should do to unroot it?
I don't know if you're blind, so I'll give you the benefit of the doubt with configuring your blind computer correctly to miss certain topics.
All the way on top, stickied, is a topic titled:
"[HOW TO] Unbricking/Restoring your Kindle Fire"
Follow that.
Read the thread on how to unbrick your KF, it's like 2 posts below this one.
Sent from my Kindle Fire using Tapatalk
Welcome to the forum!
However, there is a sticky post right at the top of this section (currently 2 post above yours) that offers help and tips for unbricking your KF.
Look Up ^
EDIT - Ninja'd!
Sorry for mentioning that I am kind of unsure on the first step where we need to do the zergrush, I have installed SDK during rooting. So the fastboot.exe should be placed in that folder right? Do I access through cmd prompt and which folder should I point to?
haze_1986 said:
Sorry for mentioning that I am kind of unsure on the first step where we need to do the zergrush, I have installed SDK during rooting. So the fastboot.exe should be placed in that folder right? Do I access through cmd prompt and which folder should I point to?
Click to expand...
Click to collapse
Please direct these types of questions in the unbrick thread. We'd be happy to help you there!
Also, please read some of the other posts before you ask questions in that thread. Some people have posted commands with what the correct folder to point to so just hunt for it and you'll figure it out.
Related
Ok. So I bricked my Kindle Fire. Could not access it through ADB. Nothing. So, I followed the unbricking method with fastboot. Got me access to ADB into the kindle again.
So now, one click will not root the device to allow me to put the other images onto the device. Nor will windows 7 mount it.
One click shows that no files or folders exist for the kindle and asks me if I am sure I am running 2.0 or higher.
I can adb into it, but without root I cannot copy files into the needed directories to get it back to stock, or put CM7 on it.
When I boot, i get the kindle fire words, then a black screen. It just stays black. Its better now because at least I can ADB into it, but without root I am hosed, and one click is not working.
I turn myself over to the mercy of the Kindle gods. Any help would be greatly appreciated.
added info:
To be clear. Windows recognizes it, and ADB can connect to it and I can navigate the file structure, but it will not let me root to copy things to the file system.
When I try to use the command prompt to get to e:, a window pops up and tells me there is no disk in the drive. Please insert a disk into drive \device\Harddisk1\DR52. Then the command prompt says, The device is not ready.
With all the knowledge and information going through this forum, not even a suggestion. Pretty please......
I'm no expert sadly but do you need to root to copy over a system file? If not you could push the stockrecovery.img that you can find here (http://forum.xda-developers.com/showthread.php?t=1390773), that may be why your device isnt booting.
Where do I push that to? What location on the device? I have downloaded the image, just not sure where to put it to get it going again.
just google it how to put android etc....
I would not say I am a noob. My question is this. It will not let me mount my sdcard. So when I push update.zip to the sdcard and then try to run it from the sdcard with twrp, I get an error message saying that it cannot mount /sdcard/update.zip, so can I put update.zip somewhere else, lets say in the system folder, and run the update from there?
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
lonelliott said:
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
Click to expand...
Click to collapse
When you do get 10 posts and post in the Dev forum they will just tell you that you posted in the wrong forum.
Your problem has been covered many times on here if you just browse around or search you will find it.
My problem is that the sdcard will not mount, nor will it hold information. I can copy a file to it, and as soon as I reboot, it will erase that file. I have searched for ways to format the sdcard, or format everything and partition but have found no answers yet.
Just for safe measure, I did another search just now in all the kindle fire forums for "mount sdcard" and "format sdcard" and I could find no answers.
Again, when I put a file onto the sdcard, like update.zip, as soon as I run it from twrp, or even fastboot, it tells me that it cannot mount the /sdcard/update.zip file.
On top of that, when I reboot it will not keep the file, it erases it, except the twrp folder, it stays after a reboot.
I can access the system through adb, fastboot and now twrp, but cannot get it to take an update.zip file to restore it. Even though I can access it through adb and fastboot, it does not show up in my explorer window and I cannot browse the device from either a windows 7 machine or a ubuntu 11.10 machine. When I plug it in, the machine recognizes it and charges it, but wont mount it to view files.
It also returned an error saying there is no listing for the sdcard in /etc/fstab.
Not sure what to try next. Any help would be greatly appreciated.
Then you must not have read and write privlage
Sent from my Kindle Fire using Tapatalk
I dont know if it will work but it fixed mine
download this http://forum.xda-developers.com/showthread.php?t=1348782
and flash it with fastboot
fastboot flash system path\to\system.img
and you may also have to get and flash boot.img from an amazon update
asb, I do have read write, tried and verified. It is failing to mount the sdcard. Thanks Kaw. I will give that a try with fastboot.
I have twrp as the boot image. If I reflash from an update will it remove the twrp? I think it would write over it, which, if it worked, would be ok with me. I am going to try both.
When I try to flash the system.img, it tells me the remote image is to large and exits.
I'm thinking of rooting this kindle fire but all the directions are for Windows. I rooted my EVO on ubuntu without adb. Where can I find directions for rooting with Linux?
please please please check the forums. also it would be helpful if we knew what software version you were running.
adbirdie said:
please please please check the forums. also it would be helpful if we knew what software version you were running.
Click to expand...
Click to collapse
Thanks 6.2.1
Getting ADB working is your best bet. Even if you can get it rooted without adb, it will save you a lot of headache later if something doesn't work.
Getting adb to work on Ubuntu with the Kindle Fire should just require downloading the sdk, running the SDK manager to install platform-tools, adding platform-tools to your path, editing ~/.android/adb_usb.ini to include 0x1949, and likely adding udev rules for it (you can find instructions on udev rules on quite a few forums, or read the README in /etc/udev/rules.d which might help).
Rootzwiki has instructions for rooting (not using KFU) and for installing TWRP afterwards too. Just follow the steps in jcase's thread for root and the TWRP post is stickied. I'd link, but I forgot my old account and don't have enough posts on this one to link yet.
A) Before using the Kindle Fire Utility to install TWRP, I DO need to uninstall BurritoRoot on my Kindle, correct?
B) Since I'm going to lose all my apps anyway, should I delete the ones that are not necessary for the process?
C and D) I do actually use my Fire to read PDF books, will Adobe Reader still work as it should? Where do I put the files when I transfer them from my computer to my Kindle?
I've got everything downloaded and ready to roll. I'm going to bed and plan on flashing in the morning, just need these questions answered before I do. Thanks.
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Another Question or two
il Stalk3r li said:
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I rooted with BurritoRoot, and yes, I found out that I do need to uninstall it before I use the Kindle Utility to install TWRP(v. 0.9).
Is there anything else I need to do before I do this?
Not the gapps, the PDFs I want to read in Adobe reader, where would I place those is transferring from my computer?
Sorry for all the questions I just want to be thorough and make sure I have every single thing right.
Thanks
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
You would place your PDF files on the SD card (the file system you can access from your computer when you connect via USB) either in the root or a folder such as books.
You would then install PDF reader or Kindle reader from the market in order to read the files.
Finally, install a good file manager (or if you are installing an alternate rom such as CM7 it comes with one) such as ES file explorer (free) or Root Explorer (paid). Navigate to your files and click on the one you want to open. A popup may ask you to choose your reader if you have both the above installed. Adobe will keep a list of recently opened files so you will not have to go through the file manager again for any previously accessed docs.
il Stalk3r li said:
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
Click to expand...
Click to collapse
Do I need to install the Kindle Fire Utility drivers while my Kindle is hooked up, or does it matter?
I don't think it matters.
Sent from my Kindle Fire using XDA Premium.
Previous "first try" threads are pretty old, I'm concerned that information is outdated.
First, I wouldn't have done it, but the Fire just cries out to be uncrippled. It is 6.3. I am pretty new to this. I stopped tearing into stuff about 11 years ago, I was OK with it then but I stopped caring about it and haven't paid attention since. But I know one thing, and that is how to ask for help.
I downloaded the SDK Manager and ran the installer, installing SDK Tools and SDK Platform-Tools, then tried to install the drivers from the Kindle Fire Utility; it is the most recent version, 9.5 I believe (from yesterday).
I got:
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Download successful.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
The system cannot find the path specified.
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Recovery Bootmode.
Please wait...
...And that's it, about half an hour ago. I know one thing, that when "NOT" is capitalized, you "don't touch the big, beautiful, shiny red button."
How long do I wait? What is going on, and if something is wrong, what do I do next?
Thanks for looking.
edited to add: I tried running install_drivers.bat; "UNC paths are not supported... Defaulting to Windows directory. The system cannot find the path specified."
Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547
kinfauns said:
Did you extract the contents of the Kindle Fire Utility zip archive before running anything?
Did you install the drivers?
Did you read this guide?
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.
M0sca said:
Thank you, yes I did. I read the guide several times. I did extract the contents first, before running anything.
I did manage to install the drivers manually, in between writing the first post and your response, by going through Device Manager and pointing it toward the Kindle Fire Utility folder.
I am confident that I won't permanently destroy anything, but at the same time I feel blind.
Click to expand...
Click to collapse
All of those "The system cannot find the path specified." errors are because it can't find the directories within the KFU folder. Did you move the run.bat file or something? Within the KFU directory, you should have...
drivers
files
tools
install_drivers.bat
run.bat
Like the first 5 errors after "Activating Fastboot (4002)" it's looking for the tools directory. Most of the time this is caused by users who try to run the batch file from within the zip archive.
EDIT: I'm not a Windows guru by any means, but I was just looking at some docs about UNC paths. Do you have the KFU directory on some shared directory or mapped network drive or something? Try moving it to some place local like your user directory and run it from there.
kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.
M0sca said:
kinfauns, I thank you for your patience.
Is it possible that the fact that I am running Windows in a vm on a Mac is part of the problem, that I downloaded Kindle Fire Utility (for Windows) in the Mac environment, then tried running it in the Windows environment?
I finally said screw it, and unplugged the Kindle. It is fine. I have to go to bed now, I will try doing it all from Windows (including the download) tomorrow.
Thank you again for your patience. I'm sorry that I ran out of time in the middle of requesting your assistance, that is rude and implies that I don't value the help. On the contrary, I value it very much. But the hours in between now and tomorrow morning mean nothing to the machines, and everything to my biological recharging. I apologize.
Click to expand...
Click to collapse
No, that's fine... no apologies necessary. It's good to step away from the situation for a while and regroup when things don't seem to go right. In the interest of full disclosure, Mac OS X Lion is my primary OS. All of this Windows stuff I do through Parallels Desktop VM and I don't have any problems with it. I don't know what you are using, but I'll warn you now that if you are trying to use Oracle's VirtualBox, it's not going to do the job for you. There seems to be some bug in their USB implementation that breaks adb and fastboot.
My guess right now is that you are trying to run KFU from a shared directory that resides on your Mac. If you look at post #2 of the guide I mentioned previously, I suggest putting everything in C:\kfu before running things. It doesn't necessarily have to be that directory, but you should trying putting it somewhere on the boot drive. The 2 minutes I spent looking at UNC paths seems to indicate cmd.exe doesn't like them and that might be the cause of your troubles. Good luck.
kinfauns, I followed the instructions better this time, downloading KFU in the Windows environment and extracting directly to C:, and everything proceeded perfectly. Thank you!
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
This may look complicated, but is super easy. If you don't feel comfortable using this method, you can use this automated tool (yes, it works on 4.5.141). It won't be as satisfying, or even feel good. You won't learn anything, but you will be rooted. Download tool here (link in OP is broken).
Pre-work:
1) Read the xda Atrix Beginners Guide (then read it again)! (Link)
2) Download and install 7zip. (Link)
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. (Link)
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
You can simply copy each command and paste in to the command prompt.
If you encounter any errors after entering a command, just ignore and keep going (assuming you entered the command properly).
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down until you see "fastboot".
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
17) Open a terminal emulator, then type "su" and hit enter. You should see "#" if you are rooted. Or, download Root Checker from the Play Store.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Note: If you experience problems with updating superuser after rooting, try going in to Manage Applications and clear Superuser data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Downloads:
My Atrix AFH Folder
*****
Thanksssss
Just want to show my appreciation. Your guide followed step by step worked flawlessly on my atrix. Ive been trying to root this darn thing for about a week and a half with no luck. found your guide and worked perfect first time around. Thanks..
David
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
upndwn4par said:
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
Remember to click THANKS if this guide helped you!
Pre-work:
1) Read the xda Atrix Noob Guide (then read it again)! Link
2) Download and install 7zip. Link
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. Link.
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down.
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Click to expand...
Click to collapse
RE super user pkg.
aksma said:
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
Click to expand...
Click to collapse
Well for me what happen is down at the bottom he has two links for two of the files you need to zip. in one of those, there is a superuser file. When doing the cmd commands at the end you will end up installing the superuser. The best thing to do which really helped me was to download the command prompt text file, that way you can mimic exactly what you see. Hope this helps.
-David
Thanks David, I just started doing the same. Lets see how it goes.
good luck
aksma said:
Thanks David, I just started doing the same. Lets see how it goes.
Click to expand...
Click to collapse
no problem. Believe me i was in the same position. I must of tried rooting mine like 15 times to no avail ,then i found this thread and it worked.
Worked like a Champ!! Thanks David... Was quick and easy.. ..
excellent
aksma said:
Worked like a Champ!! Thanks David... Was quick and easy.. ..
Click to expand...
Click to collapse
Good deal. So glad i found this thread haha.
Glad I could help!
good one.
Thanks a lot
was so expected that this guide
Going to give it a try
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Thanks!
Rooted phone
dmacdog said:
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Click to expand...
Click to collapse
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
thanks
that was cool!
very usefull!! thank you!
very useful
Sent from my MB860 using xda premium
condor7272 said:
that was cool!
Click to expand...
Click to collapse
Yes it is. Awesome feeling to look in your app drawer and see this:
THANKS!!
upndwn4par said:
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
Click to expand...
Click to collapse
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
1iJakk said:
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
Click to expand...
Click to collapse
Don't unlock your bootloader if you think you will want official Moto ICS update (major hard brick risk).