As the title states I follow the directions to get into the stock recovery ans I dont have that option. Only have NVFlash, RSD and fastboot.
Any Ideas?
James
what are you trying to do in recovery?
There isn't any recovery for now I don't think.
To flash the overclock/root images you just use fastboot
I am very familiar with android. I am referring to the stock recovery. Since I have not gotten an update yet I am not sure how moto works but most updates run thru the stock android recovery however I don't even have the stock recovery and I sure as heck don't want to exchange it because of the large amount of customizations I have done. I know I can OEM unlock and drop the stock recovery on there but with no course of action to relock it makes no sense.
James
There is a recovery, but it doesn't show up in the boot menu for some reason.
With ADB, you can to an "adb reboot recovery" and it will boot into recovery, so it's definitely there.
-Jim
But in order to adb reboot recovery on needs su access unless the xoom is different than everything other device. And I am not interested in rooting until moto releases the stock images.
James
interesting.. one can adb reboot recovery non rooted. Granted it just gives you the stock flashing screen for android but atleast I know its there. Motorola must have made some changes
Thanks.
James
cj10488 said:
interesting.. one can adb reboot recovery non rooted. Granted it just gives you the stock flashing screen for android but atleast I know its there. Motorola must have made some changes
Thanks.
James
Click to expand...
Click to collapse
Did you find a way to standard recovery menu. I spend 1 hour speaking with Moto support. They told me that I need to send back my XOOM WiFi tablet, because something wrong. I'm sure I'm not wrong in pressing that bloody buttons, it's just wrong manual and support also don't know how to access to standard recovery on WiFi version.
When you adb into recovery hit Power and Volume up. Your menu is there.
stevenege said:
When you adb into recovery hit Power and Volume up. Your menu is there.
Click to expand...
Click to collapse
No, I'm trying to access to recovery menu without PC. My PC has problems with USB, so it didn't recognize XOOM (I checked it on the another pc, so I'm sure that only that bloody Dell D620 and corporate security programs doesn't regonize XOOM)
So I need to get access from tablet with locked bootloader and without root access. According to the troubleshooting manual I need to press volume down button, as soon as Motorola logo appears, but I made all that things several hundreds times and nothing. I could see only fastboot, RSD or NvFlash, bug no Recovery.
Also as I found owners of 3G version, doesn't have such problems, looks like only WiFi version had such problems.
If somebody who has WiFi version could make video how to get access to Recovery menu from device without PC, it could help really.
Kozdoba said:
If somebody who has WiFi version could make video how to get access to Recovery menu from device without PC, it could help really.
Click to expand...
Click to collapse
I don't think you can. I certainly couldn't find a way. The only way I could enter recovery was via adb. That said, adb doesn't require root. You just have to make sure "USB debugging" is turned on under settings->applications->development.
-Jim
Sent from my Xoom using Tapatalk
BeagleBoy said:
I don't think you can. I certainly couldn't find a way. The only way I could enter recovery was via adb. That said, adb doesn't require root. You just have to make sure "USB debugging" is turned on under settings->applications->development.
-Jim
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
The most strange that Motorola support sure that we could do it via buttons. I spend 2 hours with Level 2 specialist trying how to do it. After that they advice me to send it back, because something wrong with my XOOM.
if you push the vol down button when its in the moto logo and you get the "starting fastboot protocol support" message that means you pushed the vol down button too early
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
when recovery loads up press down the power key then let go of vol up and you should see the options
i dont remember what the options are since i dont have the stock recovery anymore but im sure its the same as any other stock android recovery
Use an app called Wireless ADB, it has helped me out in situations like this.
PaulG1488 said:
if you push the vol down button when its in the moto logo and you get the "starting fastboot protocol support" message that means you pushed the vol down button too early
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
when recovery loads up press down the power key then let go of vol up and you should see the options
i dont remember what the options are since i dont have the stock recovery anymore but im sure its the same as any other stock android recovery
Click to expand...
Click to collapse
I tried to do it several time, but always I see only "starting fastboot protocol support"
Do you have WiFi version of the tablet, because it looks like this problem only with it. 3G version doesn't have such problems(
Guys who has WiFi version of the tablet please make video how you did it. I already comes to Level 3 specialist at Motorola support, because the rest specialist couldn't find Recovery menu of WiFi version.))))
ateld said:
Use an app called Wireless ADB, it has helped me out in situations like this.
Click to expand...
Click to collapse
Yes I know, but I would like to know how to get access to that menu without PC at all. I bought XOOM tablet to leave my PC at home during my business trip, so I would like to be sure that everything ok with my XOOM tablet. Right now I don't see any proof that I could access to Recovery menu without ABD
PaulG1488 said:
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
Click to expand...
Click to collapse
This doesn't work for wifi. You get the choice of nvflash, rsd and fastboot, but not recovery.
Sent from my Xoom using Tapatalk
BeagleBoy said:
This doesn't work for wifi. You get the choice of nvflash, rsd and fastboot, but not recovery.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Welp, that sucks. I hope the UMTS Xoom is better.
Related
Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?
Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.
ferparedes said:
Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?
Click to expand...
Click to collapse
For the cwm thing: first of all, with your tablet turned on, try if the VOL UP and VOL DOWN keys are working. Then turn it off.
Press VOL DOWN + POWER until you see a little write on the upper left corner, then release all and press VOL UP.
For adb: turn on your tablet and connect it to your pc. On the screen of the tablet click on the icon of asus sync in the lower right corner then click on the popup. It will search for asus sync on your computer (have you installed it, right?). From that moment on, adb should work normally.
Hope this has helped.
Thanks! adb worked. Still can't get into recovery. I think it's borked, because I used "adb reboot recovery" and the tablet just rebooted normally.
Any more ideas??
akameswaran said:
Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.
Click to expand...
Click to collapse
Maybe that's it. I'll try it...didn't want to, because I don't want to wipe anything. This nice device of ours is so much more complicated than my SGS
Try this app, if CWM is installed correctly it should work. Cheers.
http://forum.xda-developers.com/showthread.php?t=1173434&highlight=reboot+recovery
Thanks! CWM was definitely broken, probably because I attempted OTA update.
So I went and used the guide in the nvflash unbricking thread, and since that guide installs Prime 1.4, I went ahead and updated to 1.7. Now I'm rooted, cwm'ed and prime'd!!!!
Sent from my Transformer TF101 using Tapatalk
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
First,
I really want to thank everyone for their support in this forum. Everyone has been amazing.
I was trying to bring my MZ601 back to stock yesterday. Something bad happened during fastboot and asked me if I wanted to unlock my device. Then the screen locked up and didnt do anything. I rebooted the device and now it gets stuck in a boot loop with the EOS symbol (last rom I installed). When I enter recovery there is nothing there, all of my data is gone.
Worse the device is not recognized on my computer nor can it be found in adb fastboot. I have updated motorola drivers, but I think the device never gets past a certain point in order to be found.
Can somebody please help me.
Thanks,
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
Hi,
Thanks for the tips. Unfortunately, it seems that I have caused the entire sd card partition to be erased. That mean when I trry to fastboot my device is not recognized. Also, i cannot add anything to my xoom through usb. I have tried to flash through the external sd card, but to no avail. What do I have to do?
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
dfib1 said:
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply to my message.
Unfortunately I cannot find my device when it is plugged into my computer (PC). It does not show up on my computer nor in the device manager. I can start the fastboot protocol on my device by rebooting, but I also cannot find my device in ADB.
Thanks for the reply, but I am still very stuck.
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
ndanl said:
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I did everything I have done before. I have setup android sdk, java, and motorola drivers on two different PCs. Both fail to find my device when i type ADB devices nor does ADB reboot bootloader work. I tried the different cable, but that also did not work.
Hi,
I see that your problem is quite hard, try doing this:
1 - Force your tablet to shut down (vol+ + Power)
2 - Turn on while holding the vol- button
3 - Keep pressing vol-
4 - Plug on your PC and try fastboot devices, adb won't work!
5 - If 4 didn't work, keep trying until it does
6 - Install a Stock ROM (so you will solve your problems)
If the above don't work, contact me via PM, so we can talk easily (maybe GTalk or something like this). Good Luck
~XxLordxX
"This Story Ends Where It Began" - Octavarium (Dream Theater)
XxLordxX thank you!!!
I took your advice and just used fastboot. Then I flashed the stock rom I wanted to use. My xoom is back up and running. I really appreciate the tip.
Also thank you to everyone that responded in the post, again, that is why I love coming here.
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
I have this problem now but I don't know what to do. Please help me out
I got this phone used. (Droid Razr HD) Not sure of its history. As far as I know it was all stock until today.
When I found out I could root and unlock the bootloader I did so. Then I wanted to go into recovery and make a backup (yea I know...did that backwards) I powered the device off...hit the volume rocker switch and the power button at the same time and it entered into the Boot Mode selection menu. I hit the volume down to move to the recovery option and then hit the volume up button to select recovery.
At this point the big red M & Dual Core Technology logo appears. Stays there for 1.5 minutes then disappears briefly, comes back on for 15 seconds and then boots the phone normally.
So....I downloaded and installed Rom Manager and had it flash the latest CMW Recovery, turned the phone off to access the newly flashed recovery and the phone again went to the big red M & Dual Core Technology logo set there for 1.5 minutes, disappeared briefly and then booted the phone normally.
So.....I downloaded the lasted CMW Recovery image and used ADB and Fastboot to flash the recovery. Same result. Cannot access the recovery.
So....I downloaded a Stock recovery image and used ADB and Fastboot to flash the stock recover. Same result....cannot access the recovery.
Can someone tell me what I am missing or what I am doing wrong? Or what I can do access recovery.? A rooted phone with an unlocked bootloader isn't much good if you can't access recovery.
Thanks for reading and for any advice you might be able to give.
Jeff
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
ESCollins90 said:
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
Click to expand...
Click to collapse
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
jlstark1 said:
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
Click to expand...
Click to collapse
If you haven't tried it already, since you seem to have ADB setup and working, try to use "adb reboot recovery" and see if you have change in luck. If not, my knowledge does not go much further, I hope someone knows how to answer this for you. I can imagine how distraught I'd be.
The only other thing is to ensure you've installed the correct recovery:
Google Dhacker29 and choose the AndroidHosting site, choose msm8960.
(I can't post url's because i've had less than 10 posts... spam thing)
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Hope you can figure it out! Good luck!
ESCollins90 said:
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Click to expand...
Click to collapse
Thanks!! Your 2 suggestions made the difference. Works like a charm!
jlstark1 said:
Thanks!! Your 2 suggestions made the difference. Works like a charm!
Click to expand...
Click to collapse
Awesome! Enjoy your new phone!![emoji1]
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.
-------------