Database Info

unbrick samsung galaxy s vibrant.

i have a real problem, trying to flash my samsung vibrant with odin, (installing the unofficial update) my phone was bricked, i cant get into download mode, the key combination vol-up + vol-down to get to download mode is not working, i can't get into recovery mode either, (well getting into recovery mode has never worked) i tried using adb reboot recovery with sdk and it comes as device not found.
Am i screwed or there is any way to unbrick?

cervantesjc said:
i have a real problem, trying to flash my samsung vibrant with odin, (installing the unofficial update) my phone was bricked, i cant get into download mode, the key combination vol-up + vol-down to get to download mode is not working, i can't get into recovery mode either, (well getting into recovery mode has never worked) i tried using adb reboot recovery with sdk and it comes as device not found.
Am i screwed or there is any way to unbrick?
Click to expand...
Click to collapse
Take out the battery, wait a full minute. put it back in and the case back together without inadvertantly hitting either the power or up/down keys. Now press the down key. While holding it down, hold down the power key. If that doesn't put you into download mode, you have done the impossible. These phones are (almost) impossible to brick.

I have seemed to have done the something similar as I was trying to reflash with ODIN and the phone went black, I left it alone for several minutes and now when I try to turn the phone on I just have a graphic with a phone and a computer with a little triangle with an exclaimation mark in the middle and nothing else happens.

djallen1 said:
Take out the battery, wait a full minute. put it back in and the case back together without inadvertantly hitting either the power or up/down keys. Now press the down key. While holding it down, hold down the power key. If that doesn't put you into download mode, you have done the impossible. These phones are (almost) impossible to brick.
Click to expand...
Click to collapse
I really think i have the done impossible, there is no download mode nor recovery mode, (well, this has never worked) i don't know what to do, i'm getting my phone replaced.
I tried using adb on my computer, but the device is not found, my computer doesn't recognize my device.

cervantesjc said:
I really think i have the done impossible, there is no download mode nor recovery mode, (well, this has never worked) i don't know what to do, i'm getting my phone replaced.
I tried using adb on my computer, but the device is not found, my computer doesn't recognize my device.
Click to expand...
Click to collapse
UGH
I have the SAME problem...but I always had download AND recovery working...
after a few flashes in a short span...they just dissapeared...
screen just turns black after the "S" logo animation....
ADB can't see the device either

Same Here Too :-|
i've been searching and trying to get into dowload mode for a week and i't not working. i can hear it boot up but just stuck on the darn Vibrant screen

philthyman21 said:
i've been searching and trying to get into dowload mode for a week and i't not working. i can hear it boot up but just stuck on the darn Vibrant screen
Click to expand...
Click to collapse
I was there, use Odin to reflash to stock.

huh
djallen1 said:
Take out the battery, wait a full minute. put it back in and the case back together without inadvertantly hitting either the power or up/down keys. Now press the down key. While holding it down, hold down the power key. If that doesn't put you into download mode, you have done the impossible. These phones are (almost) impossible to brick.
Click to expand...
Click to collapse
i beg to differ
nothing is working for me either

So I went to This Site pathikshah. com /blog / install-android-2-2-froyo-galaxy-s/ (sorry about the spaces new user and xda wont let me post links, not spamming honest), I did exactly as it said it was working as planned until it reset after install. First instead of the vibrant screen coming up it now says:
Galaxy S
GT-I9000
Then It goes to:
Android System Recovery <3e>
on that screen it says twards the bottom:
update media please wait
E:Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E:copy_dbdata_media:Cant mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
so when I try to scroll through the recovery menu I have to push vol Up to scroll down
also it does nothing when i press the ok button (power button), unless I hold it down then it resets and goes back to the same recovery screen

I rooted the samsung galaxy s then added a rom and the rom is crashing my phone I've tried aboslutely everything don't know what else to do.

i also have a problem
i have install ROM manager and make a back up
went i try to recovery my backup it give me first the original recovery mode i know i have to select update.zip to access the clockworkmod recovery (ver 2.5.1.2 last one) i use the option restore and start it
now my phone just reboot in recovery mode
i'm looking if some one have a working ROM backup
tnx for your help
Drago.

