Database Users

[Q] Kindle has been wiped in TWRP and Windows only displays device as Unkown

My nephew managed to get into TWRP and somehow wiped the entire thing clean. I purposely keep a recovery .zip in there but even that's gone. When the Kindle is turned on it displays the Fire triangle but then the screen goes black and stays like that. I can boot into TWRP but can't use the mount option or adb because my computer, and the three others I've tried, refuses to recognize the Kindle. It shows up in Device Manager as Unknown and I can't manually install the driver. I've tried every combination of booting it with the computer off or on, uninstalling the Unknown driver, everything. Can you kind folks please save my butt? Thanks in advance for your responses.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Have you tried starting adb services and going back through the FireFireFire Utility, this has fixed a lot of boot errors that I had in the pass?
Let me know if you need help with starting adb services.
Thanks,
JohninLex

Thanks for your reply
Can you please elaborate on this a bit more? Maybe I'm not understanding correctly but I thought starting adb services wouldn't do anything in this instance since it wouldn't recognize the Kindle as being there at all? For instance, when I run Kindle Fire Utility it shows adb devices as being offline. If I could get the Kindle to show up as anything other than Unknown I'm certain I could just update the driver to an android device and have KFU take it over from there.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Did you root your Kindle "adb devices"
and the following commands?
adb shell chmod 777 /data/local/tmp
adb install Burritoroot3.apk
or did you download a file from the market to get root?
if you did it the above way with adb commands from a terminal would be great.
Either way lets set the driver, download the Kindle Fire Utility extract it to your desktop. or take note where you extracted it. Then go to your device manager and right click on the Kindle (unknown device) look for update driver and browse the the Kindle Fire Utility folder double click on the drivers folder and let it update the right driver you need for your OS (XP,Vista, 7 x86 or 64). Once it finds the right driver Open up a command prompt by going to start run and typing cmd and hitting enter. Once that is done download the KindleADB files and place them in the C:\ (drag and drop should be fine here ) go back to your command prompt and do the following commands:
** urname** C:\ " cd KindleADB " then hit enter
and then do " adb devices " it may or may not come back with your device sn but as long as it has started is what we are looking for.
Once that is done go back to your desktop leaving everything open and look through the Kindle Fire Utility until you find a file named Run.bat double click and hit run this will reinstall twrp and allow it to be remount-able. If you need a stock Kindle rom with update 6.2.2 I have a back up I can share with you.
I hope this helps but if it does not let me know and we can go back over the the driver section.
Thanks,
JohninLex

I've attempted installing the driver manually many times like you stated and on different PCs all containing KFU and the modified .ini file in the .android folder and the message I get when I attempt to manually update the driver is "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems." When I first got the message I attempted to do it in an x86 system and the driver would still not install. My inability to get ANY computer to read the kindle as anything other than Unknown is the main issue. Even if I could make it read as the default "kindle" with the exclamation point it would be enough for me to fix it. But if I can't get a driver to load I'm hopeless to fix it in any way.

Use Android composite driver on your PC to get adb working. Once the adb is working, there multiple ways to boot or install a new ROM. I recommend to start doing the following commands:
Fastboot mode.
Try these ADB commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Ng you have an Android phone, connect to you PC first to see if adb is working using composite ad driver for Windows operating system
Sent from my Amazon Kindle Fire using Tapatalk

I can't use android composite driver. Every time I attempt to install the driver manually I get the error listed above. No matter what I do I can't get the Kindle to be anything other than Unknown

i had a problem where i could only get the fire symbol screen computer would not recognize. I had to start the kindle fire utility plug my kindle into the computer then turn it off, then have kfu install latest twrp again when it says waiting for device turn device on and it will reinstall that and get you back to the recovery. so maybe you can do the same with obtain stock update. not really sure to the kindle. my computer would recognize kindle fire for a few seconds and thats how i could install new twrp

about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
if you can't get rid of the drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
nevertheless i would never install the original stock rom cause you loose fff,twrp and root
use one of the prerooted stock roms instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20

I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck

Help me save my kindle fire
I used KFU to install TWRP and up to CM9. But after that i restore to rom stock 6.2.
But after kindle start the error sorry loop in screen . I can not access to kindle.
process.android.acore force close
We try to connect and re install TWRP but not successfull. when i connect kindle to my pc (XP and window 7) it only recognize kindle as disk driver (athough i try to uninstall and setup manual driver )..
Help me urgent.
Thanks alot

http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

mhb1509 said:
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Click to expand...
Click to collapse
This comment gave a ton of hope since I have tried everything that has been mentioned already except for adding 0x006 but sadly it did not work. There's absolutely nothing I can do to get out of the Unknown state. I've never had my ass kicked this hard by a piece of hardware. I surrender.

maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
I was reading through that earlier and it was a little too intimidating. I'm just going to sit here and cry for a couple of minutes.

Kindle still recognize as disk driver
I try to do something but adb not working (device not found because it recognize as normal disk driver). My pc use window xp professional.
How can i solve this

My kindle still recognize as normal disk driver
I try to test on some computers (xp, win7) but unfortunately, my kindle still recognize as normal usb only. (not adb device).
So i don know how to fix this problem
Please help me, or give me a hint

xp is a good choice - you don't have to care about the uac (user acces control)
have you checked according to my post #12 above ?
to shorten things up i could take a look with teamviewer if you like
just gimme a pm ...

Have you added the second vendor and the second set of USB command lines in your google/extras folder? If not add those turn off the kindle then turn it back on do "fastboot devices" then put the update.zip in your platform-tools folder then push the update to your kindle to be flashed by twrp. The command for that would be "advt push update.zip /sdcard/update.zip" you can have the kindle already in twrp by this point. Also when all is over you will have to reroot and reinstall fff and twrp. If you need help send me a message.
Sent from my Kindle Fire using Tapatalk

