Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
ibz100 said:
Hi,
I'm trying to sideload the final 5.0 build to my Nexus 5.
The ADB drivers are installed. This command prompt is opened in the desktop. I manage to get to the point in Recovery Mode where I need to flash the 'update.zip' (which I have named exactly that and this happens.
Anyone help me please?
Thanks beforehand.
I'm not a regular here, if I have broken the rules, please let a moderator know and sort me out. If this is an illegal thread, please delete it. Apologies.
Click to expand...
Click to collapse
Your usb drivers are not installed correctly, reinstall the drivers and enable usb debugging in developer options. Check if you succeeded by typing in cmd (while the phone is in fastboot): fastboot devices. You should see a serialnumber if all went well.
Hi, @ibz100. It actually looks like your drivers are installed properly. At least your ADB drivers. You only use ADB while booted into the android OS, or from recovery. However, while you're booted into the bootloader (also known as fastboot mode) you'll want to use "fastboot" commands.
So boot back into the bootloader either the same way using ADB while booted into the OS, or from a powered down state hold Volume down(-) & Power keys. You can also use both volume keys + power to access the Nexus 5's secondary bootloader.
Once in fastboot mode, run the command
Code:
fastboot devices
If your serial number appears like it did for ADB devices, then your fastboot drivers are successfully installed. If not, then we need to get your fastboot drivers set up.
Read here if you need to install them. Feel free to reply here if you're having trouble installing them and I can help you through that as well.
Also useful: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If your drivers are properly installed, run the command "fastboot" without quotations to see a list of available commands to be used in fastboot. If you're still not sure what to do, just ask.
If you want to use ADB to apply the update.zip, boot into recovery mode (I'm going to assume you're using a stock recovery). Use the commands I mentioned above to get to the bootloader. Now use the volume keys to navigate from "Start" to "Recovery Mode" With Recovery selected, key the Power button. You should see a picture of an android with an exclamation mark with the text "No Command". From there hold down the Power button and tap Volume UP(+) once. This will boot you into stock recovery mode. From there use the volume keys to navigate to "Apply update from ADB". Power key to select.
Check out the Roll-up sticky guide by @rootSU for all the information you need to get yourself up and running.
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Again, if you need any more help just reply and let me know, I'm more than happy to help.
Try loading koush's universal adb drivers I was having the same problem but this solved it for me. Sidelosd worked a treat and running lollipop without problems so far...
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
ibz100 said:
Thabk you everybody, I'll try your recommended (re)installation of my fastboot drivers later and get back to you if I have any further updates on my situation.
Big thanks for all the replies guys, I really was taken aback by the sheer effort you put into helping people around here. Rest assured that it doesn't go unappreciated. Keep up the good work!
Click to expand...
Click to collapse
Well I've had my fair share of driver issues. I blame my PC. Anyways, I know how frustrating it can be.
However going back to what I said before, since your ADB drivers are properly installed (being as your device ID showed up and reboot bootloader worked) I wouldn't think it's too far fetched that you already have fastboot drivers installed. Before you try deleting/reinstalling them, I would first boot into the bootloader and run the command "fastboot devices" (no quotes). If you device ID shows up in fastboot, there's no need to mess with your drivers.
Again, the reason ADB "stopped recognizing your device" is because you booted into fastboot mode. While you're in fastboot, you need fastboot commands.
If you boot back into the OS, or into recovery, ADB will recognize your device again. That's how it's supposed to be.
So power down the phone. Hold Volume Down(-) & Power until the phone boots into the bootloader and type;
Code:
fastboot devices
If your ID shows up in a similar fashion to the way it did in your screenshot, you're golden. Let us know how it goes! :good:
Related
I've been trying to flash a new kernal on my (rooted) Kacaso M766 and there really isn't much support for it anywhere.
Nevertheless, I have (as far as I know) successfully installed adb. Everything appears fine in adb, at least. Using the "devices" command shows the tablet, back up works, resetting adb with the root permission command works, and I was able to create a debug dump, but when I use the reboot to bootloader command, my tablet reboots to the OS still.
Any ideas of what could be wrong?
I can't get to the bootloader via button combinations, but I've figured out how to get to Fastboot and Recovery with button combinations and even safe mode, but none of them bring up the bootloader screen. There are only three buttons but like I said, little to no support for this manufacture so it might be some strange button combo for all I know.
Also when I go into fastboot then plug in a USB the tablet shows up as WM8950. Any idea what drivers would I use?
Any help would be welcome. :good:
Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked
You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.
Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.
1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.
No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.
jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk
I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.
Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse
Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.
I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?
'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!
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.
-------------
Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.