cervantesjc said:
i have a real problem, trying to flash my samsung vibrant with odin, (installing the unofficial update) my phone was bricked, i cant get into download mode, the key combination vol-up + vol-down to get to download mode is not working, i can't get into recovery mode either, (well getting into recovery mode has never worked) i tried using adb reboot recovery with sdk and it comes as device not found.
Am i screwed or there is any way to unbrick?
Click to expand...
Click to collapse
Read instructions and download files from thread here:
http://forum.xda-developers.com/showthread.php?t=734475
Watch this video:
http://www.youtube.com/watch?v=AnY7P14JSWQ
Good luck

fstathes said:
Read instructions and download files from thread here:
http://forum.xda-developers.com/showthread.php?t=734475
Watch this video:
http://www.youtube.com/watch?v=AnY7P14JSWQ
Good luck
Click to expand...
Click to collapse
Thank you for the video link. I was up to that point unable to get the download/shoveling droid screen. Now I'm in the process of finally getting the phone back to stock after downloading the t-mobile update that cam through and bricked the phone.

no downloading mode
Hi i was hoping this will help me to reenabeling my bricked samsung. But i cant get it in to downloanding mode. the 3 button way isnt working and the way showed in the movie neither. Is there an other way to get the phone back to work?

I have tried all the methods posted here as well as many others from the link posted above. But to no avail.
I did everything successfully up until the reboot. Whereupon, it would not start. No amount of button combination helped me. And taking out the battery pack is no help either. It just won't start. I could use any advice.
Thank you.

I'm in the same boat now, attempted to odin back to stock and now I have a brick. It's just blank, I cant get it into download or recovery mode using any method described.
Is my only shot the jig method I've read about now?
EDIT
Nevermind, I got it. Pulled the battery, replaced it, held down both power buttons, inserted usb (already plugged in comp w/ odin open), boom..entered download mode and flashed..

cervantesjc said:
i have a real problem, trying to flash my samsung vibrant with odin, (installing the unofficial update) my phone was bricked, i cant get into download mode, the key combination vol-up + vol-down to get to download mode is not working, i can't get into recovery mode either, (well getting into recovery mode has never worked) i tried using adb reboot recovery with sdk and it comes as device not found.
Am i screwed or there is any way to unbrick?
Click to expand...
Click to collapse
Remove the battery and insert it again, now keep pressing the volume buttons and connect the USB cable to your phone, the usb cable must be connected to your pc first.

