Database Info

[Q] [HELP] Nexus S Drivers? I9020T Wind Mobile

I am trying to root my Nexus S. Actually, I'm trying to play around with the ADP developer terminal but I can't seem to get my drivers working. I even called Samsung but they told me they're supposed to not be installed (sigh).
It says that the drivers for Nexus S are missing
it also says the drivers for Android 1.0 are missing
I tried to install the Android 1.0 drivers manually through device manager (I am using Windows 7 64). I have the latest version of the android SDK installed along with the Google USB Driver package, revision 4
I navigate to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver but windows just says,
"Windows was unable to install your Android 1.0
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I checked the directory myself and it has a few files in it
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
Does anyone know what is going on and how I fix this?

Never mind, it just worked.
I right clicked the item in device manager and went to "scan for hardware changes" and then went to properties and navigated to the driver tab and went update driver and put in the directory again except this time with a trailing backslash and it worked.
I also rebooted the phone into regular mode instead of the power button + volume up boot loader.
I'm not sure which of those things made it work since I know I did the scan for hardware changes and properties / update driver thing several times without it working before.
*shrugs*
Thanks

WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!

Aro2220 said:
WAIT!!
I spoke too soon. Apparently, when I boot it back into the bootloader (power button + volume up) it changes back to Android 1.0 and says it is missing drivers. Once again it will not let me install the drivers no matter what I try.
Even though I successfully installed the driver in regular mode, now it says the driver can't be found and there's nothing I can do about it.
Please help!
Click to expand...
Click to collapse
uninstall what you installed, then go to PDAnets' website http://junefabrics.com/android/ download the free installer. then start the program, follow the on-screen instructions, and let it install the drivers for you.

"Install to phone failed
Installer fail to open device"
When I go into windows device manager it shows up as Android ADB Interface on my computer...even when in the boot loader.
But if I try adb devices it doesn't list it as a connected device.

Aro2220 said:
Install to phone failed
Installer fail to open device
Click to expand...
Click to collapse
did you go to the phones main settings, applications, development.. and enable usb/android debugging?

Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.

Aro2220 said:
Yes, I did that originally before I started having any of these problems.
When the phone is booted normally I can adb devices and it shows up. I can connect to it as well with adb shell and see all my files.
Then, I power down my phone and boot it back up holding the volume up and power button.
Now I am on the FASTBOOT MODE screen:
Code:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKF1
CARRIER INFO - TMB
SERIAL NUMBER - 12345ETC
LOCK STATE - LOCKED
SELECT - VOL UP or VOL DOWN
EXECUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Now I adb devices and nothing is there.
Click to expand...
Click to collapse
do a fastboot devices

Might be because you can't use adb in fastboot.
Sent from my Nexus S MV from the XDA Premium app.

Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
EDIT: I think I didn't know how to use the recovery module. If you press volume up then power then let go of power or something like that it shows you some command options at the top of the screen.
But I realized that wasn't clockwork and after doing some reading I think when I rebooted the phone it auto-flashed the recovery module back to the default one.
So I flashed clockwork recovery.img again using the same steps except this time I went straight into the recovery option instead of rebooting my phone and then I saw clockwork.
I followed the rest of the steps from that work and everything seems to be working.
Thanks again ;-)

Aro2220 said:
Fastboot devices found my device. I was able to unlock it and follow the instructions on http://forum.xda-developers.com/showthread.php?t=895545
But I run into a problem whenever I enter the recovery mode. It just gives me the android with the exclamation mark in a triangle symbolizing that something went wrong.
Any ideas?
Click to expand...
Click to collapse
fastboot a custom recovery like clockwork or twrp. then flash whatever rooted rom(and gapps) you plan on flashing.

Go To The Link From Your PC and Click the Box Within The YouTube video. Watch the video and in description should be a download link named NexusRootNew
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Download it
Extract it
Place into C Drive
Within the file are the drivers, Recovery and superuser
Just follow the Video and u should be ok
Sent from my Nexus S using xda premium

[Q] Too many pattern attempts... No Recovery menu

hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"

mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
did you try to pull out the battery?
if not take it off,put it again
then hold volume down + power button until it shows the bootloader screen

mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?

mmcr said:
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
Click to expand...
Click to collapse
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.

heavy_metal_man said:
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
Click to expand...
Click to collapse
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?

mmcr said:
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
Click to expand...
Click to collapse
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.

heavy_metal_man said:
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
Click to expand...
Click to collapse
boots up in safe mode

mmcr said:
boots up in safe mode
Click to expand...
Click to collapse
hmmmm. running out of ideas now. was this your device? do you know the google account ect?

heavy_metal_man said:
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
Click to expand...
Click to collapse
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.

mmcr said:
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
Click to expand...
Click to collapse
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.

So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?

se1000 said:
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
Click to expand...
Click to collapse
i've tried that several times bro, just the same out come everytime

heavy_metal_man said:
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
Click to expand...
Click to collapse
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.

mmcr said:
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
Click to expand...
Click to collapse
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.

heavy_metal_man said:
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
Click to expand...
Click to collapse
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices

mmcr said:
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
Click to expand...
Click to collapse
indeed so. but you cannot fault it as a security measure :silly:

Fastboot Mode Issue

Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
After you use the volume down key to highlight "Fastboot", do you then press the volume up key to select it? If you just sit there and wait it will reboot normally. You must press the volume up key after you've highlighted the menu option.

akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.

Thank-you for the Response
bweN diorD said:
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.
Click to expand...
Click to collapse
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.

