Related
Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.
sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.
I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire
Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!
terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.
would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility
Got twrp on it last night successfully and flashed CM7.
My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!
look at my post on page 1 of this thread !
@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.
... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.
Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!
glad to hear everything is fine ...
Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.
I looked through A LOT of bricked KF threads but I can't fix the issue that I'm having. Before I found this forum and the very useful looking tools that it provides (KFU, etc) I managed to root my KF by using adb and pushing / installing burritoroot by the command prompt. Everything looked OK, I installed su and got root access to work in the adb shell as well as for apps.
I attempted, without much success, to get the Android Market working on my KF but it always crashed. I messed with some permissions like for /system/app, but I changed that one back to match the other folders in /system.
I may have deleted an apk out of /system/app that wasn't the Android Market, but I'm not sure...
Anyway, I tried to reboot my KF and it got stuck in a boot logo loop. It reports a boot mode of 4000 (normal).
I tried the fastboot recovery method and also KFU, but there are some issues:
Root access seems to have disappeared (access through adb shell cannot be elevated)
Burritoroot will not install anymore through KFU (I get the message "Error: Could not access the Package Manager. Is the system running?"
The above message also occurs when I try to use the adb install command
Fastboot never recognizes the device. It sits on <Waiting for Device> forever.
I've tried rebooting the KF while connected and reconnecting the USB.
I made a Factory Cable, but the Fastboot condition is the same.
I uninstalled my Windows drivers until it showed up as "Kindle" in the Device Manager and installed the files that came with KFU.
I tried the KF Unbrick utility, but that didn't seem to do anything that I missed.
Additionally, when I connect with adb shell I have limited file system access. I can is through /system and some other folders, but I can't access /sdcard and I can't seem to mount the sd card
After writing all this and thinking it through, I decided to compare the /system/app directory on my KF with one in an update.zip file that I downloaded.
It looks like I deleted the file ApplicationsProvider.apk from /system/app
That seems to be the only thing missing.
Is this a Try-to-return-your-KF important file? Is my KF hosed?
fonetik said:
Is this a Try-to-return-your-KF important file? Is my KF hosed?
Click to expand...
Click to collapse
Nope, if you can get fastboot working it doesn't matter how broken /system is. Try this to sidestep the Windows driver problems I think you're having:
http://forum.xda-developers.com/showthread.php?t=1430038
Once you get TWRP installed you can restore from the stock update which will wipe and replace /system.
Thanks I'll give this a shot. I had some issues with Windows when trying to install Cyanogen on my Droid X and a Linux Live-CD got me back on track. Hopefully this will do the trick. I'll report back.
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
I had a similar problem and it was my usb driver set up:
/etc/udev/rules.d/##-android.rules
the ## for Meerkat is 70
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″
Vendorid is 1949 for KF
link that got me going: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
sorry if you already know this.
I'm new to this so thanks. I'll try it tomorrow when I get a chance.
fonetik said:
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
Click to expand...
Click to collapse
Are you sure you're in fastboot at that point? Are you using your factory cable? Try doing this to get into fastboot mode and use a different USB cable to connect with fastboot. If that doesn't work, do the same but use Firekit in case the fastboot drivers are messed up.
I'm probably not in fastboot. I'll give this a shot. Thanks again.
Edit:
That seems to have gotten me into Fastboot! I'll see if I can get TWRP installed.
There's a faint pulse =)
Edit 2: TWRP installed OK and I used it to try and install the stock update.zip. It rebooted and then got stuck at the logo again, but I'm going to keep working on it. At least I have a tool I can use.
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP. I cleared all my caches and did a factory reset. Then I installed a pre-rooted version of 6.2.1. It did a little reboot dance for a while and then came up into the OS!
Thanks a ton pokey9000. I'm happy to send a couple $$ your way.
fonetik said:
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP.
Click to expand...
Click to collapse
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
krelvinaz said:
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
Click to expand...
Click to collapse
Sorry about the confusion. It was the FFF triangle, but the KF wasn't going into recovery when I held the power button down. I reinstalled with FFF using adb and it worked. Original post subject updated.
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351
I have the a2107-F will this root process work too?
valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.
I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
YouthTeam said:
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?
unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
are that problem was solved?
how?
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.
emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?
same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.
Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.
for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.
I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot
No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks
abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?
bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone
my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet
I've been going through quite a lot of headache just trying to root this old LG G2 (D801) of mine, and would really appreciate some help. First, I tried to go through the normal steps of ioroot. After having to perform some unknown button combination to access the stock recovery (which I could only do with random, continuous button mashing), I am greeted with an error about adb being outdated whenever I try to sideload the "datroot.zip" file. I eventually realized that, somehow, after trying to (and failing to) sideload adb is temporarily changed from 1.0.32 (as required) to 1.0.31, as I can see when I simply enter "adb" in the command prompt before and after attempting to sideload. Some Googling later eventually reveals that renaming adb.exe to something else (in this case I changed it to androiddb) fixes the problem, as it indeed does for that. I then, however, get it to sideload to what seems to be between 50-60% before it fails and the phone spits out the following:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
On the command prompt's side, it says this at the same time:
"loading: 'datroot.zip' adb server is out of date. killing...
* daemon started successfully *
Total xfew: 1.22x"
After every attempt of Googling around for this, everyone seems to say that I need to use TWRP or CWM instead of the broken stock recovery, and from there just install the file as I've done before on different devices. The problem here is that, to my understanding, I actually need root in order to install a custom recovery, is that not the case? If so, how can I root in this situation if I can't install a recovery, which in turn requires me to root beforehand? If I could get any sort of guidance and hopefully regained sleep, I'd be greatly appreciative, as I'm sure you guys know far more about this kind of stuff than I do. Thank you.
try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP
rajkatiyar07 said:
try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP
Click to expand...
Click to collapse
I can't believe this actually worked! Thank you so much!
yami759 said:
I can't believe this actually worked! Thank you so much!
Click to expand...
Click to collapse
There is a thanks button in the bottom of my post too
rajkatiyar07 said:
There is a thanks button in the bottom of my post too
Click to expand...
Click to collapse
Done