hey, i also experienced bricking my phone. is there a step by step process how to unbrick it? i need urgent help please. by the way im using samsung galaxy s 4g (

after i have gone to download mode. my computer cannot recognize my device. help me please.

to the post above me. Sounds like you have a bad usb data cable. Grab you a new cable online and you should be good to go
I'm assuming you have already downloaded the drivers to your computer. Sasmung.com will have them

[Q] Idolian Studio 10 tablet Boots to recovery

Have got an idolian studio 10 tablet. when turn it on for the first time it went directly to the recovery instead of booting up. Reboot and factory reset, didn't work. Can't find the stock rom for it, can't find the usb drivers that are needed for adb. Holding volume up and power button leads to the same recovery menu. How can i fix this? Pleas help

this might help
madeinkoja said:
Have got an idolian studio 10 tablet. when turn it on for the first time it went directly to the recovery instead of booting up. Reboot and factory reset, didn't work. Can't find the stock rom for it, can't find the usb drivers that are needed for adb. Holding volume up and power button leads to the same recovery menu. How can i fix this? Pleas help
Click to expand...
Click to collapse
I need to got to their website .... Scroll to the bottom of the page, and click on to, "Downloads" once on the download page, you should see a few tabs on the right hand side. One is the 633Mb file that has everything you need to put your system together. The other tab is the actual PDF instructions on how to preform this these tsks. Can add, once you have downloaded and opened up those files, you will see another "manual inside" if i recall correctly, the manual is in English, after the Chinese .....
Hope this can help

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.

How do I fix my OnePlus One’s bootloop?

Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?

Lazy Titan said:
Greetings of the day,
Hello everyone, I'm having a oneplus one 64GB phone that is not getting start, everytime i connect it with the charger it goes into a bootloop. Yes the phone was rooted and I was using a custom ROM with the default kernel. The issue started when I tried to reset the phone to battery settings. I think I somehow messed the kernel and now it is stuck in bootloop. The problem is that I can't connect it to my computer or put it in debug mode as it just restarts again. Any idea how to actually boot it so I can install the kernel and ROM again?
Click to expand...
Click to collapse
Can it go into recovery mode(power+ vol-)?

Mr.Ak said:
Can it go into recovery mode(power+ vol-)?
Click to expand...
Click to collapse
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.

Lazy Titan said:
No, My phone is not getting on but whenever i am connecting it with my charger the phones goes in the Bootloop, and when i am connecting it to My PC while pressing Volume Up + Power Button Pc shows that the Unrecognized devices has been connected.
And i think phone is Hard Bricked. I have tried ADB software and one plus 1 drivers manually but it didn't worked too. I have tried minimal ADB too but it also didn't work.
Kindly let me know about it.
Click to expand...
Click to collapse
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.

giaur said:
Volume UP + Power should boot in fastboot mode. Volume Down + Power should boot into recovery. First, try to boot recovery.
Click to expand...
Click to collapse
I have tried both, but nothing happens with it, Volume UP + Power shows the unrecognizable device is connected and Volume Down + Power does nothing it continues with bootloop .

Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.

bmark240 said:
Have you got Developer Options enabled?
Goto About Phone & Tap Build Number until Developer Options is activated. Goto Developer Options> Advanced Restart & enable the switch.
Press power button->Restart->Recovery.
It will now boot into Recovery.
Also have you tried keeping hold of power button whilst it bootloops. Keep holding the power button until it powers off. Then press Volume Down & Power Button to power back up (you might see a slight flicker onscreen that means it should go into Recovery mode). Keep hold of these buttons until you gain Access to Recovery Mode.
This will allow you to Recover or flash a different ROM.
If you're having issues connecting to a computer (Windows) try downloading Windows Media Center for your version of Windows. This will install media drivers to recognize your phone.. If all went well you will get the pop up with A0001 (Codename of OnePlus One). From there you should be able to enter fastboot mode through ADB.
If this doesn't help you, I'm sure that someone else will untangle the puzzle to get your device in good working order buddy. Good Luck.
Click to expand...
Click to collapse
he said his device is in bootloop. how come he will turn on the developer option then?

akhiarr said:
he said his device is in bootloop. how come he will turn on the developer option then?
Click to expand...
Click to collapse
This has got to be some sort of World Record for resurrecting an old post from over five years ago. Congratulations on that achievement!
Did you just join to post that?
Lol.

Help ! Deleted Fire UI...

Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.

Xpun3414 said:
Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.

DragonFire1024 said:
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.
Click to expand...
Click to collapse
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.

Xpun3414 said:
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.
Click to expand...
Click to collapse
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.

DragonFire1024 said:
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.
Click to expand...
Click to collapse
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet

Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
If you can't boot to recovery at all, you might be perma bricked.
Sent from my Moto E4 using XDA Labs

Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.

GamerOfRassilon said:
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.
Click to expand...
Click to collapse
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..

Ok today, while in recovery mode, I plugged in the tablet & I got this.....

Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.

Xpun3414 said:
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..
Click to expand...
Click to collapse
Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
Sideloading in recovery does not require ADB authorization !!! All you need to do is to get the correct drivers loaded, to make sure that your PC can see your Fire. Recovery is for restoring things, if it needed ADB authorization, it would defeat its purpose.
Get USBDeView, and see which devices it shows when the Fire is in recovery, and plugged into a PC USB port. Then try to locate correct drivers. You may want to delete any driver related to this Fire in USBDeView, then plug it back in, make windows try to get the driver for it again.

GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
I can't believe I didn't think about that. Totally sliped my mind.
Anyway. Used a different usb cable & a different pc and BAM ! Flawless recovery. Thank you for your help.

-------------