akkay1 said:
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.
Click to expand...
Click to collapse
That's the entry to stock recovery. You have to push a combination of buttons from there to get into recovery. I forget the button combination, it has been posted many times, try searching or wait for someone else to jump in with the answer.
Sent from my LG-VS980 using XDA Premium 4 mobile app

Not sure where to post this question been reading so many post my eyes are tired......
- XT926 upgraded to kitkat 183.46 last week via flash in RSD from JB 4.1.2
- Root went well DONE (Towel root .apk)
- Unlock went well DONE (Motopocalypse .apk) yes fastboot shows the #3
- Flashed TWRP 2.7.1 DONE (did it using the adb in motopocolypse)
- Backed up my current stock ROM in TWRP seemed to go well the program confirmed the backup was successful...So I thought
- Got confident and wanted to try flashing CM11 (Kitkat version)
- After flashing CM11 my phone got stuck at boot like many others have.... no problem I backed up my stock ROM in TWRP.....So I thought
- Went to restore my stock ROM using TWRP and yup you guessed it like many others the restore failed half way through
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????

wonka144 said:
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????
Click to expand...
Click to collapse
Not sure how to help you with your immediate problem at hand, but going forward, I definitely recommend the sms backup + from the Google Play Store. Nice thing with that app is, you can link it to your gmail account, and all your text messages are backed up to your gmail.

HELP! ROM Manager bricked my O3D - Is it fixable?

NOTE: Before we start, I have now googled it and in hindsight I probably should of left RM alone!
Anyway as the title states my O3D seems totally goosed! I selected the recovery flash in ROM Manager for P920, it rebooted and all it does now is show the logo for a second, vibrate then off. I tried the usual tutorial stuff...
Power button, Vol up battery in - it comes up 'USB Device Unrecognised' and then It also keeps popping up 'Unknown Device' however when I click on properties every entry is 'Unavailable'
Power button, Vol Down, battery in does nothing (tried it a million times)
If I do...
Power button, Vol up then apply the battery - Device Manager finds... 'LG Mobile USB Modem', 'MAP SMS' (Other Devices) and 'LGE Mobile Composite USB Device'
No sign of OMAP44xx so the flash tools don't see it... strangely LG Mobile Support Tool sees the phone and tries to update it however it says it has the latest firmware, when I use the update recover option it gets to 15% but then complains that it can't communicate with the phone.
Is it dead? :crying:
Any help would be much appreciated.

dont worry. its not dead. has happened to my phone a trillion times ..
all you need to is try as below:
1. without connecting phone to usb first hold down 3d button then volume down and keep pressing power untill it starts up and then off again , then release all 3 together as it is off and repeat (remember first 3d then volume down and then power). this time just let the power button go on lg logo but keep pressing the other 2.
2. if this doesnt work, then easiest method - download omap4boot for optimus v1.21 or all in one p920 v1.3 by XDA, remove battery, only press down the volume up button and while pressing connect usb. make sure you hear 1 ding of connect , 1 dong of disconnect then 2 dings of connect. after this the ding dong should end .. if you have all drivers installed , then it will install omap drivers. a window will pop up and everything will have a green check. once it does that you can install a custom recovery twrp or cwm using fastboot . boot into recovery and flash a rom.
still if doesnt work, have patience, post a reply and will tell other steps to proceed with .....

Thanks for your time RVBSD, unfortunately (although I will keep trying!)
In No. 1 - I get the first logo, but when I re-apply the 3D/V and power, I don't get the second logo.
In No.2 - I get the first ding/dong then just 1 ding, no sign of Mr OMAP! - I'll keep trying though.

Once u get the second ding and then this music stops, Open device manager. Look for lg usb modem and disable it. Then look for omap44 something. The device manager may be refreshing quickly. Somehow i had a chance to right click on omap device and chose update driver. Select manual and choose omap.inf from the folder that u have to download as per my previous reply. Restart computer and check again.
Alternatively you can install all inf manually, right click and install, before connecting the device.
Let me know
Sent from my LG-P920 using xda app-developers app

Again, thanks again for your input but I am still no further. I manually clicked the inf and it said it installed fine... but nothing changed in Device Manager. I then attempted to 'force' the driver on the unknown device, however after it installed it returned a 'Code 10' error... unable to start.
Even tried the service software 'LGNPST' but it couldn't even connect to the port! ho-hum...

i tried it again. even on my computer it didnt take the omap drivers this time.... strange .....
but i could install fastboot, then installed cwm recovery . then flashed a rooted rom and its working ...
1. Turn off your Phone, pull out battery.
2. download omap4boot-for_optimus-v1.21 (run "start_fastboot.bat" (it will wait until phone connected)
3. connect phone with USB cable without battery, the usbboot will start
4. insert battery while the usbboot is waiting, it gives 5 secs only
5. unplug USB cable the LG logo will appear with fastboot on top
6. download the attached files to your desktop and extract
7. open cmd and in cmd navigate to fastboot.exe location, where ever downloaded
8. run fastboot.exe from cmd and choose the cwm file to be pushed to your phone
command : fastboot -s flash recovery recovery-clockwork-6.0.1.9-p920.img
9. reboot device into recovery , try to wipe cache and factory reset and try to reboot
if this works it will take you to existing installed rom, then you can reboot to recovery and flash Su_Bbox_1.20.2_gazhead_signed.zip to root it
10. else copy a custom rom to sd card , insert in the mobile , reboot into recovery and flash the cutom rom

PLease help
CAn you tell me how can mount recovery partition

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.

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