Hard reset on main-board KF
My KF is frozen. I try to do hard reset by hold pw button 20s, but not effected.
So i've just open back-slide my KF, and see KF main-board.
Have hard reset trick on this main-board.
Help me please.

[Q] ADB error:device not found

Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
plug the phone, open a terminal as administrator/root and type
adb stop-server
adb start-server
adb devices
the last command must return your device name-id
If not there is smth wrong with your installation

The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2

theminikiller said:
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
No you don't need to enable mass storage, but you need to enable USB debugging from dev settings from the device. Use these drivers
https://www.dropbox.com/s/ryn7l7z0nfc842g/u8800_pc_drivers.zip

emmm... feeling kinda stupid right now... but how do i install the drivers? xD

theminikiller said:
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
Click to expand...
Click to collapse
You have to install them manually from device manager.
Sent from my U8800

After i choose the folder with the drivers i only get a message saying it didnt find any drivers. Do you know why i cant install them?

Is it the same drivers when I'm using aurora ics as gingerbread roms?
Sent from my U8800 using Tapatalk 2

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps

kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?

theminikiller said:
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
Click to expand...
Click to collapse
I think its safe mode
Sent from my Impulse 4g running vPure Professional CM7.

kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thank you the instructions in the link provided worked for me. I am able to see my listed by adb device command...

help
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced

jakk181571 said:
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
Click to expand...
Click to collapse
this is not the forum for ur device..

then please tell then where is the correct forum.
i only when to this one because google brought me here, and it was on adb, which is what i am have trouble with.

Re: Adb - device not found (I had same problem) Fixed
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue updating my Nexus 7 in adb download mode device not found. You will also notice in system setting device driver is showing an error. You can download Adb driver installer which should detect any missing driver and fix the issue.
It worked for me straight away otherwise I had no way round getting to solve the problem. Fheww!! hope it works for you
Many Thanks.
adbdriver.com/downloads
---------- Post added at 05:55 PM ---------- Previous post was at 05:43 PM ----------
You may be missing the device driver when switching to USB Debugging mode using ADB Command prompt device not found.
Please download and intsall adb driver installer. It found my device and installed missing driver straight away problem fixed now I dont seem to have any issue.
adbdriver.com/downloads/
Glory be to Almighty God. Thank you!!

theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
same problem...

I think I soft bricked the KFHD 7', help pls.

So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.

procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..

I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2

procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?

lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.

procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well

lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.

procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?

did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:

KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!

In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2

the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command

Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium

[Q] ADB error: device unauthorized and device offline

I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.

HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.

ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.

HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.

Perfect, worked. Thanks!

I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...

usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.

I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.

Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!

legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe

maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway

legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards

c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.

legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.

I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.

SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.

after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.

I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.

thanks to the adb kill-server guy! worked for me

gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto

Something interesting?

So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.

Here are the photos

njking25 said:
Here are the photos
Click to expand...
Click to collapse
njking25 said:
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Click to expand...
Click to collapse
That is something interesting. It is asking which os to boot to, not install.
I'd like to know how you got into the bios? I am looking for a way to install Linux....
Sent from my YOGA Tablet 2-1050F using Tapatalk

njking25 said:
Here are the photos
Click to expand...
Click to collapse
Did you get this figured out?

I can see "fast boot" enabled. Have You tried to switch it off? any other menu is displayed?
Have You tried to "power+vol down" on it?

I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.

zach181 said:
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
Click to expand...
Click to collapse
This guy seems to have stumbled on it also. I flashed the stock kk firmware and I am trying to do it but can't get Lollipop update to work. But it won't boot after it fails so I am reflashing KK again.
http://forum.xda-developers.com/showpost.php?p=60490907&postcount=578

Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.

zach181 said:
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
Click to expand...
Click to collapse
If you try it do let me know. I need to get into the bios to get started on a dual boot to Linux on this bad boy...

I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.

So... conclusion. we have to damage firmware to boot efi...
If we could swap img file before upload to tab (during this 25 second wait) we could make windows installation possible. Am i right?

zach181 said:
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
Click to expand...
Click to collapse
@social-design-concepts suggested we should try to change the boot order using efibootmgr. I've been communicating with him. Here is the post in the Venue thread... http://forum.xda-developers.com/show...postcount=2083

Links giving 404

zach181 said:
Links giving 404
Click to expand...
Click to collapse
here it is again... http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083 it got truncated.

Thanks workdowg.
It seems it's not as clear cut as first thought. Mind you, I didn't expect it to be. I did try a HP keyboard with OTG in Android and that got picked up ok (No lights on keyboard)
I'm a bit in the same mind as Social-Design. I'd rather have a definite way to restore Android from a totally blank internal drive before I have a go. Just up to page 214 in the thread so it may be covered later.

UEFI soft brick?
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.

Yosha1 said:
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You can get it to boot from USB? Get someone with to use tethered twrp and get a backup of the esp and fastboot partitions.
I have 2 things you can try if the goal is getting back to booting stock Android.

Yosha1 said:
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
Have You tried booting any x64 linux iso from flash drive?

dreamnewbie said:
Have You tried booting any x64 linux iso from flash drive?
Click to expand...
Click to collapse
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.

Yosha1 said:
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Click to expand...
Click to collapse
extract and dd this to a usb drive and see if it is able to boot it View attachment 3415895 if it successfully boots replace the fastboot.img thats on the thumbrive with one for your devices and see if it boots. if your fastboot.img is named droidboot.img rename it to fastboot.img.
If you can successfully get your devices droidboot/fastboot.img to load you can then disconnect the usb-otg cable and reconnect it to your PC and use the phone flash tools to restore your device completely.