Database Info

[Solved-BADUSB]I think I managed to brick this Captivate

I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.

So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.

Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.

hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.

I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.

Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.

Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.

If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App

jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.

[Q] Tablet stuck in password screen + recovery mode doesn't work

Hello,
I'm sorry to bother you with an apparently repetitive thread, but I assure it is not.
I've been dealing with this problem for over a year now. Of course there were times that I simply gave up, but every now and then I searched all over the internet (seriously; very resilient, I am) and tried everything. Nothing seems to work.
The issue is: one day I was reading something on Google Reader and the tablet restarted. When it came back, it was in this password screen.
[AS A NEW USER I COULDN'T POST THE IMAGE - please see attachment ending in 41]
Detail: I had never, EVER set any kind of password. I don't do this with any of my devices unless I'm obliged to (as in Windows 8, this big piece of shiite).
So the thing is: I did not set a password, I did not choose to ask for a password in any situation and there isn't a single combination that I haven't tried. The thing doesn't even ask me to stop -- like 'hey, you've tried your 30k input, I think you should stop now'.
Now, for you not to start cursing me, I tried EVERYTHING that is basic and post-basic to fix it. I did wipe the data, I tried flashing another ROM, I did cold boot, factory reset, EasyFlashed, nvflashtf and whatnot. I swear to GoogleGods that I, as a non-expert-but-very-keen-on-technology, could.
Another thing that happens is when I try to enter the recovery mode, after using the nvflash, it doesn't work. The image that appears to me is this one:
[SAME THING -- attachment ending in 38]
Again: I'm not a complete noob. I know how to get into things; all I need is a simple guidance. I'm really sorry if this has been posted before and only I couldn't find it, but I won't be so if someone helps me to get it and solve my problem. I can't stand this anymore -- now it's just a matter of pride.
Thank you all.

This happened to me on my SL101 after I flashed a ROM of some sort. I used ADB commands to push the stock ROM back to it and to push another Recovery to it. Mine was in worse shape, Recovery loop, and then I finally got it to where yours currently is. My physical nor on screen keyboard would even work. Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D

DatDude123 said:
Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
Click to expand...
Click to collapse
Yeah, well, y'know, I'm not at this level yet, but I'll dig into ADB and stuff.
I tried to use this sometime in the past, but my computer was so bad back then that I had to give up to keep my sanity. Now I've got a fairly good one (very good, considering the few things I use it for), however much less time.
Tonight is the night, though. I'll study as much as I can and I'll fix this ****. Any tip you may remember now would be useful.
Thanks.

I'm struggling with something even before I start: there's no way I can get access to the system and turn the USB Debugging on.

I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.

maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
For some reason i thought you were on th sl101(slider) so i didnt comment. So heres the deal, any fix is going to be data destructive(nothing you can do at this point as even if you manage to pull data from the tablet, it will be encripted) You need Easyflasher(dev section) follow the instructios there (basically donwloading stock firmware from asus and by using nvflash in apx mode it will re-partition storage, and upload the stock firmware to the tf101)
If you hit any problems, post them here and ill help you further
Edit: just read you post more, if you tried easyflaher and it didnt work, please post the details of what you tried within easyflasher.
Its a strange issue, if it happend to me and id tried the things you already have, this is what id try:
-Flashing ubuntu from the dev section(i known very little about how nvflash works but it maybe only re-partitioning certain partitions, ubuntu i would imagine would require a full re-partitioning)
-alternativly (or on top of the previous idea) use one of the ubuntu installers(OLiFE on ubuntu worked the best for me, but franks tools/ newer software based on franks tools should work fine) and flash the Prime! rom on its own.
If these dont work, your last resort is asus - but thats a long shot lol

maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
If you can't get into anything, but you can enter APX Mode, but NVFlash doesn't work, then I'm not sure anything will as NVFlash completey deletes and recreates all the partitions on the drive
So unless you have been unlucky and downloaded a bad version of an NVFlash ROM....
I know you say you have used NVFlash but I`ll stick this here anyway
The way I restore is:
Connect tablet to PC and make sure the tablet is turned off (Make sure it is the only USB device connected other than keyboard/mouse)
Hold Volume Up + Power for a few seconds until you hear the USB connect sound on the PC, release the buttons, you are in APX mode
Install APX drivers if you have not already
Now extract this
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
And run "download.bat"
I think you should see some text appear on the tablet screen, and progress will be shown in the command prompt window on the PC
Wait for it to complete 100%
Its been a while so I can't remember if the tablet will reboot on its own or if you need to hold power for 30 seconds to get out of APX mode
Either way, make sure it is completely finished and reboot the tablet
Only thing I can remember going wrong with NVFlash was the first time I rebooted after a sucessful boot, it would hang on a black screen
Just hold power for 30 seconds and then power on normally, done, if it has worked you have your tablet back, if not, I think its a hardware issue > see asus

Im very keen to get this fixed/ find the issue as uptil now I thought the tf101 was virtually software invincible, you need to pay attention to what the nvflash process says, the one thing I can think of as to why nvflash didn't work is it can't write over encrypted partitions although that would make no sense why it wouldn't.

Just a suggestion... make sure you're not docked. Some people report issues when nvflashing while docked (I can't replicate those issues except with the Tubuntu tool).

Is there a solution?
I also have an error! see picture

[Q] Bricked worse than I thought? Help! (long)

Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.

Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?

Oop. duplicate post

It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.

Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,

If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.

That's just another download screen that theraze is describing.

Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.

Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?

The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.

Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.

[Completed] Screen inaccessible(no display) usb debug disabled cmd help

Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.

momostarz said:
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please direct your question here for further assistance:
http://forum.xda-developers.com/google-nexus-5/help/help-thread-nexus-5-question-t2496506
Good luck!

Please help - flashing incomplete

So I was trying to just do a clean install. This phone had no mods installed.
I have done this many times and all went well. I am hoping that someone can help me understand what went wrong.
So working on linux, latest fastboot/adb (29.0.6-6198805) and the March image for blueline.
flashing radio and bootloader went fine. When I got to flashing the kernel it stopped after writing slot_a and rebooting into fastboot. I got the message "waiting for any device"
The phone displayed a warming (see pics) that the bootloader is unlocked and phone vulnerable and gave me an option to pause. after a few seconds it went into a "fastbootd" screen that I never saw before (see pic attached) which gave me options to restart or go back to bootloader. Either option breaks the flashing sequence which ends with error.
Re-flashing produces the same result.
Any suggestions what causes this?
Of course the phone does not boot anymore. But I can get to bootloader again using key sequence. Bootloader is unlocked.
Thank you!

Fastbootd happens part way through a flash-all beginning with Android 10. I assume you are using the flash-all script and now doing each command individually. If not, edit the flash-all to get rid of the -w to dirty flash and keep apps and user data. My guess though is that your path is referring to an older version of fastboot. If you have ever installed the apt version of fastboot, it becomes the first to load in your path. Instead, drop the March files into your updated platform-tools folder and ./ the flash-all command in terminal directly from that folder. In a pinch, you can also sideload the ota zip (which you will need to download separately of course) from fastbootd by entering recovery from there and sideloading. Fastbootd gets you into user space, so you should have adb sideload ability.

there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?

sliding_billy said:
Fastbootd happens part way through a flash-all beginning with Android 10.
Click to expand...
Click to collapse
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?

metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
metricusa said:
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?
Click to expand...
Click to collapse
I've never ran ChromeOS, but the reboot into fastbootd not retaining the connection would definitely be a problem. The sideload does no reboots until install is complete, so that would be a better way for sure. In reality the phone did at least one reboot into fastbootd. You'd need to try a flash-all with -w in place to see if it could pull off a clean install with the factory image and not lose track of the connection. No doubt it will lose track with individual commands . The normal sequence for factory flash now is just that... run the flash-all .sh it will go into fastbootd during install while terminal will continue to work. There are definitely some spots where nothing appears to be happening on the phone or terminal until reboot. Given the remote nature of your install, I do think a sideload (follow the directions on the pixel ota developers page where you DL the file) is the best option for you.

metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
I had the same problem with my PixelBook. My conclusion was ChromeOS does not forward the USB connection to the Linux container before the phone times out, but your theory about loosing USB permission may be correct. If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.

dcarvil said:
If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.
Click to expand...
Click to collapse
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.

metricusa said:
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.
Click to expand...
Click to collapse
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?

wangdaning said:
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?
Click to expand...
Click to collapse
I'll try that.
Unplugging opens another can of worms:
The reason we are doing this is bc the phone suddenly has a problem charging. Opening the battery setting shows a red battery with the message "can't charge now". Also if plugged in while turned off the little battery shows a question mark.
Google offered to exchange it but shipping it back and forth from Europe is 140$ each way and I got a new phone for less. On top of this I risk having to pay import taxes on it.
So in short, if unplugged the phone dies.
The intent of doing this burn was to see if this issue is software related. As I said it happened suddenly after a simple restart. Battey was fine and after restart was not.
I have a feeling it's not the software though.

Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.

wangdaning said:
Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.
Click to expand...
Click to collapse
Well the option is through fedex/ups. Shipping USPS has resulted many times in the package being stuck in customs for weeks. And the price is not necessarily much lower.
Yes we looked into having it seen by a repair shop but normally we should have been able to do flash it ourselves. Plus it's a good experience for her to be exposed to some linux and the basics of hacking a phone.
Another reason is that this has a high chance of being hardware related so whatever we spend on repair shop is wasted money.
I got her a Samsung A51 and she is out of trouble for now. I have had several bad experiences with pixels so this time I am officially done with spending a fortune on them.
Update as of this morning: It is clear that the USB permission is lost while fastboot performs a reboot during flashing. We tried to quickly re-allow the permission but while the terminal waits for a device patiently it looks that the loss of link is long enough for the phone to decide that something went wrong and goes into fastbootd.
We also tried to flash just the boot.img in both slots . that went well apparently but did not change anything and the phone is still unbootable. Tried recovery but it went back into bootloader with the error that it cannot boot boot.img.
So next step is sideload. i have to figure how that works

fastboot reboot fastboot, select recovery, apply update from ADB, adb sideload whatever.zip
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on? I mean the phone will technically reboot going from bootloader to fastboot (fastbootd) and the permission will be lost. At least a repair shop could use a proper computer to test it.

wangdaning said:
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on?
Click to expand...
Click to collapse
The phone stays on while it is connected to usb. Never died in this process. The connection loss is because of permissions not power.

Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!

metricusa said:
Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!
Click to expand...
Click to collapse
Glad you got the device up. As for the charging issue, have you tried a different wired charger or a wireless charger? I assume you are converting power somehow in Europe.

sliding_billy said:
have you tried a different wired charger or a wireless charger?
Click to expand...
Click to collapse
Yes. Tried different charger and a battery pack and also charging through USB from laptop. Did not try wireless. Before I bought the new phone she was using the phone connected to a battery pack.
As you can see in the pic the battery is red and it says "can't charge" while confirming that it does receive power.
I Googled the issue and there are several reports about same behavior. I also did talk to a repair shop over the phone and they said that the power module goes bad and it is a known problem with pixel 2 and 3. He also mentioned that there is a class action lawsuit but I cannot confirm the info.
It doesn't really matter at this point.
My aim was to eliminate the remote possibility this problem was due to some software issue. We solved this and from now on it's a google issue. As I mentioned Google offered to exchange the phone. But with COVID we had to postpone some flights when we could have made the exchange.
I will contact Google and ask for some workaround the COVID crisis. I hope they will be cooperative. I don't see why not.
Thank you all